VPLS Router Flood Groups for Traffic Loop Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Virtual Private LAN Service (VPLS) networks, the simplistic split horizon rule for managing broadcast traffic can lead to resource inefficiencies and loops, as it lacks flexibility in traffic forwarding policies, particularly in managing traffic between geographically separate L2 networks.

Innovation Solution

The implementation of flood groups, which allow for configurable and selective traffic forwarding based on specific packet characteristics, enabling more controlled and efficient traffic management within VPLS domains by defining policies that determine which interfaces forward L2 packets, thereby preventing unnecessary multicasting and resource consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the split horizon rule is used to prevent traffic loops, then traffic looping is prevented, but traffic flooding control is overly simplistic and lacks flexibility

Engineering Contradiction:
Improvetraffic loop preventionVSAvoidflooding control flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the flooding control mechanism by introducing flood groups that divide interfaces into multiple sets (first set and second set). This allows differentiated flooding behavior for different interface groups, resolving the contradiction by providing both loop prevention through controlled flooding and flexibility through segmented policy application.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different flooding policies to different interface sets. The first set of interfaces uses one flooding policy while the second set uses another policy, allowing localized control optimization that maintains reliability while enhancing adaptability.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If flood groups are implemented to provide selective flooding control, then traffic management flexibility is improved, but device complexity increases

Engineering Contradiction:
Improveflooding control flexibilityVSAvoidflooding mechanism complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The flood group mechanism segments interfaces into manageable sets with distinct flooding policies, making the complexity organized and controllable. This segmentation allows the system to achieve high flexibility while maintaining manageable complexity through structured policy application.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If broadcast traffic is flooded to all customer networks, then LAN simulation is achieved, but network resources are consumed unnecessarily

Engineering Contradiction:
ImproveLAN simulationVSAvoidnetwork resource consumption
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent implements local quality by applying different flooding policies to different interface sets. The first set of interfaces applies standard flooding for LAN simulation, while the second set applies restricted flooding to prevent unnecessary resource consumption, achieving both ease of operation and resource efficiency.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7796593B1Router using internal flood groups for flooding VPLS traffic
Publication Date: 2010.09.14 JUNIPER NETWORKS INC
  • US7796593B1 patent drawing
  • US7796593B1 patent drawing
  • US7796593B1 patent drawing

AI summary

In general, techniques are described for flooding VPLS traffic with a network device according to flood groups. The network device resides within a layer 3 (L3) network and includes a control unit that executes a virtual private LAN service (VPLS) protocol that enables a VPLS domain to operate over the L3 network. The network device further includes a plurality of packet forwarding engines, each of which include a plurality of interface cards that receive a layer 2 (L2) message originating from the L2 network. The packet forwarding engines associate the L2 packet with a configurable flood group, wherein the flood group defines criteria to determine which messages to associate to the flood group and indicates a set of the interface cards for forwarding the associated messages. The packet forwarding engines further flood the L2 packet via each interface card indicated by the associated flood group.