Remote operation and maintenance arrangement method and operation and maintenance system for transformer substation monitoring system application program

Abstract

The invention discloses a remote operation and maintenance arrangement method and an operation and maintenance system for a transformer substation monitoring system application program, and belongs to the field of power system operation and maintenance. The method comprises the steps that if a scheduling system receives a selection instruction for a target template option in a plurality of task template options, an editing interface is displayed, and if an editing instruction for a service configuration item and / or a resource configuration item is received, services and / or resources needed by a target task are edited, and generating a target configuration file and sending the target configuration file to a monitoring system. And an arrangement module in the monitoring system updates the configuration file of the first application program according to the target configuration file. Therefore, the first application program can fully utilize resources and services in the monitoring system to execute the target task according to the configuration file. Tasks can be flexibly configured on the basis of the task templates in the scheduling system, diversity of task configuration is achieved, and therefore the operation and maintenance requirements of a transformer substation can be met.

Description

Technical Field

[0001] The present application relates to the field of power system operation and maintenance, and in particular to a remote operation and maintenance orchestration method and operation and maintenance system for a substation monitoring system application. Background Art

[0002] In the power system, substations are important nodes for power transmission and distribution. During the operation of substations, various emergencies may occur, such as equipment failure, damage, load abnormality, etc., which will affect the operation of substations and may even cause safety accidents. Based on this, the operation and maintenance of substations is extremely important. However, the current operation and maintenance tasks of substations are relatively simple, and only the monitoring of substation status can hardly meet the growing operation and maintenance needs of substations. Summary of the invention

[0003] The present application provides a remote operation and maintenance orchestration method and operation and maintenance system for a substation monitoring system application, which can better meet the operation and maintenance needs of the substation. The technical solution is as follows:

[0004] In a first aspect, a remote operation and maintenance orchestration method for a substation monitoring system application is provided, the method being applied to an operation and maintenance system, the operation and maintenance system comprising a monitoring system and a dispatching system, the monitoring system comprising an orchestration module and a plurality of applications, the plurality of applications corresponding one-to-one to a plurality of tasks, the method comprising:

[0005] The scheduling system displays a configuration interface, the configuration interface includes a plurality of task template options, and the plurality of task template options correspond one to one with the plurality of tasks; in response to a received selection instruction for a target template option, an editing interface is displayed, the editing interface includes a service configuration item and a resource configuration item, and the target template option is any one of the plurality of task template options; in response to a received editing instruction for the service configuration item and / or the resource configuration item, the service and / or resource required for the target task corresponding to the target template option is edited; in response to an application instruction received on the editing interface, a target configuration file is generated; and the target configuration file is sent to the monitoring system;

[0006] After receiving the target configuration file, the orchestration module updates a configuration file of a first application according to the target configuration file, where the first application is an application corresponding to the target task among the multiple applications;

[0007] The first application executes the target task through the services and / or resources in the monitoring system according to the configuration file of the first application.

[0008] In this application, the application in the monitoring system can make full use of the resources and services in the monitoring system when executing tasks. In addition, the dispatching system includes multiple task templates, on the basis of which tasks can be flexibly configured to achieve the diversity of task configuration, thereby meeting the substation operation and maintenance needs.

[0009] Optionally, the services in the monitoring system include one or more of real-time library services, message bus services, historical library services, and control bus services, and / or the resources in the monitoring system include one or more of telemetry, telesignaling, telepulse, remote control, set values, parameters, permissions, and security audits.

[0010] Optionally, the resource configuration items include one or more of resource import configuration items and resource export configuration items.

[0011] Optionally, the editing interface also includes one or more of execution cycle configuration items and device configuration items.

[0012] Optionally, each of the multiple applications is deployed in a container.

[0013] Optionally, the method further comprises:

[0014] The scheduling system obtains an application installation file and a container installation file of a second application; if the container corresponding to the second application does not exist in the monitoring system, the application installation file and the container installation file are sent to the monitoring system;

[0015] After receiving the application installation file and the container installation file, the orchestration module deploys the second application in the corresponding container according to the application installation file and the container installation file.

[0016] Optionally, the method further comprises:

[0017] The scheduling system sends a container destruction request to the monitoring system, where the container destruction request carries a target container identifier;

[0018] After receiving the container destruction request, the orchestration module destroys the container identified by the target container identifier.

[0019] Optionally, after the first application executes the target task through the services and / or resources in the monitoring system according to the configuration file of the first application, the method further includes:

[0020] The first application sends the execution result of the target task to the scheduling system through the orchestration module.

[0021] Optionally, the target task is used to obtain device data, and the method further includes:

[0022] When the first application determines according to the device data that an abnormal device state occurs, the first application sends an alarm message to the target device.

[0023] In a second aspect, an operation and maintenance system is provided, the operation and maintenance system comprising a monitoring system and a scheduling system, the monitoring system comprising an orchestration module and a plurality of applications, the plurality of applications corresponding one-to-one to a plurality of tasks;

[0024] The scheduling system is used to display a configuration interface, the configuration interface includes multiple task template options, and the multiple task template options correspond to the multiple tasks one by one; in response to a received selection instruction for a target template option, display an editing interface, the editing interface includes a service configuration item and a resource configuration item, and the target template option is any one of the multiple task template options; in response to a received editing instruction for the service configuration item and / or the resource configuration item, edit the service and / or resource required for the target task corresponding to the target template option; in response to an application instruction received on the editing interface, generate a target configuration file; and send the target configuration file to the monitoring system;

[0025] The orchestration module is configured to update a configuration file of a first application according to the target configuration file after receiving the target configuration file, where the first application is an application corresponding to the target task among the multiple applications;

[0026] The first application is used to execute the target task through the services and / or resources in the monitoring system according to the configuration file of the first application.

[0027] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the operations performed by the monitoring system or the dispatching system in the remote operation and maintenance orchestration method of the substation monitoring system application program described in the first aspect.

[0028] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the operations performed by the monitoring system or the dispatching system in the remote operation and maintenance orchestration method of the substation monitoring system application program described in the first aspect above are implemented.

[0029] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the operations performed by the monitoring system or the dispatching system in the remote operation and maintenance orchestration method of the substation monitoring system application program described in the first aspect above.

[0030] It can be understood that the beneficial effects of the second, third, fourth and fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments 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 creative work.

[0032] Figure 1 is a schematic diagram of an operation and maintenance system provided in an embodiment of the present application;

[0033] Figure 2 It is a flow chart of a remote operation and maintenance orchestration method of a substation monitoring system application provided by an embodiment of the present application;

[0034] Figure 3 This is a flowchart of an application installation, interaction and destruction process provided by an embodiment of the present application;

[0035] Figure 4 It is a flow chart of another remote operation and maintenance orchestration method of a substation monitoring system application provided by an embodiment of the present application;

[0036] Figure 5 It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0037] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0038] It should be understood that the "multiple" mentioned in this application refers to two or more. In the description of this application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in order to facilitate the clear description of the technical solution of this application, the words "first" and "second" are used to distinguish between the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the words "first" and "second" do not limit the quantity and execution order, and the words "first" and "second" do not limit them to be different.

[0039] The phrases such as "one embodiment" or "some embodiments" described in the present application mean that the specific features, structures or characteristics described in the embodiment are included in one or more embodiments of the present application. Therefore, the phrases such as "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments" that appear in the differences in the present application do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. In addition, the terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0040] The application scenarios involved in the embodiments of the present application are described below.

[0041] With the continuous development of science and technology, electricity has become an indispensable energy source in life, providing convenience for people. As an important node for power transmission and distribution, the operation and maintenance of substations is extremely important.

[0042] At present, the state data and measurement values ​​of the substation are mainly transmitted in real time through the power system communication protocol, and then the state data and measurement values ​​are compared with the set values ​​and processed accordingly to achieve the operation and maintenance of the substation. However, this operation and maintenance method is relatively fixed and it is difficult to meet the growing operation and maintenance needs.

[0043] To this end, an embodiment of the present application provides a remote operation and maintenance orchestration method for a substation monitoring system application, which can improve the diversity of operation and maintenance task configuration and better meet the operation and maintenance needs of the substation.

[0044] The operation and maintenance system provided in the embodiment of the present application is described below.

[0045] Figure 1 is a schematic diagram of an operation and maintenance system provided in an embodiment of the present application. Figure 1The operation and maintenance system 10 may include a scheduling system 101 and a monitoring system 102, wherein the monitoring system 102 may include an orchestration module and multiple applications.

[0046] The scheduling system 101 can communicate with the monitoring system 102 via a wired connection or a wireless connection. Specifically, the scheduling system 101 can communicate with the orchestration module in the monitoring system 102 via a wired connection or a wireless connection.

[0047] The scheduling system 101 is used to configure operation and maintenance tasks (hereinafter referred to as tasks), generate configuration files corresponding to the tasks, and send requests to the monitoring system 102 accordingly. For example, the scheduling system 101 may be a cloud server.

[0048] The monitoring system 102 is used to monitor and operate the substation. The monitoring system 102 can also receive and respond to requests from the dispatching system 101.

[0049] The orchestration module is used to respond to the request sent by the scheduling system 101. Specifically, the configuration file of the corresponding application program in the multiple applications can be updated according to the received request. The orchestration module can also manage each application program in the multiple applications.

[0050] Each of the plurality of applications is used to perform a task. For example, the application can perform a task by monitoring services and / or resources in the system 102.

[0051] The services and resources in the monitoring system 102 can be pre-set. The services in the monitoring system 102 provide functional and operational support for the monitoring system 102 to monitor and operate the substation. The resources in the monitoring system 102 are the hardware and software components in the monitoring system 102, which are used to support the implementation of the services in the monitoring system 102.

[0052] In some embodiments, a technician can import a substation configuration description (SCD) file into the monitoring system 102, and the monitoring system 102 can parse the SCD file to obtain corresponding resources; of course, the monitoring system 102 can also obtain corresponding resources by parsing other files, and the embodiments of the present application are not limited to this.

[0053] For example, the services in the monitoring system 102 may include one or more of a real-time library service, a message bus service, a history library service, a control bus service, and the like.

[0054] The real-time library service is used to store and process real-time data of substation equipment, such as the current status of substation equipment, sensor data, etc., to support real-time monitoring and response.

[0055] The message bus service is used to transmit messages and events between various components within the monitoring system 102, and is used to implement communication and collaboration between the monitoring systems 102.

[0056] The historical database service is used to store and manage historical data, including substation equipment operation data, alarm records, etc., and supports data analysis and backtracking.

[0057] The control bus service is used to transmit and execute substation equipment control commands, and supports operations such as remote control of substation equipment.

[0058] For example, the resources in the monitoring system 102 may include one or more of a substation equipment list, telemetry, telesignaling, telepulse, remote control, set values, parameters, permissions, and security audit.

[0059] The substation equipment list is used to define the type and function of all equipment in the substation.

[0060] Telemetry is used to monitor physical quantities such as voltage, current, frequency, etc. inside and outside the substation in real time.

[0061] Telesignaling is used to transmit substation equipment status information, such as the switch status of circuit breakers, relay status, etc.

[0062] Remote pulse is used to transmit measurement and event signals, such as the reading of the energy meter, the number of overcurrent protection actions, etc.

[0063] Remote control is used to remotely operate equipment, such as remote switching, adjusting equipment parameters, etc.

[0064] The set value is the preset parameter for equipment operation, such as the action value of the protection device, the rated parameters of the equipment, etc., to ensure that the equipment is within the safe and standardized operating range.

[0065] Parameters are specific configuration parameters for substation equipment, such as the rated voltage, current, capacity, etc. of the equipment, which are used for precise regulation and management of substation equipment.

[0066] Permissions are the authority control for technicians in the monitoring system 102, ensuring that only authorized personnel can access and operate key resources.

[0067] Security audit is the review and recording of system operations and access, which is used to track operation logs and identify potential security threats and operational anomalies.

[0068] In the embodiment of the present application, the technician can configure the task through the dispatching system 101, and the dispatching system 101 can generate a configuration file corresponding to the task, and then send the configuration file to the orchestration module in the monitoring system 102. After receiving the configuration file, the orchestration module updates the configuration file of the corresponding application according to the configuration file, and then the application executes the task indicated by the configuration file, and after executing the task, returns the execution result of the task to the dispatching system 101 to complete the monitoring and operation and maintenance of the substation.

[0069] The remote operation and maintenance orchestration method of the substation monitoring system application provided in the embodiment of the present application is explained in detail below.

[0070] It should be noted that the multiple applications in the monitoring system correspond to the multiple tasks one by one, and each of the multiple applications is used to perform a corresponding task. For example, the multiple tasks may include one or more of equipment status detection tasks, equipment control tasks, intelligent inspection tasks, data collection tasks, etc.

[0071] In some embodiments, each of the multiple applications can be deployed in a container, wherein different applications can be deployed in different containers.

[0072] For example, each of the multiple applications can be deployed in a container through k8s (kubernetes) technology.

[0073] It should be noted that in the embodiment of the present application, before configuring the task through the scheduling system, a container for carrying the application program can be installed in the monitoring system, and an application program for executing the corresponding task can be deployed in the container.

[0074] In some embodiments, the scheduling system can obtain the application installation file and container installation file of the second application, and then query whether there is a container corresponding to the second application in the monitoring system. If there is no container corresponding to the second application in the monitoring system, the scheduling system sends the application installation file and the container installation file to the monitoring system; after the orchestration module receives the application installation file and the container installation file, it deploys the second application in the corresponding container according to the application installation file and the container installation file. If there is a container corresponding to the second application in the monitoring system, the scheduling system sends the application installation file to the monitoring system; after the orchestration module receives the application installation file, it deploys the second application in the corresponding container according to the application installation file.

[0075] The second application is an application that needs to be installed.

[0076] The application installation file of the second application is used to install the second application, and includes the program code of the second application. For example, the application installation file of the second application can be an original file or a mirror file.

[0077] The container installation file of the second application is used to install the container, and contains the operating environment data of the second application. For example, the container installation file can be an original file or a mirror file of the container.

[0078] The application installation file and container installation file of the second application may be uploaded to the scheduling system by a technician, or may be obtained by the scheduling system from other systems, which is not limited in this embodiment of the present application.

[0079] For example, the orchestration module may pre-store a correspondence between a container identifier and an application identifier (hereinafter referred to as a first correspondence), the first correspondence including an application identifier corresponding to the container identifier of each container installed in the monitoring system, and the application identifier corresponding to the container identifier is the identifier of the application deployed in the container identified by the container identifier. For example, the application identifier may be an application version number, and the container identifier may be a container name.

[0080] In this case, after the scheduling system obtains the application installation file and container installation file of the second application, it can send a query request carrying the identifier of the second application to the monitoring system. After receiving the query request, the orchestration module queries the container identifier corresponding to the identifier of the second application in the first corresponding relationship, and returns the query result to the scheduling system. After the scheduling system receives the query result, if the query result indicates that the corresponding container identifier is queried, it means that the container corresponding to the second application already exists in the monitoring system, so there is no need to install the container, and the application installation file of the second application is sent to the monitoring system; if the query result indicates that the corresponding container identifier is not queried, it means that the container corresponding to the second application does not exist in the monitoring system, so it is necessary to install the container, and the application installation file and container installation file of the second application are sent to the monitoring system.

[0081] In some embodiments, the monitoring system may include an application programming interface (API) gateway.

[0082] The API gateway is used to provide various interface services. The interface services in the API gateway can be pre-set. For example, they can be set by a technician according to needs. For example, the interface services in the API gateway may include one or more of an application installation service, a file push service, a container creation service, an update application configuration service, a start application service, a stop application service, a container destruction service, a real-time data service, a command service, a historical query interaction service, etc.

[0083] For example, the scheduling system may call the application installation service shown in Table 1 below to send a query request to the monitoring system to query whether there is a container corresponding to the second application in the monitoring system.

[0084] Table 1

[0085]

[0086] The embodiment of the present application only uses Table 1 above as an example to exemplify the application installation service, and Table 1 above does not constitute a limitation on the embodiment of the present application.

[0087] Optionally, when there is no container corresponding to the second application in the monitoring system, the scheduling system can send not only the application installation file and container installation file of the second application to the monitoring system, but also the default configuration file of the second application. Similarly, when there is a container corresponding to the second application in the monitoring system, the scheduling system can send not only the application installation file of the second application to the monitoring system, but also the default configuration file of the second application to the monitoring system.

[0088] The default configuration file of the second application is used to indicate the task that the second application needs to perform. For example, the default configuration file may include an identifier of the task corresponding to the second application.

[0089] For example, the scheduling system can call the file push service shown in Table 2 below to send the application installation file of the second application to the monitoring system, or send the application installation file and a default configuration file of the second application, or send the application installation file and a container installation file of the second application, or send the application installation file, container installation file, and default configuration file of the second application.

[0090] Table 2

[0091]

[0092] The embodiment of the present application only uses Table 2 above as an example to exemplify the file push service, and Table 2 above does not constitute a limitation on the embodiment of the present application.

[0093] In some embodiments, if the orchestration module in the monitoring system receives the application installation file and the container installation file, it can first install the container according to the container installation file, and then deploy the second application in the container according to the application installation file. Afterwards, the orchestration module can store the container identifier of the container and the identifier of the second application in the first corresponding relationship in correspondence.

[0094] In other embodiments, if the orchestration module receives the application installation file, it can first determine the container corresponding to the second application, such as determining the container identified by the container identifier corresponding to the identifier of the second application in the first correspondence, and then deploy the second application in the container according to the application installation file.

[0095] For example, when the orchestration module deploys the second application in the container according to the application installation file, it can first install the second application according to the application installation file, then map the second application to the container, and then create a container instance of the container.

[0096] For example, the orchestration module may call the container creation service shown in Table 3 below to create a container instance.

[0097] Table 3

[0098]

[0099] The embodiment of the present application only uses Table 3 as an example to exemplify the container creation service, and Table 3 does not limit the embodiment of the present application.

[0100] Furthermore, after the orchestration module deploys the second application in the corresponding container, the configuration file (also referred to as a capability description configuration file) of the second application can be updated to a default configuration file sent by the scheduling system.

[0101] For example, the orchestration module may call the update application configuration service shown in Table 4 below to update the configuration file of the second application to the default configuration file.

[0102] Table 4

[0103]

[0104] The embodiment of the present application only uses Table 4 above as an example to exemplify the updating application configuration service, and Table 4 above does not constitute a limitation on the embodiment of the present application.

[0105] Optionally, the orchestration module may start the second application after updating the configuration file of the second application.

[0106] For example, the orchestration module may call the application startup service shown in Table 5 below to start the second application.

[0107] Table 5

[0108]

[0109] The embodiment of the present application only uses Table 5 above as an example to exemplify the application startup service, and Table 5 above does not constitute a limitation on the embodiment of the present application.

[0110] Optionally, after starting, the second application may read a configuration file of the second application, perform initialization accordingly, and execute tasks indicated by the configuration file.

[0111] In some cases, while executing a task, the second application may call a real-time data service to obtain data from substation equipment or send data to the dispatching system; and / or, the second application may call a command service to send a command to the substation equipment; and / or, the second application may call a historical query interaction service to obtain historical data from the dispatching system or other modules.

[0112] For example, the second application may call the real-time data service (such as datapublish service, datasuscribe service), command service (such as cmdpublish service, cmdsuscribe service), or historical query interaction service (such as sqlexecute service, sqlquery service) shown in Table 6 below.

[0113] Table 6

[0114]

[0115] The embodiment of the present application only uses Table 6 above as an example to exemplify the real-time data service, command service and historical query interaction service, and Table 6 above does not constitute a limitation on the embodiment of the present application.

[0116] In some embodiments, the arrangement module may store a correspondence between application program identifiers and task identifiers (hereinafter referred to as a second correspondence). The second correspondence includes a correspondence between the identifier of each application program installed in the monitoring system and the identifier of a task that the application program can perform.

[0117] After the orchestration module deploys the second application in the corresponding container, it can return an installation completion message to the scheduling system. After receiving the installation completion message, the scheduling system can set a task template for the task corresponding to the second application and add an option for the task template in the configuration interface. Subsequent technicians can flexibly configure the task according to the configuration interface, which is described in detail below:

[0118] Figure 2 1 is a flow chart of a remote operation and maintenance orchestration method for a substation monitoring system application provided by an embodiment of the present application. Figure 2 , the method comprises the following steps:

[0119] Step 201: The scheduling system displays a configuration interface, which includes a plurality of task template options, and the plurality of task template options correspond one to one to a plurality of tasks.

[0120] The configuration interface is an interface for configuring tasks. The configuration interface can be a front-end interface of the scheduling system. Specifically, a technician can access the scheduling system through an application (such as a browser or other specific application) in a computer device to display the configuration interface in the application. For example, the computer device can be a desktop, a portable computer, a handheld computer, a mobile phone, or a tablet computer, etc., and the embodiments of the present application are not limited to this. In this way, a technician can configure tasks anytime and anywhere, so that the operation and maintenance efficiency can be improved.

[0121] The task template option is an option corresponding to the task template. For example, the multiple task template options may include one or more of the device status detection task template option, the device control task template option, the intelligent inspection task template option, the data collection task template option, etc., which is not limited in the embodiments of the present application.

[0122] The multiple task template options correspond to the multiple task templates one by one, and the multiple task templates correspond to the multiple tasks one by one. Each task template in the multiple task templates is used to configure a corresponding task.

[0123] Step 202: The scheduling system displays an editing interface in response to the received selection instruction for the target template option, the editing interface including service configuration items and resource configuration items, and the target template option is any one of the multiple task template options.

[0124] The selection instruction for the target template option is used to select the target template option. The selection instruction can be triggered by a technician, such as a click operation, a slide operation, a voice operation, a gesture operation, or a somatosensory operation, etc., which is not limited in the present embodiment of the application.

[0125] Here, the task template corresponding to the target template option is called the target task template, and the task corresponding to the target task template is called the target task.

[0126] The service configured by this service configuration item is the service in this monitoring system.

[0127] The resources configured by this resource configuration item are the resources in the monitoring system.

[0128] The service configuration item is used to configure the services that the target task depends on. The service indicated by the service configuration item provides functional and operational support for the monitoring system to monitor and operate the substation. For example, the services in the monitoring system may include one or more of a real-time library service, a message bus service, a history library service, a control bus service, etc.

[0129] The resource configuration item is used to configure the resources that the target task depends on. The resources indicated by the resource configuration item are the hardware and software components in the monitoring system, which are used to support the implementation of the services in the monitoring system. For example, the resources in the monitoring system may include one or more of telemetry, telesignaling, telepulse, remote control, set values, parameters, permissions, security audits, etc.

[0130] In some embodiments, the resource configuration item may include one or more of a resource import configuration item and a resource export configuration item.

[0131] The resource import configuration item is a configuration item for the data that needs to be input when the target task is executed.

[0132] The resource export configuration item is a configuration item for the data that needs to be output after the target task is executed.

[0133] Optionally, the editing interface may also include one or more configuration items such as execution cycle configuration items and device configuration items.

[0134] The execution cycle configuration item is a configuration item of the target task execution cycle. For example, the execution cycle configuration item may include single time, daily, etc.

[0135] The equipment configuration item is a configuration item for the identification of the substation equipment required for operation and maintenance of the configuration target task.

[0136] Optionally, the editing interface may also include target device configuration items.

[0137] The target device configuration item is used to configure the target device to be notified when the task execution ends and / or an abnormality occurs in the device. For example, the target device can be a desktop computer, a terminal, etc., which is not limited in the embodiment of the present application.

[0138] Since the configuration interface displays all configuration items related to the target task corresponding to the target template option, the technician can know all configuration contents that can be edited when configuring the target task based on the editing interface.

[0139] Step 203: The scheduling system edits the services and / or resources required for the target task corresponding to the target template option in response to the received editing instruction for the service configuration item and / or the resource configuration item.

[0140] The editing instruction is an instruction for editing the configuration content of the service configuration item (ie, the service) and / or the configuration content of the resource configuration item (ie, the resource).

[0141] The editing instruction may be triggered by a technician, who may edit the configuration content of one or more of the service configuration item and the resource configuration item.

[0142] The editing instructions of the technician for the service configuration item and the resource configuration item may be triggered separately. Whenever the scheduling system receives an editing instruction for the service configuration item (or the resource configuration item), it may edit the configuration content of the service configuration item (or the resource configuration item) according to the editing instruction received this time.

[0143] Step 204: The scheduling system generates a target configuration file in response to the application instruction received in the editing interface.

[0144] The target configuration file is a configuration file of the application corresponding to the target task. The target configuration file contains information about the target task to be executed by the application, such as the identifier of the target task, and information about the services and / or resources required by the target task.

[0145] The application instruction is used to indicate that the target task has been configured. The application instruction can be triggered by a technician, such as a technician who can trigger the application instruction through a click operation, a slide operation, a voice operation, a gesture operation, a somatosensory operation, or the like.

[0146] After the technician completes editing the service configuration item and / or the resource configuration item in the editing interface, the application instruction may be triggered to instruct generation of a configuration file corresponding to the target task, ie, a target configuration file.

[0147] Step 205: The scheduling system sends the target configuration file to the monitoring system.

[0148] For example, the scheduling system may call the file push service shown in Table 2 above to send the target configuration file to the monitoring system.

[0149] Step 206: After receiving the target configuration file, the orchestration module in the monitoring system updates the configuration file of the first application according to the target configuration file.

[0150] The first application is an application corresponding to the target task among the multiple applications in the monitoring system. For example, the arrangement module can search for the corresponding application identifier from the second corresponding relationship according to the identifier of the target task in the target configuration file, and the found application identifier is the identifier of the first application for executing the target task.

[0151] The orchestration module may update the configuration file of the first application according to the identifier of the first application and the target configuration file, that is, update the configuration file of the first application to the target configuration file.

[0152] For example, the orchestration module may call the update application configuration service shown in Table 4 above to update the configuration file in the first application.

[0153] In some embodiments, the orchestration module may start the first application after updating the configuration file of the first application according to the target configuration file.

[0154] For example, the orchestration module may call the application startup service shown in Table 5 above to start the first application, so that the first application can read the updated configuration file to run.

[0155] Step 207: The first application executes the target task through the services and / or resources in the monitoring system according to the configuration file of the first application.

[0156] Since the configuration file of the first application program configures the resources and / or services that the first application program needs to rely on to execute the target task, the first application program can call the corresponding service to execute the target task according to the input parameters (such as resources).

[0157] For example, taking the intelligent patrol task as an example, the resource import configuration item in the target configuration file is configured with the input parameters (such as resources) required to execute the intelligent patrol task, and the input parameters need to rely on the telemetry data of the substation equipment. Then the first application can call the corresponding service to obtain the telemetry data of the substation equipment to be patrolled, and after obtaining the telemetry data, execute the specific task content of the intelligent patrol task according to the telemetry data. In this way, the execution of the intelligent patrol task can be realized.

[0158] It should be noted that the embodiments of the present application can achieve remote operation and maintenance through multiple applications in the monitoring system, which can reduce the deployment and maintenance costs of the monitoring system.

[0159] Optionally, if the target task is used to obtain device data, the first application may send an alarm message to the target device when determining that an abnormal device state occurs according to the device data.

[0160] The target device is a device that needs to receive alarm information, and may be a device used by a technician.

[0161] In this way, technicians can quickly respond to and handle the abnormal situation, thus reducing fault handling time and improving equipment reliability and operational stability.

[0162] In some embodiments, after executing the target task, the first application may send the execution result of the target task to the scheduling system through the orchestration module.

[0163] For example, after executing the target task, the first application can call the datapublish service shown in Table 6 to send the execution result of the target task to the orchestration module, and after receiving the execution result, the orchestration module returns the execution result to the scheduling system. The scheduling system can receive and store the execution result.

[0164] In some cases, if the target task corresponding to the target configuration file is a single task, the first application program may automatically stop running after executing the target task.

[0165] If the target task corresponding to the target configuration file is a periodic task, the first application will continue to run after executing the target task each time. In this case, if there is a need to end the operation of the first application, the scheduling system can instruct the first application to end the operation.

[0166] For example, the scheduling system may call the application stop service shown in Table 7 below to instruct the orchestration module to end the operation of the first application.

[0167] Table 7

[0168]

[0169] The embodiment of the present application only uses Table 7 above as an example to exemplify how to stop the application service. Table 7 above does not limit the embodiment of the present application.

[0170] As an example, if there is a need to uninstall the target application, the scheduling system may instruct the orchestration module to uninstall the target application.

[0171] The target application is the application that needs to be uninstalled.

[0172] It should be noted that if only the target application is uninstalled without destroying the corresponding target container, the orchestration module does not need to update the correspondence between the identifier of the target container and the identifier of the target application in the first correspondence. In this way, when the target application needs to be reinstalled later, it can be deployed directly in the target container without reinstalling the target container.

[0173] As an example, if there is a need to destroy the target container, the scheduling system may instruct the orchestration module to destroy the target container.

[0174] For example, the scheduling system sends a container destruction request to the monitoring system, where the container destruction request carries a target container identifier; after receiving the container destruction request, the orchestration module destroys the container identified by the target container identifier (ie, the target container).

[0175] The container destruction request is used to request the destruction of a container.

[0176] The target container identifier is the identifier of the container that needs to be destroyed.

[0177] For example, the scheduling system may call the container destruction service shown in Table 8 below to destroy the target container.

[0178] Table 8

[0179]

[0180] The embodiment of the present application only uses Table 8 above as an example to exemplify the container destruction service, and Table 8 above does not limit the embodiment of the present application.

[0181] It should be noted that if an application is deployed in the target container, the orchestration module will also uninstall the application when destroying the target container. If no application is deployed in the target container, the orchestration module will directly destroy the target container.

[0182] In some cases, after destroying the target container, the orchestration module may delete the identifier of the target container and its corresponding application identifier in the first corresponding relationship to indicate that the target container currently does not exist in the monitoring system.

[0183] For ease of understanding, the following Figure 3 The process of installing, interacting with, and destroying the above-mentioned application is illustrated by way of example.

[0184] Figure 3 This is a flowchart of an application installation, interaction and destruction process provided by an embodiment of the present application, see Figure 3 , the process includes steps 301 to 311.

[0185] Step 301: The monitoring system installs the second application, and then executes step 302.

[0186] The second application is an application that needs to be installed.

[0187] If the monitoring system has installed a container corresponding to the second application, the monitoring system deploys the second application in the container according to the application installation file of the second application.

[0188] If the monitoring system has not installed the container corresponding to the second application, the monitoring system first installs the container according to the container installation file of the second application, and then deploys the second application in the container according to the application installation file of the second application.

[0189] Step 302: The monitoring system creates a container instance corresponding to the second application, and then executes step 303.

[0190] Step 303: The monitoring system updates the configuration file of the second application, and then executes step 304.

[0191] Step 304 : The monitoring system starts the second application program, and then executes step 305 .

[0192] Step 305: The second application calls the relevant service for interaction, and then executes step 306.

[0193] The second application can call one or more services including data publishing service, data subscription service, command publishing service, command subscription service, SQL update service, SQL query service, etc. to interact with other modules (such as substation equipment, dispatching system, monitoring system, etc.).

[0194] Step 306: The monitoring system determines whether the configuration file of the second application needs to be updated.

[0195] If it is determined that the configuration file of the second application needs to be updated, step 307 is executed; if it is determined that the configuration file of the second application does not need to be updated, step 309 is executed.

[0196] Step 307 : The monitoring system obtains the target configuration file, and then executes step 308 .

[0197] The target configuration file is a configuration file that needs to be updated in the second application.

[0198] Step 308 : The monitoring system updates the configuration file of the second application to the target configuration file, and then executes step 305 .

[0199] Step 309: The monitoring system determines whether the container corresponding to the second application needs to be destroyed.

[0200] If it is determined that the container corresponding to the second application needs to be destroyed, step 310 is executed; if it is determined that the container corresponding to the second application does not need to be destroyed, step 305 is continued to be executed.

[0201] Step 310: The monitoring system stops the running of the second application program, and then executes step 311.

[0202] Step 311: The monitoring system destroys the container corresponding to the second application.

[0203] For ease of understanding, the following Figure 4 The remote operation and maintenance orchestration method of the above-mentioned substation monitoring system application is exemplified.

[0204] Figure 4 This is a flowchart of a remote operation and maintenance orchestration method for a substation monitoring system application provided by an embodiment of the present application, see Figure 4 The method includes steps 401 to 409.

[0205] Step 401: The monitoring system receives the imported SCD file, and then executes step 402.

[0206] Step 402: The monitoring system parses the SCD file to obtain corresponding resources, and then executes step 403.

[0207] Step 403: The scheduling system obtains resource information and a service list, and then executes step 404.

[0208] The resource information is information about resources in the monitoring system. The service list is a list of services in the monitoring system.

[0209] Step 404: The scheduling system generates a target configuration file according to the received editing instruction, and then executes step 405.

[0210] The target configuration file is the configuration file that needs to be updated in the application.

[0211] The scheduling system can select a target task template according to the received selection instructions for the target template option, edit the target task template according to the received editing instructions for the execution cycle configuration items, service configuration items, resource import configuration items and resource export configuration items, and generate a target configuration file according to the received application instructions.

[0212] Step 405: The scheduling system sends the target configuration file to the monitoring system, and then executes step 406.

[0213] Step 406 : The monitoring system detects the target configuration file, and then executes step 407 .

[0214] Step 407: The monitoring system executes an operation of managing the first application.

[0215] The first application is the application that needs to update the configuration file, and is also the application corresponding to the target configuration file.

[0216] The monitoring system may start the first application so that the first application may read the target configuration file to execute the target task indicated by the target configuration file.

[0217] Step 408 : The first application executes the target task, and then executes step 409 .

[0218] Step 409: The first application returns the execution result of the target task to the scheduling system.

[0219] In an embodiment of the present application, the dispatching system displays a configuration interface, which includes multiple task template options. Afterwards, in response to the received selection instruction for the target template option, the dispatching system displays an editing interface, and in response to the received editing instruction for the service configuration item and / or resource configuration item in the editing interface, edits the services and / or resources required for the target task corresponding to the target template option, and then generates a target configuration file in response to the application instruction received in the editing interface. Afterwards, the dispatching system sends the target configuration file to the monitoring system. After receiving the target configuration file, the orchestration module in the monitoring system updates the configuration file of the first application according to the target configuration file. The first application executes the target task through the services and / or resources in the monitoring system according to the configuration file of the first application. In this way, the application in the monitoring system can make full use of the resources and services in the monitoring system when executing the task. In addition, the dispatching system includes multiple task templates, and tasks can be flexibly configured based on the multiple task templates to achieve the diversity of task configuration, so as to meet the operation and maintenance requirements of the substation.

[0220] Figure 5 Schematic diagram of the structure of a computer device provided in an embodiment of the present application. Figure 5 As shown, the computer device 5 includes: a processor 50, a memory 51, and a computer program 52 stored in the memory 51 and executable on the processor 50. When the processor 50 executes the computer program 52, the operations performed by the dispatching system or the monitoring system in the remote operation and maintenance orchestration method of the substation monitoring system application in the above-mentioned embodiment are implemented.

[0221] The computer device 5 may be a general-purpose computer device or a dedicated computer device. In a specific implementation, the computer device 5 may be a desktop computer, a portable computer, a network server, a PDA, a mobile phone, a tablet computer, a wireless terminal device, a communication device or an embedded device. The embodiment of the present application does not limit the type of the computer device 5. Those skilled in the art will understand that Figure 5It is only an example of the computer device 5 and does not constitute a limitation on the computer device 5. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components, such as input and output devices, network access devices, etc.

[0222] The processor 50 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0223] In some embodiments, the memory 51 may be an internal storage unit of the computer device 5, such as a hard disk or memory of the computer device 5. In other embodiments, the memory 51 may also be an external storage device of the computer device 5, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the computer device 5. Further, the memory 51 may also include both an internal storage unit of the computer device 5 and an external storage device. The memory 51 is used to store an operating system, an application program, a boot loader, data, and other programs. The memory 51 may also be used to temporarily store data that has been output or is to be output.

[0224] An embodiment of the present application also provides a computer device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, and when the processor executes the computer program, the steps in any of the above-mentioned method embodiments are implemented.

[0225] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0226] An embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the steps in the above-mentioned method embodiments.

[0227] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above method embodiments, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above method embodiments can be implemented. Among them, the computer program includes computer program code, which can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the camera / terminal device, recording medium, computer memory, ROM (Read-Only Memory), RAM (Random Access Memory), CD-ROM (Compact Disc Read-Only Memory), magnetic tape, floppy disk and optical data storage device. The computer-readable storage medium mentioned in the present application can be a non-volatile storage medium, in other words, it can be a non-transient storage medium.

[0228] It should be understood that all or part of the steps to implement the above embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The computer instructions can be stored in the above-mentioned computer readable storage medium.

[0229] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0230] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0231] In the embodiments provided in the present application, it should be understood that the disclosed devices / computer equipment and methods can be implemented in other ways. For example, the device / computer equipment embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0232] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0233] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with the relevant regulations and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0234] The embodiments described above 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, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such 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 remote operation and maintenance orchestration method for a substation monitoring system application, characterized in that: The method is applied to an operation and maintenance system, the operation and maintenance system includes a monitoring system and a scheduling system, the monitoring system includes an orchestration module and multiple application programs, the multiple application programs correspond to multiple tasks one by one, and the method includes: The scheduling system displays a configuration interface, the configuration interface includes a plurality of task template options, and the plurality of task template options correspond one to one with the plurality of tasks; in response to a received selection instruction for a target template option, an editing interface is displayed, the editing interface includes a service configuration item and a resource configuration item, and the target template option is any one of the plurality of task template options; in response to a received editing instruction for the service configuration item and / or the resource configuration item, the service and / or resource required for the target task corresponding to the target template option is edited; in response to an application instruction received on the editing interface, a target configuration file is generated; and the target configuration file is sent to the monitoring system; After receiving the target configuration file, the orchestration module updates a configuration file of a first application according to the target configuration file, where the first application is an application corresponding to the target task among the multiple applications; The first application executes the target task through the services and / or resources in the monitoring system according to the configuration file of the first application.

2. The method according to claim 1, characterized in that The services in the monitoring system include one or more of real-time library services, message bus services, historical library services, and control bus services, and / or the resources in the monitoring system include one or more of telemetry, telesignaling, telepulse, remote control, set values, parameters, permissions, and security audits.

3. The method according to claim 1, characterized in that The resource configuration items include one or more of resource import configuration items and resource export configuration items.

4. The method according to claim 1, characterized in that The editing interface also includes one or more of execution cycle configuration items and device configuration items.

5. The method according to claim 1, characterized in that Each of the plurality of applications is deployed in a container.

6. The method according to claim 5, characterized in that The method further comprises: The scheduling system obtains an application installation file and a container installation file of a second application; if the container corresponding to the second application does not exist in the monitoring system, the application installation file and the container installation file are sent to the monitoring system; After receiving the application installation file and the container installation file, the orchestration module deploys the second application in the corresponding container according to the application installation file and the container installation file.

7. The method according to claim 5, characterized in that The method further comprises: The scheduling system sends a container destruction request to the monitoring system, where the container destruction request carries a target container identifier; After receiving the container destruction request, the orchestration module destroys the container identified by the target container identifier.

8. The method according to any one of claims 1 to 7, characterized in that: After the first application executes the target task through the services and / or resources in the monitoring system according to the configuration file of the first application, the method further includes: The first application sends the execution result of the target task to the scheduling system through the orchestration module.

9. The method according to any one of claims 1 to 7, characterized in that: The target task is used to obtain device data, and the method further includes: When the first application determines according to the device data that a device state is abnormal, it sends an alarm message to the target device.

10. An operation and maintenance system, the operation and maintenance system comprising a monitoring system and a scheduling system, the monitoring system comprising an orchestration module and a plurality of applications, the plurality of applications corresponding one-to-one to a plurality of tasks; The scheduling system is used to: display a configuration interface, the configuration interface includes a plurality of task template options, the plurality of task template options correspond one to one with the plurality of tasks; in response to a received selection instruction for a target template option, display an editing interface, the editing interface includes a service configuration item and a resource configuration item, the target template option is any one of the plurality of task template options; In response to the received editing instruction for the service configuration item and / or the resource configuration item, editing the service and / or resource required for the target task corresponding to the target template option; In response to the application instruction received in the editing interface, generating a target configuration file; and sending the target configuration file to the monitoring system; The orchestration module is used to: after receiving the target configuration file, update the configuration file of the first application according to the target configuration file, the first application being the application corresponding to the target task among the multiple applications; The first application is used to: execute the target task through the services and / or resources in the monitoring system according to the configuration file of the first application.

Images