ROHC Header Compression for MPTCP Packets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
ROHC compression of MPTCP packets often results in transmission failures due to the format of MPTCP packets, leading to inefficiencies and errors in decompressor state machines.
Innovation Solution
A user equipment device (UE) with a compressor determines the context of MPTCP option support in data packets and operates in one of three modes of compression: safe, full, or non-compression modes, adjusting compression strategies based on decompressor feedback to avoid errors and ensure successful transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If ROHC compression is applied to MPTCP packets, then header size is reduced and bandwidth efficiency is improved, but transmission failures occur due to decompressor state machine errors
Solution Approach 1:
The patent implements dynamic mode selection (uncompressed, partially compressed, or fully compressed) based on network conditions and decompressor capabilities. The compressor can transition between different compression modes to balance bandwidth efficiency and transmission reliability, avoiding state machine errors by adapting to current system state.
Solution Approach 2:
The patent changes compression parameters dynamically by adjusting the level of compression applied to MPTCP packets. When decompressor support is confirmed, full ROHC compression is applied; when support is uncertain, the system switches to partial or no compression, thereby changing the compression parameter to prevent transmission failures while maintaining optimal bandwidth usage.
2Productivity
If full ROHC compression is used for MPTCP packets, then compression efficiency is maximized, but decompressor errors occur when MPTCP option support is not confirmed
Solution Approach 1:
The patent performs preliminary verification of decompressor MPTCP option support before applying full ROHC compression. The system establishes context information and confirms capability compatibility in advance, then selects the appropriate compression mode. This preliminary action prevents decompression errors by ensuring the decompressor can handle compressed MPTCP packets before compression is applied.
Solution Approach 2:
The patent implements feedback mechanisms where the compressor receives information about decompressor capabilities and adjusts compression behavior accordingly. Based on feedback regarding MPTCP option support, the system dynamically selects between uncompressed, partially compressed, and fully compressed modes, ensuring compression efficiency is maximized only when decompression reliability is guaranteed.
3Adaptability or versatility
If MPTCP option is included in compressed packets, then multipath functionality is preserved, but compression reliability decreases due to format compatibility issues
Solution Approach 1:
The patent applies different compression qualities to different parts of the packet. The MPTCP option field is handled differently from the standard TCP header - sometimes compressed, sometimes transmitted uncompressed depending on the mode. This local quality approach allows multipath functionality to be preserved in the MPTCP option while maintaining compression reliability for the rest of the packet structure.
Solution Approach 2:
The patent segments the packet compression process into different levels: full compression of TCP header, partial compression with MPTCP option preservation, and no compression for the option field itself. This segmentation allows the system to maintain multipath functionality while managing compression reliability by treating different packet components with appropriate compression strategies.
Data Source
AI summary
Systems, methods, and mechanisms for performing ROHC header compression on TCP packets with MPTCP option enabled. A compressor may determine that a first portion of the stream of data packets is formatted according to the transmission control protocol (TCP) with a multipath TCP (MPTCP) option enabled. The compressor may establish context with a corresponding decompressor and may operate in one of three modes of compression based on the context. In some embodiments, when the context indicates that the corresponding decompressor supports decompression of TCP data packets with MPTCP option enabled, the compressor may operate in a first or second mode of compression. In some embodiments, when the context indicates that the corresponding decompressor does not support decompression of TCP data packets with MPTCP option enabled, the compressor may operation in a third mode of compression.