Client-Server Metadata Conflict Resolution via User Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack effective mechanisms to manage data conflicts that arise when multiple users and devices access and modify the same data files, particularly in enterprise information storage and retrieval systems, leading to synchronization challenges across different computing devices.

Innovation Solution

A computer-implemented method that involves clients and servers exchanging metadata entries to identify conflicts, with users selecting conflict resolutions from predefined options, and performing actions based on user choices to resolve these conflicts during the synchronization process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple users and devices access and modify the same data files simultaneously, then data accessibility and collaboration improve, but data conflicts and synchronization complexity increase

Engineering Contradiction:
Improvedata accessibilityVSAvoidsynchronization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the data object into multiple versions (first version on client, second version on server) and processes conflicts between these segmented versions through a structured two-phase synchronization process. This segmentation allows simultaneous access while managing conflicts systematically.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary conflict resolution mechanism that mediates between conflicting versions. The system presents predefined conflict resolution options (keep client version, keep server version, merge) to the user, acting as an intermediary to resolve conflicts without losing data from either source.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If conflict resolution mechanisms are implemented for multi-user access, then data consistency improves, but system complexity and user interaction requirements increase

Engineering Contradiction:
Improvedata consistencyVSAvoidconflict resolution mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by detecting conflicts before final synchronization completes. The two-phase process first identifies conflicts between client and server versions, then presents resolution options to the user before applying the resolution, ensuring data consistency is maintained proactively.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by presenting conflict resolution options to the user and receiving their selection. The system provides feedback about the conflict (showing both versions) and acts on the user's feedback by applying the chosen resolution, creating a closed-loop conflict management system.

Inventive Principle:
Principle #23Feedback

3Productivity

If automatic conflict resolution is implemented, then synchronization speed improves, but risk of data loss increases

Engineering Contradiction:
Improvesynchronization speedVSAvoiddata loss risk
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent enables self-service conflict resolution by presenting predefined options to the user and allowing them to select the appropriate resolution. This self-service approach maintains synchronization speed by avoiding complex automated analysis while preventing data loss through user oversight.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies partial automation by automatically detecting conflicts and presenting standardized resolution options, but requires user action for the final decision. This partial action approach balances automation efficiency with user control, maintaining speed while preventing data loss.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7529780B1Conflict management during data object synchronization between client and server
Publication Date: 2009.05.05 GOOGLE LLC
  • US7529780B1 patent drawing
  • US7529780B1 patent drawing
  • US7529780B1 patent drawing

AI summary

A client stores client metadata entries corresponding to a plurality of data objects. During a first phase of a synchronization process, the client sends one or more client metadata entries to a server. Each client metadata entry sent corresponds to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process. During a second phase of the synchronization process, the client receives from the server one or more server metadata entries, each having at least one parameter that has changed since a prior execution of the synchronization process. The client identifies any received server metadata entry that conflicts with a corresponding client metadata entry, requests a user to select from among a predefined set of conflict resolutions to resolve the conflict, and the performs an action in accordance with the conflict resolution selected by the user.