Data service configuration method and system based on resource domain modeling and configuration self-construction

Abstract

The application discloses a data service configuration method and system based on resource field modeling and configuration self-construction, and belongs to the technical field of power secondary equipment management configuration. The method comprises the following steps: according to the current secondary equipment type and the current business demand, corresponding meta-models are matched from the meta-model instantiation templates according to the policy constraint instructions, and instantiated resource points and instantiated functions are generated; the association relationship between the instantiated resource points and the instantiated functions is obtained; the target standard model file is parsed, the association relationship between the target standard model file and the instantiated resource points and the instantiated functions is respectively established, and the association relationship is allocated with a short address mapping relationship, and a target standard model configuration is generated; a standardized interactive description file is generated and deployed to the target power secondary equipment, and a data service configuration result is obtained. The application can solve the problems of non-standard plug-in modeling, complicated target standard model adaptation and low instantiation configuration efficiency.

Description

Technical Field

[0001] This invention relates to the field of power secondary equipment management and configuration technology, and in particular to a data service configuration method and system based on resource domain modeling and configuration self-construction. Background Technology

[0002] Currently, there are widespread problems such as fragmented data interaction and inconsistent interface standards. Data services are deeply coupled with underlying hardware resources (especially real-time computing plugins and human-machine management plugins) and upper-layer business scenarios. This results in a large amount of repetitive hard-coding development required when adapting software to different types of real-time computing plugins and human-machine management plugins, leading to long adaptation cycles, poor reusability, and high expansion costs.

[0003] While current device configuration software can import some plug-in resources, perform simple modeling, and export files in multiple formats, it still adopts a "customized development" model and has not formed a standardized modeling and configuration system. For example, there is a lack of unified standards for resource point modeling and function modeling of real-time computing plug-ins and human-machine management plug-ins, and the modeling logic of different plug-ins is independent of each other. It has not achieved systematic adaptation to the IEC 61850 standard and cannot efficiently complete the resource and function mapping between the 61850 model and the two types of plug-ins. The instantiation configuration process is cumbersome, and the association between resources and functions and the mapping between the 61850 model and plug-in resources all require manual coding, which is prone to errors and difficult to maintain. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide a data service configuration method and system based on resource domain modeling and configuration self-construction. This solves the problems of existing power secondary equipment management software, such as difficulty in adaptation, poor reusability, high expansion cost, non-standard modeling of real-time computing plug-in and human-machine management plug-in, cumbersome adaptation of 61850 model, and low efficiency of instantiation configuration.

[0005] To achieve the above objectives, the present invention is implemented using the following technical solution: On the one hand, this invention provides a data service configuration method based on resource domain modeling and self-configuration, including: Obtain the current secondary equipment type and current business requirements; Based on the current secondary equipment type and current business requirements, the corresponding metamodel is matched from the metamodel instantiation template according to the policy constraint instructions to generate real-time computing plugin instantiation resource points, human-machine management plugin instantiation resource points, real-time computing plugin instantiation functions, and human-machine management plugin instantiation functions. By associating the instantiation resource points of the real-time computing plugin with the instantiation function of the real-time computing plugin, and the instantiation resource points of the human-machine management plugin with the instantiation function of the human-machine management plugin, the relationship between resource points and functions can be obtained. The logical nodes, data objects, and data attributes in the target standard model file are analyzed. The association relationships between the target standard model file and the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, and the instantiation functions of the human-machine management plugin are established respectively. Short address mapping relationships are assigned to the association relationships, and the target standard model configuration is generated. Based on the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, the instantiation functions of the human-machine management plugin, the relationship between resource points and functions, the short address mapping relationship, and the target standard model configuration, a standardized interactive description file is generated and deployed to the target power secondary equipment to obtain the data service configuration result.

[0006] Optionally, the metamodel instantiation template includes a data metamodel, a functional metamodel, a configuration interface control metamodel, and binding rules between the functional metamodel and the data metamodel; The data meta-model includes a real-time computing plugin resource meta-model, a human-machine management plugin resource meta-model, and a target standard resource meta-model. The functional meta-model includes a basic configuration functional meta-model, a real-time computing plugin functional meta-model, a human-machine management plugin functional meta-model, a target standard functional meta-model, and an application instantiation functional meta-model. The configuration interface control metamodel includes the core interactive control metamodel and the triggering relationship between the core interactive control metamodel and the functional metamodel.

[0007] Optionally, the real-time computing plugin resource meta-model is constructed by binding the hardware and software resource attributes of the real-time computing plugin with the hardware registers and software computing units of the real-time computing plugin, respectively; the hardware and software resource attributes of the real-time computing plugin include hardware model, software version, register address, parameter threshold, computing precision and resource point category; The human-machine management plugin resource meta-model is constructed based on state value resource points and control value resource points to determine the interaction attributes, business associations, and data transmission rules between all resource points during the human-machine interaction process. The state value resource points include name, unit, value type, system attribute, and resource point identifier, and the control value resource points include name, control type, interlock attribute, associated setpoint, and resource point identifier. The target standard resource meta-model is constructed by mapping the logical nodes, data objects, and data attributes of the IEC standard to the resource points of the real-time computing plugin and the resource points of the human-machine management plugin.

[0008] Optionally, the basic configuration function meta-model is constructed by defining the input parameters, output results, and execution logic of the basic configuration function; the basic configuration function includes resource import, resource addition, resource deletion, resource modification, automatic short address allocation, and resource point verification. The construction of the real-time computing plugin functional meta-model includes: The real-time computing function unit is encapsulated based on the concept of atomization encapsulation; the real-time computing function unit includes computing logic configuration, resource point association computing, computing result feedback, computing exception handling, and computing cycle configuration; Define the input and output parameters, operation rules and triggering conditions of the real-time computing function unit, determine the binding relationship between the resource points of the real-time computing function unit and the real-time computing plugin, and obtain the constructed real-time computing plugin functional meta-model. The construction of the functional meta-model of the human-machine management plugin includes: Human-computer interaction functional units are encapsulated based on the concept of atomization encapsulation; the human-computer interaction functional units include interface display configuration, operation command forwarding, status feedback display, alarm prompt configuration, and interaction permission management; Define the interaction logic and triggering conditions of the human-computer interaction functional unit, determine the binding relationship between the resource points of the human-computer interaction functional unit and the human-computer management plugin, and obtain the constructed human-computer management plugin functional meta-model; The target standard functional meta-model is constructed by encapsulating the functional units of the IEC standard and defining the functional execution logic and associated constraints of the real-time computing plug-in and the human-machine management plug-in under the IEC standard. The application instantiation function metamodel is constructed by defining the association constraints between application instantiation functions; the application instantiation functions include instance creation, menu hierarchy configuration, group data association, priority configuration, dependency configuration, and whole group subscription configuration.

[0009] Optionally, the core interactive control metamodel is constructed by determining the display style, operation permissions, and data loading method of the control; the control includes a resource configuration tree, an instantiation configuration tree, a table configuration interface, and a pop-up selection interface.

[0010] Optionally, the policy constraint instructions include configuration generation policy, export format policy, short address allocation policy, data format constraints, function association constraints, exception handling constraints, and instantiation configuration constraints: The configuration generation strategy is as follows: select a combination of data meta-model and functional meta-model according to business requirements, formulate the configuration generation rules of the target standard model, and the association relationship of logical nodes, data objects and data attributes of the target standard model; The export format strategy is as follows: select an export format, which includes EDP format, EDP compatible format, RK3568 format, Typedata format, and target standard format. Each format defines a different file structure and data extraction and encapsulation rules. The short address allocation strategy is as follows: short addresses are allocated according to plugin model, resource point type, and logical nodes in the target standard model, and each short address is a unique value. The data format constraints are: determining the data type, value range, and format of the fields of each metamodel in the metamodel instantiation template; The functional association constraints are: determining the execution order of the functional meta-model and determining the association relationship between the target standard model and the plug-in; The exception handling constraints are: determining the alarm rules and process exit mechanism for exception scenarios.

[0011] Optional, also includes: The instantiation template of the metamodel is stored in a structured manner in the metamodel library. A unique version number is configured for each metamodel in the metamodel library and the modification log of the metamodel is recorded. Retrieve metamodels from the metamodel library based on keywords, including device type, function type, and metamodel type.

[0012] Optional, the generation of standardized interaction description files includes: Based on the file export format, extract the full configuration data and generate a standardized interactive description file; the full configuration data includes instantiated resource points of the real-time computing plugin, instantiated resource points of the human-machine management plugin, instantiated functions of the real-time computing plugin, instantiated functions of the human-machine management plugin, the relationship between resource points and functions, short address mapping relationship, and target standard model configuration. The export formats include EDP format, EDP-compatible format, target standard format, RK3568 format, and Typedata format; the target standard format includes ICD format, CID format, and SCD format.

[0013] Optionally, this also includes storing standardized interaction description files in a hierarchical manner within the tool database: The resource database in the tool database is categorized into real-time computing plugin hardware resources, real-time computing plugin software resources, human-machine management plugin status value resources, human-machine management plugin control value resources, and target standard model resources, with each type of resource corresponding to an independent data table. The application instance database in the tool database includes an application instance association table, a menu hierarchy configuration table, a group data configuration table, a priority configuration table, a dependency configuration table, an instantiation configuration association table, and a target standard mapping data table. The instantiation configuration association table stores the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, the instantiation functions of the human-machine management plugin, and the association relationships between resource points and functions; The target standard mapping data table stores short address mapping relationships and target standard model configurations.

[0014] Secondly, this invention provides a data service configuration system based on resource domain modeling and self-configuration, comprising: The data acquisition module is used to: acquire the current secondary equipment type and current business requirements; The resource point generation module is used to: match the meta-model instantiation template according to the current secondary equipment type and current business requirements, and generate instantiation resource points for the real-time computing plugin and the human-machine management plugin. The resource function association module is used to: associate the instantiation resource points and instantiation functions of the real-time computing plugin and the instantiation function of the human-machine management plugin based on the meta-model instantiation template, and obtain the association relationship between resource points and functions. The configuration generation module is used to: parse the logical nodes, data objects and data attributes in the target standard model file, establish the association relationships between the target standard model file and the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, and the instantiation functions of the human-machine management plugin, and assign short address mapping relationships to the association relationships to generate the target standard model configuration; The service configuration module is used to generate standardized interactive description files and deploy them to the target power secondary equipment based on the instantiated resource points of the real-time computing plugin, the instantiated resource points of the human-machine management plugin, the instantiated functions of the real-time computing plugin, the instantiated functions of the human-machine management plugin, the relationship between resource points and functions, the short address mapping relationship, and the target standard model configuration, so as to obtain the data service configuration results.

[0015] Compared with the prior art, the beneficial effects achieved by the present invention are as follows: This invention achieves resource and function decoupling of real-time computing plugins and human-machine management plugins through layered abstraction of meta-models, and standardizes resource point modeling and function modeling for both types of plugins. It adopts IEC standards for adaptation, supporting rapid adaptation to different models of the two types of plugins and different power secondary equipment scenarios, applicable to various application scenarios such as AC, DC, overseas, power grid systems, and industrial systems. Relying on self-configuration capabilities, it completes instantiated self-developed configurations and short address mapping between target standard models and plugin resources, fulfilling the configuration requirements of new plugins and new scenarios without modifying core code, significantly shortening the development cycle of customized products, reducing manual operation errors, and lowering maintenance costs. Through visual configuration adjustment and automated strategy matching, it supports flexible adjustment of instantiated configurations and target standard model configurations to meet personalized business needs, while ensuring that all configuration operations comply with constraint rules and industry standards. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating one embodiment of the data service configuration method based on resource domain modeling and configuration self-construction of the present invention; Figure 2 This is a flowchart illustrating another embodiment of the data service configuration method based on resource domain modeling and configuration self-construction of the present invention. Detailed Implementation

[0017] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical solution of the present invention, rather than limitations thereof. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.

[0018] The term "and / or" simply describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0019] Example 1

[0020] like Figure 1 As shown in the figure, this embodiment introduces a data service configuration method based on resource domain modeling and self-configuration, including: Obtain the current secondary equipment type and current business requirements; Based on the current secondary equipment type and current business requirements, the corresponding metamodel is matched from the metamodel instantiation template according to the policy constraint instructions to generate real-time computing plugin instantiation resource points, human-machine management plugin instantiation resource points, real-time computing plugin instantiation functions, and human-machine management plugin instantiation functions. By associating the instantiation resource points of the real-time computing plugin with the instantiation function of the real-time computing plugin, and the instantiation resource points of the human-machine management plugin with the instantiation function of the human-machine management plugin, the relationship between resource points and functions can be obtained. The logical nodes, data objects, and data attributes in the target standard model file are analyzed. The association relationships between the target standard model file and the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, and the instantiation functions of the human-machine management plugin are established respectively. Short address mapping relationships are assigned to the association relationships, and the target standard model configuration is generated. Based on the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, the instantiation functions of the human-machine management plugin, the relationship between resource points and functions, the short address mapping relationship, and the target standard model configuration, a standardized interactive description file is generated and deployed to the target power secondary equipment to obtain the data service configuration result.

[0021] This embodiment achieves resource and function decoupling of real-time computing plugins and human-machine management plugins through layered abstraction of meta-models, and standardizes resource point modeling and function modeling of the two types of plugins; it samples IEC standards to complete adaptation, supporting rapid adaptation of different models of the two types of plugins and different power secondary equipment scenarios; relying on configuration self-construction capabilities, it completes instantiation of self-developed configurations and short address mapping of target standard models and plugin resources, so that the configuration requirements of new plugins and new scenarios can be completed without modifying the core code.

[0022] Example 2

[0023] like Figure 2 As shown in Example 1, this example introduces a data service configuration method based on resource domain modeling and self-configuration, including the following steps: Step 1: Construct the metamodel instantiation template, specifically as follows: The core of this step is to standardize the resource point modeling and functional modeling of the real-time computing plugin and the human-machine management plugin. It samples the International Electrotechnical Commission (IEC) standard to adapt and extend the modeling of these two types of plugins, constructing a hierarchical meta-model system covering data, functions, and interactive controls. This provides a basic meta-model support for subsequent configuration self-construction and instantiation configuration. In this embodiment, the IEC standard is IEC 61850, and the target standard described below will use IEC 61850 as an example.

[0024] The instantiated template includes the data metamodel, the functional metamodel, the configuration interface control metamodel, and the binding rules between the functional metamodel and the data metamodel.

[0025] The binding rules between functional meta-models and data meta-models are as follows: menu-level meta-models need to be associated with human-machine management plugin resource meta-model instances; operational logic functional meta-models need to be associated with real-time operational plugin resource point meta-model instances; and 61850 logical node mapping functions need to be associated with both data meta-models and resource point meta-models.

[0026] The data meta-model refers to the standardized abstraction of device resources, covering two types of plug-in resource point modeling and 61850 adaptation. The data meta-model includes the real-time computing plug-in resource meta-model, the human-machine management plug-in resource meta-model, and the 61850 resource meta-model. For real-time computing plugins, an abstract set of hardware and software resource attributes is defined, covering fields such as hardware model, software version, register address, parameter threshold, computation precision, and resource point category. The focus is on completing resource point modeling for real-time computing plugins, clearly defining resource point classifications (such as computation parameters, status feedback, and control instruction resource points). The hardware and software resource attributes of the real-time computing plugin are precisely bound to the hardware registers and software computation units of the plugin to construct a resource meta-model, achieving standardized abstraction and modeling of resource points. The system supports parsing .ehc format hardware configuration files and .esc format software configuration files, automatically extracting attribute values ​​and resource point information to complete meta-model instantiation, ensuring that resource point data can be accurately called by subsequent functional modules.

[0027] For the HMI management plugin, two core data meta-models are abstractly defined: status value resource points (including fields such as name, unit, value type, system attribute, and resource point identifier) ​​and control value resource points (including fields such as name, control type, interlock attribute, associated setpoint, and resource point identifier). The focus is on completing the resource point modeling of the HMI management plugin. Based on status value and control value resource points, it covers all resource points in the HMI interaction process (such as display parameters, operation commands, and alarm prompts). It determines the interaction attributes, business relationships, and data transmission rules between all resource points in the HMI interaction process, constructing a resource meta-model for the HMI management plugin. This achieves systematic and standardized modeling of HMI management plugin resource points, supporting the configuration and instantiation of subsequent HMI interaction functions. It also supports user-defined business semantic tags to adapt to the resource point description requirements of different scenarios.

[0028] The IEC 61850 model resource modeling feature includes a new data meta-model extension adapted to the IEC 61850 standard. It samples the IEC 61850 standard and standardizes the resource point modeling for real-time computing and human-machine management plugins. This involves mapping the logical nodes, data objects, and data attributes of the IEC 61850 standard to the resource points of the real-time computing and human-machine management plugins (e.g., the correspondence between logical nodes and data objects in the IEC 61850 standard and plugin resource points, and data type adaptation rules). This constructs a 61850 resource meta-model, supporting the parsing and modeling of Intelligent Electronic Device Capability Description (ICD) files, configured Intelligent Electronic Device Description (CID) files, instantiated Intelligent Electronic Device Description (IID) files, and Substation Configuration Description (SCD) files, thus realizing the IEC standard. The standardized abstraction of two types of plug-in resource points under the 61850 standard ensures the interoperability of resource data across standards and devices, laying the foundation for establishing mapping relationships through short addresses in the future.

[0029] Define the storage rules for the data meta-model, clarify the mapping relationship between different resource types such as real-time computing plugin resource points, human-machine management plugin resource points, and 61850 model adaptation data and tool database table structure, standardize data storage format and synchronization rules, and ensure data consistency and traceability.

[0030] The functional metamodel refers to the atomic encapsulation of business capabilities, covering two types of plugin function modeling and 61850 adaptation. The functional metamodel includes the basic configuration functional metamodel, the real-time computing plugin functional metamodel, the human-machine management plugin functional metamodel, the 61850 functional metamodel, and the application instantiation functional metamodel. Define the input parameters, output results, and execution logic of the basic configuration functions, and construct the basic configuration function meta-model. The basic configuration functions include resource import, resource addition, resource deletion, resource modification, automatic short address allocation, resource point verification, etc. Focus on adapting to the resource configuration requirements of real-time computing plugins and human-machine management plugins to ensure that the basic configuration functions can accurately match the resource point characteristics of the two types of plugins.

[0031] For the functional modeling of real-time computing plugins, real-time computing functional units are encapsulated based on the atomic encapsulation concept. These real-time computing functional units include computing logic configuration, resource point-related computing, computing result feedback, computing exception handling, and computing cycle configuration. The input and output parameters, computing rules, and triggering conditions of each real-time computing functional unit are defined, and the binding relationship between the real-time computing functional units and the resource points of the real-time computing plugin is clarified (e.g., computing functions are bound to computing parameter resource points, and result feedback functions are bound to status feedback resource points). A functional meta-model of the real-time computing plugin is constructed to achieve standardized and reusable modeling of the real-time computing plugin functions, supporting subsequent functional instantiation.

[0032] For the functional modeling of the HMI management plugin, the HMI interaction functional units are encapsulated based on the atomic encapsulation concept. These HMI functional units include interface display configuration, operation command forwarding, status feedback display, alarm prompt configuration, and interaction permission management. The interaction logic and triggering conditions of the HMI functional units are defined, and the binding rules between the HMI functional units and HMI management plugin resource points are clarified (such as binding display functions to status value resource points and operation functions to control value resource points). A functional meta-model of the HMI management plugin is constructed to achieve atomic and composable modeling of the HMI management plugin functions, supporting subsequent function instantiation and interaction configuration.

[0033] The 61850 model functional modeling is improved by adding a new functional meta-model related to the 61850 model configuration. Sampling from the IEC 61850 standard, the functional modeling of the real-time computing plug-in and the human-machine management plug-in is extended. It encapsulates the functional units of the IEC 61850 standard, such as 61850 logical node mapping, data object association, communication parameter configuration, and short address mapping management. It also defines the functional execution logic and association constraints of the real-time computing plug-in and the human-machine management plug-in under the IEC 61850 standard, and constructs the 61850 functional meta-model to support the collaborative configuration of the 61850 functional meta-model and plug-in functions, as well as the short address mapping configuration of the 61850 functional meta-model and plug-in resource points.

[0034] It encapsulates the application instantiation function metamodel, covering application instance creation, menu hierarchy configuration, group data association, priority configuration, dependency configuration, and whole group subscription configuration. It defines the association constraints between application instantiation functions and constructs the application instantiation function metamodel. For example, application instances must be created before priority configuration can be performed, and instantiation functions must be associated with instantiation resource points. It focuses on adapting to the self-developed instantiation configuration requirements and provides constraints and support for the association between instantiation resource points and instantiation functions.

[0035] The interactive control metamodel refers to the standardized definition of interface components, adapting to the interactive requirements of two types of plugin modeling, instantiation configuration, and 61850 configuration. The configuration of the interface control metamodel includes the core interactive control metamodel and the triggering relationship between the core interactive control metamodel and the functional metamodel. The abstract defines four types of core interactive control metamodels, including resource configuration trees, instantiation configuration trees, table configuration interfaces, and pop-up selection interfaces. It clarifies the display style, operation permissions, and data loading methods of the controls to construct the core interactive control metamodels. It focuses on adapting the resource point configuration and function configuration of real-time computing plugins and human-computer management plugins, as well as the interactive requirements of 61850 resource metamodel configuration, 61850 function metamodel configuration, and instantiation configuration. For example, the resource configuration tree supports the display of resource points categorized by real-time computing plugins / human-computer management plugins, and the instantiation configuration tree supports the display of the relationship between instantiated resources and instantiated functions.

[0036] The triggering relationship between the core interactive control metamodel and the functional metamodel is as follows: right-clicking the real-time computing plugin node in the resource configuration tree triggers the 'Create real-time computing plugin resource point' functional metamodel; right-clicking the instantiated configuration tree node triggers the 'Associate instantiated resource with function' functional metamodel; and clicking the 61850 configuration interface button triggers the 'Short address mapping configuration' functional metamodel.

[0037] Meanwhile, it supports dynamic adjustment of control properties. For example, when recognizing enumeration type metamodel fields, it automatically generates drop-down selection controls; for the calculation parameter resource points of the real-time calculation plugin, it automatically generates numerical input controls and matches parameter threshold constraints; for the 61850 logical node mapping configuration, it automatically generates drop-down selection controls to load the 61850 logical node and plugin resource point list, improving the efficiency of interactive configuration.

[0038] Step 2: Store the instantiated metamodel template in a structured manner in the metamodel library, specifically as follows: This step enables standardized storage, version management, and maintenance of various meta-models, with a focus on supporting the meta-models related to real-time computing plugins and human-machine management plugins, as well as the reuse and consistency control of the 61850 resource meta-model and the 61850 functional meta-model, providing stable meta-model support for configuration self-construction and instantiation configuration.

[0039] The metamodel is stored in a standardized manner, establishing a structured metamodel library. The attribute definitions, association rules, and execution logic of the metamodel are stored according to the categories of "data / function / interactive control". Resource point metamodels and functional metamodels are stored in a separate category of "real-time computing plugin / human-machine management plugin". The 61850 resource metamodel and 61850 functional metamodel are stored separately. It supports the classification and management of metamodels of multiple types of devices such as real-time computing plugins and human-machine management plugins, ensuring the standardization and reusability of the metamodel.

[0040] Metamodel version management assigns a unique version number to each metamodel in the metamodel library (including real-time computing plugin resource / functional metamodels, human-machine management plugin resource / functional metamodels, and 61850 resource / functional metamodels), records metamodel modification logs (including modifier, modification time, and modification content), supports version rollback, and avoids metamodel conflicts under different device configuration scenarios and different plugin models; when the IEC 61850 standard is updated or the plugin model is upgraded, it can be extended and upgraded based on the original metamodel without rebuilding, reducing maintenance costs.

[0041] Metamodel retrieval and maintenance provides a keyword search function, allowing users to search for metamodels in the metamodel library based on keywords. It supports quick metamodel queries by device type (real-time computing plugin, human-machine management plugin), function type (computation function, interactive function, 61850 configuration function), and metamodel type (data, function, interactive control). It supports adding, deleting, and modifying metamodels, with automatic synchronization after modification to ensure that strategy matching is consistent with the metamodel. It also supports batch import and export of metamodels to adapt to the metamodel reuse needs of different projects.

[0042] Step 3: Execute the policy constraint instruction set, specifically: The system incorporates a built-in device adaptation strategy, matching corresponding resource parsing rules (such as .ehc / .esc file parsing rules for different models of real-time computing plugins) and meta-model instantiation templates for different types of human-machine management plugins. It provides standardized modeling strategies for resource point modeling and functional modeling of both types of plugins, ensuring consistent modeling logic across different plugin models. Furthermore, it incorporates a 61850 model adaptation strategy, sampling the IEC 61850 standard. For different models of real-time computing plugins and different types of human-machine management plugins, it matches corresponding mapping strategies between the 61850 model and plugin resource points and functions, clearly defining adaptation rules and parameter configuration requirements to ensure that the 61850 model accurately adapts to the modeling needs of both types of plugins.

[0043] The built-in configuration generation strategy automatically selects the required combination of functional meta-models and data meta-models based on the user's selected business requirements (such as resource configuration, multi-format export, 61850 model configuration, and instantiation configuration). It focuses on the built-in self-developed configuration generation strategy related to instantiation, which formulates automated 61850 model configuration generation rules for the resource points and functions of the instantiated human-machine management plugin and real-time computing plugin, as well as their relationship and the short address mapping between the 61850 model and plugin resource points, ensuring the standardization and consistency of instantiation configuration. For 61850 model configuration, it formulates automated strategies for logical node mapping and data object association to improve configuration efficiency.

[0044] The built-in export format strategy defines different file structures and data extraction rules for Embedded DisplayPort (EDP) format, EDP-compatible format, embedded processor (RK3568) format, and Typedata format. The focus is on adding export strategies for 61850 model-related formats (ICD format, CID format, SCD format), clarifying the extraction and encapsulation rules for 61850 model data, short address mapping relationships, and instantiation configuration data, ensuring that the exported files comply with the IEC 61850 standard and cross-device deployment requirements.

[0045] Built-in short address allocation strategy, for example: In response to the requirement in the instantiation of self-developed configuration to "establish the mapping relationship between the IEC 61850 model and the resource points of the human-machine management plug-in and the real-time computing plug-in through short addresses", an automated short address allocation strategy is formulated. Following the principles of uniqueness and standardization, short addresses are allocated in combination with plug-in model, resource point type and logical nodes in the 61850 model to avoid address conflicts and ensure the accuracy and traceability of short address mapping.

[0046] Data format constraints limit the data type and value range of each meta-model field. For example, the priority field must be a positive integer, the calculation precision field of the real-time calculation plugin must be a decimal between 0.001 and 1, and the short address field must be a 3-6 digit positive integer. Limit the 61850 model data and instantiation configuration data to ensure compliance with the IEC 61850 standard and modeling specifications.

[0047] Functional association constraints clarify the execution order of the functional meta-model. For example, resource point modeling of the real-time computing plugin / human-machine management plugin must be completed before functional modeling can be performed; resource modeling must be completed before application instance association can be performed; and the association between instantiated resource points and instantiated functions must be completed before short address mapping between the 61850 model and plugin resource points can be performed. Clarify the association constraints between the 61850 model configuration and the modeling of the two types of plugins. For example, the 61850 logical node must be associated with the resource point meta-model instance of the real-time computing plugin / human-machine management plugin.

[0048] The exception handling constraints define alarm rules and process exit mechanisms for exception scenarios such as file non-existence, short address conflict, 61850 model parsing failure, and abnormal association between instantiated resources and functions; for the two types of exceptions in plugin modeling, 61850 resource / function configuration, and instantiation configuration, the alarm prompts and exception handling paths are clearly defined to ensure that the configuration process can be traced back and corrected normally.

[0049] Instantiation configuration constraints define the constraint rules for self-developed instantiation configurations, such as: each instantiation function must be associated with at least one instantiation resource point, each 61850 logical node data object must correspond to a unique plugin resource point short address, and instantiation resource points must originate from the resource point modeling results of the real-time computing plugin / human-machine management plugin, to ensure the rationality and standardization of instantiation configuration.

[0050] The strategy matching and execution mechanism receives user input regarding the current secondary device type (real-time computing plugin model, human-machine management plugin type) and current business requirements (resource modeling, functional modeling, 61850 configuration, instantiation configuration). It automatically matches the optimal strategy and constraint rules, and outputs a configuration-built instruction set. It also verifies operations during the configuration process in real time (such as resource point modeling, instantiation association, and short address mapping). If constraint rules are violated, it immediately triggers alarms and blocks the operation, ensuring that the configuration process is compliant and accurate.

[0051] Step 4: Generate a standardized interaction description file and deploy it to the target secondary power equipment, specifically: This step is the core execution module for instantiating self-developed configurations and 61850 model configurations. It automatically completes the instantiation of resource points, functional instantiation, and relationship establishment for the two types of plugins, as well as the short address mapping between the 61850 model and plugin resource points. It also supports visual manual adjustment, realizing the automation and flexibility of configuration.

[0052] Metamodel instance selection: Based on the current secondary equipment type and current business requirements, the corresponding metamodel is matched from the metamodel instantiation template according to the policy constraint instructions. This includes the real-time computing plugin resource metamodel, human-machine management plugin resource metamodel, 61850 resource metamodel, real-time computing plugin functional metamodel, human-machine management plugin functional metamodel, and 61850 functional metamodel. Based on the plugin model and business scenario selected by the user, the corresponding metamodel template is automatically matched, reducing manual selection operations and improving instantiation efficiency.

[0053] Automatic configuration association covers instantiated self-developed configurations and 61850 model configurations: Instantiate resources and associate them with functions. Combined with the self-developed configuration requirements for instantiation, automatically complete the instantiation of resource points for human-machine management plugin and real-time computing plugin. That is, based on the matching resource meta-model of real-time computing plugin and resource meta-model of human-machine management plugin, combined with the parsed data of the .ehc / .esc format files of the two plugins or user input parameters, generate instantiation resource points for real-time computing plugin and human-machine management plugin. Automatically complete the instantiation of the human-machine management plugin and the real-time computing plugin functions. That is, based on the matching real-time computing plugin function meta-model and human-machine management plugin function meta-model, and combined with the configuration of function parameters according to business requirements, generate the instantiation functions of the real-time computing plugin and the human-machine management plugin. The system automatically establishes the association between instantiated resource points and instantiated functions. Based on the binding rules of the functional meta-model and the data meta-model, it achieves precise association between instantiated functions and corresponding resource points. That is, it associates the instantiated resource points of the real-time computing plugin with the instantiated functions of the real-time computing plugin, and the instantiated resource points of the human-machine management plugin with the instantiated functions of the human-machine management plugin. This results in the association between resource points and functions (e.g., the display function instance of the human-machine management plugin is associated with the status value resource point instance, and the computing function instance of the real-time computing plugin is associated with the computing parameter resource point instance), ensuring that the instantiated functions can call resource data normally.

[0054] Application instance and resource point mapping: Automatically maps application instances to instantiated resource points, supports multi-selection of resource points and keyword search, and generates group data association configurations; It is designed to meet the instantiation configuration requirements of two types of plugins, and supports filtering instantiated resource points by plugin type and resource point category to improve mapping efficiency.

[0055] The 61850 model configuration association automatically loads 61850 model files (supporting ICD / CID / IID / SCD formats), parses the logical nodes, data object information, and data attributes in the 61850 model, and automatically establishes association relationships between the 61850 model file and the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, and the instantiation functions of the human-machine management plugin, generating the 61850 model configuration to ensure that the resources and functions of the two types of plugins under the IEC 61850 standard can work together normally.

[0056] Short address mapping and allocation automatically assigns MMS / Goose short addresses. Following the short address allocation strategy in the policy constraint instructions, and combining hardware and software resource configuration results and instantiated resource point information, unique short addresses are generated according to preset rules. Based on the instantiation self-developed configuration requirements, short address mapping relationships are assigned to the aforementioned associations. Through short addresses, a mapping relationship is established between the 61850 model file and the resource points and functions of the human-machine management plugin and real-time computing plugin. The short addresses corresponding to the plugin resource points and functions of each logical node, data object, and data attribute in the 61850 model file are clearly defined, and the mapping relationship data is stored, enabling data interoperability and collaborative control between the 61850 model file and plugin resource points. The uniqueness of short addresses is automatically verified to avoid address conflicts.

[0057] The system offers visual manual adjustments, providing a graphical interface that allows users to manually modify automatically generated configurations. It primarily covers adjustments to instantiation configurations and 61850 model configurations, including adjusting instantiation resource point attributes and instantiation function parameters, adjusting the association between instantiation resources and instantiation functions, modifying the short address mapping between the 61850 model and plugin resource points, and adjusting the association between 61850 logical nodes and instantiation functions. It also supports adjusting application priority, modifying menu levels, and adding or removing associated resource points. All modifications are automatically validated against constraints (such as short address uniqueness and function association order) before being saved, ensuring the adjusted configuration is compliant and usable.

[0058] Based on the instantiated resource points of the real-time computing plugin, the instantiated resource points of the human-machine management plugin, the instantiated functions of the real-time computing plugin, the instantiated functions of the human-machine management plugin, the relationships between resource points and functions, the short address mapping relationships, and the 61850 model configuration, a standardized interactive description file is generated. Specifically, according to the file export format, the full configuration data is extracted to generate the standardized interactive description file. The full configuration data includes the instantiated resource points of the real-time computing plugin, the instantiated resource points of the human-machine management plugin, the instantiated functions of the real-time computing plugin, the instantiated functions of the human-machine management plugin, the relationships between resource points and functions, the short address mapping relationships, and the 61850 model configuration. Export formats include EDP format, EDP-compatible format, 61850 format, RK3568 format, and Typedata format. The 61850 format includes ICD format, CID format, and SCD format. Multiple format exports are supported to ensure lossless deployment across devices, meeting the deployment requirements of both the instantiated self-developed configuration and the 61850 model configuration. The system includes multi-format adaptation logic. For different export formats, it calls the corresponding format strategy. For example, when exporting EDP format, it extracts file data and instantiated resource point data in .ehc and .esc formats. When exporting EDP-compatible formats, it adds HMISCI.xml and ui_cfg.json files, which contain the instantiation configuration data of the HMISCI plugin. It also adds adaptation logic for 61850-related formats, calling the 61850 export strategy to extract 61850 model data, short address mapping relationships, and 61850 model configurations to ensure that the exported files comply with the IEC 61850 standard. For RK3568 and Typedata formats, it adapts to the export requirements of instantiation configuration data and short address mapping relationships for these two types of plugins.

[0059] Data extraction and mapping: Extracting all configuration data, including resource point modeling data, functional modeling data, instantiation configuration data (instantiated resource points, instantiated functions, and their relationships), 61850 model configuration, short address mapping relationships, etc., from the real-time computing plugin / HMISCI plugin. Data mapping is completed according to the target file structure. For example, the resource meta-modeling data and instantiation configuration data of the HMISCI plugin are converted into node attributes of HMISCI.xml, and the short address mapping relationship between the 61850 model and the plugin resource points is converted into the corresponding nodes in the SCD file, ensuring the integrity and accuracy of the exported data.

[0060] The process follows the steps of "saving data to the database → selecting the export type (including 61850 model-related formats) → constructing the target file → verifying the file's legality (compliance with IEC 61850 standards and constraint rules) → displaying the execution results in a pop-up window" to ensure that the exported data is consistent with the configuration and that the exported file can be deployed normally. It supports batch export and single file export. For 61850 model format files, an additional standard compliance verification step is added to avoid deployment failure due to exported files not conforming to industry standards.

[0061] Deploy the standardized interactive description file to the target power secondary equipment to obtain the data service configuration results.

[0062] Step 5: Store the standardized interaction description files in a hierarchical manner in the tool database, specifically as follows: This step enables the modeling of two types of plugins, configuration of the 61850 model, hierarchical storage of instantiated self-developed configuration-related data, real-time synchronization and traceability management, ensuring data consistency and maintainability.

[0063] The resource database in the tool database is categorized into real-time computing plugin hardware resources, real-time computing plugin software resources, human-machine management plugin status value resources, human-machine management plugin control value resources, and 61850 model resources, with each type of resource corresponding to an independent data table. The database focuses on storing resource point modeling data for real-time computing plugins and human-machine management plugins, as well as the data parsed from the 61850 model and short address mapping relationships, ensuring the categorized management and traceability of resource data.

[0064] It supports dynamic addition, deletion, and modification of data tables. When users operate on resource configuration, resource point modeling, and 61850 model configuration, the corresponding data tables in the database are updated synchronously to ensure consistency between interface data, configuration data, and database data. For modifications to short address mapping relationships, the relevant data tables are automatically updated synchronously to ensure the consistency of mapping data.

[0065] The application instance database in the tool database includes the application instance association table, menu hierarchy configuration table, group data configuration table, priority configuration table, dependency configuration table, instantiation configuration association table, and 61850 mapping data table; Among them, the instantiation configuration association table is specifically used to store data related to the instantiation of self-developed configurations, including instantiation resource points of real-time computing plugins, instantiation resource points of human-machine management plugins, instantiation functions of real-time computing plugins, instantiation functions of human-machine management plugins, and the relationship between resource points and functions. The 61850 mapping data table stores short address mapping relationships and 61850 model configurations.

[0066] Records full configuration information of application instances, including instantiation configuration data of two types of plugins, configuration data of the 61850 model, and short address mapping relationships. Supports traceability and rollback of configuration settings. When an abnormality occurs in the configuration settings, the modification process can be traced back through the database logs to restore the normal configuration state.

[0067] The data synchronization mechanism establishes a real-time synchronization channel between interface operations and database read / write. When the user clicks the "Save" button, the interface parameters are automatically compared with the database parameters, and an update operation is performed. It focuses on real-time synchronization of instantiated configuration data, 61850 model configuration data, and short address mapping relationships. When instantiated resource points, instantiated functions, or short address mapping relationships are modified, the corresponding data tables in the database are automatically updated. It supports cross-module data synchronization to ensure data consistency among the meta-model library, self-built configuration data, and standardized interactive description files, avoiding data deviations.

[0068] Example 3

[0069] This embodiment introduces a data service configuration system based on resource domain modeling and self-configuration, including: The data acquisition module is used to: acquire the current secondary equipment type and current business requirements; The resource point generation module is used to: match the meta-model instantiation template according to the current secondary equipment type and current business requirements, and generate instantiation resource points for the real-time computing plugin and the human-machine management plugin. The resource function association module is used to: associate the instantiation resource points and instantiation functions of the real-time computing plugin and the instantiation function of the human-machine management plugin based on the meta-model instantiation template, and obtain the association relationship between resource points and functions. The configuration generation module is used to: parse the logical nodes, data objects and data attributes in the target standard model file, establish the association relationships between the target standard model file and the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, and the instantiation functions of the human-machine management plugin, and assign short address mapping relationships to the association relationships to generate the target standard model configuration; The service configuration module is used to generate standardized interactive description files and deploy them to the target power secondary equipment based on the instantiated resource points of the real-time computing plugin, the instantiated resource points of the human-machine management plugin, the instantiated functions of the real-time computing plugin and the instantiated functions of the human-machine management plugin, the relationship between resource points and functions, the short address mapping relationship, and the target standard model configuration, so as to obtain the data service configuration results.

[0070] The specific functions of each module described above are explained in the relevant content of the method in Embodiment 1, and will not be repeated here.

[0071] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0072] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0073] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0074] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0075] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

Claims

1. A data service configuration method based on resource domain modeling and self-configuration, characterized in that, include: Obtain the current secondary equipment type and current business requirements; Based on the current secondary equipment type and current business requirements, the corresponding metamodel is matched from the metamodel instantiation template according to the policy constraint instructions to generate real-time computing plugin instantiation resource points, human-machine management plugin instantiation resource points, real-time computing plugin instantiation functions, and human-machine management plugin instantiation functions. By associating the instantiation resource points of the real-time computing plugin with the instantiation function of the real-time computing plugin, and the instantiation resource points of the human-machine management plugin with the instantiation function of the human-machine management plugin, the relationship between resource points and functions can be obtained. The logical nodes, data objects, and data attributes in the target standard model file are analyzed. The association relationships between the target standard model file and the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, and the instantiation functions of the human-machine management plugin are established respectively. Short address mapping relationships are assigned to the association relationships, and the target standard model configuration is generated. Based on the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, the instantiation functions of the human-machine management plugin, the relationship between resource points and functions, the short address mapping relationship, and the target standard model configuration, a standardized interactive description file is generated and deployed to the target power secondary equipment to obtain the data service configuration result.

2. The data service configuration method based on resource domain modeling and self-configuration as described in claim 1, characterized in that, The metamodel instantiation template includes a data metamodel, a functional metamodel, a configuration interface control metamodel, and binding rules between the functional metamodel and the data metamodel; The data meta-model includes a real-time computing plugin resource meta-model, a human-machine management plugin resource meta-model, and a target standard resource meta-model. The functional meta-model includes a basic configuration functional meta-model, a real-time computing plugin functional meta-model, a human-machine management plugin functional meta-model, a target standard functional meta-model, and an application instantiation functional meta-model. The configuration interface control metamodel includes the core interactive control metamodel and the triggering relationship between the core interactive control metamodel and the functional metamodel.

3. The data service configuration method based on resource domain modeling and self-configuration as described in claim 2, characterized in that, The real-time computing plugin resource meta-model is constructed by binding the hardware and software resource attributes of the real-time computing plugin with the hardware registers and software computing units of the real-time computing plugin, respectively; the hardware and software resource attributes of the real-time computing plugin include hardware model, software version, register address, parameter threshold, computing precision and resource point category. The human-machine management plugin resource meta-model is constructed based on state value resource points and control value resource points to determine the interaction attributes, business associations, and data transmission rules between all resource points during the human-machine interaction process. The state value resource points include name, unit, value type, system attribute, and resource point identifier, and the control value resource points include name, control type, interlock attribute, associated setpoint, and resource point identifier. The target standard resource meta-model is constructed by mapping the logical nodes, data objects, and data attributes of the IEC standard to the resource points of the real-time computing plugin and the resource points of the human-machine management plugin.

4. The data service configuration method based on resource domain modeling and self-configuration as described in claim 2, characterized in that, The basic configuration function metamodel is constructed by defining the input parameters, output results, and execution logic of the basic configuration functions; the basic configuration functions include resource import, resource addition, resource deletion, resource modification, automatic short address allocation, and resource point verification. The construction of the real-time computing plugin functional meta-model includes: The real-time computing function unit is encapsulated based on the concept of atomization encapsulation; the real-time computing function unit includes computing logic configuration, resource point association computing, computing result feedback, computing exception handling, and computing cycle configuration; Define the input and output parameters, operation rules and triggering conditions of the real-time computing function unit, determine the binding relationship between the resource points of the real-time computing function unit and the real-time computing plugin, and obtain the constructed real-time computing plugin functional meta-model. The construction of the functional meta-model of the human-machine management plugin includes: Human-computer interaction functional units are encapsulated based on the concept of atomization encapsulation; the human-computer interaction functional units include interface display configuration, operation command forwarding, status feedback display, alarm prompt configuration, and interaction permission management; Define the interaction logic and triggering conditions of the human-computer interaction functional unit, determine the binding relationship between the resource points of the human-computer interaction functional unit and the human-computer management plugin, and obtain the constructed human-computer management plugin functional meta-model; The target standard functional meta-model is constructed by encapsulating the functional units of the IEC standard and defining the functional execution logic and associated constraints of the real-time computing plug-in and the human-machine management plug-in under the IEC standard. The application instantiation function metamodel is constructed by defining the association constraints between application instantiation functions; the application instantiation functions include instance creation, menu hierarchy configuration, group data association, priority configuration, dependency configuration, and whole group subscription configuration.

5. The data service configuration method based on resource domain modeling and self-configuration as described in claim 2, characterized in that, The core interactive control metamodel is constructed by determining the display style, operation permissions, and data loading method of the control; the control includes a resource configuration tree, an instantiation configuration tree, a table configuration interface, and a pop-up selection interface.

6. The data service configuration method based on resource domain modeling and self-configuration as described in claim 2, characterized in that, The policy constraint instructions include configuration generation policy, export format policy, short address allocation policy, data format constraint, function association constraint, exception handling constraint, and instantiation configuration constraint: The configuration generation strategy is as follows: select a combination of data meta-model and functional meta-model according to business requirements, formulate the configuration generation rules of the target standard model, and the association relationship of logical nodes, data objects and data attributes of the target standard model; The export format strategy is as follows: select an export format, which includes EDP format, EDP compatible format, RK3568 format, Typedata format, and target standard format. Each format defines a different file structure and data extraction and encapsulation rules. The short address allocation strategy is as follows: short addresses are allocated according to plugin model, resource point type, and logical nodes in the target standard model, and each short address is a unique value. The data format constraints are: determining the data type, value range, and format of the fields of each metamodel in the metamodel instantiation template; The functional association constraints are: determining the execution order of the functional meta-model and determining the association relationship between the target standard model and the plug-in; The exception handling constraints are: determining the alarm rules and process exit mechanism for exception scenarios.

7. The data service configuration method based on resource domain modeling and self-configuration as described in claim 2, characterized in that, Also includes: The instantiation template of the metamodel is stored in a structured manner in the metamodel library. A unique version number is configured for each metamodel in the metamodel library and the modification log of the metamodel is recorded. Retrieve metamodels from the metamodel library based on keywords, including device type, function type, and metamodel type.

8. The data service configuration method based on resource domain modeling and self-configuration as described in claim 1, characterized in that, The generation of standardized interaction description files includes: Based on the file export format, extract the full configuration data and generate a standardized interactive description file; the full configuration data includes the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, the instantiation functions of the human-machine management plugin, the association between resource points and functions, the short address mapping relationship, and the 61850 model configuration. The export formats include EDP format, EDP-compatible format, target standard format, RK3568 format, and Typedata format; the target standard format includes ICD format, CID format, and SCD format.

9. The data service configuration method based on resource domain modeling and self-configuration as described in claim 1, characterized in that, This also includes storing standardized interaction description files in a hierarchical manner within the tool database: The resource database in the tool database is categorized into real-time computing plugin hardware resources, real-time computing plugin software resources, human-machine management plugin status value resources, human-machine management plugin control value resources, and target standard model resources, with each type of resource corresponding to an independent data table. The application instance database in the tool database includes an application instance association table, a menu hierarchy configuration table, a group data configuration table, a priority configuration table, a dependency configuration table, an instantiation configuration association table, and a target standard mapping data table. The instantiation configuration association table stores the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, the instantiation functions of the human-machine management plugin, and the association relationships between resource points and functions; The target standard mapping data table stores short address mapping relationships and target standard model configurations.

10. A data service configuration system based on resource domain modeling and self-configuration, characterized in that, include: The data acquisition module is used to: acquire the current secondary equipment type and current business requirements; The resource point generation module is used to: match the meta-model instantiation template according to the current secondary equipment type and current business requirements, and generate instantiation resource points for the real-time computing plugin and the human-machine management plugin. The resource function association module is used to: associate the instantiation resource points and instantiation functions of the real-time computing plugin and the instantiation function of the human-machine management plugin based on the meta-model instantiation template, and obtain the association relationship between resource points and functions. The configuration generation module is used to: parse the logical nodes, data objects and data attributes in the target standard model file, establish the association relationships between the target standard model file and the instantiation resource points of the real-time computing plugin, the instantiation resource points of the human-machine management plugin, the instantiation functions of the real-time computing plugin, and the instantiation functions of the human-machine management plugin, and assign short address mapping relationships to the association relationships to generate the target standard model configuration; The service configuration module is used to generate standardized interactive description files and deploy them to the target power secondary equipment based on the instantiated resource points of the real-time computing plugin, the instantiated resource points of the human-machine management plugin, the instantiated functions of the real-time computing plugin, the instantiated functions of the human-machine management plugin, the relationship between resource points and functions, the short address mapping relationship, and the target standard model configuration, so as to obtain the data service configuration results.

Images