Offline Sync Protocol Using UI Action Replay for Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Synchronization errors occur when data is modified offline on a client device and later synced with a remote computing system, often due to conflicts between local and remote versions, especially when users make changes that are inconsistent with the remote version.

Innovation Solution

A synchronization protocol that records UI manipulation actions on the client device during offline mode, allowing these actions to be sent to the remote system for replay, where errors are detected and notifications are sent back to the client for resolution, with error messages displayed in the context of the original UI screens.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is modified offline on a client device and later synchronized with a remote computing system, then offline productivity is improved, but synchronization errors occur due to conflicts between local and remote versions

Engineering Contradiction:
Improveoffline productivityVSAvoidsynchronization reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by recording UI manipulation actions locally during offline mode before synchronization occurs. This allows the client device to maintain productivity while preparing data for later synchronization, reducing conflicts by capturing the exact sequence of user interactions rather than just data states

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The synchronization system implements feedback by detecting conflicts between local and remote data versions, then presenting resolution options to the user. The system provides feedback about synchronization status and enables users to resolve conflicts by selecting which version to keep or merging changes, thereby maintaining reliability while preserving offline productivity

Inventive Principle:
Principle #23Feedback

2Reliability

If synchronization errors are detected and resolved, then data consistency is improved, but additional network data transfer and processing time are required

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system extracts only the UI manipulation actions that caused synchronization conflicts for separate processing and user review. By taking out only the problematic portions rather than retransmitting entire data sets, the system minimizes network data transfer while still achieving data consistency through targeted conflict resolution

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary detection of synchronization conflicts before full synchronization completes. By identifying and flagging potential conflicts early in the process, the system can prepare resolution options in advance, reducing the overall time required for conflict resolution and maintaining data consistency efficiently

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If a unified synchronization protocol is used for both online and offline interactions, then device complexity is reduced, but handling both modes requires more sophisticated error detection mechanisms

Engineering Contradiction:
Improveprotocol complexityVSAvoiderror detection difficulty
Core Design Contradiction:
Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements a universal synchronization protocol that handles both online and offline interactions through a single unified mechanism. The protocol records UI manipulation actions regardless of connection status, enabling the same synchronization logic to serve multiple modes of operation and reducing overall system complexity while maintaining robust error detection

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The unified protocol incorporates feedback mechanisms that track the state of data objects and UI manipulation actions throughout the synchronization process. By continuously monitoring and comparing local and remote states, the system automatically detects synchronization errors and conflicts, making error detection more manageable despite the sophistication required for unified protocol handling

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12541533B2Data synchronization error resolution
Publication Date: 2026.02.03 SAP SE
  • US12541533B2 patent drawing
  • US12541533B2 patent drawing
  • US12541533B2 patent drawing

AI summary

A synchronization protocol is provided that can be used to resolve synchronization errors encountered while trying to synchronize versions of data objects between a client device and a remote computing system. The protocol includes a client device, in an offline processing mode, handling user interface (“UI”) manipulation actions on one or more UI elements of one or more UI screens. The handling of the UI manipulation actions modifies or creates a local version of a data object stored on the client device. The UI manipulation actions are stored by the client device and sent to the remote computing system. The client device receives a synchronization error notification from the remote computing system. After receiving the notification, the client device displays, in one of the UI screens, the local version of the data object and one or more indications of a synchronization error.