L2 Access Node MPLS Data Plane Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

As networks grow in size and complexity, traffic congestion occurs due to approaching maximum bandwidth capacity, leading to inefficiencies in routing and management within service provider networks, particularly in implementing Multi-Protocol Label Switching (MPLS) protocols.

Innovation Solution

Implementing a 'light' or 'thin' version of MPLS in the data plane of Layer 2 access nodes, allowing for MPLS label-based forwarding without full MPLS protocol implementation in the control plane, enabling efficient traffic engineering and simplifying network management by avoiding the need for Virtual Local Area Network (VLAN) configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If full MPLS protocol implementation is deployed in Layer 2 access nodes, then traffic engineering capability is improved, but device complexity and operational expenses increase

Engineering Contradiction:

Improvetraffic engineering capabilityVSAvoiddevice complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments MPLS functionality into two distinct parts: data plane label forwarding and control plane protocol execution. Layer 2 access nodes only implement the data plane segment for MPLS label switching, while control plane functions remain in Layer 3 network elements. This segmentation allows traffic engineering capability to be provided without requiring full MPLS protocol implementation in access nodes, thereby reducing device complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The control plane MPLS protocol execution is extracted from Layer 2 access nodes and centralized in Layer 3 network elements. This extraction allows access nodes to perform MPLS label forwarding without the complexity of running full MPLS control plane protocols, resolving the contradiction between providing traffic engineering and maintaining simple access node architecture.

Inventive Principle:

Principle #2Taking out (Extraction)

2Adaptability or versatility

If VLAN configurations are used in access networks, then service differentiation is achieved, but management overhead and operational complexity increase

Engineering Contradiction:

Improveservice differentiation capabilityVSAvoidmanagement overhead

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent replaces the mechanical VLAN configuration system with an MPLS label-based forwarding system. Instead of using VLAN tags and complex switching configurations, the network uses MPLS labels for service differentiation and traffic engineering. This substitution eliminates the need for manual VLAN management while maintaining service differentiation capabilities through label-based forwarding in the data plane.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If MPLS is implemented in the service provider domain, then traffic patterns are engineered effectively, but the need for dual VLAN and MPLS forwarding increases device complexity

Engineering Contradiction:

Improvetraffic engineering efficiencyVSAvoidforwarding complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the MPLS implementation to exist only in the service provider domain's data plane, without requiring control plane MPLS execution in access nodes. This segmentation allows effective traffic pattern engineering through MPLS label switching while avoiding the complexity of dual VLAN and MPLS forwarding configurations in access network devices.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Layer 3 network elements act as intermediaries between Layer 2 access nodes and the MPLS network. These intermediaries handle control plane MPLS protocol execution and label distribution, allowing access nodes to perform simple MPLS label forwarding without the complexity of full MPLS implementation. This intermediary approach maintains traffic engineering efficiency while reducing forwarding complexity at the access node level.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8121126B1Layer two (L2) network access node having data plane MPLS

Publication Date: 2012.02.21 JUNIPER NETWORKS INC

AI summary

The invention is directed towards techniques for forwarding subscriber frames through a Multi-Protocol Label Switching (MPLS) aggregation network using MPLS labels. Layer two (L2) network devices, such as access nodes, of a service provider (SP) network implement MPLS functionality in the data plane, but do not implement an MPLS signaling protocol in the control plane. The L2 network devices include an interface for configuring a static pool of labels applied in the data plane of the L2 network device to output MPLS communications to the MPLS network. The access nodes may be configured by an administrator to maintain static pools of subscriber labels and MPLS labels. The access nodes autonomously allocate the subscriber labels to subscriber devices that request broadband services from a Broadband Services Router (BSR), and distribute the subscriber labels and MPLS labels as upstream assigned labels.