Truncated Data Synchronization Protocol for Client Storage Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in efficiently transferring and synchronizing large volumes of data from remote computing systems to client devices for offline use, particularly due to storage capacity limitations on client devices and the need to access relevant data without complete data sets.

Innovation Solution

A synchronization protocol that retrieves synchronization configuration information from the remote computing system, including truncation criteria and thresholds, to selectively transfer relevant data object instances to the client device, ensuring efficient storage and accessibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete data sets are transferred from remote computing system to client device for offline use, then data accessibility is improved, but storage capacity requirements increase

Engineering Contradiction:
Improvedata accessibilityVSAvoidstorage capacity
Core Design Contradiction:
ReliabilityVSVolume of stationary object

Solution Approach 1:

The patent extracts only the most relevant data object instances from the complete data set based on truncation criteria (recency, frequency, business value) and transfers them to the client device. This selective extraction approach maintains data accessibility for critical information while dramatically reducing the storage capacity required on the client device.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different quality standards to different data objects by evaluating them against truncation criteria. High-priority data objects (recently modified, frequently accessed, high business value) are transferred to the client device with full quality, while lower-priority objects are excluded or transferred with reduced quality, optimizing the balance between accessibility and storage requirements.

Inventive Principle:
Principle #3Local quality

2Volume of stationary object

If selective data transfer is implemented based on truncation criteria, then storage efficiency is improved, but data completeness is reduced

Engineering Contradiction:
Improvestorage efficiencyVSAvoiddata completeness
Core Design Contradiction:
Volume of stationary objectVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where the system continuously monitors data access patterns, modification recency, and business value metrics. This feedback informs the truncation criteria evaluation, ensuring that the most relevant data objects are identified and transferred. The system can adapt to changing data importance over time, maintaining data completeness for critical information while optimizing storage efficiency.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If synchronization protocol transfers all shared data object instances, then data accuracy is improved, but transfer time increases

Engineering Contradiction:
Improvedata accuracyVSAvoidtransfer time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent extracts only the subset of data object instances that meet the truncation criteria (most recent, most frequently accessed, highest business value) rather than transferring all shared data objects. This extraction approach maintains data accuracy for the transferred objects while significantly reducing the total transfer time required to synchronize the client device with the remote computing system.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transferring only the necessary portion of data objects that meet the truncation threshold, rather than performing the excessive action of transferring all shared data objects. This partial transfer approach achieves sufficient data accuracy for offline operations while minimizing transfer time and network bandwidth consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10768794B2Truncated synchronization of data object instances
Publication Date: 2020.09.08 SAP SE
  • US10768794B2 patent drawing
  • US10768794B2 patent drawing
  • US10768794B2 patent drawing

AI summary

A synchronization protocol is used to transfer information from a remote computing system to a client device. At the remote computing system, synchronization configuration information is retrieved. The synchronization configuration includes a synchronization rule specifying a data object schema to which the synchronization rule will apply, truncation criteria, and a truncation threshold. The truncation threshold specifies a maximum amount of shared data object instances of the data object schema that may be sent to the client device during a synchronization task. The remote computing system analyzes metadata of a plurality of shared data object instances of the data object schema. Relevant shared data object instances of the plurality of shared data object instances meeting the truncation criteria are determined by the remote computing system. The relevant data object instances are sent from the remote computing system to the client device until the truncation threshold is met.