Database Synchronization Prioritizing Recent Data Records

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database synchronization mechanisms, such as ActiveSync, often prioritize and synchronize older data records first, leading to significant delays when synchronizing large datasets, as users must wait for recent messages to be synchronized after older, less important records are processed.

Innovation Solution

The proposed solution involves generating multiple synchronization requests with incremental filter parameters to prioritize and synchronize recent data records first, using a request generator to initiate synchronization requests with varying depths, and a reconciler to remove redundant data records, ensuring that only non-redundant information is synchronized in subsequent requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If conventional synchronization mechanisms synchronize data records in chronological order (oldest first), then the synchronization process is simple to implement, but the synchronization time is excessively long and recent important messages are not available to users promptly

Engineering Contradiction:
Improvesynchronization timeVSAvoidsynchronization process simplicity
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The patent inverts the conventional chronological synchronization order by prioritizing recent data records over older ones. The system determines a priority based on recency, where more recent messages are assigned higher priority and synchronized first, directly reversing the traditional oldest-first approach to reduce user waiting time for important recent communications

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The synchronization process is segmented into multiple independent phases: determining priority based on recency, selecting data records according to priority, and synchronizing in the determined order. This segmentation allows the system to implement complex priority-based synchronization without overwhelming complexity, as each phase handles a specific aspect of the process

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple synchronization requests with incremental filter parameters are generated to prioritize recent data, then recent messages are synchronized faster, but the device complexity increases due to request generation and reconciliation mechanisms

Engineering Contradiction:
Improvesynchronization efficiencyVSAvoidsynchronization mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by determining the priority order of data records before actual synchronization begins. The request generator pre-calculates which records should be synchronized first based on recency, and the reconciler pre-identifies redundant records, allowing the synchronization process to proceed efficiently without complex real-time decision-making

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The request generator and reconciler act as intermediary components that simplify the overall system architecture. Instead of implementing complex priority-based logic within the core synchronization mechanism, the patent introduces these intermediary layers that handle priority determination and redundancy detection, keeping the main synchronization process simple while achieving high efficiency

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2584479B1Synchronization method and associated apparatus
Publication Date: 2018.07.18 BLACKBERRY LTD
  • EP2584479B1 patent drawingFigure 1
  • EP2584479B1 patent drawingFigure 2
  • EP2584479B1 patent drawingFigure 3

AI summary

An apparatus, and an associated method, facilitates synchronization of a database, such as a message database of a portable device. Synchronization is initiated at the device by the generating and transmitting of a plurality of synchronization requests, with each synchronization request requesting synchronization data of an increased synchronization depth. Synchronization operations are carried out using synchronization data returned responsive to the synchronization requests.