A general-purpose human-machine interface plug-in adaptation method for multi-industry applications

Abstract

The application relates to the technical field of power industry automation, and discloses a general human-computer interface plug-in adaptation method for multi-industry application, which comprises the following steps: constructing a human-computer interface plug-in adaptation framework, analyzing and capability description processing plug-in description information by using the human-computer interface plug-in adaptation framework, obtaining plug-in capability description information, and writing the plug-in capability description information into a plug-in capability registry; constructing a unified interface model library in the human-computer interface plug-in adaptation framework, combining the plug-in capability registry to establish interface mapping rules between the unified interface model library and plug-in interfaces, processing a calling request based on the interface mapping rules, and generating plug-in processing result information; after the plug-in processing result information is encapsulated, the plug-in processing result information is sent to the human-computer interface plug-in adaptation framework to execute interface operation, and on-demand control of plug-in instance running behavior is realized according to a plug-in running state in the operation process. The application realizes access and running of plug-ins with different interface specifications in a unified platform.

Description

Technical Field

[0001] This invention relates to the field of automation technology in the power industry, and more specifically, to a universal human-machine interface plug-in adaptation method for multi-industry applications. Background Technology

[0002] As the scale of power and industrial automation systems continues to expand, system automation platforms are gradually developing towards platformization and generalization. In engineering practice, in order to reduce the cost of repetitive development and improve system maintenance efficiency, general system automation platforms are being tested and applied to different industry scenarios such as power grids, thermal power, hydropower, new energy, and industrial dispatching.

[0003] At the human-computer interface (HCI) level, to meet the functional expansion needs of different business scenarios, systems typically employ a plug-in mechanism to extend the graphical interface functionality, encapsulating the screen display and related business logic into plug-ins for loading and execution. However, due to differences in business object models, operation management methods, and HCI interaction requirements across industries, each industry has gradually developed its own plug-in implementation specifications. These differences are mainly reflected in interface definition methods, interface call flows, and parameter organization.

[0004] Against this backdrop, when the human-machine interface of a general system automation platform needs to support plugins from multiple industries, how to maintain platform uniformity while being compatible with different plugin specifications becomes a key issue in system design.

[0005] For example, Chinese Patent Application No. 201910233149.7 discloses a method for implementing third-party application support in a power grid control system. This method involves configuring third-party application plugin loading information and plugin specification format; obtaining third-party application plugin packages and storing them in a plugin library; configuring an access interface for interaction with the plugin library within the human-machine interface framework structure, through which the plugin library accesses data objects and view objects in the human-machine interface framework structure; configuring the third-party application plugin number at startup of the human-machine interface; dynamically loading the required third-party application plugin packages based on the current third-party application plugin number and application plugin configuration information; after the third-party application plugin package is loaded into the human-machine interface, calling the interface corresponding to the third-party application plugin based on the received operation signal, sending request data to the server according to the general service protocol format, and receiving the data processing results from the server to complete the corresponding application operation. This method separates the client and server within the third-party application, resulting in high flexibility.

[0006] However, the aforementioned patent, by introducing a plug-in mechanism into the human-machine interface framework to load and invoke third-party applications, and completing data interaction with the server through a unified service protocol, achieves support for third-party applications. This method mainly solves the problems of plug-in loading and application invocation, and improves the system's scalability to a certain extent. However, this method is mainly geared towards power grid control system scenarios, and its plug-in specifications and interface invocation methods are designed based on a unified protocol, which is a plug-in mechanism implementation method in a single industry context. When the system needs to support plug-ins from different industries with different interface specifications, this method lacks the ability to uniformly adapt to multiple plug-in specifications, and cannot achieve unified access of multi-industry plug-ins without modifying the plug-ins or platform. Furthermore, this method mainly focuses on the plug-in loading and invocation process, and lacks a mechanism to support the unified scheduling and management of plug-ins during operation.

[0007] Meanwhile, Chinese patent application number 202510680409.0 discloses a host computer expandable function platform and its operating method, including: a core plug-in unit; a common plug-in unit; a plug-in manager unit; and a main interface integration unit, used to load plug-in function entry points in conjunction with the plug-in manager unit. User layout configuration is persistently stored through a database module and restored by the main window management module of the core plug-in unit after restart. Through modular and layered design, it effectively solves the pain points of redundant functions and insufficient customization in traditional host computers. The core plug-in unit provides a stable basic service framework to ensure the reliability of hardware communication and multi-threaded scheduling; the common plug-in unit encapsulates common functions such as communication protocols and data storage with standardized interfaces, allowing developers to focus on business logic development. Users can flexibly combine plug-ins such as data acquisition and alarm monitoring according to industrial scenario needs, significantly reducing the maintenance cost of multiple versions and improving system operating efficiency through intelligent resource collaboration mechanisms.

[0008] However, this invention achieves unified loading and management of plugins by constructing a plugin manager and a modular layered structure, and encapsulates some common functions through standardized interfaces, giving the system a certain degree of scalability. This method focuses on the organization and management of the plugin framework and functional modules, and its plugin system still relies on predefined interface specifications. When faced with differences in plugin specifications across different industries, it is usually necessary to adapt or reimplement according to platform specifications during the plugin development stage, making it difficult to directly support the access of existing plugins. Furthermore, this method mainly implements the functions of loading and managing plugins, and lacks a unified abstraction and conversion mechanism for interface differences between different plugin specifications, failing to form a unified adaptation model. When the types of plugins and industries increase, the adaptation logic will be scattered throughout the plugin implementation or platform, making it difficult to form a unified processing mechanism.

[0009] Furthermore, in the field of power and industrial automation, with the development of system platform design concepts, general-purpose system automation platforms are gradually being applied in engineering practice to various industry scenarios such as power grids, thermal power, hydropower, new energy, and industrial dispatching. Different application industries differ in their business object models, operation and management methods, and human-computer interaction requirements, leading to the formation of their own implementation specifications for graphical human-machine interface plugins in terms of interface definition, calling methods, and parameter organization.

[0010] Under current technological conditions, when the human-machine interface of a general system automation platform needs to support plugins from multiple industries, it is usually necessary to develop or adapt plugins for different industries separately, or to make targeted modifications to the platform itself to meet the access requirements of different plugin specifications. This approach not only increases the system development and maintenance costs, but also couples the platform with the specific industry implementation, reducing the system's versatility and scalability. At the same time, due to the lack of a unified plugin operation constraint mechanism, it is difficult to achieve unified control over the loading, calling, and operation management of different plugins, further increasing the complexity of system operation management.

[0011] Therefore, how to achieve unified adaptation of multi-industry plug-in specifications without changing the overall architecture of the human-machine interface of the general system automation platform, and how to uniformly schedule and manage the access, invocation and operation of plug-ins, so as to support the stable operation of multi-industry plug-ins on the same platform, has become an urgent technical problem to be solved.

[0012] There are currently no effective solutions to the problems in the relevant technologies. Summary of the Invention

[0013] To address the problems in related technologies, this invention proposes a universal human-machine interface plug-in adaptation method for multi-industry applications, in order to overcome the aforementioned technical problems existing in the existing related technologies.

[0014] Therefore, the specific technical solution adopted by the present invention is as follows:

[0015] A universal human-computer interface plugin adaptation method for multi-industry applications includes:

[0016] Based on the encapsulation results of data access and screen operation, a human-computer interface plugin adaptation framework is constructed. The plugin description information is parsed and the capability description is processed using the human-computer interface plugin adaptation framework to obtain the plugin capability description information and write it to the plugin capability registry.

[0017] Within the framework for building human-computer interface plugin adaptation, a unified interface model library is constructed, and interface mapping rules between the unified interface model library and plugin interfaces are established in conjunction with the plugin capability registry. Based on the interface mapping rules, the call requests are processed and plugin processing result information is generated.

[0018] After encapsulating the plugin processing result information, the industry interface adaptation component sends it to the human-machine interface plugin adaptation framework to perform interface operations. During the operation, it implements on-demand control of the plugin instance's running behavior based on the plugin's running status.

[0019] Preferably, a human-machine interface plugin adaptation framework is constructed based on the data access and screen operation encapsulation results. This framework is then used to parse and process the plugin description information to obtain plugin capability description information, which is then written to the plugin capability registry. This includes:

[0020] The interface elements, including forms, toolbars, and right-click menus, are abstracted into a unified interface. At the same time, the data access logic is encapsulated into a unified data access interface. The screen operations, including screen elements, toolbar creation, user interaction, and screen switching, are encapsulated into a unified interface call form with parameter structure description.

[0021] A centralized request interface is built to uniformly receive all calls and event requests initiated by the human-machine interface. A unified business call framework is obtained based on the unified interface, unified data access interface, interface call format and centralized request interface.

[0022] Create a plugin capability registry to store plugin capability description information, load the same interface model library to read the unified interface definition, build a unified call entry point, and establish an interface mapping rule table to maintain the mapping relationship between the unified call entry point and the plugin interface, so as to complete the initial configuration of the plugin adaptation framework.

[0023] Based on the plugin adaptation framework and the unified business call framework, a call chain is formed for interface operation, unified request conversion, interface mapping adaptation, and plugin scheduling execution, thus completing the construction of the human-computer interface plugin adaptation framework;

[0024] The system uses a human-computer interface plugin adaptation framework to scan a preset plugin directory to obtain plugin capability description information. Based on the plugin capability description information and a duplicate plugin verification mechanism, it outputs a plugin capability registry that stores all plugin capabilities and interface information.

[0025] Preferably, the human-machine interface plugin adaptation framework scans a preset plugin directory to obtain plugin capability description information, and based on the plugin capability description information and a duplicate plugin verification mechanism, outputs a plugin capability registry that stores all plugin capabilities and interface information, including:

[0026] The human-computer interface plugin adaptation framework is used to scan the preset plugin directory and obtain plugin description information, which includes plugin name, industry type of plugin, list of plugin interfaces and plugin runtime dependency information.

[0027] The plugin description information is read using the human-computer interface plugin adaptation framework, and the interface name, interface parameter structure and return data structure are extracted from the plugin description information as plugin interface definition information.

[0028] Based on the plugin interface definition information, a plugin capability description object is generated, and the plugin capability description object is written into the plugin capability registry. During the writing process, duplicate plugin verification is performed using the index entries.

[0029] The plugin registration process is completed based on the plugin verification results. When a plugin is enabled, disabled, or uninstalled, the index entries are updated or deleted to obtain a plugin capability registry that stores all plugin capabilities and interface information.

[0030] Preferably, the plugin description information is read using a human-machine interface plugin adaptation framework, and the interface name, interface parameter structure, and return data structure are extracted from the plugin description information as plugin interface definition information, including:

[0031] The human-computer interface plugin adaptation framework receives plugin description information, normalizes, reorders, and unifies the granularity of the plugin description information, and outputs a standardized plugin description sequence based on the processing results.

[0032] The structural identifier features and content change frequency of each plugin description field in the statistical standardized plugin description sequence are used to locate the boundary feature points of the plugin description information based on the structural identifier features, and to distinguish the boundary range of three types of parameters: interface name, interface parameter structure, and return data structure based on the boundary feature points.

[0033] Using the boundary point where the content change frequency changes from active to stable as the cutting point, the standardized plugin description sequence is divided into interface name blocks, input parameter blocks, and return data blocks to obtain a coarse-grained division result of the interface structure;

[0034] Based on the coarse-grained partitioning results, the information entropy values ​​of each subsequence in the interface name block, input parameter block, and return data block are analyzed, and the content change frequency distribution of the subsequence is quantified according to the information entropy values.

[0035] When the frequency distribution of content changes is greater than or equal to a preset threshold, a secondary segmentation process is performed within each corresponding subsequence to separate independent interface names, input parameters, and return data, which are then added to the interface name block, input parameter block, and return data block as plugin interface definition information.

[0036] Preferably, the plugin description information is normalized, reordered, and granularized, and a standardized plugin description sequence is output based on the processing results, including:

[0037] The plugin description information is semantically aligned by using a pre-built field semantic fingerprint library, and then the fields with the same function are mapped to a unified standard field semantic code after semantic alignment to complete the normalization process.

[0038] The complexity entropy value of the plugin description information is analyzed. Based on the complexity entropy value, the normalized plugin description information is topologically reorganized according to the target logical hierarchy to aggregate the scattered parameter attributes to the corresponding parent structure according to their belonging relationship, thus completing the sequential reorganization process.

[0039] A dual sliding window granularity discrimination mechanism is adopted, in which a standard granularity window and a reference granularity window are set to slide synchronously along the recombined plug-in description information, and the information entropy difference of the fields in the two windows is calculated in real time.

[0040] When the information entropy difference between two windows is greater than or equal to a preset threshold, it is determined that the granularity of the current region field does not match the standard granularity. Then, attribute aggregation or hierarchical splitting is performed on the plugin description information to unify the description granularity of all plugin description information to the preset standard field granularity level, and a standardized plugin description sequence is output.

[0041] Preferably, a unified interface model library is built within the framework for constructing human-computer interface plugin adaptation, and interface mapping rules between the unified interface model library and plugin interfaces are established in conjunction with the plugin capability registry. Based on these interface mapping rules, call requests are processed, and plugin processing result information is generated, including:

[0042] All screen business operations and interface interaction events are collected and classified to obtain a list of interface types to be uniformly abstracted. The list of interface types is then organized in a structured manner according to the interface description structure to build a standard data structure for a unified interface model. The interface description structure includes a uniformly agreed interface name, input parameter structure, and return result structure.

[0043] A dual-end data source is generated based on the standard data structure and unified interface model library. An interface mapping relationship and parameter mapping rules are established using the interface type and the dual-end data source. The interface mapping rules are then written into the interface mapping rule table for storage.

[0044] The system receives call requests based on a unified business call entry point, performs verification processing on the call requests, and sends them to the human-machine interface plugin adaptation framework to determine the industry interface adaptation component. The industry interface adaptation component is then combined with the interface mapping rule table to obtain the plugin interface call request and distribute it to the plugin instance.

[0045] After receiving a plugin API call request, the plugin instance parses the input parameters of the plugin API call request and generates the corresponding plugin processing result information according to its own business logic, and returns it to the industry interface adaptation component to obtain the plugin processing result information and complete the single plugin capability call processing.

[0046] Preferably, the process involves generating a dual-end data source based on a standard data structure and a unified interface model library, establishing interface mapping relationships and parameter mapping rules using interface types and dual-end data sources, and storing the obtained interface mapping rules in an interface mapping rule table.

[0047] Standard data structures are written into a unified interface model library, and each unified interface is assigned a unique interface identifier and configured with a corresponding retrieval method within the unified interface model library, thus obtaining a unified interface model library with retrieval capabilities.

[0048] Extract unified interface definition information from the unified interface model library and extract plugin interface definition information from the plugin capability registry, and use the unified interface definition information and plugin interface definition information as dual-end data sources.

[0049] Based on the interface name, interface type, or preset mapping rules, the dual-end data sources are matched, and an interface mapping relationship between the unified interface and the plugin interface is established according to the matching results.

[0050] Based on the unified interface that has been matched, the correspondence between the input parameter structure and the return result structure is analyzed to establish a one-to-one mapping between the parameter fields of the unified interface and the parameter fields of the plugin interface, and the parameter mapping rules are obtained.

[0051] Based on the interface mapping relationship and parameter-level mapping rules, interface mapping rules between the unified interface model library and plugin interfaces are generated, and the interface mapping rules are written into the interface mapping rule table for storage.

[0052] Preferably, the process involves receiving call requests based on a unified business call entry point, performing verification processing on the call requests, and then sending them to the human-machine interface plugin adaptation framework to determine the industry interface adaptation component. The process of combining the industry interface adaptation component with the interface mapping rule table to obtain the plugin interface call request and distribute it to the plugin instance includes:

[0053] When a user interface operation is triggered, the request information is encapsulated into a unified interface call request through a unified business call entry point, and the unified interface call request is combined into data to be verified according to a preset field order.

[0054] The digest algorithm is used to calculate the digest value of the data to be verified to generate a verification code. The verification code is written into the additional verification information of the unified interface call request, and the call request to be sent is sent to the human-machine interface plugin adaptation framework.

[0055] After receiving the call request to be sent, the human-machine interface plugin adaptation framework searches and matches in the unified interface model library according to the call request to be sent, determines the unified interface definition, and determines the industry interface adaptation component based on the unified interface definition.

[0056] The industry interface adaptation component searches the interface mapping rule table for matching parameter mapping relationships based on the interface name of the call request to be sent, and performs field matching, parameter reorganization and data type conversion on the input parameters of the unified interface call request based on the parameter mapping relationships to obtain a parameter structure that conforms to the plugin interface definition.

[0057] Based on the transformed parameter structure, a plugin interface call request is generated, and the plugin interface call request is distributed to the plugin instance of the corresponding industry type for execution.

[0058] Preferably, a digest algorithm is used to calculate the digest value of the data to be verified to generate a verification code, and the verification code is written into the additional verification information of the unified interface call request. The resulting call request is sent to the human-machine interface plugin adaptation framework, including:

[0059] Load the target initial link variable as the starting base value for the digest operation, and divide the data to be verified into several operation groups according to the target unit. Starting from the starting base value, perform four rounds of main loop operation on each operation group in sequence to output the operation status variable after the iteration is completed.

[0060] Several operational state variables are concatenated and combined to generate a digest value of the target length, and the digest value is determined as a unique anti-tampering verification code bound to the unified interface call request;

[0061] Write the anti-tampering verification code into the additional verification information field of the unified interface call request so that the unified interface call request and the anti-tampering verification code are bound together, thus completing the encapsulation of the call request to be sent.

[0062] The pending call request is sent to the human-machine interface plugin adaptation framework, and the anti-tampering verification code is extracted from the additional verification information field. The code is then compared with the recalculated verification code. If the comparison is consistent, it is determined that the pending call request has not been tampered with and the interface adaptation process can proceed. If the comparison is inconsistent, it is determined that the pending call request data is abnormal and the call is terminated.

[0063] Preferably, the industry interface adaptation component encapsulates the plugin processing result information and sends it to the human-machine interface plugin adaptation framework to execute interface operations. During the operation, it implements on-demand control of the plugin instance's running behavior based on the plugin's running status, including:

[0064] The industry interface adaptation component receives the plugin processing result information from each plugin instance, encapsulates the plugin processing result information in a unified manner, generates a unified interface return result, and sends it to the human-machine interface plugin adaptation framework.

[0065] The human-machine interface plugin adaptation framework receives the results returned by the unified interface, performs classification and summary processing, and transmits the summary results to the human-machine interface. The human-machine interface then performs the corresponding interface operation based on the interface interaction information.

[0066] During the operation of the human-machine interface, a plugin running status table is established based on the running status information of each plugin instance. Based on the running mode or business scenario, the applicable scenario rules of each plugin instance are read from the plugin running status table to determine which plugin instances need to be enabled or disabled, so as to achieve on-demand control of the running behavior of plugin instances.

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

[0068] 1. This invention constructs a plugin adaptation framework in a human-machine interface system and establishes a unified business call entry point to receive interface operation and interaction event requests. A unified interface model library is established within the plugin adaptation framework to uniformly abstract and define the business interfaces and interface interaction events provided by the system platform. During plugin access, the plugin interface list and parameter structure are parsed using plugin description information to generate plugin capability description information, which is then written into the plugin capability registry for unified management. An industry interface adaptation component is designed to convert unified interface calls into corresponding plugin interface calls through interface mapping rules. When performing operations on the human-machine interface, a call request is generated through the unified interface. The plugin adaptation framework sends the call request to the corresponding plugin instance for processing according to the interface mapping relationship, and uniformly encapsulates the return results from multiple plugins before feeding them back to the human-machine interface for display. Simultaneously, a plugin runtime status management mechanism controls the plugin's activation status, dynamically adjusting the plugin's execution scope under different system operating modes. This enables flexible access and expansion of plugins from different industries and has significant engineering application value.

[0069] 2. This invention relates to a human-machine interface plugin invocation mechanism based on a unified interface model. A unified interface model library is established in the human-machine interface to uniformly abstract and define system business interfaces and interface interaction events. The human-machine interface initiates invocation requests to plugins through the unified interface, thereby decoupling the system platform from the plugins. At the same time, corresponding interface adaptation components are established for different industries, and the mapping rules between the unified interface and the plugin interface are maintained in the plugin adaptation framework. The industry interface adaptation component converts the unified interface invocation request into a plugin interface invocation request according to the mapping relationship, thereby enabling plugins with different interface specifications to access and run in the unified platform.

[0070] 3. During the plugin loading process, this invention obtains and parses plugin description information, generates plugin capability description objects, and writes them into the plugin capability registry. By establishing a plugin capability index structure, it achieves unified management and rapid location of plugin capabilities. When the human-machine interface generates an operation or interaction event, it generates a unified interface call request through a unified business call entry point. The plugin adaptation framework sends the call request to the corresponding plugin instance for processing, and uniformly encapsulates and summarizes the return results of multiple plugins before feeding them back to the human-machine interface, which then performs the interface display or interactive operation.

[0071] 4. This invention establishes a plugin running status table in the plugin adaptation framework, dynamically adjusts the plugin enabling status according to the system running mode or business scenario, and sends call requests only to plugin instances that are in the enabling state during the plugin call process, thereby realizing dynamic control of the plugin execution scope.

[0072] 5. This invention introduces a plugin adaptation layer into the human-machine interface plugin framework of a general automation platform. This layer unifies and transforms the interface definitions, calling methods, and parameter organization forms of different plugin specifications, and establishes a unified interface mapping mechanism. Plugin call adaptation is completed at runtime. At the same time, a unified scheduling and management mechanism is introduced during plugin operation to uniformly control the loading, calling, and running status of plugins. This enables the platform to achieve unified access and operation of plugins from multiple industries without changing the overall architecture of the human-machine interface, reducing plugin development and system maintenance costs, and improving the system's versatility, scalability, and operational controllability. Attached Figure Description

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

[0074] Figure 1 This is a flowchart of a general human-machine interface plug-in adaptation method for multi-industry applications according to an embodiment of the present invention;

[0075] Figure 2 This is a schematic diagram of the plug-in adaptation framework structure in a general human-machine interface plug-in adaptation method for multi-industry applications according to an embodiment of the present invention.

[0076] Figure 3 This is a flowchart of plug-in access and interface adaptation in a general human-machine interface plug-in adaptation method for multi-industry applications according to an embodiment of the present invention.

[0077] Figure 4This is a schematic diagram illustrating the plug-in runtime call adaptation method for a universal human-machine interface plug-in for multi-industry applications according to an embodiment of the present invention.

[0078] Figure 5 This is a flowchart of section S1 of a general human-machine interface plug-in adaptation method for multi-industry applications according to an embodiment of the present invention. Detailed Implementation

[0079] To further illustrate the various embodiments, the present invention provides accompanying drawings, which are part of the disclosure of the present invention. These drawings are mainly used to illustrate the embodiments and can be used in conjunction with the relevant descriptions in the specification to explain the operating principles of the embodiments. With reference to these drawings, those skilled in the art should be able to understand other possible implementation methods and the advantages of the present invention.

[0080] According to embodiments of the present invention, a general human-machine interface plug-in adaptation method for multi-industry applications is provided.

[0081] The present invention will now be further described in conjunction with the accompanying drawings and specific embodiments, such as... Figure 1 As shown, the universal human-machine interface plug-in adaptation method for multi-industry applications according to an embodiment of the present invention includes:

[0082] Step S1: Based on the data access and screen operation encapsulation results, construct a human-machine interface plugin adaptation framework. Use the human-machine interface plugin adaptation framework to parse and process the plugin description information to obtain the plugin capability description information and write it to the plugin capability registry.

[0083] like Figure 5As shown, in one embodiment, a human-computer interface (HCI) plugin adaptation framework is constructed based on the data access and screen operation encapsulation results. This framework is used to parse and process plugin description information to obtain plugin capability description information, which is then written to the plugin capability registry. This includes: abstracting interface elements including windows, toolbars, and right-click menus into a unified interface; encapsulating data access logic into a unified data access interface; and encapsulating screen operations including screen elements, toolbar creation, user interaction, and screen switching into a unified interface call format with a unified parameter structure description. A centralized request interface is built to uniformly receive all calls and event requests initiated by the HCI interface. Based on the unified interface, unified data access interface, interface call format, and centralized request interface, a unified... A business invocation framework is established. A plugin capability registry is created to store plugin capability descriptions. A unified interface definition is read from the same interface model library to construct a unified invocation entry point. Simultaneously, an interface mapping rule table is established to maintain the mapping relationship between the unified invocation entry point and plugin interfaces, completing the initial configuration of the plugin adaptation framework. Based on the plugin adaptation framework and the unified business invocation framework, a call chain is formed for interface operation, unified request transformation, interface mapping adaptation, and plugin scheduling execution, completing the construction of the human-machine interface plugin adaptation framework. The human-machine interface plugin adaptation framework scans a preset plugin directory to obtain plugin capability descriptions. Based on the plugin capability descriptions and a duplicate plugin verification mechanism, a plugin capability registry storing all plugin capabilities and interface information is output.

[0084] In one embodiment, the process of using a human-machine interface plugin adaptation framework to scan a preset plugin directory to obtain plugin capability description information, and outputting a plugin capability registry storing all plugin capabilities and interface information based on the plugin capability description information and a duplicate plugin verification mechanism, includes: scanning a preset plugin directory using the human-machine interface plugin adaptation framework to obtain plugin description information containing the plugin name, the industry type to which the plugin belongs, a list of plugin interfaces, and plugin runtime dependency information; reading the plugin description information using the human-machine interface plugin adaptation framework to extract the interface name, interface parameter structure, and return data structure from the plugin description information as plugin interface definition information; generating a plugin capability description object based on the plugin interface definition information, writing the plugin capability description object into the plugin capability registry, and performing duplicate plugin verification processing using index entries during the writing process; completing the plugin registration process based on the plugin verification processing results, and updating or deleting index entries when a plugin is enabled, disabled, or uninstalled to obtain a plugin capability registry storing all plugin capabilities and interface information.

[0085] In one embodiment, using a human-machine interface plugin adaptation framework to read plugin description information and extract interface names, interface parameter structures, and return data structures from the plugin description information as plugin interface definition information includes: the human-machine interface plugin adaptation framework receiving plugin description information, normalizing, reordering, and unifying the granularity of the plugin description information, and outputting a standardized plugin description sequence based on the processing results; and statistically analyzing two types of features for each description field in the standardized plugin description sequence unit by unit: one is structural identification features, i.e., the standard semantic encoding attributes corresponding to the field; the other is content change frequency, i.e., the frequency of content attribute differences between adjacent fields, quantified into a specific range. The degree of content change within the domain is analyzed. The starting position of the semantic encoding of the interface name is taken as the starting point of the interface name block, and the point where the content change frequency changes from low to high is taken as the ending point of the interface name block, which also serves as the starting point of the input parameter block. The point where the content change frequency changes from high to low is taken as the ending point of the input parameter block, which also serves as the starting point of the return data block. Finally, the boundary feature points of the three types of structures are located. Using the located boundary feature points as cutting points, the standardized plugin description sequence is completely cut into three independent structural blocks, namely the interface name block, the input parameter block, and the return data block, thus completing the coarse-grained division of the interface structure.

[0086] For each coarse-grained block, it is split into continuous sub-sequence units. The information entropy value of each sub-sequence is calculated based on the information entropy formula. The entropy value quantifies the content complexity and field distribution characteristics of the sub-sequence: the higher the entropy value, the more independent fields the sub-sequence contains and the more complex the content distribution; the lower the entropy value, the simpler the content of the sub-sequence and the closer it is to a single independent field. The information entropy difference between adjacent sub-sequences is calculated in turn. When the entropy difference is greater than or equal to a preset threshold and the entropy values ​​of the two sub-sequences are not 0, the position is determined to be the boundary point between two independent fields, and a secondary cutting is performed at this point. After traversing each coarse-grained block, the originally continuous block is split into several independent field units. Each unit corresponds to a complete definition item, such as a single parameter field or a single return field.

[0087] The independent fields obtained from the segmentation are categorized according to block attributes: the core field within the Interface Name block is extracted as the Interface Name; all independent fields within the Input Parameter block are organized according to hierarchical relationships to obtain attributes such as parameter field names, data types, and nesting structures, forming a complete input parameter structure; all independent fields within the Return Data block are organized according to hierarchical relationships to obtain attributes such as return field names, data types, and nesting structures, forming a complete return data structure; according to the preset plugin interface definition data structure specification, the three core elements of the extracted Interface Name, Input Parameter Structure, and Return Data Structure are structured and organized, clarifying the hierarchical relationships, data type constraints, and attribute annotation rules of the fields, ultimately forming standardized plugin interface definition information with a unified format that can be directly used for plugin registration and interface mapping.

[0088] In one embodiment, the plugin description information is normalized, reordered, and granularized, and a standardized plugin description sequence is output based on the processing results. This includes: a pre-built field semantic fingerprint library for the human-computer interface plugin adaptation framework, which stores the mapping relationship between all field identifiers and standard semantic codes, covering the same functional fields with different naming styles such as English abbreviations, Chinese aliases, and uppercase and lowercase variants. During processing, all field identifiers in the plugin description information are traversed, and each field identifier is matched with the fingerprint database. Fields with the same function are uniformly mapped to standard semantic codes. Redundant comments, format control characters, and unstructured explanatory text in the plugin description information are automatically removed simultaneously to eliminate heterogeneity at the semantic level and complete semantic normalization. The structural complexity entropy value of each field after normalization is calculated to quantify the hierarchical nesting depth and the number of associated attributes of the fields. Taking the interface meta-information layer, input parameter structure layer, and return data structure layer as fixed target logical layers, all field units are topologically sorted and reorganized. Specifically, the top-level interface definition node is located, and the parameter attributes and nested sub-fields scattered in various parts of the description are aggregated and mounted to the parent structure corresponding to the input parameters and return data according to their subordinate relationships. This corrects the problem of disordered field order and fragmented structure in the original description, and forms a description structure with clear hierarchy and fixed order after reorganization.

[0089] A dual-sliding-window granularity discrimination mechanism is adopted. A standard granularity window matching the standard field granularity is pre-set, and a reference granularity window is used for comparison. The two windows slide synchronously along the recombined description sequence. The information entropy difference of the field sets in the two windows is calculated in real time. When the entropy difference is greater than or equal to a preset threshold, it is determined that the granularity of the current region's fields does not match the standard granularity. If the entropy value of the reference window is significantly higher than that of the standard window, it means that the granularity of the current region is too fine, that is, a single attribute is split into multiple independent fields. In this case, an aggregation operation is performed on the scattered attributes to merge them into field units of standard granularity. If the entropy value of the reference window is significantly lower than that of the standard window, it means that the granularity of the current region is too coarse, that is, multiple fields are combined into a composite field. In this case, a splitting operation is performed according to the hierarchical relationship to decompose it into fields of standard granularity. The granularity of all description fields is unified to the preset standard field granularity level, and a standardized plugin description sequence with fixed field order, unified semantic encoding, and consistent granularity is output.

[0090] like Figure 2 As shown, it needs to be explained that the implementation process of step S1 mainly includes two steps: building a human-computer interface plugin adaptation framework and obtaining plugin specification information and describing its capabilities. The specific implementation process is as follows:

[0091] Step 1: Build a human-computer interface plugin adaptation framework;

[0092] When the human-machine interface (HMI) starts, a unified business call framework is constructed to encapsulate interface display, data access, and screen operations. Interface operation requests are converted into unified call requests, which are then initiated through unified call methods. The specific steps are as follows: Interface elements such as forms, toolbars, and right-click menus are abstracted into unified interface objects, and method mapping is implemented through unified interface definitions; data access logic is encapsulated into a unified data access interface, supporting real-time library and configuration library operations; screen operations (screen elements, right-click menu creation, event handling, initialization, operation mode changes, toolbar creation, user interaction, refresh, screen switching, windows and pop-ups, toolbar menus, hover tips, etc.) are uniformly encapsulated into interface call formats and described using a unified parameter structure; and calls and event requests initiated by the HMI are centrally received, providing the operational foundation for subsequent unified interface model construction and unified interface calls.

[0093] Load the plugin adaptation framework component and complete the initial configuration of the plugin adaptation framework: The plugin adaptation framework is used to implement plugin access management, interface adaptation processing, and plugin operation scheduling functions. It includes a plugin capability registry, a unified interface model library, an interface mapping rule table, and a plugin operation management module. The initialization process includes: creating a plugin capability registry to store plugin capability description information; loading the unified interface model library, reading the system's preset unified interface definitions, and forming a unified call entry point; establishing an interface mapping rule table to maintain the mapping relationship between unified interfaces and plugin interfaces; and initializing the plugin operation management module to record the plugin's running status and manage and monitor the interface call process.

[0094] Step 2: Obtain plugin specification information and describe its capabilities;

[0095] (1) The plugin adaptation framework scans the preset plugin directory, loads the plugin, and obtains the plugin description information through the plugin export interface, including the plugin name, the industry type to which the plugin belongs, the plugin interface list, and the plugin runtime dependency information; among which the plugin interface list is used to describe the set of business interfaces provided by the plugin.

[0096] (2) The plugin adaptation framework parses the obtained plugin description information and extracts the plugin interface definition information. The parsing process includes reading the plugin description information and extracting interface definition information such as interface name, interface parameter structure and return data structure. If the plugin description information is parsed successfully, a plugin capability description object is generated according to the parsing result and written into the plugin capability registry. If the format of the plugin description information does not conform to the plugin specification or an exception occurs during the parsing process, the current plugin access process is terminated and the plugin access failure information is recorded.

[0097] (3) The plugin capability registry establishes an index query structure with the plugin identifier as the index, which is used to quickly locate and query plugin capability information during system operation. The specific process includes: normalizing the plugin identifier field in the plugin description information and using it as the index key; establishing the correspondence between the plugin identifier and the plugin capability description object using a key-value mapping structure, where the plugin identifier is the key and the plugin capability description object is the value; when the plugin capability description object is written to the plugin capability registry, an index entry is generated synchronously, and duplicate plugin identifiers are checked. If duplicate identifiers exist, an exception is recorded and the current plugin registration process is terminated; when a plugin is enabled, disabled, or uninstalled, the corresponding index entry is updated or deleted to keep the index query structure consistent with the plugin running status.

[0098] Step S2: Build a unified interface model library within the framework for building human-computer interface plugin adaptation, and establish interface mapping rules between the unified interface model library and plugin interfaces in conjunction with the plugin capability registry. Process the call request based on the interface mapping rules and generate plugin processing result information.

[0099] In one embodiment, a unified interface model library is built within the framework for constructing human-computer interface plugin adaptation. An interface mapping rule is established between the unified interface model library and plugin interfaces, based on the plugin capability registry. Call requests are processed according to this mapping rule, generating plugin processing result information. This includes: fully collecting and classifying screen business operations and interface interaction events to obtain a list of interface types to be uniformly abstracted; organizing the interface type list according to the interface description structure to construct a standard data structure for the unified interface model. The interface description structure includes a uniformly agreed-upon interface name, input parameter structure, and return result structure. A dual-end data source is generated based on the standard data structure and the unified interface model library, and... Establish interface mapping relationships and parameter mapping rules based on interface types and dual-end data sources. Store these interface mapping rules in an interface mapping rule table. Receive call requests based on a unified business call entry point. After performing validation on the call requests, send them to the human-machine interface plugin adaptation framework to determine the industry interface adaptation component. Combine the industry interface adaptation component with the interface mapping rule table to obtain the plugin interface call request and distribute it to the plugin instance. After receiving the plugin interface call request, the plugin instance parses the input parameters of the plugin interface call request and generates the corresponding plugin processing result information according to its own business logic, returning it to the industry interface adaptation component to obtain the plugin processing result information and complete the single plugin capability call processing.

[0100] In one embodiment, generating a dual-end data source based on a standard data structure and a unified interface model library, and establishing interface mapping relationships and parameter mapping rules using interface types and dual-end data sources, and storing the interface mapping rules in an interface mapping rule table includes: centrally writing standard data structures into a unified interface model library, assigning a unique interface identifier and configuring a corresponding retrieval method for each unified interface in the unified interface model library, resulting in a unified interface model library with retrieval capabilities; extracting unified interface definition information from the unified interface model library and extracting plugin interface definition information from the plugin capability registry, using the unified interface definition information and plugin interface definition information as dual-end data sources; performing matching processing on the dual-end data sources based on interface names, interface types, or preset mapping rules, and establishing interface mapping relationships between unified interfaces and plugin interfaces based on the matching results; performing correspondence analysis on the input parameter structure and return result structure based on the matched unified interfaces, establishing a one-to-one mapping between unified interface parameter fields and plugin interface parameter fields, and obtaining parameter mapping rules; generating interface mapping rules between the unified interface model library and plugin interfaces based on the interface mapping relationships and parameter-level mapping rules, and storing the interface mapping rules in an interface mapping rule table.

[0101] In one embodiment, receiving a call request based on a unified business call entry point and sending it to the human-machine interface plugin adaptation framework after performing verification processing on the call request to determine the industry interface adaptation component, and combining the industry interface adaptation component with the interface mapping rule table to obtain the plugin interface call request and distribute it to the plugin instance includes: when the human-machine interface triggers an interface operation, encapsulating the request information into a unified interface call request through the unified business call entry point, and combining the unified interface call request into data to be verified according to a preset field order; using a digest algorithm to calculate the digest value of the data to be verified to generate a verification code, and writing the verification code into the additional verification information of the unified interface call request, thereby obtaining the call request to be sent to the human-machine interface plugin adaptation framework. The framework is configured as follows: After receiving the call request to be sent, the human-machine interface plugin adaptation framework searches and matches the unified interface model library according to the call request to determine the unified interface definition, and determines the industry interface adaptation component based on the unified interface definition. The industry interface adaptation component searches and matches the parameter mapping relationship in the interface mapping rule table according to the interface name of the call request to be sent, and performs field matching, parameter recombination and data type conversion processing on the input parameters of the unified interface call request according to the parameter mapping relationship to obtain a parameter structure that conforms to the plugin interface definition. Based on the converted parameter structure, a plugin interface call request is generated and distributed to the corresponding industry type plugin instance for execution.

[0102] In one embodiment, a digest algorithm is used to calculate the digest value of the data to be verified to generate a check code, and the check code is written into the additional verification information of the unified interface call request. The resulting call request is then sent to the human-machine interface plugin adaptation framework. This includes: loading a preset target initial link variable as the starting reference value for the digest operation. This initial link variable is a fixed constant agreed upon by the sending and receiving ends to ensure that the sending and receiving ends have consistent initial operation conditions under completely identical input data; splitting the data to be verified into several standard operation groups according to a preset target unit length, each operation group can be further decomposed into a fixed number of sub-operation units, thereby converting the data to be verified of variable length into an adaptation loop. The standardized input unit for computation enables digest calculation of request body data of arbitrary length, adapting to unified interface call requests of different scales, and controlling memory usage during computation through iterative processing of groups. After grouping, the computation starts from the initial reference value corresponding to the initial link variable, and four rounds of main loop computation are performed on each computation group in sequence. In each round of loop, the sub-computation units within the group are obfuscated through preset nonlinear transformation functions, bit shift operations, constant superposition and modular addition operations. After completing the four rounds of computation for each group, the updated computation state variable is used as the starting value for the next group of computation and iterated sequentially, resulting in a significant change in the generated checksum.

[0103] After all the operation groups have completed iteratively, the final output of multiple sets of operation state variables are concatenated and combined in a fixed order to generate a summary value of a preset target length. This summary value is then used as a unique anti-tampering verification code bound to the current unified interface call request. This process converts the intermediate operation state into a fixed-length, standard-format verification identifier, which is easy to attach to the call request for transmission without significantly increasing the data volume of the request. It also facilitates rapid comparison by the receiving end, improving the processing efficiency of the verification process. After generating the verification code, the anti-tampering verification code is written into the additional verification information field of the unified interface call request, forming a one-to-one binding relationship between the request body and the corresponding verification code. This completes the full encapsulation of the call request to be sent, allowing the verification information to be stored separately from the business request body and bound together.

[0104] After encapsulation, the call request to be sent is sent to the human-machine interface plugin adaptation framework. Upon receiving the request, the framework extracts the original anti-tampering verification code from the additional verification information field. Then, based on the received request body, it recalculates the recalculated verification code according to the initial variables, grouping rules, and four-round loop operation logic that are completely consistent with the sending end. This allows the receiving end to completely reproduce the digest operation process of the sending end and generate a verification result that is identical to that of the sending end. The extracted original anti-tampering verification code and the recalculated verification code are compared for consistency. If they match, it is determined that the call request to be sent has not been tampered with during transmission and is legal and valid, allowing it to proceed to the subsequent interface adaptation processing flow. If they do not match, it is determined that the call request data is abnormal and may have been tampered with, and the current call process is terminated directly.

[0105] like Figure 3 and Figure 4 As shown, it should be noted that the implementation process of step S2 is mainly based on two aspects: constructing a unified interface abstraction and establishing industry interface adaptation components, and executing plugin capability calls based on the unified interface model. The specific implementation process is as follows:

[0106] Step 1: Construct a unified interface abstraction and establish industry interface adaptation components;

[0107] (1) Establish a unified interface model library in the plugin adaptation framework to perform unified interface abstraction of business operations and interface interaction events in the screen. The process of establishing the unified interface model library includes: classifying various business operations and interaction events involved in the system and determining the interface types that need to be uniformly abstracted; standardizing the definition of each type of interface, unifying the interface name, input parameter structure and return result structure, so that interfaces with the same semantics but different implementation methods in different plugins can be mapped to the same abstract interface; organizing the unified interface definition according to the preset interface description structure, wherein the interface description structure includes the interface name, input parameter structure and return result structure, thereby constructing the unified interface model data structure, and writing each interface model into the unified interface model library in a structured form for centralized management; establishing an interface identifier and retrieval method for each unified interface in the interface model library for searching in the subsequent interface matching and calling process.

[0108] (2) Establish industry interface adaptation components for different business industries. The industry interface adaptation components are used to realize the conversion relationship between the unified interface and the corresponding industry plugin interface, and establish the mapping relationship between the unified interface and the plugin interface in the interface mapping rule table. The process of obtaining the mapping relationship is as follows: extract the unified interface definition information from the unified interface model library and extract the interface definition information of the corresponding plugin from the plugin capability registry; perform matching processing on the unified interface definition and the plugin interface definition based on the interface name, interface type or preset mapping rule to establish the correspondence between the unified interface and the plugin interface; in the matching process, perform correspondence analysis on the input parameter structure and the return result structure to establish the mapping relationship between the parameter fields; generate the mapping data between the unified interface and the plugin interface according to the matching result, and write the mapping data into the interface mapping rule table for conversion processing when the interface is called later.

[0109] Step 2: Execute plugin capability calls based on the unified interface model;

[0110] (1) When the human-machine interface performs interface operations, the request information is encapsulated into a unified interface call request through a unified business call entry point, and the call request is sent to the plugin adaptation framework for processing. The call request includes the request body and additional verification information. The request body includes at least the interface name, input parameter information, call context information and timestamp. The call context information includes interface interaction event information, target primitive information or interface position coordinate information, and the timestamp is the time when the call occurred.

[0111] During the call request sending process, the call request is protected against tampering. The request body is combined according to the preset field order to form the data to be verified. A digest algorithm is used to calculate the digest of the data to be verified to generate a verification code. The verification code is written into the additional verification information and sent to the plugin adaptation framework along with the unified interface call request. After receiving the call request, the plugin adaptation framework reads the verification code from the additional verification information, recalculates the verification code according to the request body, and compares it. Based on the comparison result, it determines whether the call request has been tampered with.

[0112] (2) After receiving the unified interface call request, the plugin adaptation framework matches the interface name in the unified interface model library according to the call request and determines the corresponding unified interface definition. If no corresponding interface definition is found, the call processing is terminated and the interface call exception information is recorded.

[0113] (3) The plugin adaptation framework determines the corresponding industry interface adaptation component based on the matched unified interface definition, and passes the unified interface call request to the current industry interface adaptation component for processing.

[0114] (4) The industry interface adaptation component converts the unified interface call request into a plugin interface call request according to the interface mapping rule table, and distributes the call request to multiple plugin instances of the corresponding industry type that are in the enabled state. The conversion process includes: matching the corresponding plugin interface definition in the interface mapping rule table according to the interface name in the unified interface call request; reading the parameter mapping relationship between the unified interface and the plugin interface recorded in the interface mapping rule table, the parameter mapping relationship includes at least the unified interface parameter field, the plugin interface parameter field, and the parameter type correspondence; performing field matching, parameter reorganization, and data type conversion on the input parameters in the unified interface call request according to the parameter mapping relationship to form a parameter structure that conforms to the plugin interface definition; generating a plugin interface call request based on the converted parameter structure, and distributing the plugin interface call request to the plugin instance of the corresponding industry type for execution.

[0115] (5) After each plugin instance receives the plugin interface call request, it parses the input parameters in the plugin interface call request, processes the call request according to its own business logic, generates plugin processing result information, and returns the plugin processing result information to the industry interface adaptation component.

[0116] Step S3: After encapsulating the plugin processing result information, the industry interface adaptation component sends it to the human-machine interface plugin adaptation framework to perform interface operations. During the operation, the plugin instance's running behavior is controlled as needed based on the plugin's running status.

[0117] In one embodiment, the industry interface adaptation component encapsulates the plugin processing result information and sends it to the human-machine interface plugin adaptation framework to execute interface operations. During the operation, it implements on-demand control of plugin instance behavior based on the plugin's running status. This includes: the industry interface adaptation component receiving plugin processing result information from each plugin instance, uniformly encapsulating the plugin processing result information, generating a unified interface return result, and sending it to the human-machine interface plugin adaptation framework; the human-machine interface plugin adaptation framework receiving the unified interface return result, performing classification and summarization processing, and transmitting the summary result to the human-machine interface, using the human-machine interface to execute corresponding interface operations based on the interface interaction operation information; during the human-machine interface operation, a plugin running status table is established based on the running status information of each plugin instance, and the plugin applicable scenario rules corresponding to each plugin instance are read from the plugin running status table according to the running mode or business scenario to determine which plugin instances need to be enabled or disabled, thereby achieving on-demand control of plugin instance running behavior.

[0118] It should be noted that the implementation process of step S3 mainly involves processing the plugin execution results and providing interface feedback, as well as managing the plugin's running status. The specific implementation method is as follows:

[0119] Step 1: Plugin execution result processing and interface feedback;

[0120] (1) The industry interface adaptation component receives the processing result information returned by each plugin instance, and encapsulates the processing results in a unified manner to generate a unified interface return result. The interface return result includes at least the following: plugin identification information; execution result status information; returned data content; and interface interaction operation information. The interface interaction operation information is used to describe the interface operation behavior that the plugin needs to perform on the human-machine interface.

[0121] (2) The plugin adaptation framework receives the unified interface return results from the industry interface adaptation component and summarizes the return results of multiple plugins. During the summary process, the plugin adaptation framework classifies the return results according to the plugin execution status: if the plugin executes successfully, its return data is written into the result set; if the plugin fails to execute, the plugin execution exception information is recorded and the error status information is retained.

[0122] (3) The plugin adaptation framework returns the aggregated unified interface return results to the human-machine interface, and the human-machine interface performs corresponding interface operations based on the interface interaction operation information, including but not limited to: displaying prompt information at a specified position on the interface; popping up a business operation dialog box; updating the graphic element display status; and displaying the plugin processing result information. The interface operations are executed through the unified business call framework.

[0123] Step 2: Plugin runtime status management;

[0124] (1) The plugin operation management module is used to maintain the operation status information of plugin instances in the system and establish a plugin operation status table; the plugin operation status table is used to record the operation status of each plugin instance and its applicable operation scenarios; plugin operation status: enabled status and disabled status.

[0125] (2) During the operation of the human-machine interface, the operating status of the plug-in is dynamically controlled according to the system operating mode or business scenario. The system operating mode includes, but is not limited to: real-time operating mode; operation ticket mode; research and analysis mode. Dynamic control process: The plug-in operation management module detects changes in the current system operating mode or business scenario; reads the applicable scenario rules for each plug-in instance from the plug-in operation status table. The applicable scenario rules describe the applicable operating mode or business scenario corresponding to the plug-in instance; matches the current system operating mode or business scenario with the applicable scenario rules to determine the plug-in instances that need to be enabled or disabled; updates the plug-in operation status table and generates a set of plug-ins that are currently enabled.

[0126] (3) When the plugin adaptation framework executes the unified interface call, the industry interface adaptation component only sends the plugin interface call request to the plugin instance that is currently in the enabled state, thereby realizing on-demand control of the plugin running behavior.

[0127] The following section provides a further explanation of the human-computer interface plugin adaptation method proposed in this embodiment, taking into account specific business scenarios:

[0128] During the operation of the human-machine interface (HMI), when a user right-clicks on a target graphic element, the HMI detects the corresponding interface interaction event and generates a unified interface call request through a unified business call entry point. The unified interface call request includes a request body and additional verification information. The request body includes the interface name, input parameter information, call context information, and a timestamp. The call context information includes the target graphic element identifier, the graphic element's associated device ID, the mouse click position coordinates, and the interface interaction event type. For example, in this embodiment, the unified interface name can be defined as ContextMenuCreate, used to describe the right-click menu creation operation of the target graphic element.

[0129] After generating a unified interface call request in the human-machine interface, the request body is combined according to the preset field order to form the data to be verified, and a digest algorithm is used to calculate the digest of the data to be verified to generate a verification code. The verification code is written into the additional verification information and sent to the plugin adaptation framework along with the unified interface call request.

[0130] After receiving a unified interface call request, the plugin adaptation framework reads the verification code from the additional verification information and recalculates the verification code based on the request body for consistency comparison. If the verification results are consistent, the subsequent processing flow continues. If the verification fails, the current call processing is terminated and the exception information is recorded.

[0131] After the verification is passed, the plugin adaptation framework matches the corresponding unified interface definition in the unified interface model library based on the interface name in the unified interface call request, and determines the corresponding industry interface adaptation component; then, the industry interface adaptation component performs transformation processing on the unified interface call request according to the interface mapping rule table.

[0132] For example, in this embodiment, the unified interface ContextMenuCreate can be mapped to the target industry plugin interface DeviceMenuBuild through an interface mapping rule table. In the unified interface call request, the input parameters use objectId, x, and y as unified parameter fields; the target industry plugin interface uses deviceId, posX, and posY as plugin interface parameter fields. The industry interface adaptation component converts the unified interface ContextMenuCreate into the plugin interface DeviceMenuBuild according to the interface mapping relationship and parameter mapping relationship recorded in the interface mapping rule table, mapping objectId to deviceId, x to posX, and y to posY; it completes parameter reorganization and data type conversion according to the plugin interface definition to form a parameter structure that conforms to the plugin interface definition, and generates a plugin interface call request.

[0133] The plugin adaptation framework determines the currently enabled plugin instances based on the plugin running status table, and distributes the plugin interface call requests to the corresponding industry type plugin instances that are also enabled for execution.

[0134] After receiving a plugin interface call request, the plugin instance parses the input parameters and generates corresponding business menu data based on the plugin's own business logic. For example, the power grid industry plugin can generate menu items such as remote control operation and equipment information viewing; the thermal power industry plugin can generate menu items such as equipment status viewing and alarm information query.

[0135] After receiving the plugin processing result information returned by each plugin instance, the industry interface adaptation component encapsulates the processing results in a unified manner, generates a unified interface return result, and returns it to the plugin adaptation framework. The plugin adaptation framework summarizes and processes the return results of multiple plugins, writes the return data of successful execution into the unified interface return result set, and records the exception information corresponding to the failed plugins. Finally, the summarized unified interface return result is returned to the human-machine interface.

[0136] The human-machine interface executes corresponding interface operations based on the interface interaction operation information returned by the unified interface, including displaying a business operation menu at the corresponding position of the target graphic element, popping up a business operation dialog box, or updating the display status of the graphic element; the interface operations are executed through the unified business call framework, thereby completing a plug-in capability call process based on the unified interface model.

[0137] This invention enables flexible access and operation of different business industry plugins within a unified human-machine interface platform by constructing a unified interface model and industry interface adaptation mechanism. It involves building a plugin adaptation framework within the human-machine interface system and establishing a unified business call entry point to receive interface operation and interaction event requests. A unified interface model library is then established within the plugin adaptation framework to uniformly abstract and define the business interfaces and interface interaction events provided by the system platform. During plugin access, the plugin interface list and parameter structure are parsed using plugin description information to generate plugin capability description information, which is then written to the plugin capability registry for unified management. Addressing the issue of differences in plugin interface specifications across industries, a mapping relationship between the unified interface and plugin interfaces is established through an industry interface adaptation component. During plugin calls, the interface is used to determine the appropriate interface. The mapping rules convert unified interface calls into corresponding plugin interface calls. When performing operations on the human-machine interface, a call request is generated through the unified interface. The plugin adaptation framework sends the call request to the corresponding plugin instance for processing and encapsulates the return results of multiple plugins before feeding them back to the human-machine interface for display. At the same time, the plugin's activation status is controlled through a plugin running status management mechanism, and the scope of plugin participation is dynamically adjusted under different system running modes. This enables flexible access and expansion of plugins from different business industries in the unified human-machine interface system, reduces the development and maintenance costs of the system in cross-industry application scenarios, improves the system platform's scalability and operating efficiency, and provides support for the engineering application of the general automation platform in multiple industry scenarios such as power grids, thermal power, hydropower, new energy, and industrial dispatching.

[0138] According to another embodiment of the present invention, a universal human-machine interface plug-in adaptation system for multi-industry applications is also provided, the system comprising:

[0139] The framework capability registry construction module is used to build a human-computer interface plugin adaptation framework based on the data access and screen operation encapsulation results. The human-computer interface plugin adaptation framework is used to parse the plugin description information and process the capability description to obtain the plugin capability description information and write it to the plugin capability registry.

[0140] The plugin processing result information generation module is used to build a unified interface model library within the framework for building human-computer interface plugin adaptation, and to establish interface mapping rules between the unified interface model library and plugin interfaces in conjunction with the plugin capability registry. Based on the interface mapping rules, the module processes the call request and generates plugin processing result information.

[0141] The plugin operation monitoring and control module is used to encapsulate the plugin processing result information in the industry interface adaptation component and send it to the human-machine interface plugin adaptation framework to perform interface operations. During the operation, it can control the running behavior of the plugin instance on demand based on the plugin running status.

[0142] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A universal human-machine interface plug-in adaptation method for multi-industry applications, characterized in that, The method includes: Based on the encapsulation results of data access and screen operation, a human-computer interface plugin adaptation framework is constructed. The plugin description information is parsed and the capability description is processed using the human-computer interface plugin adaptation framework to obtain the plugin capability description information and write it to the plugin capability registry. Within the framework for building human-computer interface plugin adaptation, a unified interface model library is constructed, and interface mapping rules between the unified interface model library and plugin interfaces are established in conjunction with the plugin capability registry. Based on the interface mapping rules, the call requests are processed and plugin processing result information is generated. After encapsulating the plugin processing result information, the industry interface adaptation component sends it to the human-machine interface plugin adaptation framework to perform interface operations. During the operation, it implements on-demand control of the plugin instance's running behavior based on the plugin's running status.

2. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 1, characterized in that, The process of constructing a human-machine interface plugin adaptation framework based on data access and screen operation encapsulation results, parsing and processing plugin description information using the framework to obtain plugin capability description information, and writing it to the plugin capability registry includes: The interface elements, including forms, toolbars, and right-click menus, are abstracted into a unified interface. At the same time, the data access logic is encapsulated into a unified data access interface. The screen operations, including screen elements, toolbar creation, user interaction, and screen switching, are encapsulated into a unified interface call form with parameter structure description. A centralized request interface is built to uniformly receive all calls and event requests initiated by the human-machine interface. A unified business call framework is obtained based on the unified interface, unified data access interface, interface call format and centralized request interface. Create a plugin capability registry to store plugin capability description information, load the same interface model library to read the unified interface definition, build a unified call entry point, and establish an interface mapping rule table to maintain the mapping relationship between the unified call entry point and the plugin interface, so as to complete the initial configuration of the plugin adaptation framework. Based on the plugin adaptation framework and the unified business call framework, a call chain is formed for interface operation, unified request conversion, interface mapping adaptation, and plugin scheduling execution, thus completing the construction of the human-computer interface plugin adaptation framework; The system uses a human-computer interface plugin adaptation framework to scan a preset plugin directory to obtain plugin capability description information. Based on the plugin capability description information and a duplicate plugin verification mechanism, it outputs a plugin capability registry that stores all plugin capabilities and interface information.

3. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 2, characterized in that, The process of using a human-machine interface plugin adaptation framework to scan a preset plugin directory to obtain plugin capability description information, and outputting a plugin capability registry that stores all plugin capabilities and interface information based on the plugin capability description information and a duplicate plugin verification mechanism, includes: The HMI plugin adaptation framework is used to scan the preset plugin directory and obtain plugin description information, which includes plugin name, industry type of plugin, list of plugin interfaces and plugin runtime dependency information. The plugin description information is read using the human-computer interface plugin adaptation framework, and the interface name, interface parameter structure and return data structure are extracted from the plugin description information as plugin interface definition information. Based on the plugin interface definition information, a plugin capability description object is generated, and the plugin capability description object is written into the plugin capability registry. During the writing process, duplicate plugin verification is performed using the index entries. The plugin registration process is completed based on the plugin verification results. When a plugin is enabled, disabled, or uninstalled, the index entries are updated or deleted to obtain a plugin capability registry that stores all plugin capabilities and interface information.

4. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 3, characterized in that, The step of using a human-machine interface plugin adaptation framework to read plugin description information and extracting the interface name, interface parameter structure, and return data structure from the plugin description information as plugin interface definition information includes: The human-computer interface plugin adaptation framework receives plugin description information, normalizes, reorders, and unifies the granularity of the plugin description information, and outputs a standardized plugin description sequence based on the processing results. The structural identifier features and content change frequency of each plugin description field in the statistical standardized plugin description sequence are used to locate the boundary feature points of the plugin description information based on the structural identifier features, and to distinguish the boundary range of three types of parameters: interface name, interface parameter structure, and return data structure based on the boundary feature points. Using the boundary point where the content change frequency changes from active to stable as the cutting point, the standardized plugin description sequence is divided into interface name blocks, input parameter blocks, and return data blocks to obtain a coarse-grained division result of the interface structure; Based on the coarse-grained partitioning results, the information entropy values ​​of each subsequence in the interface name block, input parameter block, and return data block are analyzed, and the content change frequency distribution of the subsequence is quantified according to the information entropy values. When the frequency distribution of content changes is greater than or equal to a preset threshold, a secondary segmentation process is performed within each corresponding subsequence to separate independent interface names, input parameters, and return data, which are then added to the interface name block, input parameter block, and return data block as plugin interface definition information.

5. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 4, characterized in that, The process of normalizing, reordering, and unifying the granularity of plugin description information, and outputting a standardized plugin description sequence based on the processing results, includes: The plugin description information is semantically aligned by using a pre-built field semantic fingerprint library, and then the fields with the same function are mapped to a unified standard field semantic code after semantic alignment to complete the normalization process. The complexity entropy value of the plugin description information is analyzed. Based on the complexity entropy value, the normalized plugin description information is topologically reorganized according to the target logical hierarchy to aggregate the scattered parameter attributes to the corresponding parent structure according to their belonging relationship, thus completing the sequential reorganization process. A dual sliding window granularity discrimination mechanism is adopted, in which a standard granularity window and a reference granularity window are set to slide synchronously along the recombined plug-in description information, and the information entropy difference of the fields in the two windows is calculated in real time. When the information entropy difference between two windows is greater than or equal to a preset threshold, it is determined that the granularity of the current region field does not match the standard granularity. Then, attribute aggregation or hierarchical splitting is performed on the plugin description information to unify the description granularity of all plugin description information to the preset standard field granularity level, and a standardized plugin description sequence is output.

6. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 1, characterized in that, The process involves building a unified interface model library within the framework for adapting human-computer interface plugins, establishing interface mapping rules between the unified interface model library and plugin interfaces in conjunction with the plugin capability registry, processing call requests based on these interface mapping rules, and generating plugin processing result information, including: All screen business operations and interface interaction events are collected and classified to obtain a list of interface types to be uniformly abstracted. The list of interface types is then organized in a structured manner according to the interface description structure to construct a standard data structure for a unified interface model. The interface description structure includes a uniformly agreed interface name, input parameter structure, and return result structure. A dual-end data source is generated based on the standard data structure and unified interface model library. An interface mapping relationship and parameter mapping rules are established using the interface type and the dual-end data source. The interface mapping rules are then written into the interface mapping rule table for storage. The system receives call requests based on a unified business call entry point, performs verification processing on the call requests, and sends them to the human-machine interface plugin adaptation framework to determine the industry interface adaptation component. The industry interface adaptation component is then combined with the interface mapping rule table to obtain the plugin interface call request and distribute it to the plugin instance. After receiving a plugin API call request, the plugin instance parses the input parameters of the plugin API call request and generates the corresponding plugin processing result information according to its own business logic, and returns it to the industry interface adaptation component to obtain the plugin processing result information and complete the single plugin capability call processing.

7. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 6, characterized in that, The process of generating a dual-end data source based on a standard data structure and a unified interface model library, establishing interface mapping relationships and parameter mapping rules using interface types and dual-end data sources, and storing the obtained interface mapping rules in an interface mapping rule table includes: Standard data structures are written into a unified interface model library, and each unified interface is assigned a unique interface identifier and configured with a corresponding retrieval method within the unified interface model library, thus obtaining a unified interface model library with retrieval capabilities. Extract unified interface definition information from the unified interface model library and extract plugin interface definition information from the plugin capability registry, and use the unified interface definition information and plugin interface definition information as dual-end data sources. Based on the interface name, interface type, or preset mapping rules, the dual-end data sources are matched, and an interface mapping relationship between the unified interface and the plugin interface is established according to the matching results. Based on the unified interface that has been matched, the correspondence between the input parameter structure and the return result structure is analyzed to establish a one-to-one mapping between the parameter fields of the unified interface and the parameter fields of the plugin interface, and the parameter mapping rules are obtained. Based on the interface mapping relationship and parameter-level mapping rules, interface mapping rules between the unified interface model library and plugin interfaces are generated, and the interface mapping rules are written into the interface mapping rule table for storage.

8. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 7, characterized in that, The process of receiving call requests based on a unified business call entry point, performing verification processing on the call requests, and then sending them to the human-machine interface plugin adaptation framework to determine the industry interface adaptation component, and combining the industry interface adaptation component with the interface mapping rule table to obtain the plugin interface call request and distribute it to the plugin instance includes: When a user interface operation is triggered, the request information is encapsulated into a unified interface call request through a unified business call entry point, and the unified interface call request is combined into data to be verified according to a preset field order. The digest algorithm is used to calculate the digest value of the data to be verified to generate a verification code. The verification code is written into the additional verification information of the unified interface call request, and the call request to be sent is sent to the human-machine interface plugin adaptation framework. After receiving the call request to be sent, the human-machine interface plugin adaptation framework searches and matches in the unified interface model library according to the call request to be sent, determines the unified interface definition, and determines the industry interface adaptation component based on the unified interface definition. The industry interface adaptation component searches the interface mapping rule table for matching parameter mapping relationships based on the interface name of the call request to be sent, and performs field matching, parameter reorganization and data type conversion on the input parameters of the unified interface call request based on the parameter mapping relationships to obtain a parameter structure that conforms to the plugin interface definition. Based on the transformed parameter structure, a plugin interface call request is generated, and the plugin interface call request is distributed to the plugin instance of the corresponding industry type for execution.

9. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 8, characterized in that, The process of using a digest algorithm to calculate the digest value of the data to be verified to generate a verification code, and writing the verification code into the additional verification information of the unified interface call request, to obtain the call request to be sent to the human-machine interface plugin adaptation framework includes: Load the target initial link variable as the starting base value for the digest operation, and divide the data to be verified into several operation groups according to the target unit. Starting from the starting base value, perform four rounds of main loop operation on each operation group in sequence to output the operation status variable after the iteration is completed. Several operational state variables are concatenated and combined to generate a digest value of the target length, and the digest value is determined as the unique anti-tampering verification code bound to the unified interface call request; Write the anti-tampering verification code into the additional verification information field of the unified interface call request so that the unified interface call request and the anti-tampering verification code are bound together, thus completing the encapsulation of the call request to be sent. The pending call request is sent to the human-machine interface plugin adaptation framework, and the anti-tampering verification code is extracted from the additional verification information field. The code is then compared with the recalculated verification code. If the comparison is consistent, it is determined that the pending call request has not been tampered with and the interface adaptation process can proceed. If the comparison is inconsistent, it is determined that the pending call request data is abnormal and the call is terminated.

10. The method for adapting a universal human-machine interface plug-in for multi-industry applications according to claim 1, characterized in that, The industry interface adaptation component encapsulates the plugin processing result information and sends it to the human-machine interface plugin adaptation framework to execute interface operations. During the operation, it implements on-demand control of the plugin instance's running behavior based on the plugin's running status, including: The industry interface adaptation component receives the plugin processing result information from each plugin instance, encapsulates the plugin processing result information in a unified manner, generates a unified interface return result, and sends it to the human-machine interface plugin adaptation framework. The human-machine interface plugin adaptation framework receives the results returned by the unified interface, performs classification and summary processing, and transmits the summary results to the human-machine interface. The human-machine interface then performs the corresponding interface operation based on the interface interaction information. During the operation of the human-machine interface, a plugin running status table is established based on the running status information of each plugin instance. Based on the running mode or business scenario, the applicable scenario rules of each plugin instance are read from the plugin running status table to determine which plugin instances need to be enabled or disabled, so as to achieve on-demand control of the running behavior of plugin instances.

Images