Embedding Hypermedia Resources in Data Interchange Documents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Hypermedia APIs face inefficiencies in providing hypermedia resources to clients, as existing methods do not effectively anticipate and preclude subsequent requests for frequently accessed resources, leading to increased load on servers and slower response times.

Innovation Solution

The technology predicts and embeds hypermedia resources in data interchange format documents based on identified API request patterns, using analysis of client requests to anticipate which resources will be needed, and includes hint data in API requests to optimize resource delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If hypermedia resources are provided on-demand via separate API requests, then clients can access needed resources, but server load increases and response times slow down

Engineering Contradiction:
Improveresponse timeVSAvoidserver load
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system performs preliminary actions by analyzing API request patterns to predict which hypermedia resources will be needed and embedding them in advance within the data interchange format document. This allows clients to access predicted resources without making additional requests, reducing server load and improving response times.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple resource delivery operations into a single API response by embedding predicted hypermedia resources directly within the data interchange format document. This consolidation reduces the number of separate requests and responses, thereby decreasing server load and improving overall system productivity.

Inventive Principle:
Principle #5Merging (Combining)

2Productivity

If hypermedia resources are embedded in data interchange format documents, then subsequent API requests are reduced, but document size and complexity increase

Engineering Contradiction:
ImproveAPI request efficiencyVSAvoiddocument structure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system analyzes API request patterns in advance to predict which hypermedia resources will be needed, then embeds only those specific predicted resources in the data interchange format document. This selective embedding approach reduces unnecessary document bloat while still achieving the goal of reducing subsequent API requests.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies local quality by embedding hypermedia resources selectively based on predicted client needs rather than uniformly embedding all resources. This targeted approach optimizes the balance between reducing API requests and maintaining manageable document size and complexity.

Inventive Principle:
Principle #3Local quality

3Productivity

If API request patterns are analyzed to predict resource needs, then resource delivery is optimized, but processing overhead increases

Engineering Contradiction:
Improveresource delivery optimizationVSAvoidserver processing overhead
Core Design Contradiction:
ProductivityVSUse of energy by stationary object

Solution Approach 1:

The system performs partial analysis of API request patterns by focusing only on the most significant patterns that predict hypermedia resource needs, rather than analyzing all possible request variations. This selective analysis approach achieves resource delivery optimization while minimizing unnecessary processing overhead.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the parameter of analysis depth by adjusting how thoroughly API request patterns are examined based on server conditions and resource types. This dynamic parameter adjustment allows the system to optimize resource delivery while adapting processing overhead to current system state.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10567469B1Embedding hypermedia resources in data interchange format documents
Publication Date: 2020.02.18 AMAZON TECH INC
  • US10567469B1 patent drawing
  • US10567469B1 patent drawing
  • US10567469B1 patent drawing

AI summary

A technology is described for embedding hypermedia resources in data interchange format documents. An example method may include receiving an API (Application Program Interface) request for a hypermedia resource at an API server. The API request may be associated with an API request pattern, where the API request pattern includes API requests for hypermedia resources. A data interchange format document may be generated to include the hypermedia resource requested and at least one of the hypermedia resources associated with the API request pattern may be embedded in the data interchange format document. The data interchange format document may be provided in response to the API request.