Composite API Engine for Network Service Interface Bundling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network service interfaces require clients to call multiple disparate APIs to access various network resources, leading to inefficiencies due to differences in API formats, conventions, and asynchronous processing, which complicates service integration and data compatibility.

Innovation Solution

A composite engine generates a customizable one-point interface (composite API) that sits between clients and multiple network APIs, allowing seamless interaction while preserving client conventions and existing services by translating API requests and responses across different formats and conventions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If clients call multiple disparate APIs to access network resources, then clients can access various network services, but the complexity of service integration increases due to differences in API formats and conventions

Engineering Contradiction:
Improveaccess to network servicesVSAvoidservice integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a gateway as an intermediary component that sits between clients and multiple network services. This gateway translates and mediates between different API formats and conventions, allowing clients to access various network services through a unified interface without directly dealing with the complexity of multiple disparate APIs.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway is designed with multi-functional capabilities to handle multiple different API formats, conventions, and network services through a single unified interface. This universal approach allows the system to maintain adaptability to various services while reducing integration complexity by providing a common access point.

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

2Adaptability or versatility

If clients call multiple disparate APIs with different formats and conventions, then clients can access specific network resources, but the difficulty of service integration increases

Engineering Contradiction:
ImproveAPI access capabilityVSAvoidservice integration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The gateway serves as a mediating layer that handles the translation between different API formats and conventions. This intermediary approach preserves the ability to access specific network resources through their native APIs while making service integration easier by providing a standardized interface that abstracts away the format differences.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If clients handle asynchronous processing across multiple APIs, then clients can access network services, but the complexity of coordination increases

Engineering Contradiction:
Improveservice access efficiencyVSAvoidcoordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The gateway acts as an intermediary that manages asynchronous processing coordination between multiple APIs. It handles the complexity of timing, sequencing, and synchronization of asynchronous operations, allowing clients to access network services efficiently without directly managing the coordination complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway implements feedback mechanisms to track and coordinate asynchronous processing across multiple APIs. By monitoring the state of ongoing operations and providing feedback loops, the system can efficiently manage service access while reducing coordination complexity through automated state management and response aggregation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11785116B2Systems and methods for use in network service interface bundling
Publication Date: 2023.10.10 MASTERCARD INT INC
  • US11785116B2 patent drawing
  • US11785116B2 patent drawing
  • US11785116B2 patent drawing

AI summary

Systems and methods for use in facilitating application interface (API) interactions are disclosed. One exemplary method includes receiving, by a computing device, a primary API request from a client. The primary API request includes a plurality of parameters in association with a plurality of values. The computing device identifies relationships between the parameters and a plurality of interfaces, and generates a plurality of secondary requests based on the primary API request and the identified relationships. The computing device further transmits each of the plurality of secondary requests to the plurality of interfaces and receives a plurality of secondary responses from the plurality of interfaces. The computing device then generates a primary response based on the secondary responses and transmits the primary response to the client.