Routing Protocol Intermediaries for Cloud Route Table Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telecommunication applications struggle to migrate to cloud computing environments due to differences between traditional dynamic routing information exchange protocols and provider network-specific APIs, requiring frequent and resource-intensive manual updates of route tables.
Innovation Solution
Implementing routing protocol processing intermediaries (RPPIs) within virtualized computing services to translate between dynamic routing protocols and provider network APIs, allowing applications to send reachability information formatted for cloud environments, thereby automating route table updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional dynamic routing protocols are used in cloud computing environments, then applications can exchange routing information using established protocols, but manual updates of route tables are required frequently and consume significant resources
Solution Approach 1:
The patent introduces a routing protocol processor that acts as an intermediary component within the virtualized computing service. This processor receives routing information from applications using traditional dynamic routing protocols, translates it into provider network-specific API formats, and automatically updates route tables. This intermediary eliminates the need for manual route table updates while maintaining compatibility with traditional routing protocols.
2Reliability
If manual updates of route tables are performed frequently, then routing information can be kept current, but computational and resource requirements increase significantly
Solution Approach 1:
The routing protocol processor is configured to automatically perform route table updates without requiring manual intervention. It continuously monitors routing information from applications, processes changes, and updates the route tables autonomously. This self-service mechanism ensures routing information remains current while eliminating the computational overhead and resource consumption associated with manual update processes.
3Extent of automation
If traditional routing protocols are translated to provider network APIs automatically, then route table updates are automated, but routing protocol processing intermediaries are required
Solution Approach 1:
The routing protocol processor is designed as a multi-functional component that handles multiple routing protocols (such as BGP, OSPF, RIP) and translates them to various provider network-specific APIs. By consolidating these translation capabilities into a single universal processor, the system achieves high automation without proportionally increasing complexity, as the same core component serves multiple protocol and API combinations.
Data Source
AI summary
A dynamic routing information exchange protocol session is established between a protocol processing intermediary and an application pipeline function executor running at a virtualized computing service. During the session, the intermediary receives a message indicating reachability information of a pipeline function implemented by the executor, and causes an entry indicating the executor as a destination to be stored in a route table of the service. After the entry is stored, a request for the application function is directed to the executor using the entry.