A configuration method and device of a configuration interface, electronic equipment and system

Abstract

The application relates to a configuration method and device of a configuration interface, electronic equipment and a system. The method comprises the following steps: receiving a first mapping relationship reported by a control device, the first mapping relationship being generated by the control device scanning a physical device connected to the control device, and the first mapping relationship comprising a corresponding relationship between a point position identifier corresponding to each device point position of the physical device and a physical address corresponding to each device point position of the physical device; obtaining a pre-constructed interface template, the interface template comprising a second mapping relationship between a plurality of interface components and the point position identifier; matching the first mapping relationship and the second mapping relationship based on each point position identifier, so as to determine the physical address required to be mapped by each interface component in the interface template; and based on each determined physical address and each interface component, instantiating the interface template to obtain a configuration interface. The application reduces the configuration workload and improves the configuration accuracy of the configuration interface.

Description

Technical Field

[0001] This application relates to the field of smart IoT technology, and in particular to a configuration method, apparatus, electronic device and system for a configuration interface. Background Technology

[0002] In building intelligent control systems, the configuration interface graphically presents the operating status of physical devices (such as sensors, valves, and air conditioning units) and is the core means of achieving remote monitoring and operation. Currently, the configuration interface typically uses a two-sided manual binding mode. On the controller side, commissioning personnel manually define the physical address of each device point as an internal variable using a dedicated configuration tool. On the host computer configuration software side, configuration engineers need to draw the graphical interface and manually associate the attributes of each interface component with the previously defined internal variables one by one. This configuration method makes the mapping relationship between device points, control logic, and interface components entirely dependent on manual establishment and verification. When a building intelligent control system involves hundreds or thousands of device points, not only is the configuration workload enormous, but it is also highly susceptible to configuration errors due to mismatched variable names or incorrect address input. Summary of the Invention

[0003] This application provides a configuration method, apparatus, electronic device, and system for a configuration interface, in order to solve the problem that existing configuration methods for configuration interfaces involve a huge workload and are prone to errors.

[0004] Firstly, this application provides a method for configuring a configuration interface, including: The first mapping relationship reported by the receiving control device is generated by the control device scanning the physical devices it is connected to. The first mapping relationship includes the correspondence between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point of the physical device. Obtain a pre-built interface template, the interface template including a second mapping relationship between multiple interface components and the point identifier; Based on each of the point identifiers, the first mapping relationship and the second mapping relationship are matched to determine the physical address that each of the interface components in the interface template needs to be mapped. Based on the determined physical addresses and interface components, the interface template is instantiated to obtain the configuration interface.

[0005] Secondly, this application provides a configuration device for a configuration interface, comprising: The receiving module is used to receive a first mapping relationship reported by the control device. The first mapping relationship is generated by the control device scanning the physical devices it is connected to. The first mapping relationship includes the correspondence between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point of the physical device. The acquisition module is used to acquire a pre-built interface template, the interface template including a second mapping relationship between multiple interface components and the point identifier; The matching module is used to match the first mapping relationship and the second mapping relationship based on each of the point identifiers, so as to determine the physical address that each of the interface components in the interface template needs to be mapped; The configuration module is used to instantiate the interface template based on the determined physical addresses and interface components to obtain a configuration interface.

[0006] Thirdly, this application provides an electronic device, including: a processor and a memory; the processor is used to execute a configuration program of a configuration interface stored in the memory to implement the configuration method of the configuration interface as described above.

[0007] Fourthly, this application provides a configuration system for a configuration interface, including: a control device and a configuration device; The control device is used to scan the physical devices connected to it to generate a first mapping relationship. The first mapping relationship includes the correspondence between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point of the physical device. The configuration device is used to execute the configuration method of the configuration interface as described above.

[0008] Compared with the prior art, the technical solution provided in this application has the following advantages. The configuration method of the configuration interface provided in this application includes receiving a first mapping relationship reported by a control device. The first mapping relationship is generated by the control device scanning the physical devices it is connected to. The first mapping relationship includes the correspondence between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point of the physical device. The method also includes obtaining a pre-built interface template, which includes a second mapping relationship between multiple interface components and point identifiers. Based on each point identifier, the first mapping relationship and the second mapping relationship are matched to determine the physical addresses that each interface component in the interface template needs to be mapped to. Based on the determined physical addresses and each interface component, the interface template is instantiated to obtain the configuration interface. In this embodiment, the control device automatically scans physical devices and reports the first mapping relationship between point identifiers and physical addresses. Combined with a pre-built interface template that only includes the second mapping between interface components and point identifiers and does not include physical addresses, the point identifiers are used as a common link to automatically complete the mapping matching and instantiation of the configuration interface. This achieves automated configuration of the configuration interface, thereby simplifying the traditional two-sided manual binding process into a one-time automatic association, reducing the configuration workload, and avoiding variable name mismatches or address input errors caused by manual point-by-point configuration, thus improving the configuration accuracy of the configuration interface. Attached Figure Description

[0009] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

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

[0011] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0012] Figure 1 A flowchart illustrating a configuration method for a configuration interface provided in an embodiment of this application; Figure 2 A flowchart illustrating another configuration method for a configuration interface provided in this application embodiment; Figure 3A schematic diagram of the structure of a configuration system with a configuration interface provided in an embodiment of this application; Figure 4 A flowchart illustrating another configuration method for a configuration interface provided in this application embodiment; Figure 5 A flowchart illustrating another configuration method for a configuration interface provided in an embodiment of this application; Figure 6 A schematic diagram of the structure of a configuration device for a configuration interface provided in an embodiment of this application; Figure 7 A schematic diagram of the structure of a configuration system for another configuration interface provided in this application embodiment; Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0013] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0014] The following disclosure provides numerous different embodiments or examples for implementing various structures of the invention. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of the invention. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0015] refer to Figure 1 , Figure 1 This is a flowchart illustrating a configuration method for a configuration interface provided in an embodiment of this application. The configuration method for a configuration interface provided in this application includes the following steps: S101: Receive the first mapping relationship reported by the control device.

[0016] In this embodiment, the method is applied to a configuration device, which can be a host computer. The first mapping relationship is generated by the control device scanning the physical devices it connects to. This first mapping relationship includes the relationship between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point. The control device is deployed in the building site and is a hardware device, such as a gateway or field controller, that directly connects to or connects to the physical devices via a network. The control device runs a standardized application program internally, possessing the ability to automatically scan the physical devices it connects to, collect point information, and proactively generate device-reported data.

[0017] The physical devices mentioned above can be actual equipment on-site in the building, such as sensors, valves, air conditioning units, and fans. Each device contains one or more data points that can be monitored or controlled. A device point can be understood as a specific operable or monitorable data point on a physical device. For example, an air conditioning unit may contain multiple points such as return air temperature, supply air temperature, and fan operating status. A point identifier is a globally unique identifier assigned to each device point, serving as its logical identity. For example, the return air temperature point of an air conditioning unit can be described as "AHU_01_ReturnAirTemp". The point identifier is independent of the physical address and only describes the abstract identity of the point. The physical address is the actual address information of the device point in the communication protocol, such as the register address in the Modbus protocol or the object attribute address in the BACnet protocol, and is the basis for data communication with the physical device.

[0018] Specifically, the control device has a built-in protocol component library, which stores protocol component packages corresponding to different communication protocols and device types in a standardized format. Each protocol component package also encapsulates a protocol parsing module, a point mapping rule table, and a unique identifier for the corresponding front-end interface template. When a field physical device connects to the control device, the standardized application within the control device first identifies the device's communication protocol type and device category. It then selects and loads the appropriate protocol component package from the protocol component library by matching protocol feature codes. Subsequently, based on the point mapping rule table within the protocol component package, it assigns a globally unique point identifier to each physical device point, synchronously associating it with the corresponding physical address to establish a one-to-one mapping relationship between point identifiers and physical addresses. Finally, the control device proactively pushes this first mapping relationship, along with the unique identifier of the corresponding front-end interface template, to the host computer.

[0019] For example, after a smart light using the Modbus protocol is connected to the control device, the standardized application loads the corresponding smart light protocol component package. This component package has a built-in Modbus register parsing module and a lamp point mapping rule table, and declares the corresponding template identifier as "TPL_Light_Modbus". According to the mapping rules, the application assigns the identifier "Light_01_Switch" and the corresponding coil address 0x0001 to the switch control point, and assigns the identifier "Light_01_Brightness" and the corresponding holding register address 0x0002 to the brightness adjustment point, forming a complete first mapping relationship, which is reported to the host computer along with the template identifier.

[0020] S102: Obtain a pre-built interface template.

[0021] In this embodiment, the interface template includes a second mapping relationship between multiple interface components and point identifiers, and the interface template does not include individual physical addresses. The interface template is a static blueprint of the configuration interface pre-built and stored in the template library of the configuration device. It is composed of multiple graphical interface components, and each interface template corresponds to a unique identifier. Interface components can be understood as the smallest graphical interaction unit in the configuration interface, such as a temperature display dashboard, valve switch buttons, fan status indicator icons, and light brightness adjustment sliders, to present the data of the device points in an intuitive and visual way.

[0022] Specifically, the configuration device has a local pre-stored library of front-end interface templates for various device types. Each front-end interface template corresponds to a unique identifier, and the template only records the second mapping relationship between interface components and location identifiers, without recording any physical addresses. Based on the unique identifier of the front-end interface template reported by the control device, the corresponding template is retrieved from the library, and the second mapping relationship within the template is parsed. Because the interface template and protocol component packet correspond one-to-one through a unified identifier, the location identifiers within the interface template are completely consistent with the location identifiers generated by the control device. The same interface template can be adapted to all control devices that have loaded the same device identifier.

[0023] It should be noted that when obtaining the preset interface template, it can also be obtained in the following way: the control device reports the target project attribute information corresponding to the target project to which the configuration interface to be configured belongs; the target project attribute information is matched with the historical project attribute information corresponding to multiple historical projects to obtain the target historical project corresponding to the target project from multiple historical projects; the historical interface template corresponding to the target historical project is obtained, and the historical interface template is determined as the preset interface template. The target project attribute information and historical project attribute information may include building type, building area, number of floors, etc. Historical projects are previously created projects, and historical interface templates are interface templates created when creating historical projects. By matching the project attribute information of the current project with the project attribute information of historical projects, and reusing the interface template corresponding to the same historical project as the preset interface template, the need to build the interface template from scratch every time a new project is created is avoided, realizing the automatic reuse of engineering experience and shortening the design cycle of the configuration interface.

[0024] S103: Based on the location identifiers, match the first mapping relationship and the second mapping relationship to determine the physical addresses that each interface component in the interface template needs to be mapped to.

[0025] In this embodiment, using the point identifier as a common matching key, all point identifiers in the second mapping relationship of the interface template are traversed, and the corresponding entries are searched one by one in the first mapping relationship to determine the physical addresses that each interface component in the interface template needs to be mapped.

[0026] S104: Based on the determined physical addresses and interface components, instantiate the interface template to obtain the configuration interface.

[0027] In this embodiment, after mapping and matching are completed, a corresponding data communication link is established for each device point based on the mapped physical addresses. According to parameters such as data type, byte order, and read / write permissions corresponding to the device point, the operating data of the physical device can be read in real time through the bound physical address and synchronously updated to the associated interface components. Simultaneously, a command issuance channel is opened for writable points with control attributes, supporting maintenance personnel to issue control commands through the interface components. Finally, the static interface template is dynamically converted into a runnable configuration interface with real-time data display and remote control interaction capabilities, completing the entire configuration process of the configuration interface.

[0028] This embodiment provides a configuration method for a configuration interface. By controlling the device to automatically scan physical devices and report the first mapping relationship between point identifiers and physical addresses, and combining it with a pre-constructed interface template that only includes a second mapping between interface components and point identifiers but not physical addresses, the mapping matching and instantiation of the configuration interface are automatically completed using point identifiers as a common link. This achieves automated configuration of the configuration interface, thereby simplifying the traditional two-sided manual binding process into a one-time automatic association, reducing the configuration workload, and avoiding variable name mismatches or address input errors caused by manual point-by-point configuration, thus improving the configuration accuracy of the configuration interface.

[0029] refer to Figure 2 , Figure 2 This is a flowchart illustrating another configuration method for a configuration interface provided in this application embodiment. The configuration method for a configuration interface provided in this application embodiment includes the following steps: S201: Receive the first mapping relationship reported by the control device.

[0030] In this embodiment, step S201 is the same as step S101 described above. For details, please refer to step S101 described above. This embodiment will not repeat the details here.

[0031] S202: Obtain a pre-built interface template.

[0032] In this embodiment, the interface template in step S202 is generated in the following way: Obtain a pre-built point model; In response to the creation of interface components in the template editor and the selection of point markers in the point model, the created interface components are mapped to the selected point markers. In response to the completion confirmation operation for the template editor, the mapping relationship between each created interface component and each selected point identifier is determined as the second mapping relationship, and an interface template is generated based on each created interface component and the second mapping relationship.

[0033] The point model includes multiple point identifiers but does not include any physical addresses. It is a set of standardized logical point identifiers categorized by device type. Based on a unified logical identifier system, it defines standard logical points for various physical devices. Each logical point corresponds to a unique point identifier, and its identifier system is completely consistent with the specifications followed by the point identifiers generated by the control device side, ensuring accurate matching of subsequent two-way mapping relationships through the point identifiers.

[0034] The template editor is a visual configuration development tool module deployed on configuration devices, providing functions such as graphical component library, layout editing, attribute configuration, and point binding.

[0035] Specifically, after the template editor starts, it first retrieves the pre-built point model and loads all predefined point identifiers as a unified benchmark for binding interface components.

[0036] In the template editor, engineers first create interface components by selecting the corresponding type from the preset component library and dragging and dropping them to the target location on the editing canvas to complete the interface layout. Examples include dragging in components such as a temperature gauge, status indicators, and control buttons. Next, they select corresponding point markers from the point model and bind them to the interface components on the canvas, establishing a mapping between a single interface component and a single point marker. This process is repeated to complete the point marker binding configuration for all interface components on the canvas.

[0037] After the engineer completes the binding configuration of all interface components and location markers, a confirmation operation is triggered. Upon receiving the confirmation command, the template editor automatically summarizes the binding relationships of all interface components and location markers in the editing canvas and determines this binding relationship as the second mapping relationship. Finally, all created interface components and second mapping relationships are integrated to generate a complete interface template. The generated interface template only records the interface component configuration and the second mapping relationship, and does not include any physical addresses.

[0038] In this embodiment, by selecting point identifiers from a pre-built point model and binding them to interface components, an interface template that only records the second mapping relationship and does not include the physical address is generated. This achieves complete decoupling between the interface template and the physical device, avoids configuration errors caused by manually inputting point identifiers, and ensures that the point identifiers bound in the interface template are completely consistent with the point identifiers generated by the control device. This lays the foundation for subsequent automatic matching of point identifiers and reuse of interface templates.

[0039] S203: Based on the identifiers of each point, match the first mapping relationship and the second mapping relationship to determine the physical address that each interface component in the interface template needs to be mapped.

[0040] In this embodiment, step S203 specifically includes: For each point identifier in the second mapping relationship, the first mapping relationship is matched using the point identifier to obtain the matching result corresponding to the point identifier; The identifiers of each first target point that are successfully matched are determined from the second mapping relationship; For each first target point identifier, the physical address matched by the first target point identifier is determined as the physical address that the interface component corresponding to the point identifier in the interface template needs to be mapped.

[0041] In this process, the automatic instantiation engine in the configuration device sequentially traverses all the point identifiers of the bound interface components in the second mapping relationship, uses a single point identifier as a search keyword, and performs a full-entry search in the first mapping relationship. If there is an entry corresponding to the point identifier in the first mapping relationship, the matching result of the point identifier is marked as a successful match; if there is no point identifier in the first mapping relationship, the matching result is marked as a failed match. After the traversal is completed, the matching result corresponding to each point identifier is recorded.

[0042] The automatic instantiation engine in the configuration device traverses all point identifiers and corresponding matching results in the second mapping relationship, performs filtering, removes all point identifiers that failed to match, and only retains the first target point identifiers that have a successful matching result.

[0043] For each selected first target point identifier, the physical address corresponding to that identifier in the first mapping relationship is retrieved. This physical address is then assigned to the interface component bound to the corresponding identifier within the interface template, completing the one-to-one binding between the interface component and the physical address. After all first target point identifiers have been processed, all valid interface components within the interface template are assigned to communicable physical addresses, providing a complete addressing basis for subsequent interface template instantiation.

[0044] In this embodiment, by traversing the point identifiers in the second mapping relationship point by point and searching for matches in the first mapping relationship, the physical address corresponding to the successfully matched point identifier is determined as the physical address to be mapped by the corresponding interface component. This achieves an automated and accurate association between the interface component and the physical address, avoiding omissions and mismatches caused by manually checking the correspondence between variable names and physical addresses one by one.

[0045] In one implementation, after obtaining each matching result, for points where the matching result is a failure, the automatic instantiation engine marks the corresponding interface component with a message indicating that the corresponding point was not found. This process is executed completely automatically without the need for deployment personnel intervention.

[0046] In another embodiment, after obtaining the various matching results, the configuration method for a configuration interface provided in this embodiment further includes: The semantic tags corresponding to each point identifier in the first mapping relationship are parsed to obtain the first tag set corresponding to each point identifier; The identifiers of each second target point that failed to match are determined from the second mapping relationship; For each second target point identifier, perform the following operation: parse the semantic tags of the second target point identifier to obtain the second tag set corresponding to the second target point identifier; Based on the second tag set corresponding to the second target point identifier and each first tag set, determine the semantic similarity between the second target point identifier and each point identifier in the first mapping relationship; Based on the semantic similarity of each corresponding second target point identifier, determine the target processing strategy of the interface component corresponding to the second target point identifier. Based on the target processing strategy, the interface components corresponding to the second target point identifier are processed.

[0047] Semantic tags can be understood as structured information fragments with actual business meaning included in the location identifier. Location identifiers are not meaningless strings, but rather composed of multiple semantic dimensions according to preset naming rules. For example, the location identifier "AHU_01_ReturnAirTemp" can be parsed into three semantic tags: equipment type "AHU" (air handling unit), equipment number "01" (unit 1), and measurement function "ReturnAirTemp" (return air temperature).

[0048] The second tag set can be understood as the set of semantic tags obtained after semantic tag parsing of a certain second target point identifier. The second tag set carries the feature information of the second target point identifier that failed to match in terms of semantic dimensions such as device type, device number, and measurement point function.

[0049] Specifically, after obtaining each matching result, the automatic instantiation engine in the configuration device performs semantic tag parsing on all point identifiers in the first mapping relationship one by one. The parsing process is carried out according to the preset naming rules, decomposing each point identifier into tags in multiple semantic dimensions. After all point identifiers are parsed, the first tag set corresponding to each point identifier is obtained.

[0050] The automatic instantiation engine filters out point identifiers from the second mapping relationship that fail to match, and identifies them as the second target point identifiers. For example, if a temperature dashboard component with the point identifier "AHU_01_ReturnAirTemp" bound in the interface template does not find a corresponding record in the first mapping relationship, then this point identifier is marked as the second target point identifier.

[0051] For each second target point identifier, the automatic instantiation engine also parses its semantic tags according to preset naming rules to obtain the second tag set corresponding to that second target point identifier. For example, parsing "AHU_01_ReturnAirTemp" yields the device type tag "AHU", the device number tag "01", and the measurement point function tag "ReturnAirTemp". The second tag set carries the feature information of the second target point identifier that failed to match in terms of business meaning and serves as the input basis for semantic similarity calculation.

[0052] The automatic instantiation engine compares the second tag set corresponding to the second target point identifier with each of the first tag sets one by one to calculate semantic similarity. During the calculation, each semantic dimension can be compared separately and the scores added together. For example, a perfect match of the device type tag yields a corresponding preset high score, a perfect match of the measurement point function tag yields a corresponding preset high score, and the device number tag is scored based on similarity (a perfect match yields a corresponding preset high score (i.e., full score), while inconsistencies are scored based on the relationship between the number distance and the score). The scores of each semantic dimension are then added together to obtain the semantic similarity between the second target point identifier and the point identifiers in the first mapping relationship.

[0053] The automatic instantiation engine determines the target processing strategy for the interface component corresponding to the second target point identifier based on the calculated semantic similarity. The automatic instantiation engine executes the operations indicated by the target processing strategy to process the interface component corresponding to the second target point identifier accordingly.

[0054] In this embodiment, when a match fails, the semantic label of the second target point identifier that failed to match is parsed, the semantic similarity between it and each point identifier in the first mapping relationship is calculated, and the differentiated target processing strategy of the interface component is determined based on the semantic similarity, thereby improving the intelligence and fault tolerance of the configuration interface.

[0055] In this embodiment, the above-mentioned target processing strategy for determining the interface component corresponding to the second target point identifier based on the semantic similarity of each corresponding to the second target point identifier includes: When there is a target semantic similarity among the semantic similarities corresponding to the second target point identifier, the target processing strategy of the interface component corresponding to the second target point identifier is determined as the first processing strategy. When there is no target semantic similarity among the semantic similarities corresponding to the second target point identifier, the target processing strategy of the interface component corresponding to the second target point identifier is determined as the second processing strategy.

[0056] The first processing strategy is used to instruct the interface components corresponding to the second target point identifier to be processed using a first preset format, where the target semantic similarity is greater than a preset similarity threshold; the second processing strategy is used to instruct the interface components corresponding to the second target point identifier to be processed using a second preset format, where the second preset format is different from the first preset format.

[0057] The preset similarity threshold is set in advance. When the target semantic similarity is greater than the preset similarity threshold, it means that the two location identifiers are highly similar in business meaning. When the target semantic similarity is less than or equal to the preset similarity threshold, it means that the two location identifiers differ significantly in business meaning.

[0058] The first preset format can be understood as the interface component display format corresponding to the first processing strategy, used to prompt the user that there are semantically similar alternative physical addresses for the interface component, requiring the user to confirm or correct. The second preset format can be understood as the interface component display format corresponding to the second processing strategy, used to prompt the user that the corresponding point for the interface component is missing, and no semantically similar alternative physical addresses were found. The second preset format and the first preset format are significantly different in visual presentation and interaction, so that users can intuitively distinguish between the two different matching failure scenarios.

[0059] Specifically, the automatic instantiation engine compares each calculated semantic similarity with a preset similarity threshold. If a semantic similarity is greater than the preset similarity threshold, that semantic similarity is marked as the target semantic similarity; if all semantic similarities are less than or equal to the preset similarity threshold, it is determined that no target semantic similarity exists.

[0060] When target semantic similarity exists, it indicates that there is a point identifier in the first mapping relationship that is semantically highly similar to the second target point identifier. At this time, the target processing strategy of the interface component corresponding to the second target point identifier is determined as the first processing strategy. The physical address corresponding to the point identifier with target semantic similarity is used as a candidate mapping address, associated with the interface component, and displayed on the interface component in a first preset format.

[0061] When no target semantic similarity exists, it indicates that there is no point identifier in the first mapping relationship that is semantically similar to the second target point identifier. In this case, the target processing strategy for the interface component corresponding to the second target point identifier is determined as the second processing strategy. The interface component corresponding to the second target point identifier is processed using the second preset format. Since there is a significant difference between the first and second preset formats, maintenance personnel can intuitively distinguish between the two different situations and thus take corresponding processing measures.

[0062] In this embodiment, by setting a preset similarity threshold, the failure of point identifier matching is divided into two different situations, and different processing strategies are adopted for differentiated processing. This realizes intelligent processing in the matching failure scenario and improves the intelligence level of configuration interface configuration.

[0063] S204: Based on the determined physical addresses and interface components, instantiate the interface template to obtain the configuration interface.

[0064] In this embodiment, step S204 is the same as step S104 of Shanshan, and can be referred to the above-described step S104. This embodiment will not repeat the details here.

[0065] S205: Receive the updated first mapping relationship reported by the control device.

[0066] S206: Based on the updated first mapping relationship, perform the matching step of the mapping relationship and the second mapping relationship to obtain the configuration interface again.

[0067] Regarding steps S205 and S206 above, the updated first mapping relationship is obtained by updating the first mapping relationship based on the location change event when the control device detects a location change event of the physical device it is connected to. A location change event can be understood as a triggering event that causes a change in the location configuration of physical devices on-site in the building. Specifically, this includes scenarios such as adding new physical devices, removing faulty physical devices, replacing device models leading to increases or decreases in locations, offsetting physical addresses of locations, and modifying data types or read / write attributes of locations. These are the starting conditions for triggering the mapping relationship update and the adaptive adjustment of the configuration interface.

[0068] Specifically, during the operation of the control equipment, the standardized application within the equipment continuously monitors the connection status and location configuration of the connected physical devices. When a location change event is detected, the mapping update process is automatically initiated. If a new physical device is added, the application first identifies the communication protocol type and device category of the physical device, matches and loads the corresponding protocol component package from the built-in protocol component library, and then assigns a globally unique location identifier to each location of the new physical device and associates it with the corresponding physical address according to the location mapping rule table within the component package. If a physical device is removed, the address is offset, or the location attribute is changed, the corresponding entry in the location description database is directly deleted or modified to complete the local database update. After completing the local database update, the control equipment generates a complete updated first mapping relationship, encapsulates it into a standard protocol data packet, and actively reports it to the host computer. After receiving the data packet, the host computer performs protocol parsing and overwrites the original first mapping relationship cached locally with the updated first mapping relationship.

[0069] After obtaining the updated first mapping relationship, the matching step between the first and second mapping relationships (i.e., step S203) is returned to the hardware baseline to re-obtain the configuration interface. Specifically, for newly added point markers, interface components of the matching type are generated at the corresponding positions according to preset layout rules, and physical address binding is automatically completed. For point markers that have disappeared, the corresponding interface components are set to a grayed-out unavailable state with an offline prompt. For points where only the physical address has changed, the physical address bound to the interface component is directly updated, maintaining the layout, style, and interaction logic of the interface component. In this way, a configuration interface adapted to the latest hardware state is generated, completing the dynamic update of the configuration interface without manual intervention.

[0070] In this embodiment, by controlling the device to monitor point change events in real time and automatically report the updated first mapping relationship, the point identifier matching and configuration interface instantiation process is automatically re-executed. This enables the configuration interface to adaptively adjust to the dynamic changes of on-site physical equipment, avoiding the need for manual modification of point variables and interface binding when physical equipment changes. This reduces maintenance costs and improves the response efficiency to changes in on-site physical equipment.

[0071] S207: Upon receiving a self-test trigger command, for each point identifier in the first mapping relationship, based on the preset verification rule set, send a read command corresponding to each preset verification rule in the preset verification rule set to the control device.

[0072] S208: Receive the instruction response information from the control device for each read instruction.

[0073] S209: Based on the response information of each instruction and the point attribute information corresponding to the physical address, verify the device point corresponding to the physical address to obtain the verification result corresponding to the physical address.

[0074] S210: Based on the result type corresponding to each verification result, display the result in the corresponding interface component in the configuration interface in the preset format corresponding to the result type.

[0075] Regarding steps S207 to S210 above, the first mapping relationship also includes the point attribute information corresponding to each point identifier. The point attribute information specifically includes the data type, byte order, data length, read / write permissions, normal value range, alarm threshold, etc. of the device point, which is the judgment benchmark for device point verification.

[0076] The preset verification rule set is a pre-configured set of multi-dimensional point verification rules, covering three verification dimensions: communication layer, data layer, and business layer, to ensure the full-dimensional compliance of point communication links, data formats, and operating values.

[0077] The read command carries the physical address corresponding to the point identifier. The command response information is generated by the control device after accessing the device point corresponding to the physical address in the read command. In other words, the command response information is the response data collected and returned by the control device from the corresponding physical address after receiving the read command, including communication status, original data frame, parsed values, etc.

[0078] Specifically, after executing step S204 or step S206, the automatic instantiation engine in the configuration device receives the self-test command triggered by the user, reads the locally cached first mapping relationship, extracts the physical address corresponding to all point identifiers, and the point attribute information attached to each point identifier.

[0079] The system invokes a preset verification rule set, which includes three progressive preset verification rules. Each preset verification rule corresponds to specific read instruction parameters: the communication connectivity verification rule corresponds to a standard read instruction with a timeout threshold set, used to detect whether the communication link of the device location is unobstructed; the data type matching verification rule corresponds to a raw register read instruction with a specified data length, used to obtain the raw data frame of the location; and the numerical range compliance verification rule corresponds to a business numerical parsing read instruction, used to obtain the actual operating values ​​after parsing of the location. The automatic instantiation engine processes each physical address sequentially, issuing read instructions corresponding to the three types of pre-verification rules one by one, completing a full-dimensional detection of the device location corresponding to the physical address.

[0080] After receiving the read command, the control device accesses the hardware unit corresponding to the physical address, collects the current point data, and encapsulates it into a standard response frame, returning it to the automatic instantiation engine in the configuration device. The automatic instantiation engine receives all the response data corresponding to each physical address, and organizes the communication status, original data format, parsed values, and other information into the command response information corresponding to that device point, which serves as the input basis for subsequent verification and judgment.

[0081] The automatic instantiation engine uses the point attribute information carried by the first mapping relationship as a benchmark. Based on a preset verification rule set, it compares the instruction response information with the point attribute information to determine the following: If the read instruction times out without response, it is directly determined to be a communication failure; if the communication is normal but the length, byte order, and format of the returned raw data do not match the data type declared in the point attribute information, it is determined to be a data type mismatch; if the communication is normal and the data type matches, but the parsed running value exceeds the preset normal value range in the point attribute information, it is determined to be a value exceeding the limit; if all three verifications pass, the device point is determined to be normal. A complete verification result is generated for each device point.

[0082] The automatic instantiation engine pre-configures differentiated visualization formats for different result types. For example, normal device locations are marked with green status indicators, maintaining a standard display style; device locations with communication failures are rendered in gray disabled state with a communication interruption message; device locations with data type mismatches are marked with an orange highlighted border, indicating a configuration mismatch; and device locations with values ​​exceeding limits are marked in bright red, indicating that the value has exceeded the limit. Simultaneously, the system automatically summarizes information from all abnormal device locations to generate a self-inspection report, including the logical name of the location, physical address, fault type, expected parameters, actual values, and troubleshooting suggestions, supporting maintenance personnel in quickly locating and resolving issues.

[0083] In this embodiment, by attaching point attribute information in the first mapping relationship as a verification benchmark, after receiving the self-test trigger command, the system automatically completes the multi-dimensional verification of the points by sending reading commands to the control device in sequence according to the preset verification rule set. The system also displays the verification results of different types on the interface components of the configuration interface, eliminating the need for manual verification. This achieves one-click automatic self-testing of the device points and ensures the accuracy and reliability of the configuration interface operation.

[0084] This embodiment provides a configuration method for a configuration interface. By controlling the device to automatically scan physical devices and report the first mapping relationship between point identifiers and physical addresses, and combining it with a pre-constructed interface template that only includes a second mapping between interface components and point identifiers but not physical addresses, the mapping matching and instantiation of the configuration interface are automatically completed using point identifiers as a common link. This achieves automated configuration of the configuration interface, thereby simplifying the traditional two-sided manual binding process into a one-time automatic association, reducing the configuration workload, and avoiding variable name mismatches or address input errors caused by manual point-by-point configuration, thus improving the configuration accuracy of the configuration interface.

[0085] To facilitate understanding of the technical solution of this application, the configuration method of the configuration interface provided in this application is described in detail as follows: like Figure 3 As shown, the configuration system of this configuration interface adopts a layered architecture design, consisting of control equipment deployed at the engineering site and a host computer.

[0086] The control equipment deployed on-site serves as the hub connecting the underlying physical devices and the host computer. The control equipment runs a standardized application program and has a built-in protocol component library and point description storage unit. It can automatically scan connected physical devices, generate point mapping data, and report it to the host computer. The protocol component library stores protocol component packages adapted to different communication protocols and device types in a standardized format. Each protocol component package encapsulates a protocol parsing module, a point mapping rule table, and a corresponding interface template identifier, supporting rapid access for physical devices from different manufacturers and using different protocols.

[0087] The host computer includes a template editor, a model manager, and an automatic instantiation engine. The template editor provides a graphical component library and layout editing capabilities for building interface templates; the model manager is responsible for maintaining a standardized point identification system to ensure consistent identification rules across the entire link; and the automatic instantiation engine is responsible for completing bilateral mapping matching, automatic generation of configuration interfaces, automatic verification of the full-link status of equipment points, and visualization of results.

[0088] The physical devices involved in this example are terminal electromechanical devices such as air conditioning units, temperature and humidity sensors, and smart lighting in the building. Each device contains multiple readable and writable device points. Each device point corresponds to a unique physical address and a unique point identifier. The point identifier is a globally unique logical label that is independent of the physical address.

[0089] like Figure 4 As shown, during the design phase of the configuration interface, a standardized point model is first pre-built using the model manager. This point model contains multiple predefined point identifiers but does not include any physical addresses. The point model is categorized by device type, defining the correspondence between standard logical points and their corresponding identifiers for each type of device. For example, the air conditioning unit point model defines points such as return air temperature, supply air temperature, fan operating status, and fan start / stop control, along with their corresponding identifiers; the intelligent lighting point model defines points such as switch control, brightness adjustment, and color temperature adjustment, along with their corresponding identifiers. The point model only contains the correspondence between logical points and their identifiers, without involving any physical address information, and the identifier rules are completely consistent with the point identifier generation rules on the control device side.

[0090] Engineers use drag-and-drop operations in the template editor to select interface components such as temperature gauges, status indicators, switches, and brightness sliders from the component library, arranging them to the target positions on the editing canvas to complete the interface layout. Then, through point selection, corresponding point markers are selected from the point model, establishing a binding relationship with the interface components on the canvas. Once all configurations are complete, a confirmation operation is triggered, confirming the binding relationships between all interface components and point markers as a second mapping relationship, and generating the interface template along with the interface components.

[0091] During the deployment phase of the configuration interface, after the field physical devices are connected to the control equipment, the standardized application within the control equipment first identifies the communication protocol type and device category of the connected devices. It then matches the device characteristics with the protocol signatures of each component package in the protocol component library, automatically selecting and loading the protocol component package with the highest matching degree. After loading, the standardized application assigns a globally unique point identifier to each device point of the physical device according to the point mapping rule table within the component package. It synchronously associates the corresponding physical address with point attribute information, including data type, byte order, read / write permissions, and normal value range, establishing a one-to-one mapping relationship between the point identifier and the physical address and point attribute information. Once the first mapping relationship is generated, the control equipment encapsulates it along with the corresponding template identifier into a standard data packet and actively reports it to the host computer.

[0092] After receiving the first mapping relationship, the automatic instantiation engine in the host computer first retrieves the corresponding interface template from the pre-stored template library based on the template identifier reported by the control device, and parses it to obtain the second mapping relationship included in the interface template. Then, using the point identifier as the common matching key, it traverses all point identifiers in the second mapping relationship and sequentially retrieves the corresponding entries in the first mapping relationship.

[0093] If a corresponding entry is found, it is marked as the first target location identifier of a successful match, and the physical address corresponding to the location identifier in the first mapping relationship is assigned to the corresponding interface component; if no corresponding entry is found, it is marked as the second target location identifier of a failed match, and the semantic tags of the two location identifiers are further parsed, the semantic similarity is calculated, and the interface component is processed differently based on the similarity result.

[0094] After all matching is completed, the automatic instantiation engine establishes a data communication link for each bound interface component, periodically reads the real-time data of the corresponding physical address according to the parameters of the point attribute information and synchronizes it to the interface component, and finally converts the static interface template into a configuration interface that can display data in real time and support remote interaction.

[0095] like Figure 5 As shown, after the configuration interface is generated, the automatic instantiation engine reads the first mapping relationship from the local cache, traverses the physical addresses corresponding to all point identifiers, and sequentially issues corresponding read commands according to the preset verification rule set. After receiving the read command, the control device accesses the corresponding physical address to collect data and returns command response information. Based on the command response information and point attribute information, the device point is verified to obtain the corresponding verification result.

[0096] Based on the different verification result types, the results are visually displayed in a preset format on the corresponding interface components of the configuration interface. For example, normal points are marked with a green status indicator, communication fault points are grayed out with an interruption message, data mismatch points are highlighted with an orange border, and points with values ​​exceeding limits are marked with a prominent red label. Simultaneously, a self-inspection report is automatically generated, listing the point identifier, physical address, fault type, and troubleshooting suggestions for abnormal points, supporting debugging personnel in quickly locating problems.

[0097] During the operation of the control equipment, when site changes such as the addition of new equipment, removal of equipment, or replacement of models occur on site, the standardized application in the control equipment will detect the hardware topology changes in real time, automatically rescan the equipment sites, update the local site description data, generate the updated first mapping relationship, and actively report it to the host computer.

[0098] After receiving the updated first mapping relationship, the host computer does not need to modify the original interface template. It directly uses the updated first mapping relationship as the basis to re-execute the mapping matching and interface instantiation process. For newly added device points, the corresponding interface components are automatically generated according to the preset layout rules and data binding is completed. For missing device points, the corresponding interface components are set to a grayed-out unavailable state and marked with an offline prompt. For device points where only the physical address has changed, the physical address of the interface components is directly updated, while the layout and interaction logic of the interface components remain unchanged. Finally, a configuration interface adapted to the current hardware status is automatically generated. No manual modification of the template configuration is required throughout the process, achieving adaptive adaptation to dynamic changes in field equipment.

[0099] refer to Figure 6 , Figure 6 A configuration system for a configuration interface is provided in this application embodiment. The configuration system includes a control device and a configuration device.

[0100] The control device is used to scan the physical devices it is connected to and generate a first mapping relationship. The first mapping relationship represents the relationship between the point identifier corresponding to each device point of the physical device and the physical address corresponding to each device point of the physical device.

[0101] The configuration device is used to execute the configuration method of the configuration interface as described above.

[0102] This embodiment provides a configuration system for a configuration interface. By controlling the device to automatically scan physical devices and report the first mapping relationship between point identifiers and physical addresses, and combining it with a pre-constructed interface template that only includes a second mapping between interface components and point identifiers but not physical addresses, the system automatically completes the mapping matching and instantiation of the configuration interface by using point identifiers as a common link. This achieves automated configuration of the configuration interface, thereby simplifying the traditional two-sided manual binding process into a one-time automatic association, reducing the configuration workload, and avoiding variable name mismatches or address input errors caused by manual point-by-point configuration, thus improving the configuration accuracy of the configuration interface.

[0103] refer to Figure 7 , Figure 7 This is a schematic diagram of a configuration device for a configuration interface provided in an embodiment of this application. The configuration device for a configuration interface provided in this application includes: a receiving module 10, an acquiring module 20, a matching module 30, and a configuration module 40. The receiving module 10 is used to receive a first mapping relationship reported by a control device. The first mapping relationship is generated by the control device scanning the physical devices it connects to. The first mapping relationship includes the correspondence between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point of the physical device. The acquiring module 20 is used to acquire a pre-built interface template. The interface template includes a second mapping relationship between multiple interface components and the point identifiers. The matching module 30 is used to match the first mapping relationship and the second mapping relationship based on each point identifier to determine the physical addresses that each interface component in the interface template needs to be mapped to. The configuration module 40 is used to instantiate the interface template based on the determined physical addresses and each interface component to obtain a configuration interface.

[0104] In this embodiment, the configuration module 40 is further configured to: After obtaining the configuration interface, the updated first mapping relationship reported by the control device is received. The updated first mapping relationship is obtained by the control device updating the first mapping relationship based on the point change event when it detects that the physical device connected to it has a point change event. Based on the updated first mapping relationship, a matching step between the first mapping relationship and the second mapping relationship is performed to re-obtain the configuration interface.

[0105] In this embodiment, the first mapping relationship further includes point attribute information corresponding to each of the point identifiers; the configuration module 40 is also used for: After obtaining the configuration interface, upon receiving the self-test trigger command, for each of the point identifiers in the first mapping relationship, based on the preset verification rule set, a read command corresponding to each preset verification rule in the preset verification rule set is sent to the control device, and the read command carries the physical address corresponding to the point identifier. The control device receives instruction response information corresponding to each of the read instructions. The instruction response information is generated by the control device after accessing the device point corresponding to the physical address in the read instruction. Based on each instruction response information and the point attribute information corresponding to the point identifier, the device point corresponding to the point identifier is verified to obtain the verification result corresponding to the device point. Based on the result type corresponding to each of the verification results, the results are displayed in a preset format corresponding to the result type on the corresponding interface component in the configuration interface.

[0106] In this embodiment, the matching module 30 is further configured to: For each point identifier in the second mapping relationship, the first mapping relationship is matched using the point identifier to obtain the matching result corresponding to the point identifier; The identifiers of each first target point that are successfully matched are determined from the second mapping relationship; For each of the first target point identifiers, the physical address matched by the first target point identifier is determined as the physical address that the interface component corresponding to the point identifier in the interface template needs to be mapped.

[0107] This embodiment provides a configuration method for a configuration interface, which further includes a processing module. The processing module is used for: After obtaining each of the matching results, the semantic tags corresponding to each of the point identifiers in the first mapping relationship are parsed to obtain the first tag set corresponding to each of the point identifiers; The identifiers of each second target point that failed to match are determined from the second mapping relationship; For each second target point identifier, the following operation is performed: the semantic tags of the second target point identifier are parsed to obtain the second tag set corresponding to the second target point identifier; Based on the second tag set corresponding to the second target point identifier and each of the first tag sets, determine the semantic similarity between the second target point identifier and each of the point identifiers in the first mapping relationship; Based on the semantic similarity of each of the second target point identifiers, the target processing strategy of the interface component corresponding to the second target point identifier is determined. Based on the target processing strategy, the interface component corresponding to the second target point identifier is processed.

[0108] In this embodiment, the processing module is further configured to: When there is a target semantic similarity among the semantic similarities corresponding to the second target point identifier, the target processing strategy of the interface component corresponding to the second target point identifier is determined to be the first processing strategy; When there is no target semantic similarity among the semantic similarities corresponding to the second target point identifier, the target processing strategy of the interface component corresponding to the second target point identifier is determined to be the second processing strategy. Wherein, the first processing strategy is used to instruct the interface component corresponding to the second target point identifier to be processed using a first preset format, and the target semantic similarity is greater than a preset similarity threshold; The second processing strategy is used to instruct the interface component corresponding to the second target point identifier to be processed using a second preset format, which is different from the first preset format.

[0109] In this embodiment, the interface template is generated in the following way: Obtain a pre-constructed point model, wherein the point model includes multiple point identifiers; In response to the creation operation of the interface component in the template editor and the selection operation of the point identifier in the point model, the created interface component is mapped to the selected point identifier; In response to the completion confirmation operation for the template editor, the mapping relationship between each created interface component and each selected point identifier is determined as a second mapping relationship, and the interface template is generated based on each created interface component and the second mapping relationship.

[0110] This embodiment provides a configuration device for a configuration interface. By controlling the device to automatically scan physical devices and report the first mapping relationship between point identifiers and physical addresses, and combining it with a pre-constructed interface template that only includes a second mapping between interface components and point identifiers but not physical addresses, the device automatically completes the mapping matching and instantiation of the configuration interface by using point identifiers as a common link. This achieves automated configuration of the configuration interface, thereby simplifying the traditional two-sided manual binding process into a one-time automatic association, reducing the configuration workload, and avoiding variable name mismatches or address input errors caused by manual point-by-point configuration, thus improving the configuration accuracy of the configuration interface.

[0111] like Figure 8 As shown in the figure, this application provides an electronic device, which is an energy-saving electronic device, including a processor 111, a communication interface 112, a memory 113, and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114. Memory 113 is used to store computer programs; In one embodiment of this application, the processor 111, when executing the program stored in the memory 113, implements the configuration method of the configuration interface provided in any of the foregoing method embodiments.

[0112] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the configuration method for the configuration interface as provided in any of the foregoing method embodiments.

[0113] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0114] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0115] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0116] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for configuring a configuration interface, characterized in that, include: The first mapping relationship reported by the receiving control device is generated by the control device scanning the physical devices it is connected to. The first mapping relationship includes the correspondence between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point of the physical device. Obtain a pre-built interface template, the interface template including a second mapping relationship between multiple interface components and the point identifier; Based on each of the point identifiers, the first mapping relationship and the second mapping relationship are matched to determine the physical address that each of the interface components in the interface template needs to be mapped. Based on the determined physical addresses and interface components, the interface template is instantiated to obtain the configuration interface.

2. The method according to claim 1, characterized in that, After obtaining the configuration interface, the method further includes: The control device receives the updated first mapping relationship reported by the control device. The updated first mapping relationship is obtained by the control device updating the first mapping relationship based on the location change event when it detects that a location change event has occurred in the physical device connected to it. Based on the updated first mapping relationship, a matching step between the first mapping relationship and the second mapping relationship is performed to re-obtain the configuration interface.

3. The method according to claim 1 or 2, characterized in that, The first mapping relationship also includes point attribute information corresponding to each of the point identifiers; after obtaining the configuration interface, the method further includes... Upon receiving a self-test trigger command, for each of the point identifiers in the first mapping relationship, a read command corresponding to each preset verification rule in the preset verification rule set is sent to the control device based on the preset verification rule set. The read command carries the physical address corresponding to the point identifier. The control device receives instruction response information corresponding to each of the read instructions. The instruction response information is generated by the control device after accessing the device point corresponding to the physical address in the read instruction. Based on each instruction response information and the point attribute information corresponding to the point identifier, the device point corresponding to the point identifier is verified to obtain the verification result corresponding to the device point. Based on the result type corresponding to each of the verification results, the results are displayed in a preset format corresponding to the result type on the corresponding interface component in the configuration interface.

4. The method according to claim 1, characterized in that, The step of matching the first mapping relationship and the second mapping relationship based on each of the point identifiers to determine the physical address to be mapped for each of the interface components in the interface template includes: For each point identifier in the second mapping relationship, the first mapping relationship is matched using the point identifier to obtain the matching result corresponding to the point identifier; The identifiers of each first target point that are successfully matched are determined from the second mapping relationship; For each of the first target point identifiers, the physical address matched by the first target point identifier is determined as the physical address that the interface component corresponding to the point identifier in the interface template needs to be mapped.

5. The method according to claim 4, characterized in that, After obtaining each of the matching results, the method further includes: The semantic tags corresponding to each point identifier in the first mapping relationship are parsed to obtain the first tag set corresponding to each point identifier; The identifiers of each second target point that failed to match are determined from the second mapping relationship; For each second target point identifier, the following operation is performed: the semantic tags of the second target point identifier are parsed to obtain the second tag set corresponding to the second target point identifier; Based on the second tag set corresponding to the second target point identifier and each of the first tag sets, determine the semantic similarity between the second target point identifier and each of the point identifiers in the first mapping relationship; Based on the semantic similarity of each of the second target point identifiers, the target processing strategy of the interface component corresponding to the second target point identifier is determined. Based on the target processing strategy, the interface component corresponding to the second target point identifier is processed.

6. The method according to claim 5, characterized in that, The step of determining the target processing strategy for the interface component corresponding to the second target point identifier based on the semantic similarity of each of the second target point identifiers includes: When there is a target semantic similarity among the semantic similarities corresponding to the second target point identifier, the target processing strategy of the interface component corresponding to the second target point identifier is determined to be the first processing strategy; When there is no target semantic similarity among the semantic similarities corresponding to the second target point identifier, the target processing strategy of the interface component corresponding to the second target point identifier is determined to be the second processing strategy. Wherein, the first processing strategy is used to instruct the interface component corresponding to the second target point identifier to be processed using a first preset format, and the target semantic similarity is greater than a preset similarity threshold; The second processing strategy is used to instruct the interface component corresponding to the second target point identifier to be processed using a second preset format, which is different from the first preset format.

7. The method according to claim 1, characterized in that, The interface template is generated in the following way: Obtain a pre-constructed point model, wherein the point model includes multiple point identifiers; In response to the creation operation of the interface component in the template editor and the selection operation of the point identifier in the point model, the created interface component is mapped to the selected point identifier; In response to the completion confirmation operation for the template editor, the mapping relationship between each created interface component and each selected point identifier is determined as a second mapping relationship, and the interface template is generated based on each created interface component and the second mapping relationship.

8. A configuration device for a configuration interface, characterized in that, include: The receiving module is used to receive a first mapping relationship reported by the control device. The first mapping relationship is generated by the control device scanning the physical devices it is connected to. The first mapping relationship includes the correspondence between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point of the physical device. The acquisition module is used to acquire a pre-built interface template, the interface template including a second mapping relationship between multiple interface components and the point identifier; The matching module is used to match the first mapping relationship and the second mapping relationship based on each of the point identifiers, so as to determine the physical address that each of the interface components in the interface template needs to be mapped; The configuration module is used to instantiate the interface template based on the determined physical addresses and interface components to obtain a configuration interface.

9. An electronic device, characterized in that, include: Processor and memory; The processor is used to execute the configuration program of the configuration interface stored in the memory to implement the configuration method of the configuration interface according to any one of claims 1 to 7.

10. A configuration system for a configuration interface, characterized in that, include: Control equipment and configuration equipment; The control device is used to scan the physical devices connected to it to generate a first mapping relationship. The first mapping relationship includes the correspondence between the point identifiers corresponding to each device point of the physical device and the physical addresses corresponding to each device point of the physical device. The configuration device is used to execute the configuration method of the configuration interface as described in any one of claims 1 to 7.

Images