Service Segregation Loopback Interface for Multi-AS Traffic Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for managing services over multi-domain transport networks with multiple Autonomous Systems (ASs) fail to provide end-to-end tunnel connectivity and efficient traffic routing, leading to scalability issues and resource waste, as they cannot effectively bind Virtual Private Networks (VPNs) to specific paths across multiple domains and treat different types of traffic within a single service differently.
Innovation Solution
The method involves defining service segregation loopback interfaces at origin and destination endpoints, binding subsets of traffic to Abstraction and Control of Traffic Engineered Networks (ACTN) Virtual Networks (VNs) by exposing these interfaces as routing next hops, using Routing Policies and Border Gateway Protocol (BGP) signaling to ensure traffic follows specific paths within each Autonomous System (AS), and employing RSVP-TE for tunnel creation, allowing different traffic types to be routed according to their constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing binding mechanisms are used to force VPN traffic to use a particular tunnel in a single AS, then the VPN can be bound to a specific path in that AS, but there is no way to tell the ASBR of a neighbouring AS which tunnel to use, resulting in loss of end-to-end path control in multi-AS networks
Solution Approach 1:
The patent introduces a loopback interface as an intermediary element that is exposed to neighboring ASs. This loopback interface acts as a mediator that carries tunnel identification information, allowing ASBRs in neighboring ASs to identify and follow the correct tunnel path without requiring complex multi-AS tunnel management mechanisms. The loopback interface serves as a simple, universal identifier that bridges the gap between single-AS binding mechanisms and multi-AS path control requirements.
2Adaptability or versatility
If a single VPN is used to carry all traffic types, then service provision is simplified, but different traffic types cannot be routed according to their specific requirements, resulting in inability to meet diverse SLAs
Solution Approach 1:
The patent segments a single VPN into multiple service segregation groups, where each group contains traffic flows with similar requirements. By dividing the VPN traffic into distinct segments (service segregation groups), the system can apply different routing policies and tunnel bindings to each segment, enabling traffic differentiation while maintaining a unified VPN structure. This segmentation approach allows diverse SLAs to be met without creating entirely separate VPNs for each traffic type.
Solution Approach 2:
The patent applies local quality by assigning different routing characteristics and tunnel bindings to different segments of the same VPN based on their specific requirements. Each service segregation group receives tailored routing treatment (e.g., shortest path, minimal delay, high bandwidth) according to its traffic characteristics, while the overall VPN configuration remains relatively simple. This allows differentiated service quality within a unified service structure.
3Adaptability or versatility
If multiple ASs are crossed by VPN traffic, then service coverage is expanded, but there is no single end-to-end tunnel and existing techniques cannot guarantee traffic binding to specific paths in each domain, leading to resource waste and scalability issues
Solution Approach 1:
The patent uses loopback interfaces as intermediaries that are propagated across multiple ASs to maintain tunnel identification information throughout the multi-domain path. These loopback interfaces serve as mediators that allow each AS to independently identify and bind traffic to the correct tunnel segment, enabling efficient resource utilization across diverse administrative domains without requiring a single end-to-end tunnel.
Data Source
AI summary
A method (100) for managing the provision of a service between origin and destination endpoints over a communication network is disclosed. The communication network comprises at least two Autonomous Systems (ASs) and an Abstraction and Control of Traffic Engineered Networks Virtual Network (VN) between the origin and destination endpoints. The method comprises defining, at each of the origin and destination endpoints, a service segregation loopback interface corresponding to a subset of traffic belonging to the service (110). The method further comprises binding the subset of traffic to the VN by exposing the service segregation loopback interface defined at the destination endpoint as routing next hop only to traffic belonging to the subset (120).