Channel State Management (ERAN16.1 - 01)

eRAN
Channel State Management

Feature Parameter Description
Issue 01
Date 2020-05-21
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Channel State Management Feature Parameter
Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN16.1 01 (2020-05-21)..................................................................................................................................................1
1.2 eRAN16.1 01 (2020-03-30)..................................................................................................................................................1
1.3 eRAN16.1 Draft A (2020-01-15)........................................................................................................................................ 2
2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Applicable RAT......................................................................................................................................................................... 4
2.3 Features in This Document.................................................................................................................................................. 4
2.4 Feature Differences Between FDD and TDD................................................................................................................. 4
3 Overview....................................................................................................................................6
3.1 CSI Reporting Modes.............................................................................................................................................................. 6
3.2 Periodic and Aperiodic CQI Reporting..............................................................................................................................8
4 CQI Reporting.........................................................................................................................10
4.1 Principles.................................................................................................................................................................................. 10
4.1.1 Periodic CQI Reporting.................................................................................................................................................... 10
4.1.2 Aperiodic CQI Reporting................................................................................................................................................. 11
4.1.3 Optimized CQI Detection................................................................................................................................................12
4.1.4 NPREO Constant Optimization (FDD)....................................................................................................................... 12
4.2 Network Analysis.................................................................................................................................................................. 14
4.2.1 Benefits................................................................................................................................................................................. 14
4.2.2 Impacts.................................................................................................................................................................................. 15
4.3 Requirements......................................................................................................................................................................... 21
4.3.1 Licenses................................................................................................................................................................................. 21
4.3.2 Software................................................................................................................................................................................21
4.3.3 Hardware.............................................................................................................................................................................. 22
4.3.4 Others.................................................................................................................................................................................... 22
4.4 Operation and Maintenance............................................................................................................................................. 22
4.4.1 Data Configuration (FDD).............................................................................................................................................. 22
4.4.1.1 Data Preparation............................................................................................................................................................ 22
4.4.1.2 Using MML Commands............................................................................................................................................... 25
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 26
4.4.2 Data Configuration (TDD)..............................................................................................................................................26
Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. ii

eRAN

4.4.3 Activation Verification..................................................................................................................................................... 28
4.4.4 Network Monitoring......................................................................................................................................................... 30
5 CQI Reporting Optimization...............................................................................................33

5.1 Principles.................................................................................................................................................................................. 33
5.1.1 Periodic CQI Reporting Optimization (FDD)............................................................................................................33
5.1.2 Aperiodic CQI Reporting Optimization...................................................................................................................... 33
5.1.2.1 UEs in the Initial Access............................................................................................................................................... 33
5.1.2.2 UEs Involved in Handovers......................................................................................................................................... 34
5.1.2.3 UEs with Compatibility Issues.................................................................................................................................... 34
5.2.1 Benefits................................................................................................................................................................................. 35
5.2.2 Impacts.................................................................................................................................................................................. 35
5.3 Requirements......................................................................................................................................................................... 35
5.3.1 Licenses................................................................................................................................................................................. 35
5.3.2 Software................................................................................................................................................................................36
5.3.3 Hardware.............................................................................................................................................................................. 36
5.3.4 Others.................................................................................................................................................................................... 36
6 CQI Adjustment..................................................................................................................... 44
6.1 Principles.................................................................................................................................................................................. 44
6.1.1 Downlink Target IBLER.................................................................................................................................................... 44
6.1.1.1 Fixed Configuration....................................................................................................................................................... 44
6.1.1.2 Adaptive Configuration................................................................................................................................................ 45
6.1.2 CQI Adjustment Period (FDD)...................................................................................................................................... 47
6.1.3 CQI Filtering Adjustment................................................................................................................................................ 47
6.1.3.1 Initial Filtered Value of Reported CQIs................................................................................................................... 47
6.1.3.2 CQI Filtering Based on Spectral Efficiency Optimization................................................................................. 47
6.1.3.3 CQI Filtering Optimization (TDD)............................................................................................................................ 48
6.1.4 Optimized CQI Adjustment Value (FDD).................................................................................................................. 48
Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
6.1.4.1 Initial CQI Adjustment Value (FDD)........................................................................................................................ 48

6.1.4.2 CQI Adjustment Step (FDD)....................................................................................................................................... 49
6.1.5 Optimized CQI Adjustment Value (TDD).................................................................................................................. 49
6.1.5.1 Initial CQI Adjustment Value (TDD)........................................................................................................................50
6.1.5.2 CQI Adjustment Step (TDD).......................................................................................................................................50
6.1.5.3 Optimized CQI Adjustment for Different UEs (TDD)........................................................................................ 51
6.1.5.4 CQI Adjustment Value Validity Optimization (TDD)......................................................................................... 52
6.2.1 Benefits................................................................................................................................................................................. 52
6.2.2 Impacts.................................................................................................................................................................................. 52
6.3 Requirements......................................................................................................................................................................... 53
6.3.1 Licenses................................................................................................................................................................................. 53
6.3.2 Software................................................................................................................................................................................53
6.3.3 Hardware.............................................................................................................................................................................. 54
6.3.4 Others.................................................................................................................................................................................... 54
7 Parameters.............................................................................................................................. 62
8 Counters.................................................................................................................................. 63
9 Glossary................................................................................................................................... 64
10 Reference Documents........................................................................................................ 65
Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN16.1 01 (2020-05-21)

This issue includes the following changes.
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added the mutual impact None FDD ● 3900 and 5900

between periodic CQI TDD series base
reporting and energy stations
saving based on proactive ● DBS3900
scheduling. For details, see LampSite and
4.2.2 Impacts. DBS5900
LampSite
● BTS3911E
Editorial Changes
None
1.2 eRAN16.1 01 (2020-03-30)

This issue does not include any changes.
Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Description 1 Change History
1.3 eRAN16.1 Draft A (2020-01-15)

This issue introduces the following changes to eRAN15.1 01 (2019-06-06).
Technical Changes
Change Description Parameter RAT Base Station Model
Change
Changed the name of None FDD ● 3900 and 5900

U2020 to MAE-Access TDD series base stations
and the name of CME ● DBS3900 LampSite
to MAE-Deployment. and DBS5900
LampSite
● BTS3911E
Editorial Changes
Revised descriptions in this document.

eRAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a
description does not apply to all RATs, the specific RAT that it does apply to will
be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-
MIMO", "TDD cells" indicates that this function cannot be used in non-TDD cells.

eRAN
2.2 Applicable RAT

This document applies to FDD/TDD.
2.3 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Chapter/Section
LBFD-002031 Aperiodic CQI 4 CQI Reporting

Reporting
LBFD-060101 Optimization of CQI 5 CQI Reporting

Reporting Optimization
LBFD-00101501 CQI Adjustment 6 CQI Adjustment
This document describes the following TDD features.
Feature ID Feature Name Chapter/Section
TDLBFD-002031 Aperiodic CQI 4 CQI Reporting

Reporting
TDLBFD-00101501 CQI Adjustment 6 CQI Adjustment
2.4 Feature Differences Between FDD and TDD

FDD Feature TDD Feature Difference Chapter/Section
LBFD-002031 TDLBFD-002031 In FDD, aperiodic 4 CQI Reporting

Aperiodic CQI Aperiodic CQI CQI reporting can
Reporting Reporting be triggered at
intervals for UEs in
FDS mode.
However, this
function does not
apply to TDD.

eRAN
FDD Feature TDD Feature Difference Chapter/Section
LBFD-060101 None This feature is not 5 CQI Reporting

Optimization provided in TDD. Optimization
of CQI FDD supports both
Reporting periodic and
aperiodic CQI
reporting
optimization.
However, TDD
supports only
aperiodic CQI
reporting
optimization.
LBFD-001015 TDLBFD-0010150 CQI adjustment 6 CQI Adjustment

01 CQI 1 CQI Adjustment period
Adjustment configuration
applies only to
FDD.
Optimization of
reported CQIs
applies only to
TDD.

eRAN
Description 3 Overview
3 Overview
UEs report channel state information (CSI) to the eNodeB. This CSI includes a
channel quality indicator (CQI), a precoding matrix indication (PMI), and a rank
indication (RI). The information is used for downlink user plane scheduling and
downlink multiple-input multiple-output (MIMO).
CQI
A CQI is a measure of channel quality. The eNodeB automatically selects a
modulation and coding scheme (MCS) for data transmission to the UE based on
this measure.
PMI
A PMI indicates a precoding matrix. The eNodeB performs closed-loop MIMO
transmission to the UE based on this indicator.
RI
An RI is a rank that the eNodeB uses to determine the number of spatial
multiplexing layers for the UE.
3.1 CSI Reporting Modes

CSI reporting modes depend on CQI, PMI, and RI reporting modes:
● The specific CSI reporting modes are described in Table 3-1.
● RIs and CQIs/PMIs are reported in different subframes in periodic CSI
reporting mode. RIs and CQIs/PMIs are reported in the same subframes in
aperiodic CSI reporting mode.

eRAN
Table 3-1 CSI reporting modes

CSI CQI Reporting PMI Periodic or Supporting
Reporting Mode Reporting Aperiodic UEs
Mode Mode
1-0 Wideband None Periodic All UEs
1-1 Wideband Wideband Periodic
1-2 Wideband Sub-band Aperiodic
2-0 Wideband CQI None Periodic UEs with the

reporting, or corresponding
optimum sub- capabilities
band CQI
reporting at a
larger granularity
Wideband CQI None Aperiodic

reporting, or UE-
selected sub-
band CQI
reporting at a
smaller
granularity
2-1 Wideband CQI Wideband Periodic

reporting, or
optimum sub-
band CQI
reporting at a
larger granularity
2-2 Wideband CQI Sub-band Aperiodic

reporting, or UE-
selected sub-
band CQI
reporting at a
smaller
granularity
3-0 Wideband CQI None Aperiodic All UEs

reporting, or all
sub-band CQI
reporting at a
larger granularity
3-1 Wideband CQI Wideband Aperiodic

reporting, or all
sub-band CQI
reporting at a
larger granularity

eRAN
CSI CQI Reporting PMI Periodic or Supporting

Reporting Mode Reporting Aperiodic UEs
Mode Mode
3-2 Wideband CQI Sub-band Aperiodic UEs in

reporting, or all compliance
sub-band CQI with 3GPP
reporting at a Release 12 or
larger granularity later
Table 3-2 lists the CSI reporting modes supported by Huawei eNodeBs in different
MIMO transmission modes.
Table 3-2 CSI reporting modes for different MIMO transmission modes
Transmission Periodic CSI Reporting Mode Aperiodic CSI Reporting

Mode Mode
TM1 1-0 3-0
TM2 1-1 3-0
TM3 1-0 3-0
TM4 1-1 1-2 (FDD only)

3-1
3-2 (FDD only)

3-1
3-2 (FDD only)
TM7 (TDD 1-0 3-0

only)
TM8 (TDD 1-1 3-1

only)

3-1
3-2 (FDD only)
3.2 Periodic and Aperiodic CQI Reporting

CQIs can be reported periodically or aperiodically. CQI reporting is configured the
same way as CSI reporting.
Figure 3-1 illustrates how the eNodeB selects a CQI reporting mode for a
scheduled UE.

eRAN
● For a UE in frequency selective scheduling (FSS) mode, the eNodeB selects

aperiodic CQI reporting.
● For a UE in frequency diversity scheduling (FDS) mode, the eNodeB selects
periodic or aperiodic CQI reporting.
NOTE
If the periodic CQI reporting time conflicts with the aperiodic CQI reporting time, only
aperiodic CQI reporting is triggered.
For details about FSS and FDS, see Scheduling.
Figure 3-1 CQI reporting mode selection for UEs in FSS and FDS modes

eRAN
Description 4 CQI Reporting
4 CQI Reporting
4.1 Principles
In periodic mode, the reporting intervals, reporting modes, and time-frequency
resources are configured in the CQI-ReportConfig RRC IE.
● When there is no uplink data transmission, CQIs are reported over the PUCCH.
● When there is uplink data transmission, CQIs are reported over the PUSCH.
In aperiodic mode, the reporting modes are specified in uplink scheduling and
CQIs are reported over the PUSCH.
● When the UE has data to be scheduled for uplink initial transmission, CQIs are
reported in associated aperiodic CQI mode.
● When the UE has no data to be scheduled for uplink initial transmission, CQIs
are reported in CQI-only mode.
The CQI-only mode increases both uplink overhead and uplink interference. To
minimize these adverse impacts, set the CellUlschAlgo.AperiodicCsiUlTxMode
parameter to specify the transmission mode of aperiodic CQIs on the PUSCH.
● If this parameter is set to CsiOnly and there is aperiodic CQI reporting, the UE
can immediately report CQIs in CQI-only mode or in associated aperiodic CQI
mode.
● If this parameter is set to CsiWiUlService and there is aperiodic CQI
reporting, the UE cannot immediately report CQIs in CQI-only mode if the UE
has no data to be scheduled for uplink initial transmission. This can reduce
the number of times of aperiodic CQI reporting in CQI-only mode and
decreases uplink interference. However, this transmission mode is not as
prompt as aperiodic CQI reporting in CQI-only mode. In this case, the
downlink initial block error rate (IBLER) slightly increases when uplink data
services of the UE are sparse.
4.1.1 Periodic CQI Reporting

The periodic CQI reporting interval is controlled by the
CellCqiAdaptiveCfg.CqiPeriodAdaptive parameter.

eRAN
● If the parameter is set to ON, the reporting interval is adjusted based on the
PUCCH load. When the load is light, a short interval is used; when the load is
heavy, a longer interval is used.
In an FDD cell, the periodic CQI reporting interval varies across the range of
[CellCqiAdaptiveCfg.MinCqiPeriod, 160 ms].
In a TDD cell, the periodic CQI reporting interval is adjusted in the range of
[20 ms, 160 ms].
● If this parameter is set to OFF, the reporting interval is a fixed value specified
by the CellCqiAdaptiveCfg.UserCqiPeriod parameter.
4.1.2 Aperiodic CQI Reporting

Aperiodic CQI reporting allows the eNodeB to obtain more current downlink
channel quality and increase downlink transmission rates. However, aperiodic CQI
reporting consumes additional PDCCH resources. It is recommended that the
CellPdcchAlgo.PdcchSymNumSwitch parameter be set to ECFIADAPTIONON to
reduce the number of symbols used by the PDCCH and increase downlink
transmission rates.
Configurations for aperiodic CQI reporting are different for UEs in FSS and FDS
modes.
UEs in FSS Mode

Aperiodic CQI reporting is triggered at intervals configured for UEs in FSS mode.
The interval is configured using the CellDlschAlgo.FSUEAperCQITrigPeriod
parameter.
The CQIs that are aperiodically reported are only valid for a period of time
specified by the CellDlschAlgo.FSUESbCQIValidityPeriod parameter. If a UE in
FSS mode does not use the reported resources within this period of time, these
CQIs are considered invalid.
If this parameter, which controls the validity period, is set to a value at least equal
to the value used for the triggering period
(CellDlschAlgo.FSUEAperCQITrigPeriod), then FSS is more likely to be selected
for the UEs.
When smart control for frequency selective scheduling takes effect, the triggering
interval and validity period of aperiodic CQI reporting for UEs in FSS mode are
adaptively adjusted but not specified by CellDlschAlgo.FSUEAperCQITrigPeriod
or CellDlschAlgo.FSUESbCQIValidityPeriod.
UEs in FDS Mode

Aperiodic CQI reporting is not triggered for UEs in FDS mode if there is valid
periodic CQI reporting. Aperiodic CQI reporting is triggered in the following
situations:
● When there is no valid periodic CQI reporting in a period that is eight times
the periodic CQI reporting interval, aperiodic CQI reporting is triggered once.
● When there are no resources for periodic CQI reporting, aperiodic CQI
reporting is triggered every 160 ms.

eRAN
In FDD, aperiodic CQI reporting can be triggered at intervals for UEs in FDS mode.
This function is controlled by the EnAperiodicCqiRptSwitch option of the
CellAlgoSwitch.DlSchSwitch parameter. The interval is specified by the
CellDlschAlgo.FDUEEnhAperCQITrigPeriod parameter.
4.1.3 Optimized CQI Detection

False CQI detection is when the eNodeB detects a CQI but the UEs have not
reported any.
The eNodeB supports optimized CQI detection on the PUSCH and PUCCH, which
reduces the amount of false CQI detection on the network. This function is
controlled by the CellCqiAdjAlgo.CqiOptSwitch parameter.
● When the PUSCH_CQI_FALSE_DETECTION_SW option of this parameter is
selected, the amount of false CQI detection is reduced on the PUSCH.
● When the PUCCH_CQI_FALSE_DETECTION_SW option of this parameter is
selected, the amount of false CQI detection is reduced on the PUCCH.
4.1.4 NPREO Constant Optimization (FDD)

NPREO is an acronym of nomPDSCH-RS-EPRE-Offset, which is a field defined in
the CQI-ReportConfig information element (IE) since 3GPP Release 8. The NPREO
constant is used to compensate for PDSCH SINR estimation for non-TM9/TM10
UEs. The NPREO constant can be specified by the
CellDlpcPdschPa.NomPdschRsEpreOffset parameter.
● A larger NPREO constant results in a larger proportion of high ranks reported
by UEs and larger CQIs reported in the same rank.
● A smaller NPREO constant results in a smaller proportion of high ranks
reported by UEs and smaller CQIs reported in the same rank.
Properly set the NPREO constant to ensure that the CQIs and ranks reported by
UEs match PDSCH quality, thereby increasing downlink user-perceived rates.
The eNodeB supports the following two levels of NPREO constant optimization:
● Cell-level NPREO constant optimization: This function is enabled when the
CellDlpcPdschPa.CellNpreoAdjThreshold parameter is set to a value in the
range from 0 to 50 and disabled when the parameter is set to 255.
● UE-level NPREO constant optimization: This function is enabled when the
CellDlpcPdschPa.UeNpreoAdjThreshold parameter is set to a value in the
range from -2 to 20 and disabled when the parameter is set to 127.
The cell-level and UE-level NPREO constant optimization functions can be
simultaneously enabled. In this case, the two functions run independently.
Cell-Level NPREO Constant Optimization

After the cell-level NPREO constant optimization function is enabled, the eNodeB
automatically searches for the optimal cell-level NPREO constant. The eNodeB
tries different cell-level NPREO constant values. If the estimated UE throughput of
value A divided by that of value B minus 1 is greater than the
CellDlpcPdschPa.CellNpreoAdjThreshold parameter value, the eNodeB considers
that A is better than B. Once the optimal cell-level NPREO constant is determined,

eRAN
it is used to replace the CellDlpcPdschPa.NomPdschRsEpreOffset parameter

value.
NOTE
Due to real-time changes in network interference and load, the cell-level NPREO constant
optimization function starts to search for the optimal NPREO constant again in the latest
network environment one month after the last optimization.
UE-Level NPREO Constant Optimization

After the UE-level NPREO constant optimization function is enabled, the eNodeB
configures A3 measurement information for UEs in the cell. The eNodeB adjusts
the NPREO constant of a UE based on information such as A3 reports, neighboring
cell RSRP values, neighboring cell PCIs, and neighboring cell interference values.
When the CellDlpcPdschPa.UeNpreoAdjThreshold parameter is not set to 127,
the parameter value indicates the compensation value of UE-level NPREO
constant optimization.
Figure 4-1 shows the UE-level NPREO constant optimization process.
Figure 4-1 NPREO constant optimization process
The neighboring cell interference values are obtained by using a corresponding

algorithm of precise AMC. For details, see eMIMO (FDD).
If precise AMC and UE-level NPREO constant optimization are both enabled,
adjusting the CellDlschAlgo.IntrfFilterCoeff parameter value will affect the
neighboring cell interference values obtained in precise AMC and UE-level NPREO

eRAN
NOTE
The A3 offset is specified by the NCellDlRsrpMeasPara.NCellDlRsrpMeasA3Offset

parameter. The smaller the parameter value, the larger the range of non-cell-center areas
and the more the UEs for which the UE-level NPREO constant optimization function takes
effect.
For the exchange of interference information between inter-eNodeB neighboring cells, X2
or eX2 interfaces are required. If X2 interfaces are used, service coordination must be
supported in non-ideal backhaul mode.
4.2 Network Analysis
4.2.1 Benefits
eNodeBs increase downlink cell throughput based on periodic and aperiodic CQI
reporting.
Aperiodic CQI reporting, a supplement to periodic CQI reporting, provides real-
time UE channel states and increases downlink transmission rates.
For FDD, the gains of NPREO constant optimization are indicated by the User
Downlink Average Throughput.
The factors that affect the gains of NPREO constant optimization are as follows:
● PCI conflict: The larger the number of UEs in cells with PCI conflicts, the
higher the gains.
● Inter-site distance (ISD): The smaller the ISD, the denser the network, the
greater the inter-UE interference in the cell, and the higher the gains of
NPREO constant optimization.
● 2T/4T network: On a 4T network, NPREO constant optimization can
significantly increase the proportion of high ranks and offer high gains.
● eX2 interface: If it is configured, inter-eNodeB interference information can be
obtained. As a result, the function can take effect for more UEs, providing
higher gains.
● Proportion of TM9/TM10 UEs: NPREO constant optimization is mainly used to
adjust the estimated SINRs for non-TM9/TM10 UEs such as TM3/TM4 UEs.
The smaller the proportion of TM9/TM10 UEs, the higher the gains of NPREO
As UE-level NPREO constant optimization requires neighboring cell information
exchange, it is recommended that UE-level NPREO constant optimization be
enabled in continuously covered areas.
It is recommended that both cell-level and UE-level NPREO constant optimization
functions be enabled to maximize the overall gains when all the following
conditions are met. Under these conditions, when the optimal cell-level NPREO
constant is different from the CellDlpcPdschPa.NomPdschRsEpreOffset
parameter value, the User Downlink Average Throughput will increase by 1% to
5%.
● The ISD does not exceed 700 m in densely populated urban areas.
● The average downlink PRB usage in a day is greater than 20%.

eRAN
● The network is a 4T network in transmission mode 4 (TM4).
4.2.2 Impacts
Network Impacts
Aperiodic CQI reporting scheduled on the uplink in CQI-only mode occupies
PUSCH and PDCCH resources.
When the optimized CQI detection function is enabled, the average CQI value
increases slightly.
Average CQI value = (L.ChMeas.CQI.DL.0 x 0 + L.ChMeas.CQI.DL.1 x 1 +
L.ChMeas.CQI.DL.2 x 2 + L.ChMeas.CQI.DL.3 x 3 + L.ChMeas.CQI.DL.4 x 4 +
L.ChMeas.CQI.DL.11 x 11 + L.ChMeas.CQI.DL.12 x 12 + L.ChMeas.CQI.DL.13 x 13
+ L.ChMeas.CQI.DL.14 x 14 + L.ChMeas.CQI.DL.15 x 15)/∑(L.ChMeas.CQI.DL.0 to
L.ChMeas.CQI.DL.15)
For FDD, cell-level NPREO constant optimization proactively tries different NPREO
constant values. The downlink UE throughput may decrease by no more than 5%.
It takes at least one week for cell-level NPREO constant optimization to determine
the optimal NPREO constant. Therefore, the performance fluctuation lasts for
about one week.
UE-level NPREO constant optimization periodically measures the interference from
neighboring cells. If the interference changes greatly in the measurement period,
the accuracy of calculated interference will be affected. Consequently, the
performance of UE-level NPREO constant optimization will be affected and the
downlink user-perceived throughput may decrease. In addition, UE-level NPREO
constant optimization requires the UE to measure neighboring cell RSRP values
and report event A3 or A6 to the eNodeB. This consumes PDCCH CCE resources
and PUSCH RB resources and therefore affects uplink performance. The impact
increases with the growing number of UEs and the increased traffic volume of
uplink services. The number of used PDCCH CCEs can be observed using the
L.ChMeas.CCE.ULUsed.SRB and L.ChMeas.CCE.DLUsed.SRB counters.
NPREO constant optimization also causes other downlink cell KPIs to change,
including the proportion of high ranks, average CQI, average MCS index, PDSCH
IBLER, and PDSCH RBLER. For example, if the optimal cell-level NPREO constant is
greater than the CellDlpcPdschPa.NomPdschRsEpreOffset parameter value, the
proportion of high ranks reported by UEs will increase.

eRAN
Function Impacts
RAT Function Function Reference Description
Name Switch
FDD Energy saving SymbolPwrS Energy Energy saving based

TDD based on aving.TrigBn Conservation on proactive
proactive dlSchDlAvgPr and Emission scheduling may cause
scheduling bThld Reduction fluctuations in the
number of CQI and
rank reporting times.
If the
CellCqiAdaptiveCfg.C
qiPeriodAdaptive
parameter is set to
ON, the number of
UEs that report CQIs
and ranks at short
intervals decreases
and the number of
UEs that report CQIs
and ranks at long
intervals increases.
FDD Compact Cell.Customiz Compact When this function is

bandwidth edBandWidt Bandwidth enabled, the accuracy
hCfgInd (FDD) of neighboring cell
interference
calculation is affected
and the performance
of UE-level NPREO
constant optimization
is affected. The larger
the proportion of the
punctured RBs to the
RBs in the configured
LTE bandwidth, the
lower the gains of
NPREO constant
optimization.

eRAN

Name Switch
FDD LTE in-band Prb.DeployM NB-IoT Basics When this function is

deployment ode (FDD) enabled, the accuracy
of neighboring cell
interference
and the performance
of UE-level NPREO
NB-IoT RBs to the RBs
in the configured LTE
bandwidth, the lower
the gains of NPREO
FDD CDMA and AvoidCDMAI CDMA and When this function is

LTE Zero nterfSwitch LTE Zero enabled, the accuracy
Bufferzone option of the Bufferzone of neighboring cell
CellAlgoSwit interference
ch.AvoidInter calculation is affected
fSwitch and the performance
parameter of UE-level NPREO
downlink RBs shared
by LTE and CDMA to
the RBs in the
configured LTE
the gains of NPREO

eRAN

Name Switch
FDD GSM and LTE AvoidGeranIn GSM and LTE When this function is
Buffer Zone terfSwitch Buffer Zone enabled, the accuracy
Optimization option of the Optimization of neighboring cell
downlink LTE RBs that
experience
interference from
GSM to the RBs in the
configured LTE
the gains of NPREO
FDD UL Refarming AvoidUtranIn UL Refarming When this function is

Zero terfSwitch Zero enabled, the accuracy
Bufferzone option of the Bufferzone of neighboring cell
downlink LTE RBs that
experience
interference from
UMTS to the RBs in
the configured LTE
the gains of NPREO

eRAN

Name Switch
FDD GSM and LTE SpectrumClo GSM and LTE When this function is
Spectrum ud.Spectrum Spectrum enabled, the accuracy
Concurrency CloudSwitch Concurrency of neighboring cell
interference
and the performance
of UE-level NPREO
RBs shared by LTE and
GSM to the RBs in the
configured LTE
the gains of NPREO
FDD Flexible DdCellGroup. Flexible When this function is

bandwidth DdBandWidt Bandwidth enabled, the accuracy
based on h based on of neighboring cell
overlapping Overlap interference
carriers Carriers calculation is affected
(FDD) and the performance
of UE-level NPREO
punctured RBs to the
RBs in the configured
LTE bandwidth, the
lower the gains of
NPREO constant
optimization.
FDD Adaptive SFN/ CellAlgoSwit SFN When this function is

SDMA ch.SfnDlSchS enabled, the accuracy
witch of neighboring cell
interference
and the performance
of UE-level NPREO
is affected. Therefore,
you are advised not to
enable UE-level
NPREO constant
optimization.

eRAN

Name Switch
FDD DL CoMP cell FDDHomNet DL CoMP When this function is

DlCompSwitc (FDD) enabled, the accuracy
h and of neighboring cell
FDDHetNetD interference
lCompSwitch calculation is affected
options of the and the performance
CellAlgoSwit of UE-level NPREO
ch.DlCompS constant optimization
witch is affected. Therefore,
parameter you are advised not to
enable UE-level
NPREO constant
optimization.
FDD Precise AMC PreciseAmcS eMIMO When this function is

witch option (FDD) enabled, UE-level
of the NPREO constant
CellAlgoSwit optimization uses the
ch.EmimoSwi same neighboring cell
tch interference values as
parameter this function. If this
function has been
enabled and then UE-
level NPREO constant
optimization is
enabled, the gains of
NPREO constant
optimization may
decrease.
FDD Dedicated Tm9Dedicate Dedicated When this function is

carrier for dCarrier.Wor Carrier for enabled, almost all
TM9 kMode TM9 (FDD) UEs in the cell work in
TM9. NPREO constant
adjustment has no
impact on TM9 UEs.
As NPREO constant
optimization has no
gains, enabling it is
not recommended.
FDD Downlink FreqSelSwitc Scheduling When this function is

frequency h option of enabled, modifying
selective the the NPREO constant
scheduling CellAlgoSwit may affect CQI and
ch.DlSchSwit rank reporting by UEs
ch parameter in FSS mode, which in
turn affects FSS gains.

eRAN

Name Switch
FDD Downlink SMART_FSS_ Scheduling When this function is

smart SWITCH enabled, the UE-level
frequency option of the NPREO constant is
selective CellAlgoSwit always 0 to ensure
scheduling ch.DlSchExtS FSS gains.
witch
parameter
TDD None None None None
4.3 Requirements
4.3.1 Licenses
None
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
None
Mutually Exclusive Functions

Name Switch
FDD WTTx MU- Tm9FourLaye WTTx MU- WTTx MU-MIMO

MIMO rPairSwitch MIMO (FDD) cannot work with the
option of the CQI reporting interval
CellAlgoExtS adaptation.
witch.WttxM
uMimoSwitc
h parameter
TDD None None None None

eRAN
4.3.3 Hardware
Base Station Models

No requirements
Boards
For TDD, there are no requirements.
For FDD, the LBBPd, UBBPd, and later models of BBPs are compatible with NPREO
constant optimization. All boards are compatible with other functions.
RF Modules
No requirements
4.3.4 Others
For FDD, cell-level NPREO constant optimization requires that counters related to
different NPREO constant values be collected. Therefore, it requires subscription to
hour-level or 30-minute network performance counters, such as L.thrp.bits.DL,
L.thrp.bits.DL.LastTTI, L.Thrp.Time.DL.RmvLastTTI, and
L.ChMeas.PRB.DL.Used.Avg.
For TDD, there is no other requirement.
4.4 Operation and Maintenance
4.4.1 Data Configuration (FDD)
4.4.1.1 Data Preparation

The periodic CQI reporting interval can be fixedly configured or adaptively
changed.
Subfunction Parameter Name Parameter ID Setting Notes
Adaptive CQI Period CellCqiAdaptiveC Set this parameter to

change Adaptive Switch fg.CqiPeriodAdap ON.
tive
Minimal CQI CellCqiAdaptiveC The default value of
Period fg.MinCqiPeriod this parameter is
recommended.
PUCCH Periodic CqiAdaptiveCfg.P The default value of

CQI Optimize ucchPeriodicCqiO this parameter is
Switch ptSwitch recommended.

eRAN
Fixed User CQI period CellCqiAdaptiveC This parameter is valid

configuration fg.UserCqiPeriod only when the
qiPeriodAdaptive
parameter is set to
OFF.
The default value of
this parameter is
recommended.
The conditions for triggering aperiodic CQI reporting are different for UEs in
different states.
Subfunction Parameter Parameter Option Setting Notes

Name ID
Basic PDCCH CellPdcchA None The default value of

configuration Symbol lgo.PdcchS this parameter is
Number ymNumSw recommended.
Adjust itch
Switch
For UEs in FSS FS UE CellDlschA None The default value of

Aperiodic lgo.FSUEA this parameter is
CQI perCQITrig recommended.
Triggering Period
Period
FS UE CellDlschA None The default value of

Aperiodic lgo.FSUESb this parameter is
Subband CQIValidit recommended.
CQI yPeriod
Validity
Period
For UEs in DL CellAlgoS EnAperiodi Select this option.

FDS schedule witch.DlSc cCqiRptSwi
switch hSwitch tch
FD UE CellDlschA None The default value of

Enhanced lgo.FDUEE this parameter is
Aperiodic nhAperCQI recommended.
CQI Trigger TrigPeriod
Period
For UEs in the DL CellAlgoS AperiodicC Select this option.

initial access schedule witch.DlSc qiTrigOptS
switch hSwitch witch

eRAN

Name ID
For UEs Handover CellCqiAda None The default value of

involved in Aperiodic ptiveCfg.H this parameter is
handovers CQI Config oAperiodic recommended.
Switch CqiCfgSwit
ch
For UEs with Compatibili ENodeBAlg ApCqiAnd Select both of the
compatibility ty Control oSwitch.Co AckAbnCtr options.
issues Switch mpatibility lSwitch
CtrlSwitch ApCqiRptA
bnormalCt
rlSwitch
The following table describes the parameter related to optimized CQI detection.
Parameter Parameter ID Option Setting Notes

Name
CQI CellCqiAdjAlgo.C PUSCH_CQI_FALS Select both of the

Optimization qiOptSwitch E_DETECTION_SW options.
Algorithm PUCCH_CQI_FALS
Switch E_DETECTION_SW
The following table describes the parameters used for activating NPREO constant
optimization.

Name
Cell-Level CellDlpcPdschPa. None Set this parameter to

NPREO CellNpreoAdjThr a value other than
Adjustment eshold 255. The value 5 is
Threshold recommended.
UE-Level CellDlpcPdschPa. None Set this parameter to

NPREO UeNpreoAdjThre a value other than
Adjustment shold 127. If the values of
Threshold PCIs mod 3 are the
same, the value 1 is
recommended. If the
values of PCIs mod 3
are different, the
value 10 is
recommended.

eRAN
The following table describes the parameters used for optimizing NPREO constant
optimization.
Parameter Parameter ID Setting Notes

Name
Interference CellDlschAlgo.Int The value 50 is recommended.

Filter rfFilterCoeff
Coefficient
DL RSRP NCellDlRsrpMeas The value -20 is recommended.

NCell Para.NCellDlRsrp
Measurement MeasA3Offset
A3 Offset
4.4.1.2 Using MML Commands
Periodic CQI Reporting Configuration Command Examples

Adaptive change of periodic CQI reporting
//Configuring periodic CQI reporting
MOD CELLCQIADAPTIVECFG: LocalCellId=0, CqiPeriodAdaptive=ON,MinCqiPeriod=ms5;
//Configuring optimized periodic CQI reporting
MOD CQIADAPTIVECFG: PucchPeriodicCqiOptSwitch=ON;
Fixed configuration of periodic CQI reporting

MOD CELLCQIADAPTIVECFG: LocalCellId=0, CqiPeriodAdaptive=Off,UserCqiPeriod=ms40;
Aperiodic CQI Reporting Configuration Command Examples

//Configuring the number of OFDM symbols occupied by the PDCCH
MOD CELLPDCCHALGO: LocalCellId=0,PdcchSymNumSwitch=ECFIADAPTIONON;
//Setting the triggering interval and validity period
MOD CELLDLSCHALGO:
LocalCellId=0,FSUEAperCQITrigPeriod=2,FSUESbCQIValidityPeriod=10,FDUEEnhAperCQITrigPeriod=5ms;
//Configuring aperiodic CQI reporting for UEs in FDS and UEs in the initial access
MOD CELLALGOSWITCH: LocalCellId=0,
DlSchSwitch=EnAperiodicCqiRptSwitch-1&AperiodicCqiTrigOptSwitch-1;
//Configuring aperiodic CQI reporting for UEs involved in handovers
MOD CELLCQIADAPTIVECFG: LocalCellId=0,HoAperiodicCqiCfgSwitch=ON;
//Configuring aperiodic CQI reporting for UEs with compatibility issues
MOD ENODEBALGOSWITCH: COMPATIBILITYCTRLSWITCH=ApCqiAndAckAbnCtrlSwitch-1;
Optimized CQI Detection Configuration Command Examples

MOD
CELLCQIADJALGO:LocalCellId=0,CqiOptSwitch=PUSCH_CQI_FALSE_DETECTION_SW-1&PUCCH_CQI_FALSE_D
ETECTION_SW-1;
Activation Command Examples for NPREO Constant Optimization

//Enabling the cell-level NPREO constant optimization function
MOD CELLDLPCPDSCHPA: LocalCellId=101, CellNpreoAdjThreshold=5;
//Enabling the UE-level NPREO constant optimization function
MOD CELLDLPCPDSCHPA: LocalCellId=101, UeNpreoAdjThreshold=1;

eRAN
Optimization Command Examples for NPREO Constant Optimization

1. Set parameters.
//Setting the Interference Filter Coefficient
MOD CELLDLSCHALGO: LocalCellId=101, IntrfFilterCoeff=50;
//Adjusting the DL RSRP NCell Measurement A3 Offset to increase the proportion of UEs for which
UE-level NPREO constant optimization takes effect
MOD NCELLDLRSRPMEASPARA: LocalCellId=101,NCellDlRsrpMeasA3Offset=-10;
2. Set up an eX2 interface between eNodeBs. For detailed operations, see eX2 Self-
Management. Configure an X2 interface (service coordination must be supported
in non-ideal backhaul mode). For detailed operations, see S1 and X2 Self-
Management.
Deactivation Command Examples for NPREO Constant Optimization

//Disabling the cell-level NPREO constant optimization function and restoring the NPREO constant to the
expected value
MOD CELLDLPCPDSCHPA: LocalCellId=101, CellNpreoAdjThreshold=255;
MOD CELLDLPCPDSCHPA: LocalCellId=101, NomPdschRsEpreOffset=0;
//Disabling the UE-level NPREO constant optimization function
MOD CELLDLPCPDSCHPA: LocalCellId=101, UeNpreoAdjThreshold=127;
4.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.
4.4.2 Data Configuration (TDD)

changed.

tive

qiPeriodAdaptive
parameter is set to
OFF.
this parameter is
recommended.

eRAN
different states.

Name ID
Basic PDCCH CellPdcchA None Set this parameter to

configuration Symbol lgo.PdcchS ON.
Number ymNumSw
Adjust itch
Switch

Triggering Period
Period

CQI yPeriod
Validity
Period


Switch CqiCfgSwit
ch
bnormalCt
rlSwitch

Name


eRAN

MOD CELLCQIADAPTIVECFG: LocalCellId=0, CqiPeriodAdaptive=ON;




MOD CELLDLSCHALGO: LocalCellId=0,FSUEAperCQITrigPeriod=5,FSUESbCQIValidityPeriod=11;
//Configuring aperiodic CQI reporting for UEs in the initial access

MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=AperiodicCqiTrigOptSwitch-1;



MOD
ETECTION_SW-1;

4.4.3 Activation Verification

CSI Reporting Mode
If the CQI-ReportModeAperiodic IE contains rmXY in the RRC_CONN_SETUP
message traced on the Uu interface, CSI reporting mode X-Y has taken effect.
Periodic CQI Reporting

Verify whether optimized periodic CQI reporting on the PUCCH has taken effect by
performing the following steps:
Step 1 Enable 10 UEs to access the cell and perform ping services.
Step 2 Disable optimized periodic CQI reporting on the PUCCH. Then, enable a UE to
access the cell. Query the cqi-pmi-ConfigIndex value in the RRC_CONN_RECFG

eRAN
message traced over the Uu interface, as shown in Figure 4-2. The value indicates
that the CQI reporting interval is 5 ms.
Figure 4-2 CQI reporting interval of 5 ms
Step 3 Release the UE that accessed the cell in Step 2. Enable optimized periodic CQI
reporting on the PUCCH. Then, enable a UE to access the cell again. Query the
cqi-pmi-ConfigIndex value in the RRC_CONN_RECFG message traced over the Uu
interface, as shown in Figure 4-3. The value indicates that the CQI reporting
interval is 40 ms.
----End
Aperiodic CQI Reporting

Aperiodic CQI reporting has taken effect if the value of any of the counters listed
in Table 4-1 increases significantly after aperiodic CQI reporting is triggered.
Table 4-1 Counters related to aperiodic CQI reporting
Counter ID Counter Name
1526729367 through L.ChMeas.CQI.DL.DualCW.Code0.Aperiodic.0

1526729382 through
L.ChMeas.CQI.DL.DualCW.Code0.Aperiodic.15

eRAN
1526729399 through L.ChMeas.CQI.DL.DualCW.Code1.Aperiodic.0

1526729414 through
L.ChMeas.CQI.DL.DualCW.Code1.Aperiodic.15
1526729335 through L.ChMeas.CQI.DL.SingleCW.Aperiodic.0 through

1526729350 L.ChMeas.CQI.DL.SingleCW.Aperiodic.15
NPREO Constant Optimization (FDD)

● Using MML commands
Run the DSP CELLNPREOOPTIMIZESTATUS command to query the running
status of the cell-level NPREO constant optimization function. If the query
result shows that the function is running, the function has taken effect.
● Using signaling tracing
After UE-level NPREO constant optimization is enabled, it will adjust the
NPREO constants of UEs. Check the value of nomPDSCH-RS-EPRE-Offset in
the CQI-ReportConfig IE of the RRC Connection Reconfiguration message. If
the value is not equal to that configured in the MML command window, the
function has taken effect. In addition, after UE-level NPREO constant
optimization is enabled, you can check cell indicators such as the proportion
of high ranks, average CQI, and average MCS index. If the values significantly
fluctuate or change, the function has taken effect.
4.4.4 Network Monitoring

After periodic CQI reporting, aperiodic CQI reporting, and optimized CQI detection
are enabled, the User Downlink Average Throughput increases but the User
Uplink Average Throughput decreases.
For FDD, after NPREO constant optimization is enabled, the User Downlink
Average Throughput increases.
User Uplink Average Throughput = (L.Thrp.bits.UL –
L.Thrp.bits.UE.UL.LastTTI)/L.Thrp.Time.UE.UL.RmvLastTTI
User Downlink Average Throughput = (L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI)/
L.Thrp.Time.DL.RmvLastTTI
For FDD, check the cell-level downlink rank distribution, CQI distribution, MCS
index distribution, average CQI, average MCS index, PDSCH IBLER, and PDSCH
RBLER to see their changes.
Average CQI = (L.ChMeas.CQI.DL.1 + 2 x L.ChMeas.CQI.DL.2 + 3 x
L.ChMeas.CQI.DL.3 + ... 15 x L.ChMeas.CQI.DL.15)/(L.ChMeas.CQI.DL.0 +
L.ChMeas.CQI.DL.1 + L.ChMeas.CQI.DL.2 + ... L.ChMeas.CQI.DL.15)
Average MCS= (L.ChMeas.PDSCH.MCS.1+2 x L.ChMeas.PDSCH.MCS.2+3 x
L.ChMeas.PDSCH.MCS.3+...28 x L.ChMeas.PDSCH.MCS.28) /
(L.ChMeas.PDSCH.MCS.0+L.ChMeas.PDSCH.MCS.1+L.ChMeas.PDSCH.MCS.
2+...L.ChMeas.PDSCH.MCS.28)
PDSCH IBLER = (L.Traffic.DL.SCH.QPSK.ErrTB.Ibler + L.Traffic.DL.SCH.
16QAM.ErrTB.Ibler + L.Traffic.DL.SCH.64QAM.ErrTB.Ibler + L.Traffic.DL.SCH.

eRAN
256QAM.ErrTB.Ibler)/(L.Traffic.DL.SCH.QPSK.TB + L.Traffic.DL.SCH.16QAM.TB
+ L.Traffic.DL.SCH.64QAM.TB + L.Traffic.DL.SCH.256QAM.TB) x 100%
PDSCH RBLER = (L.Traffic.DL.SCH.QPSK.ErrTB.Rbler + L.Traffic.DL.SCH.
16QAM.ErrTB.Rbler + L.Traffic.DL.SCH.64QAM.ErrTB.Rbler + L.Traffic.DL.SCH.
256QAM.ErrTB.Rbler)/(L.Traffic.DL.SCH.QPSK.TB + L.Traffic.DL.SCH.16QAM.TB
+ L.Traffic.DL.SCH.64QAM.TB+ L.Traffic.DL.SCH.256QAM.TB) x 100%
Table 4-2 lists the related counters.
Table 4-2 Counters related to network monitoring

1526728261 L.Thrp.bits.DL
1526729005 L.Thrp.bits.DL.LastTTI
1526729015 L.Thrp.Time.DL.RmvLastTTI
1526728180 L.Traffic.DL.SCH.QPSK.ErrTB.Ibler
1526728182 L.Traffic.DL.SCH.16QAM.ErrTB.Ibler
1526727354 L.Traffic.DL.SCH.QPSK.TB
1526727355 L.Traffic.DL.SCH.16QAM.TB
1526728181 L.Traffic.DL.SCH.QPSK.ErrTB.Rbler
1526728183 L.Traffic.DL.SCH.16QAM.ErrTB.Rbler
1526730141 L.ChMeas.RI.Rank1

eRAN
1526727396 through L.ChMeas.CQI.DL.0 through L.ChMeas.CQI.DL.15

1526727411
1526727444 through L.ChMeas.PDSCH.MCS.0 through

1526727472 L.ChMeas.PDSCH.MCS.28

eRAN
Description 5 CQI Reporting Optimization
5 CQI Reporting Optimization
5.1 Principles
Huawei eNodeBs optimize CQI reporting for flexible control.
5.1.1 Periodic CQI Reporting Optimization (FDD)

In FDD, when the CellCqiAdaptiveCfg.CqiPeriodAdaptive parameter is set to ON
to adjust the periodic CQI reporting interval based on the PUCCH load, the
eNodeB can optimize periodic CQI reporting to increase the number of UEs that
report CQIs at long intervals.
Reporting optimization is controlled by the
CqiAdaptiveCfg.PucchPeriodicCqiOptSwitch parameter.
● If this parameter is set to ON, more UEs report CQIs at long intervals, fewer
RBs are allocated to the PUCCH, and more RBs can be allocated to the PUSCH
to increase uplink throughput. However, the UEs do not promptly report
channel quality and downlink performance may deteriorate.
● If this parameter is set to OFF, more UEs report CQIs at short intervals, the
UEs promptly report channel quality, and downlink performance may improve.
However, the uplink peak rate may be lower than that obtained when this
parameter is set to ON.
5.1.2 Aperiodic CQI Reporting Optimization

The triggering of aperiodic CQI reporting is optimized for UEs in the initial access,
UEs involved in handovers, and UEs with compatibility issues.
5.1.2.1 UEs in the Initial Access

During the initial access, if periodic CQI reporting fails repeatedly, aperiodic CQI
reporting is triggered. If the aperiodic CQI reporting fails a cyclic redundancy code
(CRC) check, the aperiodic CQI reporting is triggered again eight transmission time
intervals (TTIs) later.
Aperiodic CQI reporting scheduled in CQI-only mode occupies PUSCH and PDCCH
resources. To reduce the chance that aperiodic CQI reporting is triggered during

eRAN
initial access, Huawei eNodeBs support optimized aperiodic CQI reporting

triggering. For details about CQI-only mode, see Scheduling.
Optimized aperiodic CQI reporting triggering is controlled by the
AperiodicCqiTrigOptSwitch option of the CellAlgoSwitch.DlSchSwitch
parameter. When this option is selected and an aperiodically reported CQI fails a
CRC check, the eNodeB determines whether to trigger aperiodic CQI reporting
again based on the DRX switch setting (specified by the
CellDrxPara.DrxAlgSwitch parameter):
● If the DRX switch is turned on, aperiodic CQI reporting is not triggered again.
● If the DRX switch is turned off, aperiodic CQI reporting is triggered after eight
TTIs.
5.1.2.2 UEs Involved in Handovers

Aperiodic CQI reporting can be configured in handover commands for UEs
involved in handovers. If there are downlink services for a UE after the handover,
aperiodic CQI reporting is triggered once. This function is controlled by
CellCqiAdaptiveCfg.HoAperiodicCqiCfgSwitch:
● If this switch is turned on, aperiodic CQI reporting is configured in handover
commands. When there are downlink services for UEs after handovers,
aperiodic CQI reporting is triggered if no periodic CQI resources are
configured for the UEs, thereby increasing downlink throughput. However, the
high handover signaling overhead may decrease the handover success rate
and increase handover delay.
● If this switch is turned off, aperiodic CQI reporting is not configured in
handover commands. Instead, it is configured only after handovers.
5.1.2.3 UEs with Compatibility Issues
ACK/NACK Issues
Some UEs have compatibility issues with CQI reporting. When aperiodic CQI
reports are sent in CQI-only mode at the same time as ACK/NACK responses,
some UEs do not calculate the number of required subcarriers in line with 3GPP
specifications. As a result, the eNodeB ACK/NACK demodulation fails, which may
lead to a loss in downlink throughput.
This issue can be addressed by selecting the ApCqiAndAckAbnCtrlSwitch option
of the ENodeBAlgoSwitch.CompatibilityCtrlSwitch parameter.
● If this option is selected, the aperiodically reported CQIs are only scheduled in
preallocation mode.
● If this option is deselected, the aperiodically reported CQIs are only scheduled
in CQI-only mode.
No Aperiodic CQI Reporting in SCells

In carrier aggregation (CA) scenarios, if a reconfiguration message does not
contain aperiodic CQI reporting data, some CA UEs will not send aperiodic CQI
reports in the secondary cells (SCells). This will lead to mis-demodulation by
eNodeBs, affecting downlink performance and even deactivating SCells.

eRAN
This issue can be addressed by selecting the ApCqiRptAbnormalCtrlSwitch

option of the ENodeBAlgoSwitch.CompatibilityCtrlSwitch parameter.
● If this option is selected, each reconfiguration message sent to the UE will

carry aperiodic CQI reporting data.
● If this option is deselected, the reconfiguration message carries aperiodic CQI
reporting data when configurations for aperiodic CQI reporting are changed.
In non-CA scenarios, it is recommended that this option be deselected. If this

option is selected, the RRC signaling overhead increases and the cell capacity
decreases.
5.2.1 Benefits
Optimized periodic CQI reporting increases the number of UEs that report CQIs at
long intervals, reduces PUCCH resource consumption, and increases uplink
throughput.
Optimized aperiodic CQI reporting offers the following benefits:

● Reduced PUSCH and PDCCH resource consumption
Decreasing the number of times aperiodic CQI reporting is triggered during
initial access reduces overall PUSCH and PDCCH resource consumption.
● Increased downlink throughput
If a handover command includes configuration of aperiodic CQI reporting, a
single aperiodic CQI report will be triggered if there is a downlink service after
the handover is completed. However, the high handover signaling overhead
may decrease the handover success rate and increase handover delay.
5.2.2 Impacts
Network Impacts
Optimized periodic CQI reporting increases the number of UEs that report CQIs at
long intervals and therefore increases uplink throughput. However, UEs do not
promptly report channel quality and therefore downlink performance may
deteriorate.
Function Impacts
None
5.3 Requirements
5.3.1 Licenses
None

eRAN
5.3.2 Software
None

None
5.3.3 Hardware
Base Station Models

3900 and 5900 series base stations
Boards
No requirements
RF Modules
No requirements
5.3.4 Others
None

changed.

tive
Minimal CQI CellCqiAdaptiveC The default value of
Period fg.MinCqiPeriod this parameter is
recommended.

eRAN


qiPeriodAdaptive
parameter is set to
OFF.
this parameter is
recommended.
different states.

Name ID
Basic PDCCH CellPdcchA None The default value of

configuration Symbol lgo.PdcchS this parameter is
Number ymNumSw recommended.
Adjust itch
Switch

Triggering Period
Period

CQI yPeriod
Validity
Period
For UEs in DL CellAlgoS EnAperiodi Select this option.

FDS schedule witch.DlSc cCqiRptSwi
switch hSwitch tch
FD UE CellDlschA None The default value of

Enhanced lgo.FDUEE this parameter is
Aperiodic nhAperCQI recommended.
CQI Trigger TrigPeriod
Period

eRAN

Name ID


Switch CqiCfgSwit
ch
bnormalCt
rlSwitch

Name


MOD CELLCQIADAPTIVECFG: LocalCellId=0, CqiPeriodAdaptive=ON,MinCqiPeriod=ms5;




eRAN
MOD CELLDLSCHALGO:
LocalCellId=0,FSUEAperCQITrigPeriod=2,FSUESbCQIValidityPeriod=10,FDUEEnhAperCQITrigPeriod=5ms;
//Configuring aperiodic CQI reporting for UEs in FDS and UEs in the initial access
MOD CELLALGOSWITCH: LocalCellId=0,
DlSchSwitch=EnAperiodicCqiRptSwitch-1&AperiodicCqiTrigOptSwitch-1;



MOD
ETECTION_SW-1;


changed.

tive

qiPeriodAdaptive
parameter is set to
OFF.
this parameter is
recommended.
different states.

eRAN

Name ID
Basic PDCCH CellPdcchA None Set this parameter to

configuration Symbol lgo.PdcchS ON.
Number ymNumSw
Adjust itch
Switch

Triggering Period
Period

CQI yPeriod
Validity
Period


Switch CqiCfgSwit
ch
bnormalCt
rlSwitch

Name


eRAN

MOD CELLCQIADAPTIVECFG: LocalCellId=0, CqiPeriodAdaptive=ON;




MOD CELLDLSCHALGO: LocalCellId=0,FSUEAperCQITrigPeriod=5,FSUESbCQIValidityPeriod=11;
//Configuring aperiodic CQI reporting for UEs in the initial access

MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=AperiodicCqiTrigOptSwitch-1;



MOD
ETECTION_SW-1;


CSI Reporting Mode
If the CQI-ReportModeAperiodic IE contains rmXY in the RRC_CONN_SETUP
message traced on the Uu interface, CSI reporting mode X-Y has taken effect.
Periodic CQI Reporting

Verify whether optimized periodic CQI reporting on the PUCCH has taken effect by
performing the following steps:
Step 1 Enable 10 UEs to access the cell and perform ping services.
Step 2 Disable optimized periodic CQI reporting on the PUCCH. Then, enable a UE to
access the cell. Query the cqi-pmi-ConfigIndex value in the RRC_CONN_RECFG

eRAN
message traced over the Uu interface, as shown in Figure 5-1. The value indicates
that the CQI reporting interval is 5 ms.
Step 3 Release the UE that accessed the cell in Step 2. Enable optimized periodic CQI
reporting on the PUCCH. Then, enable a UE to access the cell again. Query the
cqi-pmi-ConfigIndex value in the RRC_CONN_RECFG message traced over the Uu
interface, as shown in Figure 5-2. The value indicates that the CQI reporting
interval is 40 ms.
----End
Aperiodic CQI Reporting

Optimized aperiodic CQI reporting triggering has taken effect if the value of the
counter listed in Table 5-1 decreases after both optimized aperiodic CQI reporting
triggering and DRX are enabled.
Table 5-1 Counter related to optimized aperiodic CQI reporting triggering

1526727441 L.ChMeas.PUSCH.MCS.29

eRAN

After CQI reporting optimization is enabled, the User Downlink Average
Throughput increases but the User Uplink Average Throughput decreases.
User Uplink Average Throughput = (L.Thrp.bits.UL –
L.Thrp.bits.UE.UL.LastTTI)/L.Thrp.Time.UE.UL.RmvLastTTI
User Downlink Average Throughput = (L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI)/
L.Thrp.Time.DL.RmvLastTTI

eRAN
Description 6 CQI Adjustment
6 CQI Adjustment
6.1 Principles
The CQI reporting may be delayed, and the CQI reporting interval significantly
exceeds the scheduling period. As a result, the reported CQI may not reflect the
channel quality and IBLER will be unable to approach the target optimum value.
In such a case, the eNodeB must calculate the difference between the reported
channel quality and the actual channel quality, based on HARQ feedback, and
adjust the CQI accordingly.
CQI adjustment is controlled by the CqiAdjAlgoSwitch option of the

CellAlgoSwitch.CqiAdjAlgoSwitch parameter. If this option is selected, the
eNodeB selects an MCS based on the adjusted CQI.
● If the selected MCS requires better channel quality than is available, the block
error rate (BLER) for data packets increases. The eNodeB then decreases the
CQI based on the feedback from the UE.
● If the current channel quality is better than that required by the selected MCS,
the BLER for data packets decreases. The eNodeB reacts by increasing the CQI
based on the feedback from the UE.
CQI adjustment enables the downlink IBLER to close in on a predefined target

value. The target IBLER determines the CQI adjustment value.
6.1.1 Downlink Target IBLER
6.1.1.1 Fixed Configuration

The downlink target IBLER for a UE depends on the downlink target IBLERs
corresponding to the bearers of the QCIs set up for the UE, as shown in Table 6-1.
The target IBLER corresponding to a bearer of a QCI set up for the UE is
determined by the CellQciPara.InitDlTargetIbler parameter. If this parameter
value is changed, the specified target IBLER takes effect only when a bearer of a
QCI is created, modified, or released for the admitted UE.

eRAN
Table 6-1 Target IBLERs for a UE

Target IBLERs Corresponding to Target IBLER for the UE
Bearers of the QCIs Set Up for the
UE
All the target IBLER values are zero. The target IBLER is determined by the
CellCqiAdjAlgo.InitDlIblerTarget
parameter.
Only one of the target IBLER values is The target IBLER is the non-zero target
non-zero. IBLER value.
More than one of the target IBLER A non-zero parameter value with the
values are non-zero. QCI that takes precedence over the
other QCIs is used as the target IBLER
for the UE. The QCIs in descending
order of precedence are as follows: QCI
2, QCI 1, QCIs for non-IMS signaling,
and QCIs for IMS signaling.
There are multiple QCIs for non-IMS The target IBLER depends on the QCI
signaling. that takes precedence over the other
QCIs. The QCIs are sorted in
descending order of QCI priority.
Multiple QCIs have the same priority The smallest target IBLER value is
but correspond to different target used.
IBLER values.
6.1.1.2 Adaptive Configuration

The downlink target IBLER can be configured both fixedly and adaptively. Adaptive
configuration of the target IBLER does not apply to UEs running services with QCI
1.
Adaptation
For FDD, downlink target IBLER adaptation is controlled by the
DlVarIBLERtargetSwitch option of the CellAlgoSwitch.CqiAdjAlgoSwitch
parameter. If this option is selected, the eNodeB adjusts the target IBLER to:
● 10% for UEs running non-small-packet services at non-edge locations.
● 30% for UEs running small-packet services at non-edge locations and UEs at
cell edges.
For TDD, the eNodeB handles UEs using multiplexing mode or bundling mode in
different ways. For details about UEs using multiplexing mode or bundling mode,
see 6.1.5.3 Optimized CQI Adjustment for Different UEs (TDD).
● For UEs using Multiplexing mode, downlink target IBLER adaptation is
controlled by the DlVarIBLERtargetSwitch option of the
eNodeB adjusts the target IBLER to:

eRAN
– 10% for UEs running non-small-packet services at non-edge locations.

– 30% for UEs running small-packet services at non-edge locations and UEs
at cell edges.
● For UEs using Bundling mode, downlink target IBLER adaptation is controlled
by the DlVarIBLERtargetSwitch option of the
eNodeB adjusts the target IBLER to:
– 10% for UEs running non-small-packet services at non-edge locations.
– 5% plus the CellCqiAdjAlgo.InitDlIblerTarget parameter value for UEs
running small-packet services at non-edge locations and UEs at cell
edges.
Enhanced Adaptation
Enhanced downlink target IBLER adaptation is controlled by the
DlEnVarIblerTargetSwitch option of the CellAlgoSwitch.CqiAdjAlgoSwitch
parameter. If this option is selected, the eNodeB adjusts the target IBLER based on
the TBS index threshold for low target IBLER specified by the
CellDlschAlgo.LowIblerTargetTbsIdxThld parameter.
When the TBS index threshold for low target IBLER is 255, the eNodeB does not
adjust the target IBLER based on the TBS index.
● For UEs performing services with slightly fluctuated CQI values, the target
IBLER is changed to 5%.
● For UEs performing services with moderately fluctuated CQI values, target
IBLER adaptation is used.
● For UEs performing services with heavily fluctuated CQI values, the target
IBLER is changed to 30%.
When the TBS index threshold for low target IBLER is not 255, the eNodeB adjusts
the target IBLER based on the TBS index.
● For UEs performing services with slightly fluctuated CQI values,

– If the TBS index is not less than the value of the
CellDlschAlgo.LowIblerTargetTbsIdxThld parameter, the target IBLER is
changed to 5%.
– If the TBS index is less than the value of the
CellDlschAlgo.LowIblerTargetTbsIdxThld parameter, the target IBLER is
changed to 10%.
● For UEs performing services with heavily fluctuated CQI values,
– If the TBS index does not exceed the value of the
CellDlschAlgo.HighIblerTargetTbsIdxThld parameter, the target IBLER is
changed to 30%.
– If the TBS index exceeds the value of the
CellDlschAlgo.HighIblerTargetTbsIdxThld parameter, the target IBLER is
changed to 10%.
● For UEs performing services with moderately fluctuated CQI values,
Target IBLER adaptation is used.

eRAN
6.1.2 CQI Adjustment Period (FDD)

In FDD, if a cell serves a large number of online users, the CQI adjustment period
is prolonged and the CQI adjustment algorithm may receive multiple HARQ
feedback messages in a CQI adjustment period.
The DlCqiAdjDeltaOptSwitch option of the CellAlgoSwitch.CqiAdjAlgoSwitch

parameter specifies how to calculate the CQI adjustment value.
● When this option is deselected, the CQI adjustment algorithm treats all the
received HARQ feedback messages in a CQI adjustment period as a single
feedback message, based on which the CQI adjustment value is calculated.
This calculation method causes slow CQI adjustment.
● When this option is selected, the CQI adjustment algorithm calculates the CQI
adjustment value based on each individual HARQ feedback message received
in a CQI adjustment period. This calculation method causes fast CQI
adjustment.
6.1.3 CQI Filtering Adjustment
6.1.3.1 Initial Filtered Value of Reported CQIs

The eNodeB applies filtering to the reported CQIs. The initial filtered value of the
CQIs reported by a newly admitted UE is determined by the RptCqiFltInitSwitch
option of the CellAlgoSwitch.CqiAdjAlgoSwitch parameter. This function does
not take effect for UEs running services with QCI 1.
● If this option is deselected, the initial filtered value is always 4.

● If this option is selected, the initial filtered value is adaptively configured
based on the reported CQIs, which can increase the User Downlink Average
Throughput.
6.1.3.2 CQI Filtering Based on Spectral Efficiency Optimization

This function is controlled by the CqiFltSpectralEffOptSwitch option of the
CellAlgoSwitch.CqiAdjAlgoSwitch parameter. This function can be used in low-
speed cells with four CRS ports. In FDD, it takes effect for TM4 UEs. In TDD, it
takes effect for TM4 or TM9 UEs.
● If this option is deselected, each time the eNodeB receives a CQI value from a
UE, it directly applies filtering to the reported CQI and the previous filtered
CQI.
● If this option is selected, each time the eNodeB receives a CQI value from a
UE, it determines the difference between the reported CQI and the previous
filtered CQI. If the difference is large, the eNodeB adjusts the reported CQI
based on spectral efficiency optimization, and then applies filtering to the
adjusted CQI and the previous filtered CQI. If the difference is small, the
eNodeB directly applies filtering to the reported CQI and the previous filtered
CQI.

eRAN
6.1.3.3 CQI Filtering Optimization (TDD)
Initial CQI Filtering Optimization

For a UE initially accessing the network with a large number of call attempts per
second (CAPS) and reporting aperiodic CQIs, the initial filtered value of the
reported CQIs is adjusted based on the first reported wideband CQI. The
CqiFastCompstSwitch option of the CellAlgoSwitch.CqiAdjAlgoSwitch
parameter specifies whether to enable this function.
The function can be enabled only when the
CellPdcchAlgo.HLNetAccSigAggLvlSelEnhSw parameter is set to ON. This
parameter determines whether to enable the enhanced aggregation level selection
for access signaling in heavily loaded networks. For details about this parameter,
see Physical Channel Resource Management.
Subsequent CQI Filtering Optimization

CQI filtering optimization has been introduced to address inconsistencies between
the trend of reported CQIs and the current link performance when there is
fluctuation in the interference, or UE movement. The inconsistency could be a low
transmission BLER paired with a decrease in reported CQI values, or a high BLER
paired with an increase in reported CQI values. The CqiFltOptSwitch option of the
CellAlgoSwitch.CqiAdjAlgoSwitch parameter specifies whether to enable this
optimization function.
● If this option is selected, each time the eNodeB receives a CQI value from a
UE, the eNodeB compares the reported value with the previous filtered CQI
value. Then, based on the BLER during the interval between the two CQI
reports, the eNodeB determines whether to apply filtering to the reported CQI
so as to generate a new filtered CQI value.
● If this option is deselected, each time the eNodeB receives a CQI value from a
UE, the eNodeB applies filtering to the reported CQI and the previous filtered
CQI to generate a new filtered CQI value.
6.1.4 Optimized CQI Adjustment Value (FDD)

An eNodeB calculates a CQI adjustment value for a UE based on HARQ feedback.
It sets an initial value for the UE during initial access, RRC connection
reestablishment, or incoming handovers. The larger the CQI adjustment value, the
more aggressive the MCS for the UE. The smaller the CQI adjustment value, the
more conservative the MCS for the UE.
6.1.4.1 Initial CQI Adjustment Value (FDD)

In FDD, the initial CQI adjustment value for UEs during initial access, RRC
connection reestablishment, or incoming handovers is specified by the
CellCqiAdjAlgo.InitDeltaCqi parameter.
The PreciseMcsAdaptSwitch option of the CellAlgoSwitch.CqiAdjAlgoSwitch
parameter determines whether the eNodeB modifies the reported CQI value for
the UEs. If this option is selected, the eNodeB:
● Modifies the reported CQI value if the CellCqiAdjAlgo.InitDeltaCqi
parameter is set to a value smaller than –1 and the UE reports consecutive

eRAN
ACKs as feedback on downlink HARQ. This function does not take effect for
UEs running services with QCI 1.
● Increases the TBS index used for the first downlink HARQ retransmission. The
increased amount is specified by the CellDlschAlgo.DlFirstHarqTxTbsIncNum
parameter.
6.1.4.2 CQI Adjustment Step (FDD)

The CQI adjustment step can be fixed, variable, or adaptively variable. The eNodeB
can fix the CQI adjustment step to the CellCqiAdjAlgo.CqiAdjStep parameter
value.
The CQI adjustment step for UEs during initial access or incoming handovers can
be fixed to the CellDlschAlgo.CqiAdjInitialStep parameter value.
Variable-Step-based CQI Adjustment

This function is controlled by the StepVarySwitch option of the
CellAlgoSwitch.CqiAdjAlgoSwitch parameter.
If this option is selected, the eNodeB determines the CQI adjustment step based
on how likely the UE is to be scheduled in the downlink within the next 100 ms.
● UE is less than 10% likely to be scheduled.
This means that the UE is not accessing many downlink services. The CQI
adjustment step is adjusted based on how far the IBLER is from its configured
target. The farther the IBLER is from the target IBLER, the larger the
adjustment step is, which helps the IBLER more rapidly approach the target
IBLER.
● UE is at least 10% likely to be scheduled.
This means that the UE is accessing many downlink services. The CQI
adjustment step is fixed to the value of the CellCqiAdjAlgo.CqiAdjStep
parameter.
Adaptive Variable-Step-based CQI Adjustment

This function takes effect when the AdaptiveStepVarySwitch option of the
CellAlgoSwitch.CqiAdjAlgoSwitch parameter is selected and the
CellCqiAdjAlgo.CqiAdjStep parameter value is used as the CQI adjustment step.
If this option is selected, the eNodeB adjusts the CQI adjustment step based on
the HARQ feedback for downlink transmissions. This function does not take effect
for UEs running services with QCI 1.
● If the eNodeB consistently receives HARQ ACKs for downlink transmissions, it
increases the CQI by a large step.
● If the eNodeB consistently receives HARQ NACKs for downlink transmissions,
it decreases the CQI by a large step.
6.1.5 Optimized CQI Adjustment Value (TDD)

The eNodeB calculates a CQI adjustment value for each UE based on HARQ
feedback. It sets an initial value for the UE during initial access, RRC connection
reestablishment, or incoming handovers. The larger the CQI adjustment value, the

eRAN
more aggressive the MCS for the UE. The smaller the CQI adjustment value, the
more conservative the MCS for the UE.
6.1.5.1 Initial CQI Adjustment Value (TDD)

The UE-specific initial CQI adjustment value is determined by the threshold for
selecting samples of the cell-specific CQI adjustment value.
● If the threshold is set to a non-zero value, the eNodeB:
– Uses this cell-specific CQI adjustment value as the initial CQI adjustment
value for UEs during initial access, RRC connection reestablishment, or
incoming handovers.
– Uses the UE-specific CQI adjustment value of a MIMO UE as a sample for
maintaining the cell-specific CQI adjustment value when initial
transmission data of the MIMO UE is dynamically scheduled for a
number of times greater than or equal to the threshold.
● If the threshold is set to zero, the initial CQI adjustment value for the UEs
during initial access, RRC connection reestablishment, or incoming handovers
is specified by the CellCqiAdjAlgo.InitDeltaCqi parameter.
In TDD, the threshold for selecting samples of the CQI adjustment value is
specified by different parameters for massive MIMO cells and common cells.
● For common cells, the threshold is specified by
CellCqiAdjAlgo.CellCqiAdjSchCntThld.
● For massive MIMO cells, the threshold is specified by
CellCqiAdjAlgo.CellDeltaCqiSampSelThd.
CQI adjustment value sample selection for massive MIMO cells requires that
the CellPdcchAlgo.AggLvlSelStrageForDualCW parameter be set to
STRATEGYBASEDONCAPACITY. For details about this parameter, see Physical
Channel Resource Management.
6.1.5.2 CQI Adjustment Step (TDD)

In TDD, the CQI adjustment step for UEs during initial access or incoming
handovers is specified by the CellCqiAdjAlgo.CqiAdjStep parameter.
The eNodeB supports adaptive variable-step-based CQI adjustment. This function
is controlled by the AdaptiveStepVarySwitch option of the
CellAlgoSwitch.CqiAdjAlgoSwitch parameter. If this option is selected and the
channel quality is fluctuating sharply, the eNodeB enlarges the CQI adjustment
step so that the CQI can quickly adapt to the channel quality.
The eNodeB can also adjust the CQI adjustment step based on how far the IBLER
is from its configured target. The StepVarySwitch option of the
CellAlgoSwitch.CqiAdjAlgoSwitch parameter specifies whether to enable this
function. If this option is selected, the eNodeB determines the CQI adjustment
step based on how likely the UE is to be scheduled in the downlink within the next
100 ms.
● UE is less than 10% likely to be scheduled.
This means that the UE is not accessing many downlink services. The CQI
adjustment step is adjusted based on how far the IBLER is from its configured
target. The farther the IBLER is from the target IBLER, the larger the

eRAN
adjustment step is, which helps the IBLER more rapidly converge on the target
IBLER.
● UE is at least 10% likely to be scheduled.
This means that the UE is accessing many downlink services. The CQI
adjustment step is fixed to the value of the CellCqiAdjAlgo.CqiAdjStep
parameter.
If the AdaptiveStepVarySwitch and StepVarySwitch options of the

CellAlgoSwitch.CqiAdjAlgoSwitch parameter are both selected, the eNodeB
adjusts the CQI by a larger step between the values specified by the two functions.
6.1.5.3 Optimized CQI Adjustment for Different UEs (TDD)
For UEs Handed Over to a Cell Whose Result of PCI Modulo 3 Conflicts with
the Source Cell's Result of PCI Modulo 3
Huawei eNodeBs support optimized CQI adjustment for UEs handed over to a cell
whose result of PCI modulo 3 conflicts with the source cell's result of PCI modulo
3. The CqiFastCompstSwitch option of the CellAlgoSwitch.CqiAdjAlgoSwitch
parameter specifies whether to enable this function.
In an intra-frequency handover, if the result of the source-cell PCI modulo 3 is the

same as the result of the target-cell PCI modulo 3, the CRS REs in the source cell
are aligned with those in the target cell. In this situation, the CQI reported by the
UE indicates a channel quality that is lower than the actual quality. As a result, an
MCS with a low index is selected for data transmission, decreasing downlink UE
throughput. The eNodeB applies a CQI adjustment value of 0 to a UE after the UE
is handed over to the target cell.
For UEs Using Bundling Mode

For UEs using the HARQ feedback mode of Bundling, the CQI adjustment
optimization is controlled by the TddBundlingCqiAdjOptSwitch option of the
● If this option is selected, the eNodeB increases the CQI adjustment value and
selects a higher-order downlink MCS.
● If this option is deselected, the CQI adjustment optimization is disabled.
For UEs Using Multiplexing Mode

For UEs using the HARQ feedback mode of Multiplexing, the CQI adjustment
optimization is controlled by the TddMultiplexingCqiAdjOptSwitch option of the
● If this option is selected, the eNodeB differentiates between common
subframes and special subframes when adjusting CQIs and selects an
appropriate downlink MCS.
● If this option is deselected, the eNodeB does not differentiate between
common subframes and special subframes when adjusting CQIs.

eRAN
6.1.5.4 CQI Adjustment Value Validity Optimization (TDD)

The validity of a CQI adjustment value is determined based on whether the value
is updated within a specified time τ. If the value is updated within τ, it is regarded
valid. If the value is not updated within τ, it is regarded invalid.
Some CQI adjustments may be invalid for reasons such as adaptive switching
between MIMO and beamforming and switching between single-codeword and
dual-codeword transmissions. When these values are used, they may not match
the channel conditions at that time. The eNodeB can assign new CQI adjustment
values based on the validity of CQI adjustment values. This function is controlled
by the CqiAdjTimeEffSwitch option of the CellAlgoSwitch.CqiAdjAlgoSwitch
parameter.
● If this option is selected, the eNodeB evaluates the validity of CQI
adjustments for each codeword transmission and assigns new CQI adjustment
values to replace invalid values.
● If this option is deselected, the eNodeB does not evaluate the validity of CQI
adjustments for codeword transmissions or assign new CQI adjustment values.
6.2.1 Benefits
Downlink CQI adjustment, using a closed-loop mechanism to dynamically
compensate for inaccurate CQIs reported by UEs, optimizes MCS selection and
increases cell throughput.
If the network has moderate or heavy loads in the downlink (for example, the
downlink PRB usage is greater than 20%) and the proportion of rank 2 and above
exceeds 40%, the downlink user-perceived rate will increase by 1% to 3% after
CQI filtering based on spectral efficiency optimization takes effect.
6.2.2 Impacts
Network Impacts
Downlink target IBLER adaptation and enhanced downlink target IBLER
adaptation do not take effect in TDD cells with CA enabled.
In massive MIMO scenarios, enhanced downlink target IBLER adaptation decreases
the average MCS index, spectral efficiency, and average cell throughput in the
downlink when most UEs in the cell are near the cell center and when wireless to
the x (WTTx) is used or there is little interference. Therefore, enhanced downlink
target IBLER adaptation is not recommended in the preceding massive MIMO
scenarios.

eRAN
Function Impacts
Name Switch
FDD Short TTI SHORT_TTI_S Short TTI Different from UEs

W option of (FDD) that are scheduled
the using normal
CellShortTtiA transmission time
lgo.SttiAlgoS intervals (TTIs), UEs
witch that are scheduled
parameter using short TTIs
cannot use the
optimized CQI
adjustment value, but
use an individual set
of CQI adjustment
values.
TDD DL CoMP CellAlgoSwit DL CoMP Enhanced downlink

ch.DlCompS (TDD) target IBLER
witch adaptation does not
take effect when this
function is enabled.
TDD Coordinated CspcAlgoPara CSPC Enhanced downlink

Scheduling .TddCspcAlgo target IBLER
based Power Switch adaptation does not
Control take effect when this
function is enabled.
6.3 Requirements
6.3.1 Licenses
None
6.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Name Switch
FDD None None None None

eRAN

Name Switch
TDD Capacity- CellPdcchAlg Physical The value of the

based CCE o.AggLvlSelSt Channel CellCqiAdjAlgo.CellD
aggregation rageForDual Resource eltaCqiSampSelThd
level selection CW Management parameter depends on
strategy the capacity-based
CCE aggregation level
selection strategy.

None
6.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
6.3.4 Others
None

Table 6-2 and Table 6-3 describe the parameters used for function activation and
optimization, respectively.

eRAN
Table 6-2 Parameters used for activation

Name
CQI Adjust CellAlgoSwitch.C CqiAdjAlgoSwitch Select this option.

Algorithm qiAdjAlgoSwitch
Switch DlVarIBLERtargetS Select this option.
witch
DlEnVarIblerTar- Select this option.

getSwitch
DlCqiAdjDeltaOpt Select this option.

Switch
RptCqiFltInitSwitc Select this option.

h
StepVarySwitch Select this option.
AdaptiveStepVar- Select this option.

ySwitch
CqiFltSpectralEf- Select this option.

fOptSwitch
Table 6-3 Parameters used for optimization

Name
Initial CellCqiAdjAlgo.In Set this parameter to its recommended

Downlink itDlIblerTarget value.
IBLER Target
Initial Delta CellCqiAdjAlgo.In Set this parameter to its recommended

Cqi itDeltaCqi value.
CQI Adjust CellCqiAdjAlgo.C Set this parameter to its recommended

Step qiAdjStep value.
TBS Index CellDlschAlgo.Lo Set this parameter to its recommended

Threshold for wIblerTargetTbsI value.
Low Target dxThld
IBLER
TBS Index CellDlschAlgo.Hi Set this parameter to its recommended

Threshold for ghIblerTargetTb- value.
High Target sIdxThld
IBLER
CQI CellDlschAlgo.Cqi Set this parameter to its recommended

Adjustment AdjInitialStep value.
Initial Step

eRAN
Activation Command Examples

//Setting the switches of the CQI adjustment algorithm
MOD
CELLALGOSWITCH:LocalCellId=0,CqiAdjAlgoSwitch=DlVarIBLERtargetSwitch-1&DlEnVarIblerTargetSwitch-1&
DlCqiAdjDeltaOptSwitch-1&RptCqiFltInitSwitch-1&StepVarySwitch-1&AdaptiveStepVarySwitch-1&CqiFltSpect
ralEffOptSwitch-1;
Optimization Command Examples

//Modifying cell-specific CQI adjustment parameters
MOD CELLCQIADJALGO:LocalCellId=0,InitDlIblerTarget=10,InitDeltaCqi=-4,CqiAdjStep=10;
//Modifying cell downlink scheduling parameters

MOD
CELLDLSCHALGO:LocalCellId=0,LowIblerTargetTbsIdxThld=21,HighIblerTargetTbsIdxThld=5,CqiAdjInitialStep=
10;


Table 6-4 and Table 6-5 describe the parameters used for function activation and
optimization, respectively.
Table 6-4 Parameters used for activation

Name
CQI Adjust CellAlgoSwitch.C CqiAdjAlgoSwitch Select this option.

Algorithm qiAdjAlgoSwitch
Switch DlVarIBLERtargetS Select this option.
witch
DlEnVarIblerTar- Select this option.

getSwitch
DlCqiAdjDeltaOpt Select this option.

Switch
IblerCqiOffsetS- Select this option.

witch
RptCqiFltInitSwitc Select this option.

h
CqiFastCompstSwi Select this option.

tch
CqiFltOptSwitch Select this option.

eRAN

Name
PreciseMcsAdaptS Select this option.

witch
TddBundlingCqiAd Select this option.

jOptSwitch
TddMultiplexingC- Select this option.

qiAdjOptSwitch
CqiAdjTimeEffSwit Select this option.

ch
StepVarySwitch Select this option.
AdaptiveStepVar- Select this option.

ySwitch
CqiFltSpectralEf- Select this option.

fOptSwitch
Table 6-5 Parameters used for optimization

Name
Initial CellCqiAdjAlgo.In Set this parameter to its recommended

Downlink itDlIblerTarget value.
IBLER Target
Initial Delta CellCqiAdjAlgo.In Set this parameter to its recommended

Cqi itDeltaCqi value.
Cell CQI CellCqiAdjAlgo.C Set this parameter to its recommended

Adjustment ellCqiAdjSchCntT value.
Schedule hld
Count Thld
Cell CQI CellCqiAdjAlgo.C Set this parameter to its recommended

Adjustment ellDeltaCqiSamp- value.
Sample SelThd
Selection Thld
CQI Adjust CellCqiAdjAlgo.C Set this parameter to its recommended

Step qiAdjStep value.
TBS Index CellDlschAlgo.Lo Set this parameter to its recommended

Threshold for wIblerTargetTbsI value.
Low Target dxThld
IBLER

eRAN

Name
TBS Index CellDlschAlgo.Hi Set this parameter to its recommended

Threshold for ghIblerTargetTb- value.
High Target sIdxThld
IBLER
Middle User CellDlschAlgo.Mi When the PreciseAmcSwitch option of the

Mcs dUserMcsThresh CellAlgoSwitch.EmimoSwitch parameter
Threshold old and the DlVarIBLERtargetSwitch option
of the CellAlgoSwitch.CqiAdjAlgoSwitch
parameter are both selected, this
parameter is fixed to 12. In other cases, set
this parameter to its recommended value.
Activation Command Examples

//Setting the switches of the CQI adjustment algorithm
MOD
CELLALGOSWITCH:LocalCellId=0,CqiAdjAlgoSwitch=DlVarIBLERtargetSwitch-1&DlEnVarIblerTargetSwitch-1&
DlCqiAdjDeltaOptSwitch-1&IblerCqiOffsetSwitch-1&RptCqiFltInitSwitch-1&CqiFastCompstSwitch-1&CqiFltOp
tSwitch-1&PreciseMcsAdaptSwitch-1&TddBundlingCqiAdjOptSwitch-1&TddMultiplexingCqiAdjOptSwitch-1&
CqiAdjTimeEffSwitch-1&StepVarySwitch-1&AdaptiveStepVarySwitch-1&CqiFltSpectralEffOptSwitch-1;
Optimization Command Examples

//Modifying cell-specific CQI adjustment parameters
MOD
CELLCQIADJALGO:LocalCellId=0,InitDlIblerTarget=10,InitDeltaCqi=-4,CellCqiAdjSchCntThld=50,CellDeltaCqiSa
mpSelThd=0,CqiAdjStep=10;
//Modifying cell downlink scheduling parameters

MOD
CELLDLSCHALGO:LocalCellId=0,LowIblerTargetTbsIdxThld=21,HighIblerTargetTbsIdxThld=5,MidUserMcsThres
hold=12;


This section describes the procedures for verifying the activation of CQI
adjustment. The following examples show test results for commercial UEs in cells
with a bandwidth of 20 MHz.
Verifying CQI Adjustment

Step 1 Enable a UE to access a cell in the cell center.
Step 2 On the MAE-Access, start channel quality monitoring and BLER monitoring on the
UE.

eRAN
● To start channel quality monitoring, choose Monitor > Signaling Trace >
Signaling Trace Management. Then in the navigation tree on the left,
choose LTE > User Performance Monitoring > Quality of Channel
Monitoring.
● To start BLER monitoring, choose Monitor > Signaling Trace > Signaling
Trace Management. Then in the navigation tree on the left, choose LTE >
User Performance Monitoring > BLER Monitoring.
Step 3 Perform downlink full packet injection on the UE (about 1000 scheduling
instances). During the packet injection, gradually move the UE towards the cell
edge.
Step 4 Check the downlink channel quality and the downlink IBLER. The CQI should be
approximately 11, and the value of Downlink IBLER(Permillage) is fluctuating
around 100. These values indicated that the downlink IBLER is approaching the
default value 10%. The results indicate that CQI adjustment has taken effect.
----End
Verifying Target IBLER Adaptation (FDD)

Step 1 Enable a UE to access the cell.
Step 2 On the MAE-Access, start BLER monitoring on the UE.
To start BLER monitoring, choose Monitor > Signaling Trace > Signaling Trace
Management. Then in the navigation tree on the left, choose LTE > User
Performance Monitoring > BLER Monitoring.
Step 3 Perform downlink full packet injection on the UE. During the packet injection,
gradually move the UE towards the cell edge. Check the downlink BLER. The
downlink IBLER is approaching 30%. The result indicates that target IBLER
adaption has taken effect. If the configured initial downlink target IBLER is 15%,
check whether the downlink IBLER approaches 15%. If the downlink IBLER
approaches 15%, the related parameter setting has taken effect.
----End
Verifying Enhanced Target IBLER Adaptation

Step 1 Enable a UE to access the cell.
Step 2 On the MAE-Access, start BLER monitoring on the UE.
To start BLER monitoring, choose Monitor > Signaling Trace > Signaling Trace
Management. Then in the navigation tree on the left, choose LTE > User
Performance Monitoring > BLER Monitoring.
Step 3 Ensure that the DlEnVarIblerTargetSwitch option has been selected.
Step 4 Perform downlink full packet injection on the UE. During the packet injection,
gradually move the UE towards the cell edge. Check the downlink BLER. The
downlink IBLER is approaching 30%. The result indicates that enhanced target
IBLER adaption has taken effect.
----End

eRAN
Verifying the Function of Optimizing the Initial CQI Adjustment Value for
UEs Handed Over to a Cell Whose Result of PCI Modulo 3 Conflicts with the
Result of Source-Cell PCI Modulo 3 (TDD)
Step 1 Configure two intra-frequency neighboring cells (referred to as cell A and cell B in
the following steps) with conflicting values of PCI modulo 3.
Step 2 Enable a UE to access cell A, perform downlink full packet injection on the UE
(about 800 scheduling instances), and move the UE at a speed of 3 km/h towards
cell B until the UE is handed over to cell B.
Step 3 On the MAE-Access, start channel quality monitoring on the UE.
Choose Monitor > Signaling Trace > Signaling Trace Management. Then in the
navigation tree on the left, choose LTE > User Performance Monitoring > MCS
Count Monitoring.
Step 4 Check the indexes of the MCSs selected for the UE in cell B before and after the
function of optimizing the initial CQI adjustment value for UEs handed over to a
cell whose result of PCI modulo 3 conflicts with the result of source-cell PCI
modulo 3 is enabled.
The index of the MCS applied when the function is disabled is less than the index
of the MCS applied when the function is enabled.
----End
Verifying Adaptation of the Initial Filtered Value of the Reported CQI and
Evaluation of CQI Adjustment Value Validity (TDD)
In the following observation example, the cell has a 20 MHz bandwidth, subframe
configuration 2 and special subframe configuration 7 are used, and the UE is
located at the cell center.
Step 1 Set the cell bandwidth to 20 MHz and configure subframe configuration 2 and
special subframe configuration 7 for the cell.
Step 2 On the MAE-Access, start channel quality monitoring and throughput monitoring
on the UE.
● Choose Monitor > Signaling Trace > Signaling Trace Management. Then in
the navigation tree on the left, choose LTE > User Performance Monitoring >
MCS Count Monitoring.
● To start throughput monitoring, choose Monitor > Signaling Trace >
Signaling Trace Management. Then in the navigation tree on the left,
choose LTE > User Performance Monitoring > Throughput Monitoring.
Step 3 Enable a UE to access the cell at the cell center, station the UE at the cell center,
and perform downlink full packet injection on the UE (about 800 scheduling
instances).
Step 4 Check the indexes of the MCSs and throughput before and after the functions are
enabled.
● The index of the MCS applied when the functions are disabled is less than the
index of the MCS applied when the functions are enabled.

eRAN
● The throughput achieved when the functions are disabled is lower than the
throughput achieved when the functions are enabled.
----End

Monitor the counters listed in Table 6-6, and use the following formula to
calculate the downlink IBLER. Check that the downlink IBLER approaches the
default value 10%.
Table 6-6 Counters related to CQI adjustment

Counter Name Counter Description
L.Traffic.DL.SCH.QPSK.E Number of downlink error TBs after initial

rrTB.Ibler transmission in QPSK modulation mode
L.Traffic.DL.SCH. Number of downlink error TBs after initial

16QAM.ErrTB.Ibler transmission in 16QAM modulation mode
L.Traffic.DL.SCH. Number of downlink error TBs after initial

64QAM.ErrTB.Ibler transmission in 64QAM modulation mode
L.Traffic.DL.SCH.QPSK.T Number of TBs initially transmitted on the downlink

B SCH in QPSK modulation mode
L.Traffic.DL.SCH. Number of TBs initially transmitted on the downlink

16QAM.TB SCH in the 16QAM modulation mode
L.Traffic.DL.SCH. Number of TBs initially transmitted on the downlink

64QAM.TB SCH in the 64QAM modulation mode

eRAN
Description 7 Parameters
7 Parameters
The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End

eRAN
Description 8 Counters
8 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Description 10 Reference Documents
10 Reference Documents
1. MIMO
2. Scheduling
3. eMIMO (FDD)
4. Compact Bandwidth (FDD)
5. NB-IoT Basics (FDD)
6. CDMA and LTE Zero Bufferzone
7. GSM and LTE Buffer Zone Optimization
8. UL Refarming Zero Bufferzone
9. GSM and LTE Spectrum Concurrency
10. Flexible Bandwidth based on Overlap Carriers (FDD)
11. SFN
12. DL CoMP (FDD)
13. Dedicated Carrier for TM9 (FDD)
14. WTTx MU-MIMO (FDD)
15. S1 and X2 Self-Management
16. Physical Channel Resource Management
17. Short TTI (FDD)
18. CSPC

Channel State Management (ERAN16.1 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Channel State Management (ERAN16.1 - 01)

Uploaded by

Copyright:

Available Formats

eRAN

Channel State Management

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................3

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. ii

4.4.2.1 Data Preparation............................................................................................................................................................ 26

5 CQI Reporting Optimization...............................................................................................33

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. iii

6.1.4.1 Initial CQI Adjustment Value (FDD)........................................................................................................................ 48

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. iv

This chapter describes changes not included in the "Parameters", "Counters",

1.1 eRAN16.1 01 (2020-05-21)

Added the mutual impact None FDD ● 3900 and 5900

1.2 eRAN16.1 01 (2020-03-30)

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 1

1.3 eRAN16.1 Draft A (2020-01-15)

Changed the name of None FDD ● 3900 and 5900

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

Feature Differences Between RATs

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 3

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Chapter/Section

LBFD-002031 Aperiodic CQI 4 CQI Reporting

LBFD-060101 Optimization of CQI 5 CQI Reporting

LBFD-00101501 CQI Adjustment 6 CQI Adjustment

This document describes the following TDD features.

Feature ID Feature Name Chapter/Section

TDLBFD-002031 Aperiodic CQI 4 CQI Reporting

TDLBFD-00101501 CQI Adjustment 6 CQI Adjustment

2.4 Feature Differences Between FDD and TDD

LBFD-002031 TDLBFD-002031 In FDD, aperiodic 4 CQI Reporting

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 4

FDD Feature TDD Feature Difference Chapter/Section

LBFD-060101 None This feature is not 5 CQI Reporting

LBFD-001015 TDLBFD-0010150 CQI adjustment 6 CQI Adjustment

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 5

3.1 CSI Reporting Modes

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 6

Table 3-1 CSI reporting modes

1-0 Wideband None Periodic All UEs

1-1 Wideband Wideband Periodic

1-2 Wideband Sub-band Aperiodic

2-0 Wideband CQI None Periodic UEs with the

Wideband CQI None Aperiodic

2-1 Wideband CQI Wideband Periodic

2-2 Wideband CQI Sub-band Aperiodic

3-0 Wideband CQI None Aperiodic All UEs

3-1 Wideband CQI Wideband Aperiodic

Issue 01 (2020-05-21) Copyright © Huawei Technologies Co., Ltd. 7

CSI CQI Reporting PMI Periodic or Supporting

3-2 Wideband CQI Sub-band Aperiodic UEs in

Transmission Periodic CSI Reporting Mode Aperiodic CSI Reporting

TM1 1-0 3-0

TM2 1-1 3-0

TM3 1-0 3-0

TM4 1-1 1-2 (FDD only)

TM6 1-1 1-2 (FDD only)