Forgotten Items Metadata for Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-replica synchronization systems, challenges arise from replacing newer data with older data due to replication order, inefficient resource allocation, and false conflicts, especially when synchronizing data across multiple devices with limited bandwidth or storage constraints, leading to unnecessary replication operations and data inconsistencies.
Innovation Solution
Implementing 'forgotten items' that can be locally removed without propagating deletions to other endpoints, using metadata to track and manage changes efficiently, and employing filtered replication to ensure only necessary data is synchronized, thereby avoiding conflicts and optimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional replication methods are used to synchronize data across multiple devices, then data consistency is maintained, but unnecessary replication operations occur and communication resources are inefficiently allocated
Solution Approach 1:
The patent extracts the concept of 'forgotten items' from traditional replication systems. These are items that have been deleted locally but are not propagated to other replicas. By separating the deletion propagation mechanism from the replication mechanism, the system avoids unnecessary replication operations while maintaining data consistency, thereby resolving the contradiction between reliability and productivity.
Solution Approach 2:
The system performs preliminary actions by tracking which items have been deleted locally before replication occurs. This allows the replication process to skip items that are marked as forgotten, preventing unnecessary replication operations. The preliminary tracking of deletion status enables efficient replication while maintaining consistency.
2Reliability
If replicas continuously synchronize data to ensure consistency, then data accuracy is maintained, but communication bandwidth is wasted on unnecessary data transfer
Solution Approach 1:
Instead of performing full replication operations continuously, the system applies partial action by only replicating items that have actually changed and are not marked as forgotten. This selective replication approach maintains data accuracy while significantly reducing communication bandwidth usage compared to continuous full synchronization.
Solution Approach 2:
The system uses feedback mechanisms where replicas track which items have been deleted locally and communicate this status to other replicas. This feedback loop allows the replication process to adjust its behavior and skip unnecessary data transfers, optimizing bandwidth usage while maintaining accuracy.
3Reliability
If all data is replicated to ensure complete information availability, then data completeness is achieved, but storage resources are over-utilized
Solution Approach 1:
The patent extracts forgotten items from the replication process. By identifying and excluding forgotten items from replication, the system maintains data completeness for active items while reducing the quantity of data stored and transmitted across replicas, thereby optimizing storage resource utilization.
Solution Approach 2:
The system discards forgotten items from the replication process temporarily, storing only metadata about them. This allows the system to maintain completeness for current data while discarding redundant copies of deleted items, reducing storage requirements. The ability to recover these items if needed maintains completeness when necessary.
Data Source
AI summary
Systems and methods that enable removal of data from an endpoint, while not propagating such removal to other endpoints when synchronizing data sources associated therewith. A designation component can indicate items as forgotten items, wherein such items are being known to an endpoint and deleted therefrom—yet, reintroduced therein and reappearing (e.g., as a create) upon re-synchronizing with the replica over again. Moreover, the forgotten items can employ additional metadata such as in from of an additional bit that indicates whether an item is a forgotten item.