Engineering configuration automatic generation system, method and equipment based on relay protection function model and physical terminal mapping and medium

Abstract

The invention belongs to the technical field of engineering configuration automation, discloses an engineering configuration automatic generation system, method and equipment based on relay protection function model and physical terminal mapping and a medium, and aims to solve the problems of low automation level, high working intensity and long design period. The system comprises a relay protection function model library module used for storing a reusable function template constructed based on IEC 61850 standard logic nodes; the physical terminal model management module is used for managing physical terminal models of the device and attributes of the physical terminal models; the function-physical mapping module is used for realizing automatic association from a function signal to a physical terminal through semantic attribute matching of a signal port; the project instantiation module is used for instantiating the template according to the primary system parameters of the project and generating a corresponding logic equipment structure and parameters; and the engineering model generation module is used for fusing instantiation and mapping results and outputting a structured multi-layer engineering model file. According to the invention, full-process automation from function configuration to physical connection is realized.

Description

Technical Field

[0001] This invention belongs to the field of engineering configuration automation technology, specifically relating to an automatic engineering configuration generation system, method, device and medium based on the mapping of relay protection function model and physical terminal. Background Technology

[0002] With the continuous advancement of the power system's transformation towards intelligence and digitalization, the modeling system based on the IEC 61850 standard has become the core foundation for interoperability and information integration of relay protection equipment and substation automation systems. This standard provides a unified data model and protocol framework for communication between devices, enabling the standardization of device descriptions and communication configurations to a certain extent.

[0003] However, current relay protection engineering configuration practices still face a series of prominent bottlenecks: standard configuration files (such as SCD / IID) mainly describe communication information and lack a complete definition of the combination and logical relationship of internal functional blocks (such as PDIS, PTOC), resulting in functional modeling relying on manual experience and being difficult to standardize; input / output signals in the functional model cannot be automatically associated with the physical terminals of the device, relying on engineers to manually map point by point, which is inefficient and prone to errors; for the differences in primary systems of different bays and lines, the degree of automation of engineering instantiation (such as LD / LN naming and parameter configuration) is low, and the workload of repetitive work is large; completed engineering configurations are difficult to be effectively reused as templates, and it is impossible to achieve rapid generation of differentiated configurations across projects; in addition, there is a lack of effective synchronization mechanism between engineering configuration files, device models and design drawings, which often leads to data inconsistencies, affecting project quality and subsequent operation and maintenance.

[0004] In summary, existing relay protection engineering configuration technologies suffer from inherent limitations in functional model construction, physical association, instantiation, reusability, and model collaboration. As a result, the entire configuration process is characterized by low automation, high workload, long design cycle, and high risk of error, making it difficult to meet the increasingly demanding requirements of modern power systems for engineering efficiency, design quality, and operational reliability. Summary of the Invention

[0005] Based on the aforementioned shortcomings and deficiencies in the existing technology, one of the objectives of this invention is to at least solve one or more of the aforementioned problems in the existing technology. In other words, one of the objectives of this invention is to provide an automatic engineering configuration generation system, method, device, and medium based on the mapping of relay protection functional models and physical terminals that meets one or more of the aforementioned requirements. The aim is to effectively solve the problems of huge manual workload, poor configuration consistency, incomplete functional models, and inconsistencies among multiple engineering models in the current relay protection engineering configuration process through deep integration and automated processing of functional models, physical models, and engineering data.

[0006] To achieve the above-mentioned objectives, the present invention adopts the following technical solution:

[0007] In a first aspect, the present invention provides an automatic engineering configuration generation system based on the mapping of relay protection function models and physical terminals, comprising: The relay protection function model library module is used to store relay protection function templates built based on the IEC61850 standard logic nodes; The physical terminal model management module is used to manage the physical terminal model of the relay protection device. The physical terminal model includes terminal type, orientation, and functional domain attribute information. The function-physical mapping module is used to automatically map the signal ports in the relay protection function model to the corresponding terminals or terminal groups in the physical terminal model according to the type, direction, functional domain and phase information of the signal ports; The engineering instantiation module is used to instantiate the relay protection function template and the corresponding physical terminal model selected from the relay protection function model library module according to the primary system configuration data of the target project, and generate the logical device structure and engineering parameters corresponding to the project. The engineering model generation module is used to generate a structured engineering model file containing a functional model layer, a physical terminal model layer, and an engineering parameter layer based on the instantiation and mapping results.

[0008] As a preferred embodiment, the function-physical mapping module executes the following mapping rules: Map the protection action output signal to the trip terminal group; Map the protection activation and measurement input signals to the current transformer terminal group; The circuit breaker status and control signals are then mapped to the operating circuit terminals.

[0009] As a preferred embodiment, the project instantiation module automatically generates the following information based on the initial system configuration data: The logical device name includes a prefix for the line or bay name, a set of logical nodes with instance numbers, a set of engineering parameters including transformer ratios and voltage levels, and a list of protection functions actually enabled.

[0010] As a preferred option, it also includes: The template reuse and differentiation derivation module is used to compare structured engineering model files of different projects, identify differences in function activation, terminal mapping and parameters, and generate new function or project templates based on the differences.

[0011] As a preferred option: The engineering model file generated by the engineering model generation module includes a communication reference layer, which is used to reference the IEC61850 communication model.

[0012] Secondly, the present invention provides a method for automatically generating engineering configurations based on the system described in the first aspect, the method comprising the steps of: Obtain the physical terminal model of the relay protection device; Select the required set of relay protection function templates from the relay protection function model library; Based on the type, direction, functional domain, and phase information of the signal ports in the functional template set, the signal ports are automatically mapped to the corresponding terminals or terminal groups in the physical terminal model; Based on the primary system configuration data of the target project, the functional template set and physical terminal model are instantiated to generate the logical device structure, logical node instance and project parameters corresponding to the project. By integrating the instantiation results and mapping relationships, a structured engineering model file containing a functional model layer, a physical terminal model layer, and an engineering parameter layer is constructed and exported.

[0013] As a preferred embodiment, the automatic mapping specifically includes: Map the trip output signal of distance protection or overcurrent protection to the trip circuit terminal; Map the overcurrent protection start signal to the digital input terminal; The phase current measurement signal of the measurement unit is mapped to the secondary terminal of the current transformer; Map the circuit breaker position status signal to the circuit breaker position contact terminal.

[0014] As a preferred embodiment, the structured engineering model file is used to automatically generate or update the intelligent electronic equipment configuration information and protection setting references in the substation configuration description file conforming to the IEC 61850 standard.

[0015] Thirdly, the present invention provides an electronic device, the computer device including a memory, a processor and a computer program, wherein when the computer program is executed by the processor, it implements the automatic engineering configuration generation method as described in the second aspect.

[0016] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the automatic generation method for engineering configuration as described in the second aspect.

[0017] Compared with the prior art, the present invention has the following beneficial effects: 1. This invention, by constructing a standardized functional model library and physical terminal models, and introducing an automatic mapping mechanism based on semantic matching, transforms the traditional complex process of engineers manually looking up tables and configuring data point by point into a process where the system automatically completes the entire process of function selection, signal mapping, instantiation, and model file generation. This greatly reduces repetitive manual labor, shortens the engineering configuration cycle, and significantly improves design efficiency.

[0018] 2. The system's built-in standardized mapping rules and automatic verification mechanism ensure the logical correctness and uniqueness of the connections between functional signals and physical terminals, overcoming problems such as mismatches and omissions that are easily caused by manual configuration. At the same time, the multi-level engineering model automatically generated based on a unified data source guarantees a high degree of consistency between functional configurations, parameter settings, physical wiring, and communication references, reducing the risk of engineering errors due to data inconsistencies from the outset.

[0019] 3. This invention deeply adheres to and integrates the IEC 61850 standard system. The functional model is directly built based on standard logical nodes, and the generated engineering model file is naturally compatible with standard SCD / ICD and other file formats, facilitating seamless integration and data exchange with other substation automation tools and equipment that comply with the same standard, thereby enhancing the system's openness and interoperability.

[0020] 4. The system's template management and differentiated derivation functions allow mature engineering configurations to be compiled into standard templates. When faced with similar new projects, these templates can be directly reused or new configurations can be quickly derived based on differences, achieving standardized accumulation and efficient reuse of engineering experience. This not only ensures consistent design quality for similar projects but also significantly improves the configuration speed for batch projects or series of products.

[0021] 5. The generated structured engineering model file serves as a unified and authoritative engineering data source, which can be directly called by subsequent tuning calculations, secondary design, schematic generation, and operation and maintenance management toolchains. This data-driven model ensures information synchronization throughout the entire process from logical configuration to physical design and document output, effectively solving the problems of data disconnection and inconsistency between drawings and configurations in traditional processes.

[0022] Further or more detailed beneficial effects will be described in conjunction with specific embodiments in the detailed implementation. Attached Figure Description

[0023] 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 these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of the automatic engineering configuration generation system described in Embodiment 1 of the present invention.

[0025] Figure 2 This is a schematic diagram of the relay protection function model library module described in Embodiment 1 of the present invention.

[0026] Figure 3 This is a schematic diagram showing the mapping relationship between the functional model and physical terminals described in Embodiment 1 of the present invention.

[0027] Figure 4 This is a schematic diagram of the engineering instantiation process described in Embodiment 1 of the present invention.

[0028] Figure 5 This is a schematic diagram of the engineering model file structure described in Embodiment 1 of the present invention.

[0029] Figure 6 This is a schematic diagram of the template reuse and differentiated derivation process described in Embodiment 1 of the present invention.

[0030] Figure 7 This is a structural diagram of the electronic device described in Embodiment 3 of the present invention.

[0031] Icon labels: 700. Electronic equipment; 701. Processor; 702. Communication bus; 703. User interface; 704. Network interface; 705. Memory. Detailed Implementation

[0032] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0033] In the following description, several embodiments of the present invention are provided. Different embodiments can be substituted or combined. Therefore, the present invention can also be considered to include all possible combinations of the same and / or different embodiments described. Thus, if one embodiment includes features A, B, and C, and another embodiment includes features B and D, then the present invention should also be considered to include embodiments containing one or more other possible combinations of A, B, C, and D, even if such embodiments are not explicitly described in the following text.

[0034] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the described elements without departing from the scope of the invention. Various processes or components may be appropriately omitted, substituted, or added to the various examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into other examples.

[0035] To facilitate a better understanding of the embodiments of the present invention, its application scenarios will be explained before providing a detailed explanation of the specific implementation methods.

[0036] The automatic engineering configuration generation system and method described in the embodiments of this specification are applied to the field of automated design and configuration of power system relay protection engineering. In these scenarios, the application of the automatic engineering configuration generation system and method aims to solve problems such as the disconnect between functional models and physical structures, reliance on manual instantiation, low configuration efficiency, and susceptibility to errors during the configuration process of relay protection engineering. By realizing the automatic fusion and processing of functional models, physical terminal models, and engineering data, the system and method improve the automation level, standardization, and reusability of engineering design.

[0037] The following is a brief explanation of the IEC61850 standard, logic nodes, logic devices, relay protection function templates, physical terminal models, signal ports, engineering instantiation, and structured engineering model files involved in the various embodiments of this specification: The IEC 61850 standard, developed by the International Electrotechnical Commission (IEC), is a communication network and system standard for substation automation systems. It provides a unified framework for information modeling, data exchange, and engineering configuration of power equipment, and is fundamental for achieving equipment interoperability and system integration. In this invention, this standard serves as the core basis for constructing the relay protection functional model and communication reference layer.

[0038] A logical node (LN) is the smallest reusable modeling unit in the IEC 61850 standard used to represent a specific function or device component in a power system. Each logical node consists of a set of data objects (DOs) with clearly defined semantics. In this invention, logical nodes are the basic elements for constructing relay protection functional models (such as distance protection PDIS, overcurrent protection PTOC, etc.).

[0039] A logical device (LD) is a virtual device entity in the IEC 61850 standard, typically corresponding to an actual physical device (such as a relay protection device) or a defined set of functions. A logical device contains one or more associated logical nodes. In this invention, the project instantiation process generates a dedicated logical device instance for each target project and assigns it a unique name.

[0040] The relay protection function template is a predefined, reusable protection function configuration scheme based on IEC 61850 logic nodes. It not only includes the logic nodes and their data objects and attributes specified in the standard, but also defines the logical relationships between function blocks, internal parameters, and signal ports for external interaction. The template is stored in a structured format, serving as the basic unit for function selection and instantiation in this invention.

[0041] A physical terminal model is a digital description of the actual hardware connection interface of a relay protection device. It represents the device's physical structure hierarchy, typically including boards, connectors, terminal blocks, etc., and defines the electrical and functional attributes of each terminal, such as: type (analog / digital), direction (input / output), functional domain (protection / measurement / control), and geometric location information. This model is the basis for automatically associating functional signals with physical wiring.

[0042] A signal port is a logical interface point defined in a relay protection function template or model for exchanging information with external systems or other functional blocks. Each signal port has specific attributes, including signal type (such as trip command, measured value), direction (input or output), functional domain, and electrical phase (A, B, C, zero sequence, etc.). These attributes are key parameters for semantic matching during function-physical automatic mapping.

[0043] Project instantiation refers to the process of specifying a selected general relay protection function template and physical terminal model based on the primary system parameters (such as substation name, bay information, voltage level, transformer ratio, etc.) and functional requirements of a specific project. This process generates project-specific logical device names, logical node instance numbers, parameter sets, and a list of actually enabled functions, transforming the general template into a configuration suitable for a specific project.

[0044] The structured engineering model file is a comprehensive configuration file generated by the system of this invention, integrating multi-layered engineering information. It adopts machine-readable structured data formats such as XML and JSON, and includes at least a functional model layer, a physical terminal model layer, and an engineering parameter layer, and can be extended to include a communication reference layer. This file serves as a data carrier containing complete engineering configuration information, and can be directly parsed and used by subsequent configuration tools, tuning software, and design systems.

[0045] Example 1: This embodiment provides an automatic engineering configuration generation system based on the mapping between relay protection function models and physical terminals, such as... Figure 1 As shown, the system includes the following modules: The relay protection function model library module stores relay protection function templates built based on the IEC 61850 standard logical node (LN) model architecture. For example... Figure 2 As shown, the relay protection function template includes at least the following: distance protection PDIS, overcurrent protection PTOC / PDIR, trip logic PTRC, reclosing logic RREC, circuit breaker logic XCBR / CSWI, measurement unit MMXU, and transformer model TCTR / TVTR logic nodes and their data objects DO and data attributes DA. For further refinement, the pre-set line protection function template includes at least: PDIS1..n (multi-segment line distance protection, distinguishing between phase-to-phase and ground distance protection), PTOC_OC1..3 (three-segment phase overcurrent protection), PTOC_EF1..3 (three-segment zero-sequence overcurrent protection), PDIR1..k (directional overcurrent element), PTRC (comprehensive trip logic), RREC (reclosing logic), XCBR (line circuit breaker logic), MMXU (voltage, current, active power, reactive power, and frequency measurement), and TCTR / TVTR (current / voltage transformer model).

[0046] The physical terminal model management module is used to manage the physical terminal models of relay protection devices. The physical terminal models include information on the type, orientation, and functional domain attributes of the terminals. The physical terminal models can optionally be obtained through an external electrical annotation-driven physical model building system.

[0047] The function-physical mapping module is used to automatically map the input / output signal type, direction, functional domain, and phase information of the signal ports in the relay protection function model to the corresponding terminals or terminal groups in the physical terminal model. For example... Figure 3 As shown, the specific mapping rules include: 1. Map the protection action output signals such as PDIS.Op.general and PTOC.Op.general to the trip terminal group; 2. Map the function activation and measurement input signals of PTOC.Str, PDIR.Str, MMXU.A.phsA, etc. to the CT / VT terminal group; 3. Map the status and control signals such as XCBR.Pos.stVal, XCBR.Tr, and XCBR.OpCnt to the circuit breaker position contacts and operating circuit terminals.

[0048] During the mapping process, priority is given to mapping if the type, direction, functional domain, and phase all match, and a verification alarm is given for cases of conflict or mismatch.

[0049] The project instantiation module is used to instantiate the selected relay protection function template and physical terminal model based on the primary system configuration data of the project, including the substation name, bay name, voltage level, CT / VT ratio, and the set of protection functions enabled for the target project. This generates project-specific logical device (LD) names, logical node (LN) instance numbers, function enablement sets, and project parameters. Specifically, the operation flow of this module is as follows: Figure 4 As shown, the following information is automatically generated: 1. Project-specific logical device (LD) name, including line name or bay (Bay) prefix; 2. A set of logical node (LN) instances and their instance numbers, such as PDIS1, PTOC1..3, PTOC_EF1..3, XCBR1; 3. Engineering parameter set, including CT / VT ratio, rated voltage, current rating, line length, and protection setting scenario identification; 4. Project Enabled Protection Function List, which records the protection function blocks actually enabled in the target project.

[0050] The engineering model generation module is used to automatically generate engineering model files for relay protection devices based on functional models, physical terminal models, and engineering instance information. For example... Figure 5 As shown, the engineering model file contains at least the following four levels: 1. Functional model layer, used to describe LD / LN structure, DO / DA data items, protection function activation status, and logical relationships between functions; 2. Physical terminal model layer, used to describe the physical topology of terminals, boards, connectors, and the electrical properties of terminals; 3. Engineering Parameter Layer: This layer describes the primary system parameters of the project, including substation, bay, voltage level, CT / VT ratio, and line type. 4. Communication reference layer, used to reference IEC 61850 communication models and message mapping information generated by other systems.

[0051] The template reuse and differentiation derivation module is used to identify differences in the functional configurations and physical terminal mappings of different engineering instances, generate a difference mapping table, and derive new relay protection function templates or engineering templates based on the difference mapping table. For example... Figure 6 As shown, template derivation is achieved through the following steps: 1. Perform difference identification on engineering model files for different engineering instances, and enable statistical protection functions for differences in physical terminal mapping and engineering parameters; 2. Automatically generate new relay protection function templates or project templates based on the difference mapping table for rapid configuration in subsequent projects; 3. Record the derivation relationship in the version management database to track the template evolution process.

[0052] The project file export module is used to export the project model file into structured file formats such as XML and / or JSON. The XML / JSON file contains a unique project model identifier, device identifier, and version number for use by project configuration tools, tuning software, and secondary design toolchains.

[0053] Example 2: This embodiment provides an automatic generation method for engineering configuration based on the mapping of relay protection function model and physical terminals. The method is based on the system described in Embodiment 1 and includes the following steps: Step S1: Obtain the physical terminal model of the relay protection device.

[0054] The physical terminal model includes connectors, terminals, and terminal attribute information. The physical terminal model can be imported from an external system or manually built within this system.

[0055] Step S2: Load the relay protection function model library and select the set of protection function templates required for the target project.

[0056] The functional model library contains pre-built templates for various protection functions based on the IEC 61850 standard, such as distance protection (PDIS), overcurrent protection (PTOC / PDIR), tripping logic (PTRC), and reclosing (RREC). Based on engineering design requirements, the required functional templates are selected from the library to form a set.

[0057] Step S3: Execute function - physical mapping.

[0058] Based on the type, direction, functional domain, and phase information of the signal ports in the selected functional template set, the input / output signals of the functional model are automatically mapped to the corresponding terminals or terminal groups in the physical terminal model. Specific mapping rules include: Map the trip output signals of distance protection or overcurrent protection (such as PDIS.Op.general, PTOC.Op.general) to the trip circuit terminals; Map the overcurrent protection activation signals (such as PTOC.Str, PDIR.Str) to the digital input terminals; The phase current measurement signals (such as MMXU.A.phsA, MMXU.A.phsB, MMXU.A.phsC) of the measurement unit are mapped to the secondary terminals of the current transformer (CT); Map the circuit breaker position status signal (such as XCBR.Pos.stVal) to the circuit breaker position contact terminal.

[0059] Step S4: Perform project instantiation.

[0060] Based on the primary system configuration data of the target project (such as substation name, bay name, voltage level, CT / VT ratio, etc.) and the set of protection functions enabled in the project design, the selected function templates and physical terminal models are instantiated. This step includes: The function template is trimmed based on the set of enabled functions, keeping only the actually enabled function blocks; Generate a project-specific instance number (such as PDIS1, PTOC1, etc.) for each enabled function block and initialize the project parameters; Generate a set of logic device (LD) names, logic node (LN) instance sets, and project parameter sets specific to the project, including parameters such as transformer ratio, rated voltage, and line length.

[0061] Step S5: Build the project model file.

[0062] Based on the functional model, physical terminal model, and engineering instantiation results, a data structure for the relay protection device engineering model is constructed, forming a structured engineering model file. This file should include at least: Functional Model Layer: Describes the instantiated LD / LN structure, data objects and data attributes, function activation status, and logical relationships; Physical terminal model layer: describes the physical topology of terminals, boards, and connectors, as well as the electrical properties of the terminals; Engineering parameter layer: Records primary system parameters and customized engineering parameters.

[0063] In addition, the file can also include a communication reference layer (used to reference IEC 61850 communication model and message mapping information) and a geometric information layer. The engineering model file contains a unique engineering model identifier, a unique device identifier, a version number, and corresponding template source information.

[0064] Step S6: Export the project model file.

[0065] The engineering model file is output in XML and / or JSON format for use by downstream relay protection configuration tools, setting software, and secondary design toolchains. This file can be used to automatically generate or update intelligent electronic device (IED) configuration information, protection setting references, and engineering specification documents in substation configuration description files conforming to the IEC 61850 standard.

[0066] Optional step S7: Template reuse and differential derivation.

[0067] After generating the engineering model files, the system can perform difference analysis on the model files of multiple projects, identifying and outputting differences in areas such as protection function activation, physical terminal mapping, and engineering parameters. Based on these differences, the system can automatically generate new functional templates or engineering templates for rapid configuration in subsequent similar projects, enabling the accumulation and reuse of engineering knowledge.

[0068] Through the above steps, this embodiment achieves full automation of the process from physical model acquisition, functional template selection, automatic mapping, project instantiation to model file generation and export, significantly improving project configuration efficiency, consistency and reusability.

[0069] Example 3: like Figure 7 As shown, this embodiment provides an electronic device, which may include: at least one processor, at least one network interface, a user interface, a memory, and at least one communication bus.

[0070] The communication bus can be used to enable communication between the various components mentioned above.

[0071] The user interface may include buttons, and optional user interfaces may also include standard wired interfaces and wireless interfaces.

[0072] The network interface may include, but is not limited to, Bluetooth modules, NFC modules, Wi-Fi modules, etc.

[0073] The processor may include one or more processing cores. It connects various parts of the electronic device via various interfaces and lines, executing instructions, programs, code sets, or instruction sets stored in memory, and accessing data stored in memory to perform various functions and process data. Optionally, the processor can be implemented using at least one hardware form of DSP, FPGA, or PLA. The processor may integrate one or more of the following: CPU, GPU, and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content required for display; and the modem handles wireless communication. It is understood that the modem may also be implemented as a separate chip without being integrated into the processor.

[0074] The memory may include RAM or ROM. Optionally, the memory may include a non-transitory computer-readable medium. The memory can be used to store instructions, programs, code, code sets, or instruction sets. The memory may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor. The memory, as a computer storage medium, may include an operating system, a network communication module, a user interface module, and automatically generated applications. The processor can be used to call the automatically generated applications stored in the memory and execute the steps of automatically generating engineering configurations mentioned in the foregoing embodiments.

[0075] Example 4: This embodiment provides a computer-readable storage medium storing instructions that, when executed on a computer or processor, cause the computer or processor to perform one or more steps as described in Embodiment 1. If the constituent modules of the above-described electronic device are implemented as software functional units and sold or used as independent products, they can be stored in the computer-readable storage medium.

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

[0077] Those skilled in the art will understand that all or part of the processes in the methods of Embodiment 2 described above can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks. Unless otherwise specified, the technical features of this embodiment and the implementation scheme can be combined arbitrarily.

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

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

[0080] The above description is merely an exemplary embodiment of the present invention and should not be construed as limiting the scope of the invention. Any equivalent changes and modifications made in accordance with the teachings of this invention are still within the scope of this invention. Those skilled in the art will readily conceive of embodiments of the invention upon considering the specification and practicing the disclosure herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not described herein. The specification and embodiments are to be considered exemplary only, and the scope and spirit of the invention are defined by the claims.

Claims

1. An automatic engineering configuration generation system based on the mapping of relay protection function models and physical terminals, characterized in that, include: The relay protection function model library module is used to store relay protection function templates built based on the IEC61850 standard logic nodes; The physical terminal model management module is used to manage the physical terminal model of the relay protection device. The physical terminal model includes terminal type, orientation, and functional domain attribute information. The function-physical mapping module is used to automatically map the signal ports in the relay protection function model to the corresponding terminals or terminal groups in the physical terminal model according to the type, direction, functional domain and phase information of the signal ports; The engineering instantiation module is used to instantiate the relay protection function template and the corresponding physical terminal model selected from the relay protection function model library module according to the primary system configuration data of the target project, and generate the logical device structure and engineering parameters corresponding to the project. The engineering model generation module is used to generate a structured engineering model file containing a functional model layer, a physical terminal model layer, and an engineering parameter layer based on the instantiation and mapping results.

2. The automatic engineering configuration generation system based on the mapping of relay protection function model and physical terminals as described in claim 1, characterized in that, The functional-physical mapping module executes the following mapping rules: Map the protection action output signal to the trip terminal group; Map the protection activation and measurement input signals to the current transformer terminal group; The circuit breaker status and control signals are then mapped to the operating circuit terminals.

3. The automatic engineering configuration generation system based on the mapping of relay protection function model and physical terminals as described in claim 1, characterized in that, The project instantiation module automatically generates the following information based on the initial system configuration data: The logical device name includes a prefix for the line or bay name, a set of logical nodes with instance numbers, a set of engineering parameters including transformer ratios and voltage levels, and a list of protection functions actually enabled.

4. The automatic engineering configuration generation system based on the mapping of relay protection function model and physical terminals as described in claim 1, characterized in that, Also includes: The template reuse and differentiation derivation module is used to compare structured engineering model files of different projects, identify differences in function activation, terminal mapping and parameters, and generate new function or project templates based on the differences.

5. The automatic engineering configuration generation system based on the mapping of relay protection function model and physical terminals according to claim 1, characterized in that: The engineering model file generated by the engineering model generation module includes a communication reference layer, which is used to reference the IEC61850 communication model.

6. A method for automatically generating engineering configurations based on the system described in any one of claims 1 to 5, characterized in that, The method includes the following steps: Obtain the physical terminal model of the relay protection device; Select the required set of relay protection function templates from the relay protection function model library; Based on the type, direction, functional domain, and phase information of the signal ports in the functional template set, the signal ports are automatically mapped to the corresponding terminals or terminal groups in the physical terminal model; Based on the primary system configuration data of the target project, the functional template set and physical terminal model are instantiated to generate the logical device structure, logical node instance and project parameters corresponding to the project. By integrating the instantiation results and mapping relationships, a structured engineering model file containing a functional model layer, a physical terminal model layer, and an engineering parameter layer is constructed and exported.

7. The automatic generation method for engineering configuration according to claim 6, characterized in that, The automatic mapping specifically refers to: Map the trip output signal of distance protection or overcurrent protection to the trip circuit terminal; Map the overcurrent protection start signal to the digital input terminal; The phase current measurement signal of the measurement unit is mapped to the secondary terminal of the current transformer; Map the circuit breaker position status signal to the circuit breaker position contact terminal.

8. The automatic generation method for engineering configuration according to claim 6, characterized in that: The structured engineering model file is used to automatically generate or update the intelligent electronic equipment configuration information and protection setting references in the substation configuration description file that conforms to the IEC 61850 standard.

9. A computer device, the computer device comprising a memory, a processor, and a computer program, characterized in that, When the computer program is executed by the processor, it implements the automatic generation method for engineering configuration as described in any one of claims 6 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the automatic generation method for engineering configuration as described in any one of claims 6 to 8.

Images