Intelligent API Request Routing via Context Matching

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional systems for routing API requests are inefficient due to the need for multiple API versions and clients to provide specific headers and content, leading to issues with version management and request routing.

Innovation Solution

A system that uses a machine learning model to crawl API servers, capture information, create context objects, and intelligently route incoming API requests based on context matching, automatically generating API versions if needed, without relying on version numbers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional routing techniques (API versioning, custom headers, accept headers) are used to route incoming API requests, then routing functionality is achieved, but system complexity increases and client operation becomes difficult

Engineering Contradiction:

Improveclient operationVSAvoidsystem complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically analyzing incoming API requests and routing them to appropriate API versions without requiring clients to provide version headers or follow complex routing protocols. The intelligent routing system independently determines the correct API version based on request content analysis.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

An intermediary intelligent routing system is introduced between the client and multiple API versions. This mediator automatically analyzes requests and directs them to the appropriate API version, eliminating the need for clients to directly manage version routing complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple versions of APIs are maintained to support different client requirements, then system adaptability improves, but version management complexity increases

Engineering Contradiction:

ImproveAPI version supportVSAvoidversion management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The intelligent routing system provides universal functionality by handling routing for multiple API versions through a single unified mechanism. Instead of requiring separate management processes for each API version, one multi-functional routing system manages all versions.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Version management complexity is extracted from the client-side requirements and consolidated into the server-side intelligent routing system. The routing logic is separated from client operations and centralized in the automated routing mechanism.

Inventive Principle:

Principle #2Taking out (Extraction)

3Measurement precision

If clients provide specific headers and content in certain formats for routing to work, then routing accuracy improves, but ease of operation deteriorates

Engineering Contradiction:

Improverouting accuracyVSAvoidclient operation

Core Design Contradiction:

Measurement precisionVSEase of operation

Solution Approach 1:

The routing approach is inverted: instead of clients providing routing information through headers and following complex formats, the system主动 (proactively) analyzes the request content and determines routing based on what the client naturally sends.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The routing system performs self-service by automatically extracting routing information from the request content itself, eliminating the need for clients to manually format headers or provide routing metadata.

Inventive Principle:

Principle #25Self-service

4Reliability

If API versioning and handshaking protocols are implemented between clients and servers, then routing reliability improves, but system complexity and communication overhead increase

Engineering Contradiction:

Improverouting reliabilityVSAvoidhandshaking protocol

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The handshaking protocol is extracted and eliminated. The intelligent routing system directly analyzes requests and routes them without requiring preliminary version negotiation or handshaking exchanges between client and server.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system skips the traditional handshaking step by directly routing requests based on content analysis. Instead of going through version negotiation protocols, the routing decision is made immediately upon receiving the request.

Inventive Principle:

Principle #21Skipping (Rushing through)

Data Source

PatentUS10831566B1Electronic system for intelligent processing and routing of incoming API requests based on context matching

Publication Date: 2020.11.10 BANK OF AMERICA CORP

AI summary

An electronic system is typically configured for crawling, via a machine learning model, into one or more API servers, wherein the one or more API servers comprise one or more versions of one or more APIs, capturing, via the machine learning model, information associated with the one or more versions of the one or more APIs, creating context objects associated with each of the one or more versions of the one or more APIs, receiving a real-time API request from a client system, processing the real-time API request received from the client system, and routing the real-time API request to an API version of the one or more versions.