SDN Header Compression via Context Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In voice over IP processes, the number of bits used for header information significantly exceeds the number of bits used for the voice payload, leading to inefficient data transmission.
Innovation Solution
A method involving processors that receive and process packet-headers, generate substitute data, and send signals to other processors to compress and decompress headers using flow table entries and context identifiers, reducing the size of packet-headers and improving transmission efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If header information is transmitted in full detail, then completeness and reliability of data transmission is improved, but transmission efficiency deteriorates due to excessive header size relative to voice payload
Solution Approach 1:
The patent uses context identifiers as simplified copies of full header information. Instead of transmitting complete header data, the system transmits compact context identifiers that reference previously established header contexts, dramatically reducing transmission overhead while maintaining the ability to reconstruct complete header information at the receiving end
Solution Approach 2:
The system performs preliminary establishment of header contexts before actual data transmission. Flow table entries and context identifiers are pre-configured and stored, allowing subsequent transmissions to reference these pre-established contexts rather than repeating full header information, thereby improving transmission efficiency
Data Source
AI summary
A method of header compression steps, performed by a first processor, of receiving a first packet-header sent from a second processor, the first packet-header having been sent in response to the second processor receiving the first packet-header encapsulated in a frame, and the frame not matching a flow table entry in the second processor. The method also includes sending a first signal to the second processor; sending a first flow table entry to the second processor; sending a second signal to a third processor; and sending a second flow table entry to the third processor. The first signal causes the second processor to generate substitute data in response to subsequently receiving a second packet-header, the substitute data being shorter that the second packet-header, the substitute data corresponding to the first signal. The second signal causes the third processor to generate the second packet-header, responsive to the substitute data subsequently received from the second processor, in accordance with the second signal.