Size-Based Data Synchronization Protocol

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data synchronization methods in mobile landscapes with thousands of users create a network load and increase bandwidth consumption and response time due to the need for multiple network connections for small messages, reducing efficiency and compatibility with offline operations.

Innovation Solution

A size-based data synchronization protocol that isolates data transfer from content interpretation, allowing clients to request a specific payload size, enabling efficient data synchronization by transmitting data in chunks based on requested sizes, reducing the need for optimization based on individual data object sizes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If messages are sent one by one to the client during data synchronization, then data can be transferred reliably, but network load increases and bandwidth consumption increases

Engineering Contradiction:
Improvedata transfer reliabilityVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments data transfer into fixed-size chunks (e.g., 64KB) rather than transmitting individual small messages separately. Multiple data objects are aggregated into single network packets, reducing the total number of connections and messages while maintaining reliable delivery through sequential chunked transfer protocol

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges multiple small data objects into larger aggregated packets for transmission. Instead of sending each message individually, multiple data items are combined into single network communications, reducing network overhead and bandwidth consumption while preserving data integrity

Inventive Principle:
Principle #5Merging (Combining)

2Ease of operation

If one network connection is opened per message per user, then data transfer can be managed simply, but network efficiency decreases and response time increases

Engineering Contradiction:
Improveconnection management simplicityVSAvoidnetwork efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent creates a universal chunked transfer protocol that handles multiple data objects through a single connection framework. The same connection infrastructure is used for transferring varying types and amounts of data, eliminating the need for separate connection management logic for each message while improving network throughput

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

3Manufacturing precision

If data synchronization is performed with many small messages, then individual data objects can be transferred precisely, but the number of connections creates load on the network

Engineering Contradiction:
Improvedata object transfer precisionVSAvoidnumber of network connections
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent segments the transfer process into controlled chunks while aggregating multiple data objects within each chunk. This segmentation approach maintains precise control over data transfer boundaries and integrity while reducing the total number of connections from thousands to a manageable few, lowering network device complexity

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9582561B2Size-based data synchronization
Publication Date: 2017.02.28 SAP SE
  • US9582561B2 patent drawing
  • US9582561B2 patent drawing
  • US9582561B2 patent drawing

AI summary

Data synchronization techniques are provided that effectively isolate data transfer over the network from actual interpretation of data. The data synchronization techniques include a protocol designed to work based on a “size” (amount) of data transferred over the network, irrespective of the content represented by the data that is transferred. The size itself may be determined, for example, by the client, backend system, an agreed-upon configuration that is maintained for a predetermined period of time, etc. In certain embodiments, a client transmits a request to the server that indicates a “requested payload size.” Using the requested payload size, the server generates a response (i.e., one or more messages) that provides the client with data, referred to herein as synchronization data, for storage at the client device.