Configuration Data Synchronization Across Partitioned Plant Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Industrial plants with distributed control systems face challenges in synchronizing configuration data across multiple servers, particularly during network interruptions, which can lead to inconsistencies and affect the robustness and reliability of the system.
Innovation Solution
A method for synchronizing configuration data across sub-networks in industrial plants, where data is stored on multiple servers, involves checking for unchanged data upon network reconnection and applying an ownership-based strategy to ensure consistency, with a journal for tracking changes and maintaining a 'zone of trust' through partitioning strategies based on spatial, functional, or organizational vicinity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration data are distributed over several servers to enhance redundancy and reliability, then system robustness is improved, but data consistency across servers deteriorates during network interruptions
Solution Approach 1:
The network is segmented into multiple sub-networks that can operate independently during interruptions, with each server maintaining local configuration data autonomy while preserving the ability to synchronize when connected
Solution Approach 2:
Configuration data are pre-synchronized and stored on multiple servers before network interruptions occur, enabling each server to continue operating with valid configuration data even when connectivity is lost
2Measurement precision
If all server replicas are compared to ensure data consistency upon network reconnection, then data accuracy is improved, but synchronization time and computational resources increase
Solution Approach 1:
The synchronization process extracts and compares only the specific configuration data elements that changed during the network interruption, rather than comparing all configuration data replicas, thereby reducing synchronization time while maintaining accuracy
Solution Approach 2:
A feedback mechanism tracks which configuration data have been modified on each server, enabling targeted synchronization that focuses only on changed elements and automatically verifies consistency upon reconnection
3Stability of the object's composition
If strict central control is implemented to maintain configuration data consistency, then data uniformity is improved, but system adaptability and ease of local modifications deteriorate
Solution Approach 1:
The system dynamically adjusts its control mode based on network availability: during connectivity, centralized consistency rules apply; during interruptions, local servers gain autonomy to modify configuration data independently, with changes synchronized when connectivity is restored
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
The invention relates to the field of industrial plants, particularly to a method for synchronizing configuration data of components within an industrial plant and their synchronisation. The method comprises the steps of: Partitioning a network (400) in the industrial plant into a first sub-network (100) and a second sub-network (200), said sub-networks (100, 200) connected by a network connection (300), wherein a first component (110, 120) with first configuration data (111, 112, 121, 122), and a first local server (180) are located in the first sub-network (100). Additionally, a second component (210, 220) with a second configuration data (211, 212, 221, 222), and a second local server (280) are located in the second sub-network (200). Storing the first configuration data (111, 112, 121, 122) on the first local server (180) and, via the network connection (300), on the second local server (280), and the second configuration data (211, 212, 221, 222) on the second local server (280) and, via the network connection (300), on the first local server (180). Interrupting the network connection (300); and updating, on the first local server (180), the first configuration data (111, 112, 121, 122) and the second configuration data (211, 212, 221, 222). Re-connecting the network connection (300); and, if the first configuration data (111, 112, 121, 122) on the second local server (280) is unchanged, overwriting the first configuration data (111, 112, 121, 122) on the second local server (280) by the updated first configuration data (111, 112, 121, 122).