Automatic acquisition and verification method of SCCD model in grid-connected implementation process

Abstract

The invention belongs to the technical field of digital substations of electric power systems, and particularly relates to an automatic acquisition and checking method for an SCCD model in a grid-connected implementation process, which comprises the following steps of: constructing an integrated technical system of multi-source acquisition, difference comparison, format conversion and automatic filing; the stock device analyzes SSH / SNMP / API protocol data by configuring a translation conversion tool; checking the acquired data and the SCCD model constant value by adopting a constant value comparison and intention comparison two-dimensional mechanism; converting the non-standard data into an IEC61850 XML format through a configurable mapping grammar; and generating and filing an SCCD-plus model file after the check is passed, thereby providing support for grid-connected auditing, operation and maintenance of the transformer substation.

Description

Technical Field

[0001] This invention belongs to the field of digital substation technology in power systems, specifically a method for automatic acquisition and verification of SCCD models during grid connection implementation. Background Technology

[0002] With the digital transformation of power systems, digital substations have become a core direction in power grid construction. The accuracy and consistency of secondary system equipment information during the grid connection phase are crucial for ensuring power grid safety and operational stability. Currently, the industry has completed structured modeling of substation equipment based on the IEC 61850 standard, constructing a unified digital model benchmark through SCD files, and using this model to drive the forward management of grid connection safety. However, in practical applications, three major bottlenecks remain:

[0003] First, there is fragmentation in equipment configuration and protocols. Substations contain both old and new equipment. Existing equipment (traditional switches, firewalls, etc.) relies on non-standard protocols such as SSH and SNMP, and the configuration formats are customized by the manufacturers. Although new equipment (new generation switches, firewalls) supports the IEC61850MMS protocol, the power grid is still in the transition period of protocol promotion, resulting in a lack of a unified channel for collecting configuration information.

[0004] Second, manual comparison is inefficient and prone to errors. The comparison between on-site configuration and SCCD model baseline values ​​relies on manual labor. For key items such as network topology, VLAN configuration, and security policies, manual verification is not only time-consuming, but also prone to omissions or misjudgments due to the complexity of the configuration, making it difficult to meet the timeliness and accuracy requirements of forward control.

[0005] Third, model staticization and format conversion are difficult. The early SCCD model was a static benchmark, which could not be automatically aligned with the dynamic configuration on site; moreover, the collected data (such as SSH return paragraphs and SNMP tables) are in heterogeneous formats, and the existing conversion methods are not flexible enough to match the XML format required by SCCD, resulting in the model being unable to support grid connection compliance judgment and subsequent operation and maintenance.

[0006] In summary, the lack of existing technologies in SCCD model management solutions that support multi-protocol adaptation, automated verification, and flexible format conversion has become a key issue hindering the forward shift of grid connection control and the refined operation and maintenance of digital substations. Summary of the Invention

[0007] To overcome the shortcomings of existing technologies and solve the aforementioned technical problems, this invention proposes an automatic acquisition and verification method for SCCD models during grid connection implementation.

[0008] The technical solution adopted by this invention to solve its technical problem is as follows: This invention proposes an automatic acquisition and verification method for SCCD models during grid connection implementation, including the following steps:

[0009] Includes the following steps:

[0010] S1: Construct an automatic data acquisition and model verification technology system based on standard communication protocols and configuration parsing mechanisms. The technology system supports multi-source protocol adaptation, multi-type device compatibility, structured data comparison, and automatic archiving.

[0011] S2: Acquire the operational configuration information of all equipment in the station through multi-source acquisition;

[0012] S3: Compare and verify the differences between the operation configuration information collected in S2 and the baseline values ​​in the SCCD model of the power plant grid connection scheme;

[0013] S4: After verification, the SCCD-plus model file is automatically archived. The SCCD-plus model file serves as a reliable data foundation for subsequent grid connection review, model distribution, and operation and maintenance support.

[0014] Furthermore, the multi-source acquisition method includes acquisition for incremental devices and acquisition for existing devices:

[0015] For incremental equipment, the IEC61850MMS communication protocol is used to directly read the equipment operation configuration information.

[0016] For existing devices, a configuration translation and conversion tool is used to collect and parse the device's operating configuration information. This configuration translation and conversion tool supports the parsing of raw configuration information for multiple communication protocols.

[0017] Furthermore, the parsing process of the configuration translation conversion tool includes:

[0018] The original configuration information of the existing equipment is extracted from diverse and heterogeneous sources. The original configuration information is then converted into a standardized data format using a normalization technique. This standardized data format is used for subsequent comparison with the baseline of the SCCD model.

[0019] Furthermore, the difference comparison adopts a two-dimensional verification mechanism of fixed value comparison plus intention comparison:

[0020] The value comparison is performed on a field-by-field basis, and the collected operation configuration information is matched one-to-one with the set values ​​in the SCCD model to verify the consistency at the field level.

[0021] The intent comparison is used to identify the consistency between the policy objective and the actual protection intent, and to determine the rationality and coverage completeness of the policy configuration.

[0022] Furthermore, the intent comparison employs a comparison algorithm based on the Cartesian product of 5-tuples, the algorithm comprising:

[0023] The fixed value rules in the SCCD model and the configuration rules for field acquisition are both abstracted into a five-tuple structure;

[0024] By calculating the Cartesian product of the set and iteratively finding the remainder set, it can be determined whether the configuration rules collected on-site completely cover the fixed value rules in the SCCD model and whether there is an issue of excessively wide range.

[0025] Furthermore, it also includes a data format conversion step:

[0026] The flexibly configurable mapping configuration syntax converts non-standard format data collected from multiple sources into XML format data that conforms to the IEC61850 standard. The mapping configuration syntax supports user-defined correspondence between data source fields and target fields.

[0027] Furthermore, the mapping configuration syntax includes a mapping addressing statement, which starts from the top-level array of the original collected data and locates the target data object through the hierarchical structure of "field.field";

[0028] Array type fields support two positioning methods: one is to filter array elements that meet the requirements by using "$+attribute filter conditions", and the other is to specify the array elements to be matched by using "#subscript or subscript range".

[0029] Furthermore, the mapping configuration syntax includes mapping output statements. These statements start with the IED name in the SCCD file and follow a hierarchical structure of "IED → Logical Device → Logical Node → Data Object → Data Attribute". The logical device corresponds to LD, the logical node corresponds to LN, the data object corresponds to DO, and the data attribute corresponds to DA. This accurately maps the converted standardized data to the corresponding position in the SCCD file.

[0030] Furthermore, the SCCD-plus model file shall contain at least the following:

[0031] Comparison between the collected equipment operation configuration information and the original modeling values ​​of the SCCD model;

[0032] The structured information of the difference comparison results includes at least one of the following: comparison result type, configuration incomplete range, redundancy strategy identifier, and configuration correction suggestion.

[0033] Furthermore, the five-tuple structure includes a source address set, a destination address set, a protocol type, a source port set, and a destination port set. The source address set and the destination address set can be a single IP address or a CIDR network segment. The protocol type includes TCP or UDP. The source port set and the destination port set can be a single port or a range of ports.

[0034] The beneficial effects of this invention are as follows:

[0035] 1. The automatic acquisition and verification method of SCCD model during grid connection implementation described in this invention solves the problems of fragmented equipment configuration acquisition and high error rate of manual verification by adopting a multi-source acquisition strategy (covering the IEC61850MMS protocol for incremental equipment and the SSH / SNMP / RESTfulAPI protocol for existing equipment) and a two-dimensional verification mechanism of "set value comparison + intent comparison". This not only improves the equipment configuration acquisition efficiency by more than 50% compared with the traditional manual method and is compatible with more than 80 different manufacturers and models of equipment, but also improves the model verification accuracy to more than 99%, effectively supporting the judgment of grid connection compliance.

[0036] 2. The automatic acquisition and verification method of SCCD model during grid connection implementation described in this invention automatically aligns the acquired data with the SCCD model and dynamically archives the verification results to form an SCCD-plus model file. This breaks down the disconnect between the static model and the dynamic configuration on site, realizes the evolution of the SCCD model from static modeling to dynamic and reliable management, provides real-time model support reflecting the on-site configuration status for the entire life cycle operation and maintenance of substation equipment, and optimizes the efficiency of operation and maintenance decision-making.

[0037] 3. The automatic acquisition and verification method of SCCD model during grid connection implementation described in this invention, through a flexibly configurable mapping configuration syntax (supporting custom data mapping rules), can complete the conversion of non-standard data to IEC61850 standard XML format without hard-coding development, adapting to the mixed equipment environment during the transition period of the IEC61850 protocol promotion in the power grid, significantly reducing the cost of later system upgrades and expansions, while ensuring the structured compatibility of data and SCCD model. Attached Figure Description

[0038] The invention will now be further described with reference to the accompanying drawings.

[0039] Figure 1 This is a system block diagram of the automatic acquisition and verification of the SCCD model of this invention. Detailed Implementation

[0040] The following will describe the embodiments of the present invention and the appendix. Figure 1 As shown, the technical solutions in the embodiments of the present invention are clearly and completely described. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0041] Example 1: This invention constructs an integrated SCCD model automatic acquisition and verification technology system that combines "multi-source acquisition - difference comparison - format conversion - automatic archiving". The specific technical solution is detailed below:

[0042] Overall technical system architecture:

[0043] The technology system takes the SCCD model as the core benchmark and integrates multi-source acquisition modules, difference comparison modules, data format conversion modules, and automatic archiving modules. It supports multi-source protocol adaptation (including IEC61850MMS, SSH, SNMP, RESTfulAPI, etc.), compatibility with multiple types of devices (incremental and existing devices), structured data comparison, and automatic archiving of verification results. It forms a complete technology chain from device configuration acquisition and data processing to dynamic model updates, providing architectural support for the reliable management of the SCCD model.

[0044] The multi-source device is configured with an acquisition module:

[0045] To address the differences in technical characteristics between incremental and existing equipment in substations, a differentiated data acquisition strategy is adopted to achieve complete acquisition of configuration information for all types of equipment.

[0046] Incremental device data acquisition: For incremental devices such as new-generation switches and new-generation firewalls that have IEC61850MMS communication capabilities, the device operation configuration information is directly read through the IEC61850MMS communication protocol, covering interface configuration, message control block, security domain attributes, VLAN configuration, mirroring configuration, Syslog configuration, etc., to achieve direct correspondence between the acquired data and SCCD model structure fields;

[0047] Existing Equipment Data Acquisition: For existing equipment such as switches, firewalls, security systems, and station control layer hosts, a configuration translation and conversion tool is used to collect and parse the equipment's operational configuration information. This tool supports multiple communication protocols such as SSH, SNMP, and RESTful API, and can extract diverse and heterogeneous raw configuration information (including formats such as regularized tables, segmented paragraphs, and tree structures) from the devices, including VLAN tables, policy rules, tunnel configurations, NAT rules, IP addresses, MAC tables, and ARP tables. Furthermore, through normalization technology, the raw configuration information is uniformly converted into a standardized data format, providing a unified data foundation for subsequent comparison with the SCCD model baseline.

[0048] SCCD model vs. on-site configuration comparison module:

[0049] A two-dimensional verification mechanism of "fixed value comparison + intent comparison" is adopted to achieve automated and high-precision difference comparison between the collected data and the baseline of the SCCD model:

[0050] Value comparison: Based on fields, a comparison mapping table is built for key fields such as IP address, port, policy ID, priority, and target address. The collected standardized data is checked against the set values ​​in the SCCD model item by item to verify the consistency at the field level and to identify any missing configuration information.

[0051] Intent Comparison: Based on the Cartesian product comparison algorithm of quintuples, both the fixed-value rules in the SCCD model and the configuration rules collected on-site are abstracted into quintuples containing source address set, destination address set, protocol type, source port set, and destination port set (where the source address set and destination address set can be in the form of a single IP address or CIDR network segment, the protocol type includes TCP protocol or UDP protocol, and the source port set and destination port set can be in the form of a single port or port range). Through the Cartesian product calculation of the sets and the iterative modulo operation, it is determined whether the configuration rules collected on-site completely cover the fixed-value rules in the SCCD model and do not have the problem of excessively wide range. In this way, the consistency between the policy objective and the actual protection intent is identified, and the rationality and coverage completeness of the policy configuration are judged.

[0052] Module for converting non-standard data to IEC61850 standard format:

[0053] Through a flexible configurable mapping syntax, non-standard format data (such as JSON format) acquired from multiple sources can be converted into XML format data conforming to the IEC61850 standard, ensuring the structured adaptation of the data to the SCCD model.

[0054] Mapping addressing statement: Starting from the top-level array of the original collected data, the target data object is located through the hierarchical structure of "field.field"; for array type fields, two positioning methods are supported: one is to filter array elements that meet the requirements by "$ + attribute filter conditions", and the other is to specify the array elements to be matched by "# index or index range", so as to achieve accurate positioning of diverse and heterogeneous collected data;

[0055] Mapping output statement: Starting from the IED name in the SCCD file, following the hierarchical structure of "IED → Logical Device → Logical Node → Data Object → Data Attribute", the non-standard data located is accurately mapped to the corresponding position in the SCCD file, ensuring that the converted data conforms to the SCL language specification specified by the IEC61850 standard and meets the structured data requirements of the SCCD model.

[0056] Automatic archiving module for verification results:

[0057] When the difference comparison results meet the preset verification requirements, the SCCD-plus model file is automatically archived. This file contains at least two core pieces of information: first, the comparison relationship between the collected equipment operation configuration information and the original modeling values ​​of the SCCD model; second, the structured information of the difference comparison results, including at least one of the following: comparison result type, configuration incompleteness range, redundancy strategy identifier, and configuration correction suggestions. The SCCD-plus model file serves as a reliable data basis for subsequent substation grid connection review, SCCD model distribution, and equipment operation and maintenance support, realizing dynamic updates and reliable management of the SCCD model throughout its entire lifecycle.

[0058] Example 2: The following detailed explanation of the SCCD model automatic acquisition and verification technology solution of this invention, based on a 220kV digital substation grid connection implementation scenario (including 32 devices, of which 8 are incremental devices and 24 are existing devices) and related technical principles, ensures that personnel in the relevant technical field can fully reproduce the technical process. In this scenario, the SCCD model is built based on the IEC61850 standard, covering core baseline settings such as network topology, VLAN configuration, and security policies. The incremental devices include 4 Huawei next-generation switches and 4 Neusoft next-generation firewalls. The existing devices include 6 H3C traditional switches, 4 Huawei traditional firewalls, 8 vertical security devices, and 6 station control layer hosts.

[0059] The hardware environment configuration is as follows:

[0060] Data Acquisition Server: Deployed at the substation control layer, equipped with a high-performance processor, large-capacity memory and storage, and featuring a dual network card design—one connecting to the incremental device network segment (192.168.10.0 / 24), and the other connecting to the existing device network segment (192.168.20.0 / 24), ensuring communication bandwidth and stability when multiple devices acquire data in parallel;

[0061] Data storage equipment: A professional database server is used to store four types of core data: original equipment configuration information, standardized data, original SCCD model files, and finally archived SCCD-plus files. Data redundancy backup is supported to ensure security.

[0062] Equipment communication links: Incremental devices are connected to the acquisition server via fiber optic Ethernet, supporting IEC61850MMS protocol communication (using standard ports); existing devices are connected via twisted-pair Ethernet, where switches and firewalls support SSH and SNMP protocol communication, the security device supports API interface communication, and the station control layer host supports SSH communication and local configuration file reading.

[0063] The software environment configuration is as follows:

[0064] Multi-source acquisition module: integrates two types of acquisition components—one is the IEC61850MMS acquisition component, used for incremental device configuration reading; the other is a configuration translation and conversion tool with built-in SSH, SNMP, and API protocol adaptation functions, which can read multi-format configuration data of existing devices;

[0065] Difference comparison module: includes a field-level comparison engine and a strategy intent comparison engine, supports custom comparison rules, and can realize two-dimensional verification of "fixed value comparison + intent comparison";

[0066] Data format conversion module: integrates mapping configuration parsing function, supports users to write mapping rules in a standardized format, and can convert non-standard data into XML format that conforms to IEC61850 standard;

[0067] Automatic archiving module: It has the function of generating SCCD-plus model files, which can integrate the collected data, comparison results and the original SCCD model, and output archived files that conform to the IEC61850 standard.

[0068] The specific implementation steps include the following:

[0069] The implementation of multi-source device configuration and data acquisition includes:

[0070] Incremental device data acquisition:

[0071] Protocol connection establishment: The acquisition server establishes communication with the switch via the IEC61850MMS protocol, and configures key parameters: the switch management IP is 192.168.10.10, the communication identifier is set to "SW_INC_001", and the timeout is set to 30 seconds to ensure connection stability;

[0072] Configuration information reading: Through the standard service of IEC61850MMS, the core configuration information of the switch is read, including network link configuration: read the VLAN ID, bound port, and VLAN IP address of the logical node "ZVLN" under the logical device "LINK"; and security policy configuration: read the rule ID, source IP set, and destination port set of the logical node "ZACL" under the logical device "SEC / ACL".

[0073] Data standardization processing: The read configuration information is converted into a unified standardized format, which includes device name, device identifier, information category (such as "network / link" and "security policy"), specific configuration items (such as VLAN table and ACL rule table) and collection time, to ensure data consistency during subsequent comparisons.

[0074] The collection of existing equipment data includes the following:

[0075] Multi-protocol data acquisition:

[0076] Using the SNMP protocol: Obtain the MAC address and port binding relationship, and the VLAN and port mapping relationship of the switch;

[0077] Using the SSH protocol: Execute the device configuration query command to obtain the VLAN configuration block text data (including VLAN ID, VLAN type, description information, bound ports, etc.);

[0078] Multi-dimensional data parsing: By configuring the paradigmatic function of the translation and conversion tool, the chunked text data obtained by SSH is parsed—extracting key information such as VLAN ID, description, and bound port, while integrating the mapping relationship data obtained by SNMP;

[0079] Unified data format: The parsed existing device configuration information is converted into a standardized format consistent with the data collected by incremental devices, eliminating data format differences caused by different protocols and device types.

[0080] The comparison between the SCCD model and the on-site configuration is implemented as follows:

[0081] Comparison of fixed values ​​(using IP address and VLAN ID as examples):

[0082] Comparison rule definition: Based on the baseline of the SCCD model, establish a key field comparison mapping table, and clarify the comparison fields (such as switch management IP, VLAN ID), the fixed values ​​in the SCCD model, the reading path of the collected data and the comparison standards (such as the IP address must be completely consistent and the VLAN ID must contain all the fixed values ​​in the model).

[0083] The automated comparison is performed as follows:

[0084] Data acquisition and reading: Extract the actual values ​​of the fields to be compared from the standardized data (e.g., the management IP of a switch is 192.168.10.11, and the VLAN ID is 10 and 20);

[0085] Model setting value reading: Extract the setting values ​​of the corresponding fields from the SCCD model (e.g., management IP is 192.168.10.10, VLAN ID is 10, 20, 30);

[0086] Difference Identifier: If the actual value is inconsistent with the set value (such as a difference in management IP), it is marked as "Field Difference"; if the actual value is missing content from the set value (such as missing VLANID=30), it is marked as "Configuration Missing".

[0087] Intent comparison (taking firewall ACL policy as an example) is as follows:

[0088] Strategy rule abstraction:

[0089] SCCD model setting rules: source IP range is 10.0.0.0 / 24, destination IP range is 192.168.1.0 / 28, protocol is TCP, and destination port range is 8800-8805;

[0090] On-site data collection configuration rules: There are two rules - the first one has a source IP range of 10.0.0.0 / 25 and a destination port range of 8800-8802, and the second one has a source IP range of 10.0.0.128 / 25 and a destination port range of 8803-8805. The remaining parameters are consistent with the model settings.

[0091] Coverage assessment: Source IP range coverage calculation: The combined source IP range of the two rules on site is 10.0.0.0 / 24, which is completely consistent with the model value;

[0092] Calculate the destination port range coverage: The destination port range of the two rules in the field is merged into 8800-8805, which is completely consistent with the model value.

[0093] Result determination: The on-site configuration rules fully cover the strategic intent of the model's setpoint rules, with no issues of excessively broad scope or missing information, and are therefore determined to be "compliant".

[0094] The conversion of non-standard data to the IEC 61850 standard format is implemented as follows:

[0095] Taking the conversion of VLAN configuration data for existing H3C traditional switches as an example:

[0096] Mapping rule configuration: Write mapping rules to specify the data source and target location:

[0097] Data source: Items 1-2 of the "VLAN table" under the "Network / Link" category in the standardized data (corresponding to VLANID=10, 20), including VLANID and bound port;

[0098] Target location: Under the logical device "LINK" with device identifier "SW_STO_001" in the SCCD file, the first and second items of the logical node "ZVLN", corresponding to the data objects "VlanId" and "Interface" and their data attribute "stVal".

[0099] Mapping execution includes:

[0100] Data addressing: Accurately locate VLAN IDs 10 and 20 and their bound ports from standardized data;

[0101] Data writing: The located VLAN ID is written to "VlanId.stVal" in the corresponding field of the logical node "ZVLN", and the bound port is written to "Interface.stVal", generating XML format data that conforms to the IEC61850 standard to ensure compatibility with the structure of the SCCD model.

[0102] The automatic archiving of verification results includes the following:

[0103] SCCD-plus model file generation:

[0104] Content integration: Three types of information are embedded into the original SCCD model: first, the collected standardized configuration data of the devices; second, the results of the comparison between set values ​​and intentions (marked as "consistent", "difference", "missing" status); and third, configuration correction suggestions (such as "supplement VLANID=30 configuration" and "change the management IP to 192.168.10.10").

[0105] Format verification: Use the configuration language verification tool of the IEC61850 standard to check the syntax compliance of the SCCD-plus file to ensure that there are no format errors;

[0106] The archiving and application are as follows:

[0107] Storage Management: Store SCCD-plus files to data storage devices, associate them with device identifiers and grid-connected batch numbers, and support retrieval by device type and acquisition time;

[0108] Grid connection verification: The grid connection verification system calls the SCCD-plus file. After the verification personnel confirm that the configuration has been corrected, the substation is allowed to connect to the grid.

[0109] Operation and maintenance support: Push the SCCD-plus file to the operation and maintenance system as the baseline data for subsequent equipment configuration changes and fault tracing.

[0110] During the implementation of this 220kV digital substation, the generated SCCD-plus model file successfully supported grid connection review and operation and maintenance management, realizing the forward control of substation grid connection and dynamic updating of the SCCD model, thus verifying the feasibility and practicality of the technical solution of this invention.

[0111] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of the present invention is defined by the appended claims and their equivalents.

Claims

1. An automatic acquisition and checking method of SCCD model in grid-connected implementation process, characterized in that, Comprise the following steps: S1: Construct an automatic acquisition and model checking technology system based on standard communication protocols and configuration analysis mechanisms, which supports multi-source protocol adaptation, multi-type device compatibility, structured data comparison, and automatic archiving; S2: Obtain the operating configuration information of the total station device through multi-source acquisition; S3: Compare and verify the differences between the operating configuration information collected in S2 and the fixed value baseline in the SCCD model of the plant station grid connection scheme; S4: After verification, automatically archive the SCCD-plus model file, which serves as the reliable data basis for subsequent grid connection audit, model distribution, and operation and maintenance support.

2. The method of claim 1, wherein the method is characterized by: The multi-source acquisition method includes acquisition of incremental devices and acquisition of inventory devices: For incremental devices, use IEC61850 MMS communication protocol to directly read device operating configuration information; For inventory devices, use configuration translation conversion tools to collect and analyze device operating configuration information, which supports the analysis of raw configuration information of multiple communication protocols.

3. The method of claim 2, wherein the method is characterized by: The analysis process of the configuration translation conversion tool includes: Extract the multi-element heterogeneous raw configuration information of the inventory device, and convert the raw configuration information into a standardized data format through normalization technology, which is used for subsequent comparison with the SCCD model fixed value baseline.

4. The method of claim 1, wherein the method is characterized by, The difference comparison adopts a two-dimensional verification mechanism of fixed value comparison and intent comparison: The fixed value comparison compares the collected operating configuration information with the set value in the SCCD model on a field-by-field basis to verify the consistency at the field level; The intent comparison is used to identify the consistency of strategy targets and actual protection intent, and to judge the rationality and completeness of strategy configuration.

5. The method of claim 4, wherein the method is characterized by: The intent comparison uses a five-tuple Cartesian product-based comparison algorithm, which includes: Abstract the fixed value rules in the SCCD model and the configuration rules collected on site into five-tuple structures; Through Cartesian product calculation and iteration set operation, it is determined whether the configuration rules collected on site completely cover the fixed value rules in the SCCD model without the problem of excessively wide range.

6. The method of claim 1, wherein the method is used in a grid-connected implementation of the SCCD model. It also includes a data format conversion step: Through a flexible mapping configuration syntax, non-standard format data obtained through multi-source acquisition is converted into XML format data conforming to IEC61850 standards, and the mapping configuration syntax supports user-defined correspondence between data source fields and target fields.

7. The method of claim 6, wherein the method is used in a grid-connected implementation of the SCCD model. The mapping configuration syntax contains mapping addressing statements, which take the top array of the original collected data as the starting point and locate the target data object through a hierarchical structure of "field.field"; Array type fields support two positioning methods: one is to filter the array elements that meet the requirements through "$+ attribute filtering conditions", and the other is to specify the array elements to be matched through "# index or index range".

8. The method of claim 6, wherein the method is used in a grid-connected implementation process of the SCCD model, and the method is characterized in that, The mapping configuration syntax includes a mapping output statement, which starts from the IED name in the SCCD file, follows a hierarchical structure of "IED→logical device→logical node→data object→data attribute", wherein the logical device corresponds to the LD, the logical node corresponds to the LN, the data object corresponds to the DO, and the data attribute corresponds to the DA, and accurately maps the converted standardized data to the corresponding position of the SCCD file.

9. The method of claim 1, wherein the method is used in a grid-connected implementation of the SCCD model. The SCCD-plus model file at least includes the following contents: Comparison relationship between the collected device operation configuration information and the original modeling value of the SCCD model; Structured information of the difference comparison result, the structured information including at least one of a comparison result type, a configuration defect range, a redundancy strategy identifier, and a configuration correction suggestion.

10. The method of claim 5, wherein the method is used in a grid-connected implementation of the SCCD model. The five-tuple structure includes a source address set, a destination address set, a protocol type, a source port set, and a destination port set, wherein the source address set and the destination address set can be a single IP address or a CIDR network segment, the protocol type includes a TCP protocol or a UDP protocol, and the source port set and the destination port set can be a single port or a port range.

Images