WAN Edge Device Tunneling for Layer 2 Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional WAN architectures face challenges such as insufficient bandwidth, high bandwidth costs, application downtime, poor SaaS performance, complex operations, and difficulty in securing networks due to their limitations in providing high availability and extensibility, especially when WAN edge devices lack Layer 2 connectivity.
Innovation Solution
The implementation of a method that configures WAN interfaces on edge devices to connect to transport networks, establishes tunnels between them, and routes specific classes of WAN traffic, even when there is no Layer 2 connectivity, using techniques like Generic Routing Encapsulation (GRE) and extended MPLS or Internet interfaces, enabling high availability and extensibility across transport networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional WAN architectures use MPLS transports or MPLS paired with Internet/LTE links in active/backup fashion, then network connectivity is provided, but bandwidth costs are high and scalability is limited
Solution Approach 1:
The patent enables WAN edge devices to perform multiple functions by allowing them to connect to multiple transport networks simultaneously and dynamically select paths. The system provides both active-active redundancy and cloud breakout capabilities through a unified architecture, eliminating the need for separate active/backup configurations.
Solution Approach 2:
The patent implements dynamic path selection where WAN edge devices can automatically switch between different transport networks (MPLS, Internet, LTE) based on real-time conditions. The active/backup configuration can dynamically transition to active-active operation, and cloud breakout paths can be dynamically activated when needed.
2Reliability
If MPLS paired with Internet/LTE links are used in active/backup fashion, then network connectivity is maintained, but application downtime occurs during failover
Solution Approach 1:
The patent pre-establishes multiple transport network connections and configures failover policies in advance. When a primary connection fails, the system has pre-configured backup paths ready for immediate activation, significantly reducing failover time and application downtime.
Solution Approach 2:
The system implements real-time monitoring of transport network conditions and dynamically switches traffic paths based on current status. This dynamic approach allows for seamless failover with minimal disruption to applications, as the system can proactively move traffic before complete connection failure occurs.
3Ease of operation
If WAN edge devices are configured with traditional routing, then Layer 2 connectivity is required, but extensibility and high availability are limited when Layer 2 connectivity is absent
Solution Approach 1:
The patent introduces a tunneling mechanism (GRE, IPsec, or MPLS) as an intermediary between WAN edge devices that lack Layer 2 connectivity. This tunneling layer encapsulates traffic and provides Layer 2-like functionality over Layer 3 networks, enabling high availability without requiring direct Layer 2 connectivity between edge devices.
Solution Approach 2:
The patent transitions from traditional Layer 2 routing to a multi-dimensional approach combining Layer 3 routing with tunneling protocols. This dimensional shift allows the system to achieve Layer 2 connectivity effects through Layer 3 infrastructure, enabling high availability across geographically distributed sites without direct Layer 2 links.
4Productivity
If cloud breakout is implemented at centralized data centers, then traffic consolidation is achieved, but SaaS performance deteriorates and deployment complexity increases
Solution Approach 1:
The patent enables cloud breakout functionality at distributed WAN edge locations rather than requiring all traffic to be backhauled to centralized data centers. This local breakout capability allows SaaS traffic to be directly routed to cloud service providers from branch offices, improving SaaS performance by reducing latency and bandwidth consumption on backhaul links.
Solution Approach 2:
The patent segments traffic flows by destination and type, allowing SaaS traffic to be routed directly to cloud providers while other traffic continues to flow through centralized data centers. This segmentation enables optimized paths for different traffic types, maintaining traffic consolidation benefits for non-SaaS traffic while improving SaaS performance through direct routing.
Data Source
AI summary
A WAN controller can configure a first WAN interface on a first WAN edge device to connect to a first transport network. The WAN controller can configure a second WAN interface on a second WAN edge device to connect to a second transport network. The WAN controller or the first WAN edge device, connected to a first access device of an access network, can determine the first WAN edge device has no Layer 2 connectivity to the second WAN edge device, connected to a second access device of the access network. The WAN controller or the first WAN edge device can establish a tunnel between the first WAN edge device and the second WAN interface. The WAN controller can route a specified class of WAN traffic received by the first WAN edge device from the access network through the tunnel.