REST API Default Identifier Response for Bandwidth Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current REST APIs face inefficiencies due to their default behavior of returning all properties for a resource, leading to excessive memory consumption, network bandwidth usage, and processor load, especially when dealing with resources having numerous large or complex properties.

Innovation Solution

Implementing an unspecified property component that returns only the default identifier property for each instance in response to a request lacking specified properties, and allowing clients to explicitly request specific properties using a property field parameter, while also providing a types-feed component to list all available properties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If REST APIs return all properties for a resource by default, then complete information is provided to clients, but memory consumption, network bandwidth usage, and processor load increase excessively

Engineering Contradiction:
Improvecompleteness of resource informationVSAvoidmemory consumption and network bandwidth usage
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent extracts only the essential identifier property from the full resource data and returns it by default. This selective extraction eliminates unnecessary data transmission while preserving the core function of resource identification, directly resolving the contradiction between information completeness and resource consumption

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of returning all properties (excessive action), the system returns only the minimal necessary identifier property (partial action). This partial response satisfies the basic need for resource identification without the overhead of complete data transmission, addressing the energy loss issue while maintaining functional completeness

Inventive Principle:
Principle #16Partial or excessive action

2Loss of information

If REST APIs return all properties for resources with many large or complex properties, then comprehensive data is available, but processor load and response time increase

Engineering Contradiction:
Improvecompleteness of resource propertiesVSAvoidprocessor load and response time
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The system extracts and returns only the identifier property by default, separating essential identification data from complex resource properties. This extraction dramatically reduces processor load and response time while clients can still access complete properties when explicitly requested

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The response data is segmented into essential identifier information (returned by default) and optional detailed properties (returned only when explicitly requested). This segmentation allows the system to handle basic identification efficiently while providing comprehensive data on demand, resolving the productivity contradiction

Inventive Principle:
Principle #1Segmentation

3Loss of information

If REST APIs return full resource state by default, then clients receive complete information, but network bandwidth consumption increases

Engineering Contradiction:
Improvecompleteness of resource stateVSAvoidnetwork bandwidth usage
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The system extracts and transmits only the identifier property over the network by default, eliminating unnecessary data transmission. Complete resource state information remains available on the server and can be transmitted when explicitly requested, resolving the contradiction between information completeness and network bandwidth usage

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10069938B1Returning identifiers in default query responses
Publication Date: 2018.09.04 EMC IP HLDG CO LLC
  • US10069938B1 patent drawing
  • US10069938B1 patent drawing
  • US10069938B1 patent drawing

AI summary

Examples are generally directed towards managing query responses. A server receives an unspecified property request associated with a resource. The request identifies a resource and omits a property field parameter. A set of instances associated with the resource is identified. An identifier for each instance in the set of instances is identified to form a set of identifiers. The server returns only the set of identifiers to the client as a response to the unspecified property request. On determining the server has received a types-feed request from the client, the server identifies all possible property types for the resource to form a list of all property types. The server returns the list of all property types to the client as a response to the types-feed request.