Industrial File Synchronization Using Qualifying Trigger Actions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing industrial control systems face inefficiencies in file synchronization, including increased memory usage and processing demands as the number of nodes grows, and often result in unintended synchronization due to reliance on timestamp-based methods that require extensive data storage and processing.
Innovation Solution
The system classifies files into established and unestablished categories based on qualifying trigger actions, using hash values and synchronization rules to determine which files need to be synchronized, thereby reducing unnecessary data transfer and processing by only synchronizing files that have undergone specific actions, such as uploads or changes, and limiting synchronization to eligible devices within predetermined groups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If timestamp-based synchronization methods are used to ensure all devices have the most up-to-date files, then file version accuracy is improved, but memory usage and processing demands increase exponentially with the number of nodes
Solution Approach 1:
The patent extracts only the essential synchronization metadata (qualifying trigger actions and timestamps of actions) from the full file content, storing this minimal information in a synchronization database. This allows the system to track file versions and determine synchronization needs without storing or processing entire file contents across all nodes, thereby reducing memory usage while maintaining version accuracy.
Solution Approach 2:
The system performs preliminary classification of files into established and unestablished categories based on qualifying trigger actions before synchronization occurs. This preliminary action allows the system to pre-determine which files require synchronization and to which devices, reducing the processing burden during actual synchronization operations and scaling efficiently with the number of nodes.
2Reliability
If all potential files are examined for synchronization across all devices, then complete file synchronization is achieved, but processing time and computational resources increase
Solution Approach 1:
The patent segments the file synchronization process into distinct categories: established files (which have undergone qualifying trigger actions) and unestablished files. This segmentation allows the system to focus processing only on established files that require synchronization, rather than examining all potential files across all devices, thereby reducing processing time while maintaining synchronization completeness.
Solution Approach 2:
The system performs partial action by synchronizing only the subset of files that have undergone qualifying trigger actions (established files) rather than all files. This selective approach maintains synchronization reliability for files that actually need updating while significantly reducing the processing time and computational resources required.
3Measurement precision
If timestamp comparison processing is performed on all potential files, then file version determination accuracy is improved, but data storage and processing demands increase exponentially
Solution Approach 1:
The patent extracts only the necessary timestamp information associated with qualifying trigger actions for each file, storing this minimal metadata in a synchronization database rather than performing full timestamp comparisons on all file contents. This extraction approach maintains version determination accuracy while reducing data processing complexity and storage requirements.
Solution Approach 2:
The system performs preliminary classification of files based on qualifying trigger actions and their associated timestamps before synchronization operations. This preliminary action organizes files into established and unestablished categories, allowing the system to determine version requirements in advance and reducing the complexity of real-time timestamp comparisons across all files during synchronization.
4Adaptability or versatility
If file synchronization is performed on all devices regardless of eligibility, then universal file availability is achieved, but unintended or undesirable synchronization occurs
Solution Approach 1:
The patent applies local quality by classifying devices into different groups with different synchronization eligibility based on their roles and characteristics in the industrial control system. The system determines which devices are eligible to receive synchronized files based on their specific functions and requirements, ensuring that file synchronization is appropriate and desirable for each local context rather than applying a universal approach, thereby preventing unintended synchronization while maintaining necessary file availability.
Data Source
AI summary
Unique systems, methods, techniques and apparatuses of industrial control system file synchronization are disclosed herein. One exemplary embodiment is an industrial control system comprising an industrial controller and a first and second computing device. The second computing device includes a second non-transitory memory device structured to store both a file set and synchronization instructions, and includes a processing device configured to execute the synchronization instructions so as to classify a subset of files from the second file set by identifying files transferred to the second computing device from the industrial controller, classify a sub-subset of files from the subset of file using a set of synchronization rules, classify a set of synchronization files from the sub-subset of files, and transfer the set of synchronization files from the second computing device to the first computing device.