Protocol Header Compression via Synchronized Sequence Numbers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data compression solutions for packet networks, particularly in voice communications, are inefficient due to redundant protocol headers and lack support for encryption, leading to increased bandwidth usage and latency issues.

Innovation Solution

A method and system that synchronize sequence numbers between protocol layers to remove redundant fields from protocol headers, integrating encryption processing for efficient compression and decompression, using a template-based approach to predict and replace sequence numbers, thereby reducing the total IP packet size and enhancing transmission speed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If protocol headers contain all necessary information for each layer, then protocol functionality and reliability are ensured, but bandwidth consumption increases and transmission efficiency decreases

Engineering Contradiction:
Improveprotocol functionalityVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts redundant protocol header fields from the data transmission. Specifically, it removes fields that can be derived from sequence number synchronization between protocol layers, such as certain checksums and control fields, thereby reducing bandwidth consumption while maintaining protocol functionality through the synchronization mechanism.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The sequence number field serves multiple functions simultaneously: it provides ordering information, enables synchronization between protocol layers, and allows for the derivation of other header fields through mathematical relationships. This multi-functionality reduces the need for separate redundant fields.

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

2Productivity

If sequence numbers are synchronized across protocol layers, then header compression efficiency is improved, but protocol complexity increases

Engineering Contradiction:
Improvecompression efficiencyVSAvoidprotocol complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent performs preliminary synchronization of sequence numbers between protocol layers before data transmission begins. This preliminary action establishes the mathematical relationships and synchronization state in advance, allowing for efficient compression during data transmission without requiring complex real-time calculations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter representation by establishing deterministic mathematical relationships between sequence numbers of different protocol layers. Instead of transmitting all header fields independently, the system uses transformed sequence number parameters that can be derived through simple mathematical operations, reducing complexity while improving compression efficiency.

Inventive Principle:
Principle #35Parameter changes

3Loss of energy

If existing compression algorithms are used, then some bandwidth reduction is achieved, but latency increases and packet loss tolerance is insufficient

Engineering Contradiction:
Improvebandwidth reductionVSAvoidlatency
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent maintains continuous compression operation without interruption for packet loss. The synchronization mechanism continues to function across lost packets through robust sequence number tracking, eliminating the need to reset compression state and thereby reducing latency while maintaining bandwidth efficiency.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The patent incorporates error detection and synchronization recovery mechanisms that are prepared in advance. When packet loss occurs, the pre-established synchronization relationships allow for quick recovery without resetting the compression state, cushioning against latency increases.

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

4Loss of energy

If protocol headers are compressed, then bandwidth usage is reduced, but encryption compatibility becomes problematic

Engineering Contradiction:
Improvebandwidth usageVSAvoidencryption compatibility
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The patent segments the protocol header into compressible fields and non-compressible fields. The sequence number synchronization mechanism operates on the compressible portions, while encryption fields are handled separately. This segmentation allows compression to be applied to specific header fields without compromising encryption compatibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The synchronized sequence number acts as an intermediary that enables compression without requiring direct modification of encrypted fields. The sequence number provides the necessary synchronization information that allows compression algorithms to function correctly even when encryption is applied to protocol headers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7978699B1Protocol compression with synchronized sequence numbers
Publication Date: 2011.07.12 PICOMOBILE NETWORKS INC
  • US7978699B1 patent drawing
  • US7978699B1 patent drawing
  • US7978699B1 patent drawing

AI summary

A system for transmitting data packets includes a sending node. The sending node includes means for forming the data packets using two or more communications protocols. A first protocol includes means to associate with a data load a first header having one or more fields. A second protocol includes means to associate with the data load a second header having one or more fields. The sending node includes compression means for removing one or more fields of the first header. A value of a removed field is predictable by reference to values of one or more fields of the second protocol. A predefined template is used to remove the one or more fields of the first header for compression and to replace the removed field for decompression. The predefined template is identified by a template number included in an added header.