Result State Tokens for Multi-Interface Pagination Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based infrastructure and distributed systems face challenges in aggregating and paginating results from multiple programmatic interfaces, which can lead to failure scenarios, permission issues, and varying pagination schemes, affecting data retrieval and user experience.

Innovation Solution

Implementing result state tokens to track pagination and failure states across different programmatic interfaces, allowing for selective service integration and retry management, thereby ensuring data aggregation and user experience are not impacted by temporary failures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If results are aggregated from multiple programmatic interfaces, then data completeness is improved, but system complexity increases due to varying pagination schemes and failure scenarios

Engineering Contradiction:
Improvedata completenessVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the aggregation process by creating separate result state tracking for each programmatic interface. Each interface's pagination state, failure state, and completion state are independently tracked using result state tokens, allowing complex multi-interface aggregation to be broken down into manageable independent units that can be handled separately and then combined.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces result state tokens as intermediary objects that mediate between multiple programmatic interfaces and the aggregation logic. These tokens serve as standardized intermediaries that encapsulate interface-specific pagination and failure information, allowing the system to handle diverse interfaces through a unified mechanism without directly managing each interface's complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If pagination is implemented across multiple interfaces, then data retrieval capability is improved, but error handling complexity increases due to different failure scenarios

Engineering Contradiction:
Improvedata retrieval capabilityVSAvoiderror handling complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent changes the state parameters of each interface interaction by tracking pagination tokens, failure states, and completion states as distinct parameters. This allows the system to manage different failure scenarios and pagination states through parameter transitions rather than complex conditional logic, simplifying error handling while maintaining comprehensive data retrieval capability.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If retry mechanisms are implemented for failed services, then reliability is improved, but system stability deteriorates due to retry storms

Engineering Contradiction:
Improveservice reliabilityVSAvoidsystem stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The patent performs preliminary actions by tracking failure states and managing retry logic through result state tokens before actual retries occur. The system pre-establishes which services have failed, their failure states, and appropriate retry strategies, preventing uncontrolled retry storms by having retry mechanisms ready and configured in advance rather than reacting impulsively to failures.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11656972B1Paginating results obtained from separate programmatic interfaces
Publication Date: 2023.05.23 AMAZON TECH INC
  • US11656972B1 patent drawing
  • US11656972B1 patent drawing
  • US11656972B1 patent drawing

AI summary

Results of different programmatic interfaces may be paginated. A request that causes aggregation of results separately returned from different programmatic interfaces may be received. Attempts to obtain the results using the different programmatic interfaces to execute the request may be made. A token that describes result states for the different programmatic interfaces may be included in a response to the request.