E-SPRing Protocol for Ethernet Ring Loop Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Ethernet network protocols, such as spanning tree, are not optimized for closed loop topologies, leading to inefficiencies in traffic management and potential endless looping of data packets when loops form in the network.
Innovation Solution
The Ethernet Shared Protection Ring (E-SPRing) control protocol, which operates independently of underlying transport protocols and control layers, uses ring-specific VLAN tags and port-based filtering to prevent loop formation and efficiently manage traffic in closed loop networks, allowing for peered or hub-and-spoke connectivity modes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If spanning tree protocol is used to control Ethernet networks, then loop prevention is achieved, but traffic management efficiency deteriorates due to blocked links and suboptimal routing
Solution Approach 1:
The patent segments the Ethernet network into multiple Virtual LANs (VLANs) with unique identifiers. Each VLAN operates as an independent broadcast domain, allowing traffic to be segmented and managed separately. This segmentation enables multiple active paths within different VLANs while preventing loops at the Ethernet layer by confining broadcast traffic to specific VLAN segments.
Solution Approach 2:
The patent introduces a bridge relay as an intermediary device that operates between the physical Ethernet layer and the VLAN layer. The bridge relay uses VLAN tags to mediate traffic flow, determining which VLAN-specific paths to activate. This intermediary mechanism allows the network to maintain closed-loop physical topology while logically preventing loops through VLAN-based traffic steering.
2Reliability
If closed loop topology is implemented, then network redundancy and protection switching are improved, but loop formation and endless packet circulation worsen
Solution Approach 1:
The patent adds a new dimension to Ethernet frame structure by inserting VLAN tags (802.1Q encapsulation). This additional dimensional layer allows the network to maintain the closed-loop physical topology for redundancy while using VLAN identifiers to logically distinguish and control traffic paths, preventing endless circulation by ensuring packets are confined to specific VLAN domains.
Solution Approach 2:
The patent applies different VLAN configurations to different segments of the closed-loop network. Each segment or link can be assigned specific VLAN memberships, creating local quality variations in traffic permissions. This allows certain links to be active for specific VLANs while blocked for others, enabling redundancy at the physical level without causing loops at the logical Ethernet level.
3Adaptability or versatility
If traditional Ethernet protocols are used, then compatibility with existing standards is maintained, but optimization for closed loop topologies is lost
Solution Approach 1:
The patent makes the VLAN-based control mechanism universal by implementing it within standard Ethernet frame structures using 802.1Q encapsulation. The bridge relay device performs multiple functions: it acts as a standard Ethernet bridge, a VLAN tagger/untagger, and a loop prevention mechanism all in one. This multi-functionality allows existing Ethernet infrastructure to be optimized for closed-loop topologies without requiring new hardware or protocols.
Data Source
AI summary
Ethernet nodes, interconnected logically or physically to construct a closed loop, may be controlled using a control protocol that governs placement of blocks on the ring. The control protocol allows one of the nodes to be designated as a root node in normal operation. The root node will block data traffic on one of its ports on the ring to prevent a forwarding loop from being created on the ring. Each node on the ring performs link level connectivity detection and, upon detection of a failure, will send out a Failure Indication Message (FIM). When a node receives a FIM, it will flush its forwarding database associated with the ring and, if it is the root node, will remove the data block on the port. When the failure recovers, the nodes adjacent the failure will transmit a recovery indication message to allow the ring to revert to its normal state.