33.data Transmission Problem
33.data Transmission Problem
Problem Analysis
4. Typical Cases
Both NR and LTE support flexible allocation of time-frequency resources in a specified bandwidth by using
frequency division multiplexing and time division multiplexing. However, unlike LTE, NR can work in both high and
low frequency bands, and allows for multiple subcarrier spacings (SCSs), such as 15 kHz, 30 KHz, 60 kHz, 120 kHz,
and 240 kHz. NR also provides a larger maximum bandwidth in a carrier than LTE, as listed in the following table
(3GPP TR 38.211).
μ SCS Number of Symbols per Slot Number of Slots per Frame Number of Slots per Subframe
0 15 14 10 1
1 30 14 20 2
2 60 14 40 4
3 120 14 80 8
4 240 14 160 16
4. Typical Cases
In-depth understanding of the E2E factors affecting 5G data transmission is the basis for
identifying data transmission faults. You need to learn how different factors affect the
variables (such as the grant count, RB quantity, MCS index, rank value, and BLER) in the 5G
uplink and downlink rate calculation.
2) Hardware Performance
Factors 1, 2, 3, 6, 7, 9, 10, 11, and 12 affect the variables such as the grant count and RB quantity, and factors 4, 5, 6, 7,
and 8 affect the variables such as the MCS index, BLER, and rank value.
Resource scheduling insufficiency may involve RBs or grants. UDP packet injection on the
base station side can be used to determine whether the resource scheduling insufficiency is
caused by a TCP fault or an air interface fault.
Average
Mechanical MCS
Test Time Downlink Rank CQI SSB SINR SSB RSRP CSI SINR CSI RSRP
Downtilt Index
Rate
December 8 0 474 Mbit/s 3.99 17.2 12.6 34.5 -72 36.5 -71
Copyright © Huawei Technologies Co., Ltd. All rights reserved. ThPMI Page 29
Weight Adaptation Algorithm (2)
When the SRS-based weight is used, the base station uses the rank adaptation algorithm to
determine the final rank value to be used.
When the SRS SINR is less than the value of ThPMI, the PMI-based weight is used and the
rank adaptation algorithm does not take effect. The RI reported by the UE is directly used.
DFT-based weights are used when the PMI is not reported, a handover is just performed, or
channel calibration fails. The rank value is selected based on the RI reported by the UE
according to the following rules:
If RI in the CSI reported by the UE is 1, rank 1 is used.
If RI in the CSI reported by the UE is 2 or 3, rank 2 is used.
If RI in the CSI reported by the UE ranges from 4 to 8, rank 4 is used.
Adaptation between SRS-based weights and PMI-based weights needs to be enabled on the
base station.
4. Typical Cases
Solution
The low rank is caused by the inappropriate test
location. Therefore, change the test location (for
example, under the tree in this example) where there
are obstacles around the antenna and the SINR is
favorable (greater than 28 dB). The rank value increases
to 4.
Analysis
TTI data analysis results show that system information (SIB1) subframe contains a large number of
error codes related to CCE allocation failures.
Reason for CCE allocation failures: In RAN2.1, SIB1 is introduced in NSA mode. When data services and
SIB1 are scheduled at the same time, CCE resources are insufficient, causing the scheduling to fail.
According to the PDCCH tracing result, SIB1 is located in slots 10 to 17 of an even-numbered frame,
and the common DCI aggregation level is 8 (48/6 = 8). For details, see the table on the next page.
If a slot may be used to transmit uplink DCI, some CCEs are reserved for the uplink DCI transmission.
The reservation percentage is specified by NRDUCellPdcch.UlMaxCcePct parameter, which is 50% by
default. According to the current specifications of CPE 1.0, a maximum of 96 CCE RBs can be processed
in one PDCCH symbol, meaning that 48 (96 x 50%) CCE RBs are reserved for downlink scheduling.
However, the common DCI in SIB1 always occupies 48 CCE RBs (aggregation level 8 x 6 RBs per CCE).
As a result, no downlink CCE is available for user data scheduling, and downlink scheduling fails.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 50
Case 2: Low Rate Due to Insufficient Downlink
Grants (4)
According to verification on the live network, changing the value of NRDUCellPdcch.UlMaxCcePct to
33 (that is, the CCE reservation percentage for uplink scheduling is 33%) can prevent scheduling
failures in single-user scenarios.
In addition, run the following command with related parameter settings so that the number of times
the base station schedules UEs reaches 1600 per second in the areas where the problem occurs
MOD NRDUCELLPDSCH: NrDuCellId=0, RateMatchSwitch=PDCCH_RATEMATCH_SW-1; MOD NRDUCELLPDCCH:
NrDuCellId=0, OccupiedRbNum=2;
Principle analysis: In RAN2.1, when PDCCH rate matching is enabled (that is, the PDCCH and PDSCH share
symbols) and the number of CCE RBs occupied by UEs is configured (Actual effective value = Configured value x
12), the allocated CCEs that are in the CCE range for public resource scheduling are not counted in the
measurement of the uplink-downlink CCE ratio. Therefore, when a slot is used to transmit SIB messages, the
downlink data scheduling in the slot can also succeed.
Solution
Change the uplink-downlink CCE ratio (it has no impact on a single UE with downlink-only services but affects
uplink scheduling in other scenarios).
Final solution: The uplink-downlink CCE ratio adaptation function will be supported in later versions.
Solution
If the channel calibration failure is caused by strong external interference, check for external interference.