DMVPN Spoke-to-Spoke Communication Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Dynamic Multipoint VPN (DMVPN) systems experience significant tunnel latency reduction after tunnel establishment, causing issues with delay-sensitive network traffic such as IP telephony and real-time applications.
Innovation Solution
The implementation of a DMVPN framework that integrates key management protocols with next hop resolution and unicast routing, eliminating the need for NHRP and incorporating next hop and prefix reachability information into the key management protocol, such as extending the GDOI protocol to enable efficient spoke-to-spoke communication without additional latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional DMVPN establishes a tunnel from spoke to spoke, then direct communication path is created, but tunnel latency reduces significantly after establishment causing problems for delay-sensitive traffic
Solution Approach 1:
The patent applies preliminary action by pre-establishing a hub-spoke tunnel before actual spoke-to-spoke communication is needed. The source spoke encapsulates packets destined for another spoke and sends them through the pre-existing hub-spoke tunnel. The hub then forwards these packets to the destination spoke through its own hub-spoke tunnel. This eliminates the need to establish direct spoke-to-spoke tunnels dynamically, preventing the latency reduction problem that occurs when tunnels are established after traffic begins.
Solution Approach 2:
The patent uses the hub as an intermediary to facilitate spoke-to-spoke communication. Instead of creating direct peer-to-peer tunnels between spokes, all communication passes through the hub which acts as a mediator. The hub receives encapsulated packets from the source spoke, extracts the inner destination address, and forwards the packets to the appropriate destination spoke. This intermediary approach maintains consistent latency characteristics by using pre-established hub-spoke tunnels rather than dynamically creating spoke-to-spoke tunnels.
2Productivity
If DMVPN uses hub to route data between spokes, then scalability is improved over non-fully meshed topology, but all traffic must pass through hub increasing latency
Solution Approach 1:
The patent segments traffic into two types: control plane traffic that passes through the hub for routing decisions, and data plane traffic that can be efficiently forwarded. By maintaining pre-established hub-spoke tunnels with optimized forwarding paths, the system separates the routing function (performed by the hub) from the data forwarding function (performed along pre-optimized paths). This segmentation allows scalable architecture while maintaining low latency for data traffic.
Solution Approach 2:
The patent implements dynamic tunnel establishment based on traffic patterns. While hub-spoke tunnels are pre-established for control plane communication, the system dynamically adapts to traffic demands by using the hub as a flexible intermediary that can establish direct spoke-to-spoke forwarding paths when needed, while maintaining the scalable hub-centric architecture for routing decisions.
Data Source
AI summary
Various embodiments of the disclosed subject matter provide methods and systems for improved efficiency in spoke-to-spoke network communication. Embodiments provide systems and methods for registering a spoke with a hub, updating at least one database with spoke registration information at the hub, and advertising the spoke registration information to other spokes using a single control plane that includes transport security, peer discovery, and unicast routing information.