Delta Querying System for Mobile Data Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software complexity and changing requirements in product cycles and delivery modes necessitate efficient data management and synchronization across different platforms, particularly for mobile applications, to enhance performance and reduce communication latency.

Innovation Solution

The implementation of a delta querying system that uses delta tokens to fetch only updated data, rather than the entire dataset, through a custom expand service configuration, which includes a connection server and a development platform, to provide enhanced data services for mobile applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire dataset is fetched from the back-end application server, then data completeness is ensured, but communication latency and data transfer time increase

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

Solution Approach 1:

The patent segments data retrieval into two modes: full dataset fetch for initial loading or historical data, and delta queries for updates. The delta query mechanism segments only the changed portions of data since the last synchronization, reducing transfer size while maintaining completeness of updated information.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by establishing a baseline of previously fetched data and tracking changes since then. The delta token mechanism prepares and stores metadata about data versions, enabling the system to pre-determine what data needs to be transferred without actually transferring the entire dataset.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If customized expand services are implemented with delta querying, then data management efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvedata management efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a connection server as an intermediary component between the mobile application and the back-end application server. This intermediary handles the complexity of delta token generation, data change detection, and selective data retrieval, shielding the mobile application from direct system complexity while maintaining high data management efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The connection server implements a universal service that handles multiple data retrieval scenarios (initial load, updates, deletions) through a single delta query mechanism. This multi-functional approach consolidates complexity into one service layer while providing efficient data management across different use cases.

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

3Loss of substance

If delta tokens are used to track data changes, then data transfer volume is reduced, but measurement and tracking complexity increases

Engineering Contradiction:
Improvedata transfer volumeVSAvoidchange detection complexity
Core Design Contradiction:
Loss of substanceVSDifficulty of detecting and measuring

Solution Approach 1:

The patent uses delta tokens as parameter identifiers that encode information about data version and change status. By changing the parameter representation from full data payloads to compact delta tokens, the system reduces data transfer volume while the connection server handles the complexity of interpreting these parameters and detecting actual data changes.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10938797B2Customized expand data services supporting delta querying
Publication Date: 2021.03.02 SAP SE
  • US10938797B2 patent drawing
  • US10938797B2 patent drawing
  • US10938797B2 patent drawing

AI summary

An application is developed and built through a development platform. The application provides a user interface to serve user requests. The application provides expanded set of data entities stored at a back-end application. The application communicates with the development platform to request data from the back-end application. The development platform communicates with the back-end application through sending and receiving communication messages with a connection server. The expand data services are implemented on the connection server to access and provide data associated with a requested data entity. The provided data expand services are also serving delta data requests associated with updates on the back-end application. The delta data is related to a previous data download request at the back-end application. The provided data expand services, which support delta data querying, are utilized during initial data loading of the application.