Page 1 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
Slow
Throughput
issue reported
No
No Subs All
affected eNodeBs
?
No
Check
eNodeB One
for issues
Implement
troublshooting
Check the
guideline
Ue config
or laptop
Page 2 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
2. Throughput Considerations
The UE estimates SINR (Signal to Interference Noise Ratio) based on the PSD (Power Spectral Density) of the downlink
Reference Signals (RS) and PSD offset between Physical Downlink Shared Channel (PDSCH) and RS. The SINR is
converted to Channel Quality Indicator (CQI) and reported to the RBS in the Channel Feedback Report (CFR). The CQI
indicates the radio quality, and is used by the link adaptation function to select the transport format matching the channel
conditions. This leads to improved radio resource use.
CFRs contain CQI, and Rank Indicator (RI). RI is used only when a Multiple Input Multiple Output (MIMO) channel is
present. CFRs are transmitted when the RBS triggers one over the Physical Uplink Shared Channel (PUSCH) based on
downlink data activity and the age of the earlier received CFR.
The RBS performs an adaptive adjustment of the SINR derived from CQI to compensate for errors and mismatches, and
fulfills the targeted operating point.
Mapping of CQI to MCS (Modulation Coding Schemes) is performed by DL Link Adaptation, Included are guiding tables
as defined in 3GPP (36213-920).
Since UE will report lower CQI values when using MIMO as opposed to SIMO in same RF environment (SINR), UE will
typically use lower Modulation/MCS. This is due to that the UE will take the inter-stream interference into account when
reporting CQI and for SIMO transmission no such interference will exist and the CQI will typically be higher. For example
when the UE is configured in SIMO it will report CQI 15 but when it is configured in MIMO it will report CQI 10.
Note, further fine tuning of MCS’s is performed with HARQ based Outer Loop Link Adaptation (maintain a certain Block
Error Rate).
Page 3 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
Page 4 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
Page 5 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
5.4. IP Settings
1. Are there any limitations on the FTP Server?
2. Receiving Window Settings
3. MTU Size Settings: 1360
Page 6 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
ENodeBFunction=1,RadioBearerTable=default,MACConfiguration=1
=================================================================================
================================
MACConfigurationId 1
dlMaxHARQTx 4
dlPathlossChange 3
tPeriodicBSRTimer 5
tPeriodicPHRTimer 200
tProhibitPHRTimer 200
tTimeAlignmentTimer 5120
ulMaxHARQTx 4
=================================================================================
================================
Total: 2 Mos
Page 7 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
From a DL UPC perspective, the validatorFO is the software entity that orders the SE's for transmission based on weight.
In a HARQ config, the order would be SI - retx - newtx. The following traces can be used to verify the validatorFO
behaviour/decision making.
lhsh gcpu00768 te e all UpDlRrcCPeBl_Ieic
lhsh gcpu01024 te e all UpcDlMacCeFt_UE
lhsh gcpu01024 te e all UpcDlMacCeFt_DL_VALIDATION
Page 8 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
sigNo = 430
header {
cellId = 12
sfn = 537
subFrameNo = 9
nrOfPuschReports = 1
nrOfPucchSrReports = 0
totalNrOfReports = 1
reportList[0] {
Page 9 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
puschReport {
meas2DlUlReportType = 2
padding0 = 0
bbUeRef = 201326912
pucchSrReport {
meas2DlUlReportType = 2
padding0 = 0
bbUeRef = 201326912
sigNo = 429
header {
cellId = 12
sfn = 537
subFrameNo = 8
nrOfPuschReports = 0
nrOfPucchReports = 1
Page 10 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
totalNrOfReports = 1
reportList[0] {
puschReport {
meas2DlUlReportType = 1
padding0 = 0
bbUeRef = 201326912
pucchReport {
meas2DlUlReportType = 1
padding0 = 0
bbUeRef = 201326912
Page 11 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
dlHarqValid = 1
One codeword:
detectedHarqIndication = 0 NACK
detectedHarqIndication = 1 ACK
5.6.3.8. UL Scheduler Checks:
lhsh gcpu01024 te e trace3 trace4 trace5 trace6 trace7 UpcUlMacCeFt_UL_SCHEDULER
lhsh gcpu01024 te e trace1 trace3 trace4 trace7 trace9 UpcUlMacCeFt_UL_VALIDATION
lhsh gcpu01024 te e trace3 trace4 trace5 UpcUlMacCeFt_UL_LINKADAPTATION
lhsh gcpu01024 te e trace5 UpcUlMacCeBl_SseSession
lhsh gcpu01024 te e trace4 UpcDlMacCeFt_DL_SCHEDULER
lhsh gcpu00256 te e all UpUlPdcpPeFt_DISCARD
lhsh gcpu00256 te e all UpUlRlcPeFt_DISCARD
lhsh gcpu00768 te e all UpDlPdcpPeFt_DISCARD
lhsh gcpu00768 te e all UpDlRlcPeFt_DISCARD
lhsh gcpu00768 te e all UpDlRlcPeFt_RETRANSM
lhsh gcpu00768 te e trace1 UpDlL1*
lhsh gcpu01024 te e trace1 UpcDlMacCeBl
mtd peek -ta ulMacPeBl -signal LPP_UP_ULMACPE_CI_UL_L1_MEAS2_DL_IND -pe 2 -rep
65535
mtd peek -ta ulMacPeBl -signal LPP_UP_ULMACPE_CI_UL_UE_ALLOC_IND -pe 1 -rep 65535
mtd peek -ta ulMacPeBl -signal LPP_UP_ULMACPE_CI_UL_L1_MEAS2_UL_IND -pe 2 -rep
65535
mtd peek -tar ulMacPeBl -sig LPP_UP_ULMACPE_CI_UL_MAC_CTRL_INFO_IND -dir 1
Note! HiCap tracing needed
5.6.3.9. Other Checks:
Page 12 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
sigNo = 432
header {
cellId = 7
sfn = 47
subFrameNo = 7
}
payloadSize = 17
nrOfUeUlMacCtrlInfo = 1
ueUlMacCtrlInfo[0] {
header {
sessionRef = 117440512
harqInfo = 1 (UpUpCommonMacCommonMacCtrlElemHarqFeedbackAck)
isDtx = 0
prbListStart = 1
prbListEnd = 2
ulHarqProcessId = 5
nrOfSduInfos = 0
nrOfMacCtrlElements = 1
size = 17
}
dummyNrOfSduInfos = 0
dummyNrOfMacCtrlElements = 0
macCtrlElementList[0] {
type = 7 (UpUpCommonMacCommonMacCtrlElemLongBsr)
powerHeadroomReport { type = 7 (UpUpCommonMacCommonMacCtrlElemLongBsr),
powerHeadroom = 0 }
cRnti { type = 7 (UpUpCommonMacCommonMacCtrlElemLongBsr), crnti = 0 }
truncatedBSR { type = 7 (UpUpCommonMacCommonMacCtrlElemLongBsr), bufferSize
= 0 }
shortBSR { type = 7 (UpUpCommonMacCommonMacCtrlElemLongBsr), bufferSize = 0
}
longBSR { type = 7 (UpUpCommonMacCommonMacCtrlElemLongBsr), bufferSizeNr1Nr2
= 0, bufferSizeNr3Nr4 = 0 }
}
}
5.6.3.9.2. The following pmCounters may be used to identify a low data rate from core to eNB:
pmIfInOctetsLink1Hi [GigaBitEthernet]
pmIfInOctetsLink1Lo [GigaBitEthernet]
Page 13 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
By sampling them at, e.g. 10 sec intervals, and calculating the difference the low input can be identified. In such cases the
operator must be notified that its transport network needs corrections. For more details please see PRIMUS solution
SCS1100666:
[http://e-support.ericsson.se/reader_iview/ui/eserver.asp?ID=SCS1100666].
Tracing can be configured to collect general routing information, interface, protocol, or service specific information.
Page 14 4/3/2017
LTE THROUGHPUT TROUBLESHOOTING GUIDELINE
References :
1. PLM LTE Wiki Page
http://lte-plm.rnd.ki.sw.ericsson.se/lte_trsh_wiki/L12A/index.php?n=UseCases.UserThroughputDegraded
LTE-SAE Slow
Throughput_Rev_0.1
Page 15 4/3/2017