CRDT Data Synchronization for Selective Cross-Device Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data management techniques are inefficient and ineffective, often leading to excessive data duplication, increased query latency, and unnecessary resource consumption due to reactive data processing and frequent updates of views that are not used.

Innovation Solution

Implementing techniques that synchronize only specific data sets between devices using conflict-free replicated data types (CRDTs) and incremental updates, while managing local views based on predefined criteria to optimize data synchronization and reduce unnecessary updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all data is synchronized between devices, then data consistency is improved, but data duplication and network bandwidth consumption increase

Engineering Contradiction:
Improvedata consistencyVSAvoiddata duplication
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments data into multiple versions (e.g., first version and second version) with different synchronization priorities. The first version contains frequently accessed or critical data that is synchronized across devices, while the second version contains less critical data that is updated locally without full synchronization. This segmentation allows the system to maintain data consistency for important information while reducing overall data duplication.

Inventive Principle:
Principle #1Segmentation

2Reliability

If data views are updated frequently, then data freshness is improved, but resource consumption increases

Engineering Contradiction:
Improvedata freshnessVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic update intervals for different data views based on their importance and access patterns. Critical data views are updated more frequently according to a shorter period, while less critical views are updated less frequently. This periodic action with varying intervals maintains data freshness for important information while significantly reducing the overall resource consumption compared to uniform frequent updates of all views.

Inventive Principle:
Principle #19Periodic action

3Reliability

If data synchronization is performed reactively, then data availability is improved, but query latency increases

Engineering Contradiction:
Improvedata availabilityVSAvoidquery latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary data synchronization proactively before queries are requested. Data is synchronized in advance according to predetermined schedules and priorities, so that when a query is made, the data is already available locally without requiring reactive network requests. This preliminary action eliminates query latency while maintaining data availability, as the system has already prepared the data in anticipation of potential queries.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If selective data synchronization is implemented, then resource efficiency is improved, but data consistency complexity increases

Engineering Contradiction:
Improveresource efficiencyVSAvoiddata consistency complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent changes the parameter of data versioning to manage selective synchronization. By assigning different version numbers and synchronization priorities to different data sets, the system can selectively synchronize only certain versions of data to specific devices based on their needs. This parameter-based approach simplifies the consistency management compared to complex conflict resolution protocols, as each data version has clearly defined synchronization rules and priorities.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12405968B2Techniques for managing data
Publication Date: 2025.09.02 APPLE INC
  • US12405968B2 patent drawing
  • US12405968B2 patent drawing
  • US12405968B2 patent drawing

AI summary

Some techniques are described herein for tracking items across different devices. Such techniques synchronize a portion of each item while locally storing another portion. In some examples, the synchronization is performed via a conflict-free replicated data type (CRDT) and includes exchanging state vectors and/or hashes corresponding to portions of items that are being synchronized. Other techniques incrementally update local views of data as new data is received. Such techniques use storage plans that maintain operations for different local views. Other techniques manage the order of updates of different local views of data using various sets of criteria described herein. For example, some views can intentionally be left out of date while other views can be updated more frequently to satisfy requests for such views.