Distributed Virtual Traffic Management in Network Elements

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional network element architectures struggle with efficient management of distributed virtual traffic, particularly in multi-function Ethernet aggregation networks, where scalability issues arise due to the lack of device-unique labels and inadequate bandwidth, leading to challenges in protection switching and traffic management.

Innovation Solution

The method involves assigning virtual destination addresses and modifying them to actual addresses for routing within the network element, using virtual local area network (VLAN) ingress and egress connection identifiers for traffic flow classification and policing, and distributing traffic management tasks among multiple traffic managers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional network element architectures are used for traffic management, then device structure is simple, but scalability is poor and bandwidth is inadequate

Engineering Contradiction:
ImprovescalabilityVSAvoiddevice structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The network element is divided into multiple independent Plug-In Units (PIUs), each capable of autonomous traffic management. Each PIU contains its own traffic manager and switching elements, allowing the system to scale by adding or removing PIUs without redesigning the entire device structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical addressing system with virtual destination addresses that add a new dimension to traditional network addressing. This virtual address layer enables scalable routing decisions without increasing the complexity of physical device interconnections.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If device-unique labels are not used for traffic identification, then label management is simple, but traffic classification and protection switching efficiency deteriorate

Engineering Contradiction:
Improvetraffic classification efficiencyVSAvoidlabel management
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Device-unique labels are assigned to traffic flows during the ingress classification stage, before traffic enters the switching fabric. This preliminary labeling enables efficient downstream processing for protection switching and traffic management without requiring complex real-time label generation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces virtual destination addresses as an intermediary layer between traditional MAC addresses and internal switching identifiers. This virtual address system serves as a mediator that simplifies traffic classification while enabling efficient protection switching through standardized label formats.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If bandwidth of individual internal system links is increased, then traffic carrying capacity is improved, but device complexity and resource utilization efficiency worsen

Engineering Contradiction:
ImprovebandwidthVSAvoidinternal link structure
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

Multiple PIUs are connected through a shared backplane infrastructure that aggregates bandwidth resources. Instead of providing dedicated high-bandwidth links between all PIU pairs, the system merges communication paths through the common backplane, achieving high total throughput without proportionally increasing individual link complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The backplane infrastructure serves multiple functions simultaneously: it provides inter-PIU communication, enables protection switching paths, and supports both working and protection traffic. This multi-functionality achieves high bandwidth utilization without requiring separate dedicated structures for each function.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Reliability

If protection switching is implemented with path monitoring, then reliability is improved, but switching speed and resource utilization efficiency worsen

Engineering Contradiction:
Improveprotection switching reliabilityVSAvoidswitching speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

Protection paths are pre-configured and labeled during system initialization and traffic classification stages. When a failure occurs, the switch can immediately activate the pre-labeled protection path without performing complex real-time path computation, achieving both high reliability and fast switching.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Each PIU autonomously monitors its own traffic paths and can independently activate protection switching for local failures. This distributed self-service approach eliminates the need for centralized path monitoring and decision-making, reducing switching latency while maintaining reliable protection.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8477619B2Method and system for distributed virtual traffic management
Publication Date: 2013.07.02 1FINITY INC
  • US8477619B2 patent drawing
  • US8477619B2 patent drawing
  • US8477619B2 patent drawing

AI summary

According to one embodiment, methods and systems may be configured to support client-to-network, network-to-client, and network-to-network flows in a network element including multiple plug-in units. Such support may include policing and shaping flows as aggregates across plug-in units, combining outputs of two upstream traffic managers to network ports on two plug-in units, combining network flows that ingress two plug-in units, and shaping traffic to client ports.