Header Compression Using Cross-Stream Address References

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional header compression schemes are unable to efficiently compress IP addresses in packet streams with similar but not exactly the same addresses, leading to suboptimal overhead reduction during context initialization.

Innovation Solution

A method for compressing first address data in a communication system by using second address data from another packet stream, where the compressor determines if the difference between the two addresses meets a predefined condition, allowing for the use of the second address as a reference for compression, and implementing specific encoding formats to represent the compressed address data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of substance

If conventional header compression schemes use separate contexts for each IP address, then context synchronization is maintained, but overhead reduction is suboptimal for similar addresses

Engineering Contradiction:
Improveheader overheadVSAvoidaddress similarity exploitation
Core Design Contradiction:
Loss of substanceVSAdaptability or versatility

Solution Approach 1:

The patent merges the handling of similar IP addresses by allowing one context to reference another context's address data. Instead of maintaining completely separate contexts for each IP address, the system combines address information from multiple contexts when addresses are similar, reducing redundancy while maintaining the ability to handle different address scenarios.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent changes the parameter representation by introducing offset values and reference indicators instead of transmitting complete address fields. When addresses are similar, only the differences (offsets) and context references are transmitted, fundamentally changing how address data is encoded and reducing overhead significantly.

Inventive Principle:
Principle #35Parameter changes

2Loss of substance

If context replication is used for exact address matches, then synchronization overhead is reduced, but addresses with small differences cannot be compressed

Engineering Contradiction:
Improvesynchronization overheadVSAvoidaddress variation handling
Core Design Contradiction:
Loss of substanceVSAdaptability or versatility

Solution Approach 1:

The patent applies partial action by transmitting only the differing portions of addresses rather than complete addresses. When addresses are similar, only the offset values and reference indicators are sent, which is less than the full address data, thereby reducing overhead while still handling address variations effectively.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent segments address data into reference portions (from the referenced context) and differential portions (offsets and unique identifiers). This segmentation allows the system to transmit only the necessary differential information while relying on the referenced context for the common portions, reducing synchronization overhead and enabling handling of address variations.

Inventive Principle:
Principle #1Segmentation

3Measurement precision

If uncompressed address values are sent for similar but different addresses, then address accuracy is maintained, but compression efficiency is reduced

Engineering Contradiction:
Improveaddress accuracyVSAvoiddata compression ratio
Core Design Contradiction:
Measurement precisionVSLoss of substance

Solution Approach 1:

The patent uses copying by referencing existing context data instead of transmitting complete address values. The referenced context acts as a template, and only the differences (offsets) need to be transmitted, maintaining address accuracy while significantly improving compression efficiency for similar addresses.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent makes the compression system universal by creating a mechanism that can handle multiple address scenarios (exact matches, similar addresses, and completely different addresses) through a single unified approach using context references and offsets, rather than requiring separate handling for each case.

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

Data Source

PatentUS8767704B2Compressing header data
Publication Date: 2014.07.01 NOKIA SOLUTIONS & NETWORKS OY
  • US8767704B2 patent drawing
  • US8767704B2 patent drawing
  • US8767704B2 patent drawing

AI summary

A method for compressing information in a communication system is provided. The method includes compressing first address data in a first packet stream by using second address data included in a second packet stream.