MPLS Label-Based ECMP Forwarding for Non-IP Traffic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing IP Equal Cost Multiple Path (ECMP) load balancing technique for MPLS traffic is ineffective in handling non-IP traffic, leading to out-of-order packet arrival and excessive jitter, which can cause application failures.

Innovation Solution

A new forwarding equivalence class (FEC) is defined to apply ECMP techniques based on labels within MPLS packets, allowing for load balancing across multiple paths without relying on IP headers, using hash values generated from labels to select the output interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If IP ECMP load balancing technique is used for MPLS traffic, then load balancing across multiple paths is achieved, but non-IP traffic handling deteriorates causing out-of-order packet arrival and excessive jitter

Engineering Contradiction:
Improveload balancing capabilityVSAvoidpacket delivery order
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies different forwarding treatment to different types of traffic by identifying non-IP traffic and directing it through a single path, while allowing IP traffic to use multiple paths for load balancing. This local differentiation resolves the contradiction by optimizing each traffic type according to its specific requirements.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments traffic into IP and non-IP categories, applying different forwarding equivalence class rules to each segment. Non-IP traffic is isolated to single-path forwarding while IP traffic can utilize multi-path load balancing, thus resolving the reliability issue for non-IP traffic while maintaining productivity for IP traffic.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple paths are used for label-switched traffic, then network capacity utilization is improved, but packet ordering deteriorates leading to application failures

Engineering Contradiction:
Improvenetwork capacity utilizationVSAvoidapplication performance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements path selection based on traffic type, allowing multiple paths to be used for IP traffic to maximize capacity utilization, while restricting non-IP traffic to single-path forwarding to ensure reliable delivery ordering. This local quality differentiation resolves the contradiction between productivity and reliability.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent introduces an intermediary classification mechanism that identifies non-IP traffic and applies special forwarding rules. This intermediary layer mediates between the conflicting requirements of multi-path capacity utilization and single-path packet ordering, allowing both to coexist in their respective domains.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2047645B1Technique for multiple path forwarding of label-switched data traffic
Publication Date: 2013.09.11 CISCO TECHNOLOGY INC
  • EP2047645B1 patent drawingFigure 1
  • EP2047645B1 patent drawingFigure 2
  • EP2047645B1 patent drawingFigure 3

AI summary

A technique for multiple path forwarding of label-switched data traffic in a communication network across multiple paths such that traffic associated with a particular label-switched path (LSP) is forwarded on the same path in the network. An incoming label associated with a packet is used to select an Equal Cost Multiple. Path (ECMP) technique that is used to identify an interface among a plurality of interfaces on which the packet may be forwarded. An incoming label associated with the packet is used to identify an outgoing label for the packet as well as the plurality of interfaces on which the packet may be forwarded. A label in the packet's label stack is hashed to produce a hash value. The hash value is then used to identify an interface from the plurality of interfaces on which the packet is forwarded. The outgoing label is placed in the packet and the packet is forwarded on the identified interface.