Key Factor Affcet Throughput
Key Factor Affcet Throughput
Key Factor Affcet Throughput
a) Insufficient Traffic - it is when the tb0TbByteLenth >= waitingData, then it means that the incoming
traffic is insufficient.
Handling process: Using gNB MAC Padding Packet Injection to check whether the Uu interface is OK or
not. If MAC Padding packet injection result is perfect it means that Uu interface RF quality is
not problem. Need to further perform the TCP problem analysis to investigate further for the
insufficient incoming traffic
b) AMBR Rate Limiting - it is when either the quota slices of SIM cards are insufficient, packet loss occurs
on the core network, resulting in a low downlink rate; UE AMBR limitation; QCI-level PDCP, RLC, and
MAC parameters setting; or when the UE cannot exceed the core network APN AMBR limit
Handling Process:
A. To avoid reaching the quota of SIM cards, it is recommended that offline charging be used
for SIM card charging.
B. For the UE AMBR limitation, make sure that the UE AMBR is enough which can be queried
over the S1 interface under (NGAP_INIT_CONTEXT_SETUP_REQ (SA)), X2 interface
(SgNB_Add_Req (NSA)), or S1AP_INITIAL_CONTEXT_SETUP_REQ (NSA) messages
C. The APN AMBR can be queried from the Attach accept message in the drive test log. The APN
AMBR can be calculated using the NSA APN AMBR Calculator. The UE AMBR limits the non-
GBR rate of the UE, and the APN AMBR limits the rate of each APN of the UE.
c) DCI and multi-user scheduling - this is when there are too many online users or background users or
insufficient downlink scheduling.
Handling Process:
A. Online / background users can be check using the Users Statistic Monitoring in U2020.
B. OSS number of users can be crosschecked thru KPI counters: N.User.RRCConn.Max,
N.User.RRCConn.Avg, N.User.RRCConn.Active.Avg, N.User.RRCConn.Active.Max.
C. CCE allocation failures can be analyzed based on the schErrCode field in the CellDT 537
tracing result. The value of the schErrCode field is 0x0 when the scheduling is successful and
is not 0 when the scheduling fails.
D. PUCCH Resource Allocation Failures (SchErrCode 0xd0003) must L3 Check PUCCH-related
configurations. Run the LST NRDUCELLPUCCH command to check whether the baseline
recommended value is used.
E. Scheduling Failure Due to Insufficient CCE Resources (SchErrCode: 0xc0331) can be optimize
by adjusting the uplink CCE ratio (specified by NRDUCellPdcch.UlMaxCcePct) and disable
SIB1: NRDUCellRsvd.RsvdParam140 in NSA scenarios. (in 20A: CCE uplink-downlink
configuration adaptation)
F. Insufficient scheduling caused by gap measurement on the NR side due to LTE inter-
frequency gap measurement (schErrCode 0x110319) can be optimize by disabling periodic
inter-frequency and inter-RAT MR measurement for NSA UEs
B. RLC problems
1. RLC SN Length Configuration Problem The recommended value of RLC SN is 18bit. If the value is
smaller than the value of 18bit, the number of windows is insufficient. The value cannot be greater
than the length of PDCP SN. gNBRlcParamGroup.DlRlcSnSize, gNBRlcParamGroup.UlRlcSnSize
2. RLC mode configuration has a direct impact on rate fluctuation. If the UM mode is used, packet
loss occurs in the protocol, which has a direct impact on the upper-layer TCP services. If the bit
error rate over the air interface is high, the TCP send window is quickly converged and the rate
drops. If the AM mode is used, the protocol does not allow packet loss. In the baseline version,
the AM mode must be set to gNBRlcParamGroup.RlcMode.
PDCP/RLC layer parameters corresponding to Default QCI with recommended value are shown below:
e) TCP Problem
Handling Process:
1. Create an IFTS tracing task.
On U2020, choose U2000->Monitor->Signaling Trace->Signaling Trace
Management->NR->Information Collection->IFTS Trace. Select L2 and enter the trace number
3201.
2. UE reconnection: After an IFTS tracing task is created in a cell, the task is not started. The tracing
task can be triggered only after the RRC connection is established. Therefore, you need to re-
access the UE to be traced.
3. Save the result. To stop a tracing task, right-click the task and choose Stop. If the Status is Finished,
click Export to save the tracing result to tmf format.
4. Data Processing. After the IFTS 3201 packet is captured, use the PDCP_MyLDT (integrated in the
5G FMA) to obtain the Pcap file.
The FMA-IPPA data transmission tool simplifies TCP problem analysis. It is integrated in 5G-FMA tools,
It can be opened via FMA->Tools-> FMA IPPA
a) Coverage (test Location) - Coverage problems include weak coverage, overshoot coverage, and
overlap coverage.
Weak coverage: When a UE is located at the cell edge or is blocked by buildings, the UE may be in weak
coverage scenarios. In this case, the signal strength is low and the MCS is poor. Generally, the higher
the RSRP, the better the MCS. However, the SSB RSRP should not exceed -65 dBm. If the UE receives
too much power, clipping may occur on the receiver. As a result, the SINR decreases, the MCS
decreases, and the data rate decreases.
Overshoot coverage: Overshoot coverage causes co-frequency interference, incorrect handovers, a
large number of handover failures, and call drops due to non-handovers, which greatly affects the MCS.
Overlap coverage: Overlap coverage causes co-channel interference, which causes frequent handovers
and affects the MCS.
Handling Process:
Weak Coverage: This is a normal situation and needs to be resolved by the coverage enhancement
solution.
Overshoot/Overlap coverage: Physical parameters or power of overshooting cells need to be adjusted
to reduce overshooting interference
Intra-system interference: Neighboring cell interference and Overshooting interference, clock out-
of-synchronization interference, loopback interference, and super-distance interference;
External Interference: Perform frequency scanning for external interference and enter the
interference analysis.
ii. If the rank value remains unchanged and the MCS is low, the rank may be fixed. In this case, check
the rank parameter.
d) Small Packets - When the proportion of small packets is high, the average MCS index is low due to the
small-packet MCS lowering algorithm even if the Uu interface condition is good.
Handling Process:
The “ReduceMcs0” field in the CellDT537 result can be used to check whether the MCS is reduced
due to small packets by compares it to the “rateMtcMcs”field. As shown in the following figure,
when the incoming traffic is insufficient (waiting data is small and usrschpdschDrbData is 0),
ReduceMcs0 is less than RateMtcMcs0, indicating that the MCS index is reduced for small packets.
e) Control Plan Problems can be NR release exception, NR SgNB addition exception, and NR SgNB change
exception
Handling Process:
A. Abnormal NR release event
i. SCG release due to LTE-to-NR handovers: No X2 interface is available between LTE and NR, or
the EN-DC switch is turned off on the LTE side (NSA_DC_CAPABILITY_SW).
ii. The LTE network normally releases the SCG. The possible cause is that the NR coverage is poor
and reaches the A2 threshold.
Recommended
MO Parameter ID Parameter Name
Value
Downlink Adaptive
NRDUCellPdsch DL_MCS_TABLE_ADAPT_SW@DlLinkAdaptAlgoSwitch Algorithm Switch 1
NRDUCellPdsch DlInitMcs DL Initial MCS 4
NRDUCellPusch UlTargetIbler Uplink Target IBLER 10
b) Terminal capability
Handling Process:
A. Non antenna switching UE:
i. Use PMI weight, RANK determined by the RI reported by UE. It is difficult to achieved
RANK4
B. Antenna switching UE:
i. Use SRS weight in good coverage area, RANK determined by the SRS measurement
result. Easy to achieved RANK4
ii. The UE reports the maximum MIMO layer capability and antenna switching capability
in the RRC_UE_CAP_INFO
c) Parameters & License
Handling Process:
A. Parameters
i. SRS and PMI weight adaptive switch should be on.
NRDUCellAlgoSwitch.DL_PMI_SRS_ADAPT_SW@AdaptiveEdgeExpEnhSwitch = 1
ii. RANK adaptive scheme under SRS weight. NRDUCellRsvdOptParam.Param1WithParamId120,
The recommended value is 0, indicating that this parameter does not take effect. By default, the
gNB uses the optimal spectral efficiency adaptive solution.
iii. Enable SU MIMO multi-stream function:
NRDUCellAlgoSwitch.DL_SU_MULTI_LAYER_SW@SuMimoMultipleLayerSw=1,
NRDUCellAlgoSwitch.UL_SU_MULTI_LAYER_SW@SuMimoMultipleLayerSw = 1
B. For Channel calibration, query the channel calibration result by running the following command
on the 5G MML: DSP NRLOCELLCHNCALIB. If the channel calibration fails, use command STR
NRLOCELLCHNCALIB to manually correct it.
e) Interference and CQI - In the peak throughput test scenario, the DMRS SINR must be greater than 30
dB. And ensures that the MCS is close to 27 and IBLER is close to 0%.
When interference signals exist in a cell, the uplink and downlink services of the cell are affected. As a
result, the access, call drop, and low rate occurred. If the high RSRP and low SINR (such as the average
RSRP >=-80dBm and average SINR <=15dB) and MCS are low, CQI is bad, BLER is high, then interference
can be analyze.
The causes of interference include Intra-system interference, inter-system interference, and external
interference.
o Intra-system interference: Neighboring cell interference and Overshooting interference, clock
out-of-synchronization interference, loopback interference, and super-distance interference;
o Inter-system interference: TDD-LTE interference; other operator 5G interference; Other system
interference
o External Interference: Perform frequency scanning for external interference and enter the
interference analysis.
f) RF Coverage and Quality which can be caused by weak coverage, overshoot coverage, and overlap
coverage leading to poorer CQI/RI reported by the UE and poorer SRS measurement result by the gNB.
g) Handovers
Handling process:
A. Inter-cell Frequent Handovers
After the handover, the UE initially accesses the network. The low RANK MSC ensures the access
success rate and handover success rate. After the handover, the initial RANK value is 1 by default,
which can be adjusted within 30 ms, the impact is small. However, if frequent handovers occur,
the RANK cannot be quickly adjusted. Therefore, the frequent handover areas need to be
optimized.
B. Strong neighbors but handover cannot be triggered
i. Neighborhood Check
ii. X2 interface Check