Network API Gateway Credential Translation for Edge Computing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service providers face challenges in managing interactions between cloud applications and multi-access edge computing (MEC) networks due to the use of different protocols by various operator APIs, requiring developers to learn and manage multiple protocols and credentials.
Innovation Solution
A network API gateway is implemented to translate requests from cloud applications into calls compatible with different operator APIs, and to manage credentials using a connectivity representation, such as a hierarchical namespace, to authenticate calls across multiple operator networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If developers write requests in a common format, then ease of operation is improved, but device complexity increases due to protocol translation requirements
Solution Approach 1:
The patent introduces an intermediary translation layer between the application layer and operator network layers. This translation layer automatically converts common format requests into operator-specific protocols, eliminating the need for developers to directly handle multiple protocol variants while managing the complexity internally.
Solution Approach 2:
The system implements a universal request format that can be translated to support multiple operator networks simultaneously. The translation service provides multi-functionality by handling different operator protocols through a single unified interface, allowing one application codebase to work across multiple networks.
2Reliability
If separate credentials are managed for each operator network, then reliability is improved through proper authentication, but device complexity and time consumption increase
Solution Approach 1:
The patent implements a universal credential management mechanism that handles authentication for multiple operator networks through a single standardized process. The translation service automatically selects and applies appropriate credentials based on the target operator network, eliminating the need for developers to manually manage separate credential sets for each network.
Solution Approach 2:
The system performs self-service credential management where the translation service automatically handles credential selection, validation, and application without developer intervention. The service monitors network conditions and automatically manages authentication tokens, reducing both complexity and time consumption while maintaining reliable authentication.
3Adaptability or versatility
If multiple protocols are learned and managed, then adaptability is improved for different operator networks, but ease of operation deteriorates due to increased learning burden
Solution Approach 1:
The translation service acts as an intermediary that absorbs the complexity of multiple operator protocols. Developers interact only with the simplified common format through the application layer, while the translation intermediary handles the protocol conversion to various operator-specific formats, maintaining adaptability without increasing operational complexity.
Solution Approach 2:
The system segments the complexity by separating the application layer (simple common format) from the network layer (multiple operator protocols). The translation service operates as an independent layer that manages protocol diversity, allowing developers to write code once in the simple format while the system adapts to different operator networks automatically.
Data Source
AI summary
The system disclosed herein is composed of a network API gateway that is configured to assign credentials to a call to an operator network. The call is initiated based on a request received from an application. The credentials are used by an operator API to authenticate the call. The network API gateway creates and uses a connectivity representation as a basis for assigning the credentials to the call. The credentials are generated by the application making the request and the credentials are passed to the network API gateway as part of a translation session (e.g., five minute time interval) during which the network API gateway translates requests for the application. Consequently, each request sent by the application to the network API gateway during the translation session no longer needs its own credentials, and thus, the developer is released from the requirement of managing credentials for each request.