Cloud Sync Client Conflict Resolution and Notification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file synchronization technologies face challenges in efficiently managing conflicts and real-time notifications across multiple locations and users in web-based collaboration environments, particularly in ensuring that changes made to files on one device are synchronized and notified across all connected devices without data loss or manual merging.

Innovation Solution

A system that includes a sync client on local computers, a sync server, and a notification server, which utilize a rules engine to manage conflicts and provide real-time or near real-time notifications, ensuring that changes made to files on one device are synchronized across all connected devices by identifying and resolving conflicts automatically or prompting users for manual merging.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual conflict merging is required when files are changed at multiple locations, then data accuracy is maintained, but user time and operational complexity increase significantly

Engineering Contradiction:
Improvedata accuracyVSAvoiduser time for manual merging
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs automatic conflict detection and resolution without requiring user intervention. The sync client autonomously identifies conflicts between local and server files, applies resolution rules, and completes synchronization, freeing users from manual merging tasks while maintaining data accuracy through systematic conflict management protocols

Inventive Principle:
Principle #25Self-service

2Productivity

If real-time notifications are implemented across all connected devices, then collaboration efficiency is improved, but network bandwidth and system resources are consumed

Engineering Contradiction:
Improvecollaboration efficiencyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system implements selective notification by sending real-time alerts only when actual file changes occur, rather than continuously broadcasting status updates. The notification server filters and prioritizes change events, transmitting only relevant synchronization notifications to connected devices, thereby reducing network bandwidth consumption while maintaining real-time collaboration awareness

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If continuous synchronization monitoring is performed across all devices, then data consistency is maintained, but processing overhead and energy consumption increase

Engineering Contradiction:
Improvedata consistencyVSAvoidprocessing overhead
Core Design Contradiction:
ReliabilityVSUse of energy by stationary object

Solution Approach 1:

The system employs event-driven periodic monitoring where the sync client checks for file changes at intervals triggered by file system events rather than continuously. When a change is detected, the client initiates synchronization; otherwise, it enters a low-power waiting state, maintaining data consistency through periodic checks while significantly reducing processing overhead and energy consumption compared to continuous monitoring

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9652741B2Desktop application for access and interaction with workspaces in a cloud-based content management system and synchronization mechanisms thereof
Publication Date: 2017.05.16 BOX INC
  • US9652741B2 patent drawing
  • US9652741B2 patent drawing
  • US9652741B2 patent drawing

AI summary

Systems and methods for synchronizing workspaces in a web-based collaboration environment with local folders on computers of collaborators of the workspaces are disclosed. Collaborators of a workspace can edit copies of work items either at the collaboration environment server or at the computer. Updates to all synchronized folders are automatically performed. Conflicts between edits made by different collaborators to the same file are flagged, and a notification is sent to the author attempting to make edits to a version of a file that has already been updated by another collaborator.