Selective MPLS Traffic Protection via Label Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
MPLS networks lack a scalable method to offer selective Fast Reroute (FRR) protection for network traffic, making service providers reluctant to provide FRR protection as it either applies to all or none of the customer traffic, which hinders the ability to offer both protected and unprotected services.
Innovation Solution
Implementing a technique where a core node distributes both protected and unprotected labels to source nodes, allowing them to selectively apply FRR protection to traffic by forwarding protected traffic over a backup tunnel and unprotected traffic along a micro loop path until convergence, enabling granular control over service provisioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full PE-PE TE mesh is deployed to provide selective FRR protection, then FRR protection is provided for customer traffic, but the device complexity and scalability deteriorate with the introduction of new PE nodes
Solution Approach 1:
The patent segments the traffic flow into protected and unprotected portions by assigning different labels (first label for protected traffic, second label for unprotected traffic) to different traffic streams. This allows selective FRR protection without requiring a full PE-PE TE mesh for all traffic, thereby reducing device complexity while maintaining reliability for protected traffic.
Solution Approach 2:
The patent applies FRR protection locally to specific traffic flows rather than universally to all traffic. By using label-based identification, the system provides protection only where needed (for traffic marked with the first label) while leaving other traffic (marked with the second label) unprotected, thus avoiding the complexity of a comprehensive mesh architecture.
2Device complexity
If conventional convergence techniques are used for unprotected traffic, then device complexity is reduced, but network resilience deteriorates during failures
Solution Approach 1:
The patent implements a dynamic traffic handling mechanism where the network can adaptively route traffic based on failure conditions. Protected traffic (first label) automatically switches to backup paths during failures, while unprotected traffic (second label) follows conventional convergence. This dynamic approach maintains simplicity for unprotected traffic while providing resilience for protected traffic.
3Reliability
If FRR protection is provided for all customer traffic, then network resilience is improved, but service versatility deteriorates as providers cannot offer both protected and unprotected services
Solution Approach 1:
The patent changes the parameter of traffic identification by introducing label-based classification. Traffic is marked with different labels (first label for protected, second label for unprotected) allowing the network to differentiate and handle traffic differently. This parameter change enables service providers to offer both protected and unprotected services simultaneously, maintaining versatility while improving resilience for protected traffic.
Data Source
AI summary
In one embodiment, a technique enables protection, e.g., Fast Reroute (FRR) protection, for selective traffic in an area of a computer network. A source node, located at an edge or perimeter of a network area or located in the core of the network area, may utilize one of a plurality of labels when forwarding traffic to a destination node, wherein a first label (“a protected label”) indicates that traffic receive FRR protection and a second label (“an unprotected label”) indicates that that traffic not receive FRR protection.