Intelligent synchronization system and method for signal point table

Abstract

The application provides a signal point table intelligent synchronization system and method, which can automatically perceive changes in the signal point table when the signal point table changes, generate early warning information, and realize model comparison display and one-key synchronization update. The system supports historical point table version archiving and modification log recording, ensuring the integrity, accuracy and traceability of model updating. Through the application, the artificial maintenance burden can be effectively reduced, the model consistency checking efficiency can be improved, and the intelligent level and system reliability of the centralized control center operation can be significantly enhanced.

Description

Technical Field

[0001] This invention relates to the field of power plant centralized control technology, and in particular to an intelligent synchronization system and method for signal point meters. Background Technology

[0002] With the increasing trend of new power systems developing towards higher proportions of renewable energy, higher levels of automation, and greater intensification, the intelligent management capabilities of the centralized control center, as a crucial hub in power production, directly impact the stability and operational efficiency of the entire system. In power plant automation systems, signal point tables play a vital role in connecting field equipment with the upper-level monitoring system, serving as the foundational data units for constructing system models and real-time monitoring logic. Signal point tables typically contain key information such as device name, measurement point address, data type, communication parameters, and access permissions. They define the standard formats and calling specifications for various remote signaling, telemetry, and remote control points, and are a key carrier for the centralized control system to achieve information acquisition, status monitoring, and remote control functions.

[0003] As operating time progresses, the equipment structure, functional modules, and control strategies of a power plant often change, necessitating continuous adjustments and updates to the signal point tables. These changes are typically driven by equipment expansion, system upgrades, communication protocol modifications, changes in dispatching instructions, or frequency and peak-shaving requirements, and their frequency and complexity are increasing year by year. Against this backdrop, the synchronous maintenance of signal point tables has become one of the core tasks of the centralized control center's daily operations and maintenance.

[0004] However, in the current mainstream signal point table management technology, most centralized control systems still rely on manual import, comparison table, script update and other methods to complete the synchronization operation of the point table. This approach has significant limitations: (1) It relies on manual identification of differences, which is inefficient and prone to errors, especially when large-scale equipment is connected or batch point tables are changed; (2) The update process usually requires manual confirmation before replacement, lacks systematic difference analysis methods, and cannot intuitively judge the specific changes between the old and new point tables; (3) It lacks a sound version control mechanism, and has weak traceability, auditing and restoration capabilities for historical point table models. Once an update error occurs, it is impossible to quickly roll back or locate the responsibility; (4) The point table update process may interrupt the system monitoring logic, causing safety hazards such as abnormal monitoring of field equipment or remote control malfunction.

[0005] Currently, some factories and stations are attempting to use automatic comparison tools or scripting languages ​​for point table identification and partial automatic replacement, but their application effectiveness is often limited by the system development platform, standards and specifications, and logical complexity. These tools generally struggle to achieve cross-platform integration and deployment, and cannot handle various change scenarios (such as batch addition of points, field format adjustments, permission configuration changes, etc.), resulting in insufficient practicality and flexibility.

[0006] In existing research and application cases, some scholars have proposed semi-automatic update methods for power plant point meter models, such as configuration file comparison and automatic communication message identification. However, these methods mostly focus on single-type changes or communication protocol processing for specific equipment manufacturers, and have not yet formed a unified, visualized, and auditable complete process mechanism. In particular, their adaptability to maintaining model consistency in large-scale centralized control systems remains weak.

[0007] In summary, there is a significant gap between traditional point-based management methods and the current intelligent operation and maintenance needs of centralized control centers, especially in terms of the lack of systematic solutions for automatic change identification, visual difference display, uninterrupted synchronous updates, and historical version archiving. Summary of the Invention

[0008] The present invention aims to at least partially solve one of the technical problems in the related art.

[0009] Therefore, the first objective of this invention is to propose an intelligent synchronization system for signal point tables.

[0010] The second objective of this invention is to propose an intelligent synchronization method for signal point tables.

[0011] The third objective of this invention is to provide an electronic device.

[0012] The fourth objective of this invention is to provide a computer-readable storage medium.

[0013] The fifth objective of this invention is to provide a computer program product.

[0014] To achieve the above objectives, a first aspect of the present invention provides an intelligent synchronization system for signal point tables, comprising:

[0015] The point table change detection module is used to connect to the database or point table file through the interface, monitor changes to the signal point table in real time, and perform difference detection on the point name, point address, data type, communication protocol and permission identifier in the old and new point tables based on the field sensitivity weight model.

[0016] The alarm generation module is used to generate alarm information based on the detected differences and push it to the operators through multiple channels including system interface, email or SMS. The alarm level is dynamically classified according to the change type, number of change points and field sensitivity.

[0017] The model comparison and display module is used to display the differences between the old and new point tables in the form of a visual difference matrix. It uses table alignment, field highlighting and structure diagram comparison to assist operators in reviewing differences and confirming updates.

[0018] The synchronization update module is used to load the new point table model into the cache and realize the dynamic mapping with the old model after the operator confirms that there are no errors. This is based on the dual version cache switching algorithm and transaction mechanism, so as to complete the one-click synchronization update without interruption.

[0019] The historical archiving and modification record module is used to archive and store the point table model before and after the update as versions, record the operator, timestamp, and differences, and support version rollback, fast rollback, and operation log auditing.

[0020] Optionally, the point table change detection module is further used for:

[0021] Let the set of points in the system at the current time be:

[0022] T o ={P o,1 P o,2 P o,3 ... P o,m}

[0023] The updated point table after the changes is as follows:

[0024] T n ={P n,1 P n,2 P n,3 ... P n,m}

[0025] Each point P i It includes the following fields:

[0026] P i ={N i A i T i C i X i ...

[0027] The difference determination method uses the following matching function:

[0028]

[0029] The field comparison weights are defined as follows:

[0030]

[0031] Wherein: T o A collection of old version point tables; T n For the new version of the point table set; P o,1 P is the i-th point in the old version; n,j N is the j-th point in the new version; i For roll call; A iFor point address; T i For data types; C i For communication protocol; X i For permission identification, σ(P) o,i ,P n,j ω is the difference judgment function, representing a comparison function of the field matching degree between two points. The return value depends on whether there is a complete match; 1 indicates complete consistency, 0 indicates no match, and 0 < ω < 1 indicates partial field changes; D(P) is used to quantify the degree of field changes of a single point; α k Assigns importance weights to fields; changes are scanned via periodic polling or data event triggering to ensure minute-level update response; a value of 1 is assigned if the old and new values ​​of a field are different, otherwise a value of 0.

[0032] Optionally, the alarm generation module is further configured to:

[0033] Define the alarm level function as follows:

[0034] L a =f(O j I j Y j )

[0035] Among them, L a Alarm level; O j For change type; I j The quantity is the number of points that change; Y j For field sensitivity.

[0036] Optionally, the model comparison and display module is further used for:

[0037] The difference matrix of the point table is defined as follows:

[0038]

[0039] Where D i,j This indicates whether the j-th field of the i-th point has changed; a value of 0 indicates that the field is consistent; a value of 1 indicates that the field is inconsistent.

[0040] Optionally, the synchronization update module is further configured to:

[0041] Construct a vertex table update graph G = (V, E), where each node is a vertex table entry and edges represent field dependencies; use topological sorting to avoid field conflicts; and perform atomic commits of update commands through a transaction mechanism.

[0042] The new model is loaded into the cache space, and the system uses a model snapshot mapping mechanism to dynamically map the old and new data; after the update window is completed, the model reference is officially switched; in this process, the system adopts a dual-version cache switching algorithm.

[0043] To achieve the above objectives, a second aspect of the present invention provides a method for intelligent synchronization of signal point tables, comprising:

[0044] By connecting to the database or point table file through the interface, changes to the signal point table are monitored in real time, and differences in point name, point address, data type, communication protocol and permission identifier in the old and new point tables are detected based on the field sensitivity weight model.

[0045] Alarm information is generated based on the detected differences and pushed to operators through multiple channels including system interface, email or SMS. The alarm level is dynamically classified according to the type of change, the number of change points and the sensitivity of the field.

[0046] The differences between the old and new point tables are displayed in the form of a visual difference matrix, using table alignment, field highlighting and structure diagram comparison to assist operators in reviewing differences and confirming updates.

[0047] After the operators confirm that there are no errors, the new point table model is loaded into the cache based on the dual-version cache switching algorithm and transaction mechanism, and the dynamic mapping with the old model is realized to complete the one-click synchronization update without interruption.

[0048] The point table model before and after the update is archived and stored as a version, recording the operator, timestamp, and differences, supporting version rollback, fast rollback, and operation log auditing.

[0049] To achieve the above objectives, a third aspect of the present invention provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0050] The memory stores computer-executed instructions;

[0051] The processor executes computer execution instructions stored in the memory to implement the method as described in any one of the second aspects.

[0052] To achieve the above objectives, a fourth aspect of the present invention provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of the second aspects.

[0053] To achieve the above objectives, a fifth aspect of the present invention provides a computer program product that, when executed by a processor, implements the method described in any one of the second aspects.

[0054] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0055] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0056] Figure 1 This is a schematic diagram of the structure of a signal point table intelligent synchronization system provided in an embodiment of the present invention;

[0057] Figure 2 This is a schematic diagram illustrating the relationships between the modules provided in an embodiment of the present invention;

[0058] Figure 3 This is a flowchart illustrating the intelligent synchronization process of the system provided in this embodiment of the invention.

[0059] Figure 4 This is a schematic diagram of the point table difference matrix visualization provided in an embodiment of the present invention. Detailed Implementation

[0060] Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention.

[0061] Figure 1 This is a schematic diagram of the structure of a signal point table intelligent synchronization system provided in an embodiment of the present invention. Figure 1 As shown, the system mainly includes five core modules: point table change detection module 1, alarm generation module 2, model comparison and display module 3, synchronization update module 4, and historical archiving module 5. The relationship between each module is shown in [reference needed]. Figure 2 The system's intelligent synchronization workflow diagram is shown below. Figure 3 .

[0062] In this embodiment of the invention, the point table change detection module 1 is used to connect to a database or point table file via an interface to monitor changes to the signal point table in real time, and to detect differences in point names, point addresses, data types, communication protocols, and permission identifiers between the old and new point tables based on a field sensitivity weight model; the alarm generation module 2 is used to generate alarm information based on the detected differences, and push it to operators through multiple channels including system interface, email, or SMS, with the alarm level dynamically graded according to the change type, the number of changed points, and field sensitivity; the model comparison and display module 3 is used to compare the differences between the old and new point tables. The differences are displayed in the form of a visual difference matrix, using table alignment, field highlighting, and structure diagram comparison to assist operators in reviewing differences and confirming updates. The synchronization update module 4 is used to load the new point table model into the cache and realize dynamic mapping with the old model after the operators confirm that there are no errors. This completes a non-interrupted one-click synchronization update. The history archiving and modification record module 5 is used to archive and store the point table model before and after the update as versions, record the operator, timestamp, and difference content, and support version rollback, fast rollback, and operation log auditing.

[0063] The following is a detailed description of each module.

[0064] (1) Signal Point Change Detection Module: This module continuously monitors the signal point data sent from the power plant to the centralized control system, automatically detecting structural changes such as additions, deletions, or field modifications. The system has built-in change judgment rules, which can accurately determine any minor differences in key fields such as point name, address, type, and permissions, and trigger subsequent processing procedures. Data Monitoring Mechanism: The system connects to a database (such as SCADA / Historian) or signal point file (CSV / XML / EXCEL, etc.) through an interface, and uses an incremental listener to collect data in real time.

[0065] Let the set of points in the system at the current time be:

[0066] T o ={P o,1 P o,2 P o,3 ... P o,m}

[0067] The updated point table after the changes is as follows:

[0068] T n ={P n,1 P n,2 P n,3 ... P n,m}

[0069] Each point P i It includes the following fields:

[0070] P i ={N i A i T i C i X i ...

[0071] The following matching function can be used to determine the difference:

[0072]

[0073] Field comparison weights can be defined as follows:

[0074]

[0075] Wherein: T o This is a collection of older version point tables (e.g., the signal point tables currently in use in the centralized control system); T n For the new version of the point table set (e.g., a signal point table uploaded from the field or newly generated after modification); P o,1 P is the i-th point in the old version; n,j Let P be the j-th point in the new version; each point P contains the following fields, i.e., signal point attributes. Where N... i For roll call (e.g., "PT101"); A i For point address; T i For data types (such as BOOL, INT, FLOAT); C i For communication protocol; X i This serves as a permission identifier (e.g., read-only (RO), write-only (RW), etc.). σ(P) o,i ,P n,j ω is the difference judgment function, representing a comparison function of the field matching degree between two points. The return value depends on whether there is a complete match; 1 indicates complete consistency, 0 indicates no match, and 0 < ω < 1 indicates partial field changes; D(P) is used to quantify the degree of field changes of a single point; α k Assign importance weights to fields, such as name, address, and type, with values ​​of 0.5, 0.3, and 0.2 respectively, to ensure sensitive difference identification. The system performs change scanning through periodic polling or data event triggering to ensure minute-level update response; the value is 1 if the old and new values ​​of a field are different, and 0 otherwise.

[0076] (2) Alarm Generation Module: Once a change in the point table is detected, this module automatically generates an alarm message and pushes it to operators through various means such as the system interface, pop-ups, and emails to ensure that relevant personnel are promptly aware of model deviations. Alarm messages can be processed in a tiered manner according to the change level, improving the priority and accuracy of operators' responses.

[0077] The alarm triggering logic is as follows:

[0078] Define the alarm level function as follows:

[0079] L a =f(O j I j Y j )

[0080] Among them, L a Alarm level (e.g., Level 1 is severe, Level 3 is minor); O j For change types, such as "field modification" or "batch addition"; I j The quantity is the number of points that change; Y j For field sensitivity, such as the importance of changes to certain fields (e.g., address, permissions).

[0081] The sensitivity weights for fields are as follows: Type / Address Error: High (Severe); Permission / Description Change: Medium; Name Format Change: Low. Example categories: Level 1 Alarm: Batch address misalignment, communication protocol loss; Level 2 Alarm: More than 50 field modifications; Level 3 Alarm: Modification of non-critical fields such as description and remarks. Alarms are triggered synchronously through system interface (graphics), voice broadcast, email, SMS, and other push channels, and written to the alarm record database, supporting time-series statistical analysis.

[0082] (3) Model comparison and display module: This module supports visual comparison between the current system model and the latest point table data, using tables, color markings, structure views and other methods to clearly display the differences between each field.

[0083] In this embodiment of the invention, the visualization diagram of the point table difference matrix is ​​shown in Figure 4 (yellow indicates consistency, red indicates difference). Operators can review the comparison results to confirm the rationality and completeness of the model adjustments. Visualization techniques include: table alignment: using hash indexes to quickly locate old and new versions of the same logical point; difference highlighting: using HTML5 DOM and CSS to dynamically render field differences; structure diagram display: displaying the device level to which the point belongs and its changes based on a tree structure (TreeMap). The point table difference matrix is ​​defined as follows:

[0084]

[0085] Where D i,j This indicates whether the j-th field of the i-th point has changed; a value of 0 indicates that the field is consistent; a value of 1 indicates that the field is inconsistent.

[0086] Furthermore, the system supports field filtering and exporting comparison reports (PDF and Excel formats), facilitating offline review. The demonstration is as follows:

[0087]

[0088] (4) Synchronization Update Module: After confirmation by the operators, the system can complete the synchronization update of the point table model with one click. This process does not affect the current operating status of the system, and maintains the continuity of the control task and the stability of the system.

[0089] The mechanisms and strategies employed by this module are as follows:

[0090] Synchronization Mechanism: To ensure the stability and reliability of the node table update process, this system constructs a node table update graph G = (V, E), where each node is a node table entry and edges represent field dependencies. During the update process, the system utilizes a topological sorting method to ensure that the update order follows the field dependencies, avoiding errors caused by field conflicts. For example, when a node depends on the state of another node, topological sorting ensures that the update operations are performed in the order of dependencies, thereby avoiding inconsistencies caused by incorrect ordering.

[0091] Furthermore, all update operations are atomically committed through a transaction mechanism, ensuring data consistency and integrity. This mechanism guarantees that if any problems occur during the update process, the system can roll back to its state before the update, thereby ensuring system stability and data security.

[0092] Hot Update Strategy: This system employs a non-interrupted update mechanism, also known as a hot update mechanism, to ensure uninterrupted system operation and continuous business tasks during point table model updates. The hot update process is implemented through background buffer loading and model snapshot mapping, as detailed below:

[0093] 1. Background Buffer Loading: The system first loads the new model into the cache space. This process occurs in the background and will not affect currently running tasks or business operations. The cache space acts as a temporary storage area to ensure a smooth data transition.

[0094] 2. Model Snapshot Mapping Mechanism: The system uses a model snapshot mapping mechanism to dynamically map the new model to the old model after the update window is completed. This mechanism enables a smooth switch between old and new models, avoiding data inconsistencies or operational conflicts caused by version switching.

[0095] 3. Dual-Version Cache Switching Algorithm: To ensure that monitoring logic is not affected during the update process, this system adopts a dual-version cache switching algorithm. Specifically, the system maintains two versions of the cache simultaneously (the old version and the new version) during the update window. After the update is completed, the system officially switches to the new model version by switching reference pointers. During this process, the dual-version cache ensures that the system does not generate "empty data" or "mismatched data," thereby avoiding false alarms caused by data inconsistency.

[0096] (5) Historical Archiving and Modification Record Module: To ensure that auditing and traceability requirements are met during model management, this system automatically records the complete model version before and after each point table change, and records detailed information such as the person making the change, the time, and the differences in operation content for each change. This module ensures the system's transparency, traceability, and effective management of historical versions. Specific implementation details are as follows:

[0097] This system defines a unique version structure for each change operation. Each version contains the following elements:

[0098] V t = <T t u t e t >

[0099] Where: V t For the t-th version (e.g., one update of the point table corresponds to one version); e t Let u be the set of tables at time t; t For timestamps; e t This serves as the operator's ID. This structure allows for detailed tracking of each change, including key information such as time, personnel, and operation details.

[0100] The system manages the relationships between different versions through the following version chain structure to ensure the integrity and traceability of the version history:

[0101] {V0→V1→...→V t}

[0102] V0 is the initial version, and each subsequent update to the dot table generates a new version. The version chain clearly records the order and relationship of each change. Through this chained management, users can easily view historical versions and trace back the details of any change operation.

[0103] This module uses MongoDB or TimescaleDB as its data storage solution, with the specific choice depending on the system's actual needs and data volume. These databases possess powerful time-series data processing capabilities, efficiently storing time-series data for each model version. Specifically: MongoDB: Suitable for flexible document storage, capable of handling various structured and semi-structured data, supporting efficient data querying and access operations. TimescaleDB: Offers optimized features for efficient storage and querying of time-series data, suitable for large-scale data storage and analysis, especially providing higher performance when processing large amounts of historical data.

[0104] The historical archiving and modification record module not only provides a complete record of the model's change process but also offers users an efficient version management tool. Whether it's difference rollback, rapid rollback, or operation auditing, it significantly improves the system's manageability and security. In practical applications, this module effectively supports complex model management needs, ensuring the transparency and compliance of the model management process.

[0105] Furthermore, the system supports mounting system logs and original uploaded files to the database for comprehensive historical data archiving and retrieval. Through the collaborative work of the above functional modules, this invention constructs a closed-loop, efficient, and secure intelligent synchronization system for signal point tables, suitable for centralized control system model management scenarios in large and medium-sized power plants, with particularly significant advantages in operating environments involving centralized scheduling of multiple power plants and frequent upgrades and access.

[0106] To implement the above embodiments, the present invention also proposes a method for intelligent synchronization of signal point tables, comprising:

[0107] By connecting to the database or point table file through the interface, changes to the signal point table are monitored in real time, and differences in point name, point address, data type, communication protocol and permission identifier in the old and new point tables are detected based on the field sensitivity weight model.

[0108] Alarm information is generated based on the detected differences and pushed to operators through multiple channels including system interface, email or SMS. The alarm level is dynamically classified according to the type of change, the number of change points and the sensitivity of the field.

[0109] The differences between the old and new point tables are displayed in the form of a visual difference matrix, using table alignment, field highlighting and structure diagram comparison to assist operators in reviewing differences and confirming updates.

[0110] After the operators confirm that there are no errors, the new point table model is loaded into the cache based on the dual-version cache switching algorithm and transaction mechanism, and the dynamic mapping with the old model is realized to complete the one-click synchronization update without interruption.

[0111] The point table model before and after the update is archived and stored as a version, recording the operator, timestamp, and differences, supporting version rollback, fast rollback, and operation log auditing.

[0112] Regarding the methods in the above embodiments, the specific manner in which each step is performed has been described in detail in the embodiments related to the device, and will not be elaborated here.

[0113] To implement the above embodiments, the present invention also proposes an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory to implement the method provided in the foregoing embodiments.

[0114] To implement the above embodiments, the present invention also proposes a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the methods provided in the foregoing embodiments.

[0115] To implement the above embodiments, the present invention also proposes a computer program product, including a computer program that, when executed by a processor, implements the methods provided in the foregoing embodiments.

[0116] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in this invention all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0117] It should be noted that personal information collected from users should be used for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. Furthermore, such collection / sharing should only be conducted after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign an agreement / authorization that includes authorization of relevant user information before the user uses the function. In addition, any necessary steps must be taken to protect and safeguard access to such personal information data and ensure that others with access to personal information data comply with their privacy policies and procedures.

[0118] This invention is intended to provide implementation schemes for users to selectively prevent the use or access to personal information data. That is, this disclosure is intended to provide hardware and / or software to prevent or block access to such personal information data. Once personal information data is no longer needed, risks can be minimized by restricting data collection and deleting data. Furthermore, where applicable, such personal information can be de-identified to protect user privacy.

[0119] In the foregoing descriptions of the embodiments, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0120] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0121] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of preferred embodiments of the invention includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of the invention pertain.

[0122] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0123] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any of the following techniques known in the art, or a combination thereof: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0124] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0125] Furthermore, the functional units in the various embodiments of the present invention can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0126] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention.

[0127] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0128] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A signal point table intelligent synchronization system, characterized in that, Comprise: A point table change detection module for interfacing with a database or a point table file, real-time monitoring of changes in the signal point table, and difference detection of point names, point addresses, data types, communication protocols and permission identifiers in the new and old point tables based on a field sensitivity weight model; An alarm generation module for generating alarm information based on the detected differences and pushing it to the operators through multi-channel methods including system interface, email or SMS, with alarm levels dynamically classified according to change type, number of changed points and field sensitivity; A model comparison and display module for displaying the differences between the new and old point tables in the form of a visual difference matrix, using table alignment, field highlighting and structure diagram comparison methods to assist operators in difference review and update confirmation; A synchronization update module for loading the new point table model into the cache and realizing dynamic mapping with the old model based on a double version cache switching algorithm and transaction mechanism after the operators confirm that there is no error, completing the non-interruptive one-key synchronization update; A historical archiving and modification record module for archiving the pre-update and post-update point table models as versions, recording the operator, timestamp and difference content, and supporting version backtracking, quick rollback and operation log auditing.

2. The system of claim 1, wherein, The point table change detection module is also used for: The current point table set in the system is: T o = {P o,1 , P o,2 , P o,3 ,..., P o,m} The new point table uploaded after the change is: T n = {P n,1 , P n,2 , P n,3 ,..., P n,m} Each point P i Contains the following fields: P i = {N i , A i , T i , C i , X i ,...} The difference judgment method uses the following matching function: The field comparison weight uses the following definition: Wherein: T o is a collection of old version point tables; T n is a collection of new version point tables; P o,1 is the i-th point in the old version; P n,j is the j-th point in the new version; N i is the point name; A i is the point address; T i is the data type; C i is the communication protocol; X i is the permission identifier, σ(P o,i , P n,j ) is a difference judgment function, which represents a comparison function of two points in the field matching degree, and the return value depends on whether it is completely matched; 1 represents complete consistency, 0 represents complete mismatch, and 0<ω<1 represents partial field change; D(P) is a function for quantifying the field change degree of a single point; α k is the field importance weight; the change scanning is performed through the dispatching cycle polling or data event triggering mode, and the minute-level update response is ensured; if the new and old values of the field are not the same, it is 1, otherwise it is 0.

3. The system of claim 2, wherein, The alarm generation module is also used for: The alarm level function is defined as: L a = f(O j , I j , Y j ) wherein, L a is the alarm level; O j is the change type; I j is the quantity, i.e. the number of points changed; Y j is the field sensitivity.

4. The system of claim 3, wherein, The model comparison and display module is also used for: The point table difference matrix is defined as: where D i,j represents whether the jth field of the ith point has changed; a value of 0 indicates the field is consistent; a value of 1 indicates the field is inconsistent.

5. The system of claim 4, wherein, The synchronization update module is also used for: A point table update graph G=(V, E) is constructed, where each node is a point table item and the edge is a field dependency; topological sorting is used to avoid field conflicts; and the update command is submitted atomically through a transaction mechanism; The new model is loaded into the cache space, and the system uses a model snapshot mapping mechanism to dynamically map the new and old data; The model reference is officially switched after the update window is completed; in this process, the system uses a double version cache switching algorithm.

6. A method of intelligently synchronizing signal point tables, the method comprising: Comprise: Interfacing with a database or a point table file, real-time monitoring of changes in the signal point table, and difference detection of point names, point addresses, data types, communication protocols and permission identifiers in the new and old point tables based on a field sensitivity weight model; Generating alarm information based on the detected differences and pushing it to the operators through multi-channel methods including system interface, email or SMS, with alarm levels dynamically classified according to change type, number of changed points and field sensitivity; Displaying the differences between the new and old point tables in the form of a visual difference matrix, using table alignment, field highlighting and structure diagram comparison methods to assist operators in difference review and update confirmation; Loading the new point table model into the cache and realizing dynamic mapping with the old model based on a double version cache switching algorithm and transaction mechanism after the operators confirm that there is no error, completing the non-interruptive one-key synchronization update; Archiving the pre-update and post-update point table models as versions, recording the operator, timestamp and difference content, and supporting version backtracking, quick rollback and operation log auditing.

7. An electronic device, comprising: Comprise: a processor, and a memory connected with the processor in communication; the memory stores computer-executed instructions; the processor executes the computer-executed instructions stored in the memory to implement the method of claim 6.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executed instructions, which, when executed by a processor, are used to implement the method of claim 6.

9. A computer program product, characterised in that, A computer program, which, when executed by a processor, implements the method of claim 6.

Images