SD-WAN Hub Cluster Route Filtering for Multi-Region Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing routing solutions for large-scale SD-WAN deployments face limitations such as end-to-end visibility loss during overlay to underlay handoffs, constrained maximum supported hops, and manual controller assignment, which hinder scalability and connectivity among SD-WAN nodes across geographical regions.

Innovation Solution

Implementing a distributed, disjoint gateway router model with multi-hop routing support, branch-to-branch VPN, and customizable VPN profiles, along with seamless switching between redundant transit points using route summarization, to enable full-mesh or customizable mesh for redundancy and resiliency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a common controller model is used for route exchanges, then route propagation is simplified, but the maximum supported overlay hops is limited to two, constraining hierarchical deployments

Engineering Contradiction:
Improveroute propagation simplicityVSAvoidmaximum supported overlay hops
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system segments the common controller into multiple distributed gateway routers, each responsible for a specific region or cluster. This segmentation allows routes to be propagated hierarchically across multiple overlay hops while maintaining the simplicity of automated route exchange within each segment. The patent implements this by dividing the network into multiple regions with local gateway routers that independently perform route propagation, enabling deployments with more than two overlay hops.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a spatial dimension to the controller architecture by distributing gateway routers across multiple geographical regions rather than using a single centralized controller. This dimensional change enables hierarchical multi-hop routing while preserving the automated route propagation benefits of the common controller model within each region.

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

2Reliability

If manual assignment of controllers to edges is implemented, then the number of edges connecting to a controller stays within acceptable limits, but deployment complexity increases

Engineering Contradiction:
Improvecontroller edge connection limit complianceVSAvoiddeployment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service by enabling gateway routers to automatically discover and assign themselves to appropriate regions without manual configuration. The distributed gateway model allows each router to autonomously determine its role and connections, eliminating the need for manual controller-to-edge assignment while maintaining acceptable connection limits through automated load distribution.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If distributed disjoint gateway routers are deployed, then scalability is enhanced and multi-hop routing is supported, but system complexity increases

Engineering Contradiction:
Improvescalability and multi-hop routing supportVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the distributed gateway system into independent regional clusters, each managed by a local gateway router. This segmentation enables scalability and multi-hop routing support while containing complexity within manageable regional boundaries, as each segment operates semi-autonomously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The distributed gateway routers are designed with multi-functionality, serving as both local route propagators and inter-region transit points. This universality reduces overall system complexity by eliminating the need for separate specialized components, as each gateway router can handle multiple routing functions across different hierarchical levels.

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

4Reliability

If route summarization is used for switching between redundant transit points, then seamless switching is achieved, but route visibility may be reduced

Engineering Contradiction:
Improveseamless switching between redundant transit pointsVSAvoidroute visibility
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent implements partial route summarization where only certain route attributes are aggregated while others remain detailed. This partial action approach enables seamless switching between redundant transit points through summarization while preserving sufficient route visibility information for proper routing decisions, balancing both requirements.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12587468B2Route filtering for clusters in multi-regional large scale deployments with distributed gateways
Publication Date: 2026.03.24 VELOCLOUD NETWORKS LLC
  • US12587468B2 patent drawing
  • US12587468B2 patent drawing
  • US12587468B2 patent drawing

AI summary

Some embodiments of the invention provide a method for using route filtering to relay routes between members of hub router clusters in an SD-WAN to reduce redundant route notifications to route reflectors (RRs) that advertise routes to hub routers in multiple regions connected by the SD-WAN and multiple edge routers at sites across the multiple regions. The method is performed at a first hub router of a first cluster. From a first edge router at a first site in a first region, the method receives routes of the first edge router. The method distributes the routes of the first edge router to a particular RR directly connected to the first cluster. The method distributes, to each other hub router of the first cluster, the routes of the first edge router along with an identifier that indicates that the routes should not be redistributed to the particular RR.