API Conversion Device Automates Version Translation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In private cloud and experiment environments, the frequent release of new API versions, such as OpenStack, leads to a mix of version numbers, increasing management costs due to the need for client libraries to absorb API version differences, and existing API Gateway solutions do not adequately reduce these costs.

Innovation Solution

An API conversion device and method that accesses storage units for API definitions, manages version numbers, and converts APIs between different versions by generating a new API conversion program when necessary, using existing API definitions and service provision system information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If client libraries are used to manage API version differences, then API version compatibility is maintained, but management cost increases

Engineering Contradiction:

ImproveAPI version compatibilityVSAvoidmanagement cost

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

An API conversion device is introduced as an intermediary component between the service provision system and external systems. This device automatically converts APIs between different versions (e.g., OpenStack Liberty, Newton, Rocky) based on version information, eliminating the need for multiple client libraries while maintaining compatibility across versions.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically changes API parameters based on version detection. The API conversion device receives API requests, identifies the target version, and automatically adjusts API parameters and structures to match the required version, enabling single-client-library operation across multiple API versions.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If API conversion programs are manually developed, then API version differences are resolved, but development cost and time increase

Engineering Contradiction:

ImproveAPI version conversion capabilityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The API conversion device performs self-service by automatically generating conversion programs using AI technology. When a new API version is detected, the system autonomously creates the necessary conversion logic without requiring manual programmer intervention, significantly reducing development time and effort.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Manual mechanical programming work is replaced with automated AI-based program generation. The system uses machine learning models to analyze API version differences and automatically produce conversion code, substituting the manual mechanical process of writing conversion programs with an intelligent automated system.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If multiple client libraries are maintained for different API versions, then version-specific functionality is preserved, but system complexity increases

Engineering Contradiction:

Improveversion-specific functionalityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A single API conversion device is designed to handle multiple API versions universally. The device can convert between various OpenStack API versions (Liberty, Newton, Rocky, and future versions) using a unified architecture, eliminating the need for separate client libraries for each version while preserving version-specific functionality through intelligent parameter adaptation.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11822982B2API conversion device, Api conversion method, and program

Publication Date: 2023.11.21 NIPPON TELEGRAPH & TELEPHONE CORP

AI summary

In an API conversion device 100, an API conversion unit 140 receives an API conversion instruction from an API-version-number management unit 120, acquires API definitions 21 to 23 and an API conversion program 24 with an API conversion DB access unit 150, converts a received API into a new version number, when the API conversion program was not successfully acquired, extracts a difference between acquired API definitions of new and old version numbers, and, when a new parameter is present in an API definition of the new version number, requests a service provision system 10 to give insufficient information, generates an API conversion program 25 of the new version number based on the insufficient information acquired from the service provision system 10 and the API definitions 21 to 23 of the new and old version numbers acquired from an API conversion DB 20, and converts the received API into the new version number based on the API definitions 21 to 23 and the API conversion program 25.