Server-Based File Version Conflict Resolution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

When multiple users edit the same file from different locations or offline, conflicting versions can be created, leading to challenges in synchronizing the most accurate and preferred version across devices.

Innovation Solution

A server-based system that applies change management rules to determine a preferred modified version of a file among multiple versions, considering source, user, time, quantity, and locality rules, and stores or discards other versions accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple users edit the same file from different locations or offline, then file accessibility and user flexibility are improved, but conflicting versions are created leading to synchronization problems

Engineering Contradiction:

Improvefile accessibilityVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing change management rules before conflicts occur. These rules define the hierarchy and preferences for different file versions, users, and modification types, enabling automatic conflict resolution when multiple users edit files offline or from different locations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The server acts as an intermediary that receives multiple modified versions from different clients, applies change management rules to determine the preferred version, and distributes the resolved version back to clients. This intermediary mechanism reconciles conflicting versions while maintaining data consistency across the network.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If all modified versions are retained for user review, then data loss is prevented, but system complexity and storage requirements increase

Engineering Contradiction:

Improvedata preservationVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system applies local quality by treating different modified versions differently based on their characteristics. The preferred version is selected and distributed to all clients, while non-preferred versions are discarded. This selective approach preserves necessary data while reducing system complexity compared to retaining all versions.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system discards non-preferred modified versions after determining the preferred version through change management rules. This discarding mechanism reduces storage requirements and system complexity while the preferred version is recovered and distributed to ensure data consistency across all clients.

Inventive Principle:

Principle #34Discarding and recovering

3Measurement precision

If manual review of all conflicting versions is required, then accurate version selection is achieved, but time consumption and user workload increase

Engineering Contradiction:

Improveversion selection accuracyVSAvoidsynchronization time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The system implements self-service by automatically determining the preferred version through pre-configured change management rules. The server autonomously compares modified versions, applies the hierarchy rules, and selects the preferred version without requiring manual user review, thereby reducing time consumption while maintaining selection accuracy.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms where change management rules are applied to modified versions, and the determined preferred version is fed back to clients for synchronization. This automated feedback loop eliminates manual review time while ensuring accurate version selection based on the established rules.

Inventive Principle:

Principle #23Feedback

4Adaptability or versatility

If change management rules are made highly configurable, then user preferences are better accommodated, but system complexity increases

Engineering Contradiction:

Improverule configurabilityVSAvoidconfiguration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system achieves universality by designing change management rules that can handle multiple scenarios through a unified framework. The same rule structure accommodates different file types, users, and modification scenarios, providing high configurability without proportionally increasing system complexity through a single versatile rule engine.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9348836B2Determining a preferred modified version from among multiple modified versions for synchronized files

Publication Date: 2016.05.24 DROPBOX INC

AI summary

A server stores files and manages the synchronization of those files across client devices in accordance with user preferences that may be embodied in change management rules. A first version of a file has been designated to be synchronized across at least a first client and a second client. The first client accesses the first version of the file and creates a first modified version of the file, and the second client accesses the first version of the file and creates a second modified version of the file. When the first and second clients attempt to re-synchronize their respective modified versions of the file, the server determines a preferred version from among the available modified versions of the file according to change management rules. Then, the preferred version is stored by the server and is subsequently served for synchronization across the client devices.