Verification method and device of substation configuration description file, electronic equipment and storage medium

Abstract

The invention relates to the technical field of electric power information security, in particular to a verification method and device for a substation configuration description file, electronic equipment and a computer readable storage medium, and the method comprises the steps: receiving a to-be-verified substation configuration description file uploaded by a user; analyzing the substation configuration description file, and extracting configuration information; performing feature extraction on the analyzed configuration information to obtain structured feature data; performing entity identification and relation extraction on the structured feature data to obtain entities related to the virtual terminal loop and relation data between the entities; constructing a knowledge graph based on the entities and the relationship data between the entities, and performing automatic verification on the virtual terminal loop integrity and configuration consistency of the substation configuration description file in combination with a preset verification rule to obtain a verification result; and outputting a verification result in a visual form. Therefore, the management efficiency of the configuration file and the correctness of verifying the configuration file can be effectively improved, the safety of the power system is enhanced, and the manual operation risk is reduced.

Description

Technical Field

[0001] This application relates to the field of power information security technology, and in particular to a method, apparatus, electronic device and computer-readable storage medium for verifying substation configuration description files. Background Technology

[0002] In the entire process of designing, commissioning, and operating smart substations, verifying the integrity of virtual terminal circuits in the Substation Configuration Description (SCD) file is a crucial step in ensuring the safe operation of the power grid. Current mainstream verification methods primarily rely on manual review or fixed inspection rules defined by XMLSchema, both of which have significant drawbacks. The problem is that existing verification methods cannot simultaneously address verification efficiency, result accuracy, and the ability to understand the semantics of power business operations, making it difficult to meet the requirements of standardized engineering and process-oriented management.

[0003] Specifically, SCD files use XML format and are characterized by their large content and complex structure. The SCD file of a 220kV substation can reach millions of lines. Manually comparing and verifying the virtual terminal connection relationships line by line is not only extremely inefficient, becoming a bottleneck in project implementation, but also prone to fatigue misjudgment due to high-intensity repetitive work. Especially for complex logic circuits across devices and bays, hidden errors are difficult to detect, posing a significant hidden danger to power grid safety. On the other hand, the inspection rules based on XMLSchema can only achieve basic syntax-level verification and lack the ability to understand the business logic and semantic relationships of the power system behind the configuration information. It is impossible to accurately judge the rationality of virtual circuit connections. Moreover, both manual verification and fixed rule verification lack unified quantitative standards, resulting in inconsistent verification quality. It is difficult to ensure the quality consistency of the acceptance process and cannot provide effective support for the safe and reliable operation of smart substations. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and computer-readable storage medium for verifying substation configuration description files, which can effectively improve the efficiency of configuration file management and the correctness of configuration files, enhance the security of power systems, and realize the safe and reliable operation of smart substations.

[0005] To achieve the above objectives, this application adopts the following technical solution: Firstly, a method for verifying substation configuration description files is provided, including: Receive the substation configuration description file uploaded by the user and trigger the verification process; The substation configuration description file is parsed to extract configuration information; The parsed configuration information is subjected to feature extraction to obtain structured feature data; Entity recognition and relationship extraction are performed on the structured feature data to obtain entity data related to virtual terminal circuits and the relationship data between entities; Based on the entity and relationship data between entities, a knowledge graph is constructed, and the integrity and configuration consistency of the virtual terminal circuits in the substation configuration description file are automatically verified in combination with preset verification rules to obtain the verification results. The verification results are output in a visual format.

[0006] Secondly, a verification device for a substation configuration description file is provided, comprising: The receiving module is used to receive the substation configuration description file to be verified uploaded by the user and trigger the verification process; The parsing module is used to parse the substation configuration description file and extract configuration information; The first extraction module is used to extract features from the parsed configuration information to obtain structured feature data; The second extraction module is used to perform entity recognition and relationship extraction on the structured feature data to obtain entity and relationship data related to virtual terminal circuits. The construction module is used to construct a knowledge graph based on the entity and the relationship data between entities, and to automatically verify the integrity and configuration consistency of the virtual terminal circuits of the substation configuration description file in combination with preset verification rules, so as to obtain the verification results. The output module is used to output the verification results in a visual form.

[0007] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method for verifying a substation configuration description file as described in any of the first aspects above.

[0008] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method for verifying a substation configuration description file as described in any of the first aspects above.

[0009] Fifthly, embodiments of this application provide a computer program product that, when run on an electronic device, causes the electronic device to execute the verification method for the substation configuration description file described in any of the first aspects above.

[0010] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here.

[0011] In this embodiment, the system first receives a substation configuration description file uploaded by a user; it then parses the file to extract configuration information, and performs feature extraction on the parsed information to obtain structured feature data. Entity recognition and relationship extraction are then performed on the structured feature data to obtain entity data related to virtual terminal circuits and the relationships between these entities. Based on this entity and relationship data, a knowledge graph is constructed, and combined with preset verification rules, the integrity and configuration consistency of the virtual terminal circuits in the substation configuration description file are automatically verified to obtain the verification results. These results are then output in a visual format. This effectively improves the efficiency of configuration file management and verifies the correctness of configuration files, enhances power system security, reduces the risk of human error, and enables the safe and reliable operation of smart substations.

[0012] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0013] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiments below. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This is a flowchart illustrating a method for verifying a substation configuration description file provided in an embodiment of this application. Figure 2 This is another flowchart illustrating the verification method for substation configuration description files provided in the embodiments of this application; Figure 3 This is a structural block diagram of the verification device for the substation configuration description file provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0014] The embodiments of the technical solutions of this application will now be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solutions of this application, and are therefore merely examples and should not be used to limit the scope of protection of this application. When the following description relates to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. Various changes, modifications, and equivalents of the methods, apparatus, and / or systems described herein will become apparent upon understanding this disclosure. For example, the order of operations described herein is merely illustrative and is not limited to those orders set forth herein, but can be changed as will become apparent upon understanding this disclosure, except for operations that must be performed in a specific order. Furthermore, for clarity and conciseness, descriptions of features known in the art may be omitted.

[0015] The embodiments described in the following examples of this disclosure are not representative of all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0016] It should be noted that currently, in most design, debugging, and maintenance stages, the verification of the integrity of virtual terminal circuits in SCD files still heavily relies on manual review by design, debugging, or maintenance engineers. While there are also methods based on XMLSchema-defined checking rules to verify the correctness of SCDs, these current technologies have the following drawbacks: (1) SCD files are in XML format, with large content and complex structure. A single SCD file for a 220kV substation can have millions of lines. Engineers need to manually compare and find the matching relationship between each ExtRef under Inputs and the DataSet under the sending end in a dedicated tool or text editor, which is time-consuming and labor-intensive and has become a bottleneck in project implementation.

[0017] (2) The number of virtual terminal connections is huge and the connection relationships are intricate. Manual review is prone to misjudgment and omission due to fatigue under high-intensity and repetitive work. In particular, for complex logic circuits that span devices and bays, the hidden errors may pose a major hidden danger to power grid safety.

[0018] (3) Manual verification lacks unified and quantitative standards, and the quality of verification varies from person to person. It is difficult to achieve standardized and process-oriented management, and it is impossible to guarantee the quality uniformity of the acceptance process.

[0019] (4) Unable to understand the power system business logic and semantic relationships behind the configuration information, such as the correctness of virtual loop connections.

[0020] It should be noted that the execution subject of the substation configuration description file verification method in this embodiment can be a substation configuration description file verification device, hereinafter referred to as "device". This device can be configured in any type of electronic device, and this application embodiment does not limit it.

[0021] See Figure 1 This is a flowchart illustrating the verification method for substation configuration description files provided in the first embodiment of this application. Figure 1 As shown, the verification method for substation configuration description files may include the following steps: Step 101: Receive the substation configuration description file uploaded by the user and trigger the verification process.

[0022] The Substation Configuration Description (SCD) file is the core configuration file of a smart substation. It is unique across the entire substation and is used to fully describe the instance configuration, communication parameters, inter-device communication information, and primary system structure of all smart electronic devices in the substation. It serves as the basis for configuring and verifying the secondary system of the substation.

[0023] Optionally, the system can receive substation configuration description files uploaded by users through the front-end page of the intelligent substation configuration file management system. These substation configuration description files can be a single substation configuration description file or a compressed package of substation configuration description files.

[0024] It should be noted that the system first receives the substation configuration description file uploaded by the user to ensure that the file is accurately transmitted to the verification system. After the file is received, the system automatically triggers the entire verification process, including file parsing, feature extraction, entity recognition and relationship extraction, knowledge graph construction and verification, and result output.

[0025] Optionally, an interaction method combining system login and front-end page upload can be adopted.

[0026] First, users must log in to the intelligent substation configuration file management system using authentication methods such as account and password, and then submit the file to be verified through the designated file upload portal on the system's front-end page. This mode, through the system's access control mechanism, can accurately identify user identities, ensuring that only authorized users can upload files, effectively preventing unauthorized files from accessing the verification system, guaranteeing the data security of power configuration files and the standardization of the verification process, and complying with relevant regulations and requirements for power information security management.

[0027] Specifically, the substation configuration description file is compatible with two file formats: it supports the upload and verification of a single substation configuration description file, adapting to single-file precise verification scenarios (such as single circuit configuration debugging, single-station single-point problem troubleshooting, etc.), and it also supports the upload and verification of a compressed package of substation configuration description files, adapting to multi-file batch verification scenarios (such as centralized verification of multi-bay configuration files, batch review of configuration files of multiple substations, etc.). It can flexibly meet the file upload requirements under different engineering stages and different verification needs, improving the scenario adaptability of the verification process.

[0028] In other words, users access the login configuration file management system and upload the scd file or scd file compressed package that needs to be verified. After the user submits the configuration file to be verified, the system background service automatically triggers the subsequent verification logic.

[0029] Step 102: Parse the substation configuration description file and extract the configuration information.

[0030] Among them, the virtual terminal circuit: based on the IEC61850 standard, the "virtual terminal" and "virtual circuit" represent the logical connection relationship of substation events (GOOSE) and sampled values ​​(SV) oriented to general objects, replacing the traditional physical terminal connection. It is the core logical link for signal transmission in the secondary system of smart substations, and its integrity directly affects the safe operation of the power grid.

[0031] Optionally, the substation configuration description file can be parsed using the Document Object Model (DOM4J) parsing method. The extracted configuration information includes intelligent electronic device information, logical device information, logical node information, and input information.

[0032] Specifically, after receiving the SCD file, the configuration file management system integrates the DOM4J parsing method to extract information such as IED, LD, LN, and Inputs.

[0033] Step 103: Extract features from the parsed configuration information to obtain structured feature data.

[0034] Among them, structured feature data refers to a set of key data with a fixed format and clear semantics extracted from the parsed information of the substation configuration description file. It can accurately characterize the core components of the virtual terminal circuit and provide standardized input for subsequent entity recognition and relationship extraction.

[0035] Optionally, the Power-Roberts model can be launched using the open-source power information security technology Apache OpenNLP utility class. Based on the Power-Roberts model, features can be extracted from the parsed configuration information to obtain structured feature data. The structured feature data includes the source intelligent electronic device (IED) name, logical device (LD) name, logical node (LN) name, data object name, as well as the reference name and configuration parameters of the substation event GOOSE control block and sampled value (SV) control block for general objects.

[0036] Optionally, the Power-Roberts engine module can be started through the Apache OpenNLP utility class to achieve accurate feature extraction based on the Power-Roberts rule engine. Feature strings can be extracted, for example, the source IED name, LD name, LN name, and data object name can be extracted from the string "LDName / LNName.DOName.DANam".

[0037] Optionally, it can also identify key configuration blocks and accurately locate the reference names and configuration parameters of the GOOSE control block (GSEControl) and SV control block (SampledValueControl).

[0038] Output structured key-value pair data, such as: {sourceIED:"PTRC01",sourceDO:"Trpt",targetIED:"CBR01",targetDA:"Pos"}.

[0039] Step 104: Perform entity recognition and relationship extraction on the structured feature data to obtain entity data related to virtual terminal circuits and the relationship data between entities.

[0040] Among them, the Power-Roberts model is a feature extraction model suitable for power configuration file analysis. It is optimized and extended based on the Roberts edge detection principle and combined with the grammatical rules and semantic features of power configuration files. It can accurately extract the core feature information related to virtual terminal circuits in substation configuration description files. It needs to be started and run through open source natural language processing tools.

[0041] Among them, entities (related to virtual terminal circuits) refer to core elements with clear functional attributes in the substation configuration description file. They are defined by the named entity recognition model and include, but are not limited to, protection intelligent electronic equipment, circuit breaker intelligent electronic equipment, logic devices, logic nodes, etc. They are the basic units that constitute virtual terminal circuits.

[0042] Among them, the relationship between entities (virtual terminal circuit relationship) refers to the functional association and logical connection between entities in the virtual terminal circuit. The core relationships include: sending substation event signals for general objects, receiving substation event signals for general objects (representing signal transmission relationship), affiliation relationship (such as logical nodes belonging to logical devices), and inclusion relationship (such as datasets containing data objects).

[0043] Optionally, a Named Entity Recognition (NER) model can be used to identify entities in the structured feature data, defining the elements in the substation configuration description file as entities. A Relationship Extraction (RE) model can be used to extract relationships from the structured feature data to obtain the relationships between entities in the virtual terminal circuit.

[0044] The relationships between entities include sending substation event signals for general objects, receiving substation event signals for general objects, attribution relationships, and inclusion relationships.

[0045] Specifically, an AI interface can be built by integrating the Deep Java Library (DJL). By utilizing Named Entity Recognition (NER) and Relationship Extraction (RE) models, the "entities" related to virtual terminal circuits (such as protection IEDs and circuit breaker IEDs) can be automatically identified from the parsed SCD file configuration information. The "relationships" between these entities (such as sending GOOSE signals and attribution relationships) can be extracted, ultimately forming structured virtual terminal circuit data, laying the foundation for subsequent knowledge graph construction and automated verification.

[0046] Optionally, the configuration file management system and the AI ​​model can be technically integrated by integrating the Deep Java Library (DJL) to build a standardized AI calling interface. The core function of DJL is to shield the underlying implementation details of the AI ​​model, allowing the configuration file management system (developed in Java) to easily call NER and RE models trained in other languages ​​such as Python, without needing to concern itself with the model's deployment environment and operating mechanism.

[0047] Optionally, structured feature data (such as source IED name, LD name, LN name, data object name, etc.) can be extracted from the SCD file. The NER model learns the syntax rules and semantic features of power sector configuration files, automatically classifying elements in the SCD as entities with clearly defined functional attributes, and outputting the entity type and entity name, for example: Entity types: protection IED, circuit breaker IED, intelligent terminal IED, logical node (LN), dataset (DataSet), data object (DO), etc.; Entity name: The specific device name (e.g., “Protection IED01”), logical node identifier (e.g., “PTRC01”), etc.

[0048] Optionally, the RE model can be used to analyze the contextual configuration information between entities to determine the specific relationships between them. For example, when the model identifies the entities "Protection IED" and "Smart Terminal IED," and their configuration information contains keywords such as "trip signal" and "permanent trip," it will automatically determine the relationship as "Protection IED sends a trip signal to Smart Terminal IED." When the "LN" and "IED" entities are identified, the hierarchical structure of the SCD file determines the relationship that "LN belongs to IED." When the "DataSet" and "DO" entities are identified, the inclusion relationship of "DataSet contains DO" is determined based on the inclusion relationship of the configuration information. The model outputs the relationship types and relationship pairs between entities, for example: Relationship types: sending GOOSE signals, receiving GOOSE signals, attribution relationship, containment relationship, etc.; Relationship pairs: (Protection IED01, sends trip signal, intelligent terminal IED01), (LN01, belongs to, IED01), (DataSet01, contains, DO01), etc.

[0049] Optionally, the entities identified by NER can be associated and integrated with the relationships extracted by RE to form structured virtual terminal loop data, which includes: all entities participating in the loop (devices, nodes, datasets, etc.); complete relationship chains between entities (signal transmission-reception paths, hierarchical affiliation, etc.); and the core attributes of the loop (such as signal type, configuration parameters, etc.).

[0050] Step 105: Based on entity and inter-entity relationship data, construct a knowledge graph and combine it with preset verification rules to automatically verify the integrity and configuration consistency of virtual terminal circuits in the substation configuration description file, and obtain the verification results.

[0051] Among them, knowledge graph (virtual terminal circuit domain) is a structured data model that graphically displays virtual terminal circuit entities and the relationships between entities. It uses intelligent electronic devices as "nodes" and virtual terminal connections, signal transmissions, and other relationships as "edges". It can intuitively present the topology of the entire station's virtual terminal circuits, providing visualized and logical data support for automated verification.

[0052] Among them, the preset verification rules are verification criteria formulated based on the power system safety operation specifications and virtual terminal configuration technical requirements. They are used to judge the integrity and configuration consistency of virtual terminal circuits. The core rules include the trip signal reception validity rules and the substation event control block parameter consistency rules for general objects, which are the core basis for automated verification.

[0053] Among them, the intelligent substation configuration file management system is a dedicated system for realizing the full lifecycle management of substation configuration description files. It supports users to upload files, trigger verification processes, and view visual verification results. It integrates functional modules such as document parsing, feature extraction, AI analysis, and knowledge graph construction, and is the core application carrier of this method.

[0054] Optionally, the preset verification rules shall include at least the following two items: If there is a GOOSE transmission signal of type trip, then the knowledge graph must have a corresponding edge for receiving GOOSE signals pointing to the legitimate target IED; The application identifier and configuration version attribute of the GOOSE control blocks at both ends of the virtual terminal connection are consistent.

[0055] In other words, a knowledge graph can be used to provide a macroscopic view of virtual terminal loop data. Simultaneously, the system combines expert knowledge bases to extract verification rules, such as "For a GOOSE transmission signal of type 'trip,' there must be a 'receive GOOSE signal' relationship edge in the knowledge graph pointing to a legitimate target IED," ensuring loop integrity. "The appID and confRev attributes of the GOOSE control blocks at both ends must be equal," ensuring consistent SCD file configuration.

[0056] Step 106: Output the verification results in a visual format.

[0057] Optionally, a full-site secondary loop diagram can be drawn using intelligent electronic devices as nodes and virtual terminal connections as edges. Nodes and edges that are verified to be abnormal can be highlighted with a preset eye-catching color and a hover prompt with abnormality details can be provided.

[0058] Specifically, inconsistent verification results can be returned to the browser frontend, which can then visualize the data using Echarts / G6 or similar methods. Using IEDs as nodes and virtual terminal connections as edges, a secondary circuit diagram of the entire substation can be drawn. Incomplete circuits or configuration errors detected by the rule engine are highlighted in a striking red color on the diagram, along with detailed hover prompts, greatly facilitating rapid problem localization. Through this visual interface, users can intuitively and globally control the connection status of all virtual terminal circuits in the substation. Not only can logical errors and configuration defects in circuit connections be clearly identified, but users can also obtain complete upstream and downstream relationship information and violation details through interactive queries (such as clicking on nodes / edges). This function transforms the traditional, slow, and error-prone process of manual, item-by-item verification into a proactive, automated, and visualized intelligent verification mode. This allows for the early detection and accurate location of potential hazards during the design, commissioning, and even operation and maintenance phases, fundamentally preventing safety accidents such as relay protection malfunctions and failures due to configuration file errors, and significantly improving the reliability, safety, and construction efficiency of smart substation projects.

[0059] In this embodiment, the system first receives a substation configuration description file uploaded by a user; it then parses the file to extract configuration information, and performs feature extraction on the parsed information to obtain structured feature data. Entity recognition and relationship extraction are then performed on the structured feature data to obtain entity data related to virtual terminal circuits and the relationships between these entities. Based on this entity and relationship data, a knowledge graph is constructed, and combined with preset verification rules, the integrity and configuration consistency of the virtual terminal circuits in the substation configuration description file are automatically verified to obtain the verification results. These results are then output in a visual format. This effectively improves the efficiency of configuration file management and verifies the correctness of configuration files, enhances power system security, reduces the risk of human error, and enables the safe and reliable operation of smart substations.

[0060] In some scenarios, embodiments of this application can be applied to intelligent station configuration file management systems. The intelligent station configuration file management system integrates the Dom4j method for parsing SCDs and also integrates the Deep Java Library (DJL) package to achieve integration of AI interfaces with Apache OpenNLP utility classes. Relying on the Power-Roberts model, the system can extract feature strings from virtual terminal loops. Regarding AI integration, the system uses Named Entity Recognition (NER) and Relation Extraction (RE) models to identify, classify, and extract entity relationships. The configuration file management system uses a knowledge graph visualization approach. Combining the system with an expert knowledge base, it determines the correctness of the loop and returns the result to the front-end page for presentation in the browser. The client browser accesses the front-end system page and uploads the SCD configuration file. An XML parser and Power-Roberts rule engine extract feature strings. The NER and RE models understand the feature information, quickly constructing a detailed virtual terminal loop knowledge graph with high parsing and retrieval efficiency. Simultaneously, it compares the results with the expert knowledge base to obtain virtual loop integrity verification results. The front-end visualization model renders knowledge graphs and verification results into interactive graphics, enabling designers or maintenance teams to easily identify and locate problems. A powerful AI-assisted design verification platform based on a configuration file management system has been built, which can greatly improve the efficiency and reliability of smart substation design, freeing engineers from tedious manual verification. Furthermore, compared to existing technologies, its applications are more extensive and targeted.

[0061] like Figure 2 As shown, this illustrates the entire process from user file upload to outputting verification results. The core of this process is automated verification achieved through a configuration file management system combined with AI and Power-Roberts models. The specific process can be divided into seven key stages: 1. User interaction phase Users (operations / maintenance personnel / designers) access the configuration file management system through terminal devices, upload the SCD file to be verified (supports single file or compressed package), and trigger the verification process.

[0062] 2. Initial Analysis and Feature Extraction The configuration file management system performs preliminary parsing on the uploaded SCD file to extract basic configuration information such as IED (Intelligent Electronic Device), LD (Logical Device), LN (Logical Node), and Inputs.

[0063] 3. Feature extraction of the Power-Roberts model Based on the initial parsed configuration information, the Power-Roberts engine further parses signal data such as ExtRef (external reference) and outputs structured feature data (including key information such as source IED, LD, LN, and data object).

[0064] 4. AI-enhanced entity and relationship extraction AI-powered intelligent analysis services identify entity types (such as "protection IED" and "circuit breaker IED") through NER models, extract relationships between entities (such as "sending trip signals", "receiving signals", and "attribution relationships") through RE models, and integrate them into virtual terminal circuit data (containing structured information about entities and relationships).

[0065] 5. Automated verification A knowledge graph is constructed based on virtual terminal circuit data, and preset verification rules (such as "trip signal must have a receiver") are loaded. Combined with an expert knowledge base, the knowledge graph and rules are compared to complete the integrity and consistency verification of virtual terminal circuits.

[0066] 6. Output of verification results The configuration file management system returns the verification results (including anomaly information) in the form of structured data and displays them visually through the system's front-end interface (e.g., presenting the loop topology as nodes / edges and highlighting anomalies).

[0067] 7. Closed-loop process Result: Users can view the verification results through the front-end interface and complete the verification of the SCD file, realizing a closed loop of the entire process of "upload-parse-extract-verify-display".

[0068] Corresponding to the verification method for substation configuration description files described in the above embodiments, Figure 3 This is a structural block diagram of the verification device for the substation configuration description file provided in the embodiments of this application.

[0069] Reference Figure 3 The verification device 200 for the substation configuration description document includes: The receiving module 210 is used to receive the substation configuration description file to be verified uploaded by the user and trigger the verification process; The parsing module 220 is used to parse the substation configuration description file and extract configuration information; The first extraction module 230 is used to extract features from the parsed configuration information to obtain structured feature data; The second extraction module 240 is used to perform entity recognition and relationship extraction on the structured feature data to obtain entity and relationship data related to virtual terminal circuits. The construction module 250 is used to construct a knowledge graph based on the entity and the relationship data between entities, and to automatically verify the integrity and configuration consistency of the virtual terminal circuits of the substation configuration description file in combination with preset verification rules, so as to obtain the verification results. Output module 260 is used to output the verification results in a visual form.

[0070] Optionally, the parsing module is specifically used for: The substation configuration description file is parsed using the Document Object Model (DOM4J) parsing method. The extracted configuration information includes intelligent electronic device information, logical device information, logical node information, and input information.

[0071] Optionally, the first extraction module specifically includes a startup unit and a feature extraction unit: The startup unit is used to start the Power-Roberts model using the Apache OpenNLP utility class, an open-source power information security technology. The feature extraction unit is used to extract features from the parsed configuration information based on the Power-Roberts model to obtain structured feature data; The structured feature data includes the source intelligent electronic device (IED) name, logical device (LD) name, logical node (LN) name, data object name, and reference names and configuration parameters of the substation event GOOSE control block and sampled value (SV) control block for general objects.

[0072] Optionally, the second extraction module specifically includes an entity recognition unit and a relationship extraction unit: An entity recognition unit is used to perform entity recognition on the structured feature data using a Named Entity Recognition (NER) model, so as to define the elements in the substation configuration description file as entities. The relation extraction unit is used to extract relations from the structured feature data using a relation extraction (RE) model to obtain the relationships between entities in the virtual terminal loop. The relationships between entities include sending substation event signals for general objects, receiving substation event signals for general objects, attribution relationships, and inclusion relationships.

[0073] Optionally, the preset verification rules used in the construction verification module include at least the following two items: If there is a GOOSE transmission signal of type trip, then the knowledge graph must have a corresponding edge for receiving GOOSE signals pointing to the legitimate target IED; The application identifier and configuration version attribute of the GOOSE control blocks at both ends of the virtual terminal connection are consistent.

[0074] Optionally, the output module is specifically used for: Draw a secondary loop diagram of the entire station using intelligent electronic devices as nodes and virtual terminal connections as edges; Nodes and edges that fail verification are highlighted with a preset, eye-catching color and provided with hover prompts for details of the failure.

[0075] Optionally, the receiving module is specifically used for: The system receives substation configuration description files uploaded by users through the front-end page of the intelligent substation configuration file management system. The substation configuration description files include a single substation configuration description file or a compressed package of substation configuration description files.

[0076] In this embodiment, the system first receives a substation configuration description file uploaded by a user; it then parses the file to extract configuration information, and performs feature extraction on the parsed information to obtain structured feature data. Entity recognition and relationship extraction are then performed on the structured feature data to obtain entity data related to virtual terminal circuits and the relationships between these entities. Based on this entity and relationship data, a knowledge graph is constructed, and combined with preset verification rules, the integrity and configuration consistency of the virtual terminal circuits in the substation configuration description file are automatically verified to obtain the verification results. These results are then output in a visual format. This effectively improves the efficiency of configuration file management and verifies the correctness of configuration files, enhances power system security, reduces the risk of human error, and enables the safe and reliable operation of smart substations.

[0077] in addition, Figure 3 The verification device for the substation configuration description document shown can be a software unit, hardware unit, or a combination of software and hardware built into existing electronic equipment. It can also be integrated into the electronic equipment as an independent component, or exist as an independent electronic equipment.

[0078] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0079] Figure 4 This is a schematic diagram of the structure of the electronic device provided in an embodiment of this application. For example... Figure 4 As shown, the electronic device 5 of this embodiment includes: at least one processor 50 ( Figure 4 (Only one is shown in the diagram) a processor, a memory 51, and a computer program 52 stored in the memory 51 and executable on the at least one processor 50, wherein the processor 50 executes the computer program 52 to implement the steps in the verification method embodiments of any of the above-described substation configuration description files.

[0080] The electronic device may be a desktop computer, laptop, handheld computer, or cloud server, etc. This electronic device may include, but is not limited to, a processor and memory. Those skilled in the art will understand that... Figure 4 This is merely an example of electronic device 5 and does not constitute a limitation on electronic device 5. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0081] The processor 50 may be a central processing unit, or it may be other general-purpose processors, digital signal processors, application-specific integrated circuits, off-the-shelf programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0082] In some embodiments, the memory 51 may be an internal storage unit of the electronic device 5, such as a hard disk or memory of the electronic device 5. In other embodiments, the memory 51 may be an external storage device of the electronic device 5, such as a plug-in hard disk, smart memory card, secure digital card, flash memory card, etc., equipped on the electronic device 5. Further, the memory 51 may include both internal storage units and external storage devices of the electronic device 5. The memory 51 is used to store operating systems, applications, boot loaders, data, and other programs, such as the program code of the computer program. The memory 51 can also be used to temporarily store data that has been output or will be output.

[0083] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps in the above-described method embodiments.

[0084] This application provides a computer program product that, when run on an electronic device, enables the electronic device to implement the steps described in the various method embodiments above.

[0085] If the integrated unit is implemented as a software functional unit and used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a device / electronic device, a recording medium, a computer memory, a read-only memory, a random access memory, an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks.

[0086] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

[0088] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.

[0089] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0090] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for verifying a substation configuration description file, characterized in that, include: Receive the substation configuration description file uploaded by the user and trigger the verification process; The substation configuration description file is parsed to extract configuration information; The parsed configuration information is subjected to feature extraction to obtain structured feature data; Entity recognition and relationship extraction are performed on the structured feature data to obtain entity data related to virtual terminal circuits and the relationship data between entities; Based on the entity and relationship data between entities, a knowledge graph is constructed, and the integrity and configuration consistency of the virtual terminal circuits in the substation configuration description file are automatically verified in combination with preset verification rules to obtain the verification results. The verification results are output in a visual format.

2. The method according to claim 1, characterized in that, The step of parsing the substation configuration description file and extracting configuration information includes: The substation configuration description file is parsed using the Document Object Model (DOM4J) parsing method. The extracted configuration information includes intelligent electronic device information, logical device information, logical node information, and input information.

3. The method according to claim 1, characterized in that, The step of extracting features from the parsed configuration information to obtain structured feature data includes: The Power-Roberts model is launched using the Apache OpenNLP utility class, an open-source power information security technology. Based on the Power-Roberts model, feature extraction is performed on the parsed configuration information to obtain structured feature data. The structured feature data includes the source intelligent electronic device (IED) name, logical device (LD) name, logical node (LN) name, data object name, and reference names and configuration parameters of the substation event GOOSE control block and sampled value (SV) control block for general objects.

4. The method according to claim 1, characterized in that, The step of performing entity recognition and relationship extraction on the structured feature data to obtain entity and relationship data related to virtual terminal circuits includes: The Named Entity Recognition (NER) model is used to perform entity recognition on the structured feature data, so as to define the elements in the substation configuration description file as entities; The relation extraction (RE) model is used to extract relations from the structured feature data to obtain the relationships between entities in the virtual terminal loop. The relationships between entities include sending substation event signals for general objects, receiving substation event signals for general objects, attribution relationships, and inclusion relationships.

5. The method according to claim 1, characterized in that, in, The preset verification rules include at least the following two items: If there is a GOOSE transmission signal of type trip, then the knowledge graph must have a corresponding edge for receiving GOOSE signals pointing to the legitimate target IED; The application identifier and configuration version attribute of the GOOSE control blocks at both ends of the virtual terminal connection are consistent.

6. The method according to claim 1, characterized in that, The step of outputting the verification results in a visual form includes: Draw a secondary loop diagram of the entire station using intelligent electronic devices as nodes and virtual terminal connections as edges; Nodes and edges that fail verification are highlighted with a preset, eye-catching color and provided with hover prompts for details of the failure.

7. The method according to claim 1, characterized in that, The received user-uploaded substation configuration description file includes: The system receives substation configuration description files uploaded by users through the front-end page of the intelligent substation configuration file management system. The substation configuration description files include a single substation configuration description file or a compressed package of substation configuration description files.

8. A verification device for a substation configuration description file, characterized in that, include: The receiving module is used to receive the substation configuration description file to be verified uploaded by the user and trigger the verification process; The parsing module is used to parse the substation configuration description file and extract configuration information; The first extraction module is used to extract features from the parsed configuration information to obtain structured feature data; The second extraction module is used to perform entity recognition and relationship extraction on the structured feature data to obtain entity and relationship data related to virtual terminal circuits. The construction module is used to construct a knowledge graph based on the entity and the relationship data between entities, and to automatically verify the integrity and configuration consistency of the virtual terminal circuits of the substation configuration description file in combination with preset verification rules, so as to obtain the verification results. The output module is used to output the verification results in a visual form.

9. An electronic device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the method as claimed in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which is loaded by a processor to perform the steps of the method according to any one of claims 1 to 7.

Images