Delta Query Support for Backend Database Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database synchronization methods lack efficient delta query support, leading to increased data transfer and processing requirements, especially in mobile applications operating offline and reconnecting to servers, resulting in higher bandwidth usage and storage needs.

Innovation Solution

Implementing a computer-implemented method that automatically generates delta calculation queries based on annotations in database views, using a generic data provider class to identify changed, added, and deleted records since a last data refresh, reducing the need for full data sets to be transferred by utilizing delta query support through query templates and annotations like 'delta-token' and 'delta-query-active'.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full data sets are transferred during synchronization, then data completeness is ensured, but bandwidth usage increases and data transfer time extends

Engineering Contradiction:
Improvedata completenessVSAvoidbandwidth usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the changed, added, and deleted records from the full data set and transfers them separately as delta data. This is achieved by implementing delta query support that identifies and retrieves only the specific portions of data that have changed since the last synchronization, rather than transferring entire data sets.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The data transfer process is segmented into two distinct phases: initial full data set transfer and subsequent delta data transfers. The delta data is further segmented into categories (changed records, added records, deleted records) allowing for targeted synchronization that reduces overall bandwidth consumption while maintaining data completeness.

Inventive Principle:
Principle #1Segmentation

2Reliability

If full data sets are transferred during synchronization, then data completeness is ensured, but processing time increases

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

Solution Approach 1:

The system extracts only the necessary delta records (changed, added, deleted) from the full data set and processes them separately. This extraction approach significantly reduces the volume of data that needs to be processed during synchronization, thereby reducing processing time while ensuring that all relevant changes are captured.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary actions by tracking and identifying changed records before synchronization occurs.通过使用annotations和delta-token机制,系统在同步之前就已经确定了需要传输的数据范围,避免了同步时的全量处理,从而减少了处理时间。

Inventive Principle:
Principle #10Preliminary action

3Reliability

If full data sets are stored locally, then data availability is ensured, but storage requirements increase

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts and stores only the delta changes (added, changed, deleted records) in the local database rather than maintaining complete data sets. This approach ensures that the local database contains only the necessary information to reconstruct the current state of data, significantly reducing storage requirements while maintaining data availability.

Inventive Principle:
Principle #2Taking out (Extraction)

4Loss of energy

If delta query support is implemented, then data transfer is minimized, but system complexity increases

Engineering Contradiction:
Improvebandwidth usageVSAvoidsystem complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent implements a universal delta query support mechanism that can be applied to multiple data sets and synchronization scenarios through a generic data provider class. This multi-functional approach allows the same delta query infrastructure to serve various data synchronization needs, reducing overall system complexity compared to implementing separate solutions for each data set.

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

Solution Approach 2:

The system introduces an intermediary layer (delta query support mechanism with annotations and query templates) that sits between the data source and the synchronization process. This intermediary automatically generates the appropriate queries to retrieve delta data, simplifying the overall system architecture by centralizing the delta query logic rather than scattering it throughout the codebase.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10621388B2Automatic delta query support for backend databases
Publication Date: 2020.04.14 SAP SE
  • US10621388B2 patent drawing
  • US10621388B2 patent drawing
  • US10621388B2 patent drawing

AI summary

The present disclosure involves systems, software, and computer implemented methods for automatically providing delta query support for backend databases. One example method includes identifying annotations for a data set. The annotations indicate data fields of the data set to be used for a delta calculation. A request for a delta calculation is received for the data set. A set of delta calculation queries are automatically generated based on the annotations and a set of query templates in response to the request for the delta calculation. The set of delta calculation queries are executed to generate a delta calculation result. The automatically generated delta calculation result is provided in response to the request for the delta calculation.