LTE11 Robust Header Compression
LTE11 Robust Header Compression
DN251052241
Issue 01
This document includes Nokia proprietary and condential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia. This
document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a
product purchased or licensed from any company within Nokia Group of Companies. Use this
document as agreed. You agree to notify Nokia of any errors you may nd in this document;
however, should you elect to use this document for any purpose(s) for which it is not
intended, You understand and warrant that any determinations You may make or actions
You may take will be based upon Your independent judgment and analysis of the content of
this document.
Nokia reserves the right to make changes to this document without notice. At all times, the
controlling version is the one available on Nokia’s site.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
© 2022 Nokia.
2 Benefits .......................................................................................................................................... 7
This feature supports ROHC( Robust header compression) for IP/UDP and IP/UDP/RTP
headers. It is described in the RFC 3095 and RFC4815.
The IP overhead of the IPv4 or IPv6 is 40 respective 60 bytes. ROHC reduces these values to
2..5 bytes (this is a typical average value).
The protocol headers are compressed due to redundancy in the header fields of consecutive
packets of the same packet stream. A packet classifier can identify different packet streams
by the combination of parameters like protocol headers being carried in the packet, the
source and destination addresses etc.
Initially, a few packets are sent uncompressed and are used to establish the context on both
sides of the link.The context comprises information about static fields, dynamic fields and
their change pattern in protocol headers . This information is used by the compressor to
compress the packet as efficiently as possible and then by the decompressor to
decompress the packet to its original state (see Figure: Principle of ROHC)
Figure: Principle of ROHC shows the download direction, there is also ROHC in the upload
direction.
The compressor always starts in the IR state. In this state, it sends uncompressed packets to
establish the context at the decompressor side. Once it gains confidence that the
decompressor has the context information, it moves to higher states of operation, either
via FO state to SO state or directly to SO state, Figure: Compressor States.
The decompressor states are shown in the following figure, Figure: Decompressor States
Mode Description
U-Mode In Unidirectional mode, packets are sent in one direction, from the compressor
to the decompressor. In cases where the return path of the reserve channels are
not available it requires periodic refresh.
R-Mode In Bidirectional Reliable mode, it issues feadback for all context updates.
The Initial Context Setup procedure supports the ROHC configuration for the conversational
voice GBR EPS bearer. This includes:
Figure 5: EPS Bearer Establishment Procedure by S1AP: Initial Context Setup Procedure
(Service Request)
The PDN GW request the addition of a new dedicated EPS bearer ([3GPP 23.401), e.g.: the
setup of a voice call by IMS
The UE requests a resource modification that causes the addition of a new dedicated EPS
bearer ([3GPP 24.301]:
The UE requests the addition of a new PDN connection including a new default EPS bearer
([3GPP 23.401]), e.g. : start of an IMS based VoIP application or connecting a laptop to a
mobile phone.
Additionally to the UE requested PDN connectivity, PDN GW might request the addition of
new dedicated EPS bearers in combination with the UE requested PDN connectivity
procedure ([3GPP 23.401]
The E-RAB Setup procedure supports the ROHC configuration for the conversational voice
GBR EPS bearer to be established. This includes
Furthermore the eNB supports a feedback channel for the ROHC. This channel is mandatory
in O- mode or R - mode of operation.
header refreshes according to RFC2507, considering the number of packets in one period
and the number of transmitted full headers.
the header refreshes apply for FO-state and SO-state (i.e. in IR-state full-headers are
anyway transmitted).
The eNB supports timer based downward transition from SO-state to FO-state as well as
timer based downward transition from SO-/FO-state to IR-state.
Requirements
For supported hardware and software, see Single RAN Features/List of Features and
Documents/List of Features Supported in Single RAN.
Alarms
There are no alarms related to the LTE11: Robust Header Compression feature.
Commands
There are no commands related to the LTE11: Robust Header Compression feature.
Parameters
Sales information
For licensing information, see 5G/System Descriptions/5G Licenses. Remember that for 5G
features, you also need to configure the Use Case Level Activation Parameters (UCLAPs). For
more information, see .
See Configuring features with BTS Site Manager or Configuring features with Web Element
Manager for general management tool instructions.
Purpose
Follow this procedure to activate the LTE11: Robust Header Compression feature.
Procedure
1 Start configuring the parameters.
Result
The robust header compression is enabled.
Purpose
Follow this procedure to deactivate the LTE11 Robust Header Compression feature.
Procedure
1 Start configuring the parameters.
Result
The robust header compression is disabled.
Issue 01
20