Local BGP Traffic Routing to Bypass MPLS Core Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud applications experience degraded user experience due to latency-based network architectures that lack direct access to users, resulting in suboptimal traffic routing through MPLS cores.
Innovation Solution
Implement a performance-based routing method that dynamically steers traffic over local connections, bypassing the MPLS core, using local path identifiers and BGP paradigms to ensure lower latency and improved network performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traffic is routed through the MPLS core to provide cloud application access, then users can reach cloud applications, but network latency increases and application performance degrades
Solution Approach 1:
The network path is segmented into two types: traditional MPLS core paths for general traffic, and new direct local paths for latency-sensitive cloud application traffic. This segmentation allows traffic to be routed differently based on application requirements, achieving low latency for cloud apps while maintaining MPLS core routing for other traffic.
Solution Approach 2:
A network intermediary (such as an edge router or gateway) is introduced to intercept cloud application traffic and redirect it through direct local paths instead of the MPLS core. This intermediary enables traffic steering based on destination identification, reducing latency for cloud applications while preserving MPLS core routing for non-cloud traffic.
2Reliability
If a traditional network architecture is used, then cloud applications are accessible, but direct access to users is lacking and user experience is degraded
Solution Approach 1:
The network architecture is extended by adding a new dimensional path (direct local access paths) alongside the traditional MPLS core dimension. This creates a multi-dimensional routing space where cloud application traffic can select the direct local access dimension, providing users with faster, more responsive application performance and improved overall user experience.
3Loss of time
If direct local connections are implemented, then latency is reduced and performance is improved, but network architecture complexity increases
Solution Approach 1:
The routing architecture is made dynamic through the introduction of BGP-based path selection and local path identifiers. Routes are advertised and selected dynamically based on local path availability and performance characteristics, allowing the network to adapt to changing conditions without requiring complex manual configuration or static routing tables.
Solution Approach 2:
The network utilizes BGP path selection parameters and local path identifiers to differentiate between MPLS core paths and direct local paths. By changing routing parameters (such as local preference, AS path, or custom BGP communities), the system enables automated path selection based on performance requirements, reducing the need for complex manual routing configuration.
Data Source
AI summary
Aspects of the subject disclosure may include, for example, selecting between paths for traffic to be routed between a communication device and an application of a cloud service provider, where the selecting is based on receiving or otherwise obtaining a local path identifier (e.g., announced by a local RIB associated with an intra-metro network over which a local path is connected); and routing the traffic between the communication device and the application of the cloud service provider via the local path responsive to the local path identifier, where the local path bypasses or otherwise avoids an MPLS core, and where a non-local path of the paths is over the MPLS core. Other embodiments are disclosed.