5G RAN Throughput Troubleshooting

Contents Page Peak Throughput calculation

General Principles for Troubleshooting Rate issue

Forward Troubleshooting Methods for Rate issue

Reverse Reasoning of Rate issue

Peak Rate Calculation Method
DL
Type Slot Type Slots/s TBS Comment
PDCCH: Each slot occupies 1-2 symbols in the front. Each downlink slot is available.
Normal D A TBSA PDCCH+DMRS 1CCE = 6REG = 6PRB; Aggregation Level: 1,2,4,8,16; In the figure, the PDCCH uses
one OFDM symbol as an example, occupying 270 RBS and a total of 90 CCES.
Normal D+SSB B TBSB DMRS for PDSCH: front-loaded DMRS and additional DMRS; Each downlink slot
has a peak RANK4 scenario, DMRS Type2, 1+0, and occupies eight RE/PRBs. In
Normal D+CSI C TBSC peak RANK8 scenarios, DMRS TYPE2, 2+0, occupies 16 RE/PRBs. Common mobility
DL test scenario, DMRS Type2, 1+1
Normal D+TRS D TBSD
By default, the CSI-RS single-user period is 40 ms, and the current 8Port uses the
Normal S E TBSE PDCCH+DMRS+GAP+SRS pattern 6, 4Port to use pattern 4. Send the packets alternately on slot7 and slot17.
Normal S+SSB F TBSF PSS+SSS+PBCH, is short for SSB, . The default period is 20 ms, occupying 20 RBS.
The 19A/B uses the CaseC pattern. The 64TRX & 32TRX subframe configuration 4:1
Normal U G TBSG PUCCH+DMRS supports a maximum of seven beams. The 8:2 subframe configuration supports a
UL maximum of eight beams, and the 8TRX uses four beams by default.
Normal U+PRACH H TBSH TRS: Cell-level signal. The default period is 20 ms. In peak scenarios, 40 ms is
recommended. It is located in slot5&6 and occupies two symbols (currently,
DL Peak Throughput:A*TBSA+B*TBSB+C*TBSC+D*TBSD+E*TBSE+F*TBSF
symbols 4 and 8). Each symbol is divided into four frequencies in the frequency
UL Peak Throughput:G*TBSG+H*TBSH domain, and the cells are staggered by mode 6.
PDSCH: Downlink data channel
Calculation Procedure
UL
 Step 1: Understand the definition of the upstream and downstream Sounding RS. The time domain location is located in the last two symbols of the
signals/channels, including: Time frequency domain location, period. Self-contained subframe. Each S subframe;
DMRS for PUSCH. The Front-loaded DMRS occupies the 1-2 symbol, and is located
 Step 2: According to the timing diagram, the overhead (signal or at the beginning of the PUSCH.
channel) contained in the slot is classified. The number of slots in the 1s Long PUCCH. By default, 14 symbols are used in the time domain. In the frequency
domain, the default Format1 occupies four RBS, and the Format3 occupies 16 RBS.
is measured based on the configuration period of each channel. The total number of RBS is 20. In the figure, the Long PUCCH time domain
occupies 14 symbols, and the frequency domain occupies 20 RBS. This feature is
 Step 3: Calculate the TBS of each slot. For details, see TS38.214.5.1.3.
recommended for low frequency bands and has good coverage performance.
 Step 4: Calculate the throughput = A slot number * A slot TBS + … Every U Slot has it.
PRACH (Short Format), subframe ratio 4:1 can be used only in short format C2 (138
number of + B slots * B slot TBS
root sequences), and 8:2 may be in format 0 (839 sequence, preferred) and C2.
PUSCH: Uplink data channel
Downlink Peak Throughput calculate
Uplink Peak Throughput calculate
Contents Page Peak rate calculation

General Principles for Troubleshooting Rate issue

Forward Troubleshooting Methods for Rate issue

Reverse Reasoning of Rate issue

Factors Affecting 5G Data Transmission "E2E"
The E2E factor is the basis for locating data transmission problems. You need to know how various factors affect the variables (Grant,
RB, MCS, rank, and BLER) in 5G uplink and downlink rate calculation.

12) TCP
6) Alarm
4) SINR/CQI/RI/SRS Windows/Thread/RTT
7) Parameter
5) Channel Condition 11) QCI/AMBR Hardware Performance
8) Channel Calibration
APP Server
3) UE Capacity HSS
RB/Modulation/Feature
gNodeB BBU

Router

CPE X2
9) Transmission Packet loss
Switch Firewall
MME/UGW

10) Transmission Packet Loss and OutofOrder/Bandwidth

1) TCP Windows/Thread/RTT/MTU
2) Hardware Performance eNodeB BBU

Factors 1, 2, 3, 6, 7, 9, 10, 11, 12, Grant, RB, 4, 5, 6, 7, and 8 affect the MCS, BLER, and rank.
Description of Probe Counter Observation
Data Collection Guide for throughput issues
Attributi
No. Log Type Precautions for Collecting Detailed Content Parameters of Content & Tool Remarks
on
1 5G 5G X2 standard interface log The collection period is the same as that of the 4G UU/S1/X2 standard interface. U2020/WebLMT
5G Main Control Board One-
2 5G Collect one-click logs at least 20 minutes after the standard interface logs are collected. U2020/WebLMT
Click Log
Huawei UEs must provide OMT
3 Ue Terminal logs Huawei UE: OMT tracing and Probe logs OMT/Probe and Probe tracing. For other UEs,
they must also be traced.
CPE mirroring packet Connect the PC to the CPE mirroring port, enable CPE port mirror, start Wireshark to capture packets, select the
4 5G Wireshark
capture corresponding NIC, and start the traffic test.
5 5G 5G IFTS tracing 1. Select L2, deploy 490/537/776/777/2133/3201, and collect the same time period as the 5G X2 standard interface trace. U2020/WebLMT Note: You only need to select one
1. Select L2, deploy 490/537/776/777/2133, and collect the same time period as the 5G X2 standard interface trace. 2. The of the following tracing modes: 1.
5G 5G Cell DT Tracing (Optional) U2020/WebLMT In the case of multi-user scenarios
CELLDT log is large. For cells with poor KPIs, only TOP1 cells are traced.
on the live network, you are
5G User Detail Trace Tracing advised to use Cell DT tracing. 2.
5G 1. Select L2, deploy 490/537/776/777/2133/3201, and collect the same time period as the 5G X2 standard interface trace. U2020
(Optional) If a single user test or VIP user
6 complaint problem occurs, you
5G GTPU Detail Trace Tracing are advised to use User Detail
5G In the navigation tree of the U2020, choose Base station Device and Transport->Information Collection-> GTPU Detail Trace. U2020 Trace to trace the trouble ticket
(Optional)
user. This tracing requires User
Trace ID.
(Optional) 5G MML Query DSP LICINFO:FUNCTIONTYPE=gNodeB; DSP LICENSE:FUNCTIONTYPE=gNodeB; LST LICENSE:;DSP ETHPORT:; DSP IPSTAT:; DSP
7 5G U2020/WebLMT
Result IPPMSESSION:;
In the main window of the WebLMT, click the Monitor tab. In the navigation tree, choose Monitor->FFT Frequency Scanning.
(Optional) FFT Frequency
8 5G Double-click FFT Frequency Scanning. On the displayed page, select Broadband Online Spectrum Scan or Broadband Offline Web LMT
Scanning
Spectrum Scan as required.
User performance monitoring during problem collection: Beam Space Monitoring; User Common Monitoring; Cell
5G Throughput Monitoring
9 5G performance monitoring: a) General Throughput Monitoring;b) HARQ Statistic Monitoring;c) DRB Statistic Monitoring; d) U2020
(Optional)
Users Statistic Monitoring;
(Optional) Packet Capture on
5G Start the Wireshark to capture packets on the PC, select the corresponding network adapter, and start the traffic test. Wireshark
the PC of the UE
10
(Optional) S1 Local Mirroring Connect the PC to the S1 mirroring port of the BTS, enable the port redirection function of the BTS, start the Wireshark to
5G Wireshark
Packet Capture capture packets, select the corresponding network adapter, and start the traffic test.
DSP GNBUEBASICINFO
11 5G Querying Basic gNodeB UE Information (Introduced in 19B) Web LMT
(optional)
4G UU/S1/X2 Standard
12 4G Deselect Paging messages and collect data for one hour during the problem period. U2020/WebLMT
Interface Log (Optional)
4G Main Control Board One-
13 4G Collect one-click logs at least 20 minutes after the standard interface logs are collected. U2020/WebLMT
Click Log (Optional)
Contents Page General Principles for Troubleshooting Rate issue

Forward Troubleshooting Methods for Rate issue

Reverse Reasoning of Rate issue

Forward Check Content
Software Version

Terminal and portable capabilities

SIM card registration

UDP packet injection command

TCP packet injection command

TCP configuration

FTP configuration

Alarm and channel calibration

Parameter check
Checking the Software Version

1. Ensure that the NR, LTE, tue, and CPE versions are the recommended versions and the versions of
different NEs match.
2. For details about the version policy, see the following link:
Base station:
http://3ms.huawei.com/hi/group/3402967/thread_7219029.html?mapId=8971623&for_statistic_from=a
ll_group_forum
Probe and CPE:
http://3ms.huawei.com/hi/group/2026401/thread_7516985.html?mapId=9288617&for_statistic_from=a
ll_group_forum&l=zh-cn
Terminal and portable capabilities
Ue capability:
Only Huawei tue, CPE, and CPE can be tested in the current phase. Compared with the tue, the CPE supports only 144RB, uplink
136RB, and uplink discontinuous scheduling. In this case, check whether the terminal capability supports the current test case.

Terminal
CPE1.0 CPE PRO Mobile phone
Type
Frequenc n78 (supporting n41
n78/n79/n41 n41/n77/n78/n79
y band commissioning)
Bandwidt
40M/60M//80M/100MHz 40M/80M/100MHz 40M/50M/60M/80M/100MHz
h
DL MIMO 2*4 MIMO: n78/n79/n41 4*4 MIMO: n78 4*4 MIMO: n41/n77/n78/n79
SA: 2*2 MIMO
UL MIMO 2*2 MIMO Current NSA: 1*1 2*2 MIMO
MIMO
DL/UL
modulati 256QAM/64QAM 256QAM/256QAM 256QAM/256QAM
on
This document is for reference only. For details, see the terminal specifications.
Commercial terminal commissioning:
1. Commissioning Guide for Commercial Terminals
(Huawei, Samsung, and Qualcomm)
http://3ms.huawei.com/km/blogs/details/6009255

2. CPE Pro Commissioning Guide

http://3ms.huawei.com/km/blogs/details/5950587
Terminal and portable capabilities
Reco
Scenari Networ Recommended Configuration
mme Remarks
o king Configuration Description
nded
It is not recommended
1. Minimum configuration
that a single laptop be
of the maintenance and
used. 1. The
test laptop: i5-4310U,8GB
Reco maintenance and test
Downli Dual memory, 512G SSD;
mme data of the CPE is lost
nk TCP laptops
2. Minimum configuration nded on a single laptop. 2.
of the service laptop: i7- The operating system is
6600U,8GB*2 memory, stalling in high rate
512G SSD scenarios.
It is not recommended
The laptop is that a single laptop be
recommended for the used. 1. The
1. Minimum configuration
serviceability baseline maintenance and test
of the maintenance and
of the PA. It is data of the CPE is lost
test laptop: i5-4310U,8GB
recommended that the on a single laptop. 2.
memory, 512G SSD; Reco
Downli Dual laptop be configured in The operating system is
mme
nk FTP laptops 2018. If you want to stalling in high rate
nded
test the mode of saving scenarios.
2. Recommended and downloading files,
configuration for the you must use the You are not advised to
service portable computer: recommended save the file during
i7-8650U,8GB*2 memory, configuration or above. download.
512G SSD
SIM card registration
The registration information of the core network contains two important information: AMBR and QCI
 AMBR restricts the Non-GBR rate of the UE.
 QCI: User QCI information is associated with PDCP, RLC, and MAC parameters (including the number of SN bits and RLC
modes) at the base station side, affecting user throughput.

UE AMBR/QCI information can be traced on the S1AP_INITIAL_CONTEXT_SETUP_REQ (NSA) or X2 interface SgNB_Add_Req

(NSA) or NGAP_INIT_CONTEXT_SETUP_REQ (SA) through the S1 interface.
TCP packet injection command
Max TCP Throughput= Window Size/RTT * Thread number
 Window Size is the size of the TCP window buffer. It is divided into the sending window and receiving window. The size of the two sides is small. The
larger the window size, the stronger the data cache capability.
 RTT is the period from the time when a TCP packet is sent to the time when the sending window receives the acknowledgment packet of the packet. The
shorter the RTT, the more quickly the sending window clears the sending buffer and fills in the new data to be sent.
 Number of Thread number threads: When the Win Size and RTT are certain, increasing the number of threads increases the TCP rate.
You are advised to use Iperf packet injection to evaluate TCP performance.
This parameter specifies the +4 thread of the 4M sending and receiving window. It is estimated based on the 5G 30 ms RTT delay and supports a
maximum of 4 Gbit/s TCP rate.

The procedure for TCP packet injection is as follows:

Step 1: Run the following command on the receive end: iperf-s-w4M-p5001–i1
 -s indicates that the server functions as the receive end.
 -w 4M indicates the window size 4M. Unit: Byte B
 -p indicates the receive port.
 -i 1 one report per second
Step 2: Run the iperf –B xx.xx.xx.xx –c xx.xx.xx.xx –p 5001 –P 4 –t 99999 –i 1 –w 4M –l 1400 –N command on the transmit end.
 -B Bind the sender IP address (if the sender has multiple IP addresses).
 -c: Indicates the IP address of the receive end.
 -p port address, which must be the same as that on the receive end.
 -P Number of concurrent threads. It is recommended that the number of threads be less than or equal to 6.
 -t runtime;
 -i statistics are displayed every second.
 -w Send window 4M;
 -l buffer length;
TCP configuration
 Recommended configurations for the TCP packet injection server: CPU 64 bit:
8 cores; Memory: 64G; 10G network adapter: *2 (one backup)
1. TCP window optimization:
Run the following command to modify the configuration:
 Disable the heuristics function.
netsh int tcp set heuristics disabled
 The TCP auto tuning is optimized.
netsh int tcp set global autotuninglevel=normal
When TCP Auto-Tuning is set to OFF, the receiving window of the initiator
of the TCP connection is fixed as follows: 65535;
When TCP Auto-Tuning is enabled, the receiving window of the initiator of
the TCP connection is =window size value * window size scaling.

2. MTU optimization
 If the MTU is set too large, fragments are generated (generally 1500B by default), increasing
the probability of packet loss, disorder, and delay.
 MTU optimization: You can use the MTURoute tool to measure the maximum size of the MTU
between the test terminal and the target server. Generally, you are advised to set this
parameter to 1400B.
 Enter netsh interface ipv4 set subinterface (network adapter name) mtu=1400
store=persistent and press Enter to change the network adapter MTU.
 Run the following command in the CMD command line:
Run the netsh interface ipv4 show subinterfaces command to check the MTU of each network
adapter.
FTP Configuration
 Recommended FTP server configuration: CPU 64-bit 8-core, memory 192G, 10G network adapter *2 (one backup),
solid state disk. Huawei RH2288 servers are recommended. The following table lists the hardware configurations.
Hardware Configuration The FTP Server network adapter buffer
is optimized as follows:
Model: RH2288 V3
Set the transmission buffer to 16384.
CPU: E5-2680v4 * 2
Memory: 8*32G
Set the receive buffer to 4096.
Hard disk: Samsung MZ-7LM4800(480GB, SSD, SATA6.0Gbps)* 3
RH2288 server
(RAID0 mode) The configuration information of the
FTP Server/Client registry is optimized.
NIC: 10G NIC *2 (one backup) DefaultSendWindow: 3f0000
Operating system: Win Server 2012 R2
TranSmitIoLength: 1f0000
TcpWindowSize: 3f0000
FTP Server if Filezilla is used, the recommended configuration is as follows: GlobalMaxTcpWindowSize: 3f0000
1. Set the number of Filezilla threads to 10 (in edit->setting->transfer->Maximum Simultaneous
Transfers). TCP window optimization in FTP
2. The Filezilla file is stored in the path where the SSD SSD is located. Server/Client Windows
3. It is recommended that the sending window be optimized. Both filezilla server options- a. Disable the heuristics function.
>Miscellaneous->Internal transfer buffer size and Socket buffer size are changed to 524288. netsh int tcp set heuristics disabled
b. Optimize the TCP auto tuning.
FTP Client: netsh int tcp set global autotuninglevel=normal
1. FTP Client network adapter buffer optimization: Set the transmission buffer to 2048 and the receive
buffer to 2048.
2. The Probe is recommended to perform the FTP free disk test to reduce the performance requirements
of the test terminal.
3. If the Filezilla is used as the client for FTP download, drag the file as much as possible. The number of
files to be dragged is related to the number of TCP download threads. The download path is the path
where the SSD SSD is located.
Alarm and channel calibration
1. The alarm list is shown in the attachment. For details about how to handle the alarm, see Operation and
Maintenance -> Fault Management ->3900 Series &5900 Series Base Station -> Alarm Management in the
product documentation.
Categ
Alarm Name Impact
ory
When the alarm severity is Major, X2-U and S1-U cannot carry services.
ALM-25954 User Plane Fault When the alarm severity is critical, the eNodeB cannot set up gNBS1 user-plane
Trans bearers for UEs. As a result, gNodeB services are affected.
missio If this alarm exists, the user plane of the link cannot perform normal services
n ALM-25952 User Plane Path Fault (such as S1-U and X2-U).
The data packets sent from the NE to the peer NE are discarded. As a result, the
ALM-25959 User Plane Path Excessive Packet Loss Rate
services carried by the user-plane path may fail.
The cell provided by the NR local cell TRP for which the alarm is generated
ALM-29871 NR Distribution Unit Cell TRP Service provides the available radio air interface capability for the customer.
Capability Degraded When the baseband detects that the uplink service data of the NR local cell TRP is
not synchronized, there is a possibility that UE access is abnormal.
When the RF input power of the port on the MERC board is too small or no power
RF is available, the downlink weak coverage or downlink output power is unavailable.
ALM-28754 RF Access Device Port Input Power
When the RF input power of the port on the MERC board is excessively high, the
Abnormal
downstream channel of the board port is disabled, services are interrupted, and
the service life of the MERC board is shortened. As a result, the MERC board is
damaged.
The radio air interface capability provided by the alarm cell for the customer
ALM-28751 Cell Capability Degraded
decreases.

2. Query the channel calibration result by running the following command on the NR base station side: DSP
NRLOCELLCHNCALIB. If channel calibration fails, manually calibrate the MML command. STR NRLOCELLCHNCALIB. If the
problem persists, handle the problem by referring to the 5G_RAN2.0 Troubleshooting Guide-Channel and Interference.

3. Check whether the counter N.Cell.Unavail.Dur.System is abnormal.

Parameter check and optimization
Downlink Key Parameters
Category Parameter ID Parameter Description
Ibler adjustment target value: Indicates the target value of initial transmission bit error convergence in outer-loop adjustment. The recommended value is 10,
NRDUCELLPDSCH.DlTargetIbler
that is, 10%.
BLER TRS Ratematch function switch. The value 1 indicates that the function is disabled, and the value 0 indicates that the function is enabled. This parameter
NRDUCellPdsch.RateMatchSwitch=TRS_RATEM
affects the PDSCH demodulation performance. Currently, the cpe does not support TRS multiplexing. If this parameter is set to 0, the TB size calculated by
ATCH_SW
the eNodeB is inconsistent with that calculated by the cpe. As a result, the PDSCH demodulation fails and the RBLER is high.
Indicates whether to enable the 256 selection table. The 64QAM or 256QAM table is recommended for PDSCH channels. It is recommended that this option
NRDUCELLALGOSWITCH.Dl256QamSwitch
be selected.
MCS NRDUCellPdsch.DlInitMcs Indicates the downlink initial MCS after the access and after the handover. The recommended value is 4.
Indicates the fixed downlink MCS index. 0: The parameter does not take effect. 1-29: Indicates that the downlink MCS index is fixed at 0 to 28. Recommended
NRDUCellRsvdParam.RsvdU8Param68
value: 0
NRDUCELLALGOSWITCH.MuMimoSwitch=DL_
Downlink MU switch: The MU-MIMO scenario is enabled, and other functions are disabled.
MU_MIMO_SW
NRDUCELLPDSCH.MaxMimoLayerNum Maximum number of MIMO layers: Maximum number of reuse layers for a cell in pairing scenarios, 8T8R:LAYER_4(4 Layers), Other:LAYER_16(16 Layers)
NRDUCELLPDSCH.DlDmrsConfigType Downlink DMRS type selection. Type1 is recommended.
NRDUCELLPDSCH.DlDmrsMaxLength Maximum symbol length of downlink DMRSs: Peak scenario 2SYMBOL (RANK8), other scenarios 1SYMBOL
Controls the number of downlink additional DMRS pilot symbols. The value can be NOT_CONF, POS1, or POS2. Peak scenario NOT_CONF, other POS1
NRDUCellPdsch.DlAdditionalDmrsPos
Rank NRDUCELLRSVDPARAM.RsvdU8Param47 Number of ports sent by the CSIRS. The value of 0/1/2/3 is 4Port/2Port/4Port/8Port.
Downlink initial RANK after access and after handover. The initial RANK value range is [RANK1,RANK8]. It is recommended that this parameter be set to
NRDUCellPdsch.DlInitRank RANK1.
Indicates the fixed downlink rank. 0: This parameter does not take effect. If this parameter is set to a value ranging from 1 to 8, the downlink rank is fixed at 1
NRDUCellRsvdParam.RsvdU8Param67
to 8. Recommended value: 0
NRDUCellAlgoSwitch.SuMimoMultipleLayerSw
Multi-stream switch for a single user. It is recommended that this switch be turned on.
=DL_SU_MULTI_LAYER_SW
Indicates whether to enable the rank adaptation solution for SRS resources. 0/1/2: The parameter does not take effect. By default, the spectral efficiency,
NRDUCellRsvd.RsvdParam44 spectral efficiency, and border protection rank adaptation solution are used by default. Recommended value: 0
NRDUCellAlgoSwitch.AdaptiveEdgeExpEnhSwit Downlink SRS power and PMI right adaptation switch: When this switch is turned off, the fixed weight solution is used. When this switch is turned on,
ch=DL_PMI_SRS_ADAPT_SW adaptive selection is performed between SRS/PMI/DFT weights. Recommended
PMI/SRS weight selection: 0:PMI rights; 1:SRS rights. When the weight adaptation switch is turned off, the value of this parameter is fixed between the weight
RANK NRDUCellPdsch.FixedWeightType
and the open-loop power.
/MCS
NRDUCellCsirs.TrsPeriod TRS period. The value 0 indicates that TRS is disabled. TRS period. The recommended value is 20 ms.
The UE-specific SRS period is fixed. 0/1/2/3/4/5/6/7 represents 5/10/20/40/80/160/320/640 slots. The recommended value is 4, that is, 80 slots.
NRDUCellRsvd.RsvdParam37
RB NRDUCellRsvd.RsvdParam67 Indicates the scheduling policy of the CPE. 0/1/2/3: The parameter does not take effect. /272RB/144RB/ Adaptive ICIC is enabled.
Indicates the PDCCH aggregation level. The value 0/1/2/3/4 indicates adaptive /2/4/8/16. If the aggregation level is too low, DCI missing detection is
Grant
NRDUCellRsvdParam.RsvdU8Param7 recommended. It is recommended that the aggregation level be adaptive.