Cloud API Service Control Plane Data Plane Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based API services face response delays and reduced service quality due to increased API call-related traffic, as both service management and API processing functions are typically implemented on the same network plane, leading to overloaded systems.

Innovation Solution

Implementing a cloud-based API service system where authentication, authorization, and metering functions are managed on a control plane, while API calls are processed on a separate data plane, allowing for increased resources to handle traffic without response delays, and integrating AI-based APIs such as character recognition, text analysis, and image analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If service management and API processing functions are implemented on the same network plane, then system simplicity is maintained, but response delays occur and service quality deteriorates when API call traffic increases

Engineering Contradiction:
Improvesystem structureVSAvoidservice quality
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent divides the cloud-based API service system into two separate network planes: a control plane for service management functions (authentication, authorization, metering) and a data plane for API call processing. This segmentation isolates management traffic from data traffic, preventing congestion in the control plane from affecting API processing performance, thereby maintaining service quality even under high traffic loads.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an API gateway as an intermediary component that receives API calls from users, performs authentication and authorization checks by interacting with control plane services, and forwards validated requests to the data plane for processing. This intermediary role allows the control plane to manage services without directly handling high-volume API traffic, preventing response delays.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If API call traffic increases, then service capacity is improved, but response delays occur for all system functions

Engineering Contradiction:
Improveservice capacityVSAvoidresponse delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

By segmenting the system into control plane and data plane, the patent enables independent scaling of each plane. The data plane can handle increased API call volume without affecting control plane response times, as management functions are isolated on a separate network plane with dedicated resources.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts management functions (authentication, authorization, metering) from the data processing path and places them on a separate control plane. This extraction ensures that high-volume API traffic does not congest the control plane, allowing management operations to respond quickly even under high service capacity conditions.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20240403151A1Cloud-based API service providing system and method
Publication Date: 2024.12.05 SAMSUNG SDS CO LTD
  • US20240403151A1 patent drawing
  • US20240403151A1 patent drawing
  • US20240403151A1 patent drawing

AI summary

There is provided a cloud-based application programming interface (API) service providing system. The system may comprise a cloud management console issuing authentication information for a requested API among a plurality of APIs, an API manager receiving a call message for a specific API, which comprises authentication information, from a user's terminal, performing authentication using the authentication information in the call message, and requesting the execution of the specific API based on the authentication result and an API execution engine generating the result of executing the specific API in response to a request from the API manager, wherein the cloud management console is a module belonging to a control plane, and the call message is received by the API manager belonging to a data plane without via the control plane.