Method and device for generating scheduling monitoring signal processing knowledge base, equipment and medium

Abstract

The invention provides a scheduling monitoring signal processing knowledge base generation method and device, equipment and a medium, and relates to the technical field of power system scheduling. The method comprises the following steps: acquiring a constant value list corresponding to each protection device in the information protection system, and extracting a device model of each protection device based on the constant value list; establishing a corresponding sub-model for each device model; obtaining protection information of all protection devices corresponding to the device model from a protection information system, and adding the protection information to the sub-model; determining scheduling monitoring signal attribute information corresponding to the protection information based on the OCS, and adding the scheduling monitoring signal attribute information to the sub-model; according to the method, the scheduling monitoring signal processing knowledge base is obtained on the basis of the multiple sub-models, automatic association of protection information of different protection devices and scheduling monitoring signals in the OCS is achieved, the association relation between the protection information and the attribute information of the corresponding scheduling monitoring signals can be rapidly obtained on the basis of the knowledge base, and therefore the processing efficiency of the scheduling monitoring signals is improved.

Description

Technical Field

[0001] This application relates to the field of power system dispatching technology, and particularly to a method, apparatus, equipment, and medium for generating a dispatching and monitoring signal processing knowledge base. Background Technology

[0002] With the continuous expansion of the power grid and the deepening of integrated control, the signal monitoring pressure on the Operation Control System (OCS) is increasing daily. Against this backdrop, existing OCS systems have revealed numerous shortcomings, particularly in signal event-based correlation analysis and intelligent handling, for which no effective solutions have yet been proposed. Currently, when a power grid fault occurs and generates alarm signals, dispatchers must obtain fault information through various means such as telephone communication and system queries. This decentralized information collection method is not only cumbersome but also inefficient, failing to meet the demands for rapid response. Meanwhile, with the rapid development of smart grids, the functions of the power grid's protection information management system (i.e., the protection information management system) are constantly improving, and the number of connected protection devices has increased significantly, accumulating a wealth of key information such as protection actions and alarms. However, due to the lack of an effective data correlation mechanism between the protection information management system and the OCS, this protection information cannot be automatically mapped to the dispatch monitoring signals. This situation leaves the dispatching end in a passive state in handling dispatch monitoring signals, unable to fully utilize the information resources of the protection information management system to make timely and accurate decisions.

[0003] Currently, due to the large number of manufacturers, models, and versions of protection devices, the protection information (such as soft messages and event logs) of different devices varies greatly. In related technologies, manual matching is usually used to match protection information with dispatch and monitoring signals, but this has the problem of low efficiency in processing dispatch and monitoring signals.

[0004] Therefore, there is an urgent need for a scheme to generate a knowledge base for the processing of scheduling and monitoring signals based on the information protection system, so as to quickly improve the efficiency of processing scheduling and monitoring signals. Summary of the Invention

[0005] This application provides a method, apparatus, equipment, and medium for generating a knowledge base for dispatch monitoring signal processing, in order to improve the problem of low efficiency in dispatch monitoring signal processing when using manual matching to match protection information with dispatch monitoring signals in related technologies.

[0006] Firstly, this application provides a method for generating a knowledge base for dispatch monitoring signal processing, applied to a power grid dispatch command and control system (DCCS). The DCCS is communicatively connected to the power grid's OCS and information protection system. The method includes:

[0007] Obtain the setting sheets corresponding to each protection device in the insurance system;

[0008] Based on the setting sheets corresponding to each protection device, the device model corresponding to each protection device is extracted to obtain multiple device models;

[0009] For each of the multiple device models, a sub-model corresponding to the device model is established;

[0010] Obtain protection information for all protection devices corresponding to the device model from the protection information system, and add the protection information to the sub-model;

[0011] Based on the scheduling and monitoring signal classification system in OCS, the scheduling and monitoring signal attribute information corresponding to the protection information is determined, and the scheduling and monitoring signal attribute information is added to the sub-model.

[0012] A knowledge base for dispatch and monitoring signal processing is obtained based on multiple sub-models corresponding to multiple device models.

[0013] In one possible implementation, determining the scheduling and monitoring signal attribute information corresponding to the protection information and adding the scheduling and monitoring signal attribute information to the sub-model includes: filtering the protection information to obtain filtered protection information; determining the scheduling and monitoring signal attribute information corresponding to the filtered protection information and adding the scheduling and monitoring signal attribute information to the sub-model.

[0014] In one possible implementation, the protection information is filtered to obtain filtered protection information, including: responding to a selection instruction received from a user, determining the protection information to be retained based on the selection instruction; and removing the protection information that was not selected to be retained from the sub-model to obtain the filtered protection information.

[0015] In one possible implementation, the protection information includes status alarms and status action events. The protection information for all protection devices corresponding to the device model is obtained from the protection information system, and this protection information is added to the sub-model. This includes: identifying all protection devices in the protection information system that match the device model; for all protection devices matching the device model, parsing the configuration file corresponding to each protection device, and extracting status alarms and status action events from each configuration file; and adding the extracted status alarms and status action events to the sub-model.

[0016] In one possible implementation, the dispatch monitoring signal classification system includes protection action signals, reclosing action signals, device alarm signals, and communication anomaly signals. Based on the dispatch monitoring signal classification system in the OCS, the dispatch monitoring signal attribute information corresponding to the protection information is determined, including: extracting a preset dispatch monitoring signal classification system from the OCS signal configuration library; extracting semantic features corresponding to each piece of information in the protection information; matching the semantic features with the dispatch monitoring signal classification system to determine the signal classification corresponding to the information; and determining the dispatch monitoring signal attribute information corresponding to the information based on the signal classification.

[0017] In one possible implementation, the method for generating the dispatch monitoring signal processing knowledge base further includes: extracting the device models of all protection devices from the protection information system according to a set period; comparing the extracted device models with the device models in the dispatch monitoring signal processing knowledge base to determine whether there are any newly added device models; if there are newly added device models, performing the step of establishing a sub-model corresponding to the device model for the newly added device model, until the newly added device model, the protection information corresponding to the newly added device model, and the dispatch monitoring signal attribute information corresponding to the protection information are added to the dispatch monitoring signal processing knowledge base.

[0018] Secondly, this application provides a device for generating a knowledge base for dispatch monitoring signal processing, applied to the DCCS of a power grid. The DCCS is communicatively connected to the OCS and the information protection system, and the device includes:

[0019] The acquisition module is used to acquire the setting sheets corresponding to each protection device in the information protection system;

[0020] The extraction module is used to extract the device model corresponding to each protection device based on the setting sheet corresponding to each protection device, and obtain multiple device models.

[0021] The model building module is used to build a sub-model corresponding to each of the multiple device models.

[0022] The first processing module is used to obtain the protection information of all protection devices corresponding to the device model from the protection information system and add the protection information to the sub-model; and, based on the scheduling and monitoring signal classification system in OCS, to determine the scheduling and monitoring signal attribute information corresponding to the protection information and add the scheduling and monitoring signal attribute information to the sub-model.

[0023] The second processing module is used to obtain a knowledge base for handling scheduling and monitoring signals based on multiple sub-models corresponding to multiple device models.

[0024] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0025] Memory is used to store instructions executed by the computer;

[0026] A processor for executing computer-executable instructions stored in memory to implement the method described in any of the first aspects.

[0027] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed, are used to implement the method described in any of the first aspects.

[0028] Fifthly, this application provides a computer program product, including a computer program that, when executed, implements the method described in any of the first aspects.

[0029] The method, apparatus, equipment, and medium for generating a dispatch monitoring signal processing knowledge base provided in this application are applied to the DCCS of a power grid. The DCCS is communicatively connected to the OCS and the protection and information system in the power grid. The method includes: obtaining the setting sheets corresponding to each protection device in the protection and information system; extracting the device models corresponding to each protection device based on the setting sheets to obtain multiple device models; establishing a sub-model corresponding to each device model; obtaining the protection information of all protection devices corresponding to the device model from the protection and information system and adding the protection information to the sub-model; determining the dispatch monitoring signal attribute information corresponding to the protection information based on the dispatch monitoring signal classification system in the OCS and adding the dispatch monitoring signal attribute information to the sub-model; and obtaining the dispatch monitoring signal processing knowledge base based on the multiple sub-models corresponding to the multiple device models. In this process, by automatically extracting the device models of each protection device in the protection information system and establishing corresponding sub-models, the protection information corresponding to the device model and the dispatch monitoring signal attribute information corresponding to the protection information are further added to the sub-models. This achieves automated association between the protection information of protection devices from different manufacturers and of different models and the dispatch monitoring signals in the OCS, efficiently constructing a complete knowledge base for dispatch monitoring signal handling. Correspondingly, when the power grid experiences an anomaly and generates a corresponding dispatch monitoring signal, based on this knowledge base for dispatch monitoring signal handling, the association between the protection information and the corresponding dispatch monitoring signal attribute information can be quickly obtained without the need for manual matching. This significantly shortens the information matching time and thus significantly improves the efficiency of dispatch monitoring signal handling. At the same time, the automated association between the protection information and the dispatch monitoring signals in the OCS ensures the accuracy of the association results, significantly improving the accuracy, consistency, and reliability of dispatch monitoring signal handling. This is of positive significance for ensuring the safe, stable, and efficient operation of the power grid in complex and ever-changing operating environments, as well as improving the overall emergency response capability and intelligent management level of the power grid. Attached Figure Description

[0030] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0031] Figure 1 A flowchart illustrating a method for generating a knowledge base for handling scheduling and monitoring signals, provided as an exemplary embodiment of this application;

[0032] Figure 2 Another flowchart illustrating the method for generating a knowledge base for handling scheduling and monitoring signals provided as an exemplary embodiment of this application;

[0033] Figure 3 Another flowchart illustrating the method for generating a knowledge base for handling scheduling and monitoring signals provided as an exemplary embodiment of this application;

[0034] Figure 4 A schematic diagram of the structure of a device for generating a knowledge base for handling scheduling and monitoring signals provided in an exemplary embodiment of this application;

[0035] Figure 5 A schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application.

[0036] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0037] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0038] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, products, or apparatus.

[0039] 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, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0040] In related technologies, when manually matching protection information with dispatch monitoring signals, dispatchers need to switch between different systems and different file directories for queries, which is time-consuming, labor-intensive, and results in a failure to quickly obtain the correlation between protection information and the corresponding dispatch monitoring signal attribute information, leading to low efficiency in the processing of dispatch monitoring signals. Furthermore, due to the varying experience and skill levels of different dispatchers during manual matching, and the large amount of repetitive work involved, dispatchers are prone to fatigue and decreased attention, making them susceptible to errors and affecting the accuracy of dispatch monitoring signal processing. Additionally, manual matching relies on the subjective judgment of dispatchers, and the matching results may vary, making it difficult to guarantee the consistency and reliability of dispatch monitoring signal processing.

[0041] To address the aforementioned issues, this application provides a scheme for generating a knowledge base for dispatch monitoring signal handling. By establishing a communication interface between the DCCS and the protection information system, the system obtains the device models corresponding to each protection device from the protection information system and establishes sub-models corresponding to these device models. Furthermore, the protection information corresponding to each device model and the dispatch monitoring signal attribute information corresponding to that protection information are added to the sub-models. By automatically associating the dispersed protection information corresponding to different protection devices with the dispatch monitoring signal attribute information, a fully functional knowledge base for dispatch monitoring signal handling is efficiently constructed. This knowledge base provides a means for intelligent handling of dispatch monitoring signals, thereby significantly improving the efficiency of dispatch monitoring signal handling. Simultaneously, the automated association between protection information and dispatch monitoring signals in the OCS ensures the accuracy of the association results, significantly improving the accuracy, consistency, and reliability of dispatch monitoring signal handling. This is of positive significance for ensuring the safe, stable, and efficient operation of the power grid in complex and ever-changing operating environments, and for enhancing the overall emergency response capability and intelligent management level of the power grid.

[0042] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0043] Figure 1 This is a flowchart illustrating a method for generating a dispatch monitoring signal handling knowledge base, provided as an exemplary embodiment of this application. The method for generating a dispatch monitoring signal handling knowledge base provided in this embodiment is applied to the DCCS of a power grid, where the DCCS is communicatively connected to the OCS and the information protection system within the power grid. Figure 1 As shown, the method for generating this knowledge base for dispatch monitoring signal handling includes the following steps:

[0044] S101. Obtain the setting sheets corresponding to each protection device in the protection system.

[0045] For example, assuming the protection information system is located in production zone I and the DCCS is located in production zone II, due to the security isolation requirements between the different production zones, to enable the DCCS to obtain the protection device setting sheets within the protection information system, the communication interface between the DCCS and the protection information system needs to be established beforehand. Specifically, forward and reverse isolation devices are deployed in both zones to ensure security isolation; a suitable communication protocol is selected based on the system characteristics; an interface module is developed in the protection information system to receive DCCS requests, query and encapsulate corresponding data such as setting sheet data, and then send it through the forward isolation device; simultaneously, a corresponding module is developed in the DCCS to generate and send data acquisition requests, as well as receive and parse received data, etc.

[0046] Accordingly, DCCS sends a data request to the protection information system via the communication interface to obtain the setting sheets corresponding to each protection device; correspondingly, the protection information system receives the data request, queries the setting sheets corresponding to each protection device, and sends the setting sheets corresponding to each protection device to DCCS via the communication interface; correspondingly, DCCS obtains the setting sheets corresponding to each protection device in the protection information system.

[0047] In the field of power system protection, a setting sheet is a standardized configuration file that records the operating parameters of a protection device. It is a set of instructions that clarifies the action logic and parameters of the protection device, and is equivalent to the "operation guidelines" of the protection device, used to ensure that it operates correctly in the event of a power grid fault.

[0048] S102. Based on the setting sheets corresponding to each protection device, extract the device model corresponding to each protection device to obtain multiple device models.

[0049] For example, for each setting sheet, the "device model" field information is accurately located and extracted. For instance, the "RCS-931AM" model is extracted from the setting sheet of the 220kV line protection device, and the "PST-1200" model is extracted from the setting sheet of the main transformer protection device. After systematic sorting and summarizing, the device model corresponding to each protection device is obtained, thus obtaining multiple device models.

[0050] S103. For each of the multiple device models, establish a sub-model corresponding to the device model.

[0051] Accordingly, since different manufacturers and different protection types of devices have different models, their protection information is different, and the corresponding scheduling and monitoring signals are different. Therefore, a sub-model is established with each device model as the keyword. Different protection device models correspond to multiple different sub-models. For example, device model CSC103A and device model PCS931N correspond to two different sub-models.

[0052] S104. Obtain the protection information of all protection devices corresponding to the device model from the protection information system, and add the protection information to the sub-model.

[0053] The protection information comes from the soft message information within the protection device. For example, protection information for all protection devices corresponding to device model CSC103A is obtained from the protection information system, and this information is added to a sub-model with device model CSC103A as the key; similarly, protection information for all protection devices corresponding to device model PCS931N is obtained from the protection information system, and this information is added to a sub-model with device model PCS931N as the key.

[0054] S105. Based on the scheduling and monitoring signal classification system in OCS, determine the scheduling and monitoring signal attribute information corresponding to the protection information, and add the scheduling and monitoring signal attribute information to the sub-model.

[0055] Among them, the dispatch monitoring signal attribute information refers to the attribute information of the monitoring signals that dispatchers can see in the OCS. The attribute information refers to the attribute name of the component, which can be event information or control behavior (such as protection actions and protection alarms).

[0056] In some embodiments, the dispatch monitoring signal classification system includes protection action signals, reclosing action signals, device alarm signals, and communication anomaly signals. Based on the dispatch monitoring signal classification system in the OCS, the dispatch monitoring signal attribute information corresponding to the protection information is determined, including: extracting a preset dispatch monitoring signal classification system from the OCS signal configuration library; extracting semantic features corresponding to each piece of information in the protection information; matching the semantic features with the dispatch monitoring signal classification system to determine the signal classification corresponding to the information; and determining the dispatch monitoring signal attribute information corresponding to the information based on the signal classification.

[0057] The signals are categorized into several types: protection action signals (including line protection actions and transformer protection actions), reclosing action signals (including successful line reclosing and unsuccessful reclosing), device alarm signals (including protection device power failure alarms and device communication interruption alarms), and communication anomaly signals (including communication interruption between the station and the master station and data transmission anomalies). For example, the DCCS extracts a pre-defined scheduling and monitoring signal classification system from the OCS signal configuration library via a communication interface and saves it as a local file. Correspondingly, natural language processing is performed on each piece of protection information to extract multi-dimensional semantic features, such as action type features, equipment type features, and anomaly type features. Action type features are used to identify action verbs in the information, equipment type features are used to identify equipment objects in the information, and anomaly type features are used to identify anomaly descriptions in the information. Further, based on a pre-trained semantic matching model, the semantic features are matched with the signal classification system to determine the signal classification to which each piece of protection information belongs. According to the matching results, each piece of protection information is labeled with corresponding scheduling and monitoring signal attribute information, such as signal classification identifier, standard signal name, signal priority, or associated handling strategy identifier. The semantic matching model is an attention-based neural network model trained using historical preservation information and labeled signal classification data.

[0058] For example, the sub-model includes a device model field, a protection information field, and a scheduling and monitoring signal attribute information field. Correspondingly, the device model is stored in the device model field, the protection information is stored in the protection information field, and the scheduling and monitoring signal attribute information is stored in the scheduling and monitoring signal attribute information field. For example, Table 1 is an example of a sub-model with device model CSC103A as the keyword provided by an exemplary embodiment of this application.

[0059] Table 1

[0060]

[0061] As shown in Table 1, protection information actions such as phase differential operation, grounding distance stage I operation, and distance stage II acceleration operation will trigger protection operation signals; protection information actions such as single-trip start reclosing and three-trip start reclosing will trigger reclosing operation; protection information actions such as equipment parameter errors, read-only memory (ROM) and verification errors, open-circuit breakdown, and flash memory (FLASH) self-test abnormalities will trigger device alarm I; protection information actions such as voltage transformer (PT) open circuit alarm, current transformer (CT) open circuit alarm, long-term differential current, and channel-1 communication interruption will trigger device alarm II, etc.

[0062] It should be noted that in some embodiments, dispatchers can also, based on the dispatch monitoring signal classification system in OCS, make manual judgments and, with the logic that protection information should be able to trigger the corresponding dispatch monitoring signal, input the dispatch monitoring signal attribute information corresponding to each protection information in the dispatch monitoring signal attribute information field of the sub-model.

[0063] S106. Based on multiple sub-models corresponding to multiple device models, a knowledge base for dispatching and monitoring signal processing is obtained.

[0064] For example, based on a pre-built template for a knowledge base for handling dispatch and monitoring signals, information from multiple sub-models is integrated to obtain the knowledge base for handling dispatch and monitoring signals. The template for the knowledge base includes sub-model serial numbers, sub-model names, protection information, and dispatch and monitoring signal attribute information. For example, Table 2 shows an example of a knowledge base for handling dispatch and monitoring signals provided in an exemplary embodiment of this application.

[0065] Table 2

[0066]

[0067] It should be noted that the presentation format of the dispatch monitoring signal processing knowledge base shown in Table 2 is only an example. In actual applications, the presentation format of the dispatch monitoring signal processing knowledge base can also be a database, data warehouse, or knowledge graph, etc. There is no limitation on the presentation format of the dispatch monitoring signal processing knowledge base here.

[0068] Optionally, before integrating the information from multiple sub-models, preprocessing operations are also performed on the information from the multiple sub-models. Preprocessing operations include, but are not limited to, data cleaning and format conversion. Among them, data cleaning refers to removing duplicate and invalid protection information entries; format conversion refers to converting heterogeneous data from different vendors into a unified encoding format.

[0069] The method for generating a dispatching monitoring signal handling knowledge base provided by the embodiments of this application automatically extracts the device models of each protection device in the protection information system and establishes corresponding sub-models. Further, the protection information corresponding to the device model and the dispatching monitoring signal attribute information corresponding to the protection information are added to the sub-models, realizing the automatic association of the protection information of protection devices from different manufacturers and different models with the dispatching monitoring signals in the OCS, and efficiently constructing a functionally complete dispatching monitoring signal handling knowledge base. Correspondingly, when an abnormality occurs in the power grid and corresponding dispatching monitoring signals are generated, based on this dispatching monitoring signal handling knowledge base, the association relationship between the protection information and the corresponding dispatching monitoring signal attribute information can be quickly obtained, without the need to match the protection information with the dispatching monitoring signals in a manual matching manner, significantly shortening the information matching time, thus significantly improving the handling efficiency of the dispatching monitoring signals. At the same time, the automatic association between the protection information and the dispatching monitoring signals in the OCS ensures the accuracy of the association results, significantly improving the accuracy of the dispatching monitoring signal handling, as well as the consistency and reliability of the dispatching monitoring signal handling, which is of positive significance for ensuring the safe, stable and efficient operation of the power grid in a complex and changeable operating environment, as well as for improving the overall emergency response ability and intelligent management level of the power grid.

[0070] In some embodiments, the protection information includes status quantity alarms and status quantity action events. Obtaining the protection information of all protection devices corresponding to the device model from the protection information system and adding the protection information to the sub-model includes: identifying all protection devices in the protection information system that match the device model; for all protection devices that match the device model, parsing the configuration files corresponding to each protection device respectively, and extracting the status quantity alarms and status quantity action events in each configuration file; adding the extracted status quantity alarms and status quantity action events to the sub-model.

[0071] Exemplarily, when the protection device is configured, the system will create a corresponding folder according to the substation name. Each folder contains XML files of the protection device name and the protection device model, and each XML file contains protection information. Correspondingly, all corresponding XML files are filtered according to the device model keyword, and the protection information contained in the XML files is parsed, for example, parsing the relevant description content of grpName = "status quantity alarm" and grpName = "status quantity action event", so as to accurately extract the corresponding status quantity alarms and status quantity action events.

[0072] Exemplarily, the corresponding description of grpName = "status quantity alarm" is, for example:

[0073] “<DIs grp="10"grpName="{cpu1} status quantity alarm"cpu="1">

[0074] <DI addr="2" description="Analog acquisition error" type="3" information sequence number="1" function type="170" / >

[0075] <DI addr="3" description="Spare" type="3" information sequence number="2" function type="170" / >

[0076] <DI addr="4" description="Device parameter error" type="3" information sequence number="3" function type="170" / >

[0077] <DI addr="5" description="ROM checksum error" type="3" information sequence number="4" function type="170" / >

[0078] <DI addr="6" description="Setting value error" type="3" information sequence number="5" function type="170" / >

[0079] <DI addr="7" description="Setting value area pointer error" type="3" information sequence number="6" function type="170" / >

[0080] <DI addr="8" description="Output not responding" type="3" information sequence number="7" function type="170" / >

[0081] <DI addr="9" description="Output breakdown" type="3" information sequence number="8" function type="170" / > addr="10" description="SRAM self - test exception" type="3" information sequence number="9" function type="170" / >

[0082] <DI addr="11" description="FLASH self - test exception" type="3" information sequence number="10" function type="170" / >

[0083] <DI addr="12" description="Spare" type="3" information sequence number="11" function type="170" / >

[0084] <DI addr="13" description="Channel maintenance differential protection withdrawn" type="3" information sequence number="12" function type="170" / >

[0085] <DI addr="14" description="Current imbalance alarm" type="3" information sequence number="13" function type="170" / >

[0086] <DI addr="15" description="Soft压板 error" type="3" information sequence number="14" function type="170" / > It should be noted that there may be an error in the original text where "软压板错” is translated as "Soft压板 error". It might be a misspelling in the original Chinese. If it is "软压板错误", it should be translated as "Soft pressure plate error".

[0087] <DI addr="16" description="System configuration error" type="3" information sequence number="15" function type="170" / >

[0088] <DI addr="17" description="Spare" type="3" information sequence number="16" function type="170" / >

[0089] <DI addr="18" description="Spare" type="3" information sequence number="17" function type="170" / >

[0090] <DI addr="19" description="Spare" type="3" information sequence number="18" function type="170" / >

[0091] <DI addr="20" description="Spare" type="3" information sequence number="19" function type="170" / >

[0092] <DI addr="21" description="Input configuration error" type="3" information sequence number="20" function type="170" / >

[0093] <DI addr="22" description="Output configuration error" type="3" information sequence number="21" function type="170" / >

[0094] <DI addr="23" description="Input communication interruption" type="3" information sequence number="22" function type="170" / >

[0095] <DI addr="24" description="Output communication interruption" type="3" information sequence number="23" function type="170" / >

[0096] <DI addr="25" description="Transmission status not restored" type="3" information sequence number="24" function type="170" / >

[0097] ……

[0098] Correspondingly, the relevant description of grpName = "Status quantity action event" is, for example:

[0099] “<DIs grp="50" grpName="{cpu1} status quantity action event" cpu="1">

[0100] <DI addr="2" description="Fault location" type="1" information sequence number="1" function type="190" / >

[0101] <DI addr="3" description="Protection startup" type="1" information sequence number="2" function type="190" / >

[0102] <DI addr="4" description="Impedance element startup" type="1" information sequence number="3" function type="190" / >

[0103] <DI addr="5" description="Zero-sequence auxiliary startup" type="1" information sequence number="4" function type="190" / >

[0104] <DI addr="6" description="Static stability loss startup" type="1" information sequence number="5" function type="190" / >

[0105] <DI addr="7" description="Spare" type="1" information sequence number="6" function type="190" / >

[0106] <DI addr="8" description="Spare" type="1" information sequence number="7" function type="190" / >

[0107] <DI addr="9" description="Spare" type="1" information sequence number="8" function type="190" / >

[0108] <DI addr="10" description="Distance II-section acceleration operation" type="1" information sequence number="9" function type="190" / >

[0109] <DI addr="11" description="Distance III-section acceleration operation" type="1" information sequence number="10" function type="190" / >

[0110] <DI addr="12" description="Distance closing acceleration operation" type="1" information sequence number="11" function type="190" / >

[0111] <DI addr="13" description="Distance proximity acceleration operation" type="1" information sequence number="12" function type="190" / >

[0112] <DI addr="14" description="Protection three-trip failure" type="1" information sequence number="13" function type="190" / >

[0113] <DI addr="15" description="Protection single-trip failure" type="1" information sequence number="14" function type="190" / >

[0114] <DI addr="16" description="Distance | Segment development action" type="1" information sequence number="15" function type="190" / >

[0115] <DI addr="17" description="Distance II segment development action" type="1" information sequence number="16" function type="190" / >

[0116] <DI addr="18" description="Distance measurement impedance" type="1" information sequence number="17" function type="190" / >

[0117] <DI.addr="19" description="Spare" type="1" information sequence number="18" function type="190" / >

[0118] <DI addr="20" description="Spare" type="1" information sequence number="19" function type="190" / >

[0119] <DI addr="21" description="Zero-sequence definite-time operation" type="1" information sequence number="20" function type="190" / >

[0120] <DI addr="22" description="Spare" type="1" information sequence number="21" function type="190" / >

[0121] <DI addr="23" description="Spare" type="1" information sequence number="22" function type="190" / >SDI

[0122] <DI addr="24" description="Spare" type="1" information sequence number="23" function type="190" / >

[0123] <DI addr="25" description="Spare" type="1" information sequence number="24" function type="190" / >

[0124] <DI addr="26" description="Zero-sequence definite-time acceleration operation" type="1" information sequence number="25" function type="190" / >

[0125] <DI addr="27" description="Spare" type="1" information sequence number="26" function type="190" / >

[0126] <DI addr="28" description="Zero-sequence manual closing acceleration action" type="1" information sequence number="27" function type="190" / >

[0127] ……”.

[0128] For example, by parsing the configuration files of all protection devices corresponding to the device model, the status alarms and status action events in each configuration file are extracted to obtain the protection information of all protection devices corresponding to that device model. For example, the protection information corresponding to device model CSC103A includes phase differential operation, ground distance I stage operation, distance II stage acceleration operation, single-pump start reclosing, three-pump start reclosing, equipment parameter error, ROM and check error, open-circuit breakdown, FLASH self-test abnormality, PT disconnection alarm, CT disconnection alarm, long-term differential current, and channel one communication interruption, etc. Further, the extracted protection information is added to the protection information field in the sub-model.

[0129] In this embodiment, by automatically identifying and parsing the configuration files of specific protection devices in the protection information system, the status alarm and action event information can be accurately extracted, realizing the standardized collection and structured storage of protection information. This effectively solves the problems of low efficiency, information omission and inconsistent formats in traditional manual collection methods, and provides a high-quality data foundation for the automated association between protection information and scheduling and monitoring signals in OCS. It also significantly improves the automation level and reliability of the knowledge base construction for scheduling and monitoring signal processing.

[0130] In some embodiments, determining the scheduling and monitoring signal attribute information corresponding to the protection information and adding the scheduling and monitoring signal attribute information to the sub-model includes: filtering the protection information to obtain filtered protection information; determining the scheduling and monitoring signal attribute information corresponding to the filtered protection information and adding the scheduling and monitoring signal attribute information to the sub-model.

[0131] For example, for the protection device of model CSC103A, assuming that its status action events such as "impedance element start", "zero sequence auxiliary start" and "compensation overvoltage satisfied" are soft message information that dispatchers do not care about or need, such information is deleted to obtain the protection information after screening. Further, the dispatch monitoring signal attribute information corresponding to the protection information after screening is determined and the dispatch monitoring signal attribute information is added to the sub-model.

[0132] In some embodiments, the protection information is filtered to obtain filtered protection information, including: responding to a selection instruction received from a user, determining the protection information to be retained based on the selection instruction; and removing the protection information that was not selected to be retained from the sub-model to obtain the filtered protection information.

[0133] For example, the DCCS provides an operable page for filtering protection information. Taking the CSC103A device as an example, the protection information list on the operable page displays "Impedance Element Start," "Zero-Sequence Auxiliary Start," "Compensation Overvoltage Satisfaction," "Phase Differential Operation," "Single-Pop Start Reclosing," "ROM and Checksum Error," and "PT Disconnection Alarm," etc. Dispatchers input selection commands by checking the checkboxes before each protection information in the list according to actual work needs. If the dispatcher believes that a certain protection information needs to be retained, they check the corresponding checkbox; otherwise, they leave it unchecked. For example, if the dispatcher checks the checkboxes corresponding to "Phase Differential Operation," "Single-Pop Start Reclosing," "ROM and Checksum Error," and "PT Disconnection Alarm," it indicates that these are protection information that needs to be retained; while the checkboxes corresponding to "Impedance Element Start," "Zero-Sequence Auxiliary Start," and "Compensation Overvoltage Satisfaction" are not checked. Correspondingly, the system monitors the dispatcher's selection operations in real time. Once the system detects that the dispatcher has completed the selection and clicked the "Confirm Filter" button, it immediately responds by receiving the selection instruction input by the dispatcher, parses the selection instruction, and determines which protection information is selected and retained, and which is not selected. Based on the parsed selection instruction, a list of protection information that needs to be retained is generated. This list records in detail the name of the selected protection information, the model of the device to which it belongs, and other key information. Taking the CSC103A device as an example, the list will clearly list "phase differential action", "single-pump start reclosing", "ROM and check error" and "PT disconnection alarm" as protection information that needs to be retained. Based on the protection information list, the system iterates and compares the protection information in the sub-model. For protection information that is not in the list, that is, protection information that has not been selected and retained, it is removed from the sub-model. For example, the protection information that was not selected, such as "impedance element start", "zero sequence auxiliary start" and "compensation overvoltage satisfied", is deleted from the sub-model corresponding to the CSC103A device.

[0134] In this embodiment, by filtering the protection information, irrelevant or redundant information can be removed, focusing on key protection data and ensuring the information quality of the protection information. By determining the scheduling and monitoring signal attribute information corresponding to the filtered protection information and adding it to the sub-model, the sub-model can more accurately associate the protection information with the scheduling and monitoring signal, which helps to improve the efficiency of the scheduling and monitoring system in identifying and processing fault signals.

[0135] In some embodiments, the method for generating the dispatch monitoring signal processing knowledge base further includes: extracting the device models of all protection devices from the protection information system according to a set period; comparing the extracted device models with the device models in the dispatch monitoring signal processing knowledge base to determine whether there are any newly added device models; if there are newly added device models, performing the step of establishing a sub-model corresponding to the device model for the newly added device model, until the newly added device model, the protection information corresponding to the newly added device model, and the dispatch monitoring signal attribute information corresponding to the protection information are added to the dispatch monitoring signal processing knowledge base.

[0136] For example, Figure 2 Another flowchart illustrating the method for generating a knowledge base for handling scheduling and monitoring signals, provided as an exemplary embodiment of this application. For example... Figure 2 As shown, the method for generating this knowledge base for dispatch monitoring signal handling includes the following steps:

[0137] S201. Obtain the setting sheets corresponding to each protection device in the protection system according to the set cycle.

[0138] For example, according to a set time period, such as every 2 hours, the setting sheets corresponding to each protection device in the protection system are obtained.

[0139] S202. Based on the setting sheets corresponding to each protection device, extract the device model corresponding to each protection device to obtain multiple device models.

[0140] S203. Compare the extracted device model with the device model in the dispatch and monitoring signal processing knowledge base to determine whether there are any newly added device models.

[0141] The device model to be extracted is compared with the device models in the dispatch and monitoring signal processing knowledge base to determine whether there is a newly added device model. This newly added device model can be one or more.

[0142] If so, execute S204;

[0143] If not, proceed with S201.

[0144] S204. For the newly added device model, establish a sub-model corresponding to the newly added device model.

[0145] That is, a sub-model is established using the model number of the newly added device as the keyword, and different protection device models correspond to multiple different sub-models.

[0146] S205. Obtain the protection information of all protection devices corresponding to the newly added device model from the protection information system, and add the protection information to the corresponding sub-model.

[0147] S206. Based on the scheduling and monitoring signal classification system in OCS, determine the scheduling and monitoring signal attribute information corresponding to the protection information, and add the scheduling and monitoring signal attribute information to the sub-model.

[0148] S207. Update the knowledge base for handling dispatch and monitoring signals based on the sub-model corresponding to the newly added device model.

[0149] The relevant information of the sub-model corresponding to the upcoming new device model will be added to the dispatch monitoring signal processing knowledge base to obtain the updated dispatch monitoring signal processing knowledge base.

[0150] In this embodiment, by extracting the protection device model from the power protection information system according to a set cycle and comparing it with the dispatch monitoring signal processing knowledge base, newly added device models can be identified in a timely manner, and subsequent sub-model establishment and information addition processes can be automatically triggered. This ensures that the dispatch monitoring signal processing knowledge base can dynamically and in real time reflect the relevant status of protection devices in the power system, reducing the loss of knowledge base information due to the omission of newly added devices, thereby providing a comprehensive and accurate data foundation for dispatch monitoring. At the same time, automated operation reduces manual intervention, improves the efficiency and accuracy of information updates, and can effectively help dispatchers quickly master the characteristics of new devices, thereby enabling them to efficiently and accurately process dispatch monitoring signals and effectively ensure the stable and reliable operation of the power system.

[0151] Figure 3 This is another flowchart illustrating a method for generating a knowledge base for handling scheduling and monitoring signals, provided as an exemplary embodiment of this application. For example... Figure 3 As shown, the method for generating this knowledge base for dispatch monitoring signal handling includes the following steps:

[0152] S301. Obtain the setting sheets corresponding to each protection device in the protection system.

[0153] S302. Based on the setting sheets corresponding to each protection device, extract the device model corresponding to each protection device to obtain multiple device models.

[0154] S303. For each device model among multiple device models, establish a sub-model corresponding to the device model.

[0155] For example, a sub-model is created using each device model as the keyword. Different protection device models correspond to multiple different sub-models. For instance, device model CSC103A and device model PCS931N correspond to two different sub-models.

[0156] S304. Identify all protection devices in the protection system that match the device model.

[0157] S305. For all protection devices that match the device model, parse the configuration file corresponding to each protection device and extract the status alarm and status action events in each configuration file.

[0158] S306. Add the extracted state quantity alarms and state quantity action events to the sub-model.

[0159] S307. Extract the preset scheduling and monitoring signal classification system from the OCS signal configuration library.

[0160] The dispatch and monitoring signal classification system includes protection action signals, reclosing action signals, device alarm signals, and communication anomaly signals.

[0161] S308. For each piece of information in the protected information, extract the corresponding semantic features.

[0162] S309. Match the semantic features with the scheduling and monitoring signal classification system to determine the signal classification corresponding to the information.

[0163] S310. Based on signal classification, determine the scheduling and monitoring signal attribute information corresponding to the information, and add the scheduling and monitoring signal attribute information to the sub-model.

[0164] For example, the sub-model includes a device model field, a protection information field, and a dispatch monitoring signal attribute information field. Correspondingly, the device model is stored in the device model field, the protection information is stored in the protection information field, and the dispatch monitoring signal attribute information is stored in the dispatch monitoring signal attribute information field.

[0165] S311. Based on multiple sub-models corresponding to multiple device models, a knowledge base for dispatching and monitoring signal processing is obtained.

[0166] For example, based on a pre-built template for a knowledge base for handling dispatch and monitoring signals, information from multiple sub-models is integrated to obtain the knowledge base for handling dispatch and monitoring signals. The template for this knowledge base includes the sub-model number, sub-model name, protection information, and dispatch and monitoring signal attribute information. For instance, the knowledge base for handling dispatch and monitoring signals is shown in Table 2.

[0167] In summary, this application has at least the following advantages:

[0168] First, by automatically extracting the device models of each protection device in the power grid protection system and establishing corresponding sub-models, and further adding the protection information corresponding to the device model and the dispatch monitoring signal attribute information corresponding to the protection information to the sub-models, the protection information of protection devices from different manufacturers and of different models is automatically associated with the dispatch monitoring signals in the OCS, efficiently constructing a complete knowledge base for dispatch monitoring signal handling. Correspondingly, when an anomaly occurs in the power grid and a corresponding dispatch monitoring signal is generated, based on this knowledge base, the association between the protection information and the corresponding dispatch monitoring signal attribute information can be quickly obtained without the need for manual matching, significantly shortening the information matching time and thus significantly improving the efficiency of dispatch monitoring signal handling. Simultaneously, the automatic association between the protection information and the dispatch monitoring signals in the OCS ensures the accuracy of the association results, significantly improving the accuracy, consistency, and reliability of dispatch monitoring signal handling. This is of positive significance for ensuring the safe, stable, and efficient operation of the power grid in complex and ever-changing operating environments, as well as improving the overall emergency response capability and intelligent management level of the power grid.

[0169] Second, by automatically identifying and parsing the configuration files of specific protection devices in the protection information system, it can accurately extract status alarm and action event information, realize the standardized collection and structured storage of protection information, effectively solve the problems of low efficiency, information omission and inconsistent format of traditional manual collection methods, provide a high-quality data foundation for the automated association between protection information and dispatch monitoring signals in OCS, and significantly improve the automation level and reliability of the construction of the dispatch monitoring signal processing knowledge base.

[0170] Third, by filtering and processing the protection information, irrelevant or redundant information can be removed, focusing on key protection data and ensuring the quality of the protection information. By determining the scheduling and monitoring signal attribute information corresponding to the filtered protection information and adding it to the sub-model, the sub-model can more accurately associate the protection information with the scheduling and monitoring signals, which helps to improve the efficiency of the scheduling and monitoring system in identifying and processing fault signals.

[0171] Fourth, by extracting protection device models from the protection information system according to a set cycle and comparing them with the dispatch monitoring signal handling knowledge base, newly added device models can be identified in a timely manner, and subsequent sub-model establishment and information addition processes can be automatically triggered. This ensures that the dispatch monitoring signal handling knowledge base can dynamically and in real time reflect the relevant status of protection devices in the power system, reducing the loss of knowledge base information due to the omission of newly added devices, thus providing a comprehensive and accurate data foundation for dispatch monitoring. At the same time, automated operation reduces manual intervention, improves the efficiency and accuracy of information updates, and can effectively help dispatchers quickly master the characteristics of new devices, thereby enabling them to handle dispatch monitoring signals efficiently and accurately, effectively ensuring the stable and reliable operation of the power system.

[0172] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0173] Figure 4 This is a schematic diagram of a device for generating a dispatch monitoring signal processing knowledge base, provided as an exemplary embodiment of this application. The device for generating a dispatch monitoring signal processing knowledge base provided in this embodiment is applied to the DCCS of the power grid, and the DCCS is communicatively connected to the OCS and the information protection system. Figure 4 As shown, the device 40 for generating the dispatch monitoring signal processing knowledge base includes an acquisition module 41, an extraction module 42, a model building module 43, a first processing module 44, and a second processing module 45, wherein:

[0174] Module 41 is used to obtain the setting sheets corresponding to each protection device in the information protection system;

[0175] Extraction module 42 is used to extract the device model corresponding to each protection device based on the setting sheet corresponding to each protection device, and obtain multiple device models;

[0176] Model building module 43 is used to build a sub-model corresponding to each of the multiple device models;

[0177] The first processing module 44 is used to obtain protection information of all protection devices corresponding to the device model from the protection information system and add the protection information to the sub-model; and, based on the scheduling and monitoring signal classification system in OCS, determine the scheduling and monitoring signal attribute information corresponding to the protection information and add the scheduling and monitoring signal attribute information to the sub-model.

[0178] The second processing module 45 is used to obtain a knowledge base for handling scheduling and monitoring signals based on multiple sub-models corresponding to multiple device models.

[0179] In one possible implementation, the first processing module 44 may be specifically used to: filter the protection information to obtain the filtered protection information; determine the scheduling and monitoring signal attribute information corresponding to the filtered protection information, and add the scheduling and monitoring signal attribute information to the sub-model.

[0180] In one possible implementation, the first processing module 44 can also be used to: respond to the received selection instruction from the user, determine the protection information that needs to be retained based on the selection instruction, and remove the protection information that was not selected to be retained from the sub-model to obtain the filtered protection information.

[0181] In one possible implementation, the protection information includes status alarms and status action events. The first processing module 44 can also be used to: identify all protection devices in the protection system that match the device model; for all protection devices that match the device model, parse the configuration files corresponding to each protection device and extract the status alarms and status action events from each configuration file; and add the extracted status alarms and status action events to the sub-model.

[0182] In one possible implementation, the dispatch monitoring signal classification system includes protection action signals, reclosing action signals, device alarm signals, and communication anomaly signals. The first processing module 44 can also be used to: extract a preset dispatch monitoring signal classification system from the OCS signal configuration library; extract the semantic features corresponding to each piece of information in the protection information; match the semantic features with the dispatch monitoring signal classification system to determine the signal classification corresponding to the information; and determine the dispatch monitoring signal attribute information corresponding to the information based on the signal classification.

[0183] In one possible implementation, the second processing module 45 may be specifically used to: extract the device models of all protection devices from the protection information system according to a set period; compare the extracted device models with the device models in the dispatch monitoring signal processing knowledge base to determine whether there are any new device models; if there are new device models, perform the step of establishing a sub-model corresponding to the device model for the new device model, until the new device model, the protection information corresponding to the new device model, and the dispatch monitoring signal attribute information corresponding to the protection information are added to the dispatch monitoring signal processing knowledge base.

[0184] The device for generating a knowledge base for dispatching and monitoring signal processing provided in this application embodiment can execute the technical solution shown in the above-described method embodiment for generating a knowledge base for dispatching and monitoring signal processing. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0185] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0186] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0187] It should be noted that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways; and it should be understood that the division of the various modules of the above device is only a logical functional division, and in actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can all be implemented in software through processing element calls; they can all be implemented in hardware; or some modules can be implemented by processing element calls to software, and some modules can be implemented in hardware. For example, the first processing module can be a separately established processing element, or it can be integrated into a chip of the above device. Alternatively, it can be stored as program code in the memory of the above device, and its function can be called and executed by a processing element of the above device. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by the integrated logic circuit in the hardware of the processor element or by software instructions.

[0188] For example, these modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). As another example, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a System-On-a-Chip (SOC).

[0189] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., Digital Video Discs, DVDs), or semiconductor media (e.g., solid-state disks (SSDs)).

[0190] Figure 5 A schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application. For example... Figure 5 As shown, the electronic device 50 in this embodiment includes:

[0191] At least one processor 51; and a memory 52 communicatively connected to said at least one processor;

[0192] The memory 52 stores instructions that can be executed by the at least one processor 51 to cause the electronic device to perform the method as described in any of the above embodiments.

[0193] Alternatively, the memory 52 can be either standalone or integrated with the processor 51.

[0194] The memory 52 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.

[0195] The processor 51 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. Specifically, when implementing the method for generating the scheduling monitoring signal processing knowledge base described in the foregoing method embodiments, the electronic device may be, for example, a server or other electronic device with processing capabilities.

[0196] Optionally, the electronic device may also include a communication interface 53. In specific implementations, if the communication interface 53, memory 52, and processor 51 are implemented independently, they can be interconnected via a bus to complete communication. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not imply that there is only one bus or one type of bus.

[0197] Optionally, in a specific implementation, if the communication interface 53, memory 52 and processor 51 are integrated on a single chip, then the communication interface 53, memory 52 and processor 51 can communicate through an internal interface.

[0198] The implementation principle and technical effects of the electronic device provided in this embodiment can be found in the foregoing embodiments, and will not be repeated here.

[0199] This application also provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed, they are used to implement the method steps as described in the above method embodiments. The specific implementation methods and technical effects are similar and will not be repeated here.

[0200] The aforementioned computer-readable storage media can be implemented from any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0201] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in a device for generating a knowledge base for scheduling and monitoring signal processing.

[0202] This application also provides a computer program product, including a computer program, which, when executed, implements the method steps as described in the above method embodiments. The specific implementation and technical effects are similar and will not be repeated here.

[0203] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0204] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0205] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for generating a knowledge base for dispatching and monitoring signal processing, characterized in that, A dispatching and command control system (DCCS) applied to a power grid, wherein the DCCS is communicatively connected to both the dispatching and monitoring system (OCS) and the information protection system (IPS) within the power grid, and the method includes: Obtain the setting sheets corresponding to each protection device in the information protection system; Based on the setting sheets corresponding to each of the protection devices, the device models corresponding to each of the protection devices are extracted to obtain multiple device models; For each of the multiple device models, a sub-model corresponding to that device model is established; The protection information of all protection devices corresponding to the device model is obtained from the protection information system, and the protection information is added to the sub-model; Based on the scheduling and monitoring signal classification system in the OCS, the scheduling and monitoring signal attribute information corresponding to the protection information is determined, and the scheduling and monitoring signal attribute information is added to the sub-model; Based on the multiple sub-models corresponding to the multiple device models, a knowledge base for handling scheduling and monitoring signals is obtained.

2. The method for generating a knowledge base for dispatch monitoring signal processing according to claim 1, characterized in that, The step of determining the scheduling and monitoring signal attribute information corresponding to the protection information and adding the scheduling and monitoring signal attribute information to the sub-model includes: The protection information is filtered to obtain filtered protection information; Determine the scheduling and monitoring signal attribute information corresponding to the protection information after the filtering process, and add the scheduling and monitoring signal attribute information to the sub-model.

3. The method for generating a knowledge base for dispatching and monitoring signal processing according to claim 2, characterized in that, The filtering process of the protection information to obtain filtered protection information includes: Upon receiving a selection instruction from the user, the system determines the protection information that needs to be retained based on the selection instruction. The protection information that was not selected to be retained is removed from the sub-model to obtain the filtered protection information.

4. The method for generating a knowledge base for dispatch monitoring signal processing according to any one of claims 1 to 3, characterized in that, The protection information includes status alarms and status action events. The step of obtaining protection information for all protection devices corresponding to the device model from the protection information system and adding the protection information to the sub-model includes: Identify all protection devices in the security system that match the device model; For all protection devices that match the device model, parse the configuration files corresponding to each protection device and extract the status alarms and status action events in each configuration file; Add the extracted state quantity alarms and state quantity action events to the sub-model.

5. The method for generating a knowledge base for dispatch monitoring signal processing according to any one of claims 1 to 3, characterized in that, The dispatch monitoring signal classification system includes protection action signals, reclosing action signals, device alarm signals, and communication anomaly signals. The determination of dispatch monitoring signal attribute information corresponding to the protection information based on the dispatch monitoring signal classification system in the OCS includes: Extract the preset scheduling and monitoring signal classification system from the signal configuration library of the OCS; For each piece of information in the protection information, extract the semantic features corresponding to that information; The semantic features are matched with the scheduling and monitoring signal classification system to determine the signal classification corresponding to the information; Based on the signal classification, the scheduling and monitoring signal attribute information corresponding to the information is determined.

6. The method for generating a knowledge base for dispatch monitoring signal processing according to any one of claims 1 to 3, characterized in that, Also includes: According to a set cycle, extract the device models of all protection devices from the information protection system; Compare the extracted device models with the device models in the dispatch and monitoring signal processing knowledge base to determine whether any new device models have been added. In the case of a new device model, for the new device model, the step of establishing a sub-model corresponding to the device model is performed until the new device model, the protection information corresponding to the new device model, and the scheduling and monitoring signal attribute information corresponding to the protection information are added to the scheduling and monitoring signal processing knowledge base.

7. A device for generating a knowledge base for dispatching and monitoring signal processing, characterized in that, A dispatching and command control system (DCCS) for power grids, wherein the DCCS is communicatively connected to the dispatching and monitoring system (OCS) and the information protection system in the power grid, the device comprising: The acquisition module is used to acquire the setting sheets corresponding to each protection device in the information protection system; The extraction module is used to extract the device model corresponding to each of the protection devices based on the setting sheet corresponding to each of the protection devices, so as to obtain multiple device models. The model building module is used to build a sub-model corresponding to each of the multiple device models. The first processing module is used to obtain protection information of all protection devices corresponding to the device model from the protection information system and add the protection information to the sub-model; and, based on the scheduling and monitoring signal classification system in the OCS, determine the scheduling and monitoring signal attribute information corresponding to the protection information and add the scheduling and monitoring signal attribute information to the sub-model. The second processing module is used to obtain a knowledge base for handling scheduling and monitoring signals based on multiple sub-models corresponding to the multiple device models.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory is used to store computer-executed instructions; The processor is configured to execute the computer execution instructions to implement the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed, are used to implement the method as described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed, it implements the method as described in any one of claims 1 to 6.

Images