IoT API Platform Bypassing Gateway for Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT API management systems face performance bottlenecks due to the need for all API calls to pass through a centralized gateway, which can lead to inefficiencies, especially for data-intensive operations.
Innovation Solution
Implementing a distributed service architecture that allows certain API calls to bypass the API gateway by generating tokens with server identifiers, enabling direct routing to specific proxy servers and providing bypass URLs for data-intensive operations, thereby optimizing system performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all API calls pass through a centralized gateway, then security and management are improved, but system performance and latency deteriorate
Solution Approach 1:
The patent segments the centralized gateway into multiple distributed proxy servers, each handling specific API calls independently. This allows data-intensive operations to bypass the central gateway while maintaining security through distributed authentication tokens, thus improving performance while preserving reliability
Solution Approach 2:
The patent introduces authentication tokens as intermediaries that carry server identifiers. These tokens enable clients to establish direct connections to specific proxy servers without going through the central gateway for every operation, reducing latency while maintaining secure authentication
2Adaptability or versatility
If a centralized gateway is used for all operations, then centralized control is improved, but data-intensive operation efficiency deteriorates
Solution Approach 1:
The patent segments control by allowing clients to be assigned to specific proxy servers through tokens, enabling data-intensive operations to be handled by optimized proxy servers directly, while the central gateway maintains overall system control through token issuance and validation
Solution Approach 2:
The patent applies partial bypassing where only data-intensive operations skip the central gateway, while other operations continue to use it. This selective approach maintains centralized control for essential functions while optimizing performance for specific high-priority operations
3Reliability
If API calls route through the API management layer, then security validation is improved, but processing time and latency increase
Solution Approach 1:
The patent performs security validation in advance by issuing authentication tokens before data-intensive operations. These pre-validating tokens contain server identifiers that enable direct routing to specific proxy servers, eliminating the need for repeated validation steps during actual data operations and thus reducing processing time while maintaining security
Data Source
AI summary
A first network device receives a token request from an application and, in response, generates a token that includes a time-stamp and a server identifier. The server identifier indicates a particular proxy server, of a group of proxy servers, in an API management layer. A second network device receives, from an application, an API call that includes the token and validates the token. The second network device routes the API call to the particular proxy server indicated by the token in response to successfully validating the token. The first network device or second network device provides a bypass uniform resource locator (URL), to the application, to bypass the API management layer, for one or more types of designated API calls.