Transit Gateway Routing Table Management for 5G Cloud Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in managing multiple transit gateway routing tables to enable seamless communication between cloud service providers and 5G NR cellular telecommunication networks, particularly in ensuring efficient routing and resilience across distributed architectures.

Innovation Solution

The implementation of a cloud-native 5G network architecture that utilizes AWS Transit Gateways, Direct Connect, and virtual routers to manage routing tables and provide connectivity between Amazon Virtual Private Clouds and on-premises networks, leveraging AWS APIs for automation and infrastructure as code to ensure scalability and resilience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple routing tables are implemented in transit gateways to enable diverse communication paths, then communication flexibility and network resilience are improved, but routing table management complexity increases

Engineering Contradiction:
Improvecommunication flexibilityVSAvoidrouting table management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary system that automatically manages routing table configurations across transit gateways. This intermediary acts as a mediator between network policies and actual routing implementations, handling the complexity of multiple routing tables while presenting a simplified interface to operators. The system automatically propagates routing decisions across multiple gateways, resolving the contradiction by hiding management complexity behind an automated intermediary layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments routing table management into modular, independently configurable units. Each transit gateway maintains its own routing tables that can be independently configured and updated. This segmentation allows flexible management of multiple routing tables without requiring centralized control of the entire routing infrastructure, thereby improving adaptability while keeping management complexity localized and manageable.

Inventive Principle:
Principle #1Segmentation

2Manufacturing precision

If routing tables are manually configured to ensure precise control, then routing accuracy is improved, but configuration time and operational overhead increase

Engineering Contradiction:
Improverouting accuracyVSAvoidconfiguration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring routing templates and policies that can be automatically applied to transit gateways. Instead of manually configuring each routing table from scratch, the system prepares routing configurations in advance as reusable templates, ensuring accuracy while dramatically reducing configuration time. These pre-configured templates maintain precise routing control through validated policies.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables self-service routing configuration through automated systems that can independently generate, validate, and apply routing table configurations. The system performs self-configuration by automatically propagating routing decisions across gateways without requiring manual intervention for each configuration change, thereby maintaining routing accuracy through automated validation while eliminating time-consuming manual configuration processes.

Inventive Principle:
Principle #25Self-service

3Reliability

If transit gateways are distributed across multiple regions to improve network resilience, then fault tolerance is improved, but system complexity and coordination overhead increase

Engineering Contradiction:
Improvenetwork resilienceVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by implementing a standardized transit gateway architecture that can be deployed identically across multiple regions. Each gateway performs the same universal functions and follows the same configuration patterns, enabling distributed deployment for improved resilience while reducing system complexity through consistency. The universal design allows automated management and simplifies coordination between distributed gateways.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent resolves the contradiction by adding a virtualization dimension to the distributed gateway architecture. Instead of managing physical complexity across regions, the system introduces a virtual routing layer that abstracts and unifies the management of distributed gateways. This dimensional shift from physical to virtual management reduces coordination overhead while maintaining the resilience benefits of geographic distribution.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS20230337113A1Managing multiple transit gateway routing tables to implement virtual routing and forwarding functionality
Publication Date: 2023.10.19 BOOST SUBSCRIBERCO LLC
  • US20230337113A1 patent drawing
  • US20230337113A1 patent drawing
  • US20230337113A1 patent drawing

AI summary

Embodiments are directed towards systems and methods for enabling communications between a cloud service provider environment and a fifth-generation New Radio (5G NR) cellular telecommunication network radio access network (RAN). One such method includes: controlling a first virtual private cloud (VPC) in a first region of the cloud service provider environment; providing a first routing table to a first transit gateway of the first region, the first routing table including an entry with a first association identifier that identifies the first VPC and a first Internet Protocol (IP) subnet identifier; providing a second routing table to the first transit gateway, the second routing table including an entry with a second association identifier that identifies a first direct connection router located at first direct connection location and a second subnet identifier; and receiving data transmitted via the first transit gateway and the first direct connection router.