Automated API Schema Generation via Network Traffic Inspection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing API systems require manual configuration and intervention to generate API schemas, which is inefficient and prone to errors, especially when dealing with dynamic components in URLs that do not contribute useful information.

Innovation Solution

A method and system that inspect network traffic data to identify and cluster API endpoints by applying a mixed type distance function and recursive schema generation, collapsing dynamic URL components into generic placeholders, thereby automatically generating API schemas without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual configuration and intervention are used to generate API schemas, then the schemas can be customized and controlled, but the process becomes inefficient and error-prone

Engineering Contradiction:
ImproveAPI schema generation efficiencyVSAvoidAPI schema generation accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system automatically generates API schemas by inspecting network traffic data without requiring manual configuration. The schema generation process serves itself by using the traffic data to identify endpoints, parameters, and data structures, eliminating the need for manual intervention while maintaining high accuracy through automated analysis algorithms.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The manual mechanical process of configuring API schemas is replaced with an automated computational system that inspects network traffic, clusters similar requests, and generates schemas algorithmically. This substitution of manual mechanics with automated computational mechanisms resolves the contradiction between efficiency and reliability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If dynamic components in URLs are preserved, then the full URL information is maintained, but the schema generation becomes complex and less reliable

Engineering Contradiction:
ImproveAPI endpoint detection accuracyVSAvoidURL processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts and separates dynamic components from URLs, identifying them as distinct elements that can be handled separately. By taking out the dynamic components (such as user IDs, post IDs, or other variable segments) from the URL structure, the system simplifies the schema generation process while maintaining accurate detection of API endpoints through dedicated dynamic component analysis.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If automated schema generation is implemented, then manual effort is reduced, but the system complexity increases

Engineering Contradiction:
ImproveManual intervention requirementVSAvoidSystem processing complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The automated schema generation system is segmented into distinct functional modules: network traffic data reception, data parsing, clustering analysis, schema generation, and output. Each module handles a specific aspect of the process, making the overall complex system manageable through modular design while maintaining ease of operation through automated execution of each segment.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11388216B2System and method for generating API schemas for networked services
Publication Date: 2022.07.12 F5 NETWORKS INC
  • US11388216B2 patent drawing
  • US11388216B2 patent drawing
  • US11388216B2 patent drawing

AI summary

A method and system for generating an API schema associated with at least one API Endpoint by inspecting network data traffic. Network data requests that have been successfully served by an application associated with at least one API endpoint are examined, parsed and processed to generate an API schema corresponding to the service associated with the at least one API Endpoint.