Conflict Resolution Component for Synchronization Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional synchronization systems face conflicts when multiple devices modify the same files, relying on a master-slave approach for conflict resolution, which can be limiting and inefficient, especially for devices with limited processing power.
Innovation Solution
A separate conflict resolution component is introduced, allowing any synchronization party to request resolution independently of the conflicting parties, enabling more dynamic and adaptive policies based on external context information, and allowing devices to outsource conflict resolution to more powerful systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a master-slave approach is used for conflict resolution, then conflict resolution can be implemented, but device autonomy and adaptability are reduced
Solution Approach 1:
The conflict resolution function is segmented from the synchronization components. Instead of having each synchronization component implement its own conflict resolution logic, the system divides the responsibility by creating a separate, dedicated conflict resolution component that handles all conflict resolution operations independently.
Solution Approach 2:
A separate conflict resolution component acts as an intermediary between synchronization components. This mediator receives conflict information from synchronization components, processes the conflicts using advanced resolution policies, and returns resolution decisions to the synchronization components, enabling autonomous conflict resolution without requiring master-slave relationships.
2Reliability
If conventional conflict resolution components are used within synchronization components, then conflict resolution can be performed, but processing power requirements increase for devices with limited capabilities
Solution Approach 1:
The conflict resolution functionality is extracted from the synchronization components and placed in a separate, dedicated component. This extraction allows devices with limited processing power to outsource complex conflict resolution operations to more powerful external systems, while still benefiting from advanced conflict resolution capabilities.
Solution Approach 2:
Instead of requiring each device to implement its own conflict resolution logic, the system uses a centralized conflict resolution component that processes conflicts for multiple devices. This copying approach allows advanced conflict resolution algorithms to be executed once centrally rather than requiring complex local implementations on each device.
3Ease of operation
If synchronization components implement their own conflict resolution logic, then self-sufficiency is achieved, but system complexity increases
Solution Approach 1:
The system merges conflict resolution functionality into a single dedicated component rather than distributing it across multiple synchronization components. This consolidation reduces overall system complexity by eliminating redundant conflict resolution logic while maintaining self-sufficiency through a centralized service architecture.
Data Source
AI summary
The subject disclosure pertains to separation of conflict resolution from a synchronization system or methodology. Upon detection of a synchronization conflict, a request can be generated by a synchronization component and transmitted to a conflict resolution component that is independent and detached from one or more synchronization components. The conflict resolution component resolves the conflict, generates a resolution response, and transmits the responses back to the requesting synchronization component for implementation, among other things.