Network Gateway Congestion Notification Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mixed-protocol environments, traditional congestion management methods are ineffective due to the loss of Forward Explicit Congestion Notification (FECN) fields when InfiniBand packets are decapsulated, leading to inadequate congestion resolution in networks using Ethernet over InfiniBand (EoIB) or Internet Protocol over InfiniBand (IPoIB) protocols.
Innovation Solution
Implementing a method and system that receive and transmit packets with congestion indicators across different network protocols, such as setting values in ECN, FECN, and BECN fields, and dropping packets as necessary, to effectively manage congestion in InfiniBand networks by using gateways to propagate congestion notifications and adjust traffic flow.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional congestion management methods are used in mixed-protocol environments, then congestion notification can be implemented within single protocols, but congestion indicators are lost during protocol conversion and decapsulation
Solution Approach 1:
The patent introduces gateway devices as intermediaries between InfiniBand and Ethernet/IP networks. These gateways perform protocol conversion while preserving congestion indicators by mapping FECN fields from InfiniBand packets to ECN fields in Ethernet/IP packets, ensuring congestion information survives the protocol transition.
Solution Approach 2:
The patent creates a universal congestion notification mechanism that works across multiple protocols (InfiniBand, Ethernet, IP). By establishing protocol-agnostic congestion indicator mappings and gateway functions, the system achieves multi-protocol compatibility while maintaining reliable congestion notification throughout the heterogeneous network.
2Reliability
If congestion indicators are preserved across protocol boundaries, then congestion management effectiveness improves, but system complexity increases due to protocol conversion requirements
Solution Approach 1:
The patent changes the parameter representation of congestion indicators across protocols by mapping FECN (Forward Explicit Congestion Notification) from InfiniBand to ECN (Explicit Congestion Notification) in Ethernet/IP. This parameter transformation allows congestion information to be preserved while adapting to different protocol requirements, reducing the complexity burden.
Solution Approach 2:
The patent segments the congestion management function into distinct components: InfiniBand network segments, gateway conversion segments, and Ethernet/IP network segments. Each segment handles congestion notification according to its native protocol, with gateways performing targeted field mappings rather than complete protocol re-implementation, thereby reducing overall system complexity.
3Productivity
If packet dropping is used for congestion control, then network throughput can be protected, but packet loss increases and reduces overall network efficiency
Solution Approach 1:
The patent implements feedback-based congestion control by setting ECN bits in packets that traverse congested network paths. Receiving devices detect these ECN-marked packets and provide feedback to transmitting devices, enabling them to adjust their sending rates dynamically. This feedback mechanism protects network throughput without requiring aggressive packet dropping.
Solution Approach 2:
The patent applies preliminary anti-action by marking packets with congestion indicators before they are dropped. By setting ECN/FECN bits in advance, the system warns transmitting devices of upcoming congestion, allowing them to reduce transmission rates proactively rather than reacting to packet drops, thereby preventing loss while maintaining throughput.
Data Source
AI summary
Methods and systems are disclosed for network congestion management. The methods and systems receive a first packet complying with a first network protocol comprising a first congestion indicator representative of a presence or absence of network congestion and further comprising a first set of data associated with a second network protocol, and provide an indication of the presence or absence of network congestion generated based, at least in part, on the first congestion indicator. The methods and systems also receive a first packet complying with a first network protocol comprising a first set of data associated with a second network protocol, and output a second packet complying with the first network protocol comprising a first congestion indicator representative of a presence of network congestion.


