Relay protection heterogeneous data conversion method, system, equipment and medium

Abstract

The invention discloses a relay protection heterogeneous data conversion method, system, equipment and medium, which simplifies the coupling relationship between heterogeneous systems by introducing a unified meta-model data structure as an intermediate standard layer, compulsorily aligns all possible data contents by using a set of last shift, and realizes the conversion of the heterogeneous data by enabling each source format to correspond to one adapter. The adapter is responsible for extracting, converting and filling a source value into a super template according to a machine readable mapping specification, the interaction effect of different data structures is improved, then instances are verified on a unified semantic level, wrong data are intercepted, the efficiency is improved, and the efficiency is improved by converting the verified instances into a format capable of being read by a target system. And multi-end multiplexing of one piece of data can be realized, so that expansion and maintenance of the system are greatly facilitated.

Description

Technical Field

[0001] This invention relates to the field of data interaction technology, specifically to a method, system, device, and medium for converting heterogeneous data in relay protection. Background Technology

[0002] Relay protection is a crucial component in ensuring the safe and stable operation of power systems. The accurate and efficient flow of related data is fundamental to the design, testing, and maintenance of protection systems. Currently, when processing heterogeneous relay protection data from different manufacturers and software, the following technical challenges exist in both design and implementation:

[0003] First, the lack of unified interface protocols leads to severe information silos. In the traditional relay protection ecosystem, protection devices from different manufacturers use proprietary setting file formats (such as XML, binary, or plain text), and different simulation software have incompatible model files (such as MDL and SLX). This results in serious data barriers, making it difficult to achieve seamless and automated flow and integration of various types of data.

[0004] Second, the development model is rigid, resulting in high integration costs and timelines. In the traditional "point-to-point" integration model, achieving interoperability between N heterogeneous systems requires developing nearly N² dedicated interfaces. Whenever a new device or software is added to the system, a new interface needs to be developed to interface with all other systems. This development model not only leads to a large amount of low-level repetitive work, significantly increasing the waste of R&D resources and project timelines, but also makes the entire information system exceptionally vulnerable and unable to adapt to the rapidly evolving needs of the future power grid.

[0005] Third, the lack of unified data verification makes it difficult to guarantee the reliability of the data transfer process. Because data is directly converted between various proprietary interfaces, a standardized intermediate verification step is lacking. Data output from one system, even if it contains formatting errors, missing information, or logical contradictions, may be directly fed into the next system, posing serious security risks to subsequent simulation analysis and operational decisions. Developers need to design separate verification logic for each interface, further increasing the development burden and making it difficult to ensure the consistency of verification rules. Therefore, how to provide a new technological solution that can break down information barriers, reduce integration complexity, and improve the reliability of data transfer is a pressing technical problem that needs to be solved in the field of relay protection. Summary of the Invention

[0006] The technical problems to be solved by this invention are the lack of unified interfaces for heterogeneous data in relay protection, high integration and development costs, and low data reliability. The aim is to provide a method, system, device, and medium for converting heterogeneous data in relay protection. By introducing a unified meta-model data structure as an intermediate standard layer, the coupling relationship between heterogeneous systems is simplified. A single template is used to force alignment of all possible data content. Each source format corresponds to an adapter, which is responsible for extracting, converting, and filling the source values ​​into a super template according to machine-readable mapping specifications, improving the interaction efficiency of different data structures. Then, instances are validated at a unified semantic level to intercept erroneous data, improving efficiency. By converting validated instances into a format readable by the target system, a single set of data can be reused across multiple devices, greatly facilitating system expansion and maintenance.

[0007] This invention is achieved through the following technical solution:

[0008] The first aspect of this invention provides a method for converting heterogeneous data in relay protection, specifically including the following steps:

[0009] A unified meta-model data structure is constructed based on heterogeneous source data types in relay protection.

[0010] Retrieve heterogeneous data source files and their uniquely corresponding input adapters, map the heterogeneous data sources to a unified metamodel data structure, and generate a unified metamodel data instance.

[0011] Perform standardized data validation on unified metamodel instances;

[0012] The unified metamodel instance, after standardization and data validation, is output in a data format recognizable by the target system.

[0013] Furthermore, the heterogeneous source data types of the relay protection include: device physical information, protection setting information, protection logic topology information, and fault recording information.

[0014] Furthermore, the unified meta-model data structure defines the following fields: protection zone number (integer type), protection status (Boolean type), resistance setting (numerical type), reactance setting (numerical type), and action delay (numerical type). Among these, the zone number, resistance setting, and reactance setting are mandatory fields.

[0015] Furthermore, the step of mapping heterogeneous data sources to a unified metamodel data structure to generate unified metamodel data instances specifically includes:

[0016] Based on the specified heterogeneous data source file and its type, invoke the input adapter that uniquely corresponds to that type;

[0017] The input adapter has a built-in mapping specification file corresponding to the heterogeneous data source files and their type formats. The mapping specification file is used to store the field-level mapping relationship between the data format of the heterogeneous data source defined in a structured declaration manner and the internal data model.

[0018] Based on the built-in mapping relationship of the input adapter, the input data that conforms to the data format of the heterogeneous data source is parsed into the unified metamodel data structure to generate a unified metamodel data instance.

[0019] Furthermore, the step of parsing the input data conforming to the data format of the heterogeneous data source into a unified metamodel data structure based on the mapping relationship built into the input adapter specifically includes:

[0020] Call the parser corresponding to the heterogeneous data source format to load the heterogeneous data source file into a structured data object in memory;

[0021] The input adapter uniquely corresponding to this type is invoked to traverse and execute each mapping rule in the mapping specification file, extracting the original value from the structured data object based on the heterogeneous data source locator;

[0022] The original value is processed by calling the specified data conversion function to obtain a valid value that conforms to the target format;

[0023] Fill valid values ​​that conform to the target format into the newly created unified metamodel data instance at the location specified by the target unified metamodel data structure field path.

[0024] Furthermore, the mapping specification file includes:

[0025] Source data locator is an expression used to uniquely identify a data item in the source data; its form is related to the source data format.

[0026] The target unified metamodel data structure field path is an expression used to uniquely identify a target field in a unified metamodel data instance;

[0027] Data transformation functions are executable logical units used to process source data values ​​into the format required by the target unified meta-model data structure fields.

[0028] Furthermore, the standardized data validation of the unified metamodel instance specifically includes:

[0029] Data integrity check is used to check for any missing required fields.

[0030] Data compliance checks are used to verify whether values ​​are within a reasonable range.

[0031] And data consistency checks, used to check whether there are logical contradictions between different set values.

[0032] A second aspect of the present invention provides a system applied to a method for converting heterogeneous data in relay protection, comprising:

[0033] The unified metamodel building module is used to predefine and store unified metamodel data structures that are independent of any specific source format based on heterogeneous source data types in the field of relay protection.

[0034] An input adapter library stores several input adapters corresponding to the heterogeneous source data types. Each input adapter has a built-in machine-readable mapping specification and parsing logic driven by the mapping specification, which is used to parse and map heterogeneous data source files of the corresponding type into unified metamodel data instances that conform to the unified metamodel data structure.

[0035] The standardized validation engine is connected to the output of the input adapter library and is used to perform standardized data validation on the unified metamodel data instance for field requirement, data type, value range and business rules, and output the validated standardized unified metamodel instance.

[0036] The output conversion module is connected to the output end of the standardized verification engine and is used to convert the standardized unified meta-model instance into a data format that the target system can recognize and output it.

[0037] A third aspect of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement a method for converting heterogeneous data for relay protection.

[0038] A fourth aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a method for converting heterogeneous data in relay protection.

[0039] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0040] By introducing a unified metamodel data structure as an intermediate standard layer, the coupling relationship between heterogeneous systems is simplified. A single template is used to force the alignment of all possible data content. Each source format corresponds to an adapter, which is responsible for extracting, transforming, and filling the source values ​​into the super template according to machine-readable mapping specifications, thereby improving the interaction efficiency of different data structures. Then, instances are validated at a unified semantic level to intercept erroneous data and improve efficiency. By converting validated instances into a format that the target system can read, a single set of data can be reused across multiple platforms, greatly facilitating system expansion and maintenance. Attached Figure Description

[0041] To more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of the present invention and should not be considered as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort. In the drawings:

[0042] Figure 1 This is a flowchart of the data transformation method in an embodiment of the present invention;

[0043] Figure 2 This is a schematic diagram of the overall system architecture in an embodiment of the present invention. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the embodiments and accompanying drawings. The illustrative embodiments and descriptions of the present invention are only used to explain the present invention and are not intended to limit the present invention.

[0045] Example 1, as one possible implementation, such as Figure 1 As shown, this embodiment provides a method for converting heterogeneous data in relay protection, including the following steps: constructing a unified metamodel data structure based on the heterogeneous source data types of relay protection; retrieving heterogeneous data source files and their uniquely corresponding input adapters, mapping the heterogeneous data sources to the unified metamodel data structure, and generating unified metamodel data instances; performing standardized data verification on the unified metamodel instances; and outputting the standardized data-verified unified metamodel instances in a data format recognizable by the target system. This embodiment simplifies the coupling relationship between heterogeneous systems by introducing a unified metamodel data structure as an intermediate standard layer. It forces the alignment of all possible data content using a single template, with each source format corresponding to an adapter. The adapter is responsible for extracting, converting, and filling the source values ​​into the super template according to machine-readable mapping specifications, improving the interaction efficiency of different data structures. Then, the instances are verified at a unified semantic level to intercept erroneous data, improving efficiency. By converting the verified instances into a format readable by the target system, a single set of data can be reused across multiple platforms, greatly facilitating system expansion and maintenance.

[0046] The specific implementation methods of this embodiment are as follows:

[0047] Step 1: Construction of the Unified Meta-Model (UMM) for Relay Protection. Following the design principles of high cohesion and low coupling, a standardized, hierarchical data structure, the Unified Meta-Model (UMM), is pre-constructed, independent of any specific hardware vendor or software platform. This UMM serves as the hub for data exchange, and its internal structure is sufficient to comprehensively describe various core information in the relay protection field, including at least: device physical information, protection setting information, protection logic topology information, and fault recording information. The UMM itself is a standard definition of a data structure, providing a unified target paradigm and semantic foundation for the mapping rules in subsequent steps.

[0048] Step Two: Mapping and Population of Heterogeneous Data Sources to the Unified Metamodel. Based on the specified heterogeneous data source file and its type, the input adapter uniquely corresponding to that type is invoked. The input adapter has built-in parsing logic for that specific format. The input adapter's functionality is driven by a machine-readable mapping specification, which defines the mapping relationship from the source data schema to the Unified Metamodel (UMM) schema. The mapping specification includes the following core components:

[0049] Source data locator: An expression used to uniquely identify a data item in the source data. Its form is related to the source data format. For example, for XML format, the locator is an XPath expression; for JSON format, it is a JSONPath expression.

[0050] Target UMM field path: An expression used to uniquely identify a target field in a UMM instance, reflecting the hierarchical structure of the UMM.

[0051] Data conversion function: An executable logical unit used to process source data values ​​into the format required by the target UMM field, which includes at least one of data type conversion, numerical scaling, unit conversion or enumeration value mapping.

[0052] For example, a specific mapping rule can be expressed as: elements in the source XML data <setting name="TZ"> 50< / setting> The value is located via its XPath path, and after unit and type conversion by the data conversion function, it is filled into the Protection.Settings["TZ"].value field of the UMM instance.

[0053] The input adapter invokes the parser corresponding to the source format, loading the source file as a structured data object in memory. The adapter iterates through and executes each mapping rule in the mapping specification: extracting raw values ​​from the structured data object based on the source data locators; processing these raw values ​​by calling the specified data transformation function to obtain valid values ​​conforming to the target format; and finally, filling these valid values ​​into the newly created UMM instance at the location specified by the target UMM field path. This completes the conversion from a specific data format to a unified metamodel.

[0054] Step 3: Standardized Data Validation Based on a Unified Metamodel. After the UMM instance is populated, a unified data validation engine is started. This differs fundamentally from existing technologies that perform fragmented validation across various private interfaces for specific formats. This invention implements centralized and unified validation at the standardized UMM level, ensuring the uniqueness and comprehensiveness of the validation rules.

[0055] The validation engine relies on a "validation rule base" bound to the UMM Schema. This rule base defines the validation logic declaratively, and the engine performs automated validation by interpreting and executing these rules. The specific processing steps include:

[0056] 1. Data Integrity Check: The engine iterates through the list of required fields marked in the UMM Schema and checks whether the corresponding fields in the UMM instance have valid values.

[0057] 2. Data compliance check: The engine calls the validators predefined for specific fields in the rule base. For example, it checks whether numeric fields fall within the preset minimum and maximum ranges, whether the values ​​of enumerated fields are in the allowed enum list, or uses regular expressions to verify whether the string format conforms to the pattern.

[0058] 3. Data consistency check: The engine executes cross-field rules defined in the rule base to check the numerical logical relationship between multiple fields. For example, it verifies whether the impedance setting of "Zone1" is less than the impedance setting of "Zone2", or checks whether the protection action time limit of each segment meets the step-increment coordination principle.

[0059] If any verification rule is not met, the engine will interrupt the process and generate a detailed verification report; if all verifications pass, the UMM instance will be marked as trusted and passed to subsequent steps.

[0060] Step Four: Mapping and Generation of the Unified Metamodel to the Target Application System. Based on the specified target application system and its type, the output adapter uniquely corresponding to that type is invoked. Its core function is to reverse-convert standard UMM data into a target system-specific format according to the specific interface requirements of the target system. This output adapter reads the UMM instance that has passed data verification and converts it into a data format recognizable by the target system according to its interface requirements. For example, if the target system is an RTDS real-time simulation platform, a dedicated TCL script adapter is invoked to convert the fixed-value data in the UMM instance into TCL script commands that can be recognized and executed by the platform. Furthermore, this invention also provides a system for implementing the above method. This system includes: a database or template library for storing the Unified Metamodel (UMM) data structure; a modular adapter library containing multiple input / output adapters; and a data conversion engine for scheduling and executing the above data conversion and verification process.

[0061] Example 2, as a possible implementation method, provides an application scenario of a method for converting heterogeneous data in relay protection. By automatically converting the XML setting file of a type A protection device from a mainstream manufacturer into a specific engineering example of the script commands required by a real-time digital simulation platform, this example demonstrates how a method for converting heterogeneous data in relay protection is applied.

[0062] Step 1: Construction of the Unified Meta-Model (UMM) for Relay Protection. Taking the distance protection setting area as an example, its data structure defines the following core fields: protection area number (integer type), activation / deactivation status (Boolean type), resistance setting (numerical type), reactance setting (numerical type), and action delay (numerical type). The area number, resistance, and reactance settings are specified as mandatory fields. This UMM definition serves as the foundation of the system and is stored in the template library for subsequent steps to call upon.

[0063] Step Two: Mapping and Population of Heterogeneous Data Sources to the Unified Metamodel. In this step, a specific source file, device_settings.xml, is processed. This file contains a list of distance protection settings, where the first setting specifies: zone 1, in operation, resistance setting of 0.85 ohms, reactance setting of 4.92 ohms, and action delay of 0.0 seconds. The input adapter parses this source file and, according to preset mapping rules, extracts and populates the above data into the corresponding fields of a new UMM instance, thus completing the conversion from a specific format to the unified metamodel.

[0064] Step 3: Standardized Data Validation Based on the Unified Metamodel. In this step, the data transformation engine performs standardized data validation on the UMM instance generated in the previous step. In this embodiment, the validation logic includes at least:

[0065] Integrity Check: The conversion engine performs standardized validation on the UMM instance generated in the previous step. The validation logic includes: checking the existence of required fields (such as region, resistance, and reactance); and verifying that numerical fields (such as resistance and reactance) are greater than zero and conform to physical meaning. If the validation fails, the process is interrupted and an alarm is triggered; if the validation passes, the UMM instance is passed to the next step.

[0066] Step 4: Mapping and Generation of the Unified Meta-Model to the Target Application System. The data conversion engine calls the corresponding output adapter based on the target system. This adapter reads the validated UMM instance and, according to the script specifications required by the platform, converts the setpoint data in the UMM into a series of parameter setting commands. Specifically, it maps the resistance setpoint 0.85 to the command set_param...R_Set0.85, the reactance setpoint 4.92 to the command set_param...X_Set4.92, and so on, ultimately generating a script file (such as load_settings.tcl) that can be directly executed by the simulation platform.

[0067] Example 3, as one possible implementation, such as Figure 2 As shown, this embodiment provides a system applied to a method for converting heterogeneous data in relay protection, including:

[0068] The unified metamodel building module is used to predefine and store unified metamodel data structures that are independent of any specific source format based on heterogeneous source data types in the field of relay protection.

[0069] An input adapter library stores several input adapters corresponding to the heterogeneous source data types. Each input adapter has a built-in machine-readable mapping specification and parsing logic driven by the mapping specification, which is used to parse and map heterogeneous data source files of the corresponding type into unified metamodel data instances that conform to the unified metamodel data structure.

[0070] The standardized validation engine is connected to the output of the input adapter library and is used to perform standardized data validation on the unified metamodel data instance for field requirement, data type, value range and business rules, and output the validated standardized unified metamodel instance.

[0071] The standardized validation engine includes: a database or template library for storing the unified metamodel data structure;

[0072] A modular adapter library containing multiple of the aforementioned input / output adapters;

[0073] And a data transformation engine for scheduling and executing the above data transformation and verification processes;

[0074] The output conversion module is connected to the output end of the standardized verification engine and is used to convert the standardized unified meta-model instance into a data format that the target system can recognize and output it.

[0075] Among them, the three files—Manufacturer A's setting file, Manufacturer B's model file, and Software waveform recording file—are examples of input data processed by the unified meta-model building module, used to demonstrate the adapter's conversion function. The target system can be a simulation test platform, a cloud-based analysis database, or third-party application software.

[0076] Example 4, as a possible implementation, provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements a method for converting heterogeneous data for relay protection.

[0077] Example 5, as a possible implementation, provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements a method for converting heterogeneous data in relay protection.

[0078] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for converting heterogeneous data in relay protection, characterized in that, The specific steps include the following: A unified meta-model data structure is constructed based on heterogeneous source data types in relay protection. Retrieve heterogeneous data source files and their uniquely corresponding input adapters, map the heterogeneous data sources to a unified metamodel data structure, and generate a unified metamodel data instance. Perform standardized data validation on unified metamodel instances; The unified metamodel instance, after standardization and data validation, is output in a data format recognizable by the target system.

2. The method for converting heterogeneous relay protection data according to claim 1, characterized in that, The heterogeneous source data types of relay protection include: device physical information, protection setting information, protection logic topology information, and fault recording information.

3. The method for converting heterogeneous relay protection data according to claim 1, characterized in that, The unified meta-model data structure defines the following fields: protection zone number (integer type), protection status (Boolean type), resistance setting (numerical type), reactance setting (numerical type), and action delay. Among these, the zone number, resistance setting, and reactance setting are required fields.

4. The method for converting heterogeneous relay protection data according to claim 1, characterized in that, The process of mapping heterogeneous data sources to a unified metamodel data structure and generating unified metamodel data instances specifically includes: Based on the specified heterogeneous data source file and its type, invoke the input adapter that uniquely corresponds to that type; The input adapter has a built-in mapping specification file corresponding to the heterogeneous data source files and their type formats. The mapping specification file is used to store the field-level mapping relationship between the data format of the heterogeneous data source defined in a structured declaration manner and the internal data model. Based on the built-in mapping relationship of the input adapter, the input data that conforms to the data format of the heterogeneous data source is parsed into the unified metamodel data structure to generate a unified metamodel data instance.

5. The method for converting heterogeneous relay protection data according to claim 4, characterized in that, The step of parsing input data conforming to the data format of the heterogeneous data source into a unified metamodel data structure based on the mapping relationship built into the input adapter specifically includes: Call the parser corresponding to the heterogeneous data source format to load the heterogeneous data source file into a structured data object in memory; The input adapter uniquely corresponding to this type is invoked to traverse and execute each mapping rule in the mapping specification file, extracting the original value from the structured data object based on the heterogeneous data source locator; The original value is processed by calling the specified data conversion function to obtain a valid value that conforms to the target format; Fill valid values ​​that conform to the target format into the newly created unified metamodel data instance at the location specified by the target unified metamodel data structure field path.

6. The method for converting heterogeneous relay protection data according to claim 4, characterized in that, The mapping specification file includes: Source data locator is an expression used to uniquely identify a data item in the source data; its form is related to the source data format. The target unified metamodel data structure field path is an expression used to uniquely identify a target field in a unified metamodel data instance; Data transformation functions are executable logical units used to process source data values ​​into the format required by the target unified meta-model data structure fields.

7. The method for converting heterogeneous relay protection data according to claim 1, characterized in that, The standardized data validation of the unified metamodel instance specifically includes: Data integrity check is used to check for any missing required fields. Data compliance checks are used to verify whether values ​​are within a reasonable range. And data consistency checks, used to check whether there are logical contradictions between different set values.

8. A system, characterized in that, The method for converting heterogeneous relay protection data according to any one of claims 1 to 7 includes: The unified metamodel building module is used to predefine and store unified metamodel data structures that are independent of any specific source format based on heterogeneous source data types in the field of relay protection. An input adapter library stores several input adapters corresponding to the heterogeneous source data types. Each input adapter has a built-in machine-readable mapping specification and parsing logic driven by the mapping specification, used to parse and map heterogeneous data source files of the corresponding type into unified metamodel data instances that conform to the unified metamodel data structure; The standardized validation engine is connected to the output of the input adapter library and is used to perform standardized data validation on the unified metamodel data instance for field requirement, data type, value range and business rules, and output the validated standardized unified metamodel instance. The output conversion module is connected to the output end of the standardized verification engine and is used to convert the standardized unified meta-model instance into a data format that the target system can recognize and output it.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method for converting heterogeneous relay protection data as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the method for converting heterogeneous relay protection data as described in any one of claims 1 to 7.

Images