E-Tree Services Over MPLS and PBB-TE Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies for implementing Ethernet E-Tree services lack standardized methods for transport, leading to inefficiencies in data routing and bandwidth management, particularly in point-to-multipoint topologies like Metro Ethernet networks.

Innovation Solution

The implementation of Ethernet E-Tree services over MPLS and PBB-TE networks using virtual bridges and PBB-TE trunks, which enforce directional traffic exchange rules to prevent direct communication between leaf nodes and ensure efficient data distribution by using multicast addresses and IGMP snooping for dynamic traffic management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Ethernet E-Tree services are implemented without standardized transport methods, then deployment flexibility is maintained, but routing efficiency and bandwidth management deteriorate

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidrouting efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent applies parameter changes by defining specific transport parameters for E-Tree services over MPLS and PBB-TE networks. It establishes standardized parameters including label distribution, traffic engineering constraints, and bandwidth management rules that transform the unstandardized deployment into an efficient standardized system while maintaining adaptability through configurable parameters.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent segments the E-Tree service implementation into distinct functional components: root node operations, leaf node operations, transit node operations, and transport network operations. Each segment has standardized protocols and procedures, allowing independent optimization while maintaining overall routing efficiency.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If direct communication between leaf nodes is permitted, then communication flexibility increases, but network security and traffic control worsen

Engineering Contradiction:
Improvecommunication flexibilityVSAvoidnetwork security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies asymmetry by creating an asymmetric communication model where root nodes can communicate with leaf nodes, but leaf nodes cannot directly communicate with each other. This asymmetric permission structure maintains network security while providing necessary communication flexibility through the controlled root node interface.

Inventive Principle:
Principle #4Asymmetry

Solution Approach 2:

The patent introduces the root node as an intermediary that mediates all communication between leaf nodes. Instead of allowing direct leaf-to-leaf communication, all traffic must pass through the root node which enforces security policies, thereby maintaining network security while enabling communication flexibility through controlled mediation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If multicast traffic is distributed to all leaf nodes, then data distribution completeness improves, but bandwidth utilization worsens

Engineering Contradiction:
Improvedata distribution completenessVSAvoidbandwidth utilization
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by implementing selective multicast distribution where traffic is sent only to leaf nodes that have expressed interest or need for that specific traffic. Instead of excessive distribution to all leaf nodes, the system performs partial distribution to only the necessary subset, improving bandwidth utilization while maintaining data distribution completeness for receiving nodes.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent implements feedback mechanisms where leaf nodes signal their reception needs to the root node, and the root node adjusts multicast distribution accordingly. This feedback loop ensures that multicast traffic is distributed completely to nodes that need it while avoiding unnecessary bandwidth consumption by nodes that do not require the traffic.

Inventive Principle:
Principle #23Feedback

4Productivity

If multiple E-Tree services share the same network infrastructure, then resource utilization improves, but service isolation and quality of service worsen

Engineering Contradiction:
Improveresource utilizationVSAvoidservice isolation
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies segmentation by dividing the shared network infrastructure into logically separate service instances, each with its own virtual bridges, service instances, and traffic engineering parameters. This segmentation allows multiple E-Tree services to share physical resources while maintaining strong service isolation through virtualization boundaries.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by allowing each E-Tree service to have customized quality parameters, traffic engineering rules, and resource allocation policies specific to its requirements. While sharing the same physical infrastructure, each service maintains its own local quality characteristics, ensuring service isolation and differentiated quality of service.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8385355B1E-Trees over MPLS and PBB-TE networks
Publication Date: 2013.02.26 KMIZRA LLC
  • US8385355B1 patent drawing
  • US8385355B1 patent drawing
  • US8385355B1 patent drawing

AI summary

An E-Tree is disclosed which includes a root node associated with a Metro Ethernet network. The E-Tree includes a first Virtual Bridge (VB), associated with the root node, which is configured to process Ethernet traffic, and a second node associated with the Metro Ethernet network. The E-Tree includes a second VB, associated with the second node, configured to process Ethernet traffic and having a first connection between the first VB and the second VB. The second VB is configured to be able to send Ethernet traffic to the first VB via the first connection, if appropriate. In the event there is a second connection between the second VB and a third VB and the second connection has been assigned a down direction from the point of view of the second VB, the second VB is not permitted to send traffic received from the second connection to another connection which from the point of view of the second VB has been assigned a down direction.