Modeling and simulation method of relay protection device and control device

Abstract

The application discloses a modeling and simulation method of a relay protection device and a control device, and relates to the technical field of power systems. The modeling and simulation method of the relay protection device comprises the following steps: receiving a standardized configuration instruction, and generating a component library management platform based on the standardized configuration instruction; when a smart calling selection instruction is received, generating a target standardized modeling template matched with the smart calling instruction, determining component combinations in the standardized modeling template, loading preset parameter configurations, setting a cooperative simulation interface, and generating a preset protection device model corresponding to the target standardized modeling template; when a self-defined calling selection instruction is received, analyzing configuration information in the self-defined calling selection instruction, determining the correlation between components, parameter configuration information and a cooperative simulation interface based on the configuration information, and generating a self-defined protection device model based on the correlation between components, the parameter configuration information and the cooperative simulation interface. The application aims to improve the modeling efficiency and simulation accuracy.

Description

Technical Field

[0001] This invention relates to the field of power system technology, and in particular to a modeling and simulation method and control device for relay protection devices. Background Technology

[0002] While current modeling and simulation methods for power system relay protection have made some progress, they still have shortcomings and cannot meet the actual needs of collaborative simulation of large power grids. For example, existing modeling and simulation methods for relay protection devices struggle to balance standardized component reuse with flexible adaptation to complex scenarios when dealing with multiple types of protection devices in a large power grid. This results in low modeling efficiency and difficulty in supporting collaborative simulation of multiple relay protection devices. Large power grid collaborative simulation systems face complex operating modes and fault types. Existing component calling methods are too simplistic and cannot quickly combine and call components according to the needs of different complex fault scenarios and different types of protection devices. This leads to insufficient modeling flexibility, low modeling efficiency and simulation accuracy, and an inability to meet the collaborative simulation requirements of multiple protection devices. Summary of the Invention

[0003] The main objective of this invention is to provide a modeling and simulation method and control device for relay protection devices, aiming to improve modeling efficiency and simulation accuracy.

[0004] To achieve the above objectives, this invention proposes a modeling and simulation method for relay protection devices, which includes: Receive standardized configuration instructions and generate a component library management platform based on the standardized configuration instructions; Upon receiving an intelligent call selection instruction, a target standardized modeling template matching the intelligent call instruction is generated, and the component combination in the standardized modeling template is determined, the preset parameter configuration is loaded, and the co-simulation interface is set, and a preset protection device model corresponding to the target standardized modeling template is generated. Upon receiving a custom call selection instruction, the configuration information in the custom call selection instruction is parsed, and the relationships between components, parameter configuration information, and co-simulation interface are determined based on the configuration information. A custom protection device model is then generated based on the relationships between components, parameter configuration information, and co-simulation interface.

[0005] In one embodiment, the standardized configuration instructions include at least one of standardized component import instructions, index query instructions, and user permission instructions. The step of receiving the standardized configuration instructions and generating a component library management platform based on the standardized configuration instructions includes: Receive standardized component import instructions, write and store standardized components in batches, and determine the attributes of each standardized component, including at least one of functional attributes, adaptation range, parameter range, co-simulation adaptability, and interface definition. Upon receiving an index query instruction, query the corresponding standardized component; Upon receiving a user permission instruction, the system determines the access control permissions that match the user permission instruction and initializes the control list to generate the component library management platform.

[0006] In one embodiment, before generating a target standardized modeling template matching the intelligent call instruction upon receiving the intelligent call selection instruction, and determining the component combinations in the standardized modeling template, loading preset parameter configurations, setting co-simulation interfaces, and generating a preset protection device model corresponding to the target standardized modeling template, the modeling and simulation method of the relay protection device further includes: Multiple standardized modeling templates are generated based on standardized components and preset protection device types, and the standardized modeling templates are stored. Each of the standardized modeling templates corresponds to a preset protection device type.

[0007] In one embodiment, the step of generating a target standardized modeling template matching the intelligent call selection instruction upon receiving the intelligent call selection instruction, determining the component combinations in the standardized modeling template, loading preset parameter configurations and setting co-simulation interfaces, and generating a preset protection device model corresponding to the target standardized modeling template includes: Upon receiving an intelligent call selection instruction, the intelligent call selection instruction is matched with multiple standardized modeling templates to obtain a matching result; Based on the matching results, a standardized modeling template matching the intelligent invocation command is generated; Based on the target standardized modeling template, determine the component combination in the target standardized modeling template, load the preset parameter configuration and set the co-simulation interface; Generate a preset protection device model corresponding to the target standardized modeling template.

[0008] In one embodiment, the custom call selection instruction includes at least one of a query instruction, a filter instruction, a modification instruction, and a co-simulation interface configuration instruction.

[0009] In one embodiment, after determining the inter-component relationships, parameter configuration information, and co-simulation interface based on the configuration information, the modeling and simulation method of the relay protection device further includes: The relationships between components, parameter configuration information, and co-simulation interfaces are verified to obtain the verification results; If the verification result is abnormal, a prompt message will be output; If the verification result is normal, the process of generating a custom protection device model based on the association between the components, parameter configuration information, and co-simulation interface is executed.

[0010] In one embodiment, simulation environment and parameter configuration information is received, and the components in the component library management platform are incrementally updated based on the simulation environment and parameter configuration information to import the new components into the standardized component library of the component library management platform. And / or, perform performance verification on the components in the component library management platform according to a preset cycle.

[0011] In one embodiment, simulation environment and parameter configuration information is received, and the components in the component library management platform are incrementally updated based on the simulation environment and parameter configuration information to import the new components into the standardized component library of the component library management platform. And / or, perform performance verification on the components in the component library management platform according to a preset cycle.

[0012] In one embodiment, the modeling and simulation method for the relay protection device further includes: After performing either the incremental update of the components in the component library management platform based on the simulation environment and parameter configuration information, or the performance verification of the components in the component library management platform according to a preset period, corresponding version record information is generated and stored.

[0013] This application also proposes a control device, the control device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the modeling and simulation method for the relay protection device described in any of the preceding claims.

[0014] The modeling and simulation method for relay protection devices in this invention enables rapid batch modeling of commonly used protection devices through pre-set standardized modeling templates, reducing repetitive operations. The customizable calling mode supports flexible configuration and parameter adjustment for specific fault scenarios. This improves upon the problems of low modeling efficiency and difficulty in supporting collaborative simulation of multiple relay protection devices, meeting both the timeliness requirements of rapid modeling for large-scale power grids and the simulation needs of complex and personalized scenarios. Attached Figure Description

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

[0016] Figure 1 This is a flowchart illustrating an embodiment of the modeling and simulation method for the relay protection device of the present invention; Figure 2 This is a flowchart illustrating another embodiment of the modeling and simulation method for the relay protection device of the present invention. Figure 3 This is a flowchart illustrating another embodiment of the modeling and simulation method for the relay protection device of the present invention; Figure 4 This is a flowchart illustrating another embodiment of the modeling and simulation method for the relay protection device of the present invention.

[0017] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of 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.

[0019] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0020] Furthermore, the use of terms such as "first" and "second" in this invention is for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. Additionally, the technical solutions of the various embodiments can be combined with each other, but only on the basis of being achievable by those skilled in the art. When the combination of technical solutions is contradictory or impossible to implement, such a combination of technical solutions should be considered non-existent and not within the scope of protection claimed by this invention.

[0021] While current modeling and simulation methods for power system relay protection have made some progress, they still have shortcomings and cannot meet the actual needs of collaborative simulation of large power grids. For example, existing modeling and simulation methods for relay protection devices struggle to balance standardized component reuse with flexible adaptation to complex scenarios when dealing with multiple types of protection devices in a large power grid. This results in low modeling efficiency and difficulty in supporting collaborative simulation of multiple relay protection devices. Large power grid collaborative simulation systems face complex operating modes and fault types. Existing component calling methods are too simplistic and cannot quickly combine and call components according to the needs of different complex fault scenarios and different types of protection devices. This leads to insufficient modeling flexibility, low modeling efficiency and simulation accuracy, and an inability to meet the collaborative simulation requirements of multiple protection devices.

[0022] To solve the above problems, refer to Figure 1 This invention proposes a modeling and simulation method for relay protection devices, the modeling and simulation method for relay protection devices including: Step S100: Receive standardized configuration instructions and generate a component library management platform based on the standardized configuration instructions; Step S200: Upon receiving an intelligent call selection instruction, generate a target standardized modeling template that matches the intelligent call instruction, determine the component combination in the standardized modeling template, load the preset parameter configuration and set the co-simulation interface, and generate a preset protection device model corresponding to the target standardized modeling template. Step S300: Upon receiving a custom call selection instruction, parse the configuration information in the custom call selection instruction, determine the association between components, parameter configuration information, and co-simulation interface based on the configuration information, and generate a custom protection device model based on the association between components, parameter configuration information, and co-simulation interface.

[0023] In this embodiment, the modeling and simulation method for relay protection devices of the present invention can be applied to the control device of a relay protection device or a large power grid collaborative simulation system. The control device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The computer program is configured to implement the steps of the modeling and simulation method for relay protection devices. The control device can be implemented using a main controller, such as an MCU (Micro Controller Unit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), a PLC (Programmable Logic Controller), or a SOC (System on Chip).

[0024] It should be noted that traditional modeling methods typically involve independent development for specific manufacturers or types of protection devices, with each R&D personnel designing components independently. This approach fails to achieve component reuse across different scenarios and equipment types. Therefore, the first step is to conduct a comprehensive review of various relay protection devices widely used in large power grids (such as 220kV line, busbar, transformer, and generator protection) and their major manufacturers. For example, by collecting technical specifications, operational logic diagrams, and parameter configuration documents from various manufacturers' protection devices, a thorough analysis of their operational logic, functional module composition, and core technical indicators can be performed. This helps determine the functional differences and common characteristics of different types of protection devices from various manufacturers, providing data support for the subsequent extraction of common core components. Based on national and industry standards such as GB / T 14285-2017 "Technical Specification for Relay Protection and Safety Automatic Devices" and DL / T 559-2019 "Setting Calculation Specification for Relay Protection and Safety Automatic Devices in Power Systems," an evaluation system was constructed using the "Analytic Hierarchy Process (AHP) + expert scoring method." This system includes dimensions such as "component reuse rate" and "co-simulation adaptability." Highly common modules with a weight greater than or equal to 85% were retained as common core components. Simultaneously, redundant logic modules specific to each manufacturer (such as proprietary communication protocol modules and redundant control modules) were eliminated. This ensures that the extracted common core components not only comply with industry standards but also possess high versatility and co-simulation adaptability. Furthermore, eliminating redundant modules effectively prevents them from affecting the versatility and reusability of the components. Then, based on the functional attributes of the extracted common core components, these components are categorized, with each category containing several components. Each component can reserve a standardized co-simulation interface to ensure seamless integration between components and between components and the large power grid co-simulation system, thus meeting the requirements for co-simulation of multiple protection devices in a large power grid. Specifically, the modeling and simulation method for relay protection devices proposed in this invention is applied to the large power grid co-simulation system. This categorization process makes the component library structure clear and easy to manage; while the reservation of standardized co-simulation interfaces improves the challenges of data interaction and timing synchronization between components and between components and the large power grid co-simulation system.

[0025] In this embodiment, staff need to clearly define the pre-defined construction principles of the standardization system to ensure its scientific rigor, practicality, and scalability. These pre-defined construction principles include, but are not limited to, the principles of universality, compatibility, standardization, and scalability. The universality principle ensures the standardization system can adapt to the modeling needs of large power grids from multiple manufacturers, of various types of protection devices, and at different voltage levels. The compatibility principle ensures seamless integration and data exchange between different components and between components and the large power grid co-simulation system. The standardization principle ensures strict adherence to relevant national and industry standards, guaranteeing that component interfaces, parameters, and logic conform to industry specifications. The scalability principle, by reserving expansion interfaces, facilitates the addition of new components and optimization of logic to adapt to new protection technologies and co-simulation requirements. Then, based on the categorized components, a standardization system is constructed according to these pre-defined construction principles. For example, a comprehensive standardization system is built for component interfaces, parameters, and logic. Finally, a component library management platform can be built. This platform centrally stores and categorizes the standardized components, achieving asset digitization and consolidation. In other words, this step centralizes and digitizes the extracted and standardized components. In this embodiment, the control device generates a component library management platform upon receiving standardized configuration commands from the user via a host computer or other devices. This component library management platform features an intelligent calling mode, designed to adapt to different modeling scenarios, enabling rapid modeling and collaborative simulation adaptation of protection devices, and improving upon the inflexible and unsuitable collaborative simulation issues of existing component calling methods. First, staff need to clarify the design principles of intelligent calling to ensure its flexibility, practicality, and reliability. These design principles include, but are not limited to: 1) Adaptability principle: adapting to different types of protection devices, various complex fault scenarios, and the collaborative simulation needs of large power grids; 2) Efficiency principle: reducing the workload of R&D personnel and improving modeling efficiency through intelligent calling; 3) Reliability principle: ensuring the validity of component calling through a verification mechanism to avoid simulation errors caused by unreasonable component combinations; and 4) Usability principle: simple and convenient calling operations to lower the professional threshold for R&D personnel. Thus, staff can output corresponding standardized configuration commands based on these design principles.

[0026] In this embodiment, to adapt to two core scenarios—batch modeling of commonly used protection devices and personalized modeling of special scenarios—a standard template mode and a custom call mode can be set. Users can flexibly switch between the two modes to meet different modeling needs. Upon receiving an intelligent call selection instruction, the control device enters the standard template mode, generates a target standardized modeling template matching the intelligent call instruction, determines the component combinations in the standardized modeling template, loads preset parameter configurations, sets the co-simulation interface, and generates a preset protection device model corresponding to the target standardized modeling template. Upon receiving a custom call selection instruction, the control device enters the custom call mode, parses the configuration information in the custom call selection instruction, determines the relationships between components, parameter configuration information, and co-simulation interfaces based on the configuration information, and generates a custom protection device model based on the relationships between components, parameter configuration information, and co-simulation interfaces.

[0027] Understandably, the standard template mode targets protection device types commonly used in large power grids, such as 220kV line protection and main transformer protection. R&D personnel can pre-configure standardized modeling templates containing core component combinations, default parameters, and collaborative interfaces on the platform. R&D personnel and other staff only need to select the corresponding template to generate a corresponding intelligent call selection instruction to the control device. This allows the control device to generate a target standardized modeling template matching the intelligent call instruction, determine the component combinations in the standardized modeling template, load preset parameter configurations, and set collaborative simulation interfaces. For example, after receiving an intelligent call selection instruction carrying a "template identifier," the control device first retrieves the identifier from the index table of the component library management platform to locate the corresponding "target standardized modeling template" object. Then, it reads the pre-stored "component combination" list (i.e., a set of component IDs or pointers) in the template object and batch instantiates these component objects in the simulation engine's memory space. It then automatically reads the definitions of the "preset parameter configurations" and "collaborative simulation interfaces" bound to the template, writes these data into the attributes of the instantiated component objects, and establishes a data bus connection between components. Finally, the aforementioned set of instantiated, configured, and connected components is encapsulated into a complete preset protection device model. The custom invocation mode, designed for non-standard equipment or special fault analysis needs, allows developers to query and filter required components on the platform according to modeling and co-simulation requirements. When developers flexibly configure the relationships, parameters, and co-simulation interfaces between components through drag-and-drop and combination, the control device receives a custom invocation selection command triggered by the developer. The control device then parses the configuration information in the custom invocation selection command and determines the relationships between components, parameter configuration information, and co-simulation interfaces based on this information. It then generates a custom protection device model based on these relationships, parameter configuration information, and co-simulation interfaces. Upon receiving the custom invocation selection command, the control device first parses the configuration information carried by the command. This configuration information is typically structured data (such as JSON or XML), containing a user-specified list of components, the connection topology between components, parameter values, and interface mapping relationships. The control device can iterate through the component relationship fields in the configuration information and establish a data interaction link (such as pointer references, message queue bindings, or shared memory mappings) for each pair of related components in memory. This step establishes the underlying implementation of the relationships, transforming the abstract connection description into an executable data channel. Then, it reads the "parameter configuration information" and "co-simulation interface" fields from the configuration information, writes them to the properties of the corresponding component object, and verifies interface type compatibility. If a parameter is not specified in the configuration information, a default value can be invoked or a parameter validation mechanism can be triggered. Finally, it is encapsulated into a custom protection device model. Unlike the standard template pattern, the structure and properties of this custom protection device model are assembled at runtime based on the configuration information, rather than being pre-defined.In this way, by customizing the protection device model, it can adapt to personalized modeling and collaborative simulation needs, ensuring that it still has strong adaptability and flexibility when facing complex and new simulation requirements.

[0028] In practical applications, this invention enables rapid batch modeling of commonly used protection devices through pre-set standardized modeling templates, reducing repetitive operations; the customizable calling mode supports flexible configuration and parameter adjustment for specific fault scenarios. This improves upon the problems of low modeling efficiency and difficulty in supporting collaborative simulation of multiple relay protection devices, meeting both the timeliness requirements of rapid modeling for large-scale power grids and the simulation needs of complex and personalized scenarios.

[0029] In another embodiment, the standardized configuration instructions include at least one of standardized component import instructions, index query instructions, and user permission instructions, as referred to Figure 2 The step of receiving standardized configuration instructions and generating a component library management platform based on the standardized configuration instructions includes: Step S110: Receive the standardized component import instruction, write and store the standardized components in batches, and determine the attributes of each standardized component. The attributes include at least one of the following: functional attributes, adaptation range, parameter range, co-simulation adaptability, and interface definition. Step S120: Upon receiving an index query instruction, query the corresponding standardized component; Step S130: Upon receiving a user permission instruction, determine the access control permissions that match the user permission instruction and initialize the control list to generate the component library management platform.

[0030] In this embodiment, the component library management platform serves as the core support for component-based modeling and intelligent invocation, enabling centralized management, indexing, querying, and maintenance of components. Firstly, the centralized component management function requires staff to import various extracted and standardized components and sub-components (with a standardized system established) into the platform for centralized storage and management. This supports batch import, batch modification, and batch deletion of components, improving management efficiency. Therefore, upon receiving a standardized component import instruction, the control device parses the instruction, batch writes and stores the standardized components, completing the import of various components and sub-components. Simultaneously, the control device parses the standardized description information of the components, automatically extracts and structures metadata such as functional attributes, adaptation range, parameter range, co-simulation adaptability, and interface definitions, establishing a complete attribute file for each component. This file labels the component's functions, adaptation range, parameter range, co-simulation adaptability, interface definitions, and other attributes, facilitating understanding of each component's characteristics by developers.

[0031] In this embodiment, upon receiving an index query instruction, the control device reads the attribute file generated in step S110, traverses the metadata of all components, and determines the corresponding standardized component. Researchers can quickly query the required components through keyword search, category filtering, and other methods, improving component query efficiency. Simultaneously, the platform supports fuzzy component queries, facilitating rapid location of target components by researchers.

[0032] In this embodiment, upon receiving a user permission instruction, the control device parses the predefined role permission policies (such as full permissions for administrators, configuration permissions for developers, and read-only permissions for simulators) in the instruction. Subsequently, these policies are compiled into Access Control Lists (ACLs) or role permission mapping tables and written to the platform's security configuration storage area. This enables the platform to support multi-user permission management, assigning different operation permissions to different roles (such as developers, administrators, and simulators), ensuring the security and management standardization of the component library. For example, administrators have full operation permissions for the component library, developers only have permissions for component querying, calling, and parameter configuration, and simulators only have permissions for component querying and viewing simulation data. This allocation of different levels of operation permissions ensures data consistency and security of the component library in a multi-user collaborative environment.

[0033] It should be noted that establishing relationships between different types of components can support intelligent component invocation; at the same time, the platform supports the visual display of component relationships, making it easier for developers to understand the logical relationships between components and optimize component combination schemes. Optionally, the relationships between components include, but are not limited to, the adaptation relationships and data interaction relationships between components, such as the relationship logic between fault feature recognition components and protection action judgment components, and the relationship logic between timing coordination components and data interaction components.

[0034] In this embodiment, researchers need to add co-simulation adaptation identifiers for different types of components. That is, add a co-simulation adaptation identifier for each component to indicate whether the component is adapted to co-simulation and the adapted co-simulation scenario (such as 220kV power grid co-simulation). This facilitates the quick screening of components adapted to co-simulation and improves the efficiency of modeling and co-simulation adaptation.

[0035] It is understood that, based on the above embodiments, researchers can divide the common core components into four categories according to their functional attributes: fault feature identification components, protection action judgment components, timing coordination components, and data interaction components.

[0036] Optionally, the fault feature identification component serves as a fundamental component for protection device modeling, enabling rapid identification and accurate calculation of fault-related features to ensure the simulation model accurately reflects the fault scenario. In this embodiment, the fault feature identification component can be further subdivided into four types: fault type identification subcomponent, fault location subcomponent, transition resistance calculation subcomponent, and fault electrical quantity acquisition subcomponent. The fault type identification subcomponent is used to quickly and accurately identify fault types (including but not limited to single-phase grounding faults, phase-to-phase faults, transitional faults, and multiple faults), providing basic information for subsequent protection action judgment. It collects electrical quantity data such as voltage and current under the fault scenario and performs logical operations based on standardized fault identification algorithms (such as the sequence component method). The identification accuracy is not less than 99%; it can adapt well to complex fault scenarios such as varying transition resistance and low-current grounding. The fault location subcomponent is used to accurately locate the fault occurrence position, providing data support for fault inversion and maintenance. The fault location sub-component combines power grid topology data and fault electrical quantity data to calculate the fault distance using standardized algorithms such as the impedance method; the location error does not exceed 5%; it can adapt to the location requirements of power grids with different voltage levels and topologies, and supports multi-fault point location, meeting the location requirements in complex fault scenarios. The corresponding formula for the impedance method is: ; To protect the line impedance from the installation point to the fault point, For transition resistance, Additional impedance provided for new energy sources The transition resistance value is calculated in real time. Thus, the transition resistance calculation subcomponent is used to accurately calculate the transition resistance value at the fault point, solving the simulation error problem caused by inaccurate transition resistance calculation in traditional modeling. An optimized impedance method is used combined with the changing patterns of fault electrical quantities for dynamic measurement. The calculation error does not exceed 10%; it can adapt to changes in transition resistance within the range of 0Ω to 100Ω, meeting the refined simulation requirements of complex fault scenarios. The fault electrical quantity acquisition subcomponent serves as the data input foundation, providing reliable data support for other components such as protection action judgment. The fault electrical quantity acquisition subcomponent collects electrical quantity data such as voltage, current, and power in real time under fault scenarios. It supports multi-source data access, possesses high concurrency and high reliability, ensuring the real-time performance and integrity of the underlying electrical quantity data.

[0037] Optionally, the protection action judgment component is used to accurately judge the action status of the protection device, ensuring the accuracy of the protection action logic in the collaborative simulation and ensuring that the simulation model can realistically simulate the action behavior of the protection device. In this embodiment, the protection action judgment component can be subdivided into four types: instant action judgment sub-component, delayed action judgment sub-component, protection setting comparison sub-component, and protection failure to operate judgment sub-component. The instant action judgment sub-component is used to judge the instant action of the protection device, ensuring that the faulty line can be quickly disconnected in the event of a serious fault. Based on the real-time comparison result of the fault electrical quantity data and the protection setting, the instant action logic is quickly triggered. The action judgment delay does not exceed 10ms; it can accurately match the instant action criteria of protection devices from different manufacturers, ensuring that the simulated action is consistent with the actual protection device action. The delayed action judgment sub-component is used to judge the delayed action of the protection device (such as delayed overcurrent, delayed zero-sequence protection, etc.), realizing the timing coordination between the main protection and the backup protection. Combining the preset action time limit and the fault duration, a comprehensive judgment is made on whether to trigger the delayed action. For example, the delay action judgment subcomponent first obtains the current backup protection's set delay time threshold (e.g., 0.5s). When a fault electrical quantity (e.g., current) is detected to exceed the preset start-up value, a timer is started internally to accumulate the fault duration. If the fault persists, the timer continues to accumulate. When the accumulated time is ≥0.5s, the component determines that the delay condition is met and triggers the "outlet trip" logic. If the fault is cleared (electrical quantity returns to normal) before the timer reaches 0.5s (e.g., 0.3s), the timer is immediately reset, and the component determines that no trip is triggered. In this way, the time limit error does not exceed 5ms; it supports flexible configuration of the delay time and can adapt to the delay action logic and time limit requirements of protection devices from different manufacturers. The protection setting comparison subcomponent serves as the data basis for action judgment, comparing the collected fault electrical quantity data with the protection setting in real time and outputting the results. It supports automated matching and high-precision comparison of multiple types of settings such as current setting, voltage setting, and time limit setting. The comparison accuracy is no less than 99.5%; it can automatically match the setting formats of protection devices from different manufacturers, effectively avoiding human error caused by manual comparison. The protection failure-to-operate judgment sub-component is used to determine whether the protection device fails to operate, providing support for simulation analysis and fault inversion. Combining fault characteristics and protection action logic, it identifies failure-to-operate scenarios and locates the causes by analyzing the matching between fault electrical quantity data and protection action status. It can accurately determine the causes of failure-to-operate, such as unreasonable setting values ​​and component failures, providing a reliable reference for modeling optimization and protection device verification.

[0038] Optionally, timing coordination components are used to coordinate the action timing of multiple sets of multi-level protection devices, adapting to the timing synchronization requirements of large power grid collaborative simulation. This ensures that multiple protection device models can coordinate their actions according to the actual action logic, simulating the collaborative cooperation process of multiple protection systems under large power grid fault scenarios. Timing coordination components can be further subdivided into three types: protection and circuit breaker coordination timing sub-components, multi-protection coordination timing sub-components, and action timing recording sub-components. The protection and circuit breaker coordination timing sub-component coordinates the action timing of protection devices and circuit breakers, ensuring the synchronization of protection actions and circuit breaker tripping actions (controlling the time difference between protection actions and actual circuit breaker tripping), avoiding simulation errors caused by timing deviations. This sub-component strictly follows the actual action timing logic of protection devices and circuit breakers, controlling the time difference between protection actions and circuit breaker tripping actions, with a timing error not exceeding 15ms. It can adapt to the action characteristics of different types of circuit breakers, ensuring the realism of collaborative simulation. The multi-protection coordination timing sub-component coordinates the action timing of multiple protection devices (such as the coordination between main protection and backup protection, and the coordination of protection devices in different areas). According to the actual protection coordination logic, it controls the action sequence and time limits of each protection device to ensure the realism of the collaborative simulation. It supports timing configuration for multiple protection devices and can simulate the linkage action of backup protection after the main protection fails, adapting to the collaborative action scenarios of multiple sets of multi-level protection devices in large power grids. For example, when the main protection fails to clear the fault within a set time, this component will precisely trigger the delayed linkage action of the backup protection; or in the coordination of upper and lower level protections, it ensures that the protection closest to the fault point acts first. The action timing recording sub-component records the action timing data of each protection device and component in real time, forming a timing log to provide data support for simulation result analysis and fault inversion. This sub-component has a recording accuracy of no less than 1ms and can record the action time, action status, data input and output of each component. It supports the export and analysis of time series data, which not only provides data support for fault inversion, but also helps staff to quickly check simulation errors (such as verifying whether over-level tripping has occurred, whether the timing coordination is correct, etc.), thereby continuously optimizing the modeling scheme.

[0039] Optionally, data interaction components are used to enable data interaction between components and multi-source data systems, while supporting data interoperability among various protection device models during collaborative simulation, ensuring real-time data transmission and sharing. Data interaction components can be further divided into three types: multi-source data receiving sub-components, parameter parsing sub-components, and data output sub-components. In this embodiment, the multi-source data receiving sub-component, facing massive heterogeneous data (such as power grid topology, protection settings, fault recordings, etc.) from multi-source data systems, provides a highly parallel receiving channel and incorporates a data caching mechanism. In complex collaborative simulation processes, network fluctuations or data concurrency can easily lead to data loss. The caching function ensures the continuity and stability of the underlying data input, meeting the data throughput requirements when multiple protection devices in a large power grid are modeled simultaneously. The data output formats from multi-source data systems are often diverse (such as XML, JSON, etc.) and may contain invalid or interfering data. The multi-source data receiving sub-component is responsible for in-depth parsing, cleaning, and transformation of this raw data, and establishing a mapping relationship between multi-vendor data and standardized data. With a resolution accuracy of no less than 99.8%, it transforms externally chaotic data into a standardized format recognizable by simulation components and completes missing data, reducing simulation configuration errors caused by inconsistent data formats. The data output sub-component outputs component action results, fault data, timing data, etc., to the co-simulation system or other data systems in a standardized format. It supports flexible configuration of output type and frequency according to simulation requirements and supports both real-time and batch output modes, ensuring that the data generated by the simulation model can be accurately recognized by the upper-level co-simulation system. It also supports data feedback to other data systems, achieving data interoperability and sharing among multiple protection device models.

[0040] Based on the above embodiments, the preset construction principles can be the principles of universality, compatibility, standardization, and extensibility. In this embodiment, a standardized system covering all dimensions of component interfaces, parameters, and logical algorithms is constructed based on the preset construction principles and different types of components. These three dimensions are interconnected and mutually supportive, forming a complete standardized system.

[0041] In this embodiment, component interface standardization unifies the interface specifications of various components, ensuring seamless integration and flexible combination between components, while supporting data interaction for collaborative simulation of multiple models. Component interface standardization includes three parts: basic interface specifications, unified input / output interfaces, and unique interface identifiers. The basic interface specifications can be based on the Common Information Model (CIM) in the DL / T 890.301 standard, combined with the needs of large power grid collaborative simulation, adding dedicated interfaces for collaborative simulation, clarifying the functional definitions, data formats, transmission rates, and other technical indicators of the interfaces, ensuring that the interfaces comply with industry standards, and adapting to the timing synchronization and data interoperability requirements of collaborative simulation. Unified input / output interfaces refer to unifying the input and output interface formats of various components. Input interfaces uniformly adopt standardized data formats (such as JSON format), clearly defining the names, types, and value ranges of input parameters, ensuring that the outputs of different components can be directly used as inputs for other components without manual conversion by the user. Output interfaces uniformly standardize the format and encoding of output data, ensuring that the data output by components can be accurately identified by the collaborative simulation system and other components. For example, the output interface format of fault feature identification components is uniformly standardized as a data packet of "fault type + fault location + transition resistance + electrical quantity data". This format ensures that protection action judgment components can directly receive and process data without secondary conversion, significantly improving the data flow efficiency between components. It should be noted that the fault type determines the protection startup logic branch and algorithm routing. For example, when a ground fault is identified, the system will accurately trigger the zero-sequence or ground distance protection logic chain, effectively avoiding parallel idling of multiple protection modules and improving computational efficiency. The fault location characterizes the specific electrical location of faults such as short circuits, grounding, and open circuits in the primary system, serving as a crucial basis for protection devices to perform intra-zone / extra-zone fault discrimination, distance measurement, sensitivity verification, and setting. The transition resistance breaks the traditional simulation's limitation of the "ideal metallic short circuit" assumption. In actual power grids, high-resistance grounding leads to increased distance protection measurement impedance. This field is directly input to the protection setting comparison sub-component and the fast-acting / delay judgment sub-component to dynamically correct the impedance relay action boundary, enabling collaborative simulation to accurately reproduce complex scenarios such as "protection maloperation / failure to operate under faults with varying transition resistance," significantly improving the realism of the simulation. Electrical quantity data includes real-time data such as voltage, current, and sequence components calculated by component logic, providing direct quantitative support for subsequent action judgment and logic verification. Unique interface identifiers mean assigning a globally unique identifier to each component interface, avoiding interface conflicts between components at the underlying level and facilitating automatic interface matching and call verification by the system. Simultaneously, this identifier embeds semantic information such as component type and functional attributes, enabling modelers and other staff to intuitively and quickly identify interface functions, improving the efficiency and accuracy of interface configuration.

[0042] In this embodiment, parameters refer to component parameters, which need to be standardized. Unifying the definition and configuration of component parameters ensures their compatibility with relay protection devices from different manufacturers and of different types, while also guaranteeing the uniformity and comparability of parameters in collaborative simulations. Different manufacturers often have different naming conventions for the same physical quantity. Therefore, it is necessary to unify parameter names and normalize synonymous parameters. For example, the "instantaneous trip current setting" and "fast trip current setting" from different manufacturers are uniformly named "instantaneous trip current setting," and "delay time" and "action time limit" are uniformly named "action time limit," ensuring consistency in parameter naming. This prevents model configuration confusion caused by naming differences. Unifying parameter types and units ensures the accuracy of underlying calculations and interactions, defining the data type (e.g., floating-point, Boolean) and physical unit (e.g., current in A, voltage in kV, time in ms) for each parameter. In complex mathematical operations, even small deviations in data type or unit (e.g., mistaking milliseconds for seconds) can lead to simulation errors. Unifying parameter types and unit standards reduces the risk of calculation errors and data interaction failures caused by format incompatibility. A unified parameter value range can establish a "safety boundary" for parameter configuration. For example, by combining national / industry standards and the actual equipment capabilities of multiple manufacturers, reasonable upper and lower limits can be set for each parameter (such as instantaneous overcurrent 0-1000A). This not only ensures that the component can adapt to protection devices of different voltage levels, but also avoids component failures caused by abnormal parameter configurations. For example, the instantaneous overcurrent setting value is uniformly defined as 0-1000A, and the action time limit value is uniformly defined as 0-1000ms. Establishing parameter mapping relationships can construct a mapping table between the parameters of protection devices from multiple manufacturers and standardized component parameters, realizing automatic parameter matching and conversion. When a component is called to adapt to protection devices from different manufacturers, the system automatically converts the manufacturer parameters to standardized component parameters according to the mapping table, eliminating the need for manual adjustment and improving modeling efficiency. At the same time, the mapping table supports dynamic updates, and when a new manufacturer's protection device is added, the corresponding parameter mapping relationship can be quickly added. In this way, the originally tedious manual verification and parameter conversion work is automatically completed by the system. Meanwhile, the dynamic update mechanism ensures that the platform can always be compatible with the latest protection devices, giving the system strong scalability. Setting default values ​​for parameters lowers the modeling threshold and improves initialization efficiency. Based on typical industry configurations and setting procedures, a set of reasonable and universal initial default values ​​for parameters can reduce the workload of parameter input for staff. The default values ​​are set based on commonly used parameter configurations of protection devices from multiple manufacturers, while also incorporating relay protection setting standards to ensure their rationality and universality. This reduces repetitive input work for staff when modeling large-scale power grids. Furthermore, reasonable default values ​​ensure that the model has basic operational logic during the initialization phase, shortening the model debugging cycle.

[0043] In this embodiment, the component logic algorithm also needs to be standardized. By unifying the core logic algorithm of the components, the universality and accuracy of the component logic can be ensured. At the same time, the extension interface is reserved to take into account the adaptability and scalability of collaborative simulation.

[0044] In this embodiment, a unified core algorithm template can be defined for various components based on the relay protection operation principle and national and industry standards. For example, the fault type identification uniformly adopts the sequence component method, the transition resistance calculation uniformly adopts the optimized impedance method, and the protection action judgment strictly follows the action criterion design logic algorithm in the regulations. In this way, the logic of the same type of component is consistent. Regardless of which manufacturer's model is called, its core protection logic operates based on the same set of "standard benchmarks," ensuring the accuracy of logic judgment in collaborative simulation. Redundant logic can be eliminated to achieve "lightweight" component functions. Non-core logic (such as proprietary communication protocol logic, local display driver logic, redundant control logic, etc.) existing in equipment from multiple manufacturers is processed, and only the core functional logic is retained. In this way, redundant logic is avoided from affecting the versatility and operating efficiency of the component. This not only avoids redundant code occupying simulation computing resources and improves operating efficiency, but also reduces logic coupling, ensures the simplicity of component logic, and facilitates subsequent optimization and maintenance.

[0045] In this embodiment, extension interfaces need to be reserved for different types of components to accommodate newly added logic algorithms. Open extension interfaces are designed outside the standardized core logic framework. When faced with new fault characteristics, innovative protection technologies, or collaborative simulation requirements, it is not necessary to reconstruct the entire component; simply adding logic algorithms or optimizing existing logic through the interfaces is sufficient. For example, a new fault identification algorithm interface can be reserved in the fault characteristic identification component. When a new fault type appears, an algorithm can be added directly without modifying the component's core logic. This ensures that the component library management platform can dynamically upgrade with the development of power grid technology, improving the adaptability and scalability of the large power grid collaborative simulation system to future complex scenarios.

[0046] In this embodiment, a periodic logic verification mechanism can be established, combined with fault injection testing technology, to periodically verify the core algorithm of the component. By simulating various extreme fault scenarios, it verifies whether the algorithm output meets the expected standards. This ensures that the component logic meets standardization requirements, effectively reducing simulation errors caused by logic drift or code defects, and verifying the accuracy and reliability of the component logic. The preset period can be set by the R&D personnel.

[0047] In this embodiment, the initial operating state of the relay protection device to be verified is set to "non-operational (non-operational) state". Fault data corresponding to the fault point is received and used as the initial input data for the internal logic judgment of the protection device. Thus, the initial input data can be injected into a preset "fault injection parameter matrix". By introducing fault injection testing, the accuracy and reliability of the component logic are verified. Simultaneously, the setting configuration of the protection device (such as operating threshold, time limit, braking coefficient, etc.) is read to complete the initial preparation before simulation. This step completes the pre-simulation preparation. The fault injection matrix covers four key dimensions: fault type (such as single / three-phase grounding, phase-to-phase short circuit, etc., used to verify sequence component routing and startup logic), fault phase (A / B / C phases, determining the sequence network phase reference and boundary conditions), transition resistance (0Ω to 100Ω stepped values, verifying the high-resistance grounding simulation fidelity and impedance boundary correction), and fault duration (start time t_start to end time t_end, accuracy ±1ms, verifying timing coordination and delay threshold).

[0048] In this embodiment, the initial input data can also be preprocessed, and fault parameters can be calculated based on the preprocessed data and preset formulas. For example, according to the type of protection device (line protection, main transformer protection, etc.) and the type of fault (single-phase grounding, three-phase short circuit, etc.), the input fault component data (initial input data) is parsed by the internal logic module of the protection device, and the core sequence component data such as positive sequence current (I1), negative sequence current (I2), zero sequence current (I0) and corresponding voltage are extracted and recorded. Subsequently, the core parameters related to the protection action criteria are calculated using the internal mathematical model of the protection device (such as preset formulas for calculating the operating current and braking current of ratio differential protection).

[0049] The preset formula includes: ; ; ; in, To protect against operating current, To protect the braking current; This is the ratio braking coefficient. This is the pre-processed positive sequence current. This is the pre-processed negative sequence current. The initial input data, which is the preprocessed zero-sequence current, includes at least one of positive-sequence current, negative-sequence current, and zero-sequence current.

[0050] In this embodiment, based on the calculated fault parameters and the configuration values ​​of the protection settings, a logical judgment of the protection action is performed, and the logical judgment result is output. For example, in ratio differential protection, it is determined whether the calculated protection action current is greater than the protection action current setting and whether it meets the constraint condition of the ratio restraint coefficient, thereby obtaining the logical judgment result of whether the protection device meets the tripping requirement at the current moment.

[0051] In this embodiment, if the logic judgment result determines that the relay protection device has reached a stable state (e.g., if three consecutive judgment results are consistent and all indicate a stable state), and the fault has been cleared by the current relay protection device, then the logic simulation verification stops. After the simulation verification ends, the system automatically outputs the protection simulation results (including the action / non-action status, action time, etc.) and synchronizes the results to the graphical operation platform. The internal logic action process of the protection device is intuitively displayed through animation and numerical representation, while the simulation record is retained to facilitate subsequent protection logic verification and fault diagnosis by the staff. Only when the logic judgment results are consistent multiple times is it determined that the relay protection device has reached a stable state, eliminating transient interference. If the fault has been successfully cleared at this time, it indicates that the protection device's logic is correct and it has effectively completed the protection task, and the verification process ends normally.

[0052] In this embodiment, if the logic judgment determines that the relay protection device has reached a stable operating state, but the fault has not been cleared by the current relay protection device, then the data is transmitted to the next-level protection device according to the topology connection relationship to continue the iterative simulation. That is, the initial input data is output to the next-level relay protection device connected to the current relay protection device, and steps S232 to S233 are executed. When the main protection reaches a stable state but fails to clear the fault (i.e., failure to operate occurs), the system will transmit the fault data to the next-level or adjacent backup protection device according to the power grid topology connection relationship, triggering its delayed action logic, thereby verifying the timing coordination and cooperative action capability between multi-level protections. If the logic judgment determines that the relay protection device has not reached a stable operating state, then the fault data corresponding to the fault point is reread and used as the initial input data, the logic judgment parameters are adjusted, and the iterative simulation continues.

[0053] Understandably, when consecutive judgment results are inconsistent, it indicates that the logic is in an oscillating or non-convergent state. At this time, the control device will reread the fault data, adjust the logic judgment parameters, and continue iterative simulation (re-execute preprocessing and logic judgment) until the action state reaches stability or meets other termination conditions, thereby ensuring the reliability and rigor of the verification process.

[0054] In ratio differential protection, the calculated protection operating current is determined to be greater than the protection operating current setting and to satisfy the constraint condition of the ratio restraint coefficient. This determines whether the protection device meets the logic judgment result for tripping at the current moment. In this embodiment, the constraint condition is that the ratio restraint coefficient is greater than or equal to the ratio restraint coefficient setting. The judgment logic is as follows: and Perform protective actions; or No protective action is performed; To set the operating current value for protection, The calculated protection operating current; Set the ratio braking coefficient to a fixed value. This is the ratio braking coefficient.

[0055] In this embodiment, the system determines whether the logical judgment result has reached a stable operating state. If the judgment results are consistent N times consecutively (N is a positive integer), transient numerical fluctuations or single-step calculation errors that may occur during the simulation calculation are filtered out. This avoids frequent start-stops or misjudgments of the protection device due to numerical oscillations under critical conditions, ensuring the stability of the output logical state. If a stable state is reached, the system further determines whether the fault has been cleared. If the fault has been cleared, the logic simulation stops; if the fault has not been cleared, data is passed to the next-level protection unit according to the topology connection relationship to continue iterative simulation. If a stable operating state has not been reached, the fault data is reread, the logical judgment parameters are adjusted, and iterative simulation continues. Furthermore, after the simulation stops, the protection simulation result is output, allowing users to view the internal logic operation process of the protection device. Simulation records are also retained for subsequent protection logic verification and fault diagnosis. Thus, by comparing the protection simulation result with the logic polarity in the protection device's instruction manual, the logical correctness of the components can be verified.

[0056] Traditional modeling and simulation methods lack a flexible and adaptable intelligent mechanism for component invocation. They cannot quickly combine and invoke components according to the needs of different complex fault scenarios and different types of protection devices, resulting in insufficient modeling flexibility, difficulty in balancing modeling efficiency and simulation accuracy, and difficulty in supporting the collaborative simulation needs of multiple protection devices.

[0057] Therefore, in another embodiment, before generating a target standardized modeling template matching the intelligent call selection instruction upon receiving the intelligent call selection instruction, and determining the component combinations in the standardized modeling template, loading preset parameter configurations, setting co-simulation interfaces, and generating a preset protection device model corresponding to the target standardized modeling template, the modeling and simulation method of the relay protection device further includes: Multiple standardized modeling templates are generated based on standardized components and preset protection device types, and the standardized modeling templates are stored. Each of the standardized modeling templates corresponds to a preset protection device type.

[0058] In this embodiment, two intelligent calling modes are designed to meet the requirements of large power grid collaborative simulation, adapting to different modeling scenarios and enabling rapid modeling and collaborative simulation of protection devices. The standard template mode is designed for commonly used protection device types (such as 220kV line protection). Based on components in a common component library, several standardized modeling templates adapted for collaborative simulation are generated and pre-stored in the control device's memory. Each standardized modeling template includes the core component combinations, parameter configurations, and collaborative simulation interface settings required for that type of protection device. During modeling, simply selecting the corresponding template quickly generates the protection device model, eliminating the need for manual component assembly by staff. Furthermore, the model can be directly integrated into the large power grid collaborative simulation system.

[0059] Optionally, refer to Figure 3 The step of generating a target standardized modeling template matching the intelligent call selection instruction upon receiving it, and determining the component combinations in the standardized modeling template, loading preset parameter configurations, setting co-simulation interfaces, and generating a preset protection device model corresponding to the target standardized modeling template includes: Step S210: Upon receiving an intelligent call selection instruction, the intelligent call selection instruction is matched with multiple standardized modeling templates to obtain a matching result; Step S220: Generate a standardized modeling template for the target that matches the intelligent invocation command based on the matching result; Step S230: Based on the target standardized modeling template, determine the component combination in the target standardized modeling template, load the preset parameter configuration, and set the co-simulation interface; Step S240: Generate a preset protection device model corresponding to the target standardized modeling template.

[0060] In this embodiment, after receiving the intelligent call selection instruction, the control device first parses the instruction. Then, it matches the identifier of the intelligent call selection instruction with the identifiers of multiple standardized modeling templates, and generates the target standardized modeling template with the highest matching degree. This target standardized modeling template is then loaded from storage to runtime for subsequent simulation calculations.

[0061] In this embodiment, assuming the modeler selects "220kV line distance protection" on the host computer interface and clicks "Generate Model," the control device receives a smart call selection command. The control device parses this command, calls the template index table of the component library management platform, and matches the identifier of the smart call selection command with the identifier in the template index table. Based on the matching result, the control device reads the complete definition file of the template from the database. This file contains a component combination list, preset parameter configurations, co-simulation interface definitions, etc. The control device can load the above definitions into a new memory area to generate a running template instance, i.e., the preset protection device model. At this point, the target standardized modeling template has changed from a static file into an operable object (the preset protection device model).

[0062] During modeling, modelers only need to select the corresponding type of protection device template from the template list in the component library management platform according to actual modeling needs. The control device will automatically call the component combinations in the template, load the preset parameter configurations and co-simulation interface settings, eliminating the need for modelers to manually combine components, configure parameters, and interfaces. Modelers can fine-tune the parameters in the template according to the specific protection device model and power grid operation mode. This improves modeling efficiency and convenience.

[0063] In one embodiment, the custom call selection instruction includes at least one of a query instruction, a filter instruction, a modification instruction, and a co-simulation interface configuration instruction.

[0064] In this embodiment, query commands include, but are not limited to, actions to control the control device to "retrieve component metadata from the component library index"; filtering commands include, but are not limited to, actions to control the control device to "filter the component list according to preset conditions (such as voltage level, protection type)". Modification commands include, but are not limited to, actions to control the control device to "overwrite the component parameter register or update the association pointer". Co-simulation interface configuration commands include, but are not limited to, actions to control the control device to "bind the data bus and verify interface protocol compatibility".

[0065] Optionally, after determining the relationships between components, parameter configuration information, and co-simulation interfaces based on the configuration information, refer to Figure 4 The modeling and simulation method for the relay protection device also includes: Step S310: Verify the relationships between components, parameter configuration information, and co-simulation interfaces to obtain verification results; Step S320: If the verification result is abnormal, output a prompt message; Step S330: If the verification result is normal, execute the process of generating a custom protection device model based on the association between the components, parameter configuration information, and co-simulation interface.

[0066] In this embodiment, after receiving a custom call selection instruction, the control device first parses the component associations, parameter configuration information, and co-simulation interface definitions in the instruction. Subsequently, it invokes an intelligent call verification mechanism, including: interface compatibility verification: automatically comparing the output interface definitions of upstream components (such as fault feature identification components) with the input interface definitions of downstream components (such as protection action judgment components) to verify whether the data types, protocol formats, and semantics match; parameter rationality verification: comparing the custom parameter configuration with the parameter value ranges and co-simulation adaptation identifiers stored in the component library to verify whether the parameters are out of range, missing, or conflicting; and co-simulation adaptability verification: checking whether the component combination has a co-simulation interface and whether the interface definition matches the current simulation environment (such as 220kV power grid co-simulation).

[0067] In this embodiment, when the verification result is abnormal, the control device immediately interrupts the model generation process and outputs prompt information according to the type of abnormality. For example, if the interface is incompatible, the prompt is "The output interface of the upstream component and the input interface of the downstream component do not match. It is recommended to adjust the interface definition"; if the parameter is abnormal, the prompt is "The parameter value exceeds the range. It is recommended to modify it"; if the co-simulation compatibility is abnormal, the prompt is "The component is missing a co-simulation interface and cannot be connected to the current simulation environment".

[0068] In this embodiment, when the verification result is normal, the control device generates a custom protection device model. Based on the custom configuration information, it dynamically instantiates the target component in memory space. Based on the verified component relationships, it establishes a data interaction link between components in memory, writes the custom parameter configuration to the component attribute register, and sets the co-simulation interface. Finally, in a new memory area, the above definitions are loaded to generate a running template instance, i.e., the custom protection device model.

[0069] In this embodiment, upon receiving the intelligent call selection instruction, the component interface compatibility, parameter rationality, and co-simulation adaptability are automatically verified, ensuring the effectiveness of the component combination after the call and the reliability of the co-simulation. At the same time, it improves the problem of insufficient simulation fidelity caused by implicit logic coupling in module combination.

[0070] In another embodiment, a dynamic maintenance and update mechanism for the component library can be established to adapt to changes in the operation mode of the large power grid, the development of protection device technology, and the upgrading of collaborative simulation requirements, ensuring that the component library is always adapted to the modeling and collaborative simulation requirements of the large power grid.

[0071] In another embodiment, the modeling and simulation method for the relay protection device further includes: Receive simulation environment and parameter configuration information, and incrementally update the components in the component library management platform based on the simulation environment and parameter configuration information, so as to import the new components into the standardized component library of the component library management platform; And / or, perform performance verification on the components in the component library management platform according to a preset cycle.

[0072] In this embodiment, the control device can receive simulation environment and parameter configuration information through a multi-source data interaction interface. That is, it can obtain information such as changes in power grid topology, adjustment of protection settings, commissioning of new types of protection devices and changes in collaborative simulation requirements in real time, and incrementally update the attributes of relevant components in the component library. Only the parameters, logic or collaborative simulation interface of the components need to be updated, without rebuilding the component library, thus improving the update efficiency.

[0073] In this embodiment, when new protection devices or new modeling and co-simulation requirements emerge, staff can extract several common core components of the new protection devices, classify these components, and complete the standardized design and co-simulation interface configuration according to a standardized system. Finally, the standardized components are imported into a standardized component library. This enriches the coverage of the standardized component library and improves the co-simulation adaptability.

[0074] It should be noted that performance verification and co-simulation compatibility verification of components in the component library can be performed regularly. This allows staff to optimize the component's logic algorithm, parameter configuration, and component interface based on feedback from simulation modeling and co-simulation results, thereby improving the component's accuracy, compatibility, and simulation fidelity. In addition, a component usage feedback mechanism can be established to collect feedback from R&D personnel and co-simulation personnel to continuously optimize component functionality.

[0075] Optionally, the modeling and simulation method for the relay protection device further includes: Receive simulation environment and parameter configuration information, and incrementally update the components in the component library management platform based on the simulation environment and parameter configuration information, so as to import the new components into the standardized component library of the component library management platform; And / or, perform performance verification on the components in the component library management platform according to a preset cycle.

[0076] In this embodiment, the control device can record the version of each update, addition, and optimization process of the component library, generate the corresponding version record, and save it to the historical version library. This improves the problem of the standardized component library being unable to be used normally due to update errors, while ensuring the consistency of the versions of each model component in the large power grid collaborative simulation system.

[0077] In this embodiment, when the 220kV ring network protection settings are adjusted, the power grid topology changes, or the collaborative simulation requirements are upgraded, the control device can automatically trigger parameter updates and collaborative simulation interface optimizations for the protection setting comparison sub-components and fault location sub-components in the standardized component library. For example, when adding a 220kV line protection device from a new manufacturer, staff extract its common core components, design them according to the standardized system, configure them according to the collaborative simulation interface, and import them into the component library. The control device can update the components and periodically (e.g., quarterly) verify the performance of the standardized component library and perform collaborative simulation compatibility verification. By combining simulation modeling and collaborative simulation feedback results, the algorithm of the transition resistance calculation sub-component is optimized, improving the calculation accuracy and simulation fidelity of the transition resistance under complex faults. By establishing version management, each updated version is retained, and version backtracking is supported, ensuring that the versions of each model component in the collaborative simulation system are consistent.

[0078] By establishing a dynamic maintenance and update mechanism for a standardized component library, the modeling of relay protection devices and the collaborative simulation requirements of large power grids have been accurately adapted, significantly improving the real-time performance, accuracy, and maintainability of the simulation.

[0079] This application also proposes a control device, the control device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the modeling and simulation method for the relay protection device described in any of the preceding claims.

[0080] The control device provided by this invention includes the modeling and simulation method for the relay protection device described above. Compared with the prior art, the beneficial effects of the control device provided by this invention are the same as those of the modeling and simulation method for the relay protection device provided in the above embodiments, and other technical features in the control device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0081] The above description is merely a preferred embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural transformations made using the contents of the present invention's specification and drawings under the inventive concept of the present invention, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present invention.

Claims

1. A modeling and simulation method for relay protection devices, characterized in that, The modeling and simulation methods for the relay protection device include: Receive standardized configuration instructions and generate a component library management platform based on the standardized configuration instructions; Upon receiving an intelligent call selection instruction, a target standardized modeling template matching the intelligent call instruction is generated, and the component combination in the standardized modeling template is determined, the preset parameter configuration is loaded, and the co-simulation interface is set, and a preset protection device model corresponding to the target standardized modeling template is generated. Upon receiving a custom call selection instruction, the configuration information in the custom call selection instruction is parsed, and the relationships between components, parameter configuration information, and co-simulation interface are determined based on the configuration information. A custom protection device model is then generated based on the relationships between components, parameter configuration information, and co-simulation interface.

2. The modeling and simulation method for relay protection devices as described in claim 1, characterized in that, The standardized configuration instructions include at least one of standardized component import instructions, index query instructions, and user permission instructions. The step of receiving the standardized configuration instructions and generating a component library management platform based on the standardized configuration instructions includes: Receive standardized component import instructions, write and store standardized components in batches, and determine the attributes of each standardized component, including at least one of functional attributes, adaptation range, parameter range, co-simulation adaptability, and interface definition. Upon receiving an index query instruction, query the corresponding standardized component; Upon receiving a user permission instruction, the system determines the access control permissions that match the user permission instruction and initializes the control list to generate the component library management platform.

3. The modeling and simulation method for relay protection devices as described in claim 2, characterized in that, Before generating a target standardized modeling template matching the intelligent call selection instruction upon receiving it, and determining the component combinations in the standardized modeling template, loading preset parameter configurations, setting the co-simulation interface, and generating a preset protection device model corresponding to the target standardized modeling template, the modeling and simulation method of the relay protection device further includes: Multiple standardized modeling templates are generated based on standardized components and preset protection device types, and the standardized modeling templates are stored. Each of the standardized modeling templates corresponds to a preset protection device type.

4. The modeling and simulation method for relay protection devices as described in claim 3, characterized in that, The step of generating a target standardized modeling template matching the intelligent call selection instruction upon receiving it, and determining the component combinations in the standardized modeling template, loading preset parameter configurations, setting the co-simulation interface, and generating a preset protection device model corresponding to the target standardized modeling template includes: Upon receiving an intelligent call selection instruction, the intelligent call selection instruction is matched with multiple standardized modeling templates to obtain a matching result; Based on the matching results, a standardized modeling template matching the intelligent invocation command is generated; Based on the target standardized modeling template, determine the component combination in the target standardized modeling template, load the preset parameter configuration and set the co-simulation interface; Generate a preset protection device model corresponding to the target standardized modeling template.

5. The modeling and simulation method for relay protection devices as described in claim 1, characterized in that, The custom call selection command includes at least one of the following: query command, filter command, modify command, and co-simulation interface configuration command.

6. The modeling and simulation method for relay protection devices as described in any one of claims 1 to 5, characterized in that, After determining the inter-component relationships, parameter configuration information, and co-simulation interface based on the configuration information, the modeling and simulation method for the relay protection device further includes: The relationships between components, parameter configuration information, and co-simulation interfaces are verified to obtain the verification results; If the verification result is abnormal, a prompt message will be output; If the verification result is normal, the process of generating a custom protection device model based on the association between the components, parameter configuration information, and co-simulation interface is executed.

7. The modeling and simulation method for relay protection devices as described in any one of claims 1 to 5, characterized in that, The modeling and simulation method for the relay protection device also includes: Receive simulation environment and parameter configuration information, and incrementally update the components in the component library management platform based on the simulation environment and parameter configuration information, so as to import the new components into the standardized component library of the component library management platform; And / or, perform performance verification on the components in the component library management platform according to a preset cycle.

8. The modeling and simulation method for relay protection devices as described in any one of claims 1 to 5, characterized in that, The simulation environment and parameter configuration information includes at least one of the following: power grid topology change information, protection setting adjustment information, information on the commissioning of new types of protection devices, and information on changes in collaborative simulation requirements.

9. The modeling and simulation method for relay protection devices as described in any one of claims 1 to 5, characterized in that, The modeling and simulation method for the relay protection device also includes: After performing either the incremental update of the components in the component library management platform based on the simulation environment and parameter configuration information, or the performance verification of the components in the component library management platform according to a preset period, corresponding version record information is generated and stored.

10. A control device, characterized in that, The control device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the modeling and simulation method for the relay protection device as described in any one of claims 1 to 9.

Images