54 eRAN16.1 LTE Downlink Capacity Solution User Guide

Product Name Confidentiality Level
LTE INTERNAL
Product Version
Total 69 pages
eRAN16.1
eRAN16.1 LTE Downlink Capacity Solution

User Guide
(For Internal Use Only)
Prepared By LTE Solution Design Department Date 2017-04-24
Reviewed By Date yyyy-mm-dd
Reviewed By Date yyyy-mm-dd
Approved By Date yyyy-mm-dd
Huawei Technologies Co., Ltd.

All rights reserved
LTE Downlink Capacity Solution User Guide About This Document
About This Document
Change History
Date Issue CR/Defect ID Section Change Description Author
2014-04-22 1.0 Completed the draft. Wang Xiaojian
2014-05-06 1.1 Revised the document Wang Xiaojian

based on Yang Shijie's
comments.
2014-07-23 1.2 Updated contents for Lu Jun

eRAN8.1 or SRAN10.1.
2015-01-08 1.3 Revised the document Lu Jun

based on Zeng Mingjie
and Huang Haichuan's
comments.
2015-06-15 1.4 Added contents for Shi Juncai

eRAN11.0.
2016-5-19 1.5 Added contents for Lin Jie

eRAN12.0.
2017-10-11 1.6 Added sections Wang Yi

3.1.35CSI Reporting Xue Huaijie
Optimization in CA and
Closed-Loop MIMO Song Minghua
Scenarios, Zhu Wei
3.1.36"Increasing the
CRS Transmission
Disabling Rate," and
3.1.37"Preference of
PDCCH Power Increase,
" for eRAN13.1.
2018-12-25 1.7 Added sections Zhuang Qianqian

3.1.38"CFI Adaption", Yuan Xi
3.1.39"Smart Frequency
Selective Scheduling", Xie Dongfeng
and 3.1.40"CQI Filtering
Based on Spectral
Efficiency Optimization"
for eRAN15.1.
Issue 01 (2021-06-21) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies
Co., Ltd.
LTE Downlink Capacity Solution User Guide About This Document
Date Issue CR/Defect ID Section Change Description Author
2019-11-08 1.8 Added sections Lu Jun

3.1.8"Enhanced Index Wang Xia
Lowering for Multiple Tao Yuechen
UEs with Small-packet
Services", 3.1.42"Data
Learning-based
Downlink Smart AMC",
3.1.43"Two-dimensional
Frequency Selective
Scheduling", and
3.1.43"Two-dimensional
Frequency Selective
Scheduling" for
eRAN16.1.
Distribution List
Copy No. Holder's Name & Role Issue Date
Keywords:
heavy traffic, Benchmark test, downlink throughput
Abstract:
This document describes the LTE downlink capacity solution and the activation method. It
aims to instruct users to improve the network performance and robustness on the live
network, therefore enabling Huawei to exceed the industry benchmark in terms of the
THP vs SINR curve in benchmark and traffic statistics performance competition for the
same city or telecom operator.
Issue 01 (2021-06-21) Huawei Proprietary and Confidential ii

Copyright © Huawei Technologies
Co., Ltd.
LTE Downlink Capacity Solution User Guide Contents
Contents
1 Introduction.......................................................................................................................1
1.1 Purpose...................................................................................................................................................... 1
1.2 Scope......................................................................................................................................................... 1
1.3 Organization............................................................................................................................................... 1
1.3.1 Relationship with Other Documents......................................................................................................... 2
1.3.2 Life Cycle................................................................................................................................................. 2
1.4 Open Issues............................................................................................................................................... 2
1.5 Assumptions............................................................................................................................................... 2
2 Solution Overview.............................................................................................................3
2.1 Scenario Analysis....................................................................................................................................... 3
2.1.1 Commercial Network Application Scenarios............................................................................................ 3
2.1.2 Benchmark Scenarios.............................................................................................................................. 5
2.1.3 Heavy Traffic Scenarios........................................................................................................................... 5
2.2 Benefits....................................................................................................................................................... 5
2.3 General Solution......................................................................................................................................... 6
2.3.2 Commercial Network Application Solution............................................................................................... 8
2.3.3 Benchmark Solution................................................................................................................................. 8
2.3.4 Heavy Traffic Solution.............................................................................................................................. 9
3 Solution Application Guide............................................................................................10

3.1 Commercial Network Applications............................................................................................................ 10
3.1.1 Enhancement of DCCH Symbol Adaptation.......................................................................................... 10
3.1.2 Downlink Frequency Selection............................................................................................................... 11
3.1.3 PUSCH DTX Detection.......................................................................................................................... 12
3.1.4 RBG Adaptation..................................................................................................................................... 14
3.1.5 Optimization of Aggregation Level Selection When the Rank Is Greater Than 1...................................15
3.1.6 Switching of UEs' CQI Configurations and MCS Selection Optimization...............................................16
3.1.7 Lowering of the MCS for Multiple UEs Running Services with Small Packets.......................................17
3.1.8 Enhanced Index Lowering for Multiple UEs with Small-packet Services...............................................17
3.1.8.1 Introduction......................................................................................................................................... 17
3.1.8.2 Parameter Configurations................................................................................................................... 18
3.1.8.3 Effect Evaluation Methods.................................................................................................................. 18
3.1.9 Rank Filter............................................................................................................................................. 18
3.1.10 Optimization of Downlink EPF Scheduling Priority Calculations..........................................................20

3.1.11 Enhancement of Downlink IBLER Adaptation......................................................................................20
3.1.12 Unrestricted PDCCH Code Rate.......................................................................................................... 22
3.1.13 Closed-Loop PDCCH Power Control................................................................................................... 22
3.1.14 Extra Power Boost............................................................................................................................... 23
3.1.15 CA UE Peak Throughput and Optimized UE RLC Parameters Adaption.............................................24
3.1.16 Optimized PUCCH Resource Allocation.............................................................................................. 24
3.1.17 Optimization of DL CQI........................................................................................................................ 25
3.1.18 256QAM.............................................................................................................................................. 26
3.1.19 Downlink Frequency Selective Scheduling Optimization.....................................................................27
3.1.20 Intra-eNodeB CSPC............................................................................................................................ 27
3.1.21 CQI Initial Filtering Optimization.......................................................................................................... 28
3.1.22 MCS Lowering in RBG Initial Transmission......................................................................................... 29
3.1.23 Breathing Pilot..................................................................................................................................... 30
3.1.24 Remaining PDCCH Power Redistribution............................................................................................31
3.1.25 Small Bandwidth RLC Optimization..................................................................................................... 32
3.1.26 Adaptive Compensation for the Initial Value of CQI Adjustment..........................................................33
3.1.27 Enhancement of Adaptive Downlink HARQ Retransmission...............................................................34
3.1.28 Flexible Target IBLER Adaptation........................................................................................................ 35
3.1.29 Optimization of PDCCH Step Adaptation............................................................................................. 36
3.1.30 Low-Power EVM Optimization............................................................................................................. 37
3.1.31 Multi-band Optimal Carrier Selection................................................................................................... 37
3.1.32 Variable Step of CQI Adjustment Optimization for CRS Transmission Disabling.................................38
3.1.33 Precise Scheduling for CA UEs........................................................................................................... 39
3.1.34 NACK/DTX Determination Optimization During PUCCH Demodulation in DL 2CC Scenarios............42
3.1.35 CSI Reporting Optimization in CA and Closed-Loop MIMO Scenarios................................................44
3.1.36 Increasing the CRS Transmission Disabling Rate...............................................................................45
3.1.37 Preference of PDCCH Power Increase................................................................................................46
3.1.38 CFI Adaption........................................................................................................................................ 47
3.1.39 Smart Frequency Selective Scheduling...............................................................................................48
3.1.39.1 Introduction....................................................................................................................................... 48
3.1.39.2 Parameter Configurations................................................................................................................. 48
3.1.39.3 Performance Prediction.................................................................................................................... 48
3.1.39.4 Effect Evaluation Methods................................................................................................................ 49
3.1.40 CQI Filtering Based on Spectral Efficiency Optimization.....................................................................49
3.1.41 NPREO Constant Optimization............................................................................................................ 50
3.1.41.1 Introduction....................................................................................................................................... 50
3.1.42 Data Learning-based Downlink Smart AMC........................................................................................52
3.1.42.1 Introduction....................................................................................................................................... 52

3.1.43 Two-dimensional Frequency Selective Scheduling..............................................................................53
3.1.43.1 Introduction....................................................................................................................................... 53
3.1.44 4T Remaining Power Increase............................................................................................................. 53
3.1.44.1 Introduction....................................................................................................................................... 53
3.2 Benchmark Applications........................................................................................................................... 55
3.3 Heavy Traffic Applications........................................................................................................................ 55
3.3.1 Optimization of the Initial Value of Closed-Loop Adjustment to PDCCH Aggregation Level..................55
3.3.2 CQI Adjustment Step Modification......................................................................................................... 56
3.3.3 Downlink Packet Bundling..................................................................................................................... 56
3.3.4 PDCCH and PDSCH Resource Allocation Optimization Mechanism.....................................................59
3.3.5 RLC Parameter Adaptation Configurations............................................................................................ 59
3.3.6 Optimization of Aperiodic CQI Reporting Triggering..............................................................................60
3.3.7 Stopping Scheduling of Abnormal UEs.................................................................................................. 61
3.3.8 Restrictions on Special Signaling Retransmission in Heavy Traffic Scenarios......................................62
3.3.9 PUCCH Outer Loop Power Control....................................................................................................... 62
3.3.10 Service Model-based Performance Optimization in the Downlink........................................................63
3.3.11 PUCCH Resource Allocation Optimization.......................................................................................... 63
3.3.12 Delayed Transmission of Status Reports............................................................................................. 64
3.3.13 Enhancement of Adaptive Downlink HARQ Retransmission...............................................................65
4 Expected Gains of Function Combinations.................................................................66

5 Cases................................................................................................................................67
6 Reference Documents....................................................................................................68
LTE Downlink Capacity Solution User Guide 6 Reference Documents
1 Introduction
1.1 Purpose
This document serves as an application guide of the LTE downlink capacity increase
solution. It describes downlink capacity increase feature portfolios and end-to-end (E2E)
deliverable applications of the solution, and provides guidelines for future solution-level
application and maintenance and for secondary development of service solutions for
existing LTE systems.
1.2 Scope
This document mainly provides guidelines for implementing the LTE downlink capacity
increase solution. Application guides of related features are optional in this document.
In addition to designs of this solution for the current version, this document includes all
designs for earlier versions.
It also serves as a reference for preparing user guides for other solutions, covering
capacity, radio networking, services, and quality of experience (QoE).
1.3 Organization
Chapter Description
2 Describes the solution overview.

● Introduces the application scenarios of the downlink solution. The
downlink solution design document is the source of this document.
● Provides values and objectives of the solution in the current version,
that is, the system effect after the solution is used.
● Describes the general solution and provides conclusions based on
different scenarios without details.
3 Describes the solution application guide. Provides detailed schemes,

configurations, solution application effect evaluations, and problem
locating instructions, based on different scenarios.
LTE Downlink Capacity Solution User Guide 6 Reference Documents
Chapter Description
4 Describes application cases of the solution on commercial networks.
1.3.1 Relationship with Other Documents

The solution design document is the source of this document.
1.3.2 Life Cycle

The draft of this document was completed at TR5.
This document was updated and finalized at TR6.
1.4 Open Issues

None
1.5 Assumptions
None
2 Solution Overview
2.1 Scenario Analysis

2.1.1 Commercial Network Application Scenarios
Commercial network applications focus on KPIs such as network spectral efficiency and
UE data rate based on MBB services and have the following characteristics:
Figure 2.1.1.1.1.1.1.1 Penetration rate of each type of service in each area
Services with the highest penetration rate include instant message (IM), web browsing,
and social networking service (SNS), followed by streaming media and Email.
Figure 2.1.1.1.1.1.1.2 Single session packet sizes for typical services
Uplink traffic packet sizes Downlink traffic packet sizes

Small packets are transmitted for downlink traffic SNS and Voice over Internet Protocol
(VoIP), small and large packets are transmitted for web browsing, and large packets are
transmitted for streaming media.
● Service distribution features a bipolar trend. The number of times that the single
LTE service volume is smaller than 50 KB accounts for over 80% (except data
card sites) and that ranging from 1 KB to 10 KB accounts for 50%. Heavy traffic
services (greater than 2 MB) take 50% to 80% of total traffic, despite a small
proportion of calls. Small traffic services (smaller than 50 KB) take less than 10%
of total traffic.
Figure 2.1.1.1.1.1.1.3 Service proportion

Proportion of calls in different areas Proportion of call service volumes in different areas
§ Single call service
volume: downlink service
volume generated during
a call (between RAB
setup and RAB release)
§ Service volume
proportion: proportion of
single call service volume
in all call service volumes
X:Single call service volume X:Single call service volume
● 99% of packet intervals are smaller than 2 seconds and packet transmission has
the abruptness feature on the whole.
Figure 2.1.1.1.1.1.1.4 Inter-packet gap
● For TCP services, the relationship between the downlink service rate and
downlink TCP status report transmission rate is reflected in the following formula:
40byte
RUL   RDL
2  MTUbyte
The MTU value may be 1500 bytes or 576 bytes. The numerator is 60 bytes
instead of 40 bytes for IPv6. The formula shows that a smaller MTU value
indicates a larger value of the downlink TCP status report transmission rate.
Typical calculation examples are as follows:
Table 2.1.1.1.1.1.1.4.1 Ratio of uplink MTU to downlink MTU
(X, MTU) 40 Bytes, 40 Bytes, 576 60 Bytes, 1500 60 Bytes, 576
1500 Bytes Bytes Bytes Bytes
RUL:RDL 1.33% 3.47% 2% 5.2%
2.1.2 Benchmark Scenarios

In commercial network Benchmark scenarios, data rates of UEs in drive tests (DTs) are
focused and resource overheads of background UEs have impacts on performance,
which is different from single cell tested networks.
2.1.3 Heavy Traffic Scenarios

In heavy traffic scenarios, PDCCH resources become bottlenecks. Reducing resource
overheads, using PDCCH resources effectively, and utilizing PDSCH resources fully are
key tasks.
2.2 Benefits
Values and general goals of the LTE downlink throughput solution are as follows:
● Maintaining the competitiveness of each vendor during Benchmark tests.
− Intra-city test
− Intra-site test
− Inter-city test
● Maintaining the competitiveness during the swapping of competitors' networks
● Maintaining the competitiveness in the P3 test
● Improving service experience of users on live networks continuously.
− Scenarios when data cards are in the majority
− Scenarios when intelligent terminals are in the majority
− Big event scenarios
● Complying with protocols and maintain the leading roadmap competitiveness
2.3 General Solution
Factors affecting downlink throughput are as follows:
Figure 2.3.1.1.1.1.1.1 Downlink solution panorama

Signaling overhead
PDSCH resource usage
Data resource usage
MIMO Antenna Transmission mode

selection deployment selection
Adjustment mechanism
DL AMC
CSI obtaining
Downlink
PDCCH Reliability&Capacity
DL throughput Control
channel
PUCCH Reliability&Capacity
DL feedback
channel
PUSCH Reliability&Capacity
Frequency selective
DL UE
scheduling&Non-Frequency Priority selection for multi-UE scheduling
selection
selective scheduling
Networking
Channel quality
Power configuration
distribution on the
entire network
Interference control
RRU performance
TCP mechanism
GBR service assurance
QoS Non-GBR service assurance

assurance
Hybrid service assurance
Terminal maturity
The following functions are added to eRAN8.X (including eRAN8.0 and eRAN8.1):
1 Enhanced downlink IBLER adaptation: Downlink MCSs are selected based on
the CQIs reported by UEs and target IBLER. If the target value of IBLER is low,
a lower downlink MCS is likely to be selected. As a result, transmission
efficiency decreases. If the target value of IBLER is too high, a higher downlink
MCS is likely to be selected. As a result, downlink packet retransmission
increases and system resources are wasted. The best target IBLER value is
10% by default. In some scenarios, however, increasing the IBLER value can
improve downlink spectral efficiency of UEs, such as cell edge UEs or UEs at
the cell center or close to the eNodeB performing small-packet services. In
eRAN8.0, the following algorithm is added based on existing target IBLER value
adaptation: The degree of channel quality fluctuation is determined based on
CQIs reported by UEs. Then, the target IBLER value 5%, 10%, or 30% is
selected for data transmission based on the degree. When the degree of
channel quality fluctuation is greater than a certain threshold, the target IBLER
value increases. When it is less than a certain threshold, the target IBLER value
decreases. Otherwise, the existing target IBLER value adaptation process starts.
This function improves downlink spectral efficiency of UEs.
2. Optimized downlink frequency selective decision: Downlink frequency selective
scheduling uses channel quality differences on UE frequency bands to obtain
frequency selective scheduling gains of channels. To calculate scheduling
priorities and select resources, downlink frequency selective scheduling requires
accurate subband CQIs. When UEs are moving at a high speed, the subband
CQIs cannot reflect channel changes in time. Therefore, frequency selective
scheduling applies to scenarios where UEs are moving at a low speed. In
versions earlier than eRAN8.1, the period of downlink frequency selection
decision is 10s by default. In eRAN8.1, the period can be selected to support
fast downlink frequency selective decision, thereby increasing the proportion of
downlink frequency selective scheduling in all scheduling and downlink spectral
efficiency of UEs.
3. Enhanced PDCCH power control: In eRAN8.1, PDCCH resource selection is
enhanced and CCE-level PDCCH power control is introduced. For the same
SNR, the transmit power is increased based on the existing aggregation level for
data transmission. Compared with earlier versions, PDCCH resource selection
can be implemented in a finer way, thereby saving PDCCH resources, reducing
PDCCH congestion probabilities, reducing PDCCH overheads, and increasing
user-perceived downlink rate.
4. PUCCH outer loop power control: The power control for PUCCH Format2x is
implemented based on the SINR of PUCCH Format1a/1b. According to live
network data, interference on Format2x is stronger than that on Format1a/1b. As
a result, the SINR on Format2x is still low when the SINR on Format1a/1b is
converged, resulting in CQI and RANK false check and affecting downlink
transmission efficiency. Therefore, Format2x channel quality needs to be
considered during PUCCH power control. A simple method is adding Format2x-
based BER for outer loop power control based on Format1a/1b SINR power
control so that the target SINR value for Format1a is adjusted adaptively to
adapt to Format2x channel quality changes. This scheme improves downlink
spectral efficiency and user-perceived rate.
5. SRB RLC parameter adaptation: In heavy traffic scenarios, the MAC scheduling
interval becomes larger. If the SRB polling timer is set to a small value, the timer
may expire for multiple times when the peer end does not return a status report
(the scheduling interval is large). As a result, invalid retransmission occurs for
multiple times. If the scheduling interval is excessively large, the retransmission
times may reach 32 and cause call drops. In eRAN8.1, adaptive adjustment is
implemented for the SRB1 and SRB2 polling timers on the eNodeB side to
reduce invalid SRB retransmission. In this manner, usable downlink PRBs and
user-perceived downlink rate can be increased.
2.3.2 Commercial Network Application Solution

This solution applies to commercial networks on which downlink spectral efficiency and
downlink UE data rates are focused. The solution is provided by version incrementally.
Table 2.3.2.1.1.1.1.1.1 Commercial network application solution

Version eRAN6.0 eRAN7.0 eRAN8.0 eRAN8.1 eRAN11.0
Optimization ● Enhanced ● Optimization of ● Enhancement ● Enhanced ● Extra power

Version eRAN6.0 eRAN7.0 eRAN8.0 eRAN8.1 eRAN11.0
point adaptive CFT aggregation of target PDCCH boost

● PUSCH DTX level selection IBLER value power ● CA UE Peak
detection when the rank adaptation in control Throughput
is greater than the downlink ● Enhanced and Optimized
● Initial block 1
error rate ● Optimization of downlink UE RLC
(IBLER) ● Switching of downlink frequency Parameters
adaptation in UEs' CQI frequency selective Adaption
the downlink configurations selective decision ● Optimized
and MCS decision PUCCH
● RBG round up selection Resource
● Enhanced optimization Allocation
downlink ● Lowering of the
frequency ● Optimization
modulation and of DL CQI
selection coding scheme
(MCS) for ● Buffer Aware
multiple UEs Scheduling
running ● 256QAM
services with
small packets
● Rank filter
● Calculations of
downlink EPF
scheduling
priorities
2.3.3 Benchmark Solution

This solution applies to Benchmark tests in which downlink full buffer download rates are
focused. The solution is provided by version incrementally.
Table 2.3.3.1.1.1.1.1.1 Benchmark solution

Version eRAN6.0 eRAN7.0 eRAN8.0 eRAN11.0
Optimization ● Enhancement of ● Optimization of Enhancement of ● Extra power boost

point CFT adaptation aggregation level target IBLER value ● CA UE Peak
● PUSCH DTX selection when the adaptation in the Throughput and
detection rank is greater than 1 downlink Optimized UE
● IBLER ● Switching of UEs' RLC Parameters
adaptation in the CQI configurations Adaption
downlink and MCS selection ● 256QAM
optimization
● Rank filter
2.3.4 Heavy Traffic Solution
This solution applies to heavy traffic scenarios in which the user quantity exceeds 200,
PDCCH congestion occurs, and PDSCH resources are not fully utilized. The solution is
provided by version incrementally.
Table 2.3.4.1.1.1.1.1.1 Heavy traffic solution

Version eRAN6.0 eRAN7.0 eRAN8.X eRAN11.0
Optimization ● PUSCH DTX detection ● RBG adaptation ● Enhanced ● Buffer Aware

point ● Optimization of the initial ● TA optimization PDCCH power Scheduling
value of closed-loop control ● Optimized
● Downlink MCS
adjustment to PDCCH optimization in ● SRB RLC PUCCH
aggregation level handover areas parameter Resource
● Reservation of control adaptation Allocation
● PUCCH
channel elements (CCEs) parameter ● PUCCH outer ● 256QAM
for uplink UEs optimization loop power
● CQI adjustment step control
modification
● RBG round up
● Downlink packet bundling
● PDSCH and PDCCH
resource allocation
optimization mechanism
● RLC parameter adaptation
configurations
● Aperiodic CQI reporting
triggering optimization
3 Solution Application Guide
3.1 Commercial Network Applications

3.1.1 Enhancement of DCCH Symbol Adaptation
Introduction
PDCCH occupies PDSCH resources. Fewer PDSCH resources occupied by PDCCHs
indicate more usable PDSCH resources and higher downlink transmission rate. PDCCH
symbol adaptation is enhanced and fast PDCCH symbol quantity adjustment is
introduced to reduce the number of symbols occupied by the PDCCH and increase
downlink transmission rate.
Enhanced PDCCH symbol adaptation coordinates well with downlink frequency selection.
When the common PDCCH symbol adaptation function is enabled, downlink frequency
selection is enabled only when the PDCCH symbol quantity is 3. After the function of
PDCCH symbol quantity adaptation is enhanced, downlink frequency selection is enabled
when the symbol quantity is adjusted to 1, thereby improving downlink spectral efficiency
and increasing user-perceived downlink rate.
Parameter Configurations
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch =ECfiAdaptionON
Effect Evaluation Methods

Expectation: Downlink throughput in DTs increases by 3%.
1. The PDCCH symbol quantity decreases. The average PDCCH symbol quantity is
calculated as follows:
(L.ChMeas.PDCCH.SymNum.1 x 1 + L.ChMeas.PDCCH.SymNum.2 x 2 +
L.ChMeas.PDCCH.SymNum.3 x
3)/sum(L.ChMeas.PDCCH.SymNum.1:L.ChMeas.PDCCH.SymNum.3)
2. You can observe traffic measurement counters to determine whether user-perceived
downlink rate increases: (L.Thrp.bits.DL –
L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI (ms).
3.1.2 Downlink Frequency Selection
Introduction
Frequency selective scheduling uses channel quality differences on UE frequency bands
to obtain frequency selective scheduling gains of channels. An eNodeB uses subband
CQIs reported by UEs to calculate the scheduling priority of each subband and perform
scheduling based on the subband scheduling priority of each UE on each subband so
that each UE is scheduled on the subband with the best channel quality. As shown in the
following figure, a is assigned to UE1, b is assigned to UE2, and c is assigned to UE1.
This is because UE1 and UE2 have the highest priorities in the scheduling queues
corresponding to the allocated RBGs.
Figure 3.1.2.1.1.1.1.1 Downlink frequency selective resource allocation
To calculate scheduling priorities and select resources, downlink frequency selective

scheduling requires accurate subband CQIs. When UEs are moving at a high speed, the
subband CQIs cannot reflect channel changes in time. Therefore, frequency selective
scheduling applies to scenarios where UEs are moving at a low speed.
When the uplink load is high, the eNodeB increases the period of reporting the subband
CQIs and adaptively adjusts the CQI reporting mode of UEs. The prolonged CQI
reporting period and the changed CQI reporting mode decrease the gain of frequency
selective scheduling.
When the downlink frequency selective scheduling mode is used, an eNodeB needs to
periodically determine the channel fluctuation and moving speed of each UE. When
downlink frequency selection conditions are met, downlink frequency selective scheduling
can be performed. When downlink frequency selection conditions are not met, UEs exit
downlink frequency selective scheduling. The CellDlschAlgo.FreqSelJudgePeriod
parameter is added to control the period of making downlink frequency selective
decisions. If the period is set to a smaller value, the UEs meeting frequency selection
conditions can be scheduled in the downlink sooner and downlink spectral efficiency
enhancement is greater. However, aperiodic CQI scheduling required for downlink
frequency selection increases, increasing uplink interference. When configuring fast
frequency selective decision, you are advised to turn on Doppler measurement reporting
period switches at the same time.
CellAlgoSwitch.DlSchSwitch, CellPdcchAlgo.PdcchSymNumSwitch, and

CellPdcchAlgo.InitPdcchSymNum affect triggering of downlink frequency selective
scheduling, as described in the following table.
Table 3.1.2.1.1.1.1.1.1 Impact of the PDCCH symbol quantity on triggering downlink
frequency selective scheduling
DL Frequency PDCCH Symbol PDCCH Initial Is DL Frequency

Selective Number Adjust Switch Symbol Number Selective
Scheduling Scheduling
Switch Triggered?
ON ON Greater than or Yes

equal to 3
Less than 3 No
The PDCCH Symbol Any adaptive Yes

Number Adjust Switch symbol number
parameter is set to
ECFIADAPTIONON.
OFF Any fixed symbol Yes

number
OFF - - No
When downlink frequency selection is enabled, you are advised to turn on the switch for
controlling simultaneous transmission of aperiodic CQIs and ACK/NACK among
compatibility switches. The purpose is to be compatible with the exceptions that UEs
report aperiodic CQIs in closed-loop MIMO mode.
MOD CELLALGOSWITCH:LOCALCELLID=0,DLSCHSWITCH=FreqSelSwitch-1;
MOD CELLALGOSWITCH:LOCALCELLID=0,DLSCHSWITCH=FreqSelJudgeIgnorDopplerSwitch-1;
MOD CELLDLSCHALGO:LOCALCELLID=0,FREQSELJUDGEPERIOD=x;
MOD CELLULSCHALGO:LOCALCELLID=0,DOPALGOSWITCH=FastReportDopSwitch-1;
MOD CELLPDCCHALGO: LocalCellId=0, PdcchSymNumSwitch =EcfiAdaptionON;

Increase downlink average MCS: (L.ChMeas.PDSCH.MCS.0 x 0 +
L.ChMeas.PDSCH.MCS.1 x 1 + ... + L.ChMeas.PDSCH.MCS.28 x
28)/sum(L.ChMeas.PDSCH.MCS.0 ... L.ChMeas.PDSCH.MCS.28)
Increase downlink spectral efficiency:
L.Thrp.bits.DL/(L.ChMeas.PRB.DL.Used.Avg x Measurement period)

3.1.3 PUSCH DTX Detection
Introduction
Uplink DTX detection refers to that the baseband detects whether a UE sends data on the
PUSCH to determine whether downlink control information (DCI) 0 is correctly received
by the UE. When the baseband detects that the UE fails to detect DCI 0, L2-related
algorithms are processed as follows:
● Perform closed-loop adjustment to the DCI 0 aggregation level. The selection of

the current DCI 0 aggregation level is adjusted according to the CQI after
downlink adjustment and the closed-loop adjustment value of DCI 2A. When
there are no downlink services or downlink services are sparse, the adjusted
CQI and DCI 2A adjustment value are inaccurate. In this case, the adjustment
value of DCI 0 needs to be introduced to ensure the DCI 0 demodulation
performance.
● Initial transmission is implemented again for uplink scheduling based on DTX
results to save uplink RB resources.
● DTX is removed from uplink SINR adjustment to improve the precision of uplink
MCS selection.
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=PuschDtxSwitch-1;

Expected gains: Uplink throughput in downlink interference scenarios in DTs increases.
Uplink RBLER decreases, and uplink spectral efficiency increases by about 3%.
1. Trace items of PUSCH DTX are available on the U2000 for you to observe the
percentage of PUSCH DTX, which is less than 5% in most cases.
Figure 3.1.3.1.1.1.1.1 U2000 PUSCH DTX
2. Decrease uplink RBLER:

(L.Traffic.UL.SCH.QPSK.ErrTB.Rbler +
L.Traffic.UL.SCH.16QAM.ErrTB.Rbler +
L.Traffic.UL.SCH.64QAM.ErrTB.Rbler)/(L.Traffic.UL.SCH.QPSK.TB +
L.Traffic.UL.SCH.16QAM.TB + L.Traffic.UL.SCH.64QAM.TB)
3. You can evaluate the gains of the feature by evaluating uplink spectral
efficiency.
L.Thrp.bits.UL/(L.ChMeas.PRB.UL.DrbUsed.Avg x Measurement period)
3.1.4 RBG Adaptation

Introduction
During RB resource allocation in downlink scheduling, two handling policies (round up
and round down) are available when the number of RBGs required by a UE is not an
integer.
Round down: RB resources can be fully used but the number of scheduling times will
increase.
Round up: All data can be scheduled at a time but a few RB resources will be wasted.
Adaptation: When resources for allocation exceed one RBG, use the roundup method.
When resources for allocation are less than one RBG, allocate resources based on the
actual RB quantity.
Assume that the bandwidth is 10 MHz, as shown in the following figure.
When 5 RBs are required by a UE, 3 RBs are used for scheduling in the current TTI and
remaining data is scheduled in subsequent TTIs if the round down method is used. If the
round up method is used, 6 RBs are used for scheduling but 1 RB is Padding. Six RBs
are used for scheduling when adaptation is used.
When 2 RBs are required by a UE, 2 RBs are used for scheduling in the current TTI if the
round down method is used. If the round up method is used, 3 RBs are used for
scheduling but 1 RB is Padding. Two RBs are used for scheduling when adaptation is
used.
Figure 3.1.4.1.1.1.1.1 RBG allocation

RBG round up:
MOD CELLDLSCHALGO: RbgAllocStrategy = ROUND_UP;
RBG round down:
MOD CELLDLSCHALGO: RbgAllocStrategy = ROUND_DOWN;
RBG adaptation:
MOD CELLDLSCHALGO: RbgAllocStrategy = ADAPTIVE;

Expected gains: The downlink UE data rate in typical MBB service scenarios increases by
5% to 10%.
Increase downlink UE data rate: (L.Thrp.bits.DL –

L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI
3.1.5 Optimization of Aggregation Level Selection When the

Rank Is Greater Than 1
Introduction
When the rank for downlink UE scheduling is greater than 1, the aggregation level of the
PDCCH is selected based on the sum of spectral efficiency corresponding to the dual-
codeword MCS. The selection method easily causes PDCCH BLER in dual-codeword
scenarios because transmit diversity is used for the PDCCH. To improve demodulation
performance of the PDCCH at near distances, the method of selecting the aggregation
level of the PDCCH needs to be optimized, that is, selecting the aggregation level based
on the spectral efficiency corresponding to the MCS corresponding to one of the two
codewords.
Currently, in the dual-codeword scenario, if dual-codeword transmission is used, the MCS
entered when the aggregation level of the PDCCH is calculated is the MCS index (less
than or equal to 28) corresponding to the spectral efficiency that is closest to the sum of
effMCS1 and effMCS2, instead of the IMCS. The selected aggregation level tends to be
small because the equivalent MCS conversion method is radical in most scenarios. In
addition, the scope of aggregation level closed-loop adjustment is limited. Therefore,
when the converted CQI after adjustment is too high, the aggregation level cannot be
adjusted to a proper value even if the closed-loop adjustment switch is enabled.
Optimization needs to be performed to solve the preceding problem, thereby improving
PDCCH correctness.
MOD CELLPDCCHALGO: LocalCellId=0, AggLvlSelStrageForDualCW = STRATEGYBASEDONCOVERAGE;
The scenario where rank 2 is used in downlink scheduling and the PDCCH BLER is high
(the PDSCH is not a bottleneck) exists when the pilot of an intra-eNodeB neighboring cell
strongly interferes the PDCCH of the cell. In this scenario, the optimization point reduces
the PDCCH BLER.
PDCCH BLER:
(L.ChMeas.PDCCH.DL.DTXNum.AggLvl1 + L.ChMeas.PDCCH.DL.DTXNum.AggLvl2
+ L.ChMeas.PDCCH.DL.DTXNum.AggLvl4 +
L.ChMeas.PDCCH.DL.DTXNum.AggLvl8)/(L.ChMeas.PDCCH.AggLvl1Num +
L.ChMeas.PDCCH.AggLvl2Num + L.ChMeas.PDCCH.AggLvl4Num +
L.ChMeas.PDCCH.AggLvl8Num)
3.1.6 Switching of UEs' CQI Configurations and MCS Selection

Optimization
Introduction
The LTE inter-site distance is small and there is a high cell handover probability when
UEs are moving. Importance has been attached to handover KPIs in earlier LTE versions
and special measures has been taken to optimize handover KPIs in handover areas. With
the development of LTE networks, attention is increasingly focused on the throughput in
handover areas. Therefore, related operations need to be optimized to achieve a balance
between the throughput in handover areas and handover KPIs. The optimization points
include the following:
Parameters are introduced to enable the downlink MCS0 order to be fixed within a
specified period before and after the handover.
Aperiodic CQI fields are added to handover commands. In addition, the aperiodic CQI
reporting is triggered through downlink services after the handover to obtain downlink
channel quality information in advance, thereby improving downlink throughput in
handover areas.
MOD CQIADAPTIVECFG: LocalCellId=0,HoAperiodicCqiCfgSwitch=ON;
MOD CELLDLSCHALGO: LocalCellId=0,HoStaticMcsTimer=10;

The gain from this optimization point is that the downlink spectral efficiency and
throughput are increased within a short period after a UE is handed over to a target cell.
The gain may not be noticeable when being included in the throughput of the whole test
and the downlink throughput remains unchanged. The gain looks relatively noticeable in
the handover area of the scatter chart. The quantitative evaluation result can be obtained
from the average geographic downlink throughput.
The following figures show the downlink SINR-THP before and after optimization,
respectively. The number of points indicating high SINR and low throughput decreases
greatly, that is, the number of points indicating low downlink throughput caused by low
MCS index in handover areas decreases greatly.
Figure 3.1.6.1.1.1.1.1 Downlink SINR-THP optimization scatter chart
DL THP improved in hand over

low DL THP in hand over area
area
3.1.7 Lowering of the MCS for Multiple UEs Running Services

with Small Packets
Introduction
Currently, for capability-limited UEs, the eNodeB lowers the MCS to increase the number
of RBs for the scheduling of a single UE to simplify product implementation. This applies
to the peak rate test of a single UE. The defect in the current algorithm lies in the
following: If multiple background UEs exist on the network or services using small packets
coexist with heavy traffic services, the eNodeB does not lower the MCS to increase the
number of RBs for capability-limited UEs. As a result, resources are wasted and the peak
throughput is not the optimal. Similarly, lowering the MCS for UEs running services with
small packets in the downlink applies to the scenario where there is only one connection
to be scheduled in the current TTI. Performance cannot be improved when multiple
services using small packets coexist in one TTI.
To solve the preceding problem that application scenarios are limited, for capability-
limited UEs, the eNodeB now lowers the MCS to increase the number of RBs for the last
UE to be scheduled (the single UE scenario is expanded to the multiple UE scenario). For
small packet service scheduling, the eNodeB now lowers the MCS to increase the
number of RBs for the last service to be scheduled (the single service scenario is
expanded to the multiple service scenario).
After the preceding changes, the competitiveness of downlink throughput and delay is
improved. In addition, downlink performance in the commercial scenario can be
improved.
MOD CELLDLSCHALGO:LOCALCELLID=0,RBPRIMCSSELECTSTRATEGY=MULTIUSER_STRATEGY,
RBPRIMCSSELECTRATIOTHD=10;
● The method of determining whether the feature has taken effect is as follows:
The proportion of MCS index 0 and RB usage that is calculated based on
L.ChMeas.PDSCH.MCS.0 and L.ChMeas.PRB.DL.Used.Avg can be used to
determine whether the feature has taken effect. If the proportion of MCS index 0
and RB usage increase sharply, the feature has taken effect.
● Feature gain evaluation:
Observe throughput improvement. The throughput is calculated by using the
following formula: Throughput = (L.Thrp.bits.DL –
3.1.8 Enhanced Index Lowering for Multiple UEs with Small-

packet Services
3.1.8.1 Introduction
With the current index lowering solution for multiple UEs running small-packet services,
the TBS index of the last UE to be scheduled can be reduced to 0 to increase the number
of RBs, which is radical. In addition, the proportion of index reduction in the previous
measurement period is used as the condition for determining whether to lower the order
in the next measurement period. As a result, ping-pong effect may occur, and the
probability of gains may be lost.
To solve the preceding problem, the maximum TBS index reduction for the last UE to be
scheduled has been changed to a configurable parameter. In addition, when interference
randomization takes effect, the eNodeB limits the range of RBs whose the index can be
reduced for the last to-be-scheduled UE to further control the interference to neighboring
cells.
3.1.8.2 Parameter Configurations

MOD CELLDLSCHALGO:LOCALCELLID=0,
RBPRIMCSSELECTSTRATEGY=MULTIUSER_STRATEGY,RBPRIMCSSELECTRATIOTHD=100;
(CELLALGOSWITCH.INTERFRANDSWITCH=OFF) MOD
CELLALGOSWITCH:LOCALCELLID=0,RBPRIMCSSELECTMAXDECTBSIDX=6;
(CELLALGOSWITCH.INTERFRANDSWITCH= ENB_BASED) MOD
CELLALGOSWITCH:LOCALCELLID=0,RBPRIMCSSELECTMAXDECTBSIDX=4;
3.1.8.3 Effect Evaluation Methods

1. The method of determining whether the feature has taken effect is as follows:
Observe the downlink IBLER and the average downlink MCS index. If their values are
lower than those before the function is enabled, this function has taken effect.
2 Feature gain evaluation
Observe the throughput rate improvement. The throughput rate is calculated by using the
following formula: Throughput rate = (L.Thrp.bits.DL –
3.1.9 Rank Filter
Introduction
Currently, when open-loop and closed-loop multiplexing are used for Huawei downlink
MIMO mode, the eNodeB depends on the rank reported by a UE for scheduling, which is
not reliable due to the following reasons:
● The reported rank may be incorrect because:

− There are differences among rank measurement algorithms or algorithm-related
parameters. As a result, the SINRs for measuring reported rank 2/3/4 for different
UEs are different, which means that the rank reported by a UE is handed over to
the high order rank too early (which means that the performance of the low order
rank is the highest) or too late (which means that the performance of the high
order rank is the highest).
− A UE measures and reports the rank based on downlink pilot signals. There are
differences between power and interference of the pilot and data channel. As a
result, the reported rank cannot reflect actual data channel status.
The envelope cannot be formed for rank adaptation because the rank
reported by the UE is incorrect. As a result, the loss of downlink throughput
occurs, as shown in Figure 3.1.9.1.1.1.1.1.
Figure 3.1.9.1.1.1.1.1 High downlink SINR-THP on EPA3
● Some reported ranks that are not reliable can be filtered out. Currently, most
false rank reporting identified during simulation and tests is the early rank 2
handover and single-codeword scheduling can reduce interference between
networks compared with dual-codeword scheduling. Therefore, the eNodeB
uses rank 1 instead of rank 2 for scheduling.
● There is a probability of missing check or false check on baseband RI reliability.
The probability of false check on baseband RI reliability is smaller than 1%,
however, the loss is caused once false check occurs. For example, the
throughput decreases by 50% if rank 2 is encoded to rank 1. Figure
3.1.9.1.1.1.1.2 shows that there is a sharp decrease in the peak throughput.
Figure 3.1.9.1.1.1.1.2 Downlink RLC throughput changing with time
This feature increases user throughput in scenarios where ranks reported by a

UE change frequently if the rank handover is too early. The gains may be
negative in the scenario where the rank handover is too late.
MOD CELLDLSCHALGO: LocalCellId=0, DlRankOptimizeSwitch=ON;

This optimization point corrects the ranks reported by UEs to improve accuracy of rank
reporting for scheduling, thereby increasing downlink throughput in scenarios where
ranks reported by a UE change frequently (the gain obtained in simulation and lab MIMO
tests ranges from 0 to 5%). This function is not recommended for commercial networks.
3.1.10 Optimization of Downlink EPF Scheduling Priority

Calculations
Introduction
For non-GBR services, the scheduling priority is calculated by using the following formula:
Prio = eff/r(t) x f(QoS) when the EPF scheduling policy is used. The average throughput
r(t) is calculated by using the following formula: r(t) = (1-alpha) x r(t-1) + alpha x R(t). R(t)
indicates the instantaneous throughput. This calculation method ensures fairness among
UEs in the full buffer scenario. In the MBB service scenario, perceived throughput is used
to evaluate performance. In this case, the throughput filtered value is replaced by the
perceived throughput in the EPF scheduling formula to improve the perceived throughput
and user experience.
MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch= EpfEnhancedSwitch -1;
Observe throughput improvement. The throughput is calculated by using the following
formula: Throughput = (L.Thrp.bits.DL –
In the typical MBB service scenario, the expected gain ranges from 5% to 10%.
3.1.11 Enhancement of Downlink IBLER Adaptation

Introduction
Downlink CQI adjustment is implemented based on a target IBLER value so that the
IBLER can converge to the target value, thereby maximizing throughput. In versions
earlier than eRAN6.0, the downlink target IBLER value is fixed at 10%. In eRAN6.0, the
target IBLER value adaptation scheme is introduced; the scheme adjusts the target
IBLER value to 30% for low SINR UEs (low MCS index) and UEs running a large
proportion of services with small packets and retains the value for other UEs at 10%. The
scheme is obtained based on full buffer service simulation and tests, and gain scenarios
are limited.
For multi-UE non-full-buffer service scenarios, reported CQIs do not match channels well
during scheduling due to network interference fluctuation. In this scenario, AMC can be
optimized noticeably. Enhancement of downlink target IBLER value adaptation uses a
relative spectral efficiency difference to implement target IBLER value adaptation
decision. When the difference is greater than a threshold, a larger target IBLER value is
used. Otherwise, a smaller target IBLER value is used.
MOD CELLALGOSWITCH:LOCALCELLID=0,CQIADJALGOSWITCH=DlEnVarIblerTargetSwitch-1;

Observe the performance counters in the following table. The converged DL IBLER value
is calculated by using the following formula:
Table 3.1.11.1.1.1.1.1.1 Performance counters for CQI adjustment

Counter Description
L.Traffic.DL.SCH.QPSK.ErrTB.Ibler Number of downlink error TBs after initial

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

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

transmission in 64QAM modulation mode
L.Traffic.DL.SCH.QPSK.TB Number of TBs initially transmitted on the

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

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

downlink SCH in 64QAM modulation
mode
Unrestricted PDCCH Bite Rate
Introduction
When the bandwidth is 10 MHz/15 MHz/20 MHz and downlink channel quality is high,
PDCCH CCE can be set to 1 to reduce PDCCH overheads and increase downlink
capacity.
MOD CELLPDCCHALGO:LOCALCELLID=0,PdcchMaxCodeRate=14;

Observe L.ChMeas.PDCCH.AggLvl1Num. There is no value at first and then values
become available. Observe the decrease in the average number of PDCCH symbols:
3.1.12 Unrestricted PDCCH Code Rate

Introduction
When the bandwidth is 10 MHz/15 MHz/20 MHz and downlink channel quality is high,
choose PDCCH CCE aggregation level 1 to reduce PDCCH overheads and increase
downlink capacity.
MOD CELLPDCCHALGO:LOCALCELLID=0,PdcchMaxCodeRate=95;

Observe L.ChMeas.PDCCH.AggLvl1Num. There is no value at first and then values
become available. Observe the average number of PDCCH symbols and the number
decreases: (L.ChMeas.PDCCH.SymNum.1 x 1 + L.ChMeas.PDCCH.SymNum.2 x 2 +
3.1.13 Closed-Loop PDCCH Power Control
Introduction
In eRAN8.X, PDCCH resources are selected based on power and aggregation levels. For
the same downlink channel quality, the same PDCCH BLER can be obtained by lowering
the aggregation level by one and increasing power. By lowering the PDCCH aggregation
level by one, the number of uplink/downlink scheduling failures caused by search space
failures decreases, thereby reducing service transmission delays of UEs and improving
user-perceived rate. In Benchmark scenarios, the PDCCH aggregation level can be
lowered to reduce CFI usage, improve downlink data rate of Benchmark UEs, and
improve competitiveness.
MOD CELLPDCCHALGO:LOCALCELLID=0,PdcchPowerEnhancedSwitch=ON;

Observe the decrease in the average number of CCEs:
(L.ChMeas.PDCCH.AggLvl1Num x 1 + L.ChMeas.PDCCH.AggLvl2Num x 2 +
L.ChMeas.PDCCH.AggLvl4Num x 4 + L.ChMeas.PDCCH.AggLvl8Num x 8)/sum
(L.ChMeas.PDCCH.AggLvl1Num x 1:L.ChMeas.PDCCH.AggLvl1Num x 8)
Observe the decrease in the average number of PDCCH symbols:

3.1.14 Extra Power Boost

Introduction
When RRUs are not fully configured, the remaining power of the power amplifier is used
to increase the DL transmit power and DL throughput of CEUs. Increase PDCCH transmit
power and lower the aggregation level to improve average DL throughput of cells.
Parameters: to be supplemented (the parameter workflow for this feature has not been
reviewed).
Gain scenarios are as follows:
The DL power is not fully used, for example, the rated RRU power is 60 W, but only 40 W
is actually used.
Three types of RRU modules are as follows: RRU3268 (2.6 GHz), RRU3642 (800 MHz),
and RU3635 (800 MHz). The last two types are used for China Telecom.
If the baseband processing unit (BBP) is UBBPd3/4/5/6, the TX/RX mode is not set to
4T4R, and the cells are configured to work in 5/10/15/20 MHz, the AWPC algorithm can
be activated to further improve throughput of CEUs.
This solution brings more gains in coverage-limited scenarios than in interference-limited

scenarios.
On:
MOD CELLDLSCHALGO:LOCALCELLID=0, CellDlCoverEnhanceSwitch-1;
Off:
MOD CELLDLSCHALGO:LOCALCELLID=0, CellDlCoverEnhanceSwitch-0;

Expected performance: CEUs' throughput increases by 5% to 10%. If the AWPC
algorithm activation conditions are met (the BBP is UBBPd3/4/5/6, the TX/RX mode is not
set to 4T4R, and the cells are configured to work in 5/10/15/20 MHz), CEUs' throughput
increases by 5% to 30% after the EPB-s is enabled.
You can observe the value of the following formula to determine whether the DL
perceivable throughput of the CEU increases:
L.Thrp.bits.DL.CEU/L.Thrp.Time.DL.CEU
perceivable throughput of the UE increases:
(L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI
3.1.15 CA UE Peak Throughput and Optimized UE RLC

Parameters Adaption
Introduction
Principles: Optimize the policy of allocating the amount of data to each component carrier
(CC) and the AMC transmission policy to increase the DL throughput when multiple
component carriers (CCs) and MIMO are used while the total number of bits transmitted
in the downlink exceeds the maximum transmission capability of a UE. When the number
of the CA UEs is small on the live network, RLC parameters are configured in a
differentiated way (including the Reordering Timer and the Status Report Prohibit Timer).
On:
MOD CELLDLSCHALGO: LOCALCELLID=0, DlCaUeCapAllocStrategy=ADAPTIVELY_DIVIDED;MOD

CELLDLSCHALGO: LOCALCELLID=0, DlCaUserSchSwitch=DlCaUserRbPriMcsSelSwitch-1
Off:
MOD CELLDLSCHALGO: LOCALCELLID=0, DlCaUeCapAllocStrategy=EQUALLY_DIVIDED;MOD

CELLDLSCHALGO: LOCALCELLID=0, DlCaUserSchSwitch=DlCaUserRbPriMcsSelSwitch-0

A benchmark test shows that using this solution increases the throughput of a CA UE at
the cell center by up to 10% in the following scenario:
● Three or more carriers are aggregated for a UE.
● A CA UE's maximum capability is lower than the maximum Uu interface
capability. For example, a category 6 UE supports 300 Mbit/s at most in the
downlink while the maximum Uu interface throughput will reach 450 Mbit/s when
three carriers, each operating at a bandwidth of 20 MHz, are aggregated.
● The UE is located at the cell center but does not have the highest throughput.
You can observe the counter L.Thrp.bits.DL to determine whether the DL
throughput of the UE increases.
3.1.16 Optimized PUCCH Resource Allocation

Introduction
Initial PUCCH power adaptation: When detecting that the PUCCH SINR is too high after a
UE accesses the network, the eNodeB uses an event triggering mechanism to quickly
generate power control commands for the UE to reduce the PUCCH power. You can set
parameters on the MML command window to activate this function.
PUCCH FMT2 code channel allocation optimization: Widen the interval of the first half
code channel of each RB for reporting CQI. For example, six CQI code channels can be
allocated on an RB. The first three code channels are numbered 0, 4 and 8, and the last
three code channels are numbered 2, 6 and 10. If not optimized, the code channels
allocation sequence is 0, 2, 4, 6, 8, and 10.
On:
MOD CellAlgoSwitch:LOCALCELLID=0, UlPcAlgoSwitch= PucchInitialPcSwitch-1; MOD

PUCCHCfg:LOCALCELLID=0, Format2ChAllocMode=1;
Off:
MOD CellAlgoSwitch:LOCALCELLID=0, UlPcAlgoSwitch= PucchInitialPcSwitch-0; MOD

PUCCHCfg:LOCALCELLID=0, Format2ChAllocMode=0;

Expected performance: The DL perceivable throughput of the UE increases by 5% at
most (gains vary depending on the PUCCH channel interference and the RSRP value).
perceivable throughput of the UE increases:
3.1.17 Optimization of DL CQI

Introduction
Optimization points of DL aperiodic CQI are as follows:
● When the eNodeB receives a CQI with a value of 0 reported by UE, the eNodeB
determines that the CQI is reliable if the reliable indicator is set to 1. The
eNodeB updates the time when the reliable CQI is received but does not perform
scheduling.
● If aperiodic piggyback CQI on PUSCH is supported, adopt it.
● If preallocation is supported, adopt it.
● When piggyback CQI on PUSCH and preallocation are not supported, if the
elapsed time is less than 5 ms since the last scheduling, scheduling is not
performed in the current TTI, and the value of aperiodic CQI request flag is not
cleared.
● When piggyback CQI on PUSCH and preallocation are not supported, if the
elapsed time is greater than 5 ms since the last scheduling, the CQI ONLY
scheduling is performed.
The optimization takes effect when the downlink frequency selection switch is turned on.
On:
MOD CELLULSCHALGO:LOCALCELLID=0, AperiodicCsiUlTxMode=CsiWiUlService;
Off:
MOD CELLULSCHALGO:LOCALCELLID=0,AperiodicCsiUlTxMode=CsiOnly;

When the downlink frequency selection switch is turned on, negative impacts on CSI
reporting and UL perceivable throughput of the UE are reduced (the UL perceivable
throughput of the UE increases by 10% at most), and the loss of the DL perceivable
throughput of the UE does not exceed 2%. However, other KPIs are not affected
obviously. You can observe the value of the following formula to determine whether the
UL throughput of the UE increases:
(L.Thrp.bits.UL – L.Thrp.bits.UE.UL.SmallPkt)/L.Thrp.Time.UE.UL.RmvSmallPkt
throughput of the UE decreases:
3.1.18 256QAM
Introduction
3GPP Release 12 introduces the 256 quadrature amplitude modulation (256QAM)
scheme. 256QAM is a supplement of the downlink quadrature phase shift keying (QPSK),
16QAM and 64QAM. It is used to increase bit rate of the UE when radio conditions are
good. Downlink 256QAM improves CCUs' downlink spectral efficiency and DL
throughput. Gains are affected by the quality of the radio channel, the EVM of the RF TX
channel of the eNodeB and that of the UEs. Each symbol in 256QAM carries information
about eight bits. Compared with 64QAM, 256QAM supports larger TBS, and the
theoretical peak spectral efficiency increases by 33%.
On:
MOD CELLALGOSWITCH:LOCALCELLID=0, DL256QAMALGOSWITCH=Dl256QamSwitch-1;

Off:
MOD CELLALGOSWITCH:LOCALCELLID=0, DL256QAMALGOSWITCH=Dl256QamSwitch-0;

You can use the following equation to calculate the 256QAM scheduling ratio:
256QAM scheduling ratio = L.Traffic.DL.SCH.256QAM.TB/

(L.Traffic.DL.SCH.256QAM.TB + L.Traffic.DL.SCH. 64QAM.TB +
L.Traffic.DL.SCH.16QAM.TB + L.Traffic.DL.SCH.QPSK.TB)
You can observe the counter L.Thrp.bits.DL to determine whether the DL throughput of
the UE increases.
throughput of the UE decreases:
3.1.19 Downlink Frequency Selective Scheduling Optimization

Introduction
When downlink frequency selective scheduling is enabled, if the interval between the
current time and the last downlink scheduling of a UE is greater than or equal to a preset
threshold, the UE stops triggering aperiodic CQI reporting in the current TTI. The
threshold can be decreased to avoid unnecessary CQI reporting, therefore minimizing the
impact of downlink frequency selective scheduling on the uplink throughput.
Parameter configurations
Run the following command to enable this function:
MOD CELLDLSCHALGO:LOCALCELLID=0, NOSCHSTOPACQITHD=5;
Run the following command to disable this function:
MOD CELLDLSCHALGO:LOCALCELLID=0, NOSCHSTOPACQITHD=40;

Expected gains: A smaller value of the NOSCHSTOPACQITHD parameter causes a
higher user throughput when downlink frequency selective scheduling is enabled. When
this parameter is set to 5, downlink frequency selective scheduling is enabled, and the
uplink PRB usage is greater than 30%, the negative gains of aperiodic CQI reporting on
the uplink user throughput decrease by more than 20%.
The following formula can be used to determine whether the user-perceived uplink
throughput increases:
You can check whether the optimization takes effect by viewing the sum of the counters
L.ChMeas.CQI.DL.SingleCW.Aperiodic, L.ChMeas.CQI.DL.DualCW.Code0.Periodic,
and L.ChMeas.CQI.DL.DualCW.Code1.Aperiodic. If the sum does not change
obviously, the value of the NOSCHSTOPACQITHD parameter is large.
3.1.20 Intra-eNodeB CSPC
Introduction
This algorithm comprehensively considers the resource allocation status of cells
configured on a BBP. By using the CQIs reported by intra-BBP CSPC UEs receiving
intra-BBP interference, this algorithm calibrates the reported CQIs based on the
interference change at the measurement and scheduling moments, therefore improving
the spectral efficiency of such UEs.
The procedure for calibrating CQIs is as follows:
The eNodeB estimates the resource allocation status of cells configured on a BBP and
obtains the number of resource block groups (RBGs) of each cell.
Based on the RBG overlapping between intra-BBP interference neighboring cells and the
serving cell, the eNodeB calibrates the modulation and coding scheme (MCS) for joint
AMC (JAMC) UEs before performing downlink scheduling. This helps the eNodeB obtain
a more accurate MCS for downlink scheduling.
This optimization applies to the scenario where the downlink PRB usage is greater than
10%. The optimization gains increase as the traffic load increases. When the average
PRB usage reaches 50%, the gains reach the peak value. When the PRB usage
continues to increase, the gains decrease gradually. The optimization does not present
gains when the PRB usage reaches the maximum.
Enable this function:
Set the IntraEnbCspcSw parameter of the CELLCSPCPARA MO to ON.
Disable this function:
Set the IntraEnbCspcSw parameter of the CELLCSPCPARA MO to OFF.

Expected gains: When the PRB usage on a network reaches about 50%, the average
downlink user throughput increases by about 5% and the average downlink CEU
throughput increases by about 10%.
The following formula is used to determine whether the downlink CEU throughput
increases:
L.Thrp.bits.DL.CEU/L.Thrp.Time.DL.CEU
The following formula is used to determine whether the downlink user throughput
increases:
3.1.21 CQI Initial Filtering Optimization
Introduction
After the initial access or incoming handover, the eNodeB performs initial filtering
optimization on full-band CQIs reported by UEs at the medium or long distance from the
cell center, which reduces the time of increasing the CQI filtering value from the initial
value to the target value. This method increases the MCS, improves the spectral
efficiency, and increases the downlink user throughput.
MOD CELLALGOSWITCH: LocalCellId=0, CqiAdjAlgoSwitch= RptCqiFltInitSwitch -1;
MOD CELLALGOSWITCH: LocalCellId=0, CqiAdjAlgoSwitch= RptCqiFltInitSwitch -0;

Expected gains:
If there are only a small number of UEs in a cell (fewer than 100 UEs in a 10 MHz cell)
when the CQI initial filtering optimization is enabled, the user throughput increases by up
to 5%.
increases:
3.1.22 MCS Lowering in RBG Initial Transmission

Introduction
When the resource block group (RBG) allocation policy is ROUND UP or ADAPTIVE, it is
probable that the size of TBs allocated to initially transmitted UEs exceeds the size of
traffic volume to be transferred at the MAC layer. In such a case, the MCS index needs to
be lowered. MCS lowering in RBG initial transmission applies to the scenario where
scheduled small packets (tail packets) occupy a high proportion and most of TTIs are
those in which the MCS indexes of scheduled UEs can be lowered.
If the RBG allocation policy is ROUND UP or ADAPTIVE, the eNodeB selects a UE by

order from the UEs for which RBs are successfully scheduled based on the resource
scheduling type 0 in the current TTI. If the size of TBs used for the UE's initial
transmission is greater than the size of traffic volume to be transferred at the UE's MAC
layer, the eNodeB lowers the MCS index for initially transmitted code word, on condition
that the total size of TBs used for the UE's initial transmission is greater than or equal to
the size of traffic volume to be transferred at the UE's MAC layer. If MCS lowering in RBG
initial transmission takes effect, the MCS index for the UE is lowered, thereby decreasing
the UE's IBLER and increasing its user-perceived downlink throughput.
To enable MCS lowering in RBG initial transmission, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0,

DLSCHSWITCH= SMALLPKTMCSSELECTALGOSW-1;
To disable MCS lowering in RBG initial transmission, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0,

DLSCHSWITCH= SMALLPKTMCSSELECTALGOSW-0;
Performance Prediction
● If the RBG allocation policy is ROUND UP or ADAPTIVE in the test scenario and
the proportion of scheduled small packets (tail packets) is high (for example,
greater than 20%), this function has the following impacts on KPIs:
− The IBLER decreases.
− The user-perceived downlink throughput increases by 1% to 5%.
− The average downlink cell throughput increases by 1% to 5%.
− The average downlink MCS indexes of UEs decrease, depending on the
proportion of UEs on which this function takes effect.
− Other KPIs related to the control plane are basically not affected.
● If the RBG allocation policy is ROUND UP or ADAPTIVE in the test scenario and
the proportion of scheduled small packets (tail packets) is low (for example,
lower than 20%), this function does not improve KPIs significantly and the KPIs
related to the user plane and control plane are basically not affected.
● If the RBG allocation policy is ROUND DOWN in the test scenario, this function
does not take effect and KPIs are not affected.
● In the benchmark scenario, the full buffer service will occupy all available RBs
and it is unnecessary to lower the MCS index. In this scenario, this function does
not improve KPIs significantly.

You can use cell trace results to determine whether this function takes effect. In the result
of the 34th trace, if the TbsDecType field is 0 and the TbsDecFlag field is 1, this function
takes effect in the current TTI.
3.1.23 Breathing Pilot

Introduction
Based on the load status between a cell and its neighboring cell, breathing pilot
determines whether to shut down the transmission of reference signals. If the neighboring
cell is not loaded, this function shuts down the transmission of the neighboring cell's
reference signals. This mitigates the interference of the neighboring cell's reference
signals to the data signals of the serving cell and further increases the SINR and MCS
index of the serving cell's data signals, thereby improving system performance.
To enable breathing pilot, select the BreathingPilotSwitch option of the
BreathingPilotAlgoSwitch parameter.
To disable breathing pilot, deselect the BreathingPilotSwitch option of the

BreathingPilotAlgoSwitch parameter.
● Since the DRX offset of UEs is set in a centralized manner (including changes
between 2T and 4T), CQI resources are allocated in more centralized time
domains. Currently, this change does not affect network KPIs.
● The decrease of PUSCH RBs (two RBs decreased in maximum) will lead to the
decrease of uplink throughput. The proportion of the maximum number of RBs
that can be decreased at or near the cell center is calculated according to the
formula: 2 RBs/Number of RBs at the bandwidth.
● According to the test result in a lab, when the ElasticCarrierSwitch parameter
is set to ON in the networking scenario with three 4T cells, turning on
EmimoElasticPortSwitch can increase downlink user throughput by 5%.
● The measurement result of the serving cell is inaccurate. As demonstrated in the
test result, the RSRP of the serving cell fluctuates significantly, affecting the
accuracy of reported measurement reports (MRs). In addition, the handover
success rate may decrease (by less than 2%).
On the live network, breathing pilot offers the following benefits:
● If the DL PRB usage of the network is less than 1% and the average number of
RRC_CONNECTED UEs in an entire day is less than 20, user-perceived
downlink throughput increases by 15%.
● If the DL PRB usage of the network ranges from 1% to 5% and the average
number of RRC_CONNECTED UEs in an entire day is less than 20, user-
perceived downlink throughput increases by 5% to 10%.
● If the DL PRB usage of the network is greater than 5% and the average number
of RRC_CONNECTED UEs in an entire day is less than 20, this function does
not offer benefits.
In the drive test (DT) scenario, breathing pilot offers the following benefits:
● If the DL PRB usage of the DT area or the neighboring cell is less than 1% and
the average number of RRC_CONNECTED UEs in an entire day is less than 20,
the throughput of cell center users (CCUs) does not increase, the throughput of
users near the cell center increases by about 30%, and the throughput of cell
edge users (CEUs) increases by about 60%.
● If the DL PRB usage of the DT area or the neighboring cell ranges from 1% to
5% and the average number of RRC_CONNECTED UEs in an entire day is less
than 20, the throughput of CCUs does not increase, the throughput of users near
the cell center increases by about 5%, and the throughput of CEUs increases by
about 10%.
● If the DL PRB usage of the DT area or the neighboring cell is greater than 5%
and the average number of RRC_CONNECTED UEs in an entire day is less
than 20, breathing pilot does not offer benefits to CCUs, users near the cell
center, or CEUs.
You can observe the counters in the following formula to determine whether the user-
perceived downlink throughput increases:
The L.Cell.ElasticCarrierEnableTti.Num counter indicates the number of TTIs in which

Elastic Carrier takes effect in a cell.
3.1.24 Remaining PDCCH Power Redistribution

Introduction
On the live network, discontinuous transmission (DTX) exists. When the network load is
not heavy, PDCCH load is light and the remaining PDCCH power can be redistributed.
Some PDCCH power is not used owing to a small number of scheduled users in each TTI
or CCE fragmentation. After RB scheduling is complete in a TTI, the eNodeB redistributes
the remaining power to desired users so as to improve their PDCCH performance.
Remaining PDCCH power redistribution offers the following benefits:
● Increasing CEUs' PDCCH power and throughput, and decreasing CEUs' DTX
proportion and service drop rate
● Increasing the PDCCH power and the number of downlink scheduling times for
users performing large-packet services, thereby improving spectral efficiency
and user throughput in a cell
● Increasing the number of schedulable RBs or scheduling times for DT users
To enable remaining PDCCH power redistribution, run the following commands:
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchSparePowerAllocStrage=WEAKCOVERAGEUSER;

MOD CELLPDCCHALGO:LOCALCELLID=0, PdcchSparePowerAllocStrage= BIGPKTUSER;
To disable remaining PDCCH power redistribution, run the following command:
MOD CELLPDCCHALGO:LOCALCELLID=0, PdcchSparePowerAllocStrage= NONE;
If the PdcchSparePowerAllocStrage parameter is set to WEAKCOVERAGEUSER, the
PDCCH performance of CEUs can be enhanced and the DTX proportion of CEUs can be
decreased. The benefits of this function become more and more obvious as the number
of users with low MCS indexes grows. Low MCS indexes indicate indexes 0 to 5. If the
proportion of users with low MCS indexes is less than 10%, it is predicted that user-
perceived throughput increases by up to 1%. If the proportion of users with low MCS
indexes is from 10% to 20%, it is predicted that user-perceived throughput increases by
up to 2%. If the proportion of users with low MCS indexes is greater than 20%, it is
predicted that user-perceived throughput increases by 1% to 2%.
You can observe the counters in the following formula to determine whether user-
Check whether the PdcchSparePowerAllocStrage parameter is set to

WEAKCOVERAGEUSER.
Check whether the proportion of DTX users to which PDCCH resources are allocated
with aggregation level 8 decreases according to the following formula:
L.ChMeas.PDCCH.DL.DTXNum.AggLvl8/L.ChMeas.PDCCH.AggLvl8Num
Check whether CEU throughput increases.
3.1.25 Small Bandwidth RLC Optimization

Introduction
When the bandwidth is 5 MHz, 3 MHz, or 1.4 MHz and the radio link control (RLC)
adaptation parameters SrbRlcParaAdaptSwitch and RlcParaAdaptSwitch are set to
ON(On), the eNodeB adaptively configures different heavy-UE number thresholds
according to the cell bandwidth. When small bandwidth RLC optimization takes effect, the
automatic repeat request (ARQ) retransmission rate decreases, and the user-perceived
rate and capacity increases in different scenarios.
The capacity can be determined by observing the counter L.thrp.bits.DL.
To enable small bandwidth RLC optimization, run the following command:
MOD CELLALGOSWITCH:LOCALCELLID=X,SmallBandOptSwitch=SmallBandRlcOptSwitch-1.
To disable low bandwidth RLC optimization, run the following command:
MOD CELLALGOSWITCH:LOCALCELLID=X,SmallBandOptSwitch=SmallBandRlcOptSwitch-0.
In the heavy-load scenarios when the bandwidth is 5 MHz, 3 MHz, or 1.4 MHz:
● If the RlcParaAdaptSwitch parameter is not set to ON(On), the small bandwidth

capacity increase feature generates gains when there are more than 75 UEs in a
cell with a bandwidth of 5 MHz, more than 45 UEs in a cell with a bandwidth of 3
MHz, and more than 20 UEs in a cell with a bandwidth of 1.4 MHz.
● If the RlcParaAdaptSwitch is set to ON(On), the small bandwidth capacity
increase feature generates gains when there are more than 75 and less than
150 UEs in a cell with a bandwidth of 5 MHz, more than 45 and less than 150
UEs in a cell with a bandwidth of 3 MHz, and more than 20 and less than 150
UEs in a cell with a bandwidth of 1.4 MHz.
● If control channel elements (CCEs) are sufficient, the user-perceived rate
increases by 2% to 5%.
● If CCEs are insufficient (with a usage of over 70%) and the physical resource
block (PRB) usage is less than 90%, the DL capacity increases by 1% to 2%.
● If CCEs are insufficient and the PRB usage is greater than 95%, the interference
is high and many UEs are located at weak coverage areas. In such a case, cell
edge UEs obtains scheduling chances and occupies CCE resources of cell
center UEs. The expected negative gain in DL capacity is less than 2%.
3.1.26 Adaptive Compensation for the Initial Value of CQI

Adjustment
Introduction
The eNodeB applies compensation to the CQI adjustment value when the following
conditions are met:
● The eNodeB sets the CellCqiAdjAlgo.InitDeltaCqi parameter to a value smaller
than –1 for the UE at initial access or an incoming handover.
● The UE reports consecutive ACKs as feedback on DL HARQ.
If adaptive compensation for the initial value of CQI adjustment takes effect, UEs'
modulation and coding scheme (MCS) selection during network attach is more accurate,
thereby increasing the user-perceived downlink throughput.
To enable adaptive compensation for the initial value of CQI adjustment:
MOD CELLALGOSWITCH:LOCALCELLID=0, CQIADJALGOSWITCH =PreciseMcsAdaptSwitch-1;
To disable adaptive compensation for the initial value of CQI adjustment:
In MBB scenarios where the downlink IBLER is far lower than the target value and the
downlink PRB usage is greater than 20%, the user-perceived downlink rate increases by
1% to 5%. When the downlink PRB usage is lower than or equal to 20%, the user-
perceived downlink rate increases by 0% to 2%. The downlink IBLER and residual block
error rate (RBLER) are expected to increase.

You can observe the counters in the following formula to determine whether the average
downlink user throughput increases:
DL User Throughput = (L.Thrp.bits.DL –

You can observe the counters in the following formula to determine whether downlink
IBLER increases:
DL 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.QPSK.TB + L.Traffic.DL.SCH.16QAM.TB +
L.Traffic.DL.SCH.64QAM.TB)
3.1.27 Enhancement of Adaptive Downlink HARQ

Retransmission
Introduction
To effectively use combining gains of hybrid automatic repeat request (HARQ), the
transport block size (TBS) index used for the initial HARQ retransmission is increased by
a fixed value to reduce the number of used resource blocks (RBs). If enhancement of
adaptive downlink HARQ retransmission takes effect, the user-perceived downlink rate
increases in heavy-traffic scenarios.
To enable enhancement of adaptive downlink HARQ retransmission:

MOD CELLDLSCHALGO:LOCALCELLID=0, DlFirstHarqTxTbsIncNum=3;
To disable enhancement of adaptive downlink HARQ retransmission:
The user-perceived downlink rate increases by 1% to 5% in heavy-traffic scenarios where
the downlink PRB usage is greater than 50% and the downlink IBLER is between 9% and
30%, the proportion of UEs at the cell center is lower than or equal to 25%. The downlink
RBLER is expected to possibly increase.


You can observe the counters in the following formula to determine whether the number
of downlink RB retransmissions reduces:
(L.ChMeas.PRB.DL.RANK1.MCS.29 + ... + L.ChMeas.PRB.DL.RANK1.MCS.31 +

L.ChMeas.PRB.DL.RANK2.MCS.29 + ... + L.ChMeas.PRB.DL.RANK2.MCS.31)/
L.ChMeas.PRB.DL.RANK2.MCS.0 + ... + L.ChMeas.PRB.DL.RANK2.MCS.31)
3.1.28 Flexible Target IBLER Adaptation
Introduction
According to theoretical analysis, spectral efficiency can be improved by increasing the
target IBLER when channel quality fluctuates significantly and by reducing the target
IBLER when channel quality fluctuates slightly. If optimization of enhanced target IBLER
adaptation takes effect, the target IBLER is adjusted adaptively according to the channel
fluctuation. This increases downlink user throughput.
To enable flexible target IBLER adaptation and set the TBS index threshold for both low
target IBLER and high target IBLER:
MOD CELLDLSCHALGO:LOCALCELLID=0,LowIblerTargetTbsIdxThld=21,HighIblerTargetTbsIdxThld=5;
To disable flexible target IBLER adaptation:
MOD CELLDLSCHALGO:LOCALCELLID=0,LowIblerTargetTbsIdxThld=255;
In heavy-traffic scenarios, the PRB usage is from 10% to 50%, and the CPU usage is less
than 55%. The downlink user throughput is expected to increase by 0% to 3%, and the
downlink IBLER is expected to increase.
In DTs, the downlink user throughput at the cell center is expected to increase by 1% to
3%, and the downlink IBLER decreases. The downlink user throughput at the cell edge is
expected to increase by 0% to 5%, and the downlink IBLER increases.


You can observe the counters in the following formula to determine whether downlink
IBLER increases:
DL 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.QPSK.TB + L.Traffic.DL.SCH.16QAM.TB +
L.Traffic.DL.SCH.64QAM.TB)
3.1.29 Optimization of PDCCH Step Adaptation

Introduction
● It is difficult for the PDCCH DTX proportion on the live network to reach the
target value. Excessively high or low DTX proportion may affect network
performance. Therefore, PDCCH aggregation level adjustment needs to be
accelerated to enable the DTX proportion to quickly approach the target value.
● When the PDCCH DTX proportion is excessively low, the PDCCH aggregation
level is low. Accelerating the reduction of aggregation level adjustment
decreases CCE usage and saves CCE resources.
● When the PDCCH DTX proportion is excessively high, the PDCCH aggregation
level is high. In this case, aggregation level increase needs to be accelerated to
save RB and CCE resources used for retransmission and improve demodulation
performance.
To set a recommended PDCCH step:
MOD CELLPDCCHALGO:LOCALCELLID=0, PdcchOutLoopAdjBaseStep=5;
To set the PDCCH step to its default value:
MOD CELLPDCCHALGO:LOCALCELLID=0, PdcchOutLoopAdjBaseStep=2;
● Scenarios of positive gains: DTX occurs in PDCCH.
● Scenarios of negative gains: the eNodeB cannot identify the DTX caused by
feedback errors in the case of severe uplink interference. If the uplink check
error rate is higher than 1%, this function generates negative gains. If the uplink
interference is greater than -105 dB after preliminary uplink interference
observation, you are not advised to change the default parameter values.

You can observe the following counters to determine whether the DL perceivable
throughput of the UE increases:
3.1.30 Low-Power EVM Optimization

Introduction
In the scenarios of low-power RRUs, the retreating power step is refined to no higher than
0.5 dB to improve the RRU error vector magnitude (EVM). The original steps are 1 dB, 3
dB, and 6 dB.
This function is enabled inside RRUs and invisible to customers. There are no MML
commands or parameters.
In the scenarios of low-power RRUs (with a power headroom other than 1 dB, 3 dB or 6
dB), the SINR at the cell center increases by 0.5 dB to 1 dB.
When RRUs have a power headroom of 2.5 dB, the downlink SINR of a UE at the cell
center increases by 1 dB. When full-buffer services are performed at the cell center, the
throughput increases by over 1% in 64QAM modulation mode and by 3% to 5% in
256QAM modulation mode.
When the power headroom for RRUs is set to 1 dB, 3 dB, or 6 dB (the same as the
original solution), this function generates no gains to the SINR at the cell center and the
EVM.

You can observe whether this function takes effect during DTs. It does not affect KPIs on
the live network.
3.1.31 Multi-band Optimal Carrier Selection

Introduction
In multi-band carrier networking scenarios, one area is covered by multiple frequencies.
The coverage of different frequencies totally or partially overlaps. Most of the live network
traffic comes from large-packet services such as web, video, and burst services. Such
data is continuously transmitted for 100 ms or even several seconds. A small percentage
of the live network traffic comes from small-packet services such as heartbeat packets,
which are transmitted for a large number of times at long intervals. This function
considers the instantaneous load information and radio channel quality of multiple
carriers. By fast capturing the collision between large-packet services, this function
transfers a specific large-packet service to the carrier with higher spectral efficiency or
lighter load to improve downlink user experience.
To enable multi-band optimal carrier selection:
Run the MOD CELLALGOSWITCH command, with the MbfcsSwitch option selected in
the Load balancing algorithm switch parameter.
To disable multi-band optimal carrier selection:
Run the MOD CELLALGOSWITCH command, with the MbfcsSwitch option deselected
in the Load balancing algorithm switch parameter.
Expected Gains
This function generates gains in the following scenarios:
● Multi-band networking with three or more frequencies is deployed.

● The average PRB usage is higher than 30%.
● Most of the traffic comes from large-packet services, such as on the network of
VIVA in Kuwait.
● The 3CC UE penetration rate is smaller than 10%.
On multi-band networks with three to five carriers and an average PRB usage of 30% to
70%, the average user-perceived downlink rate increases by 5% to 20%.
On light-traffic networks (with the PRB usage smaller than 30%), this function generates
no gains.
A higher CA-capable UE proportion indicates that the aggregation capability is closer to

the number of frequencies with the same coverage in this area, and therefore fewer gains
are obtained. The reverse is also applicable.
The increased number of UE handovers may decrease the network handover success
rate and increase the handover signaling overheads. The increased number of handovers
for a UE may increase the service drop rate.
Inter- and intra-frequency measurements increase the uplink overheads and may slightly
decrease the uplink throughput.
This function does not apply to benchmark scenarios.

You can observe the following counters to determine whether the DL perceivable
throughput of the UE increases:
3.1.32 Variable Step of CQI Adjustment Optimization for CRS

Transmission Disabling
Introduction
When breathing pilot or coordinated pilot scheduling for eMIMO is enabled for UEs
regarded as large-packet UEs, the CQI adjustment is performed at a large step in case of
significant channel quality changes. That is, the CQI adjustment is performed at a large
step when the UE reports consecutive ACKs or NACKs as feedback on DL HARQ.
To enable variable step of CQI adjustment optimization for CRS transmission disabling:
MOD CELLALGOSWITCH:LOCALCELLID=0,CQIADJALGOSWITCH=PilotOffCqiAdjOptSwitch-1;
To disable variable step of CQI adjustment optimization for CRS transmission disabling:
CELLALGOSWITCH:LOCALCELLID=0,CQIADJALGOSWITCH=PilotOffCqiAdjOptSwitch-0;
In DTs, the downlink user throughput at the middle and edge of a cell is expected to
increase by 0% to 5%.

You can observe whether the IBLER for UEs at the middle and edge of the cell increases
during DTs.
3.1.33 Precise Scheduling for CA UEs
Introduction
Level-1 CA scheduling can be optimized in the following ways if pre-scheduling is
performed:
● The eNodeB allocates as much data as possible to the SCC for pre-scheduling.
− If the SCC is idle, scheduling capabilities of the SCC are fully utilized.
− If the SCC is congested and UEs cannot obtain resources, pre-scheduling fails. In
this situation, the PCC schedules buffered data without proportion restrictions,
fully utilizing scheduling capabilities of the PCC.
In pre-scheduling, the data allocation proportion between the PCC and SCC can
be adjusted for level-l CA scheduling.
● The last packet can be scheduled on the SCC. If pre-scheduling on the SCC
fails, the PCC schedules the last packet.
Start the level-1 CA scheduling
process.
Yes
Is the data volume
buffered at the RLC layer
less than the threshold?
No
Determine the data allocation

proportion for the PCC and
SCC.
Allocate all data to the
first SCC.
Notify the SCC of the

buffered data volume
and data allocation
proportion.
End
To enable this function:
Set the CaEnhancedPreAllocSwitch option of the CaAlgoExtSwitch parameter under

MO eNodeBAlgoSwitch to 1.
To disable this function:
Set the CaEnhancedPreAllocSwitch option of the CaAlgoExtSwitch parameter under

MO eNodeBAlgoSwitch to 0.
Expected Gains
This function brings obvious gains when all of the following conditions are met:
● PUCCHAlgoSwitch.Dl2CCAckResShareSw is set to ON
● Both the PRB usage and the penetration rate of CA UEs are greater than 10%.
● The traffic proportion of activated CA UEs is greater than 10% and less than
40%.
Traffic proportion of activated CA users = L.Thrp.bits.DL.CAUser/L.Thrp.bits.DL
When PUCCHAlgoSwitch.Dl2CCAckResShareSw is set to ON and both the PRB
usage and CA user proportion are greater than 10%, the throughput for CA users and
that for all users increases by 5%- 15% and 1%-5%, respectively.
Gains of precise scheduling for CA UEs are related to the penetration rate of CA UEs and
traffic proportion of CA users, as illustrated in the following figures.
Gains of the average user throughput
5%
3%
1%
10% 30% 50% 70% 90%
Gains of the average throughput for CA users

15%
10%
5%
10% 30% 50% 70% 90%
Gains of the average user throughput
5%
3%
1%
5% 10% 30% 40% 50%

Gains of the average throughput for CA users
15%
10%
5%
5% 10% 30% 40% 50% Traffic proportion of

activated CA users
The following figures show simulation results of precise scheduling for CA users.
3.1.34 NACK/DTX Determination Optimization During PUCCH
Demodulation in DL 2CC Scenarios
Introduction
In DL 2CC scenarios using PUCCH format 3, PUCCH demodulation enables the eNodeB
to accurately identify NACK fed back by the SCC when NACK and DTX messages fed
back at Layer 1 are confused, obtaining HARQ combination gains.
Run the following commands to enable this function:
MOD CAMGTCFG: LocalCellId=xx, CellCaAlgoSwitch=2CCDlCaEnhanceSwitch-1;

MOD ENODEBALGOSWITCH: CaAlgoExtSwitch=CaEnhancedPreAllocSwitch-1;
Run the following commands to disable this function:
MOD CAMGTCFG: LocalCellId=xx, CellCaAlgoSwitch=2CCDlCaEnhanceSwitch-0;

MOD ENODEBALGOSWITCH: CaAlgoExtSwitch=CaEnhancedPreAllocSwitch-0;

There are no relevant counters. You can perform CELLDT Layer 2 tracing (trace number:
161) to check whether the function takes effect.
When this function is enabled, HARQ results are reported to Layer 2 in PUCCH format 3.
The SCC detects no HARQ from the UE, and therefore NACK is filled. The value of
ulAck1 is displayed as 0.
When this function is disabled, the value of ulAck1 is displayed as 15.
The downlink throughput increases by 2% according to DT results.
3.1.35 CSI Reporting Optimization in CA and Closed-Loop
MIMO Scenarios
Introduction
For activated CA UEs in closed-loop MIMO mode, enhanced aperiodic CQI reporting
enables CA UEs to periodically feed back PMIs, improving downlink benchmark
performance of CA UEs.
MOD CAMGTCFG: LocalCellId=xx, CellCaAlgoSwitch=CaAperiodicCqiRptSwitch-1;

MOD CELLDLSCHALGO: LocalCellId=0, FDUEEnhAperCQITrigPeriod=5ms,
EnAperiodicCqiTrigStrategy=CQI_REPORTINTERVAL_BASED, NoSchStopACqiThd=4;
Run the following commands to disable this function:
MOD CAMGTCFG: LocalCellId=xx, CellCaAlgoSwitch=CaAperiodicCqiRptSwitch-0;

Perform CELLDT Layer 2 tracing (trace number:102) or observe on the UE side to check
whether aperiodic CQIs are periodically reported. If they are, this function has taken
effect.
Expected Gains
This function brings obvious gains in benchmark DT scenarios with CA and closed-loop
MIMO enabled. In addition, the test UE must be a CA UE.
KPI Prediction
The downlink throughput increases by more than 5% according to DT results.
3.1.36 Increasing the CRS Transmission Disabling Rate

Introduction
According to 3GPP specifications, the On Duration Timer and DRX Inactivity Timer stop
after the UE receives a DRX Command MAC Control Element message from the
eNodeB.
● The eNodeB monitors UEs in the active state of DRX mode. If it detects that a
UE has no data to receive or send, it sends a DRX Command MAC Control
Element message to the UE, instructing the UE to enter the sleep state. In this
way, the eNodeB increases the CRS transmission disabling rate. The function of
increasing the CRS transmission disabling rate is controlled by the
CellDlschAlgo.PilotOffRateIncreaseSw parameter. If this parameter is set to
NOT_BASED_ON_MEASUREMENT, this function takes effect in the local cell.
● If this parameter is set to BASED_ON_MEASUREMENT, this function takes
effect in the neighboring cells if they are notified that there are large-packet
users in the local cell. eNodeBs exchange information through eX2 interfaces.
To enable this function:
Run the MOD CELLDLSCHALGO command with PilotOffRateIncreaseSw set to

NOT_BASED_ON_MEASUREMENT or BASED_ON_MEASUREMENT.
To disable this function:
Run the MOD CELLDLSCHALGO command with PilotOffRateIncreaseSw set to OFF.
Gain-Obtaining Scenarios
This function brings obvious gains in the following scenarios:
● There is significant intra-frequency interference in contiguous coverage areas,
for example, in areas where the typical inter-site distance is 500 m.
(recommended scenario for this function)
● The average number of UEs is less than 20 and the average downlink PRB
usage is less than 10% during off-peak hours in a cell.
● For LTE FDD, the cell bandwidth is 10 MHz, 15 MHz, or 20 MHz. For LTE FDD,
the cell bandwidth is 5 MHz, 10 MHz, 15 MHz, or 20 MHz.
When this function is enabled with the breathing pilot function, the average downlink
throughput will further increase by 1%-5%.

You can observe the counters in the following formula to determine whether the user-
3.1.37 Preference of PDCCH Power Increase

Introduction
This function is used with PDCCH closed-loop power control (specified by the
PdcchPowerEnhancedSwitch parameter). It enables the eNodeB to use a lower
PDCCH aggregation level under a specific SINR by increasing the power, effectively
lowering the congestion probability caused by using high aggregation levels and reducing
CCE allocation failures.
//Enabling PDCCH power control enhancement
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchPowerEnhancedSwitch=ON;
//Configuring the upper-limit for PDCCH power increase
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchPowerBoostUpperLimit=3dB;
MOD CELLPDCCHALGO: LOCALCELLID=0, PdcchPowerBoostUpperLimit=NULL;
The user-perceived throughput is expected to increase by 1% to 5% when all of the
following conditions are met:
● The uplink and downlink CCE usage is higher than 30%.
● The RB usage is 30% to 90%.
● The average number of PDCCH symbols is greater than 2.
● The uplink and downlink CCE failure rate is greater than 5%.
In other scenarios, this function has no gains or even negative gains.

You can observe the counters in the following formulas to determine whether the user-
Number of CCEs used by PDCCHs = L.ChMeas.CCE.CommUsed +

L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed
3.1.38 CFI Adaption

Introduction
The number of available CCEs is considered for CFI increase.
● When the number of available CCEs is greater than a threshold, CCEs are
considered sufficient, and the CFI does not increase.
● When the number of available CCEs is less than the threshold and CCE
allocation fails, the CFI increases. If this function takes effect, the average CFI
decreases, the number of available symbols for PDSCHs increases, and user-
perceived downlink throughput increases in heavy-load scenarios. Parameter
Configurations
Run the following command to set the CCE threshold for CFI adaption to the
recommended value (20 MHz bandwidth is used as an example):
MOD CELLPDCCHALGO: LocalCellId=0, CfiAdjCceThld =16CCE;
Run the following command to set the threshold to the default value:
MOD CELLPDCCHALGO: LocalCellId=0, CfiAdjCceThld =INF;
When CfiAdjCceThld is set to a value other than INF, the average CFI is smaller than
that when CfiAdjCceThld is set to INF, the downlink throughput increases (by 0 to 5%
with the recommended setting), but the number of CCE allocation failures increases and
the uplink throughput slightly decreases (by 2% with the recommended setting).
In moderate- and heavy-load scenarios (downlink RB usage > 50%; average CFI > 2), the
throughput gains are obvious. The smaller the value of CfiAdjCceThld, the smaller the
average CFI, and the higher the downlink throughput.
In moderate- and low-load scenarios, the throughput gains are unstable. Changing the
value of CfiAdjCceThld makes little difference.

You can observe counters in the following formula to determine whether the average
downlink CFI decreases:
(L.ChMeas.PDCCH.SymNum.1 + 2 x L.ChMeas.PDCCH.SymNum.2 + 3 x
L.ChMeas.PDCCH.SymNum.3 + 4 x
L.ChMeas.PDCCH.SymNum.4)/(L.ChMeas.PDCCH.SymNum.1 + ... +
L.ChMeas.PDCCH.SymNum.4)
You can observe counters in the following formula to determine whether the average
downlink throughput increases:

3.1.39 Smart Frequency Selective Scheduling
Smart frequency selective scheduling adds multi-user admission and large-packet
identification to the original frequency selective scheduling, and dynamically adjusts the
triggering period and validity period of aperiodic CQI reporting. It applies to heavy-load
hotspot scenarios where multiple low-speed UEs are running services and improves
downlink user experience.

Activation
//Enabling downlink frequency selective scheduling
//Enabling downlink smart frequency selective scheduling
MOD CELLALGOSWITCH:LOCALCELLID=0,DLSCHEXTSWITCH=SMART_FSS_SWITCH-1;
//Setting the frequency selective scheduling evaluation period

MOD CELLDLSCHALGO:LOCALCELLID=0,FREQSELJUDGEPERIOD=1;
//Enabling fast reporting of Doppler measurements
MOD CELLULSCHALGO:LOCALCELLID=0,DOPALGOSWITCH=FastReportDopSwitch-1;
Deactivation
//Disabling downlink smart frequency selective scheduling
//Disabling downlink frequency selective scheduling
3.1.39.3 Performance Prediction

Downlink (smart) frequency selective scheduling and related functions are recommended
for a cell when the cell meets the following conditions:
● The cell is a low-speed hotspot cell (within 10 km/h).
● The value of Downlink Resource Block Utilizing Rate is greater than 30%.
● The value of L.Traffic.ActiveUser.DL.Avg is greater than 2.
● The average number of PDCCH symbols is greater than 2 (calculated using the
L.ChMeas.PDCCH.SymNum.X counter).
Downlink frequency selective scheduling, smart frequency selective scheduling, and
related functions are not recommended in any of the following scenarios:
The buffered traffic volumes of multiple UEs are constantly large, for example, in a multi-
UE packet injection test, drive test, or downlink peak demonstration test.
The gains are as follows:

● Downlink (smart) frequency selective scheduling leverages the difference in
channel quality between subbands and allocates resources in the subband with
the optimum channel quality to each UE, improving MCS. As such, the value of
User Downlink Average Throughput increases and the expected gain is 1–10%.
Note:
1. After downlink (smart) frequency selective scheduling takes effect, the CPU
usage increases. The number of aperiodic CQI reporting times increases, which
may decrease the average uplink cell throughput and the uplink user-perceived
rate. For details about aperiodic CQI reporting, see Channel Management. In
addition, the number of UEs concurrently scheduled in the downlink increases,
which may increase the average number of PDCCH symbols.
2. If smart frequency selective scheduling is enabled after downlink frequency
selective scheduling has taken effect on a live network, smart frequency
selective scheduling will be additionally evaluated for UEs. Therefore, the value
of L.ChMeas.PRB.DL.FSS.Avg may decrease. In addition, there will be changes
in the values of related uplink counters such as the number of aperiodic CQI
reports for UEs for which frequency selective scheduling takes effect. For details
about aperiodic CQI reporting, see Channel Management. The average number
of PDCCH symbols may decrease, and the CPU usage may increase.

After downlink frequency selective scheduling is enabled, check the value of
L.ChMeas.PRB.DL.FSS.Avg. If the value of this counter is not 0, downlink frequency
selective scheduling has taken effect.
User Downlink Average Throughput = (L.Thrp.bits.DL –

3.1.40 CQI Filtering Based on Spectral Efficiency Optimization

Introduction
After the CQI filtering based on spectral efficiency optimization function is enabled, the
allocation proportion of spectral efficiency on the two codewords is optimized during CQI
filtering, increasing the user-perceived downlink data rate. This eliminates the
phenomenon that the two-codeword CQI reported by a UE with a rank greater than 1 may
be different from the previously reported CQIs.
MOD CELLALGOSWITCH:LOCALCELLID=0,CQIADJALGOSWITCH=CqiFltSpectralEffOptSwitch-1;
MOD CELLALGOSWITCH:LOCALCELLID=0,CQIADJALGOSWITCH=CqiFltSpectralEffOptSwitch-0;
The expected gains increase by 1% to 3% when UEs move at a low speed and the
● The downlink PRB usage is greater than 20%.

● The proportion of the average number of times rank 2 is reported is greater than
40%.
● The value of the L.Traffic.ActiveUser.DL.Avg counter is high.

You can observe counters in the following formula to determine whether the DL User
Throughput increases.

3.1.41 NPREO Constant Optimization
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. From
eRAN11.1 onwards, the NPREO constant can be configured using the
CELLDLPCPDSCHPA.NomPdschRsEpreOffset parameter.
NPREO constant optimization includes cell-level NPREO constant adjustment and UE-
level NPREO constant adjustment. After the cell-level NPREO constant adjustment
function is enabled, the eNodeB automatically searches for the optimal cell-level NPREO
configuration. Try different cell-level NPREO constant values and collect corresponding
data such as the cell traffic, user throughput, and downlink PRB usage. Use the collected
data to fit the polynomial curve of user throughput and cell traffic with different NPREO
constant values, and then estimate respective UE throughput. If the estimated UE
throughput with NPREO set to A is greater than that with NPREO set to B and the gain is
greater than CellDlPcPdschPA.CellNpreoAdjThreshold, A is considered to be better
than B. Once the optimal cell-level NPREO value is determined, the value replaces the
original GUI value of CellDlPcPdschPA.NomPdschRsEpreOffset.
NPREO constant optimization enables the eNodeB to select an optimal NPREO constant
for a UE so that the CQI and rank reported by the UE better match the actual channel
fluctuation. In this way, the eNodeB can select a more accurate rank and MCS for
scheduling, improving the downlink spectral efficiency.

Activation
//Enabling NPREO constant optimization

MOD CELLDLPCPDSCHPA: LocalCellId=0, CellNpreoAdjThreshold=5; //If this parameter is set
to a value other than 255, the cell-level NPREO constant adjustment function is enabled.
MOD CELLDLPCPDSCHPA: LocalCellId=0, UeNpreoAdjThreshold=1;//If this parameter is set to
a value other than 127, the cell-level NPREO constant adjustment function is enabled.
MOD GLOBALPROCSWITCH: X2SonLinkSetupType=X2_OVER_S1,
ItfTypeForNonIdealModeServ=X2;//Configure the X2 interface to support inter-cell
information transmission over the X2 interface.
MOD CELLDLSCHALGO: LocalCellId=0, IntrfFilterCoeff=50;//Configure the filter coefficient
for neighboring cell interference coefficient calculation
MOD NCELLDLRSRPMEASPARA: LocalCellId=0,NCellDlRsrpMeasA3Offset=-20;//Configuring the
downlink A3 offset for RSRP-related neighboring cell measurement
Deactivation
//Disabling NPREO constant optimization

MOD CELLDLPCPDSCHPA: LocalCellId=0, CellNpreoAdjThreshold=255; // Disabling cell-level
NPREO constant adjustment
MOD CELLDLPCPDSCHPA: LocalCellId=0, UeNpreoAdjThreshold=127;// Disabling UE-level
NPREO constant adjustment

NPREO constant optimization and related sub-functions are recommended when the
● The inter-site distance is less than 700 m in 4T dense urban areas.
● The Downlink Resource Block Utilizing Rate is greater than 20%.
The gains are as follows:
● NPREO constant optimization increases User Downlink Average Throughput by
1–5%.
Note:
After the downlink NPREO constant optimization function is enabled, different NPREO
constant values are attempted during cell-level NPREO constant adjustment. User
experience is expected to be affected for about one week, and the downlink UE
throughput may decrease by a maximum of 5%. NPREO constant optimization directly
changes the CQI and rank reporting of UEs. Therefore, this function changes items such
as the rank proportion, average CQI, average MCS index, CQI distribution, and MCS
distribution. In addition, the IBLER and RBLER may change slightly. During the
adjustment, the optimal NPREO is reconfigured for UEs. Therefore, after this function is
enabled, the number of RRC connection reconfiguration signaling increases.

With the downlink NPREO constant optimization enabled, 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. After NPREO constant optimization is enabled, it
will adjust the NPREO constants of UEs. Check the value of nomPDSCH-RE-EPRE-
Offset in the RRCConnectionReconfiguration->RadioResourceConfigDedicated-
>PhysicalConfigDedicated->CQI-ReportConfig IE. If the value is not equal to that
configured on the GUI, the function has taken effect. In addition, after NPREO constant
optimization is enabled, you can check cell indicators such as the rank proportion. If the
proportion of rank 2 changes by over 10%, the function has taken effect.
3.1.42 Data Learning-based Downlink Smart AMC
Downlink AMC enables the eNodeB to select an appropriate downlink MCS based on the
channel quality. The selected MCS determines the downlink spectral efficiency. The
traditional AMC algorithm sets a certain target IBLER value and adjusts the reported CQI
based on the ACK/NACK feedback. In this way, the final IBLER converges to the target
value. Parameters such as the target IBLER and adjustment step are fixed and cannot be
adaptively adjusted to the optimal values as the environment changes. Therefore, data
learning-based downlink smart AMC is introduced to adaptively select the downlink MCS
with the optimal downlink spectral efficiency by learning historical downlink scheduling
data.
With data learning-based downlink smart AMC a large amount of cell user data is
collected, including the downlink MCS, ACK/NACK feedback, air interface channel
quality, and channel fluctuation information. The collected data is trained using a neural
network and the resultant trained model can guide the selection of the optimal downlink
MCS in real time, improving the transmission spectral efficiency of UEs. This increases
the downlink user-perceived data rate.

Activation:
MOD CellIntelAmcConfig: LocalCellId=0, IntelligentAmcSwitch =
DL_INTEL_AMC_SELECTION_SW-1;
MOD ENODEBRESMODEALGO: ServiceMode=AI_ENHANCEMENT_SWITCH-1;
Deactivation:
MOD CellIntelAmcConfig: LocalCellId=0, IntelligentAmcSwitch =
DL_INTEL_AMC_SELECTION_SW-0;
MOD ENODEBRESMODEALGO: ServiceMode=AI_ENHANCEMENT_SWITCH-0;

Downlink intelligent AMC increases User Downlink Average Throughput by 0–10%. In
downlink MBB scenarios, stronger interference and higher proportion of UEs at the cell
edge or at a medium distance from the cell center indicate larger gains.

Check whether DL User Throughput increases:

Check whether the downlink spectral efficiency of UEs increases:
L.Thrp.bits.DL/(L.ChMeas.PRB.DL.Used.Avg x 3600 x 1000)
3.1.43 Two-dimensional Frequency Selective Scheduling
Two-dimensional frequency selective scheduling is an optimization based on smart
frequency selective scheduling. During downlink RB resource allocation, the eNodeB
reorders RBGs based on the scheduling priorities of subbands and schedules RBGs in
descending order of scheduling priorities. In addition, the eNodeB supports
retransmission avoidance for frequency selective scheduling, fully utilizing frequency
selective gains of channels.

Activation:
MOD CELLALGOEXTSWITCH:LOCALCELLID=0,DLSCHENHSWITCH=2D_FSS_SWITCH-1;
Deactivation:
MOD CELLALGOEXTSWITCH:LOCALCELLID=0,DLSCHENHSWITCH=2D_FSS_SWITCH-0;
In scenarios where the downlink PRB usage is greater than 30%, the average number of
downlink activated UEs is greater than 2, and the cell is a low-speed cell, two-
dimensional frequency selective scheduling is expected to increase User Downlink
Average Throughput by 0–5%.


3.1.44 4T Remaining Power Increase
In 4T4P scenarios, some Type B symbols do not transmit pilot signals. Therefore, the
power of these symbols is not fully utilized. The power of these symbols can be increased
to maximize power utilization and improve network performance in 4T4P scenarios.
After mutual power aid between VAM ports is used to equalize the power of Type B1 and
Type B2 symbols on ports 0/1 and ports 2/3, the PB parameter is set to the maximum
value to increase the remaining power of all UEs.
Value scenario: If the baseline PA/PB is set to 0/0, the pilot power can be increased by 3
dB and the data power remains unchanged after mutual power aid is performed between
VAM ports and PA/PB is set to –3/0. If the baseline PA/PB value is set to –3/1, data
power can be increased after mutual power aid is performed between VAM ports and the
PA/PB is set to –3/0.

Activation:
//In scenarios where the remaining power is used to increase the data power with the
baseline PA/PB being –3/1
MOD CELLDLPCPDSCH: LOCALCELLID=0, RemainingPwrUseStrategy=PORT_PWR_BALANCING;
MOD PDSCHCFG:LOCALCELLID=0, Pb=0;
//In scenarios where the remaining power is used to improve coverage, wth the baseline
PA/PB being 0/0, and the value of ReferenceSignalPwr being 152.
MOD CELLDLPCPDSCH: LOCALCELLID=0, RemainingPwrUseStrategy=PORT_PWR_BALANCING;
MOD CELLDLPCPDSCHPA:LOCALCELLID=0, PaPcOff=DB_3_P_A;
MOD PDSCHCFG :LOCALCELLID=0, ReferenceSignalPwr=182;
Deactivation:
//In scenarios where the remaining power is used to increase the data power with the
baseline PA/PB being –3/1
MOD PDSCHCFG:LOCALCELLID=0, Pb=1;
MOD CELLDLPCPDSCH: LOCALCELLID=0, RemainingPwrUseStrategy=OFF;
//In scenarios where the remaining power is used to improve coverage, wth the baseline
PA/PB being 0/0, and the value of ReferenceSignalPwr being 152.
MOD PDSCHCFG :LOCALCELLID=0, ReferenceSignalPwr=152;
MOD CELLDLPCPDSCHPA:LOCALCELLID=0, PaPcOff=DB0_P_A;
MOD CELLDLPCPDSCH: LOCALCELLID=0, RemainingPwrUseStrategy=OFF;

In scenarios where the remaining power increases data power and the downlink PRB
usage is greater than 20%, the remaining power of 4T cells is expected to increase User
Downlink Average Throughput by 0–4%.
In scenarios where the remaining power is used to improve coverage, the remaining
power of 4T cells can improve downlink coverage by 3 dB and more cell edge users can
access the network. This may increase the cell traffic volume, decrease the average
downlink UE throughput, causing a slight fluctuation in the RRC connection setup
success rate, RRC connection reestablishment success rate, E-RAB setup success rate,
RB usage, and service drop rate.


3.2 Benchmark Applications

The features and optimization points involved in the solution are described in the
commercial network application solution, and therefore related details are not provided in
this section.
3.3 Heavy Traffic Applications

3.3.1 Optimization of the Initial Value of Closed-Loop
Adjustment to PDCCH Aggregation Level
Introduction
The initial CCE aggregation level of the PDCCH is low. The CCE aggregation level in the
heavy traffic scenario on the live network of M1 is 8. This is because the initial
aggregation level is low in addition to other reasons such as uplink and downlink
interference.
The initial value of closed-loop adjustment is set to –10. If 20 consecutive packets do not
receive DTX, the value is increased by 5 until it is adjusted to 0. If 20 consecutive packets
do not receive DTX, the initial value is no longer adjusted subsequently. The purpose of
this design is to ensure the access success rate in some extreme scenarios, especially
when only uplink services are available. The minimum aggregation level needs to start
from 2, resisting interference in extreme scenarios. However, system capacity will be
affected if the CCE aggregation level is excessively low and the number of scheduling
times is small.
In eRAN6.0, the initial value of closed-loop adjustment is used in SRB signaling, TA

adjustment command, and PDCCH Order. If the initial DRB value is 0, the initial value of
closed-loop adjustment is not adjusted. In the initial value adjustment algorithm, "Initial
value adjustment is stopped if DTX occurs once for every 20 scheduling times" is
changed to "Initial value adjustment is stopped if DTX occurs for three consecutive
times".
MOD CELLPDCCHALGO: LocalCellId=0, PdcchCapacityImproveSwitch =ON;

The number of CCEs used by the PDCCH decreases: L.ChMeas.CCE.CommUsed +
L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed
Expected gains: Modifying the initial value of closed-loop PDCCH adjustment applies to
the scenario where the DRB has taken effect, lowering the PDCCH DRB aggregation
level and increasing the number of scheduled UEs.
Greater gains can be obtained when PDCCH CCE usage is 60% to 80%.
3.3.2 CQI Adjustment Step Modification

Introduction
When the scheduling probability is high, the current CQI adjustment algorithm is TTI and
small step adjustment is performed based on ACK/NACK. This helps the IBLER better
coverage to a target value. If the step is enlarged, MCS fluctuation increases and the
throughput may decrease. When packet injection is insufficient or in the sparse packet
scenarios such as VoIP, ping, and heavy traffic, CQI adjustment cannot be detected in
time. As a result, the MCS for scheduling cannot trace channel changes in time and
IBLER convergence performance is poor.
Therefore, the step adjustment scheme is introduced. The step is adjusted according to
the target IBLER value offset in the low scheduling probability scenario. When the offset
is large, the large step size is used. When the offset is small, the small step size is used.
This scheme can improve IBLER convergence for services with sparse packets to
improve downlink performance.
MOD CELLALGOSWITCH:LocalCellId=0,CqiAdjAlgoSwitch=StepVarySwitch-1;
Observe throughput improvement and IBLER convergence.
The throughput is calculated by using the following formula: Throughput =

L.Thrp.bits.DL/L.Thrp.Time.DL.
IBLER is calculated by using the following formula:
3.3.3 Downlink Packet Bundling

Introduction
Data obtained from typical networks indicates that the data packet delay of a small
number of UEs is excessively large. Certain throughput is available for such UEs,
however, user experience may not be good. In this case, there are always remaining air
interface resources. In addition, a large amount of control channel resources need to be
consumed during dynamic scheduling for VoIP services. When control channel resources
become a bottleneck, VoIP capacity is limited greatly.
For downlink packet bundling, multiple data packets are packed to consume less control
channel resources and use more data channel resources, thereby increasing capacity
and improving user experience. In eRAN6.0, according to the PDBs of different QCIs,
downlink packet bundling based on delay is implemented. The purpose is to ensure that
all service delays are similar so that service experience is similar. In addition, multiple
small packets are bundled to form a large packet. By doing this, the data channel
capacity can be increased when the control channel capacity does not change.
Therefore, packet bundling applies to the scenario where the scheduling capacity in each
TTI is limited or the PDCCH is limited whereas PDSCH resources are not fully utilized.
The scenarios include:
VoIP scenario: When the number of VoIP services connected to a cell is increasing, the
user satisfaction rate is decreasing starting from a user number until dissatisfaction
appears (the satisfaction rate is lower than the threshold). If packet bundling is available,
the delay of some packets may increase and the mean opinion score (MOS) decreases.
However, the number of satisfied users increases greatly.
Scenario where VoIP and common data services are mixed: Improve the throughput of
common data services.
Decrease the delay of common data services. The delay of some data packets with large
delay noticeably decreases. The delay of some data packets with small delay increases
but the satisfaction remains within the PDB, which means the packet delay distribution is
more balanced. In addition, the resource usage and cell throughput may increase.
MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=NonGbrBundlingSwitch-1;
Target scenarios:
The methods are used when PDCCHs are insufficient while PDSCHs are sufficient:
1. Whether the PDCCH is insufficient
Number of PDCCH CCEs used by common signaling messages:
L.ChMeas.CCE.CommUsed
Number of PDCCH CCEs used by uplink scheduling: L.ChMeas.CCE.ULUsed
Number of PDCCH CCEs used by downlink scheduling:
L.ChMeas.CCE.DLUsed
Total duration of downlink data transmission in a cell (s): L.Thrp.Time.Cell.DL
The PDCCH is insufficient when PDCCH CCE usage is greater than 80%.
PDCCH CCE usage = (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed
+ L.ChMeas.CCE.DLUsed)/(L.Thrp.Time.Cell.DL x 1000 x Number of CCEs
corresponding to the maximum CFI).
In the preceding description, 80% is a reference value. If the UE is nearer to the
eNodeB (SINR = About 25 dB), the value needs to be larger. If the UE is farther
from the eNodeB (SINR = About 0 dB), the value can be smaller.
Table 3.3.3.1.1.1.1.1.1 Number of CCEs corresponding to the largest CFI for each
bandwidth
Bandwidth 3M 5M 10 M 15 M 20 M
CFI = CCE 12 20 41 62 84
corresponding to 3
2. Whether the PDSCH is insufficient

Average number of PRBs used by the PDSCH in the downlink in a cell:
L.ChMeas.PRB.DL.Used.Avg
If RB usage is greater than 80%, the PDSCH is insufficient.
RB usage = L.ChMeas.PRB.DL.Used.Avg/Number of RBs in the system
bandwidth x 1000
3. Data packet delay
The RLC cache waiting time for data packets can be obtained through IFTS
trace data. Service delay is large if the delay for at least 10% of data packets
exceeds PDB/2 of the current QCI. Benefits can be gained by enabling the
packet bundling function if RB usage is small.
Table 3.3.3.1.1.1.3.1.1 PDB corresponding to each QCI

QCI QCI1/5/7 QCI2 QCI3 QCI4/6/8/9
PDB 100 ms 150 ms 50 ms 300 ms
Result data
4. Increased downlink throughput
Total traffic volume of downlink PDCP SDUs in a cell (by QCI): L.Thrp.bits.DL
Duration of downlink PDCP SDUs in a cell (by QCI): L.Thrp.Time.DL
Average downlink throughput: (by QCI, approximate value): Average Dl Thp =
5. Increased downlink PRB usage
RB usage = L.ChMeas.PRB.DL.Used.Avg/Number of RBs in the system
bandwidth x 1000
6. Decreased variance of the average downlink packet delay
Total processing delay of downlink data packets of DRB services in a cell (by
QCI): L.Traffic.DL.PktDelay.Time.QCI.9 (such as QCI9)
Number of successfully transmitted downlink PDCP SDUs of DRB services in a
cell (by QCI): L.Traffic.DL.PktDelay.Num.QCI.9 (such as QCI9)
Average downlink packet delay (by QCI): Average Packet Delay =
L.Traffic.DL.PktDelay.Time.QCI.9/L.Traffic.DL.PktDelay.Num.QCI.9
3.3.4 PDCCH and PDSCH Resource Allocation Optimization

Mechanism
Introduction
When the number of RRC_CONNECTED UEs serving by a cell is large, the proportion of
UEs performing small packet services is large, and PDCCH resources are insufficient, the
number of scheduled UEs in the downlink in each TTI is restricted and downlink PDSCH
resource usage decreases.
In this scenario, you are advised to use the PDCCH and PDSCH resource balancing
function. A scheduler randomly selects a UE performing large packet services and
reserves PDCCH resources for the UE. When the last UE is scheduled in the downlink,
PDSCH resources are allocated to the selected UE, thereby improving downlink RB
usage and throughput.
MOD
CELLDLSCHALGO:LOCALCELLID=0,RBPRIMCSSELECTSTRATEGY=SINGLEUSER_STRATEGY,RBPRIMC
SSELECTRATIOTHD=10;
MOD
CELLDLSCHALGO:LOCALCELLID=0,DATATHDINPDCCHPDSCHBAL=18000,UENUMTHDINPDCCHPDSCHB
AL=300;

Increase downlink PRB usage (L.ChMeas.PRB.DL.Used.Avg) and air interface
throughput (L.Thrp.bits.DL). However, the transmission duration for small packet
scheduling increases because the priority of large packet scheduling is increased and
that of small packet scheduling is decreased. As a result, the user-perceived rate in the
downlink decreases in some scenarios. Therefore, you are advised to use this method
only when the customer pays special attention to downlink PRB usage.
3.3.5 RLC Parameter Adaptation Configurations
Introduction
Analysis of data on the live network of M1 in Singapore in the heavy traffic scenario
shows that the timeout of the RLC polling retransmission timer and the timer for
prohibiting status reporting from the receiver causes a large amount of RLC
retransmission and status reports. As a result, resources are wasted and throughput is
affected. The polling retransmission timer and the timer for prohibiting status reporting
from the receiver are two parameters at the RLC layer in the protocol. The lengths of the
two timers can be calculated by using the following formula:
Length of the polling retransmission timer = Radio transmission delay of the polling PDU
+ Status report scheduling delay at the peer end + Status report radio transmission delay.
Length of the timer for prohibiting status reporting from the receiver = Status report radio
transmission delay + Retransmitted data scheduling delay at the peer end + Radio
transmission delay of retransmitted data.
In the preceding formulas, the radio transmission time can be considered as the fixed
time. In this case, the lengths of the two timers are closely related to the status report
scheduling delay or retransmitted data delay.
On the network, scheduling delay is related to the number of UEs. If there are a large
number of UEs (in the heavy traffic scenario), the interval between scheduling chances of
each UE becomes larger. As a result, the status report or retransmitted data delay also
becomes larger. If the length of the polling retransmission timer is smaller than the
scheduling interval at the peer end, the timer times out and unnecessary retransmission
is triggered when the status report at the peer end has not obtained the scheduling
chance. The increase in retransmission times causes the increase in the probability of
reaching the maximum number of RLC retransmissions, which causes call drop. If the
length of the timer for prohibiting status reporting from the receiver is smaller than the
scheduling interval at the peer end, the timer times out and status reports are sent to the
peer end again when the retransmitted data at the peer end has not obtained the
scheduling chance. As a result, resources are wasted or retransmitted data may be sent
from the peer end for the second time.
Therefore, it is more appropriate if the lengths of the two timers are set according to the
number of UEs on the network. However, the timer settings are fixed currently, failing to
meet actual network environment requirements.
To solve the preceding problem, RLC parameter adaptation configurations are required.
Parameters values are selected according to the number of UEs on the network.
MOD RLCPDCPPARAGROUP: RlcParaAdaptSwitch=1;

If there are a large number of UEs with heavy traffic, increasing the length of the timer
can reduce the number of invalid retransmission times caused by the timeout of the
polling retransmission timer, reducing RLC retransmission rates and improving downlink
perceived throughput.
3.3.6 Optimization of Aperiodic CQI Reporting Triggering
Introduction
In heavy traffic tests in the lab, the proportion of the uplink CQI_ONLY scheduling
reaches 59%. This is caused by UE access failures. The eNodeB does not receive MSG5
for a long time and UE instances are not released. CQI_ONLY scheduling is triggered
frequently due to the following reasons: Valid periodic CQIs are not received in the
downlink within the CQI period multiplied by 8 and one aperiodic CQI reporting is
triggered, and CQI_ONLY scheduling is used for aperiodic CQIs when there is no uplink
data. In addition, aperiodic CQI reporting is triggered again 8 TTIs after CRC check fails.
In addition, at some sites (for example, the ones in Canada and Australia), after DRX is
enabled, the CQI_ONLY scheduling proportion remains high. This is because UEs do not
report periodic CQIs during the sleep period after DRX is enabled and aperiodic CQI
reporting may be easily triggered because no valid periodic CQI is reported. False SR
detection causes extension in the DRX activation period. As a result, CQI_ONLY
scheduling is triggered.
To solve the preceding problem, take the following optimization measures:
1. Add restrictions on aperiodic CQI triggering during initial access: "Aperiodic CQI
reporting is triggered 200 ms after DLMAC instances are established" is
changed to "Aperiodic CQI reporting is triggered 200 ms after DLMAC instances
are established and MSG5 is received." Layer 2 identifies MSG5 using
DMAC_ACT_IND sent from layer 3.
2. If CRC check fails after aperiodic CQI reporting is triggered in the downlink,
aperiodic CQI reporting is not triggered after 8 TTIs but until aperiodic CQI
reporting triggering conditions are met.
MOD CELLALGOSWITCH: LocalCellId=0, DlSchSwitch=AperiodicCqiTrigOptSwitch-1;

Calculate the proportion of the number of times that the MCS is 29:
L.ChMeas.PUSCH.MCS.29/ (L.ChMeas.PUSCH.MCS.0 + L.ChMeas.PUSCH.MCS.1 +...
+ L.ChMeas.PUSCH.MCS.31) and the decrease in the number of aperiodic CQI reporting
samples (L.ChMeas.CQI.DL.SingleCW.Aperiodic.0 –
L.ChMeas.CQI.DL.SingleCW.Aperiodic.15,
L.ChMeas.CQI.DL.DualCW.Code0.Aperiodic.0 –
L.ChMeas.CQI.DL.DualCW.Code0.Aperiodic.15,
L.ChMeas.CQI.DL.DualCW.Code1.Aperiodic.0 –
L.ChMeas.CQI.DL.DualCW.Code1.Aperiodic.15) to observe the optimization effect.
3.3.7 Stopping Scheduling of Abnormal UEs

Introduction
Many exceptions occur on commercial networks, such as abnormal release scenarios
(plugging out SIM cards and power outage of UEs). In this scenario, a large number of
DTXs are generated and the CCE level of all PDCCHs is 8, resulting in a waste of
scheduling resources.
In eRAN6.0, when there are 15 consecutive DTXs in the PUCCH HARQ feedback, the
eNodeB stops downlink DRB scheduling (initial transmission+retransmission) to reduce
unnecessary scheduling resource usage.
MOD CELLALGOSWITCH: LocalCellId=0, CellSchStrategySwitch=AbnUeSchSwitch-1;

You can observe the effect based on the UL/DL RBLER value. After the scheme takes
effect, RBLER decreases.
DL 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.HOCmd.ErrTB.Rbler –
L.Traffic.DL.SCH.RRCRel.ErrTB.Rbler)/(L.Traffic.DL.SCH.QPSK.TB +
L.Traffic.DL.SCH.16QAM.TB + L.Traffic.DL.SCH.64QAM.TB –
L.Traffic.DL.SCH.HOCmd.TB – L.Traffic.DL.SCH.RRCRel.TB)
UL RBLER =
(L.Traffic.UL.SCH.QPSK.ErrTB.Rbler + L.Traffic.UL.SCH.16QAM.ErrTB.Rbler +
L.Traffic.UL.SCH.64QAM.ErrTB.Rbler)/(L.Traffic.UL.SCH.QPSK.TB +
L.Traffic.UL.SCH.16QAM.TB + L.Traffic.UL.SCH.64QAM.TB)
3.3.8 Restrictions on Special Signaling Retransmission in

Heavy Traffic Scenarios
Introduction
When the number of UEs exceeds the overload threshold, the maximum number of RLC
retransmission times in the inter-RAT handover command and RRC Release message is
2. When the number of UEs drops below the overload threshold, the eNodeB restores
normal signaling processing.
MOD ENODEBALGOSWITCH: HighLoadNetOptSwitch=SPECSIGRETRANSOPTSWITCH-1;

You can observe the effect based on the RBLER value in the handover command and
RRC Release message.
After the scheme takes effect, the values of the two indicators decrease.
RBLER (handover command) =

L.Traffic.DL.SCH.HOCmd.ErrTB.Rbler/L.Traffic.DL.SCH.HOCmd.TB
RBLER (RRC Release command) =

L.Traffic.DL.SCH.RRCRel.ErrTB.Rbler/L.Traffic.DL.SCH.RRCRel.TB
3.3.9 PUCCH Outer Loop Power Control
Introduction
PUCCH outer loop power control is adjusted by setting
CellAlgoSwitch.UlPcAlgoSwitch.
When OuterLoopPucchSwitch (PUCCH outer loop power control switch) is set to ON,
the eNodeB dynamically adjusts SINRTarget of PUCCH format 1a/1b based on the
difference between the BER and BERTarget of PUCCH format 2/2a/2b so that PUCCH
power control changes with the channel status, thereby improving PUCCH demodulation
performance, reducing the false detection rate of format 2/2a/2b, and increasing downlink
throughput.
● If the BER is greater than BERTarget, the value of SINRTarget increases.

● If the BER is equal to BERTarget, the value of SINRTarget remains unchanged.
● If the BER is less than BERTarget, the value of SINRTarget decreases.
After the option of the CellAlgoSwitch.UlPcAlgoSwitch parameter is set to ON, the
PUCCH is no longer restricted by the high RSRP threshold and downlink throughput can
be improved in strong interference scenarios.
When OuterLoopPucchSwitch (PUCCH outer loop power control switch) is set to OFF,
the fixed SINRTarget is used for PUCCH inner loop power control.
MOD CELLALGOSWITCH: UlPcAlgoSwitch = OuterLoopPucchSwitch-1;

After this feature is enabled, you can monitor the following counters:
Total downlink throughput (L.Thrp.bits.DL) of a cell increases.
RSRP received by the PUCCH of a cell increases: L.UL.RSRP.PUCCH.Index0 –

L.UL.RSRP.PUCCH.Index23.
PUCCH interference of the cell may increase: L.UL.Interference.PUCCH.Index0 –

L.UL.Interference.PUCCH.Index15.
3.3.10 Service Model-based Performance Optimization in the

Downlink
Introduction
Principles: Based on comprehensive considerations for buffer data volume to be
transmitted and factors such as actual data transmission rate over the air interface of the
UE, increase the scheduling priority of UEs with a short transmission time (assume that
we define the transmission time of subscriber A as T1 and that of subscriber B as T2; if
T1 is smaller than T2, then subscriber A is the one with a shorter transmission time),
thereby improving average user-perceived rate and user experience during busy hours.
On:
MOD CELLALGOSWITCH:LOCALCELLID=0,DLSCHSWITCH=DlPacketLenAwareSchS-1;
Off:
MOD CELLALGOSWITCH:LOCALCELLID=0,DLSCHSWITCH=DlPacketLenAwareSchSw-0;

After this feature is enabled, observe the increase of the value of the following formula to
determine the optimization effect.
3.3.11 PUCCH Resource Allocation Optimization

Introduction
By optimizing the PUCCH resource allocation policy, the eNodeB preferentially uses
different RB resources when allocating new PUCCHs. This method enables user data to
be multiplexed on all RBs, therefore decreasing the inter-channel interference on cell
users and enhancing the PUCCH demodulation performance. PUCCH resource
allocation optimization is controlled by a parameter. It takes effect only when the PUCCH
adaptive adjustment switch is turned off.
MOD PUCCHCFG:LOCALCELLID=0, PucchAllocPolicy = RBPRIORITYMODESW -1;
MOD PUCCHCFG:LOCALCELLID=0, PucchAllocPolicy = RBPRIORITYMODESW -0;

Expected gains:
● Enhances the PUCCH demodulation performance.

● Increases the downlink user throughput by 0% to 2%.
● Increases the uplink user throughput by 0% to 2%.
The following formula can be used to determine whether the uplink user throughput
increases:
increases:
3.3.12 Delayed Transmission of Status Reports
Introduction
When CCE resources are limited on the live network in big events, the eNodeB judges
downlink connections to be scheduled in each TTI at the MAC layer to save CCE
resources. If a connection to be scheduled contains only a downlink RLC ACK status
report (without downlink data to be sent) and the status report scheduling wait time is less
than the preset threshold, status report transmission is delayed in the current TTI. After
delayed transmission of status reports takes effect when CCE resources are limited on
the live network in big events, user-perceived downlink throughput can be increased.
To enable this function, run the following command:
MOD CELLALGOSWITCH:LOCALCELLID=0,DLSCHSWITCH=DlRLCStateReportSchDelaySw-1;
To disable this function, run the following command:
MOD CELLALGOSWITCH:LOCALCELLID=0,DLSCHSWITCH=DlRLCStateReportSchDelaySw-0;

This function applies to the scenario where CCE resources are limited on the live network
in big events. In this scenario, the downlink PRB usage exceeds 80%, the number of
RRC_CONNECTED UEs in a cell exceeds 200, the CCE usage exceeds 70%, and the
proportion of downlink RLC status reports exceeds 15%.
In the preceding scenario, this function increases user-perceived downlink throughput by

1% to 5%.
You can observe the counters in the following formula to determine whether user-
3.3.13 Enhancement of Adaptive Downlink HARQ

Retransmission
Introduction
To effectively use combining gains of hybrid automatic repeat request (HARQ), the
transport block size (TBS) index used for the initial HARQ retransmission is increased by
a fixed value to reduce the number of used resource blocks (RBs). If enhancement of
adaptive downlink HARQ retransmission takes effect, the user-perceived downlink rate
increases in heavy-traffic scenarios.
To enable enhancement of adaptive downlink HARQ retransmission:

MOD CELLDLSCHALGO:LOCALCELLID=0, DlFirstHarqTxTbsIncNum =3;
To disable enhancement of adaptive downlink HARQ retransmission:

The user-perceived downlink rate increases by 1% to 5% in heavy-traffic scenarios where
the downlink PRB usage is greater than 50% and the downlink IBLER is between 9% and
30%, the proportion of UEs at the cell center is lower than or equal to 25%. The downlink
RBLER is expected to possibly increase.


You can observe the counters in the following formula to determine whether the number
of downlink RB retransmissions reduces:

L.ChMeas.PRB.DL.RANK2.MCS.29 + ... + L.ChMeas.PRB.DL.RANK2.MCS.31)/
L.ChMeas.PRB.DL.RANK2.MCS.0 + ... + L.ChMeas.PRB.DL.RANK2.MCS.31)
4 Expected Gains of Function
Combinations
Related features:
FDD:
1) AMC optimization in burst
Downlink throughput and SINR curve at the cell edge
DT interference scenarios
or at a medium distance from the cell center: 5–10%
2) Increase of the shutdown
in 4T scenarios and 5% in 2T scenario
ratio
FDD: Related features:

In 4T scenarios, the downlink PRB usage is 10–30%, 1) AMC optimization under
User
and the downlink user-perceived rate increases by burst interference (FDD);
plane
10–15%. 2) Shutdown ratio increase
Light KPI
In 2T scenarios, the downlink PRB usage is 5%, and (FDD)
load the downlink user-perceived rate increases by 2–5%. 3) 1-2 subband CQI (FDD +
Control TDD)
plane No impact 4) CSI reporting optimization
KPI (FDD)
FDD:
User Related features:
Heavy The PRB usage is greater than 50%, the CFI is
plane 1) CFI adaptation optimization
load greater than 2, and the downlink UE throughput
KPI (FDD)
increases by 5%.
5 Cases
The following web page lists the gains of some optimization measures taken in offices on
the live network:
http://support.huawei.com/support/pages/kbcenter/view/product.do?
actionFlag=detailProductSimple&web_doc_id=SC0000822317&doc_type=12
3-2&doc_type=123-2&saveBrowserLoged=true
6 Reference Documents
BTS3900 V100R010C10SPC000B551 MML Command Reference.chm
BTS3900 V100R010C10SPC000B551 MML Command Reference.chm

LTE Downlink Capacity Solution User Guide A Acronyms and Abbreviations
A Acronyms and Abbreviations
CQI Channel quality indicator
FDD Frequency Division Duplex
LTE Long Term Evolution
MBB Mobile Broad Band
PDCCH Physical Downlink Control Channel
PDSCH Physical downlink shared channel
PUCCH Physical uplink control channel
PUSCH Physical uplink shared channel

54 eRAN16.1 LTE Downlink Capacity Solution User Guide

Uploaded by

Document Information

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

54 eRAN16.1 LTE Downlink Capacity Solution User Guide

Uploaded by

Copyright:

Available Formats

Product Name Confidentiality Level

eRAN16.1 LTE Downlink Capacity Solution

Prepared By LTE Solution Design Department Date 2017-04-24

Reviewed By Date yyyy-mm-dd

Reviewed By Date yyyy-mm-dd

Approved By Date yyyy-mm-dd

Huawei Technologies Co., Ltd.

About This Document

2014-04-22 1.0 Completed the draft. Wang Xiaojian

2014-05-06 1.1 Revised the document Wang Xiaojian

2014-07-23 1.2 Updated contents for Lu Jun

2015-01-08 1.3 Revised the document Lu Jun

2015-06-15 1.4 Added contents for Shi Juncai

2016-5-19 1.5 Added contents for Lin Jie

2017-10-11 1.6 Added sections Wang Yi

2018-12-25 1.7 Added sections Zhuang Qianqian

Issue 01 (2021-06-21) Huawei Proprietary and Confidential i

Date Issue CR/Defect ID Section Change Description Author

2019-11-08 1.8 Added sections Lu Jun

Issue 01 (2021-06-21) Huawei Proprietary and Confidential ii

3 Solution Application Guide............................................................................................10

3.1.10 Optimization of Downlink EPF Scheduling Priority Calculations..........................................................20

3.1.42.2 Parameter Configurations................................................................................................................. 52

4 Expected Gains of Function Combinations.................................................................66

2 Describes the solution overview.

3 Describes the solution application guide. Provides detailed schemes,

4 Describes application cases of the solution on commercial networks.

1.3.1 Relationship with Other Documents

1.3.2 Life Cycle

This document was updated and finalized at TR6.

1.4 Open Issues

2.1 Scenario Analysis

Figure 2.1.1.1.1.1.1.1 Penetration rate of each type of service in each area

Figure 2.1.1.1.1.1.1.2 Single session packet sizes for typical services

Uplink traffic packet sizes Downlink traffic packet sizes

Figure 2.1.1.1.1.1.1.3 Service proportion

Figure 2.1.1.1.1.1.1.4 Inter-packet gap

RUL:RDL 1.33% 3.47% 2% 5.2%

2.1.2 Benchmark Scenarios

2.1.3 Heavy Traffic Scenarios

Figure 2.3.1.1.1.1.1.1 Downlink solution panorama

PDSCH resource usage

Data resource usage

MIMO Antenna Transmission mode

GBR service assurance

QoS Non-GBR service assurance

Hybrid service assurance

2.3.2 Commercial Network Application Solution

Table 2.3.2.1.1.1.1.1.1 Commercial network application solution

Optimization ● Enhanced ● Optimization of ● Enhancement ● Enhanced ● Extra power

point adaptive CFT aggregation of target PDCCH boost

2.3.3 Benchmark Solution

Table 2.3.3.1.1.1.1.1.1 Benchmark solution

Optimization ● Enhancement of ● Optimization of Enhancement of ● Extra power boost

Table 2.3.4.1.1.1.1.1.1 Heavy traffic solution

Optimization ● PUSCH DTX detection ● RBG adaptation ● Enhanced ● Buffer Aware

3.1 Commercial Network Applications

Effect Evaluation Methods

Figure 3.1.2.1.1.1.1.1 Downlink frequency selective resource allocation

To calculate scheduling priorities and select resources, downlink frequency selective

CellAlgoSwitch.DlSchSwitch, CellPdcchAlgo.PdcchSymNumSwitch, and

DL Frequency PDCCH Symbol PDCCH Initial Is DL Frequency

ON ON Greater than or Yes

The PDCCH Symbol Any adaptive Yes