Application State Synchronization Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Applications distributed across multiple devices often experience synchronization conflicts due to discrepancies in state information, such as scoring data or game progress, when users access the same application on different devices, leading to challenges in maintaining consistent user experiences and data integrity.

Innovation Solution

An application synchronization service that employs software libraries to generate and synchronize application state information across devices, using synchronization rules embedded within the data to resolve conflicts automatically, ensuring consistent data storage without developer intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If application state information is synchronized across multiple devices, then user experience consistency is improved, but synchronization conflicts occur due to discrepancies in state information

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization conflicts
Core Design Contradiction:
Stability of the object's compositionVSObject-generated harmful factors

Solution Approach 1:

The patent applies preliminary action by embedding synchronization rules within the saved state data before conflicts occur. These rules predefine how conflicts should be resolved (e.g., selecting highest score, latest timestamp, or specific device priority) so that when synchronization conflicts arise, the resolution mechanism is already in place and can automatically execute without developer intervention or manual conflict resolution processes.

Inventive Principle:
Principle #10Preliminary action

2Extent of automation

If synchronization rules are embedded within saved state data, then conflict resolution automation is improved, but data structure complexity increases

Engineering Contradiction:
Improveconflict resolution automationVSAvoiddata structure complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent merges the synchronization rules directly into the saved state data structure itself. Rather than maintaining separate rule files or configuration databases, the synchronization logic is embedded as fields within the existing state data (e.g., priority indicators, timestamp fields, device identifier hierarchies). This integration reduces the need for additional external components while enabling automated conflict resolution.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If multiple devices access the same application, then user accessibility is improved, but state information discrepancies arise leading to conflicts

Engineering Contradiction:
Improvedevice accessibilityVSAvoidstate information reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies local quality by allowing different devices to have device-specific state information while maintaining overall synchronization through embedded rules. Each device can store and access its own local state data independently, with device-specific identifiers and conditions embedded in the data structure. The synchronization rules then selectively apply different resolution strategies based on the specific device context, conflict type, and local state conditions, enabling both multi-device accessibility and reliable state management.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10474693B2Resolving conflicts within saved state data
Publication Date: 2019.11.12 AMAZON TECH INC
  • US10474693B2 patent drawing
  • US10474693B2 patent drawing
  • US10474693B2 patent drawing

AI summary

Disclosed are various embodiments for synchronizing application state information across devices. More specifically, embodiments of the disclosure are related to resolving conflicts between application state information. A synchronization rule, an event name and/or event value are embedded within application state information obtained from devices associated with a user, from which conflicts can be resolved by an application synchronization service.