Routing Protocol Processing Intermediaries for Cloud Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing telecommunication applications struggle to migrate to cloud computing environments due to the mismatch between traditional dynamic routing information exchange protocols and provider network-specific APIs, requiring frequent manual updates and resource-intensive configuration.

Innovation Solution

Implementing routing protocol processing intermediaries (RPPIs) within virtualized computing services to translate between dynamic routing protocols and provider network APIs, enabling seamless communication and automated route table updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional dynamic routing protocols are used in cloud computing environments, then telecommunication applications can maintain their existing routing mechanisms, but frequent manual updates and resource-intensive configuration are required

Engineering Contradiction:
Improvecompatibility with cloud computing environmentsVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a routing protocol processing intermediary that sits between the application pipeline component and the control plane server. This intermediary translates routing information from dynamic routing protocols into provider network-specific API formats, eliminating the need for manual configuration updates and reducing operational complexity while maintaining compatibility with both traditional routing protocols and cloud computing environments

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If traditional dynamic routing protocols are used in cloud computing environments, then existing telecommunication applications can continue operating, but manual updates and resource-intensive configuration are required

Engineering Contradiction:
Improvecompatibility with cloud computing environmentsVSAvoidtime for manual updates
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The routing protocol processing intermediary automatically performs routing information translation and route table updates without requiring manual intervention. The system self-manages the conversion of routing protocols and dynamically updates route tables, eliminating time-consuming manual update processes while maintaining compatibility with existing telecommunication applications

Inventive Principle:
Principle #25Self-service

3Ease of operation

If routing protocol processing intermediaries are implemented, then automated routing changes and ease of use are improved, but system components and translation processes are added

Engineering Contradiction:
Improveease of use for administratorsVSAvoidnumber of system components
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The routing protocol processing intermediary simplifies administrator operations by providing a unified interface for routing management. Although it adds a system component, it consolidates multiple functions (protocol translation, route table management, API communication) into a single element, making the system easier to operate while the added complexity is hidden from end users

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12407610B1Routing protocol processing intermediaries for cloud computing environments
Publication Date: 2025.09.02 AMAZON TECH INC
  • US12407610B1 patent drawing
  • US12407610B1 patent drawing
  • US12407610B1 patent drawing

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.