Service Linkage Assistance Device for Stateful API Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing techniques are inadequate for developing adapters that support stateful APIs, as they are costly and time-consuming to create, and cannot facilitate linkage between services that expose stateful APIs and other services.

Innovation Solution

A service linkage assistance device and method that includes an executing unit to interpret and execute stateful APIs, storing dynamic information, and exposing a stateless API to facilitate linkage between stateful and stateless services, allowing for easier development and integration of adapters for stateful APIs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing adapter development techniques are used for stateful APIs, then development cost and time increase significantly, but the ability to support stateful services is lost

Engineering Contradiction:
Improveability to support stateful APIsVSAvoidadapter development time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces an intermediary component that sits between the service linkage device and the stateful service. This intermediary handles the stateful API calls and manages session information, allowing the adapter to work with stateful services without requiring complex custom development. The intermediary translates stateful service interactions into a standardized format that adapters can handle efficiently.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the adapter development into modular components: a standard adapter framework that handles common stateful service patterns, and configurable modules that can be customized for specific services. This segmentation allows developers to reuse proven patterns while only customizing the necessary portions, significantly reducing development time and complexity.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If existing adapter development techniques are used for stateful APIs, then development cost increases, but the ability to support stateful services is lost

Engineering Contradiction:
Improveability to support stateful APIsVSAvoidadapter development ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal adapter framework that can handle multiple types of stateful services through a common interface and standardized patterns. This multi-functionality allows a single adapter implementation to work with various stateful services (such as database services, message queues, or session-based services) without requiring separate custom adapters for each service type.

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

Solution Approach 2:

The intermediary component provides a standardized interface between diverse stateful services and the adapter framework, enabling universal handling of different service types through common protocols and patterns.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If stateful services are linked with other services, then service functionality improves, but integration complexity increases

Engineering Contradiction:
Improveservice linkage capabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The intermediary acts as a mediation layer between stateful services and other services in the linkage network. It handles the complexity of state management, session tracking, and protocol translation, allowing stateful services to be integrated with stateless services and other components without exposing their complexity to the broader system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where the intermediary monitors and manages session state information, providing feedback to the adapter and service linkage device about the current state of connected services. This enables coordinated operation across multiple services while maintaining proper state management.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12086658B2Service cooperation support apparatus, service cooperation support method and service cooperation support program
Publication Date: 2024.09.10 NIPPON TELEGRAPH & TELEPHONE CORP
  • US12086658B2 patent drawing
  • US12086658B2 patent drawing
  • US12086658B2 patent drawing

AI summary

A service linkage assistance device includes an executing unit which accepts a request for a stateless API for a stateful service which exposes a stateful API from a service linkage device which executes a linkage service obtained by linking multiple services including the stateful service, interprets the request, and executes the stateful API and a storage unit which stores dynamic information included in a response from the stateful API, and the stateless API is exposed to the service linkage device by the service linkage assistance device.