Feature Description
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
Contents
1 Introduction 1
1.1 Basic Characteristics 1
1.2 TCP Optimization Summary 1
1.3 Additional Information 2
2 Feature Operation 3
2.1 Network Requirements 3
2.2 Feature Operation Sequence Diagram 3
2.3 Process Steps 4
2.4 Basic Configuration 4
2.5 TCP Congestion Control 5
2.6 PDCP SDU Timer Discard in the Uplink 6
3 Parameters 8
3.1 Feature Configuration Parameters 8
3.2 Affected Parameters 9
4 Network Impact 11
6 Performance 14
6.1 KPIs 14
6.2 Counters 14
6.3 Events 15
1 Introduction
This document describes the TCP Optimization feature and its main benefits
and impacts in the LTE RAN. It is assumed that the reader has a deep
understanding of TCP and TCP congestion control.
Product identity:
DU Radio Node, see Feature Overview
Replaces: N/A
Dependencies
The TCP Optimization feature is useful to provide a low queuing delay, while
maintaining high link utilization and thereby improving the perceived end-user
performance in terms of system responsiveness without sacrificing throughput.
The feature is also capable of maintaining a more stable cell throughput under
load.
• Quality of Service
2 Feature Operation
This section describes the TCP Optimization feature in more detail, including
network configuration requirements and operation flows.
Delay-based AQM has two active modes. Mode 1 is for TCP type traffic and
mode 2 is for Guaranteed Bit Rate (GBR) such as Voice over LTE (VoLTE).
See Figure 1.
AQM RBS
UE PDCP
L0000489B
The delay-based AQM algorithm makes use of the TCP congestion avoidance
Algorithm, see TCP Congestion Control on page 5. TCP assumes that a
packet loss is due to congestion and therefore it will reduce the number of
bytes it has in flight (congestion window). By discarding a packet we can
reduce the TCP congestion window which results in a shorter queue. In LTE
RAN, the AQM algorithm is implemented in RBS for the downlink only.
However, the UE is configured to use PDCP Service Data Unit (SDU) timer
discard in the uplink.
The delay-based AQM algorithm makes use of parameters based on the type
of traffic managed. For non-GBR data traffic, the algorithm discards a packet
only once it reaches a threshold of age in the buffer, at the same time
maintaining a minimum of packets in the buffer, ensuring that the link
utilization is high while keeping the queueing delay low.
For GBR traffic, the timer threshold is given by the Packet Delay Budget (PDB)
value, as defined in 3GPP TS 23.203.
The queues apply "drop from tail", which means that the incoming packets are
dropped. This delays the congestion signal to the TCP sender which can lead
to more packet loss.
There are two mechanisms for packet discard, regardless whether TCP
Optimization is activated:
The internal configuration of the AQM algorithm depends on the AQM mode
for the Quality of Service Class Indicator (QCI) of the bearer in question.
Configuration is done slightly different depending on the AQM mode. There
are two active AQM modes; the first mode is optimized for GBR services and
the second is optimized for non-GBR services assumed to use TCP. In
general, these map to the resource type with some exceptions for important
traffic, see Table 3.
AQM mode 2 Used for GBR bearers. Packets older than the PDB
may be discarded. Packets older than twice the PDB
are discarded. The UE is configured to use PDCP SDU
timer discard. Keep lower drop threshold = 5 packets in
queue.
An end-point in the network cannot know the true Pipe Capacity (PC) for the
connection; instead it has to probe for the PC and therefore the bottleneck
rate. TCP uses three types of signals; if an ACK is received it is a signal that
more bandwidth is available, if a packet is dropped it is a signal of light
congestion, and if there are many packet drops, or, a time-out, it is a signal of
serious congestion. TCP acts on these signals by changing its congestion
window or by starting all over with the initial settings.
Packets are lost for two reasons – they are lost in transit or the network is
congested. The TCP congestion control assumes that a packet was lost due
to congestion.
assuming a standard compliant TCP sender and TCP New Reno. This
ensures that the queue is not emptied after a packet discard.
Measured in time, the optimal threshold becomes one RTT. The estimated
RTT is by default 100 ms in order to prioritize throughput when PC changes
suddenly.
Since TCP increases the congestion window slowly, and due to the high
likelihood of improved radio conditions in the target cell after handover, the
minimum age threshold is set to twice the estimated RTT. This has the benefit
that the link utilization will be high also after handover. The drawback is that
the delay in normal operation is slightly higher.
The TCP congestion control, with an IETF Standard compliant TCP sender
and optimal configuration of the eNodeB queue size is shown in Figure 2.
Outstanding
bytes Discard
2 PC
Packets in
the eNB queue
1 PC
Packets in
Non-empty queue the pipe
0
t
L0000618A
The configured value depends on the downlink value. There are only 8
allowed values for discardTimer in the IE PDCP-Config defined in 3GPP
TS 36.331: Radio Resource Control (RRC); Protocol specification, so the
nearest value greater than the minimum age threshold is chosen (see Table
1).
3 Parameters
<<MO Class>>
ManagedElement
1 1
1 1
<<MO Class>> <<MO Class>>
ENodeBFunction SystemFunctions
1 1
1 1 1
<<MO Class>> <<MO Class>> <<MO Class>>
EUtranCellFDD QciTable Licensing
estimatedE2ERTT
1 1
10 1
<<MO Class>> <<MO Class>>
QciProfilePredefined OptionalFeatures
aqmMode
pdb
1
1
<<MO Class>>
TCPOptimization
L0000617D
4 Network Impact
This section describes how the TCP Optimization feature impacts the network
functions and capabilities.
This section describes how the TCP Optimization feature affects other
features and functions.
Due to the improved radio conditions in the target cell, a higher PC is needed
to have high link utilization. The minimum age threshold is therefore doubled
at the expense of higher delay in normal operation. The gain is higher
throughput after handover.
6 Performance
6.1 KPIs
This feature has no associated Key Performance Indicators (KPIs).
6.2 Counters
Table 5 lists the counters associated with the TCP Optimization feature.
• EUtranCellFDD
• EUtranCellTDD
Table 5 Counters
Counter Description
pmPdcpPktDiscDlAqm Number of discarded PDCP (Packet Data Convergence Protocol) packets in
downlink due to the AQM algorithm
This is a PEG counter that is incremented by one for each discarded packet.
pmPdcpPktDiscDlAqmQci The number of discarded PDCP packets in downlink due to AQM algorithm for
each specific QCI
This is a Probability Density Function (PDF) counter where each QCI interval is
incremented by one for each discarded packet for that QCI.
• EUtranCellFDD
• EUtranCellTDD
6.3 Events
Table 7 lists the events associated with the TCP Optimization feature.
Table 7 Events
Event Event Parameter Description
INTERNAL_PER_UE_RB_TRAFFI EVENT_PARAM_PER_DRB_PACKET_DISC_A Total number of packets (PDCP SDUs) for
C_REP QM_DL which no part has been transmitted over the
air in the downlink direction that are
discarded due to AQM algorithm
For a full list with detailed information about PM events, see the list files in the
List Files library folder.
Prerequisites
Steps
Let the CCTR be active for one week, for continued collection of
troubleshooting data.
Prerequisites
Continuous Cell Trace Recording (CCTR) is activated since at least one week.
This ensures there is troubleshooting data available if something goes wrong.
Steps
Let the CCTR be active for one week, for continued collection of
troubleshooting data.