API Management System Dynamic Communication Scheme Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing API management systems are unable to dynamically select between synchronous and asynchronous communication schemes based on the processing time of API requests, leading to inefficient resource usage and increased development burdens for client applications.

Innovation Solution

An API management system that includes a processor and memory, featuring an API processing time estimation unit to analyze API request information and determine whether to use synchronous or asynchronous communication schemes based on estimated processing times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If an asynchronous communication scheme is used for APIs requiring long processing time, then resource consumption of the client application is reduced, but the program description becomes more complicated and development burden increases

Engineering Contradiction:
Improveresource consumptionVSAvoidprogram description complexity
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent implements dynamic selection of communication schemes (synchronous or asynchronous) based on the estimated processing time of each API. The system adapts the communication mode according to the specific API being called, rather than using a fixed mode for all APIs. This dynamic approach allows the system to optimize resource consumption for long-processing APIs while maintaining simple program descriptions for short-processing APIs.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of communication scheme selection based on the processing time characteristics of each API. By estimating the processing time and comparing it against a threshold, the system selects between synchronous and asynchronous modes, thereby optimizing both resource consumption and program complexity according to the specific API requirements.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If a synchronous communication scheme is used for APIs with short processing time, then the program description remains simple, but client application threads must be continuously secured for waiting

Engineering Contradiction:
Improveprogram description simplicityVSAvoidthread waiting time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system dynamically selects between synchronous and asynchronous communication schemes based on the estimated processing time of each API. For APIs with short processing times, the synchronous scheme is selected to maintain program simplicity, while for long-processing APIs, the asynchronous scheme is selected to avoid continuous thread waiting. This dynamic selection resolves the contradiction by adapting to each API's specific characteristics.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The communication scheme parameter is changed based on the processing time threshold. When the estimated processing time exceeds the threshold, the system switches from synchronous to asynchronous mode, thereby reducing thread waiting time while maintaining program simplicity for shorter operations.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If the communication scheme is fixed for each API, then the API management system is simple to operate, but it cannot adapt to varying processing times based on request content

Engineering Contradiction:
ImproveAPI management simplicityVSAvoidprocessing time adaptation
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary estimation of the API processing time before actually executing the API call. By analyzing the API definition information and request parameters in advance, the system can determine the appropriate communication scheme (synchronous or asynchronous) before the API execution begins, thereby adapting to varying processing times while maintaining operational simplicity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The API management system automatically selects the appropriate communication scheme based on the estimated processing time, without requiring manual configuration or complex user input. The system serves itself by making intelligent decisions about communication modes based on the API characteristics and request content, thereby maintaining simplicity while achieving adaptability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240193022A1API management system and API management method
Publication Date: 2024.06.13 HITACHI LTD
  • US20240193022A1 patent drawing
  • US20240193022A1 patent drawing
  • US20240193022A1 patent drawing

AI summary

To determine a communication scheme capable of causing an API to be efficiently executed in accordance with a processing content of the API. An API management system includes an API processing time estimation unit that acquires information of an execution request of an API, estimates a required time required for a predetermined information processing apparatus to execute the API in response to the information of the execution request of the API by analyzing a processing content of the API indicated by the execution request of the API, and determines a communication scheme used for transmitting a request for causing the predetermined information processing apparatus to execute the API to be either synchronous communication or asynchronous communication based on the estimated time.