Ethernet Header Compression Scheme for Bandwidth Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing header compression schemes for Ethernet communication protocols are inefficient due to the large size of Ethernet frame headers, leading to bandwidth inefficiency, especially when carrying small payloads, and they often compromise security by making compression keys detectable within carrier networks, making traffic vulnerable to interception.
Innovation Solution
A header compression scheme that uses a 'dummy' data structure to disguise the compression key, allowing it to be conveyed within the payload of a carrier Ethernet frame, with only special edge nodes able to recognize and retrieve the original header information, thereby reducing bandwidth usage and enhancing security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standard Ethernet headers are used for each carrier Ethernet frame, then routing and forwarding information is preserved, but bandwidth efficiency deteriorates when carrying small payloads
Solution Approach 1:
The Ethernet header is segmented into two parts: essential forwarding fields (destination MAC address, VLAN tags) that remain in the carrier frame header, and non-essential fields (source MAC address, Ethernet type) that are removed and stored in a compression context. This segmentation allows the carrier network to forward frames using only the essential fields while reducing overall header overhead.
Solution Approach 2:
Instead of transmitting the complete Ethernet header in each carrier frame, a compressed representation (compression context) is created and stored. The essential forwarding information is copied to the carrier frame header, while the removed header fields are reconstructed at the egress node using the stored compression context, eliminating redundant transmissions.
2Loss of energy
If header compression is implemented across multiple carrier networks, then bandwidth efficiency improves, but complexity of managing compression contexts across networks increases
Solution Approach 1:
The compression context management is extracted from individual network nodes and centralized at the network boundary (ingress and egress nodes of the carrier network). This allows compression to be applied consistently across multiple carrier networks without requiring each intermediate node to maintain compression contexts, simplifying multi-network management.
Solution Approach 2:
The carrier network boundary nodes act as intermediaries that manage compression contexts for traffic passing through multiple carrier networks. These boundary nodes store and retrieve compression contexts, enabling compression to persist across network boundaries without requiring complex coordination between multiple network operators.
3Reliability
If complete Ethernet headers are transmitted for each frame, then security is maintained through full header information, but bandwidth consumption increases
Solution Approach 1:
Different parts of the Ethernet header are treated with different quality levels. The destination MAC address and VLAN tags are maintained with full quality (uncompressed) for forwarding purposes, while the source MAC address and Ethernet type are compressed. This local quality differentiation maintains security and functionality where needed while reducing bandwidth consumption where possible.
Data Source
AI summary
A method of reducing the bandwidth required to send a plurality of client traffic frames over a plurality of carrier communications networks is disclosed. Related communications system, data stores and boundary nodes are also disclosed.