Header Compression for Reliable Multicast Protocols

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current packet header compression techniques are inadequate for reliable multicast transport protocols like ALC, FLUTE, MUPPET, and NORM, as they either fail to compress IP headers effectively or introduce transmission errors, limiting bandwidth conservation in wireless networks.

Innovation Solution

A method and system for establishing a compression context for packets associated with these protocols, categorizing header fields, and generating compressed packets with reduced bit counts, using techniques like ROHC and further multicast-specific compression methods to efficiently transmit and decompress headers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If general-purpose compression algorithms (e.g., gzip) are used for packet payloads, then compression capability is provided, but they are not effective for compressing packet headers which consume considerable bandwidth

Engineering Contradiction:
Improvebandwidth consumptionVSAvoidcompression effectiveness for different packet types
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The patent segments the packet into header and payload portions, applying different compression strategies to each. The header compression mechanism specifically targets the header fields (IP, UDP, RTP) with specialized algorithms, while the payload can use general-purpose compression. This segmentation allows optimized compression for each component based on its characteristics.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameters of compression by using different compression algorithms and strategies for different packet types and header fields. It dynamically adjusts compression parameters based on packet characteristics, error conditions, and network state to optimize bandwidth efficiency while maintaining compatibility.

Inventive Principle:
Principle #35Parameter changes

2Loss of energy

If ROHC compression scheme is used for UDP/IP packets, then header compression is achieved, but it only compresses UDP/IP portions and not the full packet structure including RTP headers

Engineering Contradiction:
Improvebandwidth consumptionVSAvoidcompression scope and protocol support
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent creates a universal header compression mechanism that can handle multiple protocol types (IP, UDP, RTP, ESP) within a single framework. The compression entity is designed to work with various packet structures and protocol combinations, providing multi-functional capability that extends beyond ROHC's UDP/IP limitation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent merges multiple compression approaches by combining ROHC's robust header compression capabilities with additional compression techniques for RTP and other protocol headers. It integrates different compression strategies into a unified mechanism that can compress the entire packet header structure comprehensively.

Inventive Principle:
Principle #5Merging (Combining)

3Loss of energy

If RFC 2507 IP header compression scheme is used, then IP header compression is provided, but it has problems with transmission errors and does not support error recovery

Engineering Contradiction:
Improvebandwidth consumptionVSAvoiderror resilience
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent implements error resilience mechanisms in advance by incorporating error detection and recovery capabilities into the compression framework. It uses acknowledgment packets, retransmission mechanisms, and error correction strategies that are built into the compression protocol, providing cushioning against transmission errors before they cause data loss.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The patent employs feedback mechanisms where receiving devices send acknowledgments and error reports back to transmitting devices. This feedback loop enables error detection, retransmission requests, and dynamic adjustment of compression parameters to maintain reliability in error-prone wireless environments.

Inventive Principle:
Principle #23Feedback

4Loss of energy

If DEFLATE compression mechanism is used, then compression is achieved, but it causes problems with transmission errors because it does not provide support for error recovery

Engineering Contradiction:
Improvebandwidth consumptionVSAvoiderror recovery capability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent cushions against DEFLATE's lack of error recovery by layering error protection mechanisms above the compression algorithm. It uses protocol-level error detection, acknowledgment systems, and retransmission capabilities that compensate for DEFLATE's vulnerability to transmission errors in wireless networks.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The patent introduces an intermediary compression entity that sits between the DEFLATE algorithm and the network transmission. This intermediary adds error resilience features, manages retransmissions, and coordinates between sender and receiver to provide the missing error recovery capability while maintaining DEFLATE's compression efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7430617B2Method and system for header compression
Publication Date: 2008.09.30 III HOLDINGS 3 LLC
  • US7430617B2 patent drawing
  • US7430617B2 patent drawing
  • US7430617B2 patent drawing

AI summary

A compression context for a plurality of packets is established with a receiving device. Each of these packets is associated with one or more reliable multicast protocols, such as the Layered Coding Transform (LCT) protocol, the Asynchronous Layered Coding (ALC) protocol, the FLUTE protocol, the MUPPET protocol, and the NACK-Oriented Reliable Multicast (NORM) protocol. Upon establishment of the compression context, a compressed packet is generated for one of the plurality of packets and transmitted to the receiving device. The compressed packet has a reduced number of bits in its header. Upon receipt, the receiving device decompresses the compressed packet based on the compression context.