Master Synchronization Engine for Difference Unaware Data Repositories
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional synchronization systems fail to maintain accurate contact information lists due to their inability to track changes in difference unaware information repositories, leading to duplicate entries and missed updates, which results in inefficiencies and losses in personal and business interactions.
Innovation Solution
A system and process that utilizes a master synchronization engine to track changes from both difference aware and unaware repositories, allowing difference unaware repositories to appear as difference aware by determining and exporting only the changes made since the last export, thereby creating an accurate master contact information list.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If conventional synchronization systems export current state data from difference unaware repositories, then the synchronization process is simple, but the master contact information list becomes inaccurate due to duplicates and missed updates
Solution Approach 1:
The system performs preliminary actions by maintaining a local copy of the master contact information list and comparing it with incoming data before synchronization. This allows the system to pre-identify duplicates and changes without requiring complex real-time tracking in difference unaware repositories, thus maintaining simplicity while improving accuracy
Solution Approach 2:
The system implements feedback mechanisms where the master contact information list is continuously updated based on synchronization results. The system compares exported data with the local copy, identifies discrepancies, and adjusts the master list accordingly, creating a feedback loop that maintains accuracy without complicating the basic synchronization process
2Measurement precision
If difference aware applications track changes internally, then contact information accuracy is improved, but device complexity increases
Solution Approach 1:
The system introduces an intermediary mechanism in the synchronization engine that handles the complexity of change tracking. Instead of requiring difference aware applications to implement complex change tracking, the intermediary compares exported data with the local master list copy, abstracting the complexity away from the applications while maintaining accuracy
Solution Approach 2:
The system creates a copy of the master contact information list locally and uses this copy for comparison during synchronization. This copying mechanism allows the system to track changes and maintain accuracy without requiring the applications themselves to implement complex change tracking capabilities, thus reducing application complexity
3Quantity of substance
If the system imports all contact information from difference unaware repositories, then completeness is maintained, but processing time and data volume increase
Solution Approach 1:
The system performs preliminary comparison between the local master list copy and incoming data before full synchronization. This allows the system to pre-identify which records need processing and which can be skipped, reducing processing time while maintaining completeness by ensuring all changes are caught in the comparison
Solution Approach 2:
The system extracts only the necessary information for comparison from the full contact information sets. By focusing the comparison on key identifying fields and changes rather than processing all data fields, the system maintains completeness of contact information while significantly reducing processing time and data volume handled during synchronization
Data Source
AI summary
A system and a method are disclosed for updating a master data list with data from a difference unaware information repository and a difference aware information repository. A master synchronization engine may synchronize to the difference unaware information repository and the difference aware information repository via connectors coupled to each information repository. The difference unaware information repository exports all the data stored within the repository to its respective connector. The connector determines the changes made to the data since the last synchronization and the changes are forwarded to the master synchronization engine. The difference aware information repository is capable of determining the changes made to the stored data since the last synchronization and forwards the changes to its connector. Each connector forwards the changes to the data in their respective information repositories to a database which updates the master data list.