Standardized download and rollback method and system for relay protection device configuration files based on SCD analysis

Abstract

The present invention discloses a standardized downloading and rollback method and system for relay protection device configuration files based on SCD parsing, which relates to the field of communication technology and includes the following steps: obtaining and parsing the file of the target substation, extracting the first data of the target relay protection device from the parsed file, wherein the first data includes logical devices, logical nodes, communication parameters and configuration information; semantically mapping the first data with the configuration template preset by the relay protection device manufacturer to generate an initial configuration file; downloading the initial configuration file to the target relay protection device, and obtaining a configuration rollback anchor point; obtaining the configuration application data returned by the relay protection device, and executing the rollback operation of the configuration file in combination with the configuration rollback anchor point; the present application solves the problems of large configuration differences among devices of multiple manufacturers, low deployment efficiency and complex fault rollback by constructing a semantic knowledge graph, nested parsing of SCD files and establishing a configuration rollback anchor point mechanism.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and more particularly to a method and system for standardized downloading and rollback of a relay protection device configuration file based on SCD analysis. Background Art

[0002] As the digitalization and intelligence of power systems continue to improve, the accuracy and standardization of configuration files for relay protection devices, key equipment for the safe and stable operation of power grids, play a decisive role in relay protection logic execution, communication interaction, and fault handling. Especially with the widespread adoption of the IEC 61850 standard, the structure of relay protection device configuration files has become increasingly complex, encompassing multiple layers of nested information such as logical devices (LDs), logical nodes (LNs), data objects (DOs), and data attributes (DAs). Furthermore, these configuration files must support cross-vendor communication protocols and adapt to multiple device models, posing numerous challenges to configuration generation, downloading, and maintenance.

[0003] Furthermore, the configuration and deployment process for relay protection devices requires consideration of key aspects such as configuration download mode selection, device capability compatibility verification, parameter validity verification, and configuration security packaging. After configuration deployment is complete, an identifiable fallback anchor point should be automatically generated to support subsequent fault handling or configuration rollback operations. In particular, in fallback scenarios, the system should be able to quickly restore to a historically stable configuration version, ensuring that the device can quickly resume normal operation after a configuration anomaly.

[0004] For example, the invention patent with announcement number CN118279086B discloses a method and system for automatically generating interval protection configuration model data from an SCD file, which relates to the field of electric power technology and includes: parsing an SCD file, obtaining device data based on the SCD file and constructing a business model; generating virtual terminal objects and virtual circuit objects according to the device model data; generating interoperability relationship objects according to the virtual circuit objects, and generating interval protection configuration objects according to the interoperability relationship objects. The present invention significantly improves relay protection professionals' understanding of SCD files and operational efficiency by parsing SCD files and constructing a business model with interval protection configuration as the core. By automatically processing SCD files, the time and error probability of manual configuration are reduced, and configuration efficiency and accuracy are improved. By converting SCD files into interval protection configuration model data, relay protection professionals can more intuitively understand the content of SCD files, facilitating review and comparison.

[0005] For example, the invention patent with announcement number: CN109509239A discloses a method for generating a secondary circuit configuration file for an on-site protection device that is free of SCD configuration. The substation system configuration file lacks technical control measures, and there is a risk of incorrect protection action caused by configuration file errors. To solve the above problems, it is necessary to establish a relay protection secondary circuit that does not rely on SCD file configuration to achieve process layer configuration-free configuration. By defining a virtual terminal connection template, the virtual terminal connection relationship between the receiving device and the sending device is maximized, and the template file does not change with the project. According to different project scenarios, it is only necessary to define the relationship file between the devices and send it to the device. The device will generate a process layer configuration file related to the project based on the pre-configured template and the connection relationship between the project download device. The management unit automatically generates the process file CRC for each device based on the device connection relationship, and compares it with the CRC sent by the device to achieve closed-loop verification.

[0006] The above disclosed technical solutions have at least the following technical problems:

[0007] Traditionally, only syntax-level verification is performed before deployment, lacking systematic verification of logical dependencies between configuration fields, device capability boundaries, and deployment risks. To address these issues, the present invention proposes a solution. Summary of the Invention

[0008] To overcome the aforementioned shortcomings of the prior art, embodiments of the present invention provide a standardized download and rollback method for relay protection device configuration files based on SCD parsing. By combining semantic mapping with rule-based reasoning, this method enables automatic configuration file generation, verification, downloading, and exception rollback, improving the standardization and reliability of configuration deployment. By constructing a semantic knowledge graph, nested parsing of SCD files, and establishing configuration rollback anchor points, the method effectively addresses issues such as large configuration differences among devices from multiple vendors, low deployment efficiency, and complex fault rollback.

[0009] To achieve the above object, the present invention provides the following technical solutions:

[0010] A standardized downloading and rollback method for relay protection device configuration files based on SCD parsing includes: obtaining and parsing a file of a target substation, extracting first data of a target relay protection device from the parsed file, wherein the first data includes logical devices, logical nodes, communication parameters, and configuration information; semantically mapping the first data with a configuration template preset by the relay protection device manufacturer to generate an initial configuration file; downloading the initial configuration file to the target relay protection device and obtaining a configuration rollback anchor point; obtaining configuration application data returned by the relay protection device, and executing a rollback operation of the configuration file in combination with the configuration rollback anchor point.

[0011] In a preferred embodiment, the acquisition and parsing of the target substation file are specifically as follows: automatically obtaining the SCD file of the target substation from the dispatching automation platform or the configuration management system, and performing an integrity check on the SCD file; parsing the SCD file, locating all IED nodes contained therein, and filtering out the corresponding IED entries according to the target relay protection device; parsing the logical device information under the IED entry, and extracting the logical nodes in each logical device; recursively parsing the data objects and data attributes contained under each logical node, constructing its hierarchical relationship structure in the data model, and extracting the attribute content; extracting the first data associated with the relay protection device according to the parsed SCD file, the first data including the logical device, logical node, communication parameters and configuration information.

[0012] In a preferred embodiment, the first data is semantically mapped with the configuration template preset by the relay protection device manufacturer to generate an initial configuration file, specifically as follows: according to the model and communication protocol of the target relay protection device, the corresponding preset configuration template is loaded; the collected first data is semantically matched with the configuration template to establish a mapping relationship between the data field and the template field; according to the mapping relationship, the fields in the configuration template are automatically filled, replaced and supplemented to generate an initial configuration template; during the mapping process, fields with missing fields or inconsistent structural granularity are identified and marked as semantically unresolved fields; based on the preset rule engine, the semantically unresolved fields are inferred and automatically completed; structural compatibility scoring and difference warning analysis are performed on the completed initial configuration file; based on the compatibility scoring and difference warning analysis results, the final configuration file is output for download and use by the target relay protection device.

[0013] In a preferred embodiment, the preset rule engine is used to infer and automatically complete the semantic fields to be parsed, specifically as follows: when the field names are inconsistent, the data fields are matched to the equivalent fields in the constructed knowledge graph based on the semantic similarity model; when there are granularity differences in the structural hierarchy, the structural reconstruction rules are called to perform granularity conversion operations; when there are multiple candidate fields in the matching results, a comprehensive score is performed based on the contextual semantic information and configuration template constraints to select the best matching field; when a manufacturer-private field is identified, the private field parsing rules are called through the semantic recognition module to complete the configuration segment.

[0014] In a preferred embodiment, the initial configuration file is downloaded to the target relay protection device and a configuration fallback anchor point is obtained, specifically as follows: establishing wired and wireless communication channels with the target relay protection device to obtain capability information of the target relay protection device; semantically matching the capability information with the content of the initial configuration file and selecting a configuration download mode; verifying the initial configuration file before the configuration is issued and obtaining security configuration instructions; transmitting the security configuration instructions in batches to the target relay protection device through the communication channel using the IEC61850 MMS protocol; after the target relay protection device parses and executes the instructions, the system extracts the configuration loading result returned by it; reading the current running configuration of the relay protection device and performing field consistency analysis with the initial configuration file; generating a configuration deployment version identifier based on the consistency analysis result and establishing a configuration fallback anchor point.

[0015] In a preferred embodiment, the verification of the initial configuration file is specifically as follows: the initial configuration file is nested parsed through the embedded IEC61850 standard parsing module; after completing the nested parsing, the activation dependencies and mutual exclusion conditions of the configuration items are verified through the pre-built relay protection configuration semantic knowledge graph; the device capability description information of the target relay protection device is obtained, the initial configuration file is matched, and it is determined whether the current configuration file exceeds the device capability boundary; when the operation is upgrade / reload, the current running configuration of the device is read and field difference comparison is performed; deployment risk data is extracted according to the difference comparison results, and the deployment risk score is calculated based on the weighted method; a unique configuration anchor point identifier is generated based on the deployment risk score.

[0016] In a preferred embodiment, the configuration application data returned by the relay protection device is obtained, and the configuration rollback anchor point is combined to perform the rollback operation of the configuration file, specifically as follows: receiving the configuration exception information returned by the target relay protection device through the communication interface; searching the deployment history database according to the exception information, and locating the rollback anchor point corresponding to the current configuration; extracting the rollback configuration file from the historical version library according to the rollback anchor point; downloading the rollback configuration file to the target relay protection device through the IEC 61850 MMS protocol; after the download is complete, reading the current running configuration of the device, and performing a field comparison with the rollback configuration file to confirm that the rollback is successful.

[0017] A system for a standardized downloading and rollback method of a relay protection device configuration file based on SCD parsing includes a parsing module, a mapping module, a downloading module and a rollback module, and there is a connection between the modules; the parsing module is used to obtain and parse the file of the target substation, and extract the first data of the target relay protection device from the parsed file, wherein the first data includes logical devices, logical nodes, communication parameters and configuration information; the mapping module is used to semantically map the first data with the configuration template preset by the relay protection device manufacturer to generate an initial configuration file; the downloading module is used to download the initial configuration file to the target relay protection device and obtain a configuration rollback anchor point; the rollback module is used to obtain the configuration application data returned by the relay protection device, and perform a rollback operation on the configuration file in combination with the configuration rollback anchor point.

[0018] The technical effects and advantages of the present invention's standardized downloading and rollback method and system for relay protection device configuration files based on SCD analysis are as follows:

[0019] 1. This method automatically acquires and parses the target substation's SCD file through a parsing module, accurately extracting the logical devices, logical nodes, communication parameters, and configuration information related to the target relay protection device. This generates a clearly structured and complete primary data set, laying the foundation for subsequent configuration generation. Compared to the traditional method of manually entering configuration data step by step, this method significantly improves the efficiency and accuracy of configuration file generation.

[0020] 2. The present invention uses a mapping module to achieve semantic mapping between the first data and the relay protection manufacturer's preset template, automatically generating an initial configuration file. During the semantic mapping process, the system utilizes a semantic similarity model, a rule engine, and a configuration knowledge graph to achieve field-level semantic reasoning, structural reconstruction, and private field completion, greatly improving the system's compatibility with heterogeneous device configuration templates and significantly reducing the probability of configuration conflicts and semantic errors. After the mapping is completed, the system also performs structural compatibility scoring and discrepancy warnings on the generated initial configuration file, further enhancing the rigor and controllability of the configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 The present invention is a flowchart of a standardized downloading and rollback method for a relay protection device configuration file based on SCD analysis.

[0022] Figure 2 This is a structural diagram of a standardized downloading and rollback system for relay protection device configuration files based on SCD analysis in the present invention. DETAILED DESCRIPTION

[0023] The following will provide a clear and complete description of the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0024] Example 1, Figure 1 The present invention provides a standardized downloading and rollback method for relay protection device configuration files based on SCD parsing, which includes the following steps:

[0025] S1, obtaining and parsing a file of a target substation, extracting first data of a target relay protection device from the parsed file, wherein the first data includes a logical device, a logical node, communication parameters and configuration information.

[0026] In this embodiment, the target substation file is obtained and parsed as follows:

[0027] The system automatically obtains the SCD file of the target substation from the dispatch automation platform or configuration management system and performs integrity checks, including: (1) verifying whether the basic format structure of the SCD file complies with the IEC 61850 standard; (2) extracting and verifying the compatibility of the namespace, version number and the deployed parser; (3) generating a file fingerprint (such as SHA256 hash value) to prevent tampering and support version traceability;

[0028] The system performs structural analysis on the SCD file through the built-in XML parsing module or IEC 61850 protocol compatible parsing tool, specifically including:

[0029] First, the system locates the SCD file <ied>Node,filters out the IED entries corresponding to the target relay protection device by matching,IED name, function description or device identification;

[0030] Then, the logical device information under the IED node is parsed, including the logical device identifier (LD name), the corresponding functional block, the primary device circuit identifier or voltage level, etc.

[0031] The system extracts multiple logical nodes (Logical Nodes) defined in each logical device, identifies the type of each logical node (such as PTOC for overcurrent protection, PDIF for differential protection, etc.), instance number (LN instance number) and its functional description;

[0032] Finally, the data objects (DOs) and their data attributes (DAs) contained in each logical node are read and their hierarchical relationships and attribute contents in the data model are analyzed to provide basic data support for subsequent parameter comparison and configuration item mapping.

[0033] First data associated with the relay protection device is obtained according to the parsed SCD file, where the first data includes a logical device, a logical node, communication parameters, and configuration information.

[0034] S2: semantically map the first data with a configuration template preset by the relay protection device manufacturer to generate an initial configuration file.

[0035] In this embodiment, semantic mapping is performed between the first data and the configuration template preset by the relay protection device manufacturer to generate an initial configuration file, as follows:

[0036] The system loads the configuration template preset by the corresponding manufacturer based on the model and communication protocol of the target relay protection device. The template is an ICD, CID or manufacturer-customized format file containing structural definitions such as logical devices, logical nodes, and communication parameters;

[0037] Semantic matching is performed between the first data and the manufacturer template. The matching rules are as follows:

[0038] For logical devices (LD), they are mapped to the device segments in the template based on the device identifier, functional domain, and voltage level;

[0039] For logical nodes (LN), fill in the corresponding sections of the template based on the type identifier (such as PTOC, PDIF) and instance number;

[0040] For communication parameters (such as AP, IP, MAC, etc.), compare the network structure and fill them into the communication structure;

[0041] For configuration information (such as GOOSE, report blocks, and datasets), fill in the corresponding fields according to the field names and data model levels;

[0042] Semantically map the content after semantic matching, such as matching logical devices with device segments in the template, mapping logical nodes to the template LN structure based on their types and instance numbers, mapping communication parameters to the template communication topology fields, and mapping the configuration information (such as data sets, report control blocks, and GOOSE control blocks) structures and filling in corresponding fields;

[0043] Based on the mapping relationship, the relevant fields in the manufacturer template are automatically filled, replaced, or supplemented to generate the initial configuration template. In cases where the fields can be directly mapped, the system prioritizes one-to-one mapping for automatic filling. If there are missing fields or inconsistent structure granularity, they are recorded as "semantic unresolved fields" and temporarily stored for further processing.

[0044] Based on the rule engine, the system infers and automatically completes the semantically unresolved fields. Through this inference mechanism, the system can expand the traditional method of supporting only standard field mapping to an intelligent configuration matching method with cross-vendor and unstructured data adaptability. Specifically, it includes:

[0045] If the field names are inconsistent, the system calls the semantic similarity model to perform similarity matching between the field to be parsed and the known fields in the semantic knowledge graph, thereby identifying equivalent or similar fields and achieving unified mapping of field names;

[0046] If there are granularity differences in the structural hierarchy, the predefined structural reconstruction rule library is called to achieve granularity conversion and hierarchical reorganization through rule-driven implementation to ensure consistency of fields at the structural level;

[0047] If there are multiple candidate fields in the matching result, a comprehensive score is performed based on the contextual semantic information and configuration template constraints to select the best matching field;

[0048] If it is a manufacturer-private field, the semantic recognition module automatically identifies the manufacturer to which the field belongs and calls the corresponding private field parsing rules to complete the parsing and completion of the specific configuration segment;

[0049] After completing the configuration file filling and semantic completion process, the system further performs structural compatibility scoring and difference warning analysis on the generated initial configuration file to ensure the correctness of the configuration results and the feasibility of deployment. Specifically, it includes:

[0050] Calculate the field mapping completeness score (actual number of matching fields / total number of fields that should be configured);

[0051] Check the integrity of the control block (whether there are isolated or disconnected items in the report block, data set, GOOSE link, etc.);

[0052] Compare the communication topology with the original SCD file to see if it is consistent, and detect whether there is any communication disconnection or redundant configuration;

[0053] If the score is lower than the system-set threshold (e.g., 85%), the system will automatically generate a structural difference analysis report, marking key difference fields and their potential impacts for review by operations personnel or automatic system repair.

[0054] After completing semantic reasoning and structural consistency assessment, the system outputs the final configuration content as a configuration file that complies with the specifications of the target relay protection device manufacturer. The configuration file can be in CID, ICD, or other compatible formats, and is accompanied by a summary information file, including: the number of logical nodes, the number of control blocks, communication port configuration, configuration mapping log, etc., for manual review and archiving.

[0055] Furthermore, through the above steps, the present invention realizes the process from SCD structure extraction, basic template mapping, and then to semantic graph-driven intelligent completion, and finally forms a standardized and highly compatible configuration file. It breaks through the problems of manual adaptation, format restrictions and cross-vendor migration difficulties in existing methods, and has a significant degree of automation and engineering application value.

[0056] The difference early warning analysis formula is as follows:

[0057]

[0058] Where: It is a difference early warning indicator. is the number of structurally incompatible fields, A field that was not successfully semantically mapped or completed.

[0059] S3: Download the initial configuration file to the target relay protection device and obtain the configuration rollback anchor point.

[0060] In this embodiment, the initial configuration file is downloaded to the target relay protection device, and the configuration fallback anchor point is obtained, as follows:

[0061] Establish a wired or wireless communication channel with the target relay protection device and obtain device capability information, including model identification, firmware version, supported function modules, control block capacity, and current configuration status, through IEC 61850 MMS service or manufacturer-specific protocol;

[0062] Semantically match device capability information with the content of the initial configuration file to be deployed, and automatically select the appropriate configuration download mode. The download modes include but are not limited to full download, incremental update, or function segmented loading. This matching process ensures that the configuration file structure is highly compatible with the device's supported capabilities, avoiding loading failures.

[0063] Before the configuration is issued, the system verifies the initial configuration file, including field integrity, structural consistency, and logical conflict detection. It also calculates the configuration summary information and generates a digital signature. The system encapsulates the configuration file together with the version identifier, verification summary, and unique token to form a secure configuration instruction.

[0064] Through the established communication channel, the IEC 61850 MMS protocol or the manufacturer's proprietary protocol is used to transmit the encapsulated configuration instructions in batches to the target relay protection device. During the process, the system monitors the status of the instructions in real time, including data frame integrity, transmission rate, abnormal response, etc., and supports breakpoint resumption and abnormal retry mechanisms.

[0065] After receiving the configuration, the target device performs local parsing and parameter loading operations. The system extracts the configuration loading results from the data returned by the device, including key information such as logical node activation status, control block configuration results, report enablement status, and configuration version number;

[0066] The system reads the currently activated actual running configuration from the target device through standard read commands or a protocol parser, compares the obtained running status with the initial configuration file, performs field-level consistency analysis, evaluates the loading effect, identifies discrepant fields or ineffective parameters, and generates a difference analysis list and configuration consistency score.

[0067] Based on the consistency comparison results, the detailed data of this configuration process is archived, including the target device identification, configuration content, deployment time, loading results and comparison report. The configuration deployment version identification is generated simultaneously, and a configuration rollback anchor point is established to support subsequent abnormal recovery or version rollback operations.

[0068] The configuration consistency scoring formula is as follows:

[0069]

[0070] Where: The closer the score is to 1, the more consistent the actual running configuration is with the expected configuration. is the number of fields with inconsistent values, is the number of fields that were not loaded or failed to parse. is the number of inactive logical nodes or function blocks, is the total number of fields in the initial configuration file.

[0071] In this embodiment, the system verifies the initial configuration file as follows:

[0072] The system is based on an embedded IEC 61850 standard parsing module, which reads the initial configuration file structure and performs the following two-level nested parsing:

[0073] Level 1: Identify and verify the integrity of the structural levels such as IED, logical device (LD), logical node (LN);

[0074] Level 2: Verify the syntax validity and value range of the data object (DO) and data attribute (DA) under each logical node to ensure consistency in structure and field dimensions.

[0075] After completing the basic structure analysis, the pre-built semantic knowledge graph of relay protection configuration is used to identify the associated logic, activation dependencies, and mutual exclusion conditions between configuration fields, and determine whether there are logical mismatches or illegal combinations. For example, it can determine whether the necessary event trigger mechanism is missing when a functional LN node is activated; analyze whether there are coordination time logic conflicts between multiple protection components; and automatically identify the risk of functional mapping failure caused by manufacturer differences.

[0076] Obtain the device capability description of the target relay protection device (such as supported LN types, maximum configuration block length, supported protocol types, etc.) and match it one-to-one with the initial configuration file to determine whether the current configuration exceeds the device capability boundary. If incompatibility is found, the system will provide compatibility prompts and recommend configuration adjustments or switching deployment strategies.

[0077] If the current configuration is an upgrade deployment or reload operation, the system reads the device's current running configuration version and compares the field differences with the initial configuration file. The specific operations are: generating a difference mapping table for newly added, changed, and deleted fields; marking the field path and change type; and initiating a compatibility impact analysis for key field changes.

[0078] Deployment risk data is obtained based on the field difference comparison. The deployment risk data includes field completeness, structure matching, logical conflict factor, and historical deployment success rate. A deployment risk score is output based on the deployment risk data using a weighted method.

[0079] Based on the deployment risk score, the system generates a unique configuration anchor identifier and performs pre-deployment simulation rollback testing to verify the feasibility and stability of configuration loading.

[0080] S4: Obtain the configuration application data sent back by the relay protection device, and perform the rollback operation of the configuration file in combination with the configuration rollback anchor point.

[0081] In this embodiment, the configuration application data returned by the relay protection device is obtained, and the configuration rollback anchor point is combined to perform the rollback operation of the configuration file, as follows:

[0082] The system receives configuration application data sent back by the target relay protection device through the communication interface. The data includes the current configuration version number, configuration loading status, activation field information and abnormal alarm information;

[0083] Based on the returned exception information, the system calls the deployment history database to retrieve the fallback anchor point and historical configuration versions corresponding to the current configuration;

[0084] According to the selected fallback anchor point, extract the corresponding fallback configuration file from the historical version library;

[0085] Download the fallback configuration file to the target relay protection device via the IEC 61850 MMS protocol or the manufacturer's proprietary communication protocol;

[0086] After the download is complete, the system reads the current running configuration from the device and performs a field-level comparison with the rollback configuration file to confirm whether the configuration has been successfully rolled back. If the rollback is successful, the system updates the configuration version information, generates a rollback log and event record, and archives the rollback process. If the rollback fails, the system triggers the exception handling mechanism, notifies the operation and maintenance personnel, and recommends manual intervention.

[0087] Example 2, Figure 2 The present invention provides a system for standardized downloading and rollback of relay protection device configuration files based on SCD parsing, which is characterized by comprising a parsing module, a mapping module, a downloading module and a rollback module, and there are connections between the modules;

[0088] a parsing module, configured to obtain and parse a file of a target substation, and extract first data of a target relay protection device from the parsed file, wherein the first data includes a logical device, a logical node, communication parameters, and configuration information;

[0089] A mapping module, configured to perform semantic mapping between the first data and a configuration template preset by the relay protection device manufacturer to generate an initial configuration file;

[0090] The download module is used to download the initial configuration file to the target relay protection device and obtain the configuration rollback anchor point;

[0091] The rollback module is used to obtain the configuration application data sent back by the relay protection device and perform the rollback operation of the configuration file in combination with the configuration rollback anchor point.

[0092] The above formulas are all dimensionless and numerical calculations. The formulas are obtained by collecting a large amount of data and performing software simulation to obtain the most recent real situation. The preset parameters in the formulas are set by technicians in this field according to actual conditions.

[0093] The above embodiments may be implemented in whole or in part through software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product.

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

[0095] In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0096] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0097] Finally: The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.< / ied>

Claims

1. A standardized download and rollback method for relay protection device configuration files based on SCD analysis, characterized in that: include: Obtaining and parsing a file of a target substation, and extracting first data of a target relay protection device from the parsed file, wherein the first data includes a logical device, a logical node, communication parameters, and configuration information; Performing semantic mapping on the first data and a configuration template preset by the relay protection device manufacturer to generate an initial configuration file; Download the initial configuration file to the target relay protection device and obtain the configuration rollback anchor point; Obtain the configuration application data sent back by the relay protection device, and perform the rollback operation of the configuration file in combination with the configuration rollback anchor point; Download the initial configuration file to the target relay protection device and obtain the configuration rollback anchor point, specifically: Establish wired and wireless communication channels with the target relay protection device to obtain the capability information of the target relay protection device; Semantically match the capability information with the initial configuration file content and select the configuration download mode; Verify the initial configuration file before sending it down and obtain security configuration instructions; Transmit safety configuration instructions to the target relay protection device in batches using the IEC 61850 MMS protocol through the communication channel; After the target relay protection device parses and executes the instruction, the system extracts the configuration loading result returned by it; Read the current running configuration of the relay protection device and perform field consistency analysis with the initial configuration file; Generate a configuration deployment version identifier based on the consistency analysis results and establish a configuration rollback anchor point.

2. The standardized downloading and rollback method for relay protection device configuration files based on SCD analysis according to claim 1 is characterized in that: The details of obtaining and parsing the target substation file are as follows: Automatically obtain the SCD file of the target substation from the dispatch automation platform or configuration management system and perform integrity check on the SCD file; Parse the SCD file, locate all IED nodes contained therein, and filter out the corresponding IED entries according to the target relay protection device; Parse the logical device information under the IED entry and extract the logical nodes in each logical device; Recursively parse the data objects and data attributes contained in each logical node, build their hierarchical relationship structure in the data model, and extract the attribute content; First data associated with the relay protection device is extracted according to the parsed SCD file, where the first data includes logical devices, logical nodes, communication parameters, and configuration information.

3. The standardized downloading and rollback method for relay protection device configuration files based on SCD analysis according to claim 2 is characterized in that: The semantic mapping of the first data with the configuration template preset by the relay protection device manufacturer to generate an initial configuration file is as follows: Load the corresponding preset configuration template according to the model and communication protocol of the target relay protection device; Perform semantic matching on the collected first data and the configuration template, and establish a mapping relationship between the data field and the template field; Automatically fill, replace, and supplement fields in the configuration template based on the mapping relationship to generate an initial configuration template; During the mapping process, fields with missing fields or inconsistent structural granularity are identified and marked as fields to be semantically resolved. Reasoning and automatic completion of semantically resolved fields based on a preset rule engine; Perform structural compatibility scoring and difference warning analysis on the completed initial configuration file; Based on the compatibility score and difference warning analysis results, the final configuration file is output for downloading and use in the target relay protection device.

4. The standardized downloading and rollback method for relay protection device configuration files based on SCD analysis according to claim 3 is characterized in that: The preset rule engine is used to infer and automatically complete the semantic fields to be parsed, as follows: When field names are inconsistent, the data fields are matched to equivalent fields in the knowledge graph based on the semantic similarity model; When there are granularity differences in the structural hierarchy, the structural reconstruction rules are called to perform granularity conversion operations; When there are multiple candidate fields in the matching result, a comprehensive score is performed based on the contextual semantic information and the configuration template constraints to select the best matching field; When a manufacturer's private field is identified, the semantic recognition module calls the private field parsing rules to complete the configuration segment.

5. The standardized downloading and rollback method for relay protection device configuration files based on SCD analysis according to claim 1 is characterized in that: The verification of the initial configuration file is as follows: Through the embedded IEC 61850 standard parsing module, the initial configuration file is nested and parsed; After nested parsing is completed, the pre-built semantic knowledge graph of relay protection configuration is used to verify the activation dependencies and mutual exclusion conditions of the configuration items. Obtain the device capability description information of the target relay protection device, match the initial configuration file, and determine whether the current configuration file exceeds the device capability boundary; When the operation is upgrade / reload, the device's current running configuration is read and a field difference comparison is performed; Extract deployment risk data based on the difference comparison results and calculate the deployment risk score based on a weighted method; Generates a unique configuration anchor ID based on the deployment risk score.

6. The standardized downloading and rollback method for relay protection device configuration files based on SCD analysis according to claim 1 is characterized in that: The configuration application data returned by the relay protection device is obtained, and the configuration rollback anchor point is combined to perform the rollback operation of the configuration file, as follows: Receive configuration abnormality information sent back by the target relay protection device through the communication interface; Search the deployment history database based on exception information and locate the fallback anchor point corresponding to the current configuration; Extract the fallback configuration file from the historical version library based on the fallback anchor; Download the fallback configuration file to the target relay protection device via the IEC 61850 MMS protocol; After the download is complete, the device's current running configuration is read and compared against the rollback configuration file to confirm that the rollback was successful.

7. A system using the standardized downloading and rollback method for relay protection device configuration files based on SCD analysis as described in any one of claims 1 to 6, characterized in that: It includes parsing module, mapping module, download module and fallback module, and there are connections between modules; a parsing module, configured to obtain and parse a file of a target substation, and extract first data of a target relay protection device from the parsed file, wherein the first data includes a logical device, a logical node, communication parameters, and configuration information; A mapping module, configured to perform semantic mapping between the first data and a configuration template preset by the relay protection device manufacturer to generate an initial configuration file; The download module is used to download the initial configuration file to the target relay protection device and obtain the configuration rollback anchor point; The rollback module is used to obtain the configuration application data sent back by the relay protection device and perform the rollback operation of the configuration file in combination with the configuration rollback anchor point.

Images