Periodic Offline Data Conflict Resolution Through Staged Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Remote networked systems that periodically disconnect from network access experience data conflicts due to modifications by different users, leading to transaction locking, data inconsistency, and audit issues, which existing technologies struggle to resolve efficiently.

Innovation Solution

A method for resolving data conflicts in periodically offline systems involves detecting conflicts, inserting conflict metadata into a staging data structure, evaluating associated datasets, and selecting a valid data value for synchronization with backend systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of moving object

If remote systems operate periodically offline to maintain continuous functionality, then system availability and operational continuity are improved, but data conflicts arise leading to transaction locking and data inconsistency

Engineering Contradiction:
Improvesystem availabilityVSAvoiddata consistency
Core Design Contradiction:
Duration of action of moving objectVSReliability

Solution Approach 1:

The system segments data conflicts into discrete conflict metadata items that can be individually detected, staged, and resolved. Each conflict is isolated in a conflict staging data structure, allowing systematic processing without blocking entire transactions. This segmentation enables the system to maintain offline operation while managing data consistency through structured conflict handling.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by detecting conflicts and inserting them into a conflict staging data structure before actual data synchronization occurs. This staging area allows the system to prepare conflict resolution strategies in advance, evaluate datasets beforehand, and select valid data values before committing changes, thereby preventing transaction locking and maintaining data consistency during offline operations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If conflicts are resolved by blocking transactions until resolved, then data integrity is maintained, but productivity and processing speed decrease

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs conflict detection and staging as preliminary actions before data synchronization. By identifying conflicts and preparing resolution strategies in advance within the conflict staging data structure, the system avoids transaction blocking during actual data processing. This allows continuous productivity while maintaining data integrity through pre-evaluated conflict resolutions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where conflict metadata items are evaluated against associated datasets to determine valid data values. This feedback loop allows the system to automatically select appropriate data values and synchronize them without requiring transaction blocking, thereby maintaining both data integrity and processing speed through intelligent conflict resolution.

Inventive Principle:
Principle #23Feedback

3Reliability

If manual conflict resolution is implemented, then data consistency can be maintained, but operational complexity and auditing overhead increase

Engineering Contradiction:
Improvedata consistencyVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service conflict resolution by automatically detecting conflicts, staging them in the conflict metadata structure, evaluating associated datasets, and selecting valid data values without requiring manual intervention. This automated process reduces operational complexity and auditing overhead while maintaining data consistency through systematic computer-executed resolution procedures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms to automatically evaluate conflict metadata items against their associated datasets and determine valid data values. This automated feedback loop eliminates the need for manual conflict resolution, reducing operational complexity and auditing overhead while maintaining data consistency through programmatic evaluation and selection of appropriate data values.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12386814B2Data conflict resolution in periodically offline systems
Publication Date: 2025.08.12 SAP SE
  • US12386814B2 patent drawing
  • US12386814B2 patent drawing
  • US12386814B2 patent drawing

AI summary

Computer-readable media, methods, and systems are disclosed for electronic data conflict resolution in periodically offline systems. In response to detecting one or more conflicts on a particular electronic data entity, conflict metadata items associated with the one or more conflicts are inserted into a conflict staging data structure. For each of the conflict metadata items inserted into the conflict staging data structure, the conflict metadata items with their associated datasets are retrieved and evaluated. Based on the conflict evaluation, a valid data value is selected from among the associated datasets. Based on the valid data value, the particular electronic data entity is synchronized to one or more backend systems.