Substation monitoring comprehensive application development method, system and equipment for service-oriented architecture, and storage medium

Abstract

The invention discloses a transformer substation monitoring comprehensive application development method, system and equipment of a service-oriented architecture, and a storage medium, and relates to the technical field of power electronics and power transformation control, and the method comprises the steps: packaging a function unit of transformer substation monitoring according to a function logic based on the service-oriented architecture, and obtaining a service with an independent interface; establishing a service management center, registering the packaged service between the substation monitoring and the external application, and generating service description information; service calling is executed according to the service description information, an external application initiates a request through a service management center, and a server side completes data interaction and instruction execution according to request content and records a service calling relation; and combining and configuring the registered services based on the service calling relationship. According to the method, modular packaging and multiplexing of transformer substation monitoring functions are achieved, service registration and calling are unified, cross-system data interaction and multi-service collaboration are supported, and system expansibility and integration efficiency are improved.

Description

Technical Field

[0001] This invention relates to the field of power electronics and substation control technology, specifically to a service-oriented architecture-based substation monitoring integrated application development method, system, equipment, and storage medium. Background Technology

[0002] With the continuous improvement of power grid automation, substation monitoring systems have gradually evolved from traditional centralized architectures to open, modular architectures. Existing substation monitoring systems typically employ communication protocols based on the IEC 61850 standard, achieving real-time monitoring and control through standardized data exchange between the master station and bay / process layer equipment. In recent years, with the advancement of smart grids and dispatch automation, substation monitoring systems increasingly require data fusion and interaction with various external applications such as energy management systems, distribution automation systems, and dispatch management systems. This places higher demands on the system's scalability, flexibility, and functional reusability.

[0003] However, existing substation monitoring integrated application development still generally relies on tightly coupled functional unit designs. The interfaces of monitoring systems from different manufacturers vary significantly, and the encapsulation granularity of functional modules is inconsistent, making it difficult to achieve cross-system reuse and rapid expansion during application layer development. At the same time, the service invocation mechanism lacks a unified registration and description standard, requiring external applications to rely on specific interface protocols when invoking monitoring functions, resulting in long development cycles, complex maintenance, and high coupling. Summary of the Invention

[0004] In view of the above-mentioned problems, the present invention is proposed.

[0005] Therefore, the technical problem solved by this invention is that existing substation monitoring integrated application development methods have problems such as high system architecture coupling, inconsistent functional unit encapsulation granularity, and lack of standardization of external application interfaces, resulting in low data interaction efficiency, poor service reusability, and complex development and maintenance between the monitoring system and external applications.

[0006] To address the aforementioned technical problems, this invention provides the following technical solution: a service-oriented architecture-based substation monitoring integrated application development method, comprising: encapsulating the functional units of substation monitoring according to functional logic based on a service-oriented architecture to obtain services with independent interfaces; establishing a service management center to register the encapsulated services between substation monitoring and external applications and generate service description information; executing service calls based on the service description information, with external applications initiating requests through the service management center, and the server completing data interaction and instruction execution based on the request content, and recording service call relationships; and combining and configuring the registered services based on the service call relationships.

[0007] As a preferred embodiment of the service-oriented architecture-based substation monitoring integrated application development method described in this invention, the encapsulation of substation monitoring functional units according to functional logic includes classifying and summarizing the data acquisition, monitoring, control, and access control functional units in substation monitoring, and encapsulating them according to the logical relationship of the functional units to obtain data services, event services, control services, and application services with independent interfaces.

[0008] As a preferred embodiment of the service-oriented architecture-based substation monitoring integrated application development method described in this invention, the establishment of the service management center includes: establishing a service management directory, uniformly storing the interface parameters, access paths, and dependency information of registered services, configuring service monitoring rules, recording the status, number of requests, and response time of service calls, setting access control rules, performing authentication when external applications access registered services, recording the request content and response information during the service call process, and identifying and archiving call anomalies.

[0009] As a preferred embodiment of the service-oriented architecture substation monitoring integrated application development method described in this invention, the step of registering and encapsulating the service between the substation monitoring and external applications and generating service description information includes: entering the encapsulated service into the service registration directory according to the service type; establishing registration entries based on the service interface, service name, and access method; verifying and confirming the registration entries through the service management center; and generating service description information containing service identifier, input and output parameters, communication protocol, and call path.

[0010] As a preferred embodiment of the substation monitoring integrated application development method based on service-oriented architecture described in this invention, the step of executing a service call based on service description information includes: an external application initiating a call request based on the service description information; a service management center matching the corresponding registration entry based on the request content and forwarding the request; and the server performing data interaction and instruction processing based on the input parameters in the service description information.

[0011] As a preferred embodiment of the substation monitoring integrated application development method based on service-oriented architecture described in this invention, the method of recording service call relationships includes: registering the call source address, request time, and service identifier of the external application during the service call process; recording the input parameters, output results, and call path of the call; generating a call chain list according to the order of service calls; statistically analyzing the number of repeated calls and response time for the same service; and writing the recorded call relationship information into the service management center.

[0012] As a preferred embodiment of the service-oriented architecture substation monitoring integrated application development method described in this invention, the step of combining and configuring registered services includes: grouping registered services with related dependencies according to the call relationships recorded by the service management center; matching the input and output parameters of the combined services according to the service type; and deduplicating services that are called repeatedly during the service combination process.

[0013] Another objective of this invention is to provide a service-oriented substation monitoring integrated application development system. This system can achieve modular encapsulation and service-oriented invocation of substation monitoring functions through a unified service-oriented scheme based on functional unit encapsulation, service registration description, and invocation configuration. This solves the problems of high coupling of monitoring functions, inconsistent interfaces, and complex invocation management in the prior art.

[0014] As a preferred embodiment of the service-oriented architecture-based substation monitoring integrated application development system of the present invention, it includes: a functional unit encapsulation module, a service registration and description generation module, a service call execution module, and a service combination configuration module; the functional unit encapsulation module is used to encapsulate the functional units of substation monitoring according to functional logic to form service units with independent interfaces; the service registration and description generation module is used to complete the registration of the encapsulated services between substation monitoring and external applications, and generate service description information based on the encapsulated content, including service identifier, access method, and input / output parameters; the service call execution module is used to execute service calls based on the service description information, with external applications initiating requests through the service management center, and the server completing data interaction and instruction execution according to the request content, and recording the interaction relationships during the call process; the service combination configuration module is used to combine and configure multiple registered services to form a unified call structure with associated logic, realizing the process-oriented connection between encapsulated services.

[0015] Another object of the present invention is to provide a service-oriented architecture substation monitoring integrated application development device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program as a step in implementing a service-oriented architecture substation monitoring integrated application development method.

[0016] Another object of the present invention is to provide a service-oriented architecture substation monitoring integrated application development storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the service-oriented architecture substation monitoring integrated application development method are implemented.

[0017] The beneficial effects of this invention are as follows: The service-oriented architecture substation monitoring integrated application development method provided by this invention encapsulates the functional units of substation monitoring according to functional logic, enabling each functional unit to form a service with an independent interface, reducing the coupling between modules, and realizing the modularization and reuse of functions; by establishing a service management center, the encapsulated services are registered between substation monitoring and external applications, and service description information is generated, which can realize unified registration and access definition of services and improve the standardization of system interface management; service calls are executed based on service description information, and external applications can realize cross-system data interaction and command execution through the service management center, ensuring the consistency of call processes between different systems; based on service call relationships, the registered services are combined and configured, which can realize flexible orchestration and collaborative operation between multiple services, improving the scalability and integration development efficiency of the substation monitoring system. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is an overall flowchart of a service-oriented architecture-based substation monitoring integrated application development method provided in Embodiment 1 of the present invention.

[0020] Figure 2 This is a diagram of an integrated substation monitoring application platform, which is a service-oriented architecture-based substation monitoring integrated application development method provided in Embodiment 1 of the present invention. Detailed Implementation

[0021] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of the present invention.

[0022] Example 1, referring to Figures 1-2 As an embodiment of the present invention, a method for developing a comprehensive substation monitoring application based on a service-oriented architecture is provided, comprising: S1: Based on service-oriented architecture, the functional units of substation monitoring are encapsulated according to functional logic to obtain services with independent interfaces.

[0023] Furthermore, the functional units of substation monitoring are encapsulated according to functional logic. This includes classifying and summarizing the data acquisition, monitoring, control, and access control functional units in substation monitoring, and encapsulating them according to the logical relationship between the functional units to obtain data services, event services, control services, and application services with independent interfaces.

[0024] It should be noted that the data acquisition, monitoring, control, and access control functional units in the substation monitoring system are categorized and summarized. Based on the logical relationships between these functional units, functional decomposition and reorganization are performed. Data extraction and interface definition are performed for the data acquisition unit; status identification and event marking are performed for the monitoring unit; command structure and parameter limitations are defined for the control unit; and user roles and access control are defined for the access control unit.

[0025] After classification, the aforementioned functional units are logically encapsulated according to service-oriented encapsulation requirements, forming encapsulated objects with independent calling interfaces. Each encapsulated object includes input parameters, output parameters, and data interaction conventions. Through this encapsulation process, data services, event services, control services, and application services are obtained respectively. Among them, data services correspond to the real-time data access interface of the acquisition unit, event services correspond to the event push interface of the monitoring unit, control services correspond to the operation instruction interface of the control unit, and application services correspond to the permission management and application access interface.

[0026] It should also be noted that the functional units of substation monitoring, such as data acquisition, monitoring, control, and access management, are encapsulated and categorized according to functional logic, forming data, event, control, and application services with independent access interfaces. Through the logical decomposition and reorganization of functional units, standardized encapsulation and unified interface management of multiple business functions within the monitoring system are achieved. This process maintains the independence of functional logic and the consistency of interfaces, enabling modular invocation and expansion of different types of monitoring services, providing structured support for flexible configuration, cross-domain invocation, and intelligent integration of substation monitoring functions.

[0027] S2: Establish Service Management Center 100 to register encapsulated services and generate service description information between substation monitoring and external applications.

[0028] Furthermore, establishing a service management center 100 includes: establishing a service management directory; uniformly storing the interface parameters, access paths, and dependency information of registered services; configuring service monitoring rules; recording the status, number of requests, and response time of service calls; setting access control rules; performing authentication when external applications access registered services; recording the request content and response information during the service call process; and identifying and archiving call exceptions.

[0029] It should be noted that Service Management Center 100 is established to uniformly register and centrally manage various encapsulated services within the service domains. Service Management Center 100 constructs a service registration directory, uniformly storing the interface parameters, access paths, and dependency information of each registered item, and indexing them according to the structured classification of the service domains. The service registration directory includes various types of encapsulated services such as data acquisition, operation control, platform application, and event alarm services. All encapsulated services are recorded in the directory as independent access interfaces.

[0030] Specifically, the Service Management Center 100 manages the service call process, recording call status, request count, and response time in real time. It also verifies access paths and configures identity verification logic according to access control rules, such as... Figure 2 As shown, when a cross-platform application calls the registration service, the requester is authenticated. Cross-platform application 101 includes smart alarm APP, power metering APP, network security monitoring APP, etc., while cross-platform development 102 includes application scenarios such as substation data retrieval, secondary system online monitoring, and remote maintenance access. All of these achieve business access by calling the encapsulated service through the registration directory.

[0031] Furthermore, during the invocation phase, the Service Management Center 100 synchronously records the request content and response information. When a service invocation anomaly is detected, the abnormal request is identified and archived, recording the anomaly type, occurrence time, and request source. By continuously recording service invocation relationships, an access log is formed, which is used to trace the interaction relationships between different service domains.

[0032] exist Figure 2 In the data acquisition service domain 103, the encapsulated data services correspond to monitoring communication, telemetry, and remote pulse access interfaces; in the operation control service domain 104, the encapsulated control services correspond to remote control, remote adjustment, and setpoint area switching interfaces; in the platform application service domain 105, the encapsulated application services correspond to permission definition and application access interfaces; and in the event alarm service domain 106, the encapsulated event services correspond to event push, event statistics, and event query interfaces. All encapsulated services are registered, invoked, and recorded through the service management center 100, forming a complete service-oriented monitoring application invocation system.

[0033] It should also be noted that by unifying data acquisition, operation control, platform application, and event alarm services into the service registration directory, a hierarchical domain structure calling system is formed, enabling cross-platform applications and cross-platform development to achieve unified access and invocation of encapsulated services through the registration directory.

[0034] Furthermore, registering and encapsulating services between substation monitoring and external applications and generating service description information includes: entering the encapsulated services into the service registration directory according to service type; establishing registration entries based on service interface, service name, and access method; verifying and confirming the registration entries through the service management center 100; and generating service description information containing service identifier, input and output parameters, communication protocol, and call path.

[0035] It should be noted that the encapsulated services provided for substation monitoring are categorized and organized according to their functional characteristics into data acquisition, operation control, platform application, and event alarm categories. After each type of service is encapsulated, the encapsulated services are entered into the service registration directory one by one through a service registration process, with the service category and invocation relationship identified during entry. During the registration process, registration entries are created for the service interface, service name, and access method.

[0036] Furthermore, after a registration entry is established, a service management process is executed, which verifies the legality of the interface and the call path through a verification step. Verification includes checking the service identifier, input / output parameter format, communication protocol type, and access path consistency. Upon successful verification, corresponding service description information is generated. This description information includes detailed information such as the service identifier, input / output parameters, communication protocol type, and call path. The generated service description information is then uniformly numbered and archived.

[0037] When external applications call the encapsulated service of substation monitoring, they can access it through the call path defined in the registry directory and complete the interaction of input and output parameters according to the interface conventions in the description information, thereby realizing a unified service call process between substation monitoring and external applications.

[0038] It should also be noted that a unified service registration and encapsulation mechanism is introduced between substation monitoring and external applications. By classifying and organizing the encapsulated services on the monitoring side according to their functional characteristics, establishing registration entries, and generating standardized service description information, the interfaces, communication protocols, and call paths of various services are uniformly defined and verified. Through the legality verification of registration entries and the archiving management of description information, the entire process from service encapsulation to invocation is made traceable and consistent, thereby ensuring the standardization and scalability of substation monitoring services during cross-system invocation.

[0039] S3: Execute service calls based on service description information. External applications initiate requests through the service management center 100. The server completes data interaction and instruction execution based on the request content and records the service call relationship.

[0040] Furthermore, the service call based on the service description information includes: the external application initiates a call request based on the service description information; the service management center 100 matches the corresponding registration entry based on the request content and forwards the request; and the server performs data interaction and instruction processing based on the input parameters in the service description information.

[0041] It should be noted that external applications initiate call requests based on the generated service description information. The request content includes the target service identifier, input parameters, and invocation method. Upon receiving the call request, the service management process matches the corresponding registration entry in the registry based on the request content and verifies whether the service requested is in a callable state. If a match is successful, the call request content is forwarded to the corresponding server. The server then performs data interaction and instruction processing based on the input parameters defined in the service description information. During execution, input parameters are passed in by the external application, and output data is processed by the server and returned to the caller. The data interaction process strictly follows the communication protocol and call path defined in the service description information to ensure consistency between the call behavior and the registration information.

[0042] It should also be noted that by introducing a matching and verification mechanism based on service description information during the service invocation phase, precise correspondence and consistent interaction between external applications and registered services are achieved. External applications initiate requests based on service description information. The service management process automatically matches the target service in the registration directory and verifies its callability status, ensuring the legality and validity of the invocation. After the invocation content is confirmed through matching, the server executes data interaction and instruction processing based on the input parameters defined in the description information. The output data is returned to the caller according to the defined path. This achieves verifiability of the invocation path and standardization of the data processing process between external applications and the server, thereby ensuring the integrity and consistency of the service invocation process.

[0043] Furthermore, recording service call relationships includes registering the external application's call source address, request time, and service identifier during the service call process; recording the call input parameters, output results, and call path; generating a call chain list according to the order of service calls; statistically analyzing the number of repeated calls to the same service and the response time; and writing the recorded call relationship information into the service management center 100.

[0044] It should be noted that during the service invocation phase, the source information of invocation requests initiated by external applications is recorded. The source address, request time, and service identifier are all registered synchronously when the invocation is triggered. The input parameters, output results, and invocation path in the invocation request are recorded sequentially to form a complete invocation data chain. During execution, a invocation chain is generated according to the time sequence of service invocations, and multiple invocations of the same service are numbered and categorized. When duplicate invocations are detected, the corresponding number of invocations and their impact time are calculated and statistical analysis is performed.

[0045] It should also be noted that by recording service call relationships, the entire process from request initiation to result return can be tracked during the service call execution phase, so that the source, timing and result of each call are recorded in a standardized manner, thereby providing basic data for the identification and management of subsequent call relationships.

[0046] S4: Based on service call relationships, combine and configure registered services.

[0047] Furthermore, the combination and configuration of registered services includes grouping registered services with related dependencies according to the call relationships recorded in the service management center 100, matching the input and output parameters of the combined services according to the service type, and deduplicating services that are called repeatedly during the service combination process.

[0048] It should be noted that, based on the recorded service call relationships, services with dependencies are identified, and the related registered services are divided into several groups according to the dependency chain. Each group of services corresponds to a specific business call process. After grouping, the input and output parameters of each group of services are matched and mapped according to the service type.

[0049] During the combined execution phase, services that are repeatedly called within each group are deduplicated to prevent the same service from being triggered repeatedly in multiple call chains. Deduplication methods include comparing the service identifier with the input parameters; if identical call targets are detected, only the result of the first call is retained for reference in subsequent call flows.

[0050] When the combined call is executed, the call request is triggered one by one according to the service dependency order. The parameters between the calls are automatically passed to the input of the next service according to the output result of the previous service, realizing the serial and parallel logic control of the combined service.

[0051] It should also be noted that by performing dependency grouping, parameter mapping, and deduplication of duplicate calls on registered services, a dynamic composite invocation mechanism for complex service relationships is formed. Service dependency chains are mapped to grouped logical structures, and orderly connections between different services are achieved by matching input and output parameters. Furthermore, duplicate call targets are identified and deduplicated during the composite execution phase to prevent redundant triggering and resource consumption.

[0052] Example 2, an embodiment of the present invention, provides a service-oriented architecture-based substation monitoring integrated application development system, including a functional unit encapsulation module, a service registration and description generation module, a service call execution module, and a service composition configuration module.

[0053] The functional unit encapsulation module is used to encapsulate the functional units of substation monitoring according to functional logic, forming service units with independent interfaces.

[0054] The service registration and description generation module is used to register encapsulated services between substation monitoring and external applications, and generate service description information based on the encapsulated content. The description information includes definitions such as service identifier, access method, and input / output parameters.

[0055] The service call execution module is used to execute service calls based on service description information. External applications initiate requests through the service management center 100. The server completes data interaction and instruction execution based on the request content and records the interaction relationships during the call process.

[0056] The service composition configuration module is used to combine and configure multiple registered services to form a unified calling structure with related logic, thereby realizing the process-oriented connection between encapsulated services.

[0057] This embodiment also provides a computer device, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements a service-oriented architecture substation monitoring integrated application development system as proposed in the above embodiment.

[0058] This embodiment also provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it implements a service-oriented architecture substation monitoring integrated application development system as proposed in the above embodiment.

[0059] If a function is implemented as 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 technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0060] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0061] More specific examples of computer-readable media (a non-exhaustive list) include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0062] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0063] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A service-oriented architecture-based development method for integrated substation monitoring applications, characterized in that, include: Based on a service-oriented architecture, the functional units of substation monitoring are encapsulated according to functional logic to obtain services with independent interfaces. Establish a service management center to register encapsulated services and generate service description information between substation monitoring and external applications; Service calls are executed based on service description information. External applications initiate requests through the service management center, and the server completes data interaction and instruction execution based on the request content, and records service call relationships. Based on service call relationships, registered services are combined and configured.

2. The substation monitoring integrated application development method based on service-oriented architecture as described in claim 1, characterized in that: The process of encapsulating the functional units of substation monitoring according to functional logic includes classifying and summarizing the data acquisition, monitoring, control, and access control functional units in substation monitoring, and encapsulating them according to the logical relationship of the functional units to obtain data services, event services, control services, and application services with independent interfaces.

3. The substation monitoring integrated application development method based on service-oriented architecture as described in claim 1 or 2, characterized in that: The establishment of the service management center includes: establishing a service management directory to uniformly store the interface parameters, access paths and dependency information of registered services; configuring service monitoring rules to record the status, number of requests and response time of service calls; setting access control rules to perform authentication when external applications access registered services; recording the request content and response information during the service call process; and identifying and archiving call exceptions.

4. The substation monitoring integrated application development method based on service-oriented architecture as described in claim 3, characterized in that: The process of registering and encapsulating services between substation monitoring and external applications and generating service description information includes: entering the encapsulated services into the service registration directory according to service type; establishing registration entries based on service interface, service name and access method; verifying and confirming the registration entries through the service management center; and generating service description information containing service identifier, input and output parameters, communication protocol and call path.

5. The substation monitoring integrated application development method based on service-oriented architecture as described in any one of claims 1, 2, and 4, characterized in that: The process of executing a service call based on service description information includes: an external application initiating a call request based on the service description information; the service management center matching the corresponding registration entry based on the request content and forwarding the request; and the server performing data interaction and instruction processing based on the input parameters in the service description information.

6. The substation monitoring integrated application development method based on service-oriented architecture as described in claim 5, characterized in that: The process of recording service call relationships includes registering the external application's call source address, request time, and service identifier during the service call process; recording the call input parameters, output results, and call path; generating a call chain list according to the order of service calls; statistically analyzing the number of repeated calls to the same service and the response time; and writing the recorded call relationship information into the service management center.

7. The substation monitoring integrated application development method based on service-oriented architecture as described in any one of claims 1, 2, 4, and 6, characterized in that: The process of combining and configuring registered services includes grouping registered services with related dependencies according to the call relationships recorded by the service management center, matching the input and output parameters of the combined services according to the service type, and deduplicating services that are called repeatedly during the service combination process.

8. A service-oriented substation monitoring integrated application development system, employing the service-oriented substation monitoring integrated application development method as described in any one of claims 1 to 7, characterized in that: It includes a functional unit encapsulation module, a service registration and description generation module, a service invocation execution module, and a service composition configuration module; The functional unit encapsulation module is used to encapsulate the functional units of substation monitoring according to functional logic, forming service units with independent interfaces. The service registration and description generation module is used to register the encapsulated service between substation monitoring and external applications, and generate service description information based on the encapsulated content. The description information includes definitions such as service identifier, access method and input / output parameters. The service call execution module is used to execute service calls based on service description information. External applications initiate requests through the service management center, and the server completes data interaction and instruction execution according to the request content, and records the interaction relationships during the call process. The service composition configuration module is used to combine and configure multiple registered services to form a unified calling structure with related logic, thereby realizing the process-oriented connection between encapsulated services.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the service-oriented architecture substation monitoring integrated application development method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the service-oriented architecture substation monitoring integrated application development method according to any one of claims 1 to 7.

Images