Ethernet Protection Switching in PBB-TE Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Ethernet networks lack scalable end-to-end sub-50 ms resiliency mechanisms for bidirectional linear protection in Provider Backbone Bridging Traffic Engineering (PBB-TE) domains, as existing solutions are not designed to handle large networks and do not support sub-50 ms protection switching.
Innovation Solution
A method and system utilizing IEEE 802.1Qag Connectivity Fault Management (CFM) and Remote Defect Indicator (RDI) for bidirectional linear protection switching, where two PBB-TE trunks with different VLAN Identifiers (VIDs) are established, and data traffic is remapped from a working trunk to a backup trunk upon fault detection, leveraging existing Ethernet technology.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing resiliency mechanisms are used in Ethernet networks, then network protection is provided, but the mechanisms are not scalable to large networks and do not support sub-50 ms protection switching
Solution Approach 1:
The patent segments the protection switching function into distributed components within the Ethernet network infrastructure. Each network device independently performs protection switching based on local fault detection, eliminating the need for centralized control and enabling scalability to large networks while achieving sub-50 ms switching times.
Solution Approach 2:
The patent pre-configures protection paths and establishes backup Ethernet services before faults occur. This preliminary setup allows immediate switching upon fault detection without requiring complex real-time path computation, thereby achieving sub-50 ms protection switching times.
2Reliability
If complex protection mechanisms are implemented, then reliability is improved, but the complexity of the system increases
Solution Approach 1:
The patent implements self-service protection switching where each network device autonomously detects faults and switches traffic to protection paths without requiring complex coordination or control messages between devices. This simplifies the overall system architecture while maintaining end-to-end linear protection capability.
3Loss of time
If sub-50 ms protection switching is achieved, then service recovery time is reduced, but the complexity of detection and switching mechanisms increases
Solution Approach 1:
The patent replaces complex mechanical-style protection switching mechanisms with Ethernet-native protocols and procedures. By utilizing standard Ethernet fault detection capabilities and simplified switching logic, the system achieves sub-50 ms recovery times without requiring complex detection and measurement mechanisms.
Data Source
AI summary
A method of providing protection switching on a backbone network includes configuring a service instance table for a first port of a first bridge. The service instance table includes a Virtual Local Access Network (VLAN) identifier entry for one or more service instances. The method also includes mapping data traffic received at the first bridge onto a first trunk by setting a VLAN identifier entry for a first service instance and transmitting data traffic to a second bridge on the first trunk in accordance with the mapping and monitoring the first trunk for faults by exchanging continuity check messages with the second bridge over the first trunk. The method additionally includes, upon detecting a fault, remapping data traffic for the first service instance by changing the VLAN identifier entry for the first service instance and transmitting data traffic to the second bridge in accordance with the remapping.