Heat network system measuring point information synchronization method and device

Abstract

The application discloses a kind of heat network system measuring point information synchronization method and device, the method includes: obtaining the configuration file and data configuration file of each controller;Each functional block of each controller is traversed, and the functional block of reference measuring point information is determined;Based on the functional block of reference measuring point information, the actual measuring point information corresponding to the functional block is found in the measuring point library of controller;Reference measuring point information is compared with actual measuring point information;If the measuring point page number and / or measuring point description of reference measuring point information and actual measuring point information are inconsistent, then the reference measuring point information in the functional block is synchronized to actual measuring point information;After the reference measuring point information of all functional blocks in controller is synchronized, the data object structure of each controller after synchronization is written into disk.The application can synchronize the reference information in all controllers before configuration is downloaded, and improve the efficiency of configuration design, modification, migration and debugging.

Description

Technical Field

[0001] This application relates to the field of automation technology, and in particular to a method and apparatus for synchronizing measurement point information in a heating network system. Background Technology

[0002] In the configuration design and commissioning of large-scale distributed control systems (DCS) such as those for heating network units and thermal power units, data sharing among multiple controllers is often involved. In DCS, data sharing is typically achieved through cross-referencing of measurement points between controllers. Therefore, in the configuration, there are referrers and referenced parties. To ensure correct data sharing across controllers, the referrer needs to record the referenced party's measurement point name, logical page number, node number, branch number, slot number, channel number, and other index information, thereby enabling data sharing.

[0003] However, during configuration design and debugging, multiple debugging personnel often modify configuration data and logic, or perform operations such as exporting, importing, and replacing measurement point names. This causes changes to the logic page number, node number, branch number, slot number, or channel number of the referenced device. The referencing device is unaware that the referenced device has been modified and downloads this erroneous logic to the controller, leading to abnormal data referenced across controllers and incorrect control logic operations. This can cause malfunctions in local equipment, resulting in equipment damage and personal injury. Summary of the Invention

[0004] This disclosure provides a method and apparatus for synchronizing measurement point information in a heating network system, thereby at least solving the above-mentioned technical problems existing in the prior art.

[0005] According to a first aspect of this application, a method for synchronizing measuring point information in a heating network system is provided, comprising:

[0006] Obtain the configuration file and data configuration file of each controller; wherein, the configuration file is used to characterize the logical relationships in the controller, the logical relationships include the composition and connection relationship of tasks, logical pages under tasks, and functional blocks under logical pages; the data configuration file includes measurement point information; the measurement point information includes measurement point page number and measurement point description;

[0007] Based on the configuration configuration file and the data configuration file, a data object structure for each controller is constructed in memory;

[0008] Iterate through each function block of each controller to determine the function block that references the measurement point information;

[0009] Based on the function block that references the measurement point information, the actual measurement point information corresponding to the function block is searched in the measurement point library of the controller;

[0010] Compare the referenced measurement point information with the actual measurement point information;

[0011] If the referenced measurement point information is inconsistent with the measurement point page number and / or measurement point description of the actual measurement point information, the referenced measurement point information in the function block will be synchronized with the actual measurement point information.

[0012] After the reference measurement point information of all functional blocks in the controller is synchronized, the synchronized data object structure of each controller is written to the disk.

[0013] In one possible implementation, the step of traversing each function block of each controller to determine the function block referencing the measurement point information includes:

[0014] Number each controller;

[0015] Based on the configuration configuration file, the task configuration information in the controller is read sequentially according to the number, and each task is created in memory;

[0016] Based on the configuration configuration file, the operation order of the logical pages under the task is read, and the logical pages under each task are established in memory;

[0017] Traverse each function block under the logical page to determine the function block that references the measurement point information.

[0018] In one possible implementation, when traversing all function blocks in the controller, if the currently traversed function block does not reference measurement point information, the currently traversed function block is skipped, and the next function block is traversed.

[0019] In one possible implementation, based on the function block referencing the measurement point information, the actual measurement point information corresponding to the function block is searched in the controller's measurement point library, including:

[0020] Determine the type of the function block;

[0021] Based on the type of the function block, determine the reference measurement point information of the function block; and search for the actual measurement point information corresponding to the function block in the controller's measurement point library.

[0022] In one possible implementation, the type of the functional block includes: structure type, unstructure type, inter-station reference type, and redundant measurement point reference type; determining the reference measurement point information of the functional block based on its type includes:

[0023] In response to the fact that the function block is a structure type, the reference measurement point information and multiple sub-measurement point information of the function block are determined;

[0024] In response to the fact that the function block is a non-structure type, the reference measurement point information of the function block is determined;

[0025] In response to the fact that the function block is of the inter-station reference type, the reference measurement point information and controller number of the function block are determined;

[0026] In response to the function block being a redundant measurement point reference type, the reference measurement point information and redundant measurement point information of the function block are determined.

[0027] In one possible implementation, in response to the function block being a structure type, the method further includes:

[0028] If the currently traversed function block has reference test point information, determine whether the reference test point information contains sub-test point information;

[0029] In response to the fact that the referenced measurement point information contains sub-measurement point information, the actual measurement point information corresponding to the function block is searched in the measurement point library of the controller.

[0030] In one possible implementation, it further includes:

[0031] The data object structure of each synchronized controller is displayed on the graphical interface.

[0032] According to a second aspect of this application, a device for synchronizing measuring point information in a heating network system is provided, comprising:

[0033] The acquisition module is used to acquire the configuration configuration file and data configuration file of each controller; wherein, the configuration configuration file is used to characterize the logical relationships in the controller, and the logical relationships include the composition and connection relationship of tasks, logical pages under tasks, and functional blocks under logical pages; the data configuration file includes measurement point information; the measurement point information includes measurement point page number and measurement point description;

[0034] A construction module is used to construct the data object structure of each controller in memory based on the configuration configuration file and the data configuration file;

[0035] The determination module is used to traverse each function block of each controller and determine the function block that references the measurement point information.

[0036] The lookup module is used to search for the actual measurement point information corresponding to the function block in the controller's measurement point library based on the function block that references the measurement point information.

[0037] The comparison module is used to compare the referenced measurement point information with the actual measurement point information;

[0038] The synchronization module is used to synchronize the referenced measurement point information in the function block to the actual measurement point information if the referenced measurement point information is inconsistent with the measurement point page number and / or measurement point description of the actual measurement point information.

[0039] The writing module is used to write the synchronized data object structure of each controller to the disk after the reference measurement point information of all function blocks in the controller is synchronized.

[0040] According to a third aspect of this application, an electronic device is provided, comprising:

[0041] At least one processor;

[0042] and a memory communicatively connected to the at least one processor; wherein,

[0043] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method described in this application.

[0044] According to a fourth aspect of this application, a non-transitory computer-readable storage medium is provided storing computer instructions for causing the computer to perform the methods described in this application.

[0045] According to a fifth aspect of this application, a computer program product is provided, comprising a computer program or instructions that, when executed by a processor, implement the method described in this application.

[0046] This application's technical solution solves the problem of cross-controller index failure caused by changes in the referenced and referenced measurement point information during configuration design and debugging, following operations such as modifying, importing, exporting, and replacing measurement point names. This mismatch between the original measurement point reference information and the modified actual measurement point information leads to the failure of cross-controller indexes in the configuration. This application synchronizes the reference information in all controllers before the configuration is downloaded, replacing the cumbersome process of manual verification and replacement in existing technologies, significantly improving the efficiency of configuration design, modification, migration, and debugging.

[0047] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description

[0048] The above and other objects, features, and advantages of exemplary embodiments of this application will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings. Several embodiments of this application are illustrated in the drawings by way of example and not limitation, in which:

[0049] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

[0050] Figure 1This paper illustrates the steps of the method for synchronizing measuring point information in a heating network system according to an embodiment of this application.

[0051] Figure 2 A flowchart illustrating the method for synchronizing measuring point information in a heating network system according to an embodiment of this application is shown.

[0052] Figure 3 This paper shows a structural block diagram of the heating network system measuring point information synchronization device in an embodiment of this application;

[0053] Figure 4 A schematic diagram of the composition structure of an electronic device according to an embodiment of this application is shown. Detailed Implementation

[0054] To make the objectives, features, and advantages of this application more apparent and understandable, the technical solutions in 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, and 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.

[0055] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0056] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0057] In the following description, the terms "first" and "second" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first" and "second" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0058] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0059] It should be understood that in the various embodiments of this application, the sequence number of each implementation process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0060] The following description, in conjunction with the accompanying drawings, introduces a method and apparatus for synchronizing measuring point information in a heating network system provided in this application.

[0061] like Figure 1 As shown, this application provides a method for synchronizing measuring point information in a heating network system, including:

[0062] S101, Obtain the configuration file and data configuration file of each controller; wherein, the configuration file is used to characterize the logical relationships in the controller, the logical relationships include the composition and connection relationship of tasks, logical pages under tasks, and functional blocks under logical pages; the data configuration file includes measurement point information; the measurement point information includes measurement point page number and measurement point description.

[0063] The heating network system refers to the engineering facilities and management system used to achieve centralized heating. Its function is to efficiently transport heat energy from heat sources to heat users. These users can be residential buildings, commercial buildings, industrial plants, etc., meeting their needs for heating, domestic hot water, or industrial heat, and are an important component of urban energy supply and infrastructure.

[0064] Measuring points are sensing nodes in a heating network system used to collect key operational data. Examples include temperature sensors and pressure transmitters installed on pipelines, flow meters at heating stations, and heat meters at user terminals.

[0065] The configuration file refers to the configuration data used to describe the internal logical hierarchy of the controller. It can be implemented using a structured file format, such as an XML file, a JSON file, or a database table structure. The hierarchical relationship between tasks, logical pages, and functional blocks is expressed through node nesting or associated fields. The data configuration file is the carrier for storing measurement point information. It can be implemented using a CSV file, a relational database, or an in-memory data table. The measurement point page number is used to identify the logical page location, and the measurement point description includes index information such as the measurement point name, node number, and slot number.

[0066] S102, Based on the configuration configuration file and the data configuration file, construct the data object structure of each controller in memory.

[0067] In this application, constructing a data object structure in memory refers to mapping the logical relationships of the controller and measurement point information into an operable data model. This model can use a tree structure to represent the hierarchical relationship between tasks and logical pages, and a linked list structure to store function block instances. Measurement point information is associated with the corresponding function blocks in key-value pairs. For example, a task node contains multiple logical page nodes, and each logical page node holds several function block objects. These function block objects are associated with their corresponding measurement point information through pointers or references.

[0068] S103, traverse each function block of each controller to determine the function block that references the measurement point information.

[0069] The methods for determining the referenced measurement point information when traversing a function block include: judging whether it contains measurement point references by checking the attribute markers of the function block object, such as setting a boolean flag "hasReference"; or checking whether the parameter type is a measurement point reference type by traversing the input and output parameter list of the function block. For example, when the input parameter type of the function block is "PointReference", it is determined that the function block contains a measurement point reference.

[0070] S104, based on the function block referencing the measurement point information, search for the actual measurement point information corresponding to the function block in the controller's measurement point library.

[0071] The methods for finding actual measurement point information include: constructing query conditions based on the measurement point reference parameters of the function block and executing an SQL query statement in the measurement point database for matching; or performing a hash lookup through the measurement point index table in memory. For example, when the measurement point reference contains a logical page number and a measurement point name, a composite key value is constructed to locate the corresponding actual measurement point record in the hash table.

[0072] S105, compare the referenced measurement point information with the actual measurement point information.

[0073] The methods for comparing measurement point information include: comparing the character sequences of the measurement point page number and the measurement point description field by field to see if they match completely; or calculating the checksum of the measurement point information for comparison. For example, the measurement point page number can be converted into an integer value for comparison, and the digest value can be compared after performing an MD5 hash operation on the measurement point description string.

[0074] S106, if the referenced measurement point information is inconsistent with the measurement point page number and / or measurement point description of the actual measurement point information, then the referenced measurement point information in the function block is synchronized with the actual measurement point information.

[0075] Synchronizing measurement point information can be achieved by: updating the measurement point reference field of the function block through assignment operations on the memory data structure; or by calling the configuration update interface provided by the controller for writing. For example, when a mismatch in measurement point page numbers is detected, the "pageID" field value of the function block is replaced with the corresponding value of the actual measurement point information, and a dirty flag update of the data object structure is triggered.

[0076] S107, after the reference measurement point information of all functional blocks in the controller is synchronized, the synchronized data object structure of each controller is written to the disk.

[0077] The methods for writing to disk include: serializing the data object structure in memory into a binary file or text file for storage; or updating configuration data in batches through database transactions. For example, the Protocol Buffers serialization framework can be used to convert controller data objects into byte streams and write them to a configuration file at a specified path.

[0078] This application addresses the issue of cross-controller data inconsistency caused by configuration changes by synergistically constructing an in-memory data model and a measurement point information verification mechanism. Specifically, the dynamic data model built based on the configuration file can fully map the controller's logical hierarchy. By traversing function blocks and automatically identifying measurement point reference nodes, combined with real-time retrieval of the measurement point library and a dual-parameter verification mechanism, automatic detection and correction of measurement point information changes are achieved. This closed-loop processing flow of "construction-traversal-retrieval-comparison-correction" effectively avoids control logic errors caused by changes in index information such as logical page numbers and node numbers due to configuration modifications, ensuring the accuracy and reliability of cross-controller data sharing in distributed control systems.

[0079] For example, the system first obtains the controller's configuration file and data configuration file. The configuration file records the hierarchical relationships of tasks, logical pages, and functional blocks, while the data configuration file contains key information such as measurement point page numbers and descriptions. When constructing the controller's data object structure in memory based on these files, an operable dynamic data model is formed by associating logical relationships with measurement point data. When traversing functional blocks, nodes requiring processing are selected by identifying their measurement point reference markers. For example, if a functional block of controller A references a measurement point of controller B, the system will perform a precise search in the measurement point library based on the functional block type. Functional blocks of structure type will simultaneously process sub-measurement point information, while redundant types will associate redundant measurement point data. A dual-parameter verification mechanism is used when comparing measurement point page numbers and descriptions. When it is found that the page number of measurement point P1 of controller B changes from 3 to 5 or the description changes from "temperature sensor" to "pressure sensor," a synchronization operation is immediately triggered to update the functional block's reference information to the actual measurement point information. After synchronizing all functional blocks, the corrected data in memory is permanently stored on disk.

[0080] This application's embodiments achieve automatic verification and synchronization of measurement point information by constructing an in-memory data object structure. Specifically, when the logical page number or measurement point description in the configuration configuration file changes, the system can traverse function blocks and retrieve the actual information in the measurement point library to promptly correct outdated data from the referencing party. For example, in a thermal power unit control system, if the commissioning personnel modify the logical page number of the referenced controller, this method can complete the synchronous update of the referenced information before data sharing between controllers, thereby avoiding abnormal control logic operations caused by incorrect references. By establishing a closed-loop processing flow of "construction-traversal-retrieval-comparison-correction," the problem of the referencing party's inability to synchronize updates due to changes in the referenced party's measurement point information during configuration commissioning is effectively solved, ensuring the accuracy of cross-controller data sharing and system stability.

[0081] In some embodiments, the step of traversing each functional block of each controller to determine the functional block referencing the measurement point information includes:

[0082] Number each controller;

[0083] Based on the configuration configuration file, the task configuration information in the controller is read sequentially according to the number, and each task is created in memory;

[0084] Based on the configuration configuration file, the operation order of the logical pages under the task is read, and the logical pages under each task are established in memory;

[0085] Traverse each function block under the logical page to determine the function block that references the measurement point information.

[0086] Among these, the controller number refers to assigning a unique identifier to each controller, which can be implemented using numeric numbers, letter codes, or a combination of these codes. Its purpose is to establish an ordered management framework in a multi-controller environment. The task configuration information reading order refers to loading task data sequentially according to the controller number order. This can be implemented using sequential reading, segmented loading, or parallel processing methods, aiming to ensure a mapping relationship between memory task objects and physical controllers. Logical page operation order resolution refers to constructing the memory logical page structure based on the execution timing recorded in the configuration file. This can be implemented using topological sorting, timing resolution, or priority marking methods, aiming to ensure complete consistency between the memory model and the actual execution timing of logical pages by the controllers.

[0087] This application establishes a management framework for multi-controller environments through a controller numbering mechanism, ensuring a deterministic order for reading task configuration information for each controller. Upon system startup, all controllers are uniquely numbered according to preset rules, such as using an incremental numbering method like 001, 002, etc. Then, the task configuration information of each controller is read sequentially according to the numbering order, constructing a set of task objects corresponding to the physical controllers in memory. After the task objects are constructed, the logical page operation order recorded in the configuration file is parsed, and a logical page hierarchy structure is established according to the actual execution order. Finally, functional blocks are traversed layer by layer under the logical page hierarchy. This top-down hierarchical traversal strategy accurately locates the physical position of all functional blocks, and combined with a measurement point reference judgment mechanism, achieves complete coverage of measurement point reference nodes.

[0088] For example, in a system containing three controllers, the controllers are first numbered 001, 002, and 003. The system reads the task configuration files of each controller sequentially according to the numbering order, and establishes memory task objects corresponding to the physical locations of the controllers. For each task, the execution order of logical pages recorded in the configuration configuration file is parsed. For example, if task A contains the operation order of logical page 1-logical page 3-logical page 2, then the corresponding logical page linked list structure is constructed in memory. Subsequently, the functional blocks are traversed one by one according to the operation order at the logical page level. When a functional block is detected to have a measurement point reference, its measurement point information is recorded and the subsequent synchronization process is triggered. This implementation ensures that the traversal order is strictly consistent with the actual execution timing of the controllers, and at the same time, the numbering mechanism avoids the confusion of configuration information in multi-controller scenarios.

[0089] This application implements ordered management of measurement point information traversal in a multi-controller environment. The controller numbering mechanism ensures a deterministic order of task configuration information reading, avoiding information confusion in multi-controller scenarios. A memory model consistent with the physical execution timing is established based on the task and logical page construction process of the configuration file, eliminating measurement point reference identification errors caused by disordered logical page operation order. The hierarchical function block traversal strategy guarantees complete coverage of all measurement point reference nodes, significantly improving the systematicness and reliability of the measurement point information synchronization process in the heating network system, thereby effectively solving the problem of control logic operation errors caused by abnormal cross-controller reference data.

[0090] In some embodiments, when traversing all function blocks in the controller, if the currently traversed function block does not reference measurement point information, the currently traversed function block is skipped and the next function block is traversed.

[0091] This application can be implemented using algorithms such as depth-first traversal or breadth-first traversal. "Skipping the currently traversed function block" means that when it is detected that the current function block does not involve measurement point references, the subsequent processing flow of that function block is directly terminated and the processing of the next function block is initiated. This can be achieved by setting a status flag or using conditional statements. This application, through a pre-judgment mechanism, excludes invalid processing steps from the operation flow, allowing computational resources to be concentrated on the measurement point reference function blocks that truly require synchronization.

[0092] This application embeds conditional judgment logic during the function block traversal process. When the measurement point reference flag of the current function block is detected to be invalid, the measurement point search, comparison, and synchronization operations of that function block are immediately skipped, and the processing flow of the next function block is directly entered. This step forms a logical closed loop with the preceding steps such as building the data object structure based on the configuration file and determining the function blocks that reference measurement point information. By performing validity screening during the traversal stage, redundant measurement point library queries and data comparison operations are avoided for irrelevant function blocks, thereby reducing system resource consumption.

[0093] For example, within the controller's logical page, when traversing to a function block, the measurement point reference flag in the function block's attribute table is read first. If this flag indicates no referenced measurement point information, the measurement point library query, comparison, and synchronization operations for that function block are skipped, and the processing flow of the next function block in the logical page is immediately initiated. This implementation, by setting a dedicated flag in the function block's attribute table, achieves rapid identification and skipping of invalid processing steps, significantly reducing the number of unnecessary system calls.

[0094] This application employs a pre-judgment mechanism during the traversal process to effectively avoid redundant processing of function blocks that do not reference measurement point information, reducing system resource consumption and wasted processing time, thereby improving the overall processing efficiency of measurement point information synchronization in the heating network system. This approach allows computing resources to be concentrated on the measurement point reference function blocks that truly require synchronization, significantly optimizing system performance while ensuring synchronization accuracy.

[0095] In some embodiments, based on the function block referencing the measurement point information, the actual measurement point information corresponding to the function block is searched in the controller's measurement point library, including:

[0096] Determine the type of the function block;

[0097] Based on the type of the function block, determine the reference measurement point information of the function block; and search for the actual measurement point information corresponding to the function block in the controller's measurement point library.

[0098] This application classifies and identifies functional blocks through a type judgment module, establishing a mapping relationship between different types of functional blocks and measurement point information structures. Based on this, the measurement point parsing module determines the corresponding referenced measurement point information according to type characteristics. For example, for structure types, it extracts the main and sub-measurement point information; for inter-station reference types, it obtains the combination information of the controller number and measurement point identifier; and for redundant types, it identifies the relationship between main and backup measurement points. Finally, the measurement point matching module performs multi-dimensional index matching in the measurement point database to ensure accurate location of actual measurement point information. This type-based processing strategy maintains the integrity of measurement point information for different types of functional blocks while improving the accuracy of cross-controller measurement point synchronization.

[0099] For example, when processing function blocks of the structure type, the system parses the main test point information and multiple sub-test point information contained therein, and simultaneously matches the main test point identifier and sub-test point index in the test point database. For function blocks of the inter-station reference type, the system extracts the combined parameters of the controller number and the test point identifier, and locates the test point information of the target controller in the distributed test point database. For redundant test point reference types, the system identifies the association between the main and backup test points, and simultaneously verifies the synchronization status of the main and backup test points in the test point database. This specific implementation ensures the adaptability and accuracy of different types of function blocks when searching for test points.

[0100] This application can establish differentiated measurement point information positioning logic based on the differences in function block types, solving the problem of mismatch in measurement point information structure features caused by differences in function block types. When configuration modifications cause changes in the measurement point information of the referenced party, it can accurately locate the actual measurement point information, avoiding measurement point positioning deviations caused by type differences, thereby effectively ensuring the accuracy and reliability of cross-controller measurement point synchronization.

[0101] In some embodiments, the type of the functional block includes: structure type, unstructure type, inter-station reference type, and redundant measurement point reference type; determining the reference measurement point information of the functional block based on its type includes:

[0102] In response to the fact that the function block is a structure type, the reference measurement point information and multiple sub-measurement point information of the function block are determined;

[0103] In response to the fact that the function block is a non-structure type, the reference measurement point information of the function block is determined;

[0104] In response to the fact that the function block is of the inter-station reference type, the reference measurement point information and controller number of the function block are determined;

[0105] In response to the function block being a redundant measurement point reference type, the reference measurement point information and redundant measurement point information of the function block are determined.

[0106] Specifically, when a structure-type function block is detected, the system recursively parses its contained sub-measurement point fields to construct a complete measurement point path index; for non-structure types, the system directly extracts the measurement point identifier; when processing inter-station reference types, the system performs a joint query between the controller number and the local measurement point index; for redundant measurement point reference types, the system simultaneously maintains the synchronization status of the primary and backup measure points. This type-based processing mechanism establishes a mapping relationship between measurement point reference characteristics and data structures, enabling reference scenarios of varying complexity to obtain matching parsing strategies.

[0107] For example, when a function block is identified as a structure type, the system will parse its multiple sub-measurement point fields. For instance, a temperature sensor module may contain three sub-measurement points: "temperature value," "alarm threshold," and "calibration coefficient." The system will establish reference paths for these three sub-measurement points respectively. When processing inter-station reference types, the system will use the controller number as a prefix identifier. For instance, when controller A references a measurement point of controller B, a complete identifier of "B_measurement point page number_measurement point description" will be generated. In redundant measurement point reference scenarios, the system will maintain the synchronization status between the primary measurement point and the backup measurement point. When the primary measurement point changes, the system will automatically trigger the update operation of the backup measurement point.

[0108] This application employs differentiated parsing strategies for different types of measurement point reference relationships. The structure type processing mechanism ensures accurate positioning of nested measurement points within complex data structures, while the non-structure type processing method avoids the parsing overhead of simple reference scenarios. Inter-station reference types achieve accurate cross-domain addressing through controller number binding, and redundant measurement point reference types ensure data synchronization in high-availability scenarios through redundant information association. This classification processing mechanism effectively solves the problem of inaccurate identification of measurement point reference features in diverse industrial control systems, thereby ensuring the reliability of cross-controller data sharing.

[0109] In some embodiments, in response to the functional block being a structure type, the method further includes:

[0110] If the currently traversed function block has reference test point information, determine whether the reference test point information contains sub-test point information;

[0111] In response to the fact that the referenced measurement point information contains sub-measurement point information, the actual measurement point information corresponding to the function block is searched in the measurement point library of the controller.

[0112] This application establishes a dual detection mechanism in the measurement point processing flow of structure-type function blocks: First, after confirming that the function block is a structure type, when the current function block is found to have referenced measurement point information, it further verifies whether the referenced measurement point information contains sub-measure point information. If sub-measure point information is detected, the corresponding actual measurement point information search operation is performed in the controller measurement point library. This hierarchical and progressive detection and search mechanism, by adding a sub-measure point level verification step on top of the top-level measurement point detection, ensures that the measurement point information search range can cover the entire structure level, thereby avoiding measurement point mapping errors caused by missing factor measurement point information.

[0113] For example, when traversing a structure type function block, the system first reads the metadata field of its referenced measurement point information and determines whether sub-measurement point information exists by parsing the structure identifier bit in the field. If the identifier bit indicates the existence of sub-measurement point information, the system locates the actual storage location of the top-level measurement point and sub-measurement points in the controller measurement point library according to the hierarchical index of the measurement point information, and updates the measurement point information at each level synchronously. For example, when processing a device structure containing temperature sensor sub-measurement points, the system first synchronizes the device measurement point information, and then synchronizes the page number and description information of the temperature sensor sub-measurement points layer by layer.

[0114] This application introduces a sub-measurement point information detection mechanism into the measurement point processing flow of structure-type function blocks, ensuring that the measurement point information search scope covers the complete hierarchical structure. This layered and progressive detection and search mechanism effectively guarantees the integrity and accuracy of measurement point information for complex structures, avoids measurement point mapping errors caused by missing factor measurement point information, and thus solves the problems of cross-controller data sharing anomalies and control logic operation errors.

[0115] In some embodiments, it also includes:

[0116] The data object structure of each synchronized controller is displayed on the graphical interface.

[0117] Graphical interface (GUI) display refers to presenting the controller's data object structure through a visual interactive interface. This can be achieved using hierarchical tree diagrams, topology connection diagrams, or tabular comparison views. Specifically, this display function establishes a dynamic mapping relationship between in-memory data structures and graphical interface elements, enabling the controller's task configuration information, logical page operation order, and the association between functional blocks and measurement point information to be represented visually. Its purpose is to provide a visual verification method for manual review, enabling confirmation of the technical status during the final solidification stage of the heating network system's measurement point information synchronization process.

[0118] This application visualizes the controller data object structure built in memory after the synchronization operation is completed, forming a closed-loop verification mechanism by comparing and correcting the data with the measurement point information. After the synchronization module completes the correction of the measurement point page number and description, the write module triggers an update command for the graphical interface before performing a disk write operation. This causes the interface display component to parse and render the data object structure according to preset visualization rules. This display method maintains a dynamic relationship with the data object structure built in memory, reflecting the modification traces during the synchronization process in real time. In particular, it provides explicit identification of the synchronization status of the measurement point page number and description, for example, by using color to distinguish between synchronized and differing measurement points.

[0119] For example, before comparing and correcting the measurement point information and writing the data object structure to disk, a hierarchical, expanded tree structure is used to display the task configuration information of each controller. The top-level node displays the controller number and version information, the middle-level nodes are arranged according to the logical page operation order, and the bottom-level nodes display the measurement point reference relationship in units of function blocks. When an inconsistency is detected in the measurement point page number or measurement point description, the corresponding function block node is automatically marked in a red warning state. After the synchronization correction is completed, the mark automatically turns into a green confirmation state. Debugging personnel can click on each level node to expand and view the specific measurement point information layer by layer, and directly trigger the difference comparison function in the graphical interface to compare the currently displayed measurement point information with the actual information in the measurement point library side by side.

[0120] After completing the synchronization of measurement point information in the heating network system, this application visualizes the controller data object structure built in memory through a graphical interface. This visualization explicitly identifies the synchronization status of measurement point page numbers and descriptions, allowing commissioning personnel to progressively examine the task configuration, logical page operation order, and the relationship between functional blocks and measurement point information for each controller. This provides an opportunity for manual review before finalizing the data to disk, effectively compensating for the shortcomings of plain text configuration files in intuitively locating measurement point association errors. Ultimately, this ensures that the configuration data written to disk has the reliability guarantee of visual verification.

[0121] As a specific example, such as Figure 2 As shown, the specific steps for implementing this application are as follows:

[0122] Step 1: Read the system symbol library file on the disk and load the system symbol library into memory.

[0123] Step 2: Read the configuration files and data files of all controllers, and create a new data object structure for the controller in memory.

[0124] Step 3: Assume that a total of N controller data object structures with numbers 1 to N are read (N>=1).

[0125] Step 4: Iterate through controllers [i], where i > 0 and i <= N.

[0126] Step 5: Based on the computation task configuration information read by controller [i] from the configuration configuration file, create new computation tasks at each level under the controller. Assume that the total number of newly created computation tasks in controller [i] is M, where M>=1.

[0127] Step 6: Read the configuration files for each task level in controller [i], and create logical pages for each task level based on the configuration files.

[0128] Step 7: Iterate through the tasks [j] in the controller [i], where j>0 and j<=M.

[0129] Step 8: Read the data file of the logical page according to the operation order of the logical page under task [j], and load the operation data of the logical page into memory.

[0130] Step 9: Traverse all functional blocks in the logical pages loaded into memory. If all functional blocks have been traversed, proceed to step 22. Otherwise, proceed to step 10.

[0131] Step 10: If the current function block does not reference KKS, proceed to step 9 and iterate through the next function block in the logical page. If the function block references KKS, proceed to step 11.

[0132] Step 11: Determine the type of the function block. If the function block is a structure type (the function block will reference a primary key (primary KKS) and several subkeys (sub KKS)), proceed to step 12. If the function block is a non-structure type, proceed to step 13.

[0133] Step 12: Obtain the main KKS and all child KKS of the function block. Iterate through all obtained KKS and search for the corresponding measurement point in the current controller measurement point library. If no corresponding measurement point is found, set the page number of the KKS within the function block to 0 and the description to empty. If a corresponding measurement point is found, obtain the page number (generated in real-time by compiling the measurement point after reading the file) and description (the measurement point description may be modified individually, resulting in inconsistency with the measurement point description referenced in the function block), and compare them with the page number (obtained by reading the logical page configuration file) and description (obtained by reading the logical page configuration file) of the KKS in the function block. If the page numbers are inconsistent, update the page number of the KKS in the function block and assign the page number of the measurement point to the page number corresponding to the KKS in the current function block. If the descriptions are inconsistent, update the description of the KKS in the function block and assign the description of the measurement point to the description corresponding to the KKS in the current function block. Then execute Step 9.

[0134] Step 13: Determine the function block type. If the function block is a non-structural general function block (referring only to the KKS of a single measurement point within the current device), proceed to step 14. Otherwise, proceed to step 15.

[0135] Step 14: Search for the test point corresponding to the non-structured function block KKS in the test point library. If no corresponding test point is found, set the page number corresponding to the KKS within the function block to 0 and the description corresponding to the KKS within the function block to empty. If a corresponding test point is found, obtain the page number (the page number is generated in real-time by compiling the test point after reading the file) and the description of the test point, and compare them with the page number (obtained by reading the logical page configuration file) and description of the KKS in the function block. If the page numbers are inconsistent, update the page number corresponding to the KKS in the function block and assign the page number of the test point to the page number corresponding to the KKS in the current function block. If the descriptions are inconsistent, update the description corresponding to the KKS in the function block and assign the description of the test point to the description corresponding to the KKS in the current function block. Finally, execute step 9.

[0136] Step 15: Determine the function block type. If the type is an inter-station reference function block (the referenced measurement point is not within this controller), proceed to step 16. If it is a redundant measurement point reference function block (referencing two measurement points, a primary measurement point and a redundant measurement point), proceed to step 18.

[0137] Step 16: Obtain the KKS referenced in the function block, traverse all controllers, and query the KKS in the controller measurement point library. If the measurement point corresponding to the current KKS is found, record the current controller number, the page number corresponding to the measurement point, and the measurement point description, and proceed to Step 17. If no corresponding measurement point is found after traversing all controllers, set the controller number and page number corresponding to the KKS in the function block to 0, and set the measurement point description information to empty, and proceed to Step 9.

[0138] Step 17: Compare the controller number and page number corresponding to KKS in the function block with the controller number and page number recorded in Step 16. If the controller number is inconsistent, update the recorded controller number to the controller number corresponding to KKS in the function block. If the page number is inconsistent, update the recorded page number to the page number corresponding to KKS in the function block. If the description is inconsistent, update the recorded description to the description corresponding to KKS in the function block. Finally, execute Step 9.

[0139] Step 18: Obtain the primary KKS and redundant KKS of the redundant function block. Query the controller measurement point library for the measurement point corresponding to the primary KKS and the redundant KKS. If both the primary and redundant measurement points exist, proceed to step 19. Otherwise, set the page number corresponding to the primary measurement point KKS in the function block to 0 and the description to empty. Set the page number of the redundant measurement point in the function block to 0 and the description to empty, then proceed to step 9.

[0140] Step 19: Record the page number and description of the measurement point corresponding to the primary KKS queried in Step 19. Record the page number and description of the measurement point corresponding to the redundant KKS queried in Step 19.

[0141] Step 20: Compare the page number and description of the main KKS recorded in Step 19 with the corresponding page number and description of the main KKS in the function block. If the page numbers do not match, update the page number corresponding to the main KKS in the function block to the corresponding page number of the main KKS. If the descriptions do not match, update the description corresponding to the main KKS in the function block to the corresponding description of the main KKS.

[0142] Step 21: Compare the page number and description of the redundant KKS recorded in Step 19 with the corresponding page number and description of the redundant KKS in the function block. If the page numbers are inconsistent, update the recorded redundant page number to the page number corresponding to the redundant KKS in the function block. If the descriptions are inconsistent, update the recorded redundant measurement point description to the description corresponding to the redundant KKS in the function block, and then execute Step 9.

[0143] Step 22: Execute j = j + 1. If j <= M, return to step 8. Otherwise, execute step 23.

[0144] Step 23: Execute i = i + 1. If i <= N, return to step 6; otherwise, execute step 24.

[0145] Step 24: Write the synchronized logical pages of all controllers in memory into the configuration file on the disk, according to the data structure of the controller object created in Step 2.

[0146] Step 25: After the graphical user interface detects that all configuration files have been successfully written, it starts the visualization interface refresh thread to refresh all controller data in memory in the order of task and logical page.

[0147] like Figure 3 As shown in the figure, this application embodiment provides a device for synchronizing measuring point information of a heating network system, including:

[0148] The acquisition module 301 is used to acquire the configuration configuration file and data configuration file of each controller; wherein, the configuration configuration file is used to characterize the logical relationships in the controller, and the logical relationships include the composition and connection relationship of tasks, logical pages under tasks, and functional blocks under logical pages; the data configuration file includes measurement point information; the measurement point information includes measurement point page number and measurement point description;

[0149] Module 302 is used to construct the data object structure of each controller in memory based on the configuration configuration file and the data configuration file;

[0150] Module 303 is used to traverse each function block of each controller and determine the function block that references the measurement point information.

[0151] The lookup module 304 is used to search for the actual measurement point information corresponding to the function block in the controller's measurement point library based on the function block referencing the measurement point information.

[0152] The comparison module 305 is used to compare the referenced measurement point information with the actual measurement point information;

[0153] The synchronization module 306 is used to synchronize the referenced measurement point information in the function block to the actual measurement point information if the referenced measurement point information is inconsistent with the measurement point page number and / or measurement point description of the actual measurement point information.

[0154] The writing module 307 is used to write the synchronized data object structure of each controller to the disk after the reference measurement point information of all functional blocks in the controller is synchronized.

[0155] According to embodiments of this application, this application also provides an electronic device and a readable storage medium.

[0156] The electronic device includes at least one processor and a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor, which, when executed, enable the at least one processor to perform the heating network system measuring point information synchronization method described in this application. The computer instructions are used to cause the computer to execute the heating network system measuring point information synchronization method described in this application.

[0157] This application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implements the method for synchronizing measuring point information of a heating network system according to this application.

[0158] Figure 4 A schematic block diagram of an example electronic device 800 that can be used to implement embodiments of this application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the application described and / or claimed herein.

[0159] like Figure 4 As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. The RAM 803 may also store various programs and data required for the operation of the electronic device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0160] Multiple components in electronic device 800 are connected to I / O interface 805, including: input unit 806, such as keyboard, mouse, etc.; output unit 807, such as various types of displays, speakers, etc.; storage unit 808, such as disk, optical disk, etc.; and communication unit 809, such as network card, modem, wireless transceiver, etc. Communication unit 809 allows electronic device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0161] The computing unit 801 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as the method for synchronizing measurement point information in a heating network system. For example, in some embodiments, the method for synchronizing measurement point information in a heating network system can be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by the computing unit 801, one or more steps of the method for synchronizing measurement point information in a heating network system described above can be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform a method for synchronizing measurement point information of a heating network system by any other suitable means (e.g., by means of firmware).

[0162] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0163] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0164] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0165] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0166] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0167] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0168] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for synchronizing measuring point information in a heating network system, characterized in that, include: Obtain the configuration file and data configuration file of each controller; wherein, the configuration file is used to characterize the logical relationships in the controller, the logical relationships include the composition and connection relationship of tasks, logical pages under tasks, and functional blocks under logical pages; the data configuration file includes measurement point information; the measurement point information includes measurement point page number and measurement point description; Based on the configuration configuration file and the data configuration file, a data object structure for each controller is constructed in memory; Iterate through each function block of each controller to determine the function block that references the measurement point information; Based on the function block that references the measurement point information, the actual measurement point information corresponding to the function block is searched in the measurement point library of the controller; Compare the referenced measurement point information with the actual measurement point information; If the referenced measurement point information is inconsistent with the measurement point page number and / or measurement point description of the actual measurement point information, the referenced measurement point information in the function block will be synchronized with the actual measurement point information. After the reference measurement point information of all functional blocks in the controller is synchronized, the synchronized data object structure of each controller is written to the disk.

2. The method according to claim 1, characterized in that, The process of traversing each functional block of each controller to determine the functional block that references the measurement point information includes: Number each controller; Based on the configuration configuration file, the task configuration information in the controller is read sequentially according to the number, and each task is created in memory; Based on the configuration configuration file, the operation order of the logical pages under the task is read, and the logical pages under each task are established in memory; Traverse each function block under the logical page to determine the function block that references the measurement point information.

3. The method according to claim 1, characterized in that, When traversing all function blocks in the controller, if the currently traversed function block does not reference measurement point information, the currently traversed function block is skipped and the next function block is traversed.

4. The method according to claim 1, characterized in that, Based on the function block referencing the measurement point information, the actual measurement point information corresponding to the function block is searched in the controller's measurement point library, including: Determine the type of the function block; Based on the type of the function block, determine the reference measurement point information of the function block; and search for the actual measurement point information corresponding to the function block in the controller's measurement point library.

5. The method according to claim 4, characterized in that, The types of the functional blocks include: structured types, unstructured types, inter-station reference types, and redundant measurement point reference types; determining the referenced measurement point information of the functional block based on its type includes: In response to the fact that the function block is a structure type, the reference measurement point information and multiple sub-measurement point information of the function block are determined; In response to the fact that the function block is a non-structure type, the reference measurement point information of the function block is determined; In response to the fact that the function block is of the inter-station reference type, the reference measurement point information and controller number of the function block are determined; In response to the function block being a redundant measurement point reference type, the reference measurement point information and redundant measurement point information of the function block are determined.

6. The method according to claim 5, characterized in that, In response to the function block being a structure type, it also includes: If the currently traversed function block has reference test point information, determine whether the reference test point information contains sub-test point information; In response to the fact that the referenced measurement point information contains sub-measurement point information, the actual measurement point information corresponding to the function block is searched in the measurement point library of the controller.

7. The method according to claim 1, characterized in that, Also includes: The data object structure of each synchronized controller is displayed on the graphical interface.

8. A device for synchronizing measuring point information in a heating network system, characterized in that, include: The acquisition module is used to acquire the configuration configuration file and data configuration file of each controller; wherein, the configuration configuration file is used to characterize the logical relationships in the controller, and the logical relationships include the composition and connection relationship of tasks, logical pages under tasks, and functional blocks under logical pages; the data configuration file includes measurement point information; the measurement point information includes measurement point page number and measurement point description; A construction module is used to construct the data object structure of each controller in memory based on the configuration configuration file and the data configuration file; The determination module is used to traverse each function block of each controller and determine the function block that references the measurement point information. The lookup module is used to search for the actual measurement point information corresponding to the function block in the controller's measurement point library based on the function block that references the measurement point information. The comparison module is used to compare the referenced measurement point information with the actual measurement point information; The synchronization module is used to synchronize the referenced measurement point information in the function block to the actual measurement point information if the referenced measurement point information is inconsistent with the measurement point page number and / or measurement point description of the actual measurement point information. The writing module is used to write the synchronized data object structure of each controller to the disk after the reference measurement point information of all function blocks in the controller is synchronized.

9. An electronic device, characterized in that, include: At least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the method according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-7.

Images