Unified API Generation and Consumption Channel

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for creating and consuming RESTful APIs are burdensome, requiring developers to navigate multiple interfaces and manage credentials, leading to complex and inefficient processes.

Innovation Solution

The implementation of an API Generation and Consumption (AGC) module that allows clients to create and access resources through a single channel, using RESTful API requests, eliminating the need for separate interfaces and simplifying the process of defining and utilizing resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional methods are used for creating and consuming RESTful APIs, then developers can access web service functionality, but the process becomes complex and inefficient due to multiple interfaces and credential management

Engineering Contradiction:
ImproveAPI creation and consumption processVSAvoidSystem interface complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent combines the API creation interface and API consumption interface into a single unified interface. This allows developers to both define new resources (which creates APIs) and consume existing resources through the same channel, eliminating the need to switch between multiple interfaces and manage separate credentials for each.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The single interface is designed to perform multiple functions: it can create new resources (API generation), access existing resources (API consumption), and manage authentication credentials all in one place. This multi-functional design simplifies the developer experience by providing a universal access point for all API-related operations.

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

2Productivity

If separate interfaces are used for API creation and consumption, then specific functions can be specialized, but the overall process becomes more complex and time-consuming

Engineering Contradiction:
ImproveAPI development efficiencyVSAvoidTime for navigating multiple interfaces
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

By merging the creation and consumption operations into a single interface, the patent eliminates the time developers would otherwise spend navigating between separate interfaces. The unified interface allows seamless transition between creating resources and consuming them, significantly reducing the time loss associated with interface switching and credential management.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If multiple interfaces and credentials are required, then security can be managed separately for each interface, but the burden on developers increases

Engineering Contradiction:
ImproveSecurity managementVSAvoidCredential management burden
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The single interface implements universal authentication that works for both resource creation and resource consumption operations. Instead of requiring separate credentials for different interfaces, the system provides a unified authentication mechanism that secures all operations through one interface, maintaining security while dramatically reducing the operational burden on developers.

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

Data Source

PatentUS9851952B2Seamless restful API generation and consumption through a single channel
Publication Date: 2017.12.26 ORACLE INT CORP
  • US9851952B2 patent drawing
  • US9851952B2 patent drawing
  • US9851952B2 patent drawing

AI summary

Techniques are disclosed for enabling seamless RESTful API generation and consumption through a single channel. Certain techniques are disclosed that allow for clients to both create an API and then immediately use or consume the API through a single channel of communication with a single component, such as a series of HTTP requests and/or responses sent between an application and an API Generation and Consumption (AGC) module.