Automatic Congestion Handling Feature Parameter Description: Issue Date

eRAN
Automatic Congestion Handling

Feature Parameter Description
Issue Draft A
Date 2020-12-29
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: [email protected]
Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

(2020-12-29)
eRAN
Automatic Congestion Handling Feature Parameter
Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN17.1 Draft A (2020-12-29)........................................................................................................................................ 1
2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Applicable RAT......................................................................................................................................................................... 3
2.3 Features in This Document.................................................................................................................................................. 3
3 Overview....................................................................................................................................5
4 Automatic Congestion Handling......................................................................................... 6
4.1 Principles.................................................................................................................................................................................... 6
4.1.1 Architecture............................................................................................................................................................................ 6
4.1.2 ACH Procedure...................................................................................................................................................................... 7
4.1.2.1 Data Collection.................................................................................................................................................................. 8
4.1.2.2 Trigger Condition Judgment....................................................................................................................................... 12
4.1.2.3 Intelligent Optimization Functions and Parameter Adjustment....................................................................12
4.1.2.4 Customization of Intelligent Optimization Rules................................................................................................29
4.2 Network Analysis.................................................................................................................................................................. 30
4.2.1 Benefits................................................................................................................................................................................. 30
4.2.2 Impacts.................................................................................................................................................................................. 38
4.3 Requirements......................................................................................................................................................................... 40
4.3.1 Licenses................................................................................................................................................................................. 41
4.3.2 Software................................................................................................................................................................................41
4.3.3 Hardware.............................................................................................................................................................................. 42
4.3.4 Others.................................................................................................................................................................................... 42
4.4 Operation and Maintenance............................................................................................................................................. 42
4.4.1 Data Configuration........................................................................................................................................................... 42
4.4.1.1 Data Preparation............................................................................................................................................................ 43
4.4.1.2 Using MML Commands............................................................................................................................................... 49
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 50
4.4.2 Activation Verification..................................................................................................................................................... 50
4.4.3 Network Monitoring......................................................................................................................................................... 51
5 Parameters.............................................................................................................................. 54
Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

(2020-12-29)
eRAN
Description Contents
6 Counters.................................................................................................................................. 55
7 Glossary................................................................................................................................... 56
8 Reference Documents...........................................................................................................57
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

(2020-12-29)
eRAN
Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN17.1 Draft A (2020-12-29)

This issue introduces the following changes to eRAN16.1 01 (2020-03-30).
Technical Changes
Change Parameter RAT Base Station
Description Change Model
Canceled the None FDD BTS3911E

compatibility with
the BTS3911E as
of this version.
Deleted the Deleted the FDD ● 3900 and 5900

GlobalProcSwitc GlobalProcSwitc series base
h.RrcConnPunish h.RrcConnPunish stations
Thd parameter Thd parameter. ● DBS3900
from this version LampSite and
and replaced this DBS5900
parameter with LampSite
the
GlobalProcSwitc
h.LteRrcConnPun
ishmentThld
parameter.
Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

(2020-12-29)
eRAN
Description 1 Change History
Editorial Changes
Deleted descriptions related to micro base stations. For details, see 4.1.2.1 Data
Collection.

(2020-12-29)
eRAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters

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

This document applies to FDD.
2.3 Features in This Document

This document describes the following FDD features.

(2020-12-29)
eRAN
Description 2 About This Document
Feature ID Feature Name Chapter/Section
LOFD-081205 Automatic 4 Automatic Congestion Handling

Congestion Handling

(2020-12-29)
eRAN
Description 3 Overview
3 Overview
In ACH, an eNodeB periodically checks cell congestion status. The eNodeB adjusts
parameter settings based on congestion conditions to mitigate cell congestion,
improving network performance and user experience.

(2020-12-29)
eRAN
Description 4 Automatic Congestion Handling
4 Automatic Congestion Handling
4.1 Principles
4.1.1 Architecture
If the ACHSwitch option of the ENodeBAlgoSwitch.IOptAlgoSwitch parameter is
selected, this function is enabled in both FDD and TDD cells.
If only the FDD_ACH_SWITCH option of the ParaAutoOptCfg.AchEffectiveType
parameter is selected, this function is enabled only in FDD cells.
For LampSite base stations, uplink RS power adaptation can be enabled by
selecting the UL_RS_PWR_ADAPT_SW option of the
CellAlgoExtSwitch.HeavyLoadPrfmOptSwitch parameter but does not depend
on the ACHSwitch option of the ENodeBAlgoSwitch.IOptAlgoSwitch parameter.
Intelligent optimization functions of ACH have been predefined on the eNodeB.
These functions specify when and how to adjust or restore parameter settings.
Thresholds of the trigger conditions can be customized. The eNodeB periodically
checks whether trigger conditions of every intelligent optimization function are
met. If trigger conditions of an intelligent optimization function are met, the
eNodeB adjusts or restores the corresponding parameter setting. Figure 4-1 shows
the architecture of ACH.

(2020-12-29)
eRAN
Figure 4-1 ACH architecture
4.1.2 ACH Procedure

Figure 4-2 outlines the ACH procedure.
Figure 4-2 ACH procedure
NOTE
Each intelligent optimization function shown in Figure 4-2 includes two intelligent
optimization rules: parameter setting adjustment and parameter setting restoration. For
details, see 4.1.2.3 Intelligent Optimization Functions and Parameter Adjustment.
The eNodeB determines whether to trigger intelligent optimization functions

based on the monitoring results of items listed in Table 4-1 and predefined trigger
conditions. The procedure consists of the following steps:
1. Data collection
The eNodeB collects data required for intelligent optimization functions every
5 minutes.
2. Trigger condition judgment
The eNodeB determines whether the trigger condition of either rule of an
intelligent optimization function is met based on the collected data in a
period specified by LIOptRule.Period. If no trigger condition is met, the

(2020-12-29)
eRAN
current procedure will end and a new procedure will start in the next period.
Parameter setting adjustment or restoration is triggered if the corresponding
trigger condition is met.
3. Intelligent optimization by ACH
The eNodeB delivers the parameter setting adjustment or restoration
measures predefined in the triggered intelligent optimization functions.
4. Adjustment or restoration of parameter settings
The eNodeB automatically adjusts or restores the parameter settings.
NOTE
● If a parameter value has been changed to the target value in the previous period,
the eNodeB will not change the parameter value again specified by a triggered
intelligent optimization function in the current period.
● After the parameter setting is adjusted, if operators change the setting of any
parameter in the same MO of a predefined parameter in the parameter setting
adjustment measures, the parameter values that have been adjusted will be
restored to the values before the adjustment. As a result, the adjustment measures
fail. To avoid parameter setting restoration after manual modification, ACH has a
four-hour enforcement mechanism. After ACH is enabled, the eNodeB checks
whether the trigger conditions of each intelligent optimization function are met
every four hours. If the trigger conditions are not met, the eNodeB does not take
any action. If the trigger conditions are met, the parameter setting adjustment
measures are forcibly executed again. The four-hour enforcement mechanism does
not apply to uplink RS power adaptation.
● All executions of intelligent optimization functions are recorded in SON logs, not in
operation logs.
4.1.2.1 Data Collection

The eNodeB periodically calculates the number of UEs in a cell, UE occupation
rate of a cell, physical resource block (PRB) usage, PDCCH CCE usage, UE
occupation rate of an eNodeB, and physical uplink shared channel (PUSCH) and
physical uplink control channel (PUCCH) interference, and then determines
whether to trigger adaptive parameter adjustment. The measurement period is
fixed and is 5 minutes by default. Table 4-1 describes the required measurement
items and their calculation formulas.
Table 4-1 Required measurement items and their calculation formulas

Measurement Calculation Formula
Item
User_Spec_Occupy_ L.Traffic.User.Ulsync.Avg/Maximum number of UL-sync

Rate UEs supported by a cell
Ulsync_User_Num L.Traffic.User.Ulsync.Avg

(2020-12-29)
eRAN

Item
PDCCH_CCE_Utiliza FDD: (L.ChMeas.CCE.CommUsed +

tion_Rate L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed)/
(Number of CCEs per TTI when the maximum number of
fixed PDCCH symbols is used x Number of TTIs in a
measurement period)
NOTE
● The corresponding formula applies when the
CellPdcchAlgo.PdcchSymNumSwitch parameter is set to ON
or ECFIADAPTIONON or when the
CellPdcchAlgo.PdcchSymNumSwitch parameter is set to OFF
and the CellPdcchAlgo.InitPdcchSymNum parameter is set
to the maximum allowed number of symbols. The
corresponding formula has been used since eRAN11.1.
● When the system bandwidth is 1.4 MHz, the maximum
number of symbols is 4. For other system bandwidths, the
maximum number of symbols is 3.
DL_PRB_Utilization_ L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail
Rate
UL_PRB_Utilization_ L.ChMeas.PRB.UL.Used.Avg/L.ChMeas.PRB.UL.Avail
Rate
ENB_USER_SPEC_E Max{User_Spec_Occupy_Rate (Cell0),

QU_OCCUPY_Rate User_Spec_Occupy_Rate (Cell1), ...,
User_Spec_Occupy_Rate (Baseband Board1),
User_Spec_Occupy_Rate (Baseband Board2), ...}
NOTE
● User_Spec_Occupy_Rate (Cell) indicates the proportion of
UL-sync UEs in a cell in the maximum allowed number of UEs
in the cell. The number of UL-sync UEs in a cell is indicated by
L.Traffic.User.Ulsync.Avg.
● User_Spec_Occupy_Rate (Baseband Board) indicates the
proportion of total UL-sync UEs in all cells served by a
baseband processing unit (BBP) in the maximum number of
UEs supported by the BBP. The number of UL-sync UEs in a
cell is indicated by L.Traffic.User.Ulsync.Avg.
PUSCH IN L.UL.Interference.Avg

(2020-12-29)
eRAN

Item
PUCCH IN (L.UL.Interference.PUCCH.Index0 x Intf(0) +

L.UL.Interference.PUCCH.Index1 x Intf(1) + ... +
L.UL.Interference.PUCCH.Index15 x Intf(15))/
(L.UL.Interference.PUCCH.Index0 +
L.UL.Interference.PUCCH.Index1 + ... +
L.UL.Interference.PUCCH.Index15)
NOTE
This formula is a simplified engineering calculation formula used
for this feature. If it is used for theoretical calculations in other
scenarios, convert the units of the quantities in the numerator to
milliwatt.
● Intf (0) = –121.5
● Intf (1) = –120.5
● Intf (2) = –119.5
● Intf (3) = –118.5
● Intf (4) = –117.5
● Intf (5) = –116.5
● Intf (6) = –115.5
● Intf (7) = –114.5
● Intf (8) = –113.5
● Intf (9) = –112.5
● Intf (10) = –110
● Intf (11) = –106
● Intf (12) = –102
● Intf (13) = –98
● Intf (14) = –94
● Intf (15) = –90
EQV_BW_SF_ULSYN Number of UL-sync UEs x 20/(Uplink bandwidth

C_USER_NUM coefficient x Uplink-downlink subframe configuration
coefficient x Cell capacity scale factor)
● For details about uplink bandwidth coefficient, see
Table 4-2.
● For details about uplink-downlink subframe
configuration coefficient, see Table 4-3.
● The cell capacity scale factor is specified by the
CellMLB.CellCapacityScaleFactor parameter.
RL_EQV_BW_SF_UL Number of UL-sync UEs with equivalent bandwidths and

SYNC_USER_NUM uplink-downlink subframe configurations/(Number of UL-
sync UEs with equivalent bandwidths and uplink-downlink
subframe configurations in a base station x Number of
valid cells in the base station x 100)

(2020-12-29)
eRAN
Table 4-2 Mapping between the bandwidth and the uplink bandwidth coefficient
Cell.UlBandWidth Uplink Bandwidth Coefficient
CELL_BW_N6 1.4
CELL_BW_N15 3
CELL_BW_N25 5
CELL_BW_N50 10
CELL_BW_N75 15
CELL_BW_N100 20
Table 4-3 Mapping between the RAT and the uplink-downlink subframe
configuration coefficient
Cell.FddTddInd Cell.SubframeAssignme Uplink-downlink
nt Subframe
Configuration
Coefficient
CELL_FDD N/A 1
CELL_TDD SA0 0.6
SA1 0.4
SA2 0.2
SA3 0.3
SA4 0.2
SA5 0.1
SA6 0.5
NULL 1
NOTE
● All UE number specifications involved in this document are calculated according to the
traffic models for data services.
● The maximum number of UL-sync UEs that an LTE FDD cell can serve is also determined
by the CellRacThd.CellCapacityMode parameter.
● If a BBP model changes, the eNodeB automatically calculates the UE number
specification based on the new BBP model.
In FDD, when the maximum number of fixed PDCCH symbols is used, the number
of available CCEs depends on the system bandwidth and the value of
PHICHCfg.PhichResource. When the system bandwidth is 1.4 MHz, the maximum
number of PDCCH symbols is 4. For other system bandwidths, the maximum

(2020-12-29)
eRAN
number of PDCCH symbols is 3. PHICHCfg.PhichResource is equivalent to Ng in

3GPP TS 36.211. The parameter value can be 1/6, 1/2, 1, or 2. Table 4-4 lists the
corresponding number of available CCEs per TTI. ACH uses the number of
available CCEs that correspond to Ng = 1.
Table 4-4 Number of CCEs per TTI when the maximum number of PDCCH
symbols is used
Bandwidth (MHz) 20 15 10 5 3 1.4
PHICHCfg.PhichResource = 87 65 43 21 12 6
1/6
PHICHCfg.PhichResource = 86 64 42 21 12 6
1/2
PHICHCfg.PhichResource = 1 84 62 41 20 12 6
PHICHCfg.PhichResource = 2 80 59 39 19 11 6
4.1.2.2 Trigger Condition Judgment

If both of the following conditions are met, related parameters are adjusted
accordingly. For details, see 4.1.2.3 Intelligent Optimization Functions and
Parameter Adjustment.
● The collected data described in 4.1.2.1 Data Collection meets a trigger
condition for the corresponding intelligent optimization function described in
4.1.2.3 Intelligent Optimization Functions and Parameter Adjustment.
● The intelligent optimization function is not in penalty. The penalty duration is
specified by the LIOptRule.PenaltyTime parameter.
4.1.2.3 Intelligent Optimization Functions and Parameter Adjustment

A group of intelligent optimization functions is predefined for ACH on the eNodeB.
Each intelligent optimization function contains two rules, adjustment and
restoration. When the traffic load increases, the parameter settings are adjusted.
When the traffic load decreases, the parameter settings are restored. Table 4-5
lists the intelligent optimization functions and their corresponding IDs.
Table 4-5 Intelligent optimization functions and corresponding IDs
Optimization Function Intelligent Optimization Function

ID
TA optimization (FDD) 1
Abnormal UE detection and scheduling 2
Smart control for downlink frequency 3

selective scheduling
Adaptive RBG allocation 4

(2020-12-29)
eRAN
Optimization Function Intelligent Optimization Function

ID
Downlink non-GBR packet bundling 5
Uplink PRB allocation policy 6

optimization
PDCCH CCE capacity improvement 7
T302 optimization 8
Penalty for abnormal UE access 9
Intelligent AC control 10
Limitation on PUSCH power 12
Immunity of PUCCH to interference 13
Dynamic downlink CA control 14
Smart control for DRX 15
Intelligent increase in the A1 threshold 17
Smart control for dynamic DRX 18
Uplink RS power adaptation 251
A trigger condition and a parameter adjustment operation are configured for each
intelligent optimization rule.
● A set of trigger conditions corresponding to a rule ID is called a rule, and a

single trigger condition is called an atom rule. Atom rules corresponding to a
rule ID can be checked by running the LST LIOPTRULEMEMBER command.
● Each rule ID identifies an intelligent optimization action. The mapping
relationship can be checked by running the LST LIOPTRULE command.
● For details about measurement items involved in trigger conditions, see Table
4-1. Related thresholds can be adjusted by running the MOD
LIOPTATOMRULE command. For details about the adjustment method, see
4.4.1.2 Using MML Commands.
Table 4-6 lists the trigger condition corresponding to each atom rule ID.
Table 4-6 Trigger condition of each atom rule ID
Atom Rule ID Trigger Condition
1 User_Spec_Occupy_Rate > 50%
2 PDCCH_CCE_Utilization_Rate > 60%
3 DL_PRB_Utilization_Rate < 90%

(2020-12-29)
eRAN
Atom Rule ID Trigger Condition
4 UL_PRB_Utilization_Rate > 20%
5 User_Spec_Occupy_Rate < 40%
6 PDCCH_CCE_Utilization_Rate < 25%
7 DL_PRB_Utilization_Rate > 95%
8 UL_PRB_Utilization_Rate < 10%
11 ENB_USER_SPEC_EQU_OCCUPY_RATE > 50%
12 ENB_USER_SPEC_EQU_OCCUPY_RATE < 40%
15 PUSCH IN > –100 dBm
16 PUSCH IN < –110 dBm
17 PUCCH IN > –105 dBm
18 PUCCH IN < –115 dBm
19 UL_PRB_Utilization_Rate > 80%
20 UL_PRB_Utilization_Rate < 70%
21 ULSYNC_USER_NUM > 200
22 ULSYNC_USER_NUM < 160
23 Ulsync_User_Num x (20 MHz/Bandwidth) > 200
24 Ulsync_User_Num x (20 MHz/Bandwidth) < 160
131 EQV_BW_SF_ULSYNC_USER_NUM > 600
132 RL_EQV_BW_SF_ULSYNC_USER_NUM > 120
133 EQV_BW_SF_ULSYNC_USER_NUM < 400
134 RL_EQV_BW_SF_ULSYNC_USER_NUM < 80
The LST LIOPTRULE command can be executed to list the intelligent optimization
functions supported by ACH in the current release. The following describes all
intelligent optimization functions of ACH. Their default trigger conditions and
related thresholds are set by default.

(2020-12-29)
eRAN
NOTE
● If a parameter is manually adjusted by an operator and adaptively adjusted by an

intelligent optimization function, the latest adjustment will take effect. Therefore, it is
not recommended that operators manually adjust parameters using MML commands
specified by intelligent optimization functions while intelligent optimization functions
are taking effect. If the operator must manually adjust a parameter, it is recommended
that the corresponding intelligent optimization function be deactivated before adjusting
the parameter.
● An intelligent optimization rule must use the same measurement items to determine
whether to trigger the adjustment or restoration. In addition, a hysteresis must be
reserved between the threshold for triggering adjustment and the threshold for
triggering restoration. This can prevent frequent parameter modifications.
Adaptive RBG Allocation

In heavy traffic scenarios, the eNodeB adaptively allocates resource block groups
(RBGs) to reduce the consumed PDCCH CCEs and increase the downlink cell
capacity.
The eNodeB adaptively allocates the RBGs to meet data transmission
requirements. If more than one RBG is required, the eNodeB rounds up the
required number. For example, if the eNodeB calculates that 1.5 RBGs are
required, it allocates two RBGs. If fewer than one RBG is required, the eNodeB
allocates the required PRBs. For example, if two PRBs are required and they are
not enough to compose an RBG, the eNodeB allocates two PRBs. Adaptive RBG
allocation allows the eNodeB to schedule user data with minimum scheduling
occurrences at the cost of wasting a few PRBs. This function reduces the total
number of scheduling occurrences on the network and the number of the
consumed PDCCH CCEs.
This intelligent optimization function is activated by default.
The following table describes the trigger conditions and corresponding parameter
adjustments specified by intelligent optimization rules.
Rule ID Atom Rule ID Parameter Adjustment
7 Either of the The MOD CELLDLSCHALGO command is

following: executed with the
● 1 and 3 CellDlschAlgo.RbgAllocStrategy
parameter set to ADAPTIVE.
● 23 and 3
8 Either of the The parameter settings are restored to

following: those in the current database.
● 5 or 7
● 24 or 7
NOTE
The combination of atom rules 1 and 3 will be disused in later versions. You are advised to
use the combination of atom rules 23 and 3.
Atom rule 5 or 7 will be disused in later versions. You are advised to use atom rule 24 or 7.

(2020-12-29)
eRAN
Uplink PRB Allocation Policy Optimization

In heavy-traffic scenarios, the uplink PRBs between neighboring cells overlap with
each other, causing significant uplink interference before the uplink PRB allocation
policy is optimized. This function randomizes the positions of uplink PRBs,
reducing uplink interference and increasing uplink cell capacity.
This intelligent optimization function is deactivated by default.
11 Either of the The MOD CELLULSCHALGO command is

● 1 and 4 CellUlschAlgo.UlRbAllocationStrategy
parameter set to
● 23 and 4 FS_INRANDOM_ADAPTIVE.

● 5 or 8
● 24 or 8
NOTE
Abnormal UE Detection and Scheduling

After this function is activated, if the eNodeB detects 16 consecutive uplink cyclic
redundancy code (CRC) errors on a UE in the uplink, the eNodeB stops uplink
scheduling for the UE. The eNodeB then resumes uplink scheduling when it
receives a scheduling request (SR) from the UE. If the eNodeB detects 16
consecutive uplink discontinuous transmissions (DTXs) on a UE in the downlink,
the eNodeB stops downlink scheduling for the UE. The eNodeB then resumes
downlink scheduling when the uplink CRC result is correct or when periodic CQI
reporting reverts to normal on the PUCCH.
This function enables the eNodeB to detect abnormal UEs and cease scheduling,
preventing PRBs and PDCCH CCEs from being wasted by abnormal UEs. With this
function, the eNodeB can schedule more services in heavy traffic scenarios,
improving cell capacity. However, a slight probability exists that the eNodeB
incorrectly identifies abnormal UEs. If a UE is incorrectly identified as an abnormal
UE, it will experience prolonged transmission delay, degraded user experience, and
an increased probability of service drops.
This intelligent optimization function is deactivated by default.

(2020-12-29)
eRAN
3 Either of the The MOD CELLALGOSWITCH command is

following: executed with the AbnUeSchSwitch
● 1 and 2 option of the
CellAlgoSwitch.CellSchStrategySwitch
● 23 and 2 parameter selected to enable the function
of abnormal UE detection and scheduling.

● 5 or 6
● 24 or 6
NOTE
Smart Control for Downlink Frequency Selective Scheduling

Downlink frequency selective scheduling triggers large-scale aperiodic CQI
reporting, consuming a large number of uplink PRBs and CCEs and increasing
uplink interference. In the event of network congestion, disabling downlink
frequency selective scheduling helps reduce the interference and increase the
uplink cell capacity. However, disabling downlink frequency selective scheduling
slightly decreases downlink cell throughput.
5 Either of the The MOD CELLALGOSWITCH command is

following: executed with the FreqSelSwitch option of
● 1 and 2 the CellAlgoSwitch.DlSchSwitch
parameter deselected to disable downlink
● 23 and 2 frequency selective scheduling.

● 5 or 6
● 24 or 6

(2020-12-29)
eRAN
NOTE
T302 Optimization
An eNodeB sends an RRC Connection Reject message to a UE if the eNodeB
rejects the RRC connection request of the UE for a reason. The RRC Connection
Reject message contains the T302 timer IE. The UE initiates an RRC connection
request to access the network again after the waiting period specified by the T302
timer has expired. When the network traffic is heavy, flow control is likely to be
triggered because the number of UEs trying to access the eNodeB exceeds the
hardware capability or the CPU usage is excessively high. If flow control occurs, all
new UEs' access requests are rejected. The UEs wait for a specified period and
reinitiate RRC connection requests. Consequently, a large number of RRC
connection requests and rejection messages are generated. A large value can be
specified for the T302 timer to reduce the number of repeated access requests of
UEs, which decreases the signaling overhead and reduces the degree of a decrease
in the access success rate.
This intelligent optimization function is deactivated by default. For details about
how to activate this function, see 4.4.1.2 Using MML Commands.
15 11 The MOD RRCCONNSTATETIMER

command is executed with the
RrcConnStateTimer.T302 parameter set
to 16. RrcConnStateTimer.T302 is an
eNodeB-level parameter.
16 12 The parameter settings are restored to

those in the current database.
Penalty for Abnormal UE Access

If a UE accesses a cell repeatedly and fails, the RRC setup success rate of the cell
decreases and extra signaling is generated.
The eNodeB recognizes such UEs and rejects access requests to resolve this issue.
In a period specified by the sum of UeTimerConst.T300 and
RrcConnStateTimer.FilterReptRrcConnReqTimer, if the eNodeB detects that the
number of access requests initiated by a UE exceeds the threshold specified by
GlobalProcSwitch.LteRrcConnPunishmentThld, it considers the UE as abnormal
and automatically rejects the RRC connection requests of the UE. The request
rejection message contains the T302 timer IE, and the UE can re-initiate another
RRC connection request only after waiting for a period specified by the T302 timer.
In this way, signaling load caused by such repeated access is reduced.

(2020-12-29)
eRAN

17 11 The MOD GLOBALPROCSWITCH

command is executed with the
GlobalProcSwitch.LteRrcConnPunish-
mentThld parameter set to 5.
GlobalProcSwitch.LteRrcConnPunish-
mentThld is a base-station-level
parameter.

Intelligent AC Control
When a cell is congested, the intelligent AC control function limits the proportion
of UE access with the cause value MO Signaling or MO Data to ensure smooth
access. This prevents a large number of UEs from accessing the network
simultaneously, which mitigates the signaling impact on the network and the
congestion in the cell.
19 1 The MOD CELLALGOSWITCH command is

executed with the
CellAlgoSwitch.AcBarAlgoSwitch
parameter set to
ACBAR_SWITCH_DYNAMIC and the
DYNAMIC_FOR_MO option of the
CellAlgoSwitch.AcBarAlgoforDynSwitch
parameter selected.
The MOD CELLACBAR command is
executed with the
CellAcBar.AcBarringInfoCfgInd,
CellAcBar.AcBarringForMoDataCfgInd,
and CellAcBar.AcBarringForMoSigCfgInd
parameters set to CFG.


(2020-12-29)
eRAN
NOTE
Based on the congestion judgment algorithm of intelligent AC control, the eNodeB

performs relevant parameter modifications when the preceding trigger conditions are met.
Immunity of PUCCH to Interference

In a cell with heavy traffic load, strong PUCCH interference affects PUCCH
demodulation. In a cell with heavy traffic load and strong PUCCH interference, the
PUCCH power can be increased to counter interference, enhance the PUCCH
reliability, reduce the downlink block error rate (BLER), decrease the DTX
proportion, and increase downlink throughput.

(2020-12-29)
eRAN
25 13 and 17 When the serving cell meets the trigger

conditions, the serving cell and intra-
eNodeB or inter-eNodeB high-interference
neighboring cells with X2 interfaces set up
between the serving eNodeB and
neighboring eNodeBs (the serving cell
notifies the inter-eNodeB neighboring cells
over X2 interfaces) perform the following
parameter adjustments:
● The MOD CELLPCALGO command is
executed with the
CellPcAlgo.PucchCloseLoopPcType
parameter set to
USE_P0NOMINALPUCCH, and with the
CellPcAlgo.PucchPcTargetSinrOffset
parameter set to the same value as the
ParaAutoOptCfg.PUCCHPcSINROffset
4AutoOpt parameter.
● The MOD CELLULPCCOMM command
is executed with the
CellUlpcComm.P0NominalPUCCH
parameter set to the same value as the
ParaAutoOptCfg.P0NominalPUCCH4A
utoOpt parameter.
NOTE
1. In a 5-minute period, if the number of
handovers between the serving cell and
target intra-frequency neighboring cells
exceeds ParaAutoOptCfg.HOTimesThd, a
maximum of five top-ranked intra-frequency
neighboring cells are selected as high-
interference neighboring cells. The preceding
measures can be taken only when the ACH
is enabled for the serving cell and the
selected neighboring cells.
2. If no neighboring cell meets the condition,
the eNodeB performs the preceding
operations only on the serving cell.
3. After the rule is triggered, if the X2 interface
is faulty or the neighbor relationship with a
neighboring cell is deleted, parameter
settings will be restored for the neighboring
cell after four hours.
4. After the rule is triggered, parameter
settings will be restored for a neighboring
cell immediately if the neighboring cell is
deactivated.

(2020-12-29)
eRAN
26 14 or 18 When the serving cell meets the trigger

conditions, the serving cell and its
neighboring cells with parameter
modifications restore their parameter
values to those in the current database.
Dynamic Downlink CA Control

The uplink resources of a cell are easily restricted compared with downlink
resources when most of services performed by UEs in the cell are uplink real-time
services in heavy-traffic scenarios. If uplink traffic load is heavy, the uplink service
experience can be preferentially guaranteed by reducing the uplink overhead of
CA UEs. This is implemented by disabling downlink carrier aggregation (CA).
Downlink CA can be enabled again after the uplink traffic load restores to a
normal level.
After downlink CA is disabled for a cell, the eNodeB does not configure secondary
cells (SCells) for UEs in the process of initial access, incoming handover, and
incoming RRC connection reestablishment. In addition, when smart primary
component carrier (PCC) is enabled on both the local eNodeB and neighboring
eNodeBs, the local eNodeB notifies intra-eNodeB neighboring cells and the
neighboring eNodeBs that the cell is heavily loaded and cannot perform downlink
CA. This prevents CA UEs in other cells from being handed over to the cell.
27 Either of the The MOD CAMGTCFG command is

following: executed in the serving cell with the
● 21 and 19 CaMgtCfg.CellMaxPccNumber parameter
set to 0 when the serving cell meets the
● 23 and 19 trigger condition.

following: those in the current database for the
● 22 or 20 serving cell when it meets the trigger
condition.
● 24 or 20
NOTE
The combination of atom rules 21 and 19 will be disused in later versions. You are advised
to use the combination of atom rules 23 and 19.
Atom rule 22 or 20 will be disused in later versions. You are advised to use atom rule 24 or
20.

(2020-12-29)
eRAN
Smart Control for DRX

In a heavy traffic scenario with excessive UEs in discontinuous reception (DRX)
mode, the eNodeB maintains multiple timers for each UE in DRX mode. This
makes an impact on board CPU loads, even triggering flow control because of
CPU overload. At the same time, Uu signaling overhead of configuring UEs in DRX
mode increases. When the network is congested, disabling DRX helps decrease
board CPU loads and avoid flow control. Disabling DRX also reduces Uu signaling
overhead and increases cell capacity.
29 1 The MOD CELLDRXPARA command is

executed with the
CellDrxPara.DrxAlgSwitch parameter set
to OFF.

Intelligent Increase in the A1 Threshold

To meet the requirements on latency and reliability for Uu signaling messages, the
scheduling priorities for Uu signaling messages are high and low-order
modulation scheme is used for the messages. In a heavy traffic scenario, excessive
Uu signaling messages reduce the scheduling opportunity of data services,
affecting user experience and decreasing cell capacity. A low A1 reference signal
received power (RSRP) threshold related to inter-frequency handovers results in
inter-frequency measurement configuration from being delivered to a UE and then
being deleted repeatedly, especially when the channel quality fluctuates. If the A1
RSRP threshold is increased a bit, the preceding situation can be avoided, reducing
unnecessary signaling overhead, improving user experience, and increasing cell
capacity.

(2020-12-29)
eRAN
33 Either of the The MOD INTERFREQHOGROUP

following: command is executed with the
● 1 and 2 InterFreqHoGroup.A3InterFreqHoA1Thd
Rsrp parameter set to a value 6 dB greater
● 23 and 2 than the
InterFreqHoGroup.A3InterFreqHoA2Thd
Rsrp parameter value and the
InterFreqHoGroup.InterFreqHoA1ThdRsr
p parameter set to a value 6 dB greater
than the
InterFreqHoGroup.InterFreqHoA2ThdRsr
p parameter value.
● 5 or 6
● 24 or 6
NOTE
TA Optimization (FDD)
An eNodeB maintains uplink timing for each UE to ensure that the signals sent by
all UEs can reach the eNodeB simultaneously within a period. Maintaining uplink
timing involves two procedures: A UE sends the eNodeB uplink signals for timing
advance (TA) measurement, and then the eNodeB sends the UE a TA adjustment
instruction.
If a UE does not send uplink signals to the eNodeB for TA measurement within a
certain period of time, the eNodeB performs uplink scheduling for the UE. This
allows the eNodeB to determine the TA for the UE by using the demodulation
reference signal (DMRS). This process consumes PDCCH scheduling resources and
uplink PRBs. The eNodeB periodically sends TA adjustment instructions to UEs to
maintain uplink synchronization. This process also consumes PDCCH scheduling
resources and downlink PRBs.
If the traffic load is light, the eNodeB will have sufficient channel resources to
maintain uplink timing for UEs, ensuring TA accuracy and service quality. If
network congestion occurs, it is recommended that the TA optimization function
be enabled. This function reduces the uplink scheduling resources used for TA
measurement using DMRS and lowers the transmission frequency of TA
adjustment instructions, reducing the consumed PDCCH scheduling resources and
PRBs and increasing the cell capacity.

(2020-12-29)
eRAN
In addition, because the transmission frequency of TA adjustment instructions

decreases, UEs may enter the out-of-synchronization state. This situation is
avoidable if TimeAlignmentTimer.TimeAlignmentTimer is set to INFINITY.
1 Either of the The MOD TATIMER command is executed

following: with the TimeAlignmentTim-
● 1 and 2 er.TimingResOptSwitch parameter set to
ON and the TimeAlignmentTim-
● 23 and 2 er.TimeAlignmentTimer parameter set to
INFINITY to enable the TA optimization
function.

● 5 or 6
● 24 or 6
NOTE
PDCCH CCE Capacity Improvement

The CCE aggregation level varies with UE channel conditions in scheduling. If the
remaining consecutive CCEs cannot meet the aggregation level requirements, the
eNodeB cannot schedule the corresponding UE. In this situation, CCEs are
fragmented and PDCCH CCEs cannot be fully utilized.
PDCCH CCE capacity improvement enables the eNodeB to reallocate CCEs, in the
event of a CCE allocation failure for scheduling, by aggregating CCEs at a low level
and increasing the transmit power. This processing mechanism has the same effect
as high-level CCE aggregation. PDCCH CCE capacity improvement increases the
CCE allocation success rate, improving the PDCCH CCE usage and therefore
increasing uplink and downlink cell capacity.
A high CCE aggregation level is used for scheduling to obtain better control
channel demodulation performance. When CCE resources are sufficient in a cell, a
higher CCE aggregation level enables UEs to obtain a better experience. When CCE
resources are insufficient in a cell due to congestion, this function can decrease
the CCE aggregation level of the data radio bearer (DRB) until the normal
demodulation requirement is met, which saves CCE resources, schedules more UEs,
and increases uplink and downlink cell capacity.

(2020-12-29)
eRAN
13 Either of the The MOD CELLPDCCHALGO command is

● 1 and 2 CellPdcchAlgo.PdcchCapacityImproveS-
witch parameter set to ON to enable
● 23 and 2 PDCCH CCE capacity improvement.

● 5 or 6
● 24 or 6
NOTE
Limitation on PUSCH Power

PUSCH closed-loop power control is implemented based on the target signal to
interference plus noise ratio (SINR). If the actual SINR is less than the target SINR,
the eNodeB instructs the UE to increase the PUSCH transmit power. If strong
PUSCH interference occurs, UEs in neighboring cells may increase the PUSCH
transmit power in a competitive way. Consequently, interference between
neighboring cells becomes increasingly strong and the PUSCH quality deteriorates.
In scenarios with both heavy traffic and strong PUSCH interference, this function
limits the RSRP to a value below the upper threshold. This reduces uplink
interference and increases the uplink throughput of UEs far away from the cell
center.

(2020-12-29)
eRAN
23 13 and 15 When the serving cell meets the trigger

conditions, it notifies intra-eNodeB or
inter-eNodeB high-interference
neighboring cells with X2 interfaces set up
between the serving eNodeB and
neighboring eNodeBs (the serving cell
notifies the inter-eNodeB neighboring cells
over X2 interfaces) to perform the
following parameter adjustments:
● Selecting PuschRsrpHighThdSwitch
option of the
CellAlgoSwitch.UlPcAlgoSwitch
parameter
● Modifying the
CellPcAlgo.PuschRsrpHighThd
parameter value to be identical to the
value of the
ParaAutoOptCfg.PUSCHRsrpHighThd4
AutoOpt parameter
NOTE
1. In a 5-minute period, if the number of
handovers between the serving cell and
target intra-frequency neighboring cells
exceeds ParaAutoOptCfg.HOTimesThd, a
maximum of five top-ranked intra-frequency
neighboring cells are selected as high-
interference neighboring cells.
2. After the rule is triggered, if the X2 interface
is faulty or the neighbor relationship with a
neighboring cell is deleted, parameter
settings will be restored for the neighboring
cell after four hours.
3. After the rule is triggered, parameter
settings will be restored for a neighboring
cell immediately if the neighboring cell is
deactivated.
24 14 or 16 When meeting the trigger conditions, the

serving cell notifies its neighboring cells
with parameter modifications to restore
their parameter values to those in the
current database.
Downlink Non-GBR Packet Bundling

On a network serving a high proportion of smart terminals and small-packet
services, multiple downlink data packets can be combined and then transmitted in
heavy traffic scenarios. This processing mechanism reduces the number of
occurrences for scheduling, lowers the consumed CCEs, and improves the downlink
PRB usage and downlink cell capacity. However, downlink non-GBR packet

(2020-12-29)
eRAN
bundling lowers scheduling priorities and increases scheduling delay for some UEs
causing their user experience to deteriorate. When CCE usage is low in light traffic
conditions, you are advised not to enable this function.
This intelligent optimization function is activated by default. The following table

describes the trigger conditions and corresponding parameter adjustments
specified by intelligent optimization rules.
9 1 and 2 The MOD CELLALGOSWITCH command is

executed with the NonGbrBundlingSwitch
option of the CellAlgoSwitch.DlSchSwitch
parameter selected to enable downlink
non-GBR packet bundling.
10 5 or 6 The parameter settings are restored to

NOTE
This intelligent optimization function takes effect only when the downlink non-GBR packet
bundling function (described in Scheduling) has been enabled. If the downlink non-GBR
packet bundling function is disabled, the intelligent optimization function cannot take
effect when the trigger conditions are met, and an alarm is reported indicating that the
configured value is greater than the licensed value.
Smart Control for Dynamic DRX

In heavy traffic scenarios, UEs in connected mode frequently exchange data with
the network, increasing network load and decreasing the number of available RRC
connections. When there are a large number of UEs that access a cell, smart
control for dynamic DRX reduces the amount of RRC connection establishment
and release signaling for services that use small, sparse packets or heartbeat
packets, decreases the signaling overhead generated for maintaining uplink
synchronization of UEs, and increases cell capacity.

35 27 The MOD CELLALGOSWITCH command is

executed with the DynDrxSwitch option
of the CellAlgoSwitch.DynDrxSwitch
parameter selected.


(2020-12-29)
eRAN
Uplink RS Power Adaptation

In high-density LampSite networking with heavy traffic, overlapping cell coverage
and uneven coverage areas result in imbalanced UE distribution and cell loads. If
some cells are congested, the user-perceived rate is severely affected. When a
large number of UEs access a cell, the uplink RS power adaptation function
adjusts the RS power of the cell based on the UE distribution and available uplink
resources to scale the cell coverage area. This balances UE distribution and uplink
loads.
501 131 and 132 The MOD PDSCHCFG command is

executed with the
PDSCHCfg.ReferenceSignalPwr
parameter set to a value equal to the
PDSCHCfg.ReferenceSignalPwr
parameter value deducted by 3 dBm.
502 133 or 134 The parameter settings are restored to

NOTE
To protect the lower limit of the PDSCHCfg.ReferenceSignalPwr parameter, uplink RS

power adaptation does not take effect if the following condition is met before automatic
parameter adjustment: PDSCHCfg.ReferenceSignalPwr ≤ [–17.8 – 10lg(Cell bandwidth/20
MHz)].
4.1.2.4 Customization of Intelligent Optimization Rules

The intelligent optimization rules of ACH can be customized to help handle
different network congestions. The concepts related to customizing intelligent
optimization rules are as follows:
● Intelligent optimization rule

It indicates a set of conditions for triggering the adjustment or restoration
operations of an intelligent optimization function. For example, the conditions
"User_Spec_Occupy_Rate > 50%" and "DL_PRB_Utilization_Rate < 90%" for
triggering the adjustment operation of the intelligent optimization function
"Adaptive RBG Allocation" in 4.1.2.3 Intelligent Optimization Functions and
Parameter Adjustment are called an intelligent optimization rule.
● Intelligent optimization atom rule
It indicates one of the conditions for triggering the adjustment or restoration
operations of an intelligent optimization function. For example, the condition
"User_Spec_Occupy_Rate > 50%" or "DL_PRB_Utilization_Rate < 90%" for
triggering the adjustment operation of the intelligent optimization function

(2020-12-29)
eRAN
"Adaptive RBG Allocation" in 4.1.2.3 Intelligent Optimization Functions and

Parameter Adjustment is called an intelligent optimization atom rule.
The following scenarios for customizing an intelligent optimization rule are
supported:
● Deactivating an intelligent optimization rule
Enabling this feature will activate some of the intelligent optimization
functions by default. You can customize intelligent optimization functions
based on network conditions.
You can run the ACT LIOPTRULE command to activate an intelligent
optimization rule or DEA LIOPTRULE to deactivate an intelligent optimization
rule. For details, see 4.4.1.2 Using MML Commands.
● Disabling a trigger condition (referred to as an intelligent optimization atom
rule) for an intelligent optimization rule
If a default atom rule for an intelligent optimization rule is too strict, the
intelligent optimization rule will be difficult to apply. In this situation, you can
disable the trigger condition to make the intelligent optimization rule be
easily applied, thereby improving feature performance.
NOTE
If all of the atom rules of an intelligent optimization rule are disabled, the intelligent
optimization rule is deactivated.
● Modifying a trigger condition (referred to as an intelligent optimization atom
rule) for an intelligent optimization rule
If a default atom rule for an intelligent optimization rule is too strict, you can
modify the threshold of the atom rule, in addition to disabling it, to make the
intelligent optimization rule be easily applied. The user number threshold and
the user proportion threshold can be decreased properly according to the
average number of UEs in RRC_CONNECTED mode. It is recommended that
the PUCCH noise interference (NI) threshold and the PUSCH NI threshold be
not decreased. The essence of the optimization function, limitation on PUSCH
power, is to increase the throughput of users at the cell edge by decreasing
the throughput of users near the cell enter. This optimization function may
produce negative gains at a low cell interference level because the positive
gains of users at the cell edge may not compensate the loss of users near the
cell center.
If an atom rule for an intelligent optimization rule is too loose, the intelligent
optimization rule will be applied too frequently, adversely affecting ACH
performance. In this situation, you can increase the value of the threshold for
the atom rule.
For details about how to customize the intelligent optimization rules, see 4.4.1
Data Configuration.
4.2 Network Analysis
4.2.1 Benefits
ACH provides the following gains:

(2020-12-29)
eRAN
● Adjusting the parameter settings based on the predefined intelligent

optimization functions in the event of network congestion to improve
network performance and user experience
● Reducing the complexity of the service guarantee process and reducing
manual O&M costs in heavy traffic scenarios
NOTE
Intelligent optimization functions cannot remove hardware resource bottlenecks.
Most Beneficial Scenarios

To achieve optimal benefits, the following procedures must be completed before
individual optimization functions are enabled:
● Obtain information about the trigger conditions, described in 4.1.2.3
Intelligent Optimization Functions and Parameter Adjustment, for
individual optimization functions. An optimization function takes effect only if
the corresponding trigger condition is met.
● Verify parameter settings on the live network. Evaluate the function
performance and check whether it is necessary to activate intelligent
optimization functions. Table 4-7 describes when to activate intelligent
optimization functions.
NOTE
When the modified parameter values in the intelligent optimization rule of an

intelligent optimization function conflict with the configurations on the live network, if
the condition for triggering the rule is met, the rule is executed but does not take
effect. In the SON log, operators can find the corresponding "Modify Cell-level
Runtime Parameters" or "Modify eNodeB-level Runtime Parameters" event. In this
scenario, operators may consider that the optimization function does not bring a
positive gain. To avoid this, it is recommended that the DEA LIOPTRULE command be
executed to deactivate the corresponding intelligent optimization rule.
Table 4-7 Diagnosis conditions for activating intelligent optimization

functions
Intelligent Diagnosis Condition MML Command to
Optimization View Parameter
Function Settings
Adaptive RBG If the LST CELLDLSCHALGO

allocation CellDlschAlgo.RbgAllocStrategy
parameter has been set to
ADAPTIVE before the function is
activated, this function does not
work after being activated. It is
recommended that this function
be deactivated in this case.

(2020-12-29)
eRAN

Function Settings
Uplink PRB If the LST CELLULSCHALGO

allocation CellUlschAlgo.UlRbAllocationStr
policy ategy parameter has been set to
optimization FS_INRANDOM_ADAPTIVE
before the function is activated,
this function does not work after
being activated. It is
Abnormal UE If the AbnUeSchSwitch option of LST

detection and the CELLALGOSWITCH
scheduling CellAlgoSwitch.CellSchStrategy-
Switch parameter has been
selected before the function is
Smart control If the FreqSelSwitch option of the LST

for downlink CellAlgoSwitch.DlSchSwitch CELLALGOSWITCH
frequency parameter has been deselected
selective before the function is activated,
scheduling this function does not work after
T302 If the RrcConnStateTimer.T302 LST

optimization parameter has been set to 16 RRCCONNSTATETIM-
before the function is activated, ER
Penalty for If the value of LST

abnormal UE GlobalProcSwitch.LteRrcConnPu GLOBALPROCSWITC
access nishmentThld is less than 5 but H
greater than 0 before this function
is activated, penalty for abnormal
UE access is easy to trigger. In this
case, if the function is activated
and the parameter is set to 5, it is
difficult to trigger penalty for
abnormal UE access, and
therefore it is recommended that
this function be deactivated.

(2020-12-29)
eRAN

Function Settings
Intelligent AC If the LST

control CellAlgoSwitch.AcBarAlgoSwitch CELLALGOSWITCH
ACBAR_SWITCH_DYNAMIC and
the DYNAMIC_FOR_MO option of
the
CellAlgoSwitch.AcBarAlgoforDy
nSwitch parameter has been
selected before the function is
Immunity of If the LST CELLPCALGO

PUCCH to CellPcAlgo.PucchCloseLoopPc- and LST
interference Type parameter has been set to CELLULPCCOMM
USE_P0NOMINALPUCCH before
the function is activated, this
function does not work after
If the
CellUlpcComm.P0NominalPUCC
H parameter has not been set to a
default value before the function
is activated, this function does not
Dynamic If the LST CAMGTCFG

downlink CA CaMgtCfg.CellMaxPccNumber
control parameter has been set to 0
Smart control If the CellDrxPara.DrxAlgSwitch LST CELLDRXPARA

for DRX parameter has been set to OFF

(2020-12-29)
eRAN

Function Settings
Intelligent This function does not work after LST

increase in the being activated and you are INTERFREQHOGROU
A1 threshold advised to deactivate this function P
if the following conditions are met
before the function is activated:
● InterFreqHoGroup.A3InterFre
qHoA1ThdRsrp ≥
InterFreqHoGroup.A3InterFre
qHoA2ThdRsrp + 6 dBm
● InterFreqHoGroup.A3InterFre
qHoA1ThdRsrp ≥
InterFreqHoGroup.InterFreqH
oA2ThdRsrp + 6 dBm
Smart control If the DynDrxSwitch option of LST
for dynamic the CELLALGOSWITCH
DRX CellAlgoSwitch.DynDrxSwitch
parameter has been selected
Downlink If the NonGbrBundlingSwitch LST

non-GBR option of the CELLALGOSWITCH
packet CellAlgoSwitch.DlSchSwitch
bundling parameter has been selected
Limitation on If the PuschRsrpHighThdSwitch LST

PUSCH power option of the CELLALGOSWITCH
CellAlgoSwitch.UlPcAlgoSwitch
parameter has been selected

(2020-12-29)
eRAN

Function Settings
TA If the TimeAlignmentTim- LST TATIMER

optimization er.TimingResOptSwitch
(FDD) parameter has been set to ON
and the TimeAlignmentTim-
er.TimeAlignmentTimer
INFINITY before the function is
If the TimeAlignmentTim-
er.TimingAdvCmdOptSwitch,
TimeAlignmentTim-
er.TimeAlignmentTimer, and
TimeAlignmentTim-
er.TimingMeasMode parameters
are not set to their default values,
it is recommended that this
function be deactivated.
PDCCH CCE If the LST

capacity CellPdcchAlgo.PdcchCapacityIm- CELLPDCCHALGO
improvement proveSwitch parameter has been
set to ON before the function is
Benefit Description
The following are benefits of the intelligent optimization functions in the event of
network congestion:
● Adaptive RBG allocation

This function enables the eNodeB to adaptively allocate the number of RBGs
to meet the data transmission requirements. The eNodeB can schedule user
data with a minimum number of scheduling occurrences at the cost of
wasting a few PRBs. This function reduces the total number of scheduling
occurrences, lowers the number of the PDCCH CCE overhead, and increases
the value of Cell Downlink Average Throughput.
● Abnormal UE detection and scheduling
This function enables the eNodeB to detect abnormal UEs and stop
scheduling for abnormal UEs, preventing uplink and downlink PRBs and CCEs
from being wasted by abnormal UEs. The eNodeB can schedule more services

(2020-12-29)
eRAN
in heavy traffic scenarios, increasing the values of Cell Downlink Average

Throughput and Cell Uplink Average Throughput.
● Smart control for downlink frequency selective scheduling
This function enables the eNodeB to reduce aperiodic CQI reporting,
decreasing the consumed CCEs and uplink PRBs. This function helps reduce
the uplink interference and increase the value of Cell Uplink Average
Throughput.
● T302 optimization
Owing to excessive UEs or a high CPU usage, all new UEs' access requests are
rejected. The request rejection message contains the T302 timer IE. When the
waiting period specified by the T302 timer has expired, the UEs can re-initiate
RRC connection requests. This function is used for increasing the T302 period
in such scenarios to decrease the number of repeated UE access attempts and
increase the RRC connection setup success rate. The number of Msg3
messages is reduced, conserving CCE and uplink PRB resources, which slightly
increases uplink capacity. The CPU usage of the main control board also
decreases because less signaling is processed.
● Penalty for abnormal UE access
This function reduces the signaling overhead generated during the UE access
by decreasing the access attempts of abnormal UEs. The CPU usage of the
main control board is decreased, and the value of RRC Setup Success Rate
(Service) is increased.
● Immunity of PUCCH to interference
In heavy-traffic and high PUCCH interference scenarios, this intelligent
optimization function increases the PUCCH transmit power, enhances the
PUCCH transmission performance, decreases the DTX proportion, and
increases the values of Cell Downlink Average Throughput and User
Downlink Average Throughput.
● Dynamic downlink CA control
This function preferentially guarantees uplink service experience of users in a
heavy-traffic cell by disabling downlink CA for UEs in the process of initial
access, incoming handovers, or incoming RRC connection reestablishment.
Therefore, this function will reduce the average and maximum numbers of CA
UEs in the downlink CA state in the cell and its neighboring cells that may be
configured as SCells for UEs in the cell.
● Smart control for DRX
This function decreases CPU loads of boards by disabling the DRX feature in
heavy-traffic scenarios. This prevents flow control from being triggered,
decreases Uu signaling overheads, and increases cell capacity.
● Smart control for dynamic DRX
This function decreases Uu signaling overheads and increases cell capacity by
activating dynamic DRX in heavy-traffic scenarios.
● Uplink PRB allocation policy optimization
This function enables the eNodeB to randomize the positions of allocated
uplink PRBs, reducing the interference among neighboring cells and increasing
the value of Cell Uplink Average Throughput.
● Intelligent AC control

(2020-12-29)
eRAN
This function controls the access of UEs when cell congestion occurs. A
signaling storm is avoided because UEs do not access the network
simultaneously, which reduces the number of UE access failures, and increases
the value of RRC Setup Success Rate (Service).
● Intelligent increase in the A1 threshold
This function raises the A1 RSRP threshold related to inter-frequency
handovers to prevent inter-frequency measurement configuration from being
delivered to a UE and then being deleted repeatedly, when the channel
quality fluctuates. This decreases unnecessary signaling overheads, improves
user experience, and increases cell capacity.
● Downlink non-GBR packet bundling
This function enables the eNodeB to combine multiple downlink data packets
before transmitting them, reducing the total number of scheduling
occurrences at the cost of fairness for some UEs. This function lowers the
number of consumed CCEs, improves the downlink PRB usage, and increases
the value of Cell Downlink Average Throughput.
● TA optimization (FDD)
This function enables the eNodeB to reduce the resources used for TA
measurement and lower the transmission frequency of TA adjustment
instructions, reducing the consumed PDCCH CCEs and uplink and downlink
PRBs and increasing the values of Cell Downlink Average Throughput and
Cell Uplink Average Throughput.
● PDCCH CCE capacity improvement
This function enables the eNodeB to reallocate CCEs, in the event of a CCE
allocation failure for scheduling, by aggregating CCEs at a low level and
increasing the transmit power. This function improves the PDCCH CCE usage
and increases the values of Cell Downlink Average Throughput and Cell
Uplink Average Throughput.
A high CCE aggregation level is used for scheduling to obtain better control
channel demodulation performance. When CCE resources are sufficient in a
cell, a higher CCE aggregation level enables UEs to obtain a better experience.
When CCE resources are insufficient in a cell due to congestion, this function
decreases the CCE aggregation level of the DRB. This function continues until
the normal demodulation requirement is met, which conserves CCE resources,
schedules more UEs, and increases the values of Cell Downlink Average
Throughput and Cell Uplink Average Throughput.
● Limitation on PUSCH power
This function prevents the RSRP values received in neighboring cells of a
heavily loaded cell from exceeding the preset threshold in heavy traffic and
strong PUSCH interference scenarios, thereby controlling uplink interference
and increasing the uplink throughput of UEs far away from the cell center in
the heavily loaded cell. This method improves the experience of UEs far away
from the cell center in a heavily loaded cell by sacrificing the experience of
UEs near the cell center and UEs at a medium distance from the cell center in
neighboring cells. Therefore, this method may decrease the uplink cell and
user throughputs in the neighboring cells of the heavily loaded cell. When
there are multiple heavily loaded neighboring cells, the neighboring cells may
notify each other to limit the PUSCH power. This may decrease the uplink
throughput of UEs in the center of the heavily loaded cells. In this scenario,
this function aims to decrease uplink interference and increase the uplink

(2020-12-29)
eRAN
throughput of UEs far away from the cell center. However, it cannot ensure
that the average uplink cell and user throughputs of a heavily loaded cell do
not decrease.
● Uplink RS power adaptation
This function enables the eNodeB to adjust cell RS power based on the UE
distribution and available uplink resources in high-density LampSite
networking with heavy traffic. In this way, the cell coverage can be adjusted
to balance UE distribution and uplink loads when a large number of UEs
access a cell.
This function may decrease the value of User Uplink Average Throughput in
unconventional scenarios where there are a large number of UEs but the PRB
usage is low.
4.2.2 Impacts
Network Impact
The following are impacts of intelligent optimization functions on a network:
● Adaptive RBG allocation

This function reduces the period of time for user data in the buffer and lowers
the number of active UEs in a cell. This function may slightly decrease the
average number of scheduled UEs per TTI in the downlink.
● Abnormal UE detection and scheduling
After this function is executed, the transmission delay of UEs who are
incorrectly detected as abnormal UEs at a low probability is prolonged. In
addition, the value of Service Drop Rate increases and the value of RRC
Setup Success Rate (Service) decreases for UEs which are incorrectly
detected as abnormal UEs because of poor signal quality.
● Smart control for downlink frequency selective scheduling
This function sacrifices the downlink frequency selective scheduling gains, that
is, reduces Cell Downlink Average Throughput.
● T302 Optimization
This function may increase the waiting time for some UEs to re-access a cell.
● Penalty for abnormal UE access
This function slows down the access of abnormal UEs.
● Immunity of PUCCH to interference
After this function is executed, interference with neighboring cells may
increase as PUCCH transmit power of neighboring cells competes to increase.
● Dynamic downlink CA control
This function reduces downlink throughput and downlink PRB usage of a cell
and neighboring cells that may be configured as SCell for UEs that treat the
local cell as their primary cell (PCell). This function decreases User Downlink
Average Throughput of UEs which access the cell after the function is
enabled.
● Smart control for DRX
After this function is executed, UE power consumption increases.

(2020-12-29)
eRAN
● Smart control for dynamic DRX

After this function is executed, the RSRP measurement period is extended
because dynamic DRX is activated. As a result, the number of delayed
handovers, service drops, or RRC connection reestablishments increases. For
details, see the impacts of dynamic DRX described in DRX and Signaling
Control.
● Downlink non-GBR packet bundling
This function enables the eNodeB to combine multiple downlink data packets
before transmitting them, reducing the total number of scheduling
occurrences at the expense of fairness for some UEs. As a result, this function
prolongs the delay for a number of UEs.
● TA optimization (FDD)
This function reduces the scheduling requests for TA measurement and
adjustment in the uplink and downlink, and therefore the average numbers of
scheduled UEs per TTI both in the downlink and uplink in the cell may slightly
decrease. This function also slightly decreases the TA accuracy of UEs,
affecting high-speed UE throughput.
● PDCCH CCE capacity improvement
This function increases the transmit power for CCEs, which may increase the
interference against the corresponding symbols in neighboring cells,
decreasing the value of Cell Downlink Average Throughput. This function
decreases the DRB aggregation level, which increases the downlink DTX
proportion and the downlink IBLER. The values of Cell Downlink Average
Throughput and Cell Uplink Average Throughput decrease when the value
of Downlink Resource Block Utilizing Rate is greater than 95%, the CCE
usage is greater than 60%, and most UEs in the cell are far away from the cell
center.
● Limitation on PUSCH power
After this function is executed, for a cell with a limited high PUSCH RSRP
threshold, the uplink modulation and coding scheme (MCS) and User Uplink
Average Throughput of CCUs and UEs at the medium distance of the cell
center may decrease.
● Uplink RS power adaptation
After this function is executed, for a cell with a decrease in RS power, the
downlink MCS index and User Downlink Average Throughput of the cell
may decrease.

(2020-12-29)
eRAN
Function Impacts
RAT Function Function Referenc Description
Name Switch e
FDD CA cell None Carrier The

TDD Aggregati CaMgtCfg.CellMaxPccNumbe
on r parameter of the serving cell
is set to 0 when dynamic
downlink CA control in ACH is
enabled and the trigger
condition is met. In this case,
if the PccSmartCfgSwitch
option of the
ENodeBAlgoSwitch.CaAlgoS
witch parameter is selected
on the serving eNodeB and
neighboring eNodeBs, CA UEs
in intra- or inter-eNodeB
neighboring cells are not
handed over to the cell even
when the number of CA UEs
in the cell does not exceed the
preset threshold.
FDD DRX CellDrxPara. DRX and DRX is disabled for a cell if

TDD DrxAlgSwitch Signaling smart control for DRX in ACH
Control is activated and the trigger
condition is met. In this case,
UEs in the cell do not enter
DRX mode any more.
FDD UL CPC UL_COORD_P Uplink If limitation on PUSCH power

C_SWITCH Coordinat in ACH and uplink coordinated
option of the ed power control (UL CPC) are
UlCsAlgoPara Schedulin both enabled, limitation on
.UlCsSw g PUSCH power affects UL CPC
parameter performance. This occurs
when the
ParaAutoOptCfg.PUSCHRsrp
HighThd4AutoOpt parameter
value is less than –82 dBm. A
smaller parameter value leads
to a greater impact, and UL
CPC will not take effect when
the parameter is set to a
sufficiently small value.
4.3 Requirements

(2020-12-29)
eRAN
4.3.1 Licenses
The following are FDD license requirements.
RAT Feature ID Feature Name Model Sales Unit
FDD LOFD-081205 Automatic LT1S000ACH0 per eNodeB

Congestion 0
Handling
Uplink RS power adaptation applies only to LampSite cells. This function does not
require a license yet.
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
Name Switch e
FDD Downlink NonGbrBund Schedulin The intelligent optimization

TDD non-GBR lingSwitch g function downlink non-GBR
packet option of the packet bundling depends on
bundling CellAlgoSwit downlink non-GBR packet
ch.DlSchSwit bundling in the scheduling
ch parameter function.
When the cell traffic load
meets the trigger condition for
the rule correlated to the
intelligent optimization
function, the parameter
settings are adjusted as
specified by the rule.
FDD Dynamic CellAlgoSwit DRX and Smart control for dynamic

TDD DRX ch.DynDrxSw Signaling DRX depends on the dynamic
itch Control DRX function.
When the cell traffic load
meets the trigger condition for
the rule correlated to the
function, the parameter
settings are adjusted as
specified by the rule.

(2020-12-29)
eRAN

Name Switch e
FDD Intelligent ● ACBAR_S Access When the cell load meets the
TDD access WITCH_DY Class trigger condition of an
class NAMIC Control intelligent optimization rule in
control option of the intelligent optimization
the function intelligent AC control,
CellAlgoS the eNodeB automatically
witch.AcB adjusts the parameter settings
arAlgoSwi based on the related
tch intelligent optimization rule.
parameter An intelligent optimization
● DYNAMIC_ rule takes effect only when
FOR_MO the corresponding license
option of control item is available.
the
CellAlgoS
witch.AcB
arAlgofor
DynSwitch
parameter
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
4.3.4 Others
None
4.4 Operation and Maintenance
4.4.1 Data Configuration

(2020-12-29)
eRAN
4.4.1.1 Data Preparation

NOTE
● A set of intelligent optimization rules for ACH has been predefined on the eNodeB. You
only need to activate the feature license and set the feature switch.
● The following intelligent optimization functions are deactivated by default: T302
optimization, penalty for abnormal UE access, intelligent AC control, limitation on
PUSCH power, and immunity of PUCCH to interference. Activate them in advance if
required.
Table 4-8 and Table 4-9 describe the parameters used for function activation and
optimization, respectively.
Table 4-8 Parameters used for activation
Parameter Name Parameter ID Setting Notes
Intelligent Optimization ENodeBAlgoSwitch.IOp It is recommended that

Algorithm Switch tAlgoSwitch the ACHSwitch option be
selected for eNodeBs on
which congestion is easy
to occur.
ACH Effective Type ParaAutoOptCfg.AchEff It is recommended that

ectiveType the FDD_ACH_SWITCH
option be selected for
eNodeBs on which
congestion is easy to
occur.
Heavy Load Performance CellAlgoExtSwitch.Heav It is recommended that

Optimization Switch yLoadPrfmOptSwitch the
UL_RS_PWR_ADAPT_SW
option be selected if the
inter-cell distance is short
and the load is heavy.
Table 4-9 Parameters used for optimization
Rule ID LIOptRule.RuleID Retain the default values.
Period LIOptRule.Period
Penalty Time LIOptRule.PenaltyTime
Adaptive RAT LIOptRule.AdaptiveRAT
Atom Rule ID LIOptAtomRule.AtomR Retain the default values.

uleID
Threshold for Numerical LIOptAtomRule.Thresh
Parameter oldforNumPara

(2020-12-29)
eRAN
Rule ID LIOptRuleMember.Rule Retain the default values.

ID
Atom Rule ID LIOptRuleMember.Ato
mRuleID
Active Status LIOptRuleMember.Acti
veStatus
PUSCH RSRP High ParaAutoOptCfg.PUSC This parameter is used
Threshold for Auto HRsrpHighThd4AutoOp for limitation on PUSCH
Optimization t power.
If this parameter is set to
a smaller value, it is more
difficult for the uplink
RSRP to reach the
maximum value in uplink
interference scenarios,
and the uplink
throughput becomes
lower when the uplink
RSRP does not reach the
maximum value. A larger
value causes the opposite
effect.
If the
UL_COORD_PC_SWITCH
option of the
UlCsAlgoPara.UlCsSw
parameter is selected,
you are advised to set the
ParaAutoOptCfg.PUSCH
RsrpHighThd4AutoOpt
parameter of limitation
on PUSCH power to a
value greater than or
equal to -82 dBm.

(2020-12-29)
eRAN
PUCCH PC SINR Offset ParaAutoOptCfg.PUCC This parameter is used

for Auto Optimization HPcSINROffset4AutoO for immunity of PUCCH
pt to interference.
a smaller value, the
PUCCH transmit power of
UEs in a cell becomes
lower, therefore
generating less
interference to other UEs
in the cell and UEs in
neighboring cells. A
larger value causes the
opposite effect.
P0 Nominal PUCCH for ParaAutoOptCfg.P0No This parameter is used

Auto Opt minalPUCCH4AutoOpt for immunity of PUCCH
to interference.
a larger value,
interference to
neighboring cells
becomes stronger and
the total throughput of
the network decreases. If
this parameter is set to a
smaller value,
interference to
neighboring cells
becomes weaker but the
throughput in the local
cell decreases.

(2020-12-29)
eRAN
Handover Times ParaAutoOptCfg.HOTi This parameter is used

Threshold mesThd for limitation on PUSCH
power and immunity of
PUCCH to interference.
a smaller value, excessive
collaborative neighboring
cells are available, which
may include neighboring
cells with minor mutual
interference. In this case,
the uplink throughput of
the cells with light load
decreases. If this
parameter is set to a
larger value, collaborative
neighboring cells are
insufficient. Consequently,
cells with heavy load
cannot obtain
performance gains from
ACH.

(2020-12-29)
eRAN
A3 based Interfreq A2 InterFreqHoGroup.A3In This parameter is used

RSRP threshold terFreqHoA2ThdRsrp for intelligent increase in
the A1 threshold.
A smaller value of this
parameter results in a
lower probability of
triggering event A2 and a
starting inter-frequency
measurements. A larger
value of this parameter
results in the opposite
effects.
After intelligent increase
in the A1 threshold takes
effect, the
A3InterFreqHoA1ThdRsr
p parameter value will be
changed to the sum of
p and 6 dBm. A smaller
value of the
p parameter results in a
higher probability of
triggering event A1 and
stopping inter-frequency
measurements. In this
case, due to signal
fluctuation, the
measurement
configuration is delivered
and then deleted
repeatedly, and ACH
optimization measures
cannot offer gains. A
larger value of the
p parameter results in a
measurements. This
reduces the probability
that the measurement
and then deleted
repeatedly due to signal
fluctuation.

(2020-12-29)
eRAN
A4A5 Based Interfreq A2 InterFreqHoGroup.Inter This parameter is used

RSRP Threshold FreqHoA2ThdRsrp for intelligent increase in
the A1 threshold.
A smaller value of this
triggering event A2 and a
starting inter-frequency
measurements. A larger
value of this parameter
results in the opposite
effects.
After intelligent increase
in the A1 threshold takes
effect, the
InterFreqHoA1ThdRsrp
parameter value will be
changed to the sum of
and 6 dBm. A smaller
value of the
higher probability of
measurements. In this
case, due to signal
fluctuation, the
measurement
and then deleted
repeatedly, and ACH
optimization measures
cannot offer gains. A
larger value of the
measurements. This
reduces the probability
that the measurement
and then deleted
repeatedly due to signal
fluctuation.

(2020-12-29)
eRAN
4.4.1.2 Using MML Commands
Activation Command Examples

Enabling ACH for both FDD and TDD cells
MOD ENODEBALGOSWITCH: IOptAlgoSwitch=ACHSwitch-1;
Enabling ACH only for FDD cells

MOD PARAAUTOOPTCFG: AchEffectiveType=FDD_ACH_SWITCH-1;
Enabling uplink RS power adaptation for a LampSite cell

MOD CELLALGOEXTSWITCH: HeavyLoadPrfmOptSwitch=UL_RS_PWR_ADAPT_SW-1;
Optimization Command Examples

After ACH is enabled, operators can activate, deactivate, and modify intelligent
optimization rules, and mask and modify atom rules of intelligent optimization
rules.
//(Optional) Activating an intelligent optimization rule of ACH
LST LIOPTRULE: RuleID=3;
ACT LIOPTRULE: RuleID=3;
//(Optional) Deactivating an intelligent optimization rule of ACH

DEA LIOPTRULE: RuleID=3;
//(Optional) Modifying intelligent optimization rule 3 with Period set to 200, Penalty Time set to 100, and
Adaptive RAT set to FDD
MOD LIOPTRULE: RuleID=3, Period=200, PenaltyTime=100, AdaptiveRAT=FDD;
//(Optional) Masking an atom rule of an intelligent optimization rule

LST LIOPTRULEMEMBER: AtomRuleID=1, RuleID=1;
MOD LIOPTRULEMEMBER: RuleID=1, AtomRuleID=1, ActiveStatus=DEACTIVATED;
//(Optional) Modifying an atom rule of an intelligent optimization rule with Threshold for Numerical
Parameter set to 30
LST LIOPTRULEMEMBER: AtomRuleID=1, RuleID=1;
LST LIOPTATOMRULE: AtomRuleID=1;
MOD LIOPTATOMRULE: AtomRuleID=1, ThresholdforNumPara=30;
After ACH is enabled, operators can tune parameters related to ACH according to
the actual application effect of the live network, so as to achieve optimal network
performance.
//(Optional) Modifying the ACH algorithm configurations with PUSCH RSRP High Threshold for Auto
Optimization set to -90 and Handover Times Threshold set to 20
LST PARAAUTOOPTCFG:;
MOD PARAAUTOOPTCFG: PUSCHRsrpHighThd4AutoOpt=-90, HOTimesThd=20;
Deactivation Command Examples

Disabling ACH for both FDD and TDD cells
MOD PARAAUTOOPTCFG: AchEffectiveType=FDD_ACH_SWITCH-0&TDD_ACH_SWITCH-0;
Disabling ACH only for FDD cells

(2020-12-29)
eRAN

MOD PARAAUTOOPTCFG: AchEffectiveType=FDD_ACH_SWITCH-0&TDD_ACH_SWITCH-1;
Disabling uplink RS power adaptation for a LampSite cell

MOD CELLALGOEXTSWITCH: HeavyLoadPrfmOptSwitch=UL_RS_PWR_ADAPT_SW-0;
4.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.
4.4.2 Activation Verification

Method 1: SON Logs
On the MAE-Access, select LTE Automatic Congestion Handling Log to view the
SON logs. This function has taken effect if the following logs that contain specific
information are displayed:
● Set Automatic Congestion Handling Switch
● Modify Cell-level Runtime Parameters
● Recover Cell-level Runtime Parameters
● Modify eNodeB-level Runtime Parameters
● Recover eNodeB-level Runtime Parameters
Method 2: MML Commands

ACH modifies the running values of parameters, instead of the configured values
in the database. In this situation, the running values may differ from the
configured values. You can query the configured values of the parameters by
running correlated LST commands and perform the following step to query the
running values:
Run the DSP LIOPTRULE command to view the values of Action Type, Action,
Local Cell ID, and Executive Status for a specific intelligent optimization rule.
Check the intelligent optimization rules for which the value of Action Type is
MODIFY. If the value of Executive Status for an intelligent optimization rule is:
● UN-EXECUTED or EXECUTING
The parameter value in use is the same as the configured value. In this
situation, run the corresponding LST command to query the configured value,
which is also the current value in use for that parameter.
● EXECUTED
The parameter value has been changed. In addition, if the value of Action
Type is MODIFY, you can check whether the parameter value in use is the
same as the target value of the change by running the MML command in the
Action field.
The fields in the command output of DSP LIOPTRULE are as follows:
● Action Type
The value can be either MODIFY or RESUME. If it is MODIFY, the intelligent
optimization rule is used to change parameter values. If it is RESUME, the

(2020-12-29)
eRAN
intelligent optimization rule is used to restore parameter values to the

originally configured values.
● Action
This indicates which and how parameters are modified when an intelligent
optimization rule applies. This field does not take effect if Action Type is set
to RESUME.
● Local Cell ID
This indicates the ID of the cell to which intelligent optimization rules are
applied. This field does not take effect for eNodeB-level intelligent
optimization rules.
● Executive Status
The value can be UN-EXECUTED, EXECUTING, and EXECUTED. UN-
EXECUTED indicates that the intelligent optimization rule has not been
executed. EXECUTING indicates that the intelligent optimization rule is being
executed. EXECUTED indicates that the intelligent optimization rule has been
executed.
4.4.3 Network Monitoring

When individual optimization functions are activated, view the automatic
operations (specified by intelligent optimization functions), and monitor the
feature performance. The feature performance can be monitored through key
performance indicators (KPIs), such as PRB usage, PDCCH CCE usage, uplink and
downlink cell throughput, uplink and downlink UE throughput, and RRC setup
success rate.
● Monitoring KPIs
Table 4-10 Monitoring KPIs
KPIs Used in Calculation Formula Note

Performance
Monitoring
DL PRB usage L.ChMeas.PRB.DL.Used.Avg/ These KPIs

L.ChMeas.PRB.DL.Avail are only
used for
UL PRB usage L.ChMeas.PRB.UL.Used.Avg/ monitoring
L.ChMeas.PRB.UL.Avail resource
PDCCH CCE FDD: (L.ChMeas.CCE.CommUsed + usage and
usage L.ChMeas.CCE.ULUsed + are not
L.ChMeas.CCE.DLUsed)/(Number of CCEs used for
per TTI when the maximum number of evaluating
fixed PDCCH symbols is used x Number of gains.
TTIs in a measurement period)
DL cell L.Thrp.bits.DL/ These KPIs

throughput L.Thrp.Time.Cell.DL.HighPrecision are used
for
UL cell L.Thrp.bits.UL/ observing
throughput L.Thrp.Time.Cell.UL.HighPrecision

(2020-12-29)
eRAN
KPIs Used in Calculation Formula Note

Performance
Monitoring
DL user (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI)/ function

throughput L.Thrp.Time.DL.RmvLastTTI gains.
UL user (L.Thrp.bits.UL -
throughput L.Thrp.bits.UE.UL.SmallPkt)/
L.Thrp.Time.UE.UL.RmvSmallPkt
RRC setup L.RRC.ConnReq.Succ/L.RRC.ConnReq.Att

success rate
PUSCH L.UL.Interference.Avg These KPIs

interference are only
used for
PUCCH (L.UL.Interference.PUCCH.Index0 x Intf (0) monitoring
interference + L.UL.Interference.PUCCH.Index1 x Intf uplink
(1) +...+ L.UL.Interference.PUCCH.Index15 interferenc
x Intf (15))/ e and are
(L.UL.Interference.PUCCH.Index0 + not used
L.UL.Interference.PUCCH.Index1 +...+ for
L.UL.Interference.PUCCH.Index15) evaluating
gains.
Average CPU VS.BBUBoard.CPULoad.Mean This KPI is

load only used
for
monitoring
average
CPU usage
of a board
and is not
used for
evaluating
gains.
Table 4-11 lists the counters used for calculating the KPIs in Table 4-10.
Table 4-11 Counters used in KPI calculation
Counter ID Counter Name
1526726737 L.ChMeas.PRB.UL.Used.Avg
1526726740 L.ChMeas.PRB.DL.Used.Avg
1526728434 L.ChMeas.PRB.UL.Avail
1526728433 L.ChMeas.PRB.DL.Avail
1526728303 L.ChMeas.CCE.CommUsed

(2020-12-29)
eRAN
Counter ID Counter Name
1526728304 L.ChMeas.CCE.ULUsed
1526728305 L.ChMeas.CCE.DLUsed
1526728261 L.Thrp.bits.DL
1526728259 L.Thrp.bits.UL
1526728997 L.Thrp.Time.Cell.DL.HighPrecision
1526728998 L.Thrp.Time.Cell.UL.HighPrecision
1526729005 L.Thrp.bits.DL.LastTTI
1526729015 L.Thrp.Time.DL.RmvLastTTI
1526729415 L.Thrp.bits.UE.UL.SmallPkt
1526729416 L.Thrp.Time.UE.UL.RmvSmallPkt
1526726658 L.RRC.ConnReq.Att
1526726659 L.RRC.ConnReq.Succ
1526728298 L.UL.Interference.Avg
1526734061 to L.UL.Interference.PUCCH.Index0 to
1526734076 L.UL.Interference.PUCCH.Index15
1593835634 VS.BBUBoard.CPULoad.Over
1526728465 L.Signal.Num.Uu
● Using the SON logs

For detailed operations, see 4.4.2 Activation Verification.

(2020-12-29)
eRAN
Description 5 Parameters
5 Parameters
The following hyperlinked EXCEL files of parameter documents match the

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

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

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

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

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

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

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

(2020-12-29)
eRAN
Description 7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

(2020-12-29)
eRAN
Description 8 Reference Documents
8 Reference Documents
1. Scheduling
2. Access Class Control
3. DRX and Signaling Control
4. Carrier Aggregation
5. Uplink Coordinated Scheduling

(2020-12-29)

Automatic Congestion Handling Feature Parameter Description: Issue Date

Uploaded by

Copyright:

Available Formats

Automatic Congestion Handling Feature Parameter Description: Issue Date

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Automatic Congestion Handling Feature Parameter Description: Issue Date

Uploaded by

Copyright:

Available Formats

eRAN

Automatic Congestion Handling

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

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

Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

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

1.1 eRAN17.1 Draft A (2020-12-29)

Canceled the None FDD BTS3911E

Deleted the Deleted the FDD ● 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

● The technical principles of features and their related parameters

2.2 Applicable RAT

2.3 Features in This Document

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 3

Feature ID Feature Name Chapter/Section

LOFD-081205 Automatic 4 Automatic Congestion Handling

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 4

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 5

4 Automatic Congestion Handling

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 6

Figure 4-1 ACH architecture

4.1.2 ACH Procedure

Figure 4-2 ACH procedure

The eNodeB determines whether to trigger intelligent optimization functions

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 7

4.1.2.1 Data Collection

Table 4-1 Required measurement items and their calculation formulas

User_Spec_Occupy_ L.Traffic.User.Ulsync.Avg/Maximum number of UL-sync

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 8

Measurement Calculation Formula

PDCCH_CCE_Utiliza FDD: (L.ChMeas.CCE.CommUsed +

ENB_USER_SPEC_E Max{User_Spec_Occupy_Rate (Cell0),

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 9

Measurement Calculation Formula

PUCCH IN (L.UL.Interference.PUCCH.Index0 x Intf(0) +

EQV_BW_SF_ULSYN Number of UL-sync UEs x 20/(Uplink bandwidth

RL_EQV_BW_SF_UL Number of UL-sync UEs with equivalent bandwidths and

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 10

CELL_TDD SA0 0.6

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 11

number of PDCCH symbols is 3. PHICHCfg.PhichResource is equivalent to Ng in

Bandwidth (MHz) 20 15 10 5 3 1.4

4.1.2.2 Trigger Condition Judgment

4.1.2.3 Intelligent Optimization Functions and Parameter Adjustment

Table 4-5 Intelligent optimization functions and corresponding IDs

Optimization Function Intelligent Optimization Function

Abnormal UE detection and scheduling 2

Smart control for downlink frequency 3

Adaptive RBG allocation 4

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 12

Optimization Function Intelligent Optimization Function

Downlink non-GBR packet bundling 5