Layer 2.5 Protocol for FCoE Traffic Policy Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Fibre Channel over Ethernet (FCoE) protocol is limited in its reach across network boundaries due to its operation at the data link layer, preventing it from being routable across network layers and lacking essential traffic management controls like per-priority pause, explicit congestion notification, and bandwidth allocation, which are crucial for managing congestion and optimizing bandwidth in interconnected networks.
Innovation Solution
A method is introduced to control traffic across network layers by identifying issue sources within interconnected networks and sending traffic policies from one router to another along the route to the issue source, allowing for congestion management and bandwidth optimization across layer 2 network boundaries through routers operating in the network layer, enabling pause commands and bandwidth adjustments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If FCoE protocol operates at data link layer to provide flow control and congestion notification, then reliability is improved, but reach across network boundaries is limited and routability is lost
Solution Approach 1:
The patent extends FCoE functionality from layer 2 to layer 3 by introducing a layer 2.5 protocol that operates over IP networks. This dimensional transition allows FCoE traffic management capabilities to traverse network boundaries while maintaining protocol compatibility with both layer 2 switches and layer 3 routers.
Solution Approach 2:
The patent introduces an intermediary protocol layer that mediates between FCoE layer 2 requirements and IP layer 3 routing. This intermediary translates FCoE control messages into IP-based transmissions, enabling congestion notification and flow control to propagate across network boundaries without direct layer 2 connectivity.
2Adaptability or versatility
If FCoE provides per-priority pause and bandwidth allocation at layer 2, then traffic management control is improved, but complexity increases when extending across network layers
Solution Approach 1:
The patent segments traffic management functions into distinct IP-based message types handled by the intermediary protocol. Each message type (congestion notification, pause request, bandwidth allocation) is independently defined and routed, allowing selective implementation and reducing overall system complexity.
Solution Approach 2:
The patent creates a universal IP-based message format that can carry multiple FCoE control functions within a single protocol framework. This multi-functional approach consolidates per-priority pause, congestion notification, and bandwidth allocation into unified message structures, reducing implementation complexity.
3Length of moving object
If routers are introduced to enable layer 3 routing of FCoE traffic, then network reach is improved, but loss of FCoE-specific functions occurs
Solution Approach 1:
The patent introduces an intermediary protocol layer that preserves FCoE-specific functions while enabling IP routing. The intermediary translates FCoE control messages into IP packets for transmission across layer 3 boundaries, then reconstructs the original FCoE messages at the destination, maintaining all FCoE functionality despite router involvement.
Solution Approach 2:
The patent implements feedback mechanisms where congestion notifications and flow control messages are propagated back through the IP network to traffic sources. This feedback loop ensures that FCoE reliability mechanisms remain effective even when traffic traverses layer 3 routers, as congestion information is actively communicated back to sources.
Data Source
AI summary
Sending traffic policies includes identifying a location of an issue source with a first router in a network layer of an interconnected network and sending to a second router located along a route towards the issue source a traffic policy that addresses an issue caused with the issue source.