Provider Backbone Bridge Architecture for Zero Packet Loss Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current technologies fail to provide zero packet loss and load sharing between customer networks using Bridges over Provider Backbone Bridge Networks or IP/MPLS networks for TDM streams and I-tagged frames.

Innovation Solution

The proposed architecture includes a Control Word block for framing and sequencing TDM payloads, an I-tag Translator for frame manipulation, and a Scheduler module for distributing frames through virtual ports, along with MPLS-TP for tunneling, ensuring resilient data routing and switching between customer networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional bridging architecture is used for routing data over Provider Backbone Bridge Network, then basic connectivity is provided, but packet loss occurs and load sharing between customer networks is not achieved

Engineering Contradiction:

Improvepacket loss preventionVSAvoidbridging architecture complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the bridging architecture into multiple functional components: Ingress PBB, Egress PBB, MPLS-TP network, and virtual ports. Each component performs a specific function (ingress processing, egress processing, tunneling, scheduling) to collectively achieve zero packet loss and load sharing without requiring complete architectural redesign.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces MPLS-TP (Multi-Protocol Label Switching - Transport Profile) as an intermediary layer between traditional PBB architecture and IP/MPLS networks. This intermediary enables resilient data routing with zero packet loss by providing structured tunneling and scheduling mechanisms while maintaining compatibility with existing bridging standards.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If single path routing is used in Provider Backbone Bridge Network, then architecture simplicity is maintained, but network resiliency and load sharing capability are reduced

Engineering Contradiction:

Improvenetwork resiliencyVSAvoidrouting architecture complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic path selection through virtual ports (VP1, VP2, etc.) that can be configured to distribute traffic across multiple MPLS-TP tunnels. The Scheduler module dynamically schedules frames through different virtual ports based on load conditions, enabling load sharing and improved network resiliency while maintaining manageable architectural complexity through standardized interfaces.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS9258140B2Architecture for routing data of a customer network over provider's network in provider backbone bridges

Publication Date: 2016.02.09 TEJAS NETWORKS LTD

AI summary

Embodiments of the disclosure are related to routing or switching data of a customer network over a provider's network in Provider Backbone Bridge (PBB) to another customer network such that the traffic in the communication channel between the two customer networks is reduced and thus prevents packet loss. The architecture model for routing or switching data of a customer network over a provider's network is a B-component bridge used in backbone networks which performs Σn1 data path protection to prevent packet loss, data aggregation for load sharing, TDM (Time Division Multiplexing) to Ethernet Circuit Emulation.