Non-hierarchical Sync Scope Mapping for Multi-master Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing hierarchical synchronization solutions are inadequate for non-hierarchical scenarios, particularly in multi-master environments, as they require items to be physically moved or cannot share overlapping sets of items across different synchronization scopes, making it difficult to share data without disrupting existing applications or folder structures.
Innovation Solution
The method extends hierarchical synchronization scopes to non-hierarchical scenarios by mapping different physical organizations to similar logical organizations and using an organization-based synchronization algorithm, allowing items to be added to sync communities without physical movement and enabling sharing across multiple communities while preserving uniqueness and ordering constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If hierarchical synchronization scopes are used in multi-master environments, then data consistency within hierarchical structures is maintained, but non-hierarchical sync scenarios cannot be supported and items cannot be shared across multiple independent scopes
Solution Approach 1:
The patent segments the synchronization scope definition into hierarchical and non-hierarchical components. It introduces independent scope identifiers that can represent either hierarchical folders or flat item sets, allowing the system to handle different sync scenarios separately while using a unified synchronization engine. This segmentation enables versatile sync scope selection without overwhelming system complexity.
Solution Approach 2:
The patent adds a new dimension to synchronization by introducing non-hierarchical scope definitions alongside traditional hierarchical folder-based scopes. Items can now be organized into flat, independent sync scopes that are not bound by folder hierarchies, enabling sharing across multiple scopes without requiring physical movement through hierarchical structures.
2Ease of operation
If items are physically moved to folders to enable synchronization, then items can be included in sync scopes, but existing application behavior and folder structures are disrupted
Solution Approach 1:
The patent creates a logical copy or reference mechanism where items are added to non-hierarchical sync scopes without physical movement. The synchronization system maintains references to items in their original locations while including them in alternative sync scopes, allowing items to be shared across multiple scopes without disrupting their physical folder structure or application behavior.
Solution Approach 2:
The patent introduces an intermediary layer (the non-hierarchical sync scope definition mechanism) that connects items to synchronization without requiring physical reorganization. This intermediary allows items to be included in sync operations while remaining in their original folder locations, thus maintaining folder structure stability while improving ease of operation.
3Adaptability or versatility
If traditional hierarchical synchronization is used, then parent-child ordering constraints are maintained, but items cannot be shared across multiple independent synchronization scopes
Solution Approach 1:
The patent makes the synchronization system universal by enabling it to handle both hierarchical and non-hierarchical sync scopes with a single engine. Items can participate in multiple independent scopes simultaneously, and the system maintains data consistency across all scopes through unified conflict resolution and version management mechanisms, thus achieving multi-scope sharing while preserving reliability.
Data Source
AI summary
Extending hierarchical synchronization (sync) scopes to non-hierarchical scenarios may involve a method for synchronizing differently organized data stores comprising mapping different physical organizations to similar logical organizations and utilizing an organization-based synchronization algorithm to synchronize the differently organized stores. Also, the uniqueness constraints of the organizations may be preserved as well as the parent-child ordering constraints of the organizations.


