Paginated Data Transfer with Version-Aware Server Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Retrieving data from a data platform using a single request is challenging due to bandwidth, processing, or time constraints, and ensuring data consistency across multiple requests is difficult, especially when different server devices process the requests and their data may not be synchronized.

Innovation Solution

Implementing paginated data transfer techniques that use version and device identifiers in API calls to route requests to the same server device, ensuring data consistency and reducing the likelihood of incomplete or duplicate data by using device identifiers to maintain communication with the same server and version identifiers to detect data changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is retrieved using multiple requests due to bandwidth, processing, or time constraints, then data can be successfully retrieved, but data consistency across requests cannot be ensured when different server devices process the requests

Engineering Contradiction:

Improvedata retrieval capabilityVSAvoiddata consistency

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by including version identifiers and device identifiers in the initial response to the first request. This allows subsequent requests to carry forward this identification information, enabling the system to proactively route requests to the same server device and maintain data consistency without requiring complex coordination mechanisms during the actual data retrieval process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by having server devices evaluate version identifiers to determine whether requests are associated with different data versions. This feedback mechanism enables dynamic routing decisions, where the system adjusts request routing based on the evaluated version information, ensuring that requests are directed to appropriate server devices that can provide consistent data responses.

Inventive Principle:

Principle #23Feedback

2Productivity

If requests are routed to different server devices to distribute load, then processing capacity is improved, but data version mismatches occur between server devices

Engineering Contradiction:

Improverequest processing capacityVSAvoiddata version alignment

Core Design Contradiction:

ProductivityVSManufacturing precision

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The version identifier acts as an intermediary element that mediates between the requestor device and multiple server devices. By evaluating this intermediary identifier, the system can determine the appropriate server device to handle subsequent requests, ensuring that data version alignment is maintained while still allowing for distributed request processing across multiple server devices when appropriate.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If version identifiers are used to track data changes, then data consistency is improved, but additional processing overhead is introduced

Engineering Contradiction:

Improvedata consistencyVSAvoidprocessing overhead

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service by enabling server devices to automatically evaluate version identifiers and make routing decisions without requiring external coordination or complex validation logic. The server device independently determines whether a request is associated with a different data version and routes accordingly, reducing the need for additional processing overhead from external systems while maintaining data consistency.

Inventive Principle:

Principle #25Self-service

Data Source

PatentEP4708820A1Paginated data transfer techniques

Publication Date: 2026.03.11 MICROSOFT TECHNOLOGY LICENSING LLC

Figure 1
Figure 2A
Figure 2B

AI summary

In examples, a requestor device requests data from a data platform. A response from the data platform may include a version identifier indicating a version of data used to process the request and a device identifier indicating the server device that processed the request. Accordingly, the requestor device may include the version identifier and device identifier in a subsequent request, such that the request is routed to the server device accordingly. In examples, the server device may evaluate the version identifier to determine whether the request is associated with a different version of the data, as may occur when the data of the server device has since been updated. Similarly, the requestor device may evaluate a version identifier from the data platform as compared to that of a previously received response to determine whether the response is associated with a different version of data than that of a previous response.