Multi-Carrier Unified Scheduling (eRAN19.1 - 07)

eRAN
Multi-carrier Unified Scheduling

Feature Parameter Description
Issue 07
Date 2024-01-05
HUAWEI TECHNOLOGIES CO., LTD.

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

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

Security Declaration
Vulnerability
Huawei's regulations on product vulnerability management are subject to the Vul. Response Process. For
details about this process, visit the following web page:
https://www.huawei.com/en/psirt/vul-response-process
For vulnerability information, enterprise customers can visit the following web page:
https://securitybulletin.huawei.com/enterprise/en/security-advisory
Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
Multi-carrier Unified Scheduling Feature Parameter
Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN19.1 07 (2024-01-05)..................................................................................................................................................1
1.2 eRAN19.1 06 (2023-11-30)..................................................................................................................................................1
1.3 eRAN19.1 05 (2023-09-27)..................................................................................................................................................2
1.4 eRAN19.1 04 (2023-08-23)..................................................................................................................................................3
1.5 eRAN19.1 03 (2023-06-29)..................................................................................................................................................3
1.6 eRAN19.1 02 (2023-04-28)..................................................................................................................................................4
1.7 eRAN19.1 01 (2023-03-09)..................................................................................................................................................5
1.8 eRAN19.1 Draft A (2022-12-30)........................................................................................................................................ 6
2 About This Document.............................................................................................................8

2.1 General Statements................................................................................................................................................................ 8
2.2 Applicable RAT......................................................................................................................................................................... 9
2.3 Features in This Document.................................................................................................................................................. 9
2.4 Feature Differences Between FDD and TDD............................................................................................................... 12
3 Overview................................................................................................................................. 14
4 Multi-carrier Unified Scheduling....................................................................................... 16
4.1 Principles.................................................................................................................................................................................. 16
4.1.1 Virtual Grid Function........................................................................................................................................................ 16
4.1.1.1 Virtual Grid Model Building........................................................................................................................................17
4.1.1.2 Virtual Grid Model Updating..................................................................................................................................... 24
4.1.1.3 Switches for the Virtual Grid Function................................................................................................................... 25
4.1.1.4 Conditions for Using Virtual Grid Models..............................................................................................................27
4.1.1.5 Relationship Between Virtual Grid Models and Handovers............................................................................ 29
4.1.2 Smart Carrier Selection................................................................................................................................................... 30
4.1.2.1 Smart Carrier Selection Scenarios and Procedures............................................................................................ 33
4.1.2.2 Carrier or Carrier Combination Priority Factors and Selection.......................................................................44
4.1.3 Ultra-Low-Latency Scheduling for Intra-eNodeB CA............................................................................................ 51
4.1.3.1 Delayed SCell Deactivation......................................................................................................................................... 51
4.1.3.2 Data Split with Ultra-Low Latency...........................................................................................................................52
4.1.4 Ultra-Low-Latency Scheduling for Inter-eNodeB CA Based on Relaxed Backhaul..................................... 53
4.1.5 Multi-Frequency Optimal Carrier Scheduling.......................................................................................................... 54
4.2 Network Analysis.................................................................................................................................................................. 55
Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
Description Contents
4.2.1 Benefits................................................................................................................................................................................. 55
4.2.2 Impacts.................................................................................................................................................................................. 57
4.2.2.1 Smart Carrier Selection................................................................................................................................................ 57
4.2.2.2 Ultra-Low-Latency Scheduling for Intra-eNodeB CA......................................................................................... 70
4.2.2.3 Ultra-Low-Latency Scheduling for Inter-eNodeB CA Based on Relaxed Backhaul..................................73
4.2.2.4 Multi-Frequency Optimal Carrier Scheduling...................................................................................................... 74
4.3 Requirements......................................................................................................................................................................... 77
4.3.1 Licenses................................................................................................................................................................................. 77
4.3.2 Software................................................................................................................................................................................78
4.3.2.1 Smart Carrier Selection................................................................................................................................................ 78
4.3.2.2 Ultra-Low-Latency Scheduling for Intra-eNodeB CA......................................................................................... 79
4.3.2.3 Ultra-Low-Latency Scheduling for Inter-eNodeB CA Based on Relaxed Backhaul..................................79
4.3.2.4 Multi-Frequency Optimal Carrier Scheduling...................................................................................................... 80
4.3.3 Hardware.............................................................................................................................................................................. 83
4.3.4 Networking.......................................................................................................................................................................... 83
4.3.5 Others.................................................................................................................................................................................... 84
4.4 Operation and Maintenance............................................................................................................................................. 84
4.4.1 Data Configuration........................................................................................................................................................... 84
4.4.1.1 Data Preparation............................................................................................................................................................ 84
4.4.1.2 Using MML Commands............................................................................................................................................... 92
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 95
4.4.2 Activation Verification......................................................................................................................................................95
4.4.3 Network Monitoring......................................................................................................................................................... 96
5 Parameters.............................................................................................................................. 97
6 Counters.................................................................................................................................. 98
7 Glossary................................................................................................................................... 99
8 Reference Documents........................................................................................................ 100
Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. iv

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

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

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Added descriptions of the impact relationships between smart carrier selection
based on virtual grids and energy saving functions. For details, see 4.2.2.1 Smart
Carrier Selection.
Added descriptions of the impact relationships between ultra-low-latency
scheduling for intra-eNodeB CA and the following functions: energy saving based
on proactive scheduling and precise Scheduling for CA UEs. For details, see 4.2.2.2
Ultra-Low-Latency Scheduling for Intra-eNodeB CA.
Revised descriptions of the impact relationships between multi-frequency optimal
carrier scheduling and the downlink scheduling policy. For details, see 4.2.2.4
Multi-Frequency Optimal Carrier Scheduling.
Added descriptions of the network impacts of smart carrier selection based on
virtual grids. For details, see 4.2.2.1 Smart Carrier Selection.
1.2 eRAN19.1 06 (2023-11-30)

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Technical Changes
None
Editorial Changes
Corrected the criteria for determining the traffic volumes of a UE in event-
triggered carrier selection (triggered by traffic model changes). For details, see
Event-triggered Carrier Selection (Triggered by Traffic Model Changes).
Revised the descriptions of the impact relationship between smart carrier selection
based on virtual grids and frequency-priority-based inter-frequency handover. For
details, see 4.2.2.1 Smart Carrier Selection.
For FDD, added recommendations on the functions to be enabled together with

the Multi-carrier Unified Scheduling feature. For details, see 4.2.1 Benefits.
Corrected the RAT of the prerequisite function "scheduling priority optimization

for CA" in Multi-Frequency Optimal Carrier Scheduling. For details, see 4.3.2.4
Multi-Frequency Optimal Carrier Scheduling.
Added descriptions related to cell load in "Carrier or Carrier Combination Priority

Factors". For details, see 4.1.2.2 Carrier or Carrier Combination Priority Factors
and Selection.
1.3 eRAN19.1 05 (2023-09-27)

Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added support for Activated the BIT2 option FDD ● 3900 and 5900
prohibition of smart of the TDD series base
carrier selection eNBCellRsvdPara.RsvdSw stations (macro
triggered by inter- Para10 parameter. base stations)
frequency event A2 ● DBS3900
for non-CA UEs under LampSite and
weak coverage. For DBS5900
details, see Event- LampSite
triggered Carrier
Selection (Triggered
by Event A1 or A2)
in 4.1.2.1 Smart
Carrier Selection
Scenarios and
Procedures.

eRAN
Editorial Changes
Added setting notes and MML command examples for the
TRAFFIC_AWARENESS_SCS_OPT_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter. For details, see
4.4.1.1 Data Preparation and 4.4.1.2 Using MML Commands.
Added the description that the eNodeB delivers event A4 measurement
configurations to a non-CA UE if the strongest inter-frequency neighboring cell
predicted using virtual grid models is an unknown neighboring cell. For details, see
4.1.1.4 Conditions for Using Virtual Grid Models.
Added descriptions of the network impacts of smart carrier selection based on
virtual grids. For details, see 4.2.2.1 Smart Carrier Selection.
Added descriptions of prohibition of SCell configuration triggered by inter-
frequency event A2 for CA UEs under weak coverage. For details, see Event-
triggered Carrier Selection (Triggered by Event A1 or A2) in 4.1.2.1 Smart
Carrier Selection Scenarios and Procedures.
1.4 eRAN19.1 04 (2023-08-23)

Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Revised the descriptions of the network impact of "ultra-low-latency scheduling
for intra-eNodeB CA". For details, see 4.2.2.2 Ultra-Low-Latency Scheduling for
Intra-eNodeB CA.
Revised the setting notes for the AI_ENHANCEMENT_OPT_SWITCH option of the
eNodeBResModeAlgo.ServiceMode parameter. For details, see 4.4.1.1 Data
Preparation.
1.5 eRAN19.1 03 (2023-06-29)


eRAN
Technical Changes
Model
Added prohibition of Activated the BIT13 option FDD ● 3900 and 5900
smart carrier selection of the TDD series base
for UEs that have eNBRsvdPara.RsvdSwPara stations (macro
accessed local cells 7 parameter. base stations)
through RRC ● DBS3900
connection LampSite and
reestablishments. For DBS5900
details, see 4.1.1.1 LampSite
Virtual Grid Model
Building and 4.1.2
Smart Carrier
Selection.
Added support for the Modified parameter: FDD ● 3900 and 5900
multi-carrier unified Added the series base
scheduling for CA UBBPD_SCH_FUNCTION_ stations (macro
function by the ENH_SWITCH option to base stations)
UBBPd. For details, the ● DBS3900
see 4.1.5 Multi- EnodebAlgoExtSwitch.Ne LampSite and
Frequency Optimal tworkPrfmOptSwitch DBS5900
Carrier Scheduling parameter. LampSite
and 4.3.3 Hardware.
Editorial Changes
Added descriptions of the benefits of the multi-frequency optimal carrier
scheduling function. For details, see 4.2.1 Benefits.
Added descriptions of the impact relationship between smart carrier selection
based on virtual grids and low power consumption mode. For details, see 4.2.2.1
Smart Carrier Selection.
1.6 eRAN19.1 02 (2023-04-28)


eRAN
Technical Changes
Model
Added support for cell Activated reserved FDD ● 3900 and 5900
capability adjustment parameters: TDD series base
during smart carrier ● eNBRsvdPara.RsvdPara stations (macro
selection when PCI- 62 base stations)
modulo-3 results of ● DBS3900
involved cells are the ● eNBCellRsvdPara.Rsvd
U8Para67 LampSite and
same. For details, see DBS5900
4.1.2.2 Carrier or LampSite
Carrier Combination
Priority Factors and
Selection.
Optimized the Added the FDD ● 3900 and 5900

cooperation between MultiCarrUnifiedSch.FssP series base
multi-carrier unified rbRatioThld parameter. stations (macro
scheduling for CA and base stations)
frequency selective ● DBS3900
scheduling. For LampSite and
details, see 4.2.2.4 DBS5900
Multi-Frequency LampSite
Optimal Carrier
Scheduling.
Editorial Changes
Added the feature ID and feature name of the TDD feature TDLNOFD-19150601
Multi-Frequency Optimal Carrier Scheduling. For details, see 2.3 Features in This
Documentand 2.4 Feature Differences Between FDD and TDD.
1.7 eRAN19.1 01 (2023-03-09)

Technical Changes
None
Editorial Changes
Added descriptions of the impact relationships between multi-carrier unified

scheduling for CA and the following functions. For details, see 4.2.2.4 Multi-
Frequency Optimal Carrier Scheduling.

eRAN
● Dynamic power sharing between LTE carriers

● Extreme power sharing
● Downlink frequency selective scheduling
● CCE-usage-based downlink data split for CA UEs
● Downlink MU-MIMO
1.8 eRAN19.1 Draft A (2022-12-30)

This issue introduces the following changes to eRAN18.1 03 (2022-08-25).
Technical Changes
Model
Added support for Modified parameter: FDD ● 3900 and 5900

QCI-based selection Added the TDD series base
of UEs for which SCS_FORBID_SW option stations (macro
smart carrier selection to the base stations)
is not allowed. For QciPara.AggregationAttri ● DBS3900
details, see: bute parameter. LampSite and
● 4.1.1.1 Virtual DBS5900
Grid Model LampSite
Building
● 4.1.2 Smart
Carrier Selection
Optimized the criteria Modified parameter: FDD ● 3900 and 5900

for determining traffic Added the TDD series base
models for event- FAST_TRAFFIC_AWARENE stations (macro
triggered carrier SS_SCS_SW option to the base stations)
selection (triggered MultiCarrUnifiedSch.Mult ● DBS3900
by traffic model iCarrierUnifiedSchEnSw LampSite and
changes). For details, parameter. DBS5900
see Event-triggered Added the LampSite
Carrier Selection CellMultiCarrUniSch.Traff
(Triggered by Traffic icModeExitPeriodNum
Model Changes) in parameter.
4.1.2.1 Smart Carrier
Selection Scenarios
and Procedures.

eRAN

Model
Added multi-carrier Modified parameter: FDD ● 3900 and 5900

unified scheduling for Added the TDD series base
CA to Multi- CA_MULTI_CARR_UNIFIED stations (macro
Frequency Optimal _SCH_SW option to the base stations)
Carrier Scheduling. MultiCarrUnifiedSch.Mult ● DBS3900
For details, see 4.1.5 iCarrierUnifiedSchEnSw LampSite and
Multi-Frequency parameter. DBS5900
Optimal Carrier LampSite
Scheduling.
Replaced the reserved Modified parameter: FDD ● 3900 and 5900

parameter used to Added BIT3 of the TDD series base
prohibit delayed eNBCellRsvdPara.RsvdSw stations (macro
deactivation of inter- Para8 parameter to the base stations)
eNodeB SCells added parameter disuse list and ● DBS3900
based on relaxed replaced it with the LampSite and
backhaul with a INB_SCELL_DLY_DEACTV_ DBS5900
formal parameter. For FORBID_SW option of the LampSite
details, see 4.1.3.1 CellMultiCarrUniSch.Cell
Delayed SCell MultiCarrUnifiedSchSw
Deactivation. parameter.
Added support for None TDD ● 3900 and 5900

scheduling priority series base
optimization for CA in stations (macro
TDD. For details, see base stations)
4.1.5 Multi- ● DBS3900
Frequency Optimal LampSite and
Carrier Scheduling. DBS5900
LampSite
Editorial Changes
Revised descriptions of virtual grid model indexes. For details, see 4.1.1.1 Virtual
Grid Model Building.
Revised descriptions of the handling related to UE handover. For details, see
Special Handling of UE Handovers in 4.1.2.1 Smart Carrier Selection Scenarios
and Procedures.
Revised descriptions of the application scenarios of short-cycle carrier selection.
For details, see Periodic Carrier Selection in 4.1.2.1 Smart Carrier Selection
Scenarios and Procedures.

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 optimal gains, contact Huawei professional service engineers.
Functions mentioned in this document work properly only when enabled in the
specified applicable scenarios (such as RAT and networking). If a function not
mentioned in this document is enabled or a function is enabled in a scenario not
specified as applicable, exceptions or other impacts may occur.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a
description does not apply to all RATs, the specific RAT that it does apply to will
be stated.

eRAN
For example, in the statement "TDD cells are compatible with enhanced MU-
MIMO", "TDD cells" indicates that this function cannot be used in non-TDD cells.
2.2 Applicable RAT

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

This document describes the following FDD features.
Feature ID Feature Name Chapter/Section
LNOFD-15133 Multi-carrier Unified See the corresponding sections of the

2 Scheduling subfeatures.
LNOFD-15133 Smart Carrier Selection 4.1.1 Virtual Grid Function

201 Based on Virtual Grids 4.1.2 Smart Carrier Selection
4.2.1 Benefits
4.2.2.1 Smart Carrier Selection
4.3.1 Licenses
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others
4.4 Operation and Maintenance
LNOFD-16133 Ultra-Low-Latency 4.1.3 Ultra-Low-Latency Scheduling

203 Scheduling for Intra-eNodeB CA
4.2.1 Benefits
4.2.2.2 Ultra-Low-Latency
Scheduling for Intra-eNodeB CA
4.3.1 Licenses
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others

eRAN
LNOFD-18130 Ultra-Low-Latency 4.1.4 Ultra-Low-Latency Scheduling

201 Scheduling for Inter- for Inter-eNodeB CA Based on
eNodeB CA Based on Relaxed Backhaul
Relaxed Backhaul 4.2.1 Benefits
Scheduling for Inter-eNodeB CA
Based on Relaxed Backhaul
4.3.1 Licenses
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others
LNOFD-18130 Multi-Frequency 4.1.5 Multi-Frequency Optimal

202 Optimal Carrier Carrier Scheduling
Scheduling 4.2.1 Benefits
4.2.2.4 Multi-Frequency Optimal
Carrier Scheduling
4.3.1 Licenses
Carrier Scheduling
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others
This document describes the following TDD features.
TDLNOFD-151 Multi-carrier Unified See the corresponding sections of the

506 Scheduling subfeatures.

eRAN
TDLNOFD-151 Smart Carrier 4.1.1 Virtual Grid Function

50601 Selection Based on 4.1.2 Smart Carrier Selection
Virtual Grids
4.2.1 Benefits
4.3.1 Licenses
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others
TDLNOFD-161 Ultra-Low-Latency 4.1.3 Ultra-Low-Latency Scheduling

50601 Scheduling for Intra-eNodeB CA
4.2.1 Benefits
4.3.1 Licenses
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others
TDLNOFD-181 Ultra-Low-Latency 4.1.4 Ultra-Low-Latency Scheduling

50601 Scheduling for Inter- for Inter-eNodeB CA Based on
eNodeB CA Based on Relaxed Backhaul
Relaxed Backhaul 4.2.1 Benefits
4.3.1 Licenses
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others

eRAN
TDLNOFD-191 Multi-Frequency 4.1.5 Multi-Frequency Optimal

50601 Optimal Carrier Carrier Scheduling
Scheduling 4.2.1 Benefits
Carrier Scheduling
4.3.1 Licenses
Carrier Scheduling
4.3.3 Hardware
4.3.4 Networking
4.3.5 Others
2.4 Feature Differences Between FDD and TDD

FDD Feature TDD Feature Difference Chapter/Section
LNOFD-151332 TDLNOFD-15150 None 4 Multi-carrier

Multi-carrier 6 Multi-carrier Unified
Unified Unified Scheduling
Scheduling Scheduling
LNOFD-15133201 TDLNOFD-15150 None 4.1.1 Virtual Grid

Smart Carrier 601 Smart Carrier Function
Selection Based Selection Based 4.1.2 Smart
on Virtual Grids on Virtual Grids Carrier Selection
LNOFD-16133203 TDLNOFD-16150 None 4.1.3 Ultra-Low-

Ultra-Low-Latency 601 Ultra-Low- Latency
Scheduling Latency Scheduling for
Scheduling Intra-eNodeB CA
LNOFD-18130201 TDLNOFD-18150 None 4.1.4 Ultra-Low-

Ultra-Low-Latency 601 Ultra-Low- Latency
Scheduling for Latency Scheduling for
Inter-eNodeB CA Scheduling for Inter-eNodeB CA
Based on Relaxed Inter-eNodeB CA Based on
Backhaul Based on Relaxed Relaxed
Backhaul Backhaul

eRAN
FDD Feature TDD Feature Difference Chapter/Section
LNOFD-18130202 TDLNOFD-19150 On the UBBPd: 4.1.5 Multi-

Multi-Frequency 601 Multi- ● For TDD, multi- Frequency
Optimal Carrier Frequency carrier unified Optimal Carrier
Scheduling Optimal Carrier scheduling for Scheduling
Scheduling CA does not
take effect.
● For FDD, multi-
carrier unified
scheduling for
CA can take
effect.

eRAN
Description 3 Overview
3 Overview
In multi-carrier scenarios, the following factors prevent UEs from continuously

using large bandwidths for transmission, thereby reducing radio resource
efficiency:
● Regarding UE capability, some UEs do not support carrier aggregation (and
therefore are referred to as non-CA UEs) and some UEs that support carrier
aggregation (referred to as CA UEs) cannot aggregate as many carriers as
configured on the network. The differing capabilities for CA affect UE
scheduling.
● Regarding spectral efficiency, the eNodeB does not consider spectral efficiency
when it configures carriers for UEs. As a result, the eNodeB cannot accurately
select optimal carriers for UEs.
● Regarding scheduling delay, inter-carrier data scheduling for CA UEs involves
one or more procedures of secondary cell (SCell) configuration, activation,
and data split.
– Measurement-based SCell configuration takes several seconds to
complete.
– To maintain synchronization between the UE and the eNodeB, SCells are
activated on the UE and eNodeB simultaneously. If the eNodeB sends a
Media Access Control control element (MAC CE) for SCell activation to
the UE in subframe n, then the SCell is activated on the UE and eNodeB
in subframe (n + x). The value of x is stipulated by physical layer
protocols. For FDD, x is equal to 8. For TDD, x is greater than or equal to
8.
– Data distribution from the primary cell (PCell) to an SCell requires
multiple information exchanges between them, increasing the latency.
Multi-carrier Unified Scheduling uses the following functions to address the
preceding issues:
● Virtual grid function: The base station uses the historical data of multiple UEs
as the input and virtual grids as features to explore the mapping in signal
characteristics from the virtual grids in a cell to a frequency. This mapping is
contained in an entity called virtual grid model. Virtual grid models are then
built to eliminate the requirement for measurement gaps and obtain accurate
spectral efficiency of each frequency, resulting in a user-perceived rate as high
as that with a single large-bandwidth carrier. Moreover, the base station can

eRAN
Description 3 Overview
select optimal carriers or carrier combinations for UEs based on the UE-level
spectral efficiency obtained from the models. For details, see 4.1.1 Virtual
Grid Function.
● Smart carrier selection: During initial access of UEs, the base station considers
the bandwidths, load, and virtual-grid-predicted spectral efficiency of different
frequencies to select carriers or carrier combinations that can provide the
maximum downlink throughput for the UEs. Periodic or event-triggered
evaluation is performed for UEs that stay online for a long time, so that the
UEs are always served by the optimal carriers or carrier combinations. For
details, see 4.1.2 Smart Carrier Selection.
● Ultra-low-latency scheduling for intra-eNodeB CA: Delayed SCell deactivation
is supported. It prevents frequent SCell deactivation and activation and
therefore reduces the performance loss caused by SCell activation latency. In
addition, the number of interactions between the PCell and SCells is reduced
to allow for simultaneous scheduling in the PCell and activated SCells. For
details, see 4.1.3 Ultra-Low-Latency Scheduling for Intra-eNodeB CA.
● Ultra-low-latency scheduling for inter-eNodeB CA based on relaxed backhaul:
In the data split process of inter-eNodeB CA based on relaxed backhaul, there
is a relatively long delay before the buffered data is scheduled. Ultra-low-
latency scheduling enables the eNodeB to start data distribution and physical
uplink control channel (PUCCH) resource allocation to the SCells of an
involved CA UE as early as in the transmission time interval (TTI) in which the
buffer for the UE is no longer empty, increasing the user-perceived throughput
of the UE. In addition, a proxy Radio Link Control (RLC) entity can be set up
at each eNodeB serving an SCell of a UE involved in inter-eNodeB CA based
on relaxed backhaul. Each proxy RLC entity distributes data to the MAC layer
of the corresponding inter-eNodeB SCell, preventing inaccurate scheduling
capability estimation caused by the delay. For details, see 4.1.4 Ultra-Low-
Latency Scheduling for Inter-eNodeB CA Based on Relaxed Backhaul.
● Multi-frequency optimal carrier scheduling: This function includes two sub-
functions, scheduling priority optimization for CA and multi-carrier unified
scheduling for CA. For details, see 4.1.5 Multi-Frequency Optimal Carrier
Scheduling.
– In scheduling priority optimization for CA, the base station calculates the
scheduling capability of each carrier for individual CA UEs based on the
spectral efficiency, bandwidth, and load. It maintains a high scheduling
priority of a CA UE on the carrier with the highest scheduling capability
and adjusts the scheduling priorities of the UE on the carriers that do not
have the highest scheduling capability based on the scheduling delay to
prevent the UE from preempting resources of non-CA UEs.
– In multi-carrier unified scheduling for CA, the base station schedules each
CA UE on its primary component carrier (PCC) and secondary component
carriers (SCCs) in a unified manner so that the PCC and SCCs can obtain
the buffered traffic volume in real time and the PCC can allocate PUCCH
resources to the SCCs in real time. This increases scheduling accuracy for
CA UEs on their PCCs and SCCs and improves downlink user experience.

eRAN
Description 4 Multi-carrier Unified Scheduling
4 Multi-carrier Unified Scheduling
4.1 Principles
4.1.1 Virtual Grid Function
Virtual Grids
A virtual grid is a signal grid of a cell. UEs in the same area of a cell normally have
the same radio signal characteristics, including the reference signal received power
(RSRP) and other information of the serving cell and intra-frequency neighboring
cells. Based on the measurements of radio signals, UEs with the same radio
characteristics are categorized as a single group. The base station considers these
UEs to be located in one signal grid, which is referred to as a virtual grid, as
illustrated in Figure 4-1. For example, if the measurement result for a frequency
measured by UE 1 is [(F1-Cell 1, F1-RSRP 1), (F1-Cell 2, F1-RSRP 2), (F1-Cell 3, F1-
RSRP 3), ...] and the measurement result for the same frequency measured by UE
2 is the same as that of UE 1, UE 1 and UE 2 are considered to be in the same
virtual grid (grid 1).
Figure 4-1 Virtual grids

eRAN
Virtual Grid Model

The eNodeB builds virtual grid models based on the mapping from intra-frequency
signal characteristics to inter-frequency signal characteristics measured by previous
UEs in a cell, as illustrated in Figure 4-2.
Figure 4-2 Virtual grid model
Virtual grid models include RSRP prediction models and spectral efficiency
prediction models. The spectral efficiency prediction models are categorized into
intra-frequency models and inter-frequency models. After obtaining a UE's virtual
grid information on a frequency, the eNodeB queries the RSRP prediction model
for a neighboring frequency to quickly predict the RSRP of the UE on this
neighboring frequency. In addition, the eNodeB queries the spectral efficiency
prediction models for target frequencies to quickly predict the spectral efficiency
of the UE on these frequencies.
4.1.1.1 Virtual Grid Model Building

Figure 4-3 shows the process of building virtual grid models.
Figure 4-3 Process of building virtual grid models
The building process is as follows:

eRAN
1. The eNodeB determines the scope of cells and frequencies for which virtual
grid models are to be built. The scope is determined based on the attributes
of the cells and frequencies, and each RSRP prediction model or spectral
efficiency prediction model is identified by an index in the format of [Cell,
Frequency].
The following cells will not be selected for virtual grid model building:
– Cells in which UEs are stationary and therefore handovers are not
involved, such as eMTC-only cells and NB-IoT cells (eMTC and NB-IoT are
short for enhanced Machine Type Communication and Narrowband
Internet of Things, respectively.)
– Cells with multiple physical cell IDs, for example, a single frequency
network (SFN) cell or a cell with the Cell.MultiRruCellFlag parameter
set to BOOLEAN_TRUE
– High-speed-mobility cells, for example, cells with high speed mobility
enabled, cells with ultra high speed mobility enabled, cells with the
PATTERN_ADJ_SWITCH option of the
SectorSplitGroup.SectorSplitSwitch parameter selected, and cells on the
same frequency as those with the BEAM_NUM_ADJ_SWITCH option of
the SectorSplitGroup.SectorSplitSwitch parameter selected
– Cells that can only serve as SCells, where UE admission is not supported
and therefore samples cannot be collected, for example, cells with the
Cell.WorkMode parameter set to DL_ONLY or LAA and cells with the
ForbidCellSiSwitch option of the CellSiMap.SiSwitch parameter selected
– Cells with cell radius greater than 100 km enabled
The following neighboring frequencies will not be selected for virtual grid
model building:
– Frequencies (identified by the EutranInterNFreq.DlEarfcn parameter)
that belong to band 46 and serve licensed assisted access (LAA) cells
– Frequencies for which the VG_MODEL_FORBID_BUILD_FLAG option of
the EutranInterNFreq.AggregationAttribute parameter is selected
– Frequencies for which the FREQ_MEAS_FLAG option of the
EutranInterNFreq.AggregationAttribute parameter is deselected
– Frequencies (identified by the EutranInterNFreq.DlEarfcn parameter) on
each of which at least one cell of the eNodeB is working with the
BEAM_NUM_ADJ_SWITCH option of the
SectorSplitGroup.SectorSplitSwitch parameter selected
The following UEs will not be selected for virtual grid model building:
– UEs for which smart carrier selection is not allowed. When the eNodeB
builds and maintains virtual grid models, it does not collect data of these
UEs, which can be specified based on SPIDs, UE capabilities, or QCIs.
▪ These UEs can be specified based on SPIDs by selecting the

SCS_FORBID_SW option of the SpidCfg.AggregationAttribute
parameter. For details, see Flexible User Steering.
▪ These UEs can be specified based on UE capabilities by selecting the

SCS_FORBID_SW option of the
UeCompat.BlacklistControlExtSwitch2 parameter. For details, see
Terminal Awareness Differentiation.

eRAN
▪ These UEs can be specified based on QCIs by selecting the

SCS_FORBID_SW option of the QciPara.AggregationAttribute
parameter. For a UE running services with multiple QCIs, smart
carrier selection is not allowed as long as the SCS_FORBID_SW
option of the QciPara.AggregationAttribute parameter is selected
for any of the QCIs.
– UEs that have accessed local cells through intra-base-station RRC
connection reestablishments. If the REEST_SCS_FORBID_SW option of
the MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter is
selected, the eNodeB does not collect data of these UEs when it builds
and maintains virtual grid models.
– UEs that have accessed local cells through inter-base-station RRC
connection reestablishments. If the BIT13 option of the
eNBRsvdPara.RsvdSwPara7 parameter is selected, the eNodeB does not
collect data of these UEs when it builds and maintains virtual grid
models.
– Heavy-traffic UEs. As heavy-traffic UEs occupy a significant portion of
traffic on networks, selecting these UEs for data collection may adversely
affect the accuracy of virtual grid models. When the
CellMultiCarrUniSch.VgMdlBuildUlTrafficThld parameter is set to a
non-zero value, the eNodeB does not select heavy-traffic UEs for data
collection when building and maintaining virtual grid models. A UE is
considered to have heavy traffic if its uplink traffic volume exceeds the
CellMultiCarrUniSch.VgMdlBuildUlTrafficThld parameter value or its
downlink traffic volume exceeds the CellDlschAlgo.DlUserDataThld
parameter value.
Virtual grid models occupy a large amount of resources of main control
boards. The switches to be turned on for virtual grid models vary depending
on main control board models. The virtual grid model specifications are listed
in Table 4-1. When the AI_ENHANCEMENT_SWITCH or
AI_ENHANCEMENT_OPT_SWITCH option (for the UMPTe or UMPTga), the
UMPTB_ENHANCEMENT_SWITCH option (for the UMPTb), or the
UMPTG_ENHANCEMENT_SWITCH option (for the UMPTg) of the
eNodeBResModeAlgo.ServiceMode parameter is deselected, running the RST
APP command will delete the successfully built models.

eRAN
Table 4-1 Specifications of virtual grid models

Mai Switch to Be Turned Specifications of Description
n On Virtual Grid Models
Con
trol
Boa
rd
UM UMPTB_ENHANCEM ● If this option is None

PTb ENT_SWITCH option selected, the eNodeB
of the supports 18 RSRP
eNodeBResModeAl- prediction models
go.ServiceMode and 36 spectral
parameter efficiency prediction
models.
● If this option is
deselected, the
eNodeB does not
support RSRP
prediction models or
spectral efficiency
prediction models.
UM AI_ENHANCEMENT_ ● If any of the options The

PTg SWITCH or is selected, the AI_ENHANCEME
a AI_ENHANCEMENT_ eNodeB supports 90 NT_SWITCH and
OPT_SWITCH option RSRP prediction AI_ENHANCEME
of the models and 114 NT_OPT_SWITCH
eNodeBResModeAl- spectral efficiency options of the
go.ServiceMode prediction models. eNodeBResMode
parameter ● If neither of the Algo.ServiceMod
options is selected, e parameter
the eNodeB supports cannot both be
36 RSRP prediction selected.
models but no
spectral efficiency
prediction models.

eRAN

Con
trol
Boa
rd
UM ● If the
PTe AI_ENHANCEMENT_
SWITCH option of
the
eNodeBResModeAl-
go.ServiceMode
parameter is selected,
the eNodeB supports
90 RSRP prediction
models and 114
spectral efficiency
prediction models.
● If the main control
board is working in
LTE&NR (LN) or
GSM&UMTS&LTE&NR
(GULN) mode and
the
AI_ENHANCEMENT_
OPT_SWITCH option
of the
eNodeBResModeAl-
go.ServiceMode
parameter is selected,
the eNodeB supports
18 RSRP prediction
models and 36
spectral efficiency
prediction models.
● If both options are
deselected, the
eNodeB supports 36
RSRP prediction
models but no
spectral efficiency
prediction models.

eRAN

Con
trol
Boa
rd
UM UMPTG_ENHANCEM ● If the option is None

PTg ENT_SWITCH option selected, the eNodeB
of the supports 168 RSRP
eNodeBResModeAl- prediction models
go.ServiceMode and 198 spectral
parameter efficiency prediction
models.
● If the option is
deselected, the
eNodeB supports 90
RSRP prediction
models and 108
spectral efficiency
prediction models.
If the number of virtual grid models to be built exceeds the limit, the models
are prioritized based on the following factors, and then higher-priority models
are selected for building as long as the limit allows.
a. Intra-eNodeB or inter-eNodeB model: If a model is to be built for the
operating frequency of an intra-eNodeB inter-frequency cell, the model is
an intra-eNodeB model, whereas if it is for the operating frequency of an
inter-eNodeB inter-frequency cell, the model is an inter-eNodeB model. If
the INTER_ENB_VG_MDL_PRI_BUILD_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is
deselected, intra-eNodeB models take precedence over inter-eNodeB
models. If this option is selected, inter-eNodeB models take precedence
over intra-eNodeB models.
b. Local cell bandwidth: If a model is to be built for a larger-bandwidth cell,
the model has a higher priority.
c. Neighboring frequency priority: The camping priority is considered. If a
model is to be built for a neighboring frequency with a higher camping
priority, the model has a higher priority.
d. Neighboring frequency bandwidth: If a model is to be built for a larger-
bandwidth neighboring frequency, the model has a higher priority. This
factor applies only to intra-eNodeB models.
Table 4-2 and Table 4-3 provide an example to illustrate how the preceding
factors work when the INTER_ENB_VG_MDL_PRI_BUILD_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is deselected.

eRAN
Table 4-2 An example scenario of virtual grid model building
Cell Frequen Bandwi Neighborin Neighboring Neighboring

cy dth g Frequency Frequency
Frequency Bandwidth Priority
Cell 1 F1 20 MHz F2 10 MHz 6
F3 20 MHz 7
Cell 2 F2 10 MHz F1 20 MHz 7
F3 20 MHz 7
Table 4-3 lists the factors of each candidate model.
Table 4-3 Factors of each candidate model
Candidate Intra- or Local Cell Neighboring Neighboring

Model Index Inter- Bandwidth Frequency Frequency
eNodeB Priority Bandwidth
[Cell 1, F2] Intra-eNodeB 20 MHz 6 10 MHz
[Cell 1, F3] Inter-eNodeB 20 MHz 7 20 MHz
[Cell 2, F1] Intra-eNodeB 10 MHz 7 20 MHz
[Cell 2, F3] Inter-eNodeB 10 MHz 7 20 MHz
These candidate models are sorted in the following descending order of

priority: [Cell 1, F2], [Cell 2, F1], [Cell 1, F3], [Cell 2, F3].
If frequencies are added and the number of virtual grid models has not
reached the limit, models are built for these new frequencies in the sequence
in which the frequency configurations take effect.
2. The eNodeB randomly selects a specific number of UEs in individual cells at a
specific time and collects their measurement reports on target frequencies as
sample data for RSRP prediction model training. In addition, the eNodeB
collects the PRB usage and spectral efficiency of the neighboring cells of the
strongest cell on each target frequency and queries the UEs' reception
capabilities; then it uses the collected data and query results as sample data
for spectral efficiency prediction model training. The eNodeB collects sample
data for at least 24 hours. If only a small amount of sample data is collected
for building a model and the number of consecutive building times has
reached the maximum, the eNodeB waits for 28 days before it tries to build
the model again.
NOTE
The eNodeB does not build virtual grid models within 14 days of an eNodeB software
upgrade. However, models built before the upgrade can still be used during this
period. After the 14 days, the eNodeB restarts the model building process.

eRAN
3. When data collection is complete, the eNodeB starts the model training
process and calculates the accuracy of each model.
4. The eNodeB checks the model accuracy to evaluate whether the conditions
for launching models are met. If the accuracy of an RSRP prediction model
meets a certain requirement, the model is considered to have been built
successfully and can be put into use. Otherwise, the RSRP model is considered
to have failed to be built and the eNodeB goes back to 2. If the number of
consecutive building failures has reached the maximum, the eNodeB waits for
28 days before it tries to build the model again. If the relative error of a
spectral efficiency prediction model meets a certain requirement, the eNodeB
considers that the conditions are met and the model has been built
successfully, and it puts the model into use. Otherwise, the eNodeB considers
that the model has failed to be built.
As the use of virtual grid models increases CPU usage, the eNodeB performs flow
control as follows: It stops using virtual grid models to inquire about the RSRP and
spectral efficiency of neighboring frequencies when board CPU usage exceeds
60%. It resumes the inquiry when the board CPU usage drops below 45%.
Virtual grid model building also involves the following mechanisms:
● When the INTRAF_EFF_MDL_PRI_BUILD_SW option of the

MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is selected, the
eNodeB supports preferential building of intra-frequency spectral efficiency
models.
● When the VG_MDL_COORDINATE_TRAIN_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is selected and
virtual grid model building is triggered, the eNodeB can collect measurement
reports from UEs that treat the local cell as their SCell for model building.
4.1.1.2 Virtual Grid Model Updating

Figure 4-4 shows the process of updating virtual grid models.
Figure 4-4 Process of updating virtual grid models

eRAN
After virtual grid models are built, the eNodeB monitors their performance and
updates them as follows:
1. After a model is put into use, the eNodeB starts the model monitoring and
updating process, in which it performs 2 and 4 in parallel.
2. The eNodeB monitors related KPIs in real time, based on which the eNodeB
determines the changes in the handover success rate while the model is being
used. It then proceeds to 3.
3. If KPIs such as the success rate of inter-frequency handovers based on the
model-based prediction results are lower than expected for two consecutive
hours, the eNodeB suspends the use of this model and puts it into use again
one day later. If the KPIs are still lower than expected, the eNodeB goes to 6
to build a new model, and uses the new model after it is successfully built. If
the KPIs are higher than expected after the model is put into use again, the
model will continue to be used.
4. The eNodeB monitors the model accuracy by performing a model accuracy
test every third day and then proceeds to 5.
5. If the model accuracy decreases, the eNodeB stops using the model, proceeds
to 6 to build a new model, and uses the new model after it is successfully
built.
6. The eNodeB builds a new model. It randomly selects a specific number of UEs
at a specific time in the cell for which the new model is to be built, collects
data from these UEs, and uses the collected data to build the new model.
Virtual grid model updating also involves the following mechanisms:
When the VG_MDL_PRED_NCELL_ENH_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is selected and virtual
grid model building is triggered, the eNodeB considers the following inter-
frequency neighboring cells reported by UEs during data collection as unknown
neighboring cells and includes them in model training; after the virtual grid
models are built, the eNodeB can predict the RSRP values of these unknown
neighboring cells:
● Neighboring cells with physical cell identifier (PCI) conflicts
● Neighboring cells not in the inter-frequency neighboring relation table (NRT)
● Neighboring cells whose coverage areas dynamically change
These neighboring cells have the COVERAGE_DYNAMIC_CHANGE_FLAG
option of the EutranExternalCell.AggregationAttribute parameter selected.
This option can be manually set. It can also be automatically set by the
eNodeB based on the X2 interface, if such a neighboring cell is served by
another eNodeB and the BEAM_NUM_ADJ_SWITCH option of the
SectorSplitGroup.SectorSplitSwitch parameter is selected for the sector
corresponding to the cell.
4.1.1.3 Switches for the Virtual Grid Function

The virtual grid function serves as a basic capability in which successfully built
virtual grid models are used in different features to improve user experience.
Virtual grid model building is not controlled by a separate switch. Instead, it is
controlled by the switches of the features that use virtual grid models.
Currently, the virtual grid function is used in smart carrier selection and Mid- and
Low-Band Coordination. Virtual grid model building is enabled when any feature

eRAN
that uses virtual grid models is enabled and is disabled only when all features that
use virtual grid models are disabled.
This document mainly focuses on smart carrier selection. For details about Mid-
and Low-Band Coordination, see Low-Band Booster.
Enabling the Virtual Grid Function

For smart carrier selection and Mid- and Low-Band Coordination, the building and
use of virtual grid models can be enabled by selecting the options listed in Table
4-4.
Table 4-4 Enabling the virtual grid function

Building and Options to Be Selected in the Options to be Selected in
Use of Virtual Case of Smart Carrier the Case of Mid- and Low-
Grid Models Selection Band Coordination
Building of SMART_CARRIER_SELECTION LOW_FREQ_SCS_OPT_SW or

RSRP _SW or LTE_RSRP_VG_MDL_BUILD_S
prediction LTE_RSRP_VG_MDL_BUILD_S W option of the
models W option of the MultiCarrUnifiedSch.MultiC
MultiCarrUnifiedSch.MultiCa arrierUnifiedSchSw
rrierUnifiedSchSw parameter parameter
Use of RSRP SMART_CARRIER_SELECTION LOW_FREQ_SCS_OPT_SW

prediction _SW option of the option of the
models MultiCarrUnifiedSch.MultiCa MultiCarrUnifiedSch.MultiC
rrierUnifiedSchSw parameter arrierUnifiedSchSw
parameter
Building of When any of the options that control the building of RSRP
spectral prediction models is selected, spectral efficiency prediction
efficiency models can be built if either of the following options is
prediction selected:
models ● LTE_SPEC_EFF_VG_MDL_BUILD_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw
parameter
● SMART_CARRIER_SELECTION_ENH_SW option of the
parameter
Use of spectral When any of the options that control the use of RSRP
efficiency prediction models is selected, spectral efficiency prediction
prediction models can be used if the
models SMART_CARRIER_SELECTION_ENH_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is
selected.
Disabling the Virtual Grid Function

The building and use of virtual grid models can be disabled by deselecting the
options listed in Table 4-5.

eRAN
Table 4-5 Disabling the virtual grid function
Disabling the Options to Be Deselected

Building and Use of
Virtual Grid Models
Disabling the building All the SMART_CARRIER_SELECTION_SW,

of RSRP prediction LOW_FREQ_SCS_OPT_SW, and
models LTE_RSRP_VG_MDL_BUILD_SW options of the
parameter
Disabling the use of Both the SMART_CARRIER_SELECTION_SW and

RSRP prediction LOW_FREQ_SCS_OPT_SW options of the
models MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw
parameter
Disabling the building Both the SMART_CARRIER_SELECTION_ENH_SW and

of spectral efficiency LTE_SPEC_EFF_VG_MDL_BUILD_SW options of the
prediction models MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw
parameter
Disabling the use of SMART_CARRIER_SELECTION_ENH_SW option of the

spectral efficiency MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw
prediction models parameter
4.1.1.4 Conditions for Using Virtual Grid Models

This section describes the conditions for using virtual grid models in smart carrier
selection.
The eNodeB delivers to a UE the event A3 measurement configurations related to

the frequency that the UE is camping on. After receiving A3 measurement reports
from the UE, the eNodeB uses virtual grid models to inquire about the spectral
efficiency of the serving frequency and the RSRP and spectral efficiency of
candidate frequencies based on the reported A3 measurement results. The time-
to-trigger for event A3 is specified by the
MultiCarrUnifiedSch.IntraFreqMeasA3TimeToTrig parameter.
For neighboring frequencies that meet both of the following conditions, no

measurements are needed to obtain their RSRP values. Instead, the RSRP values
predicted using the virtual grid models of the serving cell are utilized. For
neighboring frequencies that meet neither of these conditions, the eNodeB
delivers event A4/A5 measurement configurations related to these frequencies to
the UE:
● Condition 1: An RSRP prediction model is available, and the prediction

accuracy of the model meets an accuracy requirement. The accuracy
requirement for PCC anchoring of CA UEs and handovers of non-CA UEs is
specified by the MultiCarrUnifiedSch.VgModelPredHoMeasRsrpThld
parameter, and the accuracy requirement for SCell configuration for CA UEs is
specified by the MultiCarrUnifiedSch.VgModelPredSccMeasRsrpThld
parameter.

eRAN
● Condition 2
– For a candidate frequency for SCell configuration for a CA UE, the
prediction result meets the entering or leaving condition for event A5.
– For a candidate frequency for the PCC anchoring of a CA UE:
▪ If MultiCarrUnifiedSch.VgModelPredHoMeasRsrpThld is set to a
value other than ACCURACY100_ENH, the prediction result meets
the entering or leaving condition for event A5.
▪ If MultiCarrUnifiedSch.VgModelPredHoMeasRsrpThld is set to
ACCURACY100_ENH, the prediction result meets the leaving
condition for event A5.
– For a candidate frequency for the handover of a non-CA UE:
▪ If MultiCarrUnifiedSch.VgModelPredHoMeasRsrpThld is set to a
value other than ACCURACY100_ENH, the prediction result meets
the entering or leaving condition for event A4.
▪ If MultiCarrUnifiedSch.VgModelPredHoMeasRsrpThld is set to
ACCURACY100_ENH, the prediction result meets the leaving
condition for event A4.
If the strongest inter-frequency neighboring cell predicted for a UE using the

virtual grid models is an unknown neighboring cell, the eNodeB delivers event
A4/A5 measurement configurations related to all candidate frequencies to the UE.
The measurements are stopped once the eNodeB receives measurement reports
from the UE or when it does not receive measurement reports from the UE within
3 seconds.
If the UE is a CA UE, the eNodeB delivers event A5 measurement configurations to

the UE. In the measurement configurations, threshold 1 for the serving cell and
threshold 2 for neighboring cells are always –43 dBm and –140 dBm, respectively.
The UE evaluates whether the entering condition for event A5 is met based on the
two thresholds and, if met, sends measurement reports to the eNodeB. If the UE
determines that the entering condition for event A5 is met and sends the
measurement reports, the eNodeB checks whether the reported measurement
result meets the threshold for PCC anchoring or the threshold for SCell
configuration. For details about the thresholds for PCC anchoring and SCC
configuration, see Carrier Aggregation.
If the UE is a non-CA UE, the eNodeB delivers event A4 measurement

configurations to the UE. In the measurement configurations, the threshold for
event A4 is –140 dBm. The UE evaluates whether the entering condition for event
A4 is met based on the threshold and, if met, sends measurement reports to the
eNodeB. If the UE determines that the entering condition for event A4 is met and
sends the measurement reports, the eNodeB checks whether the reported
measurement result meets the threshold for handovers of non-CA UEs (specified
by the InterFreqHoGroup.InterFreqLoadBasedHoA4ThdRsrp parameter).
When the VG_MDL_ACCURACY_ADAPT_SW option of the

eNodeB adaptively selects a model accuracy for a carrier selection algorithm that
uses virtual grid models. This adaptive selection is based on the corresponding
inter-frequency RSRP threshold for event A4/A5.

eRAN
The virtual grid models of the serving cell may not provide the spectral efficiency
of a UE on some neighboring frequencies. In this case, the eNodeB can use the
inter-frequency event A4/A5 measurement results of the UE to obtain the RSRP of
a neighboring frequency and then input the RSRP into the spectral efficiency
model of the cell on the neighboring frequency to query the spectral efficiency of
this frequency.
The following is an example in which the UE is served by cell 1 on F1. Cell 1 has
the following three neighboring frequencies:
● Neighboring frequency F2, on which cell 2 operates
Table 4-6 lists the virtual grid models built by the eNodeB.
Table 4-6 An example of virtual grid models
Model Index RSRP Prediction Model Spectral Efficiency

Prediction Model
[Cell 1, F1] N/A Available
[Cell 1, F2] Available Available
[Cell 1, F3] Unavailable Unavailable
[Cell 1, F4] Unavailable Unavailable
[Cell 3, F3] N/A Available
[Cell 3, F4] Available Available
In the preceding example of virtual grid models, the spectral efficiency models of
cell 1 for F1 and F2 are available. In this case, the eNodeB can obtain the RSRP of
the UE on F1 from A3 measurements and uses the obtained RSRP to query the
spectral efficiency of F1 and F2. In the example, the spectral efficiency models of
cell 1 for F3 and F4 are unavailable. In this case, the eNodeB can instruct the UE in
cell 1 to measure F3 so as to obtain the RSRP of the UE on F3. Then, the eNodeB
uses the obtained RSRP to query the spectral efficiency model of cell 3 for F3 or
F4, thus allowing the spectral efficiency of F3 or F4 to be obtained.
4.1.1.5 Relationship Between Virtual Grid Models and Handovers

The prediction results of virtual grid models can be used in the following types of
handovers:
● Necessary handovers (coverage-based inter-frequency handovers)
When the EutranInterNFreq.InterFreqHoEventType parameter is set to
EventA4, the MultiCarrUnifiedSch.VgMdlPredNecHoMeasRsrpThld
parameter is set to ACCURACY100_ENH, and smart carrier selection based on
virtual grids takes effect, the eNodeB does not deliver measurement
configurations related to any candidate neighboring frequency if all these
frequencies are predicted to meet the leaving condition for event A4. In this

eRAN
case, the eNodeB periodically checks the model-based prediction results based
on event A3 measurement reports from the UE. As long as at least one
candidate neighboring frequency meets the entering condition for event A4,
the eNodeB delivers event A4 measurement configurations to the UE and
performs a handover based on the measurement results.
● Unnecessary handovers
– Service-based inter-frequency handover
When the MultiCarrUnifiedSch.VgMdlPredNecHoMeasRsrpThld
parameter is set to ACCURACY100_ENH and smart carrier selection
based on virtual grids takes effect, the eNodeB does not deliver
measurement configurations related to any candidate neighboring
frequency if all these frequencies are predicted to meet the leaving
condition for the measurement event related to service-based inter-
frequency handovers. In this case, the eNodeB periodically checks the
model-based prediction results based on event A3 measurement reports
from the UE. As long as at least one candidate neighboring frequency
meets the entering condition for the measurement event related to
service-based inter-frequency handovers, the eNodeB delivers
configurations of the measurement event related to service-based inter-
frequency handovers to the UE and performs a handover based on the
measurement results.
– PRB-usage-based connected mode load equalization
Models are used in the same way as in service-based inter-frequency
handovers.
– User-number-based connected mode load equalization
Models are used in the same way as in service-based inter-frequency
handovers.
For details about coverage-based inter-frequency handover and service-based
inter-frequency handover, see Mobility Management in Connected Mode.
For details about PRB-usage-based connected mode load equalization and user-
number-based connected mode load equalization, see Intra-RAT Mobility Load
Balancing.
4.1.2 Smart Carrier Selection

With smart carrier selection, the eNodeB selects the optimal carriers or carrier
combinations for UEs based on predictions by virtual grid models. This function
involves basic concepts of CA and mobility management (such as handovers). For
details about these concepts, see Carrier Aggregation and Mobility Management
in Connected Mode. In the following descriptions, UEs that support CA are referred
to as CA UEs, and UEs that do not support CA are referred to as non-CA UEs.
Smart carrier selection is compatible with non-CA UEs and CA UEs that are
capable of 2CC–8CC aggregation. After smart carrier selection is enabled, a
maximum of 16 PCC frequencies can be configured on an eNodeB. For each PCC
frequency, a maximum of 16 SCC frequencies can be specified, and all of these
SCC frequencies can be specified for an operator. Ensure that the total number of
frequencies configured as candidate PCCs and SCCs does not exceed 17. Any
additional frequencies will not be selected for CA.
Smart carrier selection involves the options listed in Table 4-7.

eRAN
Table 4-7 Options involved in smart carrier selection

Option Function Controlled by Remarks
the Option
SMART_CARRIER_SELEC When this option is N/A

TION_SW option of the selected, smart carrier
MultiCarrUnifiedSch.M selection is enabled.
ultiCarrierUnifiedSchSw With this function, the
parameter eNodeB can use the
inter-frequency air
interface quality
predicted by virtual grid
models to select optimal
carrier combinations for
CA UEs.
SMART_CARRIER_SELEC When this option is N/A

TION_ENH_SW option selected, enhanced smart
of the carrier selection is
MultiCarrUnifiedSch.M enabled. This function
ultiCarrierUnifiedSchSw includes smart carrier
parameter selection for non-CA UEs
during initial access and
improvement of spectral
efficiency prediction
accuracy.
TRAFFIC_AWARENESS_S When both options are N/A

CS_SW and selected, the function of
INTER_ENB_UL_UU_CAP traffic model-aware
B_EVAL_SW options of smart carrier selection is
the enabled, allowing for
MultiCarrUnifiedSch.M service-type-based smart
ultiCarrierUnifiedSchSw carrier selection.
parameter
UL_CARR_SEL_ENH_SW When this option is This function is

option of the selected, enhanced supported only in TDD.
MultiCarrUnifiedSch.M uplink carrier selection is
ultiCarrierUnified- enabled, allowing for
SchEnSw parameter uplink-load-based
switching from a TDD
cell to an FDD cell.

eRAN
Option Function Controlled by Remarks

the Option
LOAD_BASED_CARR_SEL When this option is It is recommended that

_OPT_SW option of the selected, load-based this function be enabled
MultiCarrUnifiedSch.M carrier selection when the downlink PRB
ultiCarrierUnified- optimization is enabled. usage of the cell
SchEnSw parameter involved is greater than
50% and the PRB usage
difference between this
cell and the inter-
frequency cells having
the same coverage as
this cell is greater than
15%. In addition, it is
recommended that the
CellMLB.InterFreqMlbT
hd parameter be set to a
value greater than 40%.
HIGH_LOAD_CELL_FILTE If this option is selected, This function does not

R_SW option of the high-load cell filtering is distinguish between
MultiCarrUnifiedSch.M enabled. With this traffic models of UEs.
ultiCarrierUnified- function, the base
SchEnSw parameter station does not select
high-load cells as
candidate PCells.
To allow more carrier combinations for CA to be configured and increase the inter-
frequency overlapping coverage area as well as the proportion of occasions where
smart carrier selection based on virtual grids takes effect, it is recommended that
smart carrier selection be enabled together with SCC coverage threshold
adaptation. For details about SCC coverage threshold adaptation, see Low-Band
Booster.
If prohibition of smart carrier selection for specific UEs is enabled, the eNodeB
performs adaptive PCC anchoring and SCell configuration for the CA UEs involved.
For details, see Carrier Aggregation. Specific UEs include:
● UEs for which smart carrier selection is not allowed. These UEs can be
specified based on SPIDs, UE capabilities, or QCIs.
– These UEs can be specified based on SPIDs by selecting the
SCS_FORBID_SW option of the SpidCfg.AggregationAttribute
parameter. For details, see Flexible User Steering.
– These UEs can be specified based on UE capabilities by selecting the
SCS_FORBID_SW option of the UeCompat.BlacklistControlExtSwitch2
parameter. For details, see Terminal Awareness Differentiation.
– These UEs can be specified based on QCIs by selecting the
SCS_FORBID_SW option of the QciPara.AggregationAttribute
parameter. For a UE running services with multiple QCIs, smart carrier
selection is not allowed as long as the SCS_FORBID_SW option of the
QciPara.AggregationAttribute parameter is selected for any of the QCIs.

eRAN
● UEs that have accessed local cells through intra-base-station or inter-base-

station RRC connection reestablishments.
– If the REEST_SCS_FORBID_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter is
selected, smart carrier selection does not take effect for UEs that have
accessed local cells through intra-base-station RRC connection
reestablishments.
– If the BIT13 option of the eNBRsvdPara.RsvdSwPara7 parameter is
selected, smart carrier selection does not take effect for UEs that have
accessed local cells through inter-base-station RRC connection
reestablishments.
4.1.2.1 Smart Carrier Selection Scenarios and Procedures

The scenarios for smart carrier selection based on virtual grids include initial
carrier selection, periodic carrier selection, and event-triggered carrier selection
(including carrier selection triggered by traffic model changes, A1/A6-triggered
carrier selection, and A1/A2-triggered carrier selection).
During smart carrier selection based on virtual grids, the eNodeB performs special
handling of handovers in special scenarios.
Initial Carrier Selection

For a CA UE, all frequencies are candidate frequencies for initial carrier selection.
The eNodeB delivers measurement configurations related to all frequencies, uses
the prediction results of virtual grid models to evaluate the frequencies for which
virtual grid models have been built, and uses the measurement results to evaluate
the frequencies for which virtual grid models have not been built. It selects an
optimal carrier or carrier combination from all the frequencies for the UE.
For a non-CA UE:
● If the CellMultiCarrUniSch.NonCaConnUeScsA1RsrpThld parameter is set to

0, the frequencies for which virtual grid models have been built are candidate
frequencies for initial carrier selection. The eNodeB selects an optimal carrier
only from the frequencies for which virtual grid models have been built.
a value other than 0, all frequencies are candidate frequencies for initial
carrier selection. The eNodeB delivers measurement configurations related to
all frequencies, uses the prediction results of virtual grid models to evaluate
the frequencies for which virtual grid models have been built, and uses the
measurement results to evaluate the frequencies for which virtual grid models
have not been built. It selects an optimal carrier from all the frequencies for
the UE.
Initial carrier selection happens in the following scenarios:
● In the case of CA UEs

– Initial access
– Necessary handovers
– Inter-eNodeB unnecessary incoming handovers

eRAN
– Unnecessary intra-eNodeB incoming handovers except PCC-anchoring-

triggered handovers
– Incoming RRC connection reestablishments
● In the case of non-CA UEs
– Initial access
Figure 4-5 takes initial access as an example to illustrate the signaling procedure.
Figure 4-5 Smart carrier selection based on virtual grids during initial access
For CA UEs, the candidate frequencies are determined by the UE-reported CA

capabilities and the PccFreqCfg and SccFreqCfg settings. In TDD, if there are LAA
frequencies, the eNodeB arranges them in descending order based on the number
of sector equipment sets operating on the individual frequencies, and selects a
maximum of four LAA frequencies. For each LAA sector equipment set, only one of
its operating frequencies can be selected.
For non-CA UEs, based on the UE-reported event A3 measurement results, the
eNodeB selects only the frequencies whose RSRP and spectral efficiency can be
predicted by virtual grid models as the candidate frequencies. If no virtual grid
models are applicable for a non-CA UE and the
LOAD_BASED_CARR_SEL_OPT_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter is selected, the
eNodeB selects a neighboring cell whose downlink PRB usage difference from the
serving cell is greater than or equal to 15% based on A4 measurement results for
carrier selection.

eRAN
NOTE
During initial access of a CA UE, if the AdpCaSwitch option of the

ENodeBAlgoSwitch.CaAlgoSwitch parameter is selected, the eNodeB initiates a blind SCell
configuration procedure for the UE before selecting the optimal carrier combination based
on the prediction results of virtual grid models or the measurement results. During this
procedure, the eNodeB generates a list of blind-configurable cell combination candidates
based on the settings of the PccFreqCfg and SccFreqCfg managed objects (MOs),
operator-defined band combinations, UE-reported CA capabilities, and blind-configurable
candidate cells. The eNodeB then sorts the blind-configurable cell combination candidates
by aggregated bandwidth and selects the candidate with the largest aggregated bandwidth
for the UE.
Periodic Carrier Selection

For UEs whose RRC connections have been set up, the eNodeB periodically
initiates the procedure for smart carrier selection based on virtual grids. For CA
UEs, long-cycle carrier selection is applicable. For non-CA UEs, short-cycle carrier
selection is applicable.
● Long-cycle carrier selection takes effect only in SCell change for CA UEs. The
candidate frequencies are generated in the same way as in initial carrier
selection. For details about the SCell activation conditions, see Carrier
Aggregation.
Two long-cycle timers are used for triggering carrier selection:
– Timer 1 is used for prompt selection of optimal carriers or carrier
combinations for moving UEs. When timer 1 expires, the eNodeB initiates
the procedure for smart carrier selection based on virtual grids again if
the downlink traffic volume of the UE meets the SCell activation
conditions and there is a more than 30% difference between the current
air interface capability of the serving cell combination for the UE and the
capability during the previous carrier selection. Timer 1 is specified as
follows:
▪ If both the network and UE support non-standalone (NSA)

networking but no secondary cell group (SCG) has been added for
the UE, timer 1 is specified by the
NsaDcMgmtConfig.ScgAdditionInterval parameter.
▪ If both the network and UE support NSA networking and an SCG has
been added for the UE, timer 1 is specified by the
NsaDcMgmtConfig.NsaDcLteScellConfigIntvl parameter.
▪ In other situations, timer 1 is specified by the

CaMgtCfg.SccCfgInterval parameter.
– Timer 2 is used for prompt selection of optimal carriers or carrier
combinations for UEs when the radio signal characteristics of neighboring
cells change (for example, when cell status changes from unavailable to
available). Timer 2 is six times timer 1 in length. When timer 2 expires,
the eNodeB initiates the procedure for smart carrier selection based on
virtual grids if the downlink traffic volume of the UE meets the SCell
activation conditions.

eRAN
NOTE
When timer 1 expires and the procedure for smart carrier selection based on
virtual grids is triggered, timer 2 restarts.
● Short-cycle carrier selection takes effect only for non-CA UEs and is used for
prompt selection of optimal carriers for UEs upon network load changes.
The cycle is 100 ms. At the end of each cycle, if the percentage of the data
transmission duration in the cycle in the cell is greater than or equal to 60%,
the eNodeB initiates the procedure for smart carrier selection based on virtual
grids and randomly selects three frequencies as the candidate frequencies for
each UE that meets all the following conditions: (1) The downlink traffic
volume of the UE is greater than 10 kilobytes; (2) the percentage of the data
transmission time of the UE in the total data transmission time of all UEs in
the cell is less than or equal to 50%; (3) the modulation and coding scheme
(MCS) index used for the UE is less than or equal to 20.
As short-cycle carrier selection increases CPU usage, the eNodeB performs
flow control by stopping short-cycle carrier selection when the board CPU
usage exceeds 70% and resuming the selection when the board CPU usage
drops below 45%.
Figure 4-6 illustrates the signaling procedure.
Figure 4-6 Periodic smart carrier selection based on virtual grids
Event-triggered Carrier Selection (Triggered by Traffic Model Changes)

Smart carrier selection is based on traffic model identification. The traffic model of
a UE can be downlink-preferred, uplink-preferred, or neutral. By default, the
eNodeB considers the traffic model of a UE to be downlink-preferred when the UE
accesses a cell through initial access, an incoming handover, or an incoming RRC
connection reestablishment. After the access, the eNodeB identifies the traffic

eRAN
model of the UE according to the uplink and downlink traffic volumes. The traffic
models are listed in Table 4-8.
Table 4-8 UE traffic models

Model Meaning
Downlink-preferred Light uplink traffic
Uplink-preferred Heavy uplink traffic and light downlink traffic
Neutral Heavy uplink traffic and heavy downlink traffic
Table 4-9 lists the criteria for determining the uplink and downlink traffic volumes
of a UE.
Table 4-9 Criteria for determining the traffic volumes of a UE

Direc Traffic Switch Status Criterion
tion Status
Uplin Heavy N/A The average amount of remaining

k traffic data in the uplink buffer per TTI is
greater than or equal to the threshold
specified by the
CellMultiCarrUniSch.UlTrafficVolume
Thld parameter for three consecutive
100-ms periods.
Light The The average amount of remaining

traffic FAST_TRAFFIC_AW data in the uplink buffer per TTI is less
ARENESS_SCS_SW than the threshold specified by the
option of the CellMultiCarrUniSch.UlTrafficVolume
MultiCarrUnifiedS Thld parameter for 30 consecutive
ch.MultiCarrierUnif 100-ms periods.
iedSchEnSw
parameter is
deselected.
The The average amount of remaining

FAST_TRAFFIC_AW data in the uplink buffer per TTI is less
ARENESS_SCS_SW than the threshold specified by the
option of the CellMultiCarrUniSch.UlTrafficVolume
MultiCarrUnifiedS Thld parameter for n consecutive 100-
ch.MultiCarrierUnif ms periods. (n is equal to
iedSchEnSw CellMultiCarrUniSch.TrafficModeExit
parameter is PeriodNum.)
selected.

eRAN
Direc Traffic Switch Status Criterion

tion Status
Down Heavy The The average amount of remaining

link traffic FAST_TRAFFIC_AW data in the downlink buffer per TTI is
ARENESS_SCS_SW greater than or equal to the threshold
option of the specified by the
MultiCarrUnifiedS CellMultiCarrUniSch.DlTrafficVolume
ch.MultiCarrierUnif Thld parameter for three consecutive
iedSchEnSw 1-second periods.
parameter is
deselected.

FAST_TRAFFIC_AW data in the downlink buffer per TTI is
ARENESS_SCS_SW greater than or equal to the threshold
option of the specified by the
MultiCarrUnifiedS CellMultiCarrUniSch.DlTrafficVolume
ch.MultiCarrierUnif Thld parameter for three consecutive
iedSchEnSw 100-ms periods.
parameter is
selected.
Light The The average amount of remaining

traffic FAST_TRAFFIC_AW data in the downlink buffer per TTI is
ARENESS_SCS_SW less than the threshold specified by the
option of the CellMultiCarrUniSch.DlTrafficVolume
MultiCarrUnifiedS Thld parameter for three consecutive
ch.MultiCarrierUnif 1-second periods.
iedSchEnSw
parameter is
deselected.

FAST_TRAFFIC_AW data in the downlink buffer per TTI is
ARENESS_SCS_SW less than the threshold specified by the
option of the CellMultiCarrUniSch.DlTrafficVolume
MultiCarrUnifiedS Thld parameter for n consecutive 100-
ch.MultiCarrierUnif ms periods. (n is equal to
iedSchEnSw CellMultiCarrUniSch.TrafficModeExit
parameter is PeriodNum.)
selected.
In addition to long-cycle carrier selection, carrier selection can be performed for

CA UEs upon traffic model changes so that the eNodeB can quickly select the
optimal carriers or carrier combinations for CA UEs whose traffic models have
changed. This procedure takes effect only for CA UEs that are incapable of NSA
DC and allows PCells and SCells to be changed. For these UEs, the eNodeB selects
candidate frequencies based on traffic models as follows:
● In the case of a UE traffic model change to the downlink-preferred traffic
model:

eRAN
– If the downlink traffic is heavy, the candidate frequencies are generated

in the same way as in initial carrier selection.
– If the downlink traffic is light:
▪ If the previous traffic model is uplink-preferred and the

FAST_TRAFFIC_AWARENESS_SCS_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter is
selected, the candidate frequencies are generated in the same way as
in initial carrier selection.
▪ Otherwise, the eNodeB does not trigger smart carrier selection.

● In the case of a UE traffic model change to the neutral model:
– If the previous traffic model is uplink-preferred, the candidate frequencies
are generated in the same way as in initial carrier selection.
– If the previous traffic model is downlink-preferred, the eNodeB selects the
operating frequencies of the PCell and SCells serving the UE.
● In the case of a UE traffic model change to the uplink-preferred traffic model,
the candidate frequencies are as follows:
– Operating frequencies of the PCell and SCells serving the UE
– Frequencies whose RSRP can be predicted based on event A3 reports
when the TRAFFIC_AWARENESS_SCS_OPT_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is selected
– Frequencies for which the UL_LOAD_TRNSFR_TARGET_FLAG option of
the EutranInterNFreq.AggregationAttribute parameter is selected when
the serving cell is a TDD cell and the UL_CARR_SEL_ENH_SW option of
selected
Figure 4-7 illustrates the signaling procedure for carrier selection triggered by
traffic model changes.

eRAN
Figure 4-7 Carrier selection triggered by traffic model changes
Event-triggered Carrier Selection (Triggered by Event A1 or A6)

For UEs whose RRC connections have been set up, the eNodeB performs the
procedure for smart carrier selection based on virtual grids when event A1 or A6 is
triggered, in addition to periodic triggering of this procedure. Figure 4-8 illustrates
the signaling procedure.

eRAN
Figure 4-8 Smart carrier selection based on virtual grids when event A1 or A6 is
triggered
The A1-triggered procedure allows the eNodeB to quickly select optimal carriers or
carrier combinations for the UEs during their movement from low-frequency cell
edges to cell centers in a multi-frequency concentric cell networking scenario. (A
low-frequency cell is a cell whose downlink center frequency is less than 1 GHz.)
In the case of CA UEs:
● When both PCell and SCell changes are allowed and the
EnhancedPccAnchorSwitch option of the ENodeBAlgoSwitch.CaAlgoSwitch
parameter is selected, the eNodeB delivers A1 measurement configurations to
UEs during initial access, necessary incoming handovers, or incoming RRC
connection reestablishments. The RSRP threshold for event A1 is specified by
the CaMgtCfg.EnhancedPccAnchorA1ThdRsrp parameter. After receiving an
A1 measurement report from a UE, the eNodeB sends an RRC Connection
Reconfiguration message to the UE to stop A1 measurements and triggers the
procedure for smart carrier selection based on virtual grids. If the
LOAD_BASED_CARR_SEL_OPT_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter is selected and
PCell change has not been triggered for a CA UE, the eNodeB performs smart
carrier selection at 10-second intervals for the UE.
● When only SCell changes are allowed and the
CaMgtCfg.EnhancedSccSelA1ThldRsrp parameter is set to a value other
than –40 dBm, the eNodeB delivers A1 measurement configurations to UEs
during initial access, necessary incoming handovers, or incoming RRC
connection reestablishments, with the RSRP threshold for event A1 being the
value of this parameter. After receiving an A1 measurement report from a UE,
the eNodeB sends an RRC Connection Reconfiguration message to the UE to

eRAN
stop A1 measurements and triggers the procedure for smart carrier selection
based on virtual grids.
In the case of non-CA UEs:

a non-zero value, the eNodeB delivers A1 measurement configurations to UEs
during initial access, with the RSRP threshold for event A1 being the value of
this parameter. After receiving an A1 measurement report from a UE, the
eNodeB sends an RRC Connection Reconfiguration message to the UE to stop
A1 measurements and triggers the procedure for smart carrier selection based
on virtual grids. If the LOAD_BASED_CARR_SEL_OPT_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter is selected, the
eNodeB preferentially delivers measurement configurations for frequencies
with light load to non-CA UEs.
The A6-triggered procedure allows the eNodeB to quickly select optimal carriers or
carrier combinations for the UEs when the PCell does not provide contiguous
coverage and inter-eNodeB cells cannot be configured as SCells. If the
A6_BASED_SCS_SW option of the
eNodeB performs smart carrier selection for UEs whose SCells cannot be changed
after they send A6 measurement reports. This procedure takes effect only for CA
UEs and allows both PCells and SCells to be changed for the UEs.
In the following example (Figure 4-9), inter-eNodeB CA based on relaxed

backhaul is not enabled, and the initial carrier combination for the UE includes
cells 0, 1, and 2, among which cell 0 is the PCell of the UE. As the UE moves, the
priority of this carrier combination becomes lower than that of the carrier
combination of cells 3 and 4. When the UE sends A6 measurement reports but its
SCells cannot be changed, the eNodeB promptly triggers smart carrier selection to
select cell 3 as the PCell and cell 4 as an SCell for the UE.
Figure 4-9 A6-triggered carrier selection

eRAN
Event-triggered Carrier Selection (Triggered by Event A1 or A2)

If a UE sends an event A2 report related to coverage-based inter-frequency
handover, the UE is normally located in a weak coverage area. Smart carrier
selection for the UE normally fails to select a carrier that meets the coverage
requirements, and even may cause a service drop on the UE due to the large
amount of measurement configuration signaling delivered to it. In this case, the
following functions can be enabled to prevent service drops caused by smart
carrier selection for UEs under weak coverage:
● Prohibition of SCell configuration triggered by inter-frequency event A2 for CA
UEs under weak coverage
This function is controlled by the RcvA2CfgSccSwitch option of the
CaMgtCfg.CellCaAlgoSwitch parameter.
– If this option is deselected, SCell configuration, SCell change, and PCC
anchoring for CA UEs are affected by event A2 reporting.
After the serving eNodeB of the PCell for a CA UE receives an event A2
report related to coverage-based inter-frequency handover from the UE,
the eNodeB stops configuring SCells, changing SCells, and performing
PCC anchoring for the UE. If the eNodeB receives an event A1 report
related to coverage-based inter-frequency handover, the eNodeB can
configure SCells in a blind manner (if blind SCell configuration is
enabled) or after receiving an event A4 report related to carrier
management from the UE, can change SCells, and can perform PCC
anchoring for the UE.
– If this option is selected, SCell configuration, SCell change, and PCC
anchoring are not affected by event A2 reporting. The serving eNodeB of
the PCell for a CA UE can still configure SCells, change SCells, and
perform PCC anchoring for the UE after receiving an event A2 report
related to coverage-based inter-frequency handover from the UE.
● Prohibition of smart carrier selection triggered by inter-frequency event A2 for
non-CA UEs under weak coverage
This function is controlled by the BIT2 option of the
eNBCellRsvdPara.RsvdSwPara10 parameter.
– If this option is selected, whether smart carrier selection takes effect for
non-CA UEs is affected by event A2 reporting related to coverage-based
inter-frequency handover.
After the eNodeB receives an event A2 report related to coverage-based
inter-frequency handover from a non-CA UE, the eNodeB prohibits smart
carrier selection from taking effect for the UE. If the eNodeB receives an
event A1 report related to coverage-based inter-frequency handover from
the UE, the eNodeB allows smart carrier selection to take effect for the
UE.
– If this option is deselected, whether smart carrier selection takes effect
for non-CA UEs is not affected by event A2 reporting related to coverage-
based inter-frequency handover.
Special Handling of UE Handovers

When handovers are triggered for UEs that have SCells configured, SCell
configuration during handovers takes effect by default in smart carrier selection

eRAN
for these UEs. For details, see "Mobility and Load Management" in Carrier
Aggregation.
Due to compatibility issues, certain UEs may experience a low handover success
rate or failures of FDD-to-TDD handovers with SCell configuration. To prevent
these problems from occurring, operators can set the
UeCompat.BlacklistControlExtSwitch1 parameter to enable differentiated
handling for these UEs:
● If the SCS_BASED_HO_SWITCH option is selected, handovers triggered by
smart carrier selection are prohibited for these UEs.
● If the SCS_FDD_TO_TDD_HO_WITH_SCC_SW option is selected, FDD-to-TDD
handovers with SCell configuration triggered by smart carrier selection are
prohibited for these UEs.
For details about differentiated handling, see Terminal Awareness Differentiation.
If the signal levels of the target cell for a handover and its intra-frequency
neighboring cell are similar, the handover may fail.
● For a low-frequency cell from which handovers for smart carrier selection
based on virtual grids are triggered, operators can set the
MultiCarrUnifiedSch.GFactorThldForLowFreqHoTrg parameter to a value
other than 32767. With this setting, an inter-frequency neighboring cell can
be selected as the target cell for the handovers only when it meets the
conditions specified by the parameter, thereby reducing the handover failure
probability.
● For a non-low-frequency cell from which handovers for smart carrier selection
based on virtual grids are triggered, operators can set the
MultiCarrUnifiedSch.GFactorThldForHoTrgCell parameter to a value other
than 32767. With this setting, an inter-frequency neighboring cell can be
selected as the target cell for the handovers only when it meets the
conditions specified by the parameter, thereby reducing the handover failure
probability.
4.1.2.2 Carrier or Carrier Combination Priority Factors and Selection
Carrier or Carrier Combination Priority Factors

In smart carrier selection for a UE, the eNodeB assigns the candidate carrier or
carrier combination with the highest priority to the UE. The priority of each
candidate is calculated based on the following factors:
● Downlink air interface capability
Air interface capability is the paramount factor in the calculation of the
priorities of candidates. The eNodeB assigns the carrier or carrier combination
with the highest downlink air interface capability to the UE to increase the
downlink user-perceived rate. This capability evaluation considers the UE-level
downlink spectral efficiency, cell bandwidth, and cell load. These factors are
explained as follows:
– UE-level downlink spectral efficiency
▪ The eNodeB preferentially inquires about UE-level downlink spectral

efficiency from virtual grid models. Spectral efficiency predicted by

eRAN
virtual grid models can be used for smart carrier selection only when
the predictions cover all frequencies.
▪ If the eNodeB fails to acquire UE-level downlink spectral efficiency

from virtual grid models, it estimates the UE-level downlink spectral
efficiency of a frequency based on the measured RSRP values for
multiple cells on that frequency, the number of transmit antennas at
the eNodeB, and the number of receive antennas at the UE.
However, sometimes the estimated UE-level downlink spectral
efficiency may not be accurate. It is recommended that the
SPECTRUM_EFF_EVALUATION_OPT_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter be
selected so that cell-level spectral efficiency is used instead in the
following scenarios:
○ UE capabilities are restricted. Some UEs report the measurement
results of only the strongest cell on each of frequencies to be
evaluated. Using cell-level spectral efficiency mitigates the
inaccuracy of UE-level downlink spectral efficiency caused by
limited UE measurement capabilities or other factors.
○ UEs are moving at high speeds, and therefore the RSRP of the
serving cell fluctuates by at least 5 dB during measurements.
Using cell-level spectral efficiency mitigates the inaccuracy of
UE-level downlink spectral efficiency caused by fast UE mobility.
▪ For massive multiple-input multiple-output (MIMO) cells serving UEs

that support UE pairing for massive MIMO, the massive MIMO gain
coefficient specified by the CaMgtCfg.MassiveMimoGainCoefficient
parameter also needs to be considered, and the scenarios where this
coefficient is considered vary depending on the setting of the
SCC_CARR_CAPB_WITH_MM_GAIN_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter.
○ If this option is deselected, this coefficient is considered only
when UEs that support UE pairing for massive MIMO treat a
massive MIMO cell as their PCell.
○ If this option is selected, this coefficient is considered when UEs
that support UE pairing for massive MIMO treat a massive
MIMO cell as either their PCell or SCell.
▪ If a UE is located in the overlapping area of two or more cells

including a candidate target cell and the PCI-modulo-3 results of
these cells are the same, the capability of the candidate target cell
needs to be adjusted. The parameters involved are as follows:
○ eNBRsvdPara.RsvdPara62. This parameter specifies the
threshold for identifying UEs in overlapping areas. If the RSRP of
the serving cell measured by a UE minus that of the strongest
intra-frequency neighboring cell measured by the UE is less than
or equal to the actually effective value of this parameter, the UE
is in the overlapping area. If this parameter is set to a value in
the range of 1 to 21, the actually effective value equals the
configured value minus 11. If this parameter is set to 0 or a
value greater than 21, this parameter does not take effect.

eRAN
○ eNBCellRsvdPara.RsvdU8Para67. This parameter specifies the

capability adjustment factor for candidate target cells. If this
parameter is set to a value in the range of 1 to 100, the actual
adjustment factor is the result of (Value of this parameter – 1)/
100. If this parameter is set to 0 or a value greater than or equal
to 101, the adjustment factor is 1, indicating that no adjustment
is performed and the evaluated carrier capability is the same as
the actual carrier capability. If the adjustment factor of the
corresponding cell is not obtained, its carrier capability is
evaluated with the adjustment factor 1, that is, the evaluated
carrier capability is the same as the actual carrier capability.
For details about the eNBRsvdPara.RsvdPara62 and
eNBCellRsvdPara.RsvdU8Para67 parameters, see 5 Parameters.
▪ For licensed assisted access (LAA) cells, the LAA interference

coefficient, which is estimated using the interference duty ratio of
the operating frequency, must also be considered. For the definition
of the interference duty ratio, see Licensed Assisted Access (TDD).
– Equivalent downlink cell bandwidth
The equivalent downlink cell bandwidth equals the number of available
downlink RBs in a cell multiplied by CellMLB.CellCapacityScaleFactor.
However, for UEs incapable of transmission mode 9 (TM9), the equivalent
downlink cell bandwidth is calculated by decreasing this product
according to the proportion of Multimedia Broadcast multicast service
Single Frequency Network (MBSFN) subframes if the
DL_UU_CAPB_EVAL_OPT_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is selected.
– Cell load
▪ The smart carrier selection algorithm considers cell load only when
the CaMgtCfg.MinDlAvgToBeScheduledUeNum parameter is set to
a non-zero value.
▪ It is represented by the average number of UEs for which the

downlink buffer is not empty.
▪ If the UE does not support pairing for massive MIMO, the eNodeB
filters out the combinations that include high-load inter-frequency
massive MIMO cells acting as candidate SCells. A high-load inter-
frequency massive MIMO cell is defined as follows:
○ If the CaMgtCfg.HLUeCntThldForScellConfig parameter is set
to 65535, massive MIMO cells in the inter-frequency massive
MIMO load steering state are defined as high-load inter-
frequency massive MIMO cells. For details about inter-frequency
massive MIMO load steering, see Intra-RAT Mobility Load
Balancing.
○ If the CaMgtCfg.HLUeCntThldForScellConfig parameter is set
to a value other than 65535, massive MIMO cells whose number
of UEs exceeds this value are defined as high-load massive
MIMO cells.
▪ In addition, when the LOAD_BASED_CARR_SEL_OPT_SW option of


eRAN
selected, the control channel element (CCE) usage will be considered

in cell capability evaluation.
● Uplink air interface capability
The eNodeB assigns the carrier or carrier combination with the highest uplink
air interface capability to the UE to increase the uplink user-perceived rate.
This capability evaluation considers the UE-level uplink spectral efficiency and
the number of uplink RBs that can be allocated to the UE. These factors are
explained as follows:
– UE-level uplink spectral efficiency of the UE in a candidate inter-
frequency cell is estimated based on the uplink signal to interference plus
noise ratio (SINR) of the UE in this cell. This uplink SINR is calculated
based on the following factors: SINR of the UE in the serving cell,
maximum UE transmit power, and differences between the serving cell
and the candidate inter-frequency cell in terms of path loss, interference
plus noise, and the number of uplink receive antennas.
– Number of uplink RBs that can be allocated to the UE is estimated based
on the following factors: number of available RBs, number of RBs
allocated to other UEs, and maximum number of consecutive RBs that
can be allocated.
When a neutral traffic model is identified, the uplink air interface capability
can be evaluated only if the candidate cell is a cell served by the same
eNodeB of the PCell rather than an inter-eNodeB cell and is deployed on the
UBBPd or a later baseband processing unit (BBP).
● Downlink bandwidth and number of carriers
– Downlink bandwidth
The downlink bandwidth of each candidate equals the total number of
available downlink RBs. A candidate with a larger bandwidth has a higher
priority.
– Number of carriers
If two candidates have the same aggregated bandwidth, the candidate
that contains fewer carriers has a higher priority. This is because fewer
carriers mean fewer PDCCH/PUCCH resources are consumed.
● Carrier priorities for CA
– PCell change
PCell change causes a transient decrease in the data rate. Therefore, if
PCell change is not required after a candidate is selected for a UE, the
candidate has a higher priority.
– PCC duplex mode priority
The PCC duplex mode priority is specified by the
CaMgtCfg.FTCA2CCAnchorPolicy and
CaMgtCfg.FTCAMultiCCAnchorPolicy parameters. This factor applies
only to UEs that support FDD+TDD CA.
– PCC priority
The PCC priority is specified by the PccFreqCfg.PreferredPccPriority
parameter.
– SCell change

eRAN
SCell change causes a transient decrease in the data rate. Therefore, if

SCell change is not required after a candidate is selected for a UE, the
candidate has a higher priority.
– SCC priority
The SCC priority is specified by the SccFreqCfg.SccPriority parameter.
● Whether a handover is required
A handover causes a transient decrease in the data rate. Therefore, if
handover is not required after a candidate is selected for a UE, the candidate
has a higher priority.
Factors and Their Priorities in Carrier Combination Selection for CA UEs

For CA UEs, carriers or carrier combinations are selected based on the following
factors in descending order of priority, which varies depending on the traffic
model:
● Downlink-preferred traffic model: hysteresis-considered downlink bandwidth,
hysteresis-considered downlink air interface capability, PCC duplex mode
priority, PCC priority, PCell change, hysteresis-considered downlink PCC air
interface capability, SCell change, downlink bandwidth, number of carriers,
SCC priority, and downlink air interface capability.
● Uplink-preferred traffic model: hysteresis-considered uplink air interface
capability, hysteresis-considered downlink bandwidth, hysteresis-considered
downlink air interface capability, PCC duplex mode priority, PCC priority, PCell
change, hysteresis-considered downlink PCC air interface capability, SCell
change, downlink bandwidth, number of carriers, SCC priority, and downlink
air interface capability.
● Neutral traffic model: hysteresis-considered downlink bandwidth, hysteresis-
considered downlink air interface capability, hysteresis-considered uplink air
interface capability, PCC duplex mode priority, PCC priority, PCell change,
hysteresis-considered downlink PCC air interface capability, SCell change,
downlink bandwidth, number of carriers, SCC priority, and downlink air
interface capability.
Hystereses are used to prevent the selection of a carrier with a small bandwidth
difference from the currently serving carrier.
● The hysteresis for bandwidths is specified by the
MultiCarrUnifiedSch.BandwidthHysteresis parameter. The base station
considers two candidates to have the same hysteresis-considered bandwidth if
the difference in their aggregated bandwidths is less than the value of this
parameter. During A6-triggered carrier selection, the eNodeB considers all
candidates to have the same hysteresis-considered bandwidth.
● The hysteresis for downlink air interface capabilities is specified by the
MultiCarrUnifiedSch.CarrierCapabilityHysteresis parameter. The base
station considers two candidates to have the same hysteresis-considered
downlink air interface capability if the difference in their downlink air
interface capabilities is less than the value of this parameter.
● The hysteresis for uplink air interface capabilities is specified by the
MultiCarrUnifiedSch.UlCarrierCapabilityHyst parameter. The base station
considers two candidates to have the same hysteresis-considered uplink air
interface capability if their uplink air interface capability difference is less than
the value of this parameter.

eRAN
● It is recommended that the SmartCaPccSelSwitch option of the

ENodeBAlgoSwitch.CaAlgoExtSwitch parameter be deselected. If this option
is selected, the factor of PCell change is considered after the factor of
hysteresis-considered downlink PCC air interface capability and before the
factor of SCell change.
Factors and Their Priorities in Carrier Selection for Non-CA UEs

For non-CA UEs, carriers are selected based on the following factors in descending
order of priority: hysteresis-considered downlink air interface capability, handover,
downlink bandwidth, and downlink air interface capability. The carrier selection
range in terms of the duplex mode (FDD or TDD) of such a UE depends on the
NON_CA_SCS_SCOPE_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter.
● If this option is selected, the eNodeB selects carriers only from those in the
same duplex mode as the serving cell of the UE.
● If this option is deselected, the eNodeB selects carriers from either those in
the same duplex mode as or those in a different duplex mode from the
serving cell of the UE.
Pre-evaluation for Carrier Combination Selection for CA UEs

In light-load scenarios where the load is balanced among frequencies and
frequency bands differ greatly in bandwidth, CA UEs generally perform better
when they camp on large-bandwidth carriers instead of engaging in carrier
combination selection. In other words, smart carrier selection based on virtual
grids provides limited gains in this scenario. In addition, if no virtual grid models
are available or more models are required than allowed, carrier selection will
cause inter-frequency measurement gaps. In this case, pre-evaluation for carrier
combination selection needs to be enabled to reduce unnecessary inter-frequency
measurement gaps.
Pre-evaluation can be performed when the
MultiCarrUnifiedSch.PredictiveCapbGainThld parameter is set to a non-zero
value and smart carrier selection is triggered for a UE in any of the following
scenarios:
● Initial carrier selection
● Periodic carrier selection
● Carrier selection triggered by a traffic model change to the downlink-
preferred model
● A1-triggered carrier selection
Figure 4-10 shows the handling process.

eRAN
Figure 4-10 Process of pre-evaluation for carrier or carrier combination selection

for CA UEs
1. The eNodeB checks whether the UE is a full-bandwidth UE. If it is, the

eNodeB performs 2. Otherwise, the eNodeB performs 5. (A UE is a full-
bandwidth UE if it meets the following condition: The aggregated bandwidth
of the current serving carrier combination for the UE equals the maximum
aggregated bandwidth of all carrier combinations that can be configured for
the UE with the current PCell remaining unchanged.)
2. The eNodeB checks whether the current PCell can be changed. If the change
is allowed, the eNodeB performs 3. Otherwise, the eNodeB performs 4.
3. The eNodeB checks whether the current PCell has the highest PCC priority. If
it has, the eNodeB performs 4. Otherwise, the eNodeB performs 5.
4. The eNodeB pre-evaluates the air interface capability gain that the UE can
obtain from the carrier or carrier combination selection. If the gain is greater
than the threshold specified by the

eRAN
MultiCarrUnifiedSch.PredictiveCapbGainThld parameter, the eNodeB

performs 5. Otherwise, the process ends.
5. The eNodeB performs smart carrier selection.
4.1.3 Ultra-Low-Latency Scheduling for Intra-eNodeB CA

Ultra-low-latency scheduling for intra-eNodeB CA is enabled when the
ULTRA_LOW_LATENCY_SCH_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is selected.
Ultra-low-latency scheduling for intra-eNodeB CA includes the following functions:
● Delayed SCell deactivation
● Accurate data split with ultra-low latency
4.1.3.1 Delayed SCell Deactivation

Burst services account for a large proportion of the services performed on a
network and continuously occur at short intervals. After a burst service of a CA UE
is complete, the SCells for the UE may be deactivated due to a decrease in traffic.
The SCells need to be reactivated when another burst service arrives. However, it
takes a relatively long time to reactivate the SCells, and as a result, the usage rate
of resources in the SCells is low, which negatively affects user experience.
To address this issue, delayed SCell deactivation is introduced. Figure 4-11
illustrates this function. When the downlink buffer for a UE that has an SCell
activated is cleared, an SCell deactivation waiting timer starts. This timer is
specified by the CellMultiCarrUniSch.ScellDeactvWaitingTimer parameter. If the
buffer remains empty before the timer expires, the eNodeB deactivates the SCell
for the UE when the timer expires. Note that the actual deactivation delay
deviates from the value of this parameter by 0–100 ms.
If this parameter is set to an appropriate value, SCells can remain in an active
state for most UEs that have frequent burst data transmission, and as a result, the
eNodeB no longer needs to wait for SCell re-activation and can receive valid
channel state information (CSI) from the UEs earlier. Therefore, the data
transmission performance of SCells is improved.

eRAN
Figure 4-11 Principles of delayed SCell deactivation
If inter-eNodeB CA based on relaxed backhaul is enabled, the delayed SCell

deactivation function may increase the inter-eNodeB transmission load. To prevent
a significant increase in inter-eNodeB transmission load, delayed deactivation of
inter-eNodeB SCells added based on relaxed backhaul can be prohibited by
selecting the INB_SCELL_DLY_DEACTV_FORBID_SW option of the
CellMultiCarrUniSch.CellMultiCarrUnifiedSchSw parameter.
4.1.3.2 Data Split with Ultra-Low Latency

In the intra-eNodeB CA and inter-eNodeB CA based on eNodeB coordination
scenarios, data distribution to SCells and PUCCH resource allocation start as early
as in the transmission time interval (TTI) when the UE buffer changes from empty
to non-empty, as Figure 4-12 illustrates. This allows simultaneous scheduling in
the PCell and SCells to be achieved.
In scenarios where PCells are congested, data split with ultra-low latency allows
the eNodeB to first measure the extent to which a PCell is congested. If the
eNodeB determines that all resources of the PCell are occupied by non-CA UEs,
the eNodeB distributes small-packet data to the SCell with the strongest
scheduling capability. This way, the eNodeB makes full use of the resources in the
large-bandwidth SCell to mitigate the congestion on the low-band carrier.
Data split with ultra-low latency takes effect in the inter-eNodeB CA based on
eNodeB coordination scenario only when the function switch
(ULTRA_LOW_LATENCY_SCH_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter) is turned on for all
the eNodeBs involved.

eRAN
Figure 4-12 Principles of data split with ultra-low latency
4.1.4 Ultra-Low-Latency Scheduling for Inter-eNodeB CA

In inter-eNodeB CA based on relaxed backhaul, the following interactions are
involved before scheduling can be started in an inter-eNodeB SCell: data
distribution from the PCell to the SCell, SCell request for PUCCH resources to the
PCell, and PUCCH resource allocation by the PCell to the SCell. These interactions
introduce a delay that is three times the inter-eNodeB one-way transmission delay.
Therefore, the scheduling in the SCell starts later than in the PCell by a delay that
is at least three times the inter-eNodeB one-way transmission delay.
In MBB-centric scenarios, data transmission has been completed for most UEs
within the interaction delay. As a result, SCells for inter-eNodeB CA based on
relaxed backhaul are seldom used and do little to improve the user experience of
UEs involved in inter-eNodeB CA based on relaxed backhaul.
As such, ultra-low-latency scheduling for inter-eNodeB CA based on relaxed
backhaul is introduced. This function is controlled by the
INTER_ENB_ULTRA_LOW_LATENCY_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter. This function
requires that the PCell involved be an FDD cell and the preceding option be
selected on all the eNodeBs engaged.
After this function is enabled, data distribution to and PUCCH resource allocation
for the inter-eNodeB SCells of a UE can be started as early as in the TTI when the
buffer for the UE is no longer empty. In this way, scheduling can be started in the
inter-eNodeB SCells following a single inter-eNodeB one-way transmission. In
addition, a proxy RLC entity can be set up at each eNodeB serving an SCell of the
UE. Each proxy RLC entity distributes data to the MAC layer of the corresponding
inter-eNodeB SCell, preventing inaccurate scheduling capability estimation caused
by delay and improving the user-perceived throughput of the UE.

eRAN
4.1.5 Multi-Frequency Optimal Carrier Scheduling

Multi-frequency optimal carrier scheduling includes two functions, scheduling
priority optimization for CA and multi-carrier unified scheduling for CA.
● In scheduling priority optimization for CA, the base station calculates the
scheduling capability of each carrier for individual CA UEs based on the
spectral efficiency, bandwidth, and load. It maintains a high scheduling
priority of a CA UE on the carrier with the highest scheduling capability and
adjusts the scheduling priorities of the UE on the carriers that do not have the
highest scheduling capability based on the scheduling delay to prevent the UE
from preempting resources of non-CA UEs.
● In multi-carrier unified scheduling for CA, the base station schedules each CA
UE on its PCC and SCCs in a unified manner so that the PCC and SCCs can
obtain the buffered traffic volume in real time and the PCC can allocate
PUCCH resources to the SCCs in real time. This increases scheduling accuracy
for CA UEs on their PCCs and SCCs and improves downlink user experience.
Scheduling Priority Optimization for CA

On a multi-frequency network, the spectral efficiencies of different frequencies
measured by a CA UE at the same time vary because of large-scale and small-
scale fading in radio channels.
When the load on a multi-frequency network is heavy, there is strong competition

among UEs for scheduling resources. Considering that MBB burst services have
high initial scheduling priorities and the average rate of these services converges
slowly, scheduling CA UEs only on the carrier with the highest comprehensive
scheduling capability will bring multi-carrier spectral efficiency benefits and multi-
carrier load balancing benefits, ultimately increasing the user-perceived rates
across the network.
To achieve this, scheduling priority optimization for CA is introduced. With this

function, the base station calculates the scheduling capability of each carrier for a
CA UE based on the spectral efficiency, bandwidth, and load, and maintains a high
scheduling priority for the carrier that has the highest scheduling capability. The
base station also adjusts the scheduling priorities of the CA UE on the carriers that
do not have the highest scheduling capability based on the scheduling delay to
prevent the CA UE from preempting resources of non-CA UEs.
Scheduling priority optimization for CA is applicable in scenarios where inter-

eNodeB CA based on eNodeB coordination or intra-eNodeB CA is enabled, and
can be enabled by selecting the CA_SCH_PRIORITY_OPT_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter.
● If only the CA_SCH_PRIORITY_OPT_SW option of the

MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter is selected,
this function takes effect only on FDD carriers.
● If both the CA_SCH_PRIORITY_OPT_SW and
CA_MULTI_CARR_UNIFIED_SCH_SW options of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter are selected,
this function takes effect on both FDD and TDD carriers.

eRAN
In inter-eNodeB CA based on eNodeB coordination scenarios, the preceding

options must be selected on all the eNodeBs engaged. This function does not take
effect for UEs for which guaranteed bit rate (GBR) bearers have been established.
Multi-carrier Unified Scheduling for CA

In multi-carrier scenarios, the scheduling of a CA UE is relatively separate on its
PCC and SCCs, and each SCC needs to apply for PUCCH resources from the PCC
through the pre-scheduling mechanism. There is a delay between pre-scheduling
and actual scheduling. As a result, resource allocation from the PCC may be
inaccurate, preventing PCC and SCC resource usage from being maximized.
To address this issue, multi-carrier unified scheduling for CA is introduced. This
function enables the base station to schedule each CA UE on its PCC and SCCs in a
unified manner so that the PCC and SCCs can obtain the buffered traffic volume in
real time and the PCC can allocate PUCCH resources to the SCCs in real time. This
function increases scheduling accuracy for CA UEs on their PCCs and SCCs,
improving downlink user experience.
In intra-eNodeB CA scenarios, multi-carrier unified scheduling for CA can be
enabled by selecting the CA_MULTI_CARR_UNIFIED_SCH_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchEnSw parameter.
In FDD, when the UBBPd is used, this function requires that the
UBBPD_SCH_FUNCTION_ENH_SWITCH option of the
EnodebAlgoExtSwitch.NetworkPrfmOptSwitch parameter be selected.
4.2 Network Analysis
4.2.1 Benefits
Smart carrier selection based on virtual grids, ultra-low-latency scheduling for
intra-eNodeB CA, and multi-frequency optimal carrier scheduling must be enabled
together. If only one of them is enabled, the optimal effect cannot be achieved.
The benefits depend on related factors as follows:
● The larger the number of carriers on the network and the larger the
bandwidth of each carrier, the greater the benefits.
● The benefits increase when the network is neither extremely lightly loaded
nor extremely heavily loaded.
● The higher the proportion of last TTIs, the greater the benefits. The
proportion is equal to (L.Thrp.Time.DL – L.Thrp.Time.DL.RmvLastTTI)/
L.Thrp.Time.DL.
● The higher the proportion of CA transmission time, the greater the benefits.
– When the CaInstantlyJudgeSwitch option of the
CaMgtCfg.CellCaAlgoSwitch parameter is selected, the proportion of CA
transmission time is equal to L.Thrp.Time.DL.RmvLastTTI.CAUser/
L.Thrp.Time.DL.RmvLastTTI.
– When the CaInstantlyJudgeSwitch option of the
CaMgtCfg.CellCaAlgoSwitch parameter is deselected, the proportion of
CA transmission time is equal to L.Thrp.Time.DL.RmvLastTTI.CAUser/

eRAN
L.Thrp.Time.DL.RmvLastTTI/[(L.Thrp.bits.DL.CAUser/L.Thrp.bits.DL)/
(L.Traffic.User.PCell.DL.Avg/L.Traffic.User.Avg)].
Smart carrier selection based on virtual grids enables the eNodeB to select
optimal carriers or carrier combinations for UEs from multiple carriers based on
factors such as the UE-level spectral efficiency and load. Therefore, the average
downlink UE throughput increases.
Smart carrier selection based on virtual grids also enables the eNodeB to be aware
of traffic models of UEs so that carriers or carrier combinations that provide the
highest uplink and downlink throughput are selected from multiple candidates for
the UEs. However, this function of traffic model-aware smart carrier selection
slightly decreases the average downlink UE throughput across the network. When
operators intend to increase the uplink throughput of an individual UE running
large-packet uplink services, it is recommended that this function be enabled in
one of the following scenarios:
● FDD+TDD networking
● Multi-band FDD networking
● Uplink 2CC aggregation is enabled, and the numbers of aggregated carriers in
the downlink and uplink cannot simultaneously reach their respective
maximums due to UE limitations.
Ultra-low-latency scheduling for intra-eNodeB CA increases the SCell usage and
therefore raises the average downlink data rate of UEs, especially in scenarios
where service bursts are frequent.
Multi-frequency optimal carrier scheduling increases the average downlink UE
throughput on the entire network. The benefits depend on the following factors:
● The larger the number of carriers on the network and the larger the
bandwidth of each carrier, the greater the benefits.
● The larger the number of frequencies on the network and the greater the
load difference between frequencies, the greater the benefits.
● The benefits are greater in the case of medium or heavy load than in other
load cases. It is recommended that multi-frequency optimal carrier scheduling
be enabled for base stations that each have an average downlink PRB usage
greater than 20%.
● The higher the proportion of CA UEs whose SCells are configured on the same
BBP as the PCell, the greater the benefits. It is recommended that multi-
carrier unified scheduling for CA, a sub-function of multi-frequency optimal
carrier scheduling, be enabled for base stations on each of which the
proportion is greater than 70%. The proportion is equal to
L.Traffic.User.SCell.SameBBPWithPCell.DL.Avg divided by
L.Traffic.User.SCell.DL.Avg.
● The higher the proportion of CA UEs, the greater the benefits. It is
recommended that multi-carrier unified scheduling for CA, a sub-function of
multi-frequency optimal carrier scheduling, be enabled for base stations on
each of which the proportion is greater than 60%. The proportion is equal to
L.Traffic.User.PCell.DL.Avg divided by L.Traffic.User.Avg.
When the Multi-carrier Unified Scheduling feature is enabled on a multi-frequency
FDD network, it is recommended that the following functions be also enabled to
further increase the average downlink UE throughput:

eRAN
● TBS index rise for downlink HARQ retransmissions (controlled by the

PreciseMcsAdaptSwitch option of the CellAlgoSwitch.CqiAdjAlgoSwitch
parameter). For details about the principles of this function, see Scheduling.
● Downlink traffic-model-based performance optimization (controlled by the
DlPacketLenAwareSchSw option of the CellAlgoSwitch.DlSchSwitch
● Two-dimensional frequency selective scheduling (controlled by the
2D_FSS_SWITCH option of the CellAlgoExtSwitch.DlSchEnhSwitch
The Multi-carrier Unified Scheduling feature allows optimal carriers or carrier

combinations to be selected for UEs and enables optimal data split between
frequency bands, thereby increasing the average downlink UE throughput. If the
preceding listed functions are also enabled, the downlink scheduling performance
of individual frequency bands can be improved, further increasing the average
downlink UE throughput.
4.2.2 Impacts
Network Impacts
Smart carrier selection based on virtual grids has the following impacts on the
network:
● The UE distribution across frequency bands changes. Therefore, the values of
band-specific counters and indicators also change.
● The CPU usage of the main control board increases because of frequent
virtual grid model query and optimal carrier or carrier combination
evaluation.
● After this function is enabled, more resources of the main control board are
consumed. If the number of UEs is too large, congestion may occur earlier
than expected, causing the RRC connection setup success rate to decrease and
the service drop rate to increase.
● The number of handovers increases because the eNodeB needs to select
better carriers for UEs whenever there are changes such as load and
interference changes on the frequency bands.
● The number of signaling messages over the air interface and the signaling
radio bearer (SRB) traffic increase. The average MCS index may decrease
because SRBs use MCSs with small indexes. In addition, RRC connection
reconfiguration messages may fail to be sent, which increases the service drop
rate and the number of connection reestablishments.
● Due to gap-assisted inter-frequency measurements by UEs selected by the
eNodeB for virtual grid model building and updating, the uplink throughput
and downlink throughput of these UEs decrease and network interference
indicators vary slightly. As only a few UEs are selected, the impact on the
average downlink UE throughput and average uplink UE throughput is
negligible when there are more than 15 online UEs in a cell.

eRAN
● For fast-moving UEs that cannot be identified, the selected carriers or carrier
combinations may not be optimal throughout the service duration. As a
result, the throughput of such UEs may decrease.
● After the eNodeB has built virtual grid models, enhanced processing of inter-
frequency neighboring cells unknown to the eNodeB increases the success
rate of inter-frequency handovers based on virtual grids if there are unknown
neighboring cells. In addition, due to these unknown neighboring cells, the
value of the L.VirtualGrid.Model.InterFreq.MeasFree.Times counter may
slightly increase or decrease.
● The overall network resource consumption increases slightly. As a result, fewer
resources are available for UEs performing full buffer services, and the
throughput of these UEs may decrease slightly.
● In light load scenarios with a large difference in the bandwidths of frequency
bands, the positive gains of smart carrier selection based on virtual grids may
be less than the negative impacts brought by measurements. As a result, the
UE throughput decreases in such scenarios.
● The number of handovers for PCC anchoring of NSA UEs when this function
takes effect is greater than that when intelligent selection of serving cell
combinations takes effect. (The latter function is controlled by the
CaSmartSelectionSwitch option of the ENodeBAlgoSwitch.CaAlgoSwitch
parameter.)
● If there are abnormal UEs on the network, the number of RRC connection
reestablishments increases. The increase can be prevented by selecting the
SCS_FORBID_SW option of the SpidCfg.AggregationAttribute or
UeCompat.BlacklistControlExtSwitch2 parameter.
● The eNodeB does not build virtual grid models within 14 days of an eNodeB
software upgrade. However, models built before the upgrade can still be used
during this period. After the 14 days, the eNodeB restarts the model building
process. Therefore, within 14 days of the upgrade, the numbers of gap-
assisted inter-frequency measurements, air interface signaling messages, and
RRC connection reconfiguration messages may decrease, and the service drop
rate may also decrease, further leading to changes in the values of user-plane
performance indicators, such as the number of UEs, user-perceived rate, and
traffic volume.
● On a network where there are both FDD cells and TDD cells, the SCells for
individual UEs may change from FDD cells to TDD cells or from TDD cells to
FDD cells. If the FDD and TDD cells use different DRX policies, the values of
the L.Cdrx.Enter.Num (which measures the number of times UEs enter DRX)
and L.Cdrx.Exit.Num (which measures the number of times UEs exit DRX)
counters may increase.
Function Impacts
● Functions in the category "RAN functions"

eRAN
RAT Function Function Reference Description

Name Switch
FDD Fast rank RankRapidRpt None This function is

TDD reporting Switch option recommended, as it
of the helps smart carrier
CellAlgoSwitc selection based on
h.DlSchSwitch virtual grids achieve
parameter higher average
downlink data rates
of UEs. However, this
function increases
PUSCH resource
consumption and
CPU usage.
FDD CQI RptCqiFltInitS Channel This function is

TDD adjustment witch option of State recommended, as it
the Manageme helps smart carrier
CellAlgoSwitc nt selection based on
h.CqiAdjAlgoS virtual grids achieve
witch higher average
parameter downlink data rates
of UEs.
FDD Multi-band MbfcsSwitch Multi-band Both smart carrier

TDD optimal option of the Optimal selection based on
carrier CellAlgoSwitc Carrier virtual grids and
selection h.MlbAlgoSwit Selection multi-band optimal
ch parameter carrier selection
involve short-cycle
carrier selection.
When smart carrier
selection based on
virtual grids takes
effect, multi-band
optimal carrier
selection no longer
takes effect.

eRAN

Name Switch
FDD CA UE CaUserLoadTra Intra-RAT When the

TDD transfer nsferSw option Mobility CaUserLoadTrans-
switch of the Load ferSw option is
CellAlgoSwitc Balancing selected, a candidate
h.EnhancedMl cell that meets any of
bAlgoSwitch the following
parameter conditions can be
selected as the target
cell for load transfer:
● Condition 1: The
load difference
between the
serving cell and
the candidate cell
is greater than
CellMLB.UeNumD
iffThd and the air
interface capability
of the candidate
cell for CA is not
lower than that of
the serving cell for
CA.
● Condition 2: The
number of UEs in
the serving cell is
greater than the
result of
CellMLB.InterFreq
MlbUeNumThd/(
1–
CellMLB.UeNumD
iffThd –
CellMLB.UeNumD
iffOffsetTransCa),
and the UE
quantity difference
between the
serving cell and
the candidate cell
is greater than the
sum of
CellMLB.UeNumD
iffThd and
CellMLB.UeNumD
iffOffsetTransCa.
When smart carrier
selection based on
virtual grids takes

eRAN

Name Switch
effect, candidate cells

that meet only
condition 1 cannot be
selected as target
cells for load transfer.
FDD Frequency- FreqPriorIFHO Mobility If smart carrier

TDD priority- Switch option Manageme selection based on
based inter- of the nt in virtual grids and
frequency CellAlgoSwitc Connected frequency-priority-
handover h.FreqPriority Mode based inter-frequency
HoSwitch handover are both
parameter enabled, UEs may
experience ping-pong
handovers.

eRAN

Name Switch
FDD EN-DC NSA_PCC_ANC NSA On an NSA network,

TDD Optimal HORING_SWIT Networking it is recommended
Carrier CH option of based on that NSA PCC
Selection the EPC anchoring be enabled
NsaDcMgmtCo before smart carrier
nfig.NsaDcAlg selection based on
oSwitch virtual grids is
parameter enabled. In this case,
smart carrier
selection based on
virtual grids performs
only SCC selection for
NSA UEs but does not
perform PCC
anchoring for NSA
UEs.
If NSA PCC anchoring
is not enabled, smart
carrier selection
based on virtual grids
has the following
impacts:
1. Smart carrier
selection based on
virtual grids
performs both PCC
anchoring and SCC
selection for NSA
UEs. In this case, it
is possible that
SCGs cannot be
added for NSA UEs
or the SCGs added
for NSA UEs have
to be changed.
2. After an SCG is
added for an NSA
UE, smart carrier
selection based on
virtual grids
cannot accurately
evaluate the CA
capability of LTE
carriers in the NSA
DC combination.
As a result, the
optimal carrier
combination for

eRAN

Name Switch
CA may not be
configured for the
UE on the LTE side.
FDD PCC CaTrafficTrigg Carrier It is not

TDD anchoring erSwitch Aggregatio recommended that
for CA UEs option of the n smart carrier
ENodeBAlgoS selection based on
witch.CaAlgoS virtual grids and PCC
witch anchoring for CA UEs
parameter be both enabled. If
they are both
enabled, UEs may
experience ping-pong
handovers.
FDD NSA NSA_DC_CAPA NSA Select the

TDD Networking BILITY_SWITC Networking LTE_SCELL_MEAS_OP
based on H option of the based on T_SW option of the
EPC NsaDcMgmtCo EPC EnodebAlgoExtSwitc
nfig.NsaDcAlg h.NsaDcAlgoSwitch
oSwitch parameter when
parameter smart carrier
selection based on
virtual grids takes
effect. Then the
duration of a single
round of LTE SCell
measurements for a
UE in the NSA DC
state can be specified
by the
NsaDcMgmtConfig.
NsaDcLteScellMeas-
Duration parameter.

eRAN

Name Switch
FDD Service- ServiceBasedIn Mobility When the

TDD based inter- terFreqHoSwit Manageme SMART_CARRIER_SE
frequency ch option of nt in LECTION_OPT_SW
handover the Connected option of the
ENodeBAlgoS Mode MultiCarrUnifiedSch.
witch.HoAlgoS MultiCarrierUni-
witch fiedSchSw parameter
parameter is selected and smart
SrvBasedInterF carrier selection is
reqHoSw triggered for CA UEs,
option of the the eNodeB
CellAlgoSwitc preferentially selects
h.HoAllowedS the carrier
witch combination in which
parameter the PCell works on
the target frequency
expected to carry
certain services.

eRAN

Name Switch
FDD SPID- SpidCfg.RatFre Flexible After smart carrier

TDD specific cell qPriorityInd User selection based on
reselection Steering virtual grids is
enabled, the cells
corresponding to the
optimal carriers or
carrier combinations
selected by the
eNodeB for UEs with
specific SPIDs are not
the cells on which the
UEs are camping. To
prevent smart carrier
selection based on
virtual grids from
affecting the camping
policies for these UEs,
it is recommended
that the following
options be selected:
● SMART_CARRIER_
SELECTION_OPT_
SW option of the
MultiCarrUnifiedS
ch.MultiCarrierUn
ifiedSchSw
parameter. If this
option is selected
and a cell
reselection policy
specific to the
SPID of a non-CA
UE has been
configured, smart
carrier selection
will not be
triggered for the
UE during initial
access.
● SCS_PCC_ANCHO
R_OPT_SW option
of the
MultiCarrUnifiedS
ch.MultiCarrierUn
ifiedSchEnSw
parameter. If this
option is selected
and a cell

eRAN

Name Switch
reselection policy
specific to the
SPID of a CA UE
has been
configured, PCC
anchoring will not
be triggered for
the UE during
initial access.
FDD Inter- RelaxedBackh Carrier When both traffic

TDD eNodeB aulCaSwitch Aggregatio model-aware smart
uplink 2CC option of the n carrier selection and
aggregation ENodeBAlgoS inter-eNodeB uplink
based on witch.CaAlgoS 2CC aggregation
relaxed witch based on relaxed
backhaul parameter backhaul are enabled,
CaMgtCfg.Rela the eNodeB acts as
xedBHCaUlMa follows during carrier
xCcNum set to evaluation based on
2CC uplink air interface
capabilities: If two
inter-eNodeB uplink
CCs have been
configured for a UE,
the eNodeB considers
the uplink air
interface capability of
the PCell only, when
it calculates the
capability of the
serving cell
combination for the
UE. As a result, an
incorrect handover
occurs because the
calculated air
interface capability of
the serving cell
combination is less
than the actual
capability. You are
advised not to enable
both of the functions.

eRAN

Name Switch
FDD Flexible CA MultiCarrierFl Carrier When smart carrier

TDD exCaSwitch Aggregatio selection based on
option of the n virtual grids takes
CaMgtCfg.Cell effect, flexible CA no
CaAlgoSwitch longer takes effect. In
parameter this case, smart
carrier selection
based on virtual grids
takes effect for CA
UEs.
FDD Guaranteed- GUARANTEED_ Intra-RAT You are advised not

TDD UE-based UE_MLB_SWIT Mobility to enable both
load CH option of Load guaranteed-UE-based
equalization the Balancing load equalization and
CellMLB.Enhan smart carrier
cedMlbAlgoEx selection based on
tSwitch virtual grids. If they
parameter are both enabled,
ping-pong handovers
occur.
FDD Adaptive TM4_TM9_AD Massive After adaptive

TM4/TM9 APTIVE_LAYER MIMO TM4/TM9 layering
layering ING_SW option (FDD) takes effect, the
of the CaMgtCfg.MassiveM
CellMimoPara imoGainCoefficient
Cfg.AdaptiveL parameter of smart
ayeringSwitch carrier selection does
parameter not take effect.
Instead, the
CaMgtCfg.Tm9GainC
oefficient parameter
takes effect.
● Functions related to CIoT

Name Switch
FDD eMTC EMTC_ONLY_C eMTC eMTC UEs are not

introduction ELL_SWITCH selected for virtual
option of the grid model building.
CellEmtcAlgo. Smart carrier
EmtcAlgoSwit selection is not
ch parameter performed for eMTC
UEs. Virtual grid
models cannot be
built for eMTC-only
cells.

eRAN
● Functions related to energy saving

Name Switch
FDD Intelligent CellShutdown. Energy The progress of

TDD power-off of CellShutdown Conservatio virtual grid model
carriers in Switch set to n and building will be
the same ON Emission affected after
coverage Reduction intelligent power-off
of carriers in the
same coverage takes
effect.
FDD Dynamic CARRIER_DYN_ Energy The progress of

TDD carrier SHUTDOWN_S Conservatio virtual grid model
shutdown W option of n and building will be
the Emission affected after
CellShutdown. Reduction dynamic carrier
CarrierShutdo shutdown takes
wnEnhancedS effect.
w parameter
FDD Multi-carrier CellShutdown. Energy The progress of
TDD coordinated CellShutdown Conservatio virtual grid model
energy Switch set to n and building will be
saving ON_MULTI_CA Emission affected after multi-
RRIER_HIER_S Reduction carrier coordinated
HUTDOWN energy saving takes
effect.
FDD RF module eNodeBAutoP Energy The progress of

regular time owerOff.AutoP Conservatio virtual grid model
sleep owerOffSwitch n and building will be
set to ON Emission affected after RF
Reduction module regular time
sleep takes effect.
FDD Automatic CellAutoShutd Energy The progress of

TDD cell own.CellAutoS Conservatio virtual grid model
shutdown hutdownSwitc n and building will be
h set to ON Emission affected after
Reduction automatic cell
shutdown takes
effect.
FDD Low power CellLowPower. Energy The progress of

TDD consumptio LowPwrSwitch Conservatio virtual grid model
n mode n and building is affected
Emission after low power
Reduction consumption mode
takes effect.

eRAN

Name Switch
FDD Intelligent InterRatCellSh Energy The progress of

power-off of utdown.ForceS Conservatio virtual grid model
carriers in hutdownSwitc n and building will be
the same h set to ON Emission affected after
coverage of Reduction intelligent power-off
UMTS of carriers in the
network same coverage as
UMTS networks takes
effect.
FDD pRRU deep ● RRU.DORM Energy The progress of

TDD dormancy ANCYSW Conservatio virtual grid model
set to ON n and building will be
● EnodebMpr Emission affected after pRRU
uEs.MpruDo Reduction deep dormancy takes
rmancyDlEa effect.
rfcn set to a
value other
than -1
● UE_DET_PR
RU_DEEP_D
ORMANCY_
SW option
of the
EnodebMpr
uEs.Dorman
cyAlgoSwitc
h parameter
selected
FDD GUL joint ● InterRatCell Multi-RAT The progress of

TDD carrier Shutdown.F Coordinate virtual grid model
shutdown orceShutdo d Energy building will be
wnSwitch Saving affected after GUL
set to ON joint carrier shutdown
● InterRatCell takes effect.
Shutdown.S
hutDownTy
pe set to
BY_UTRAN_
WITH_LOA
D

eRAN

Name Switch
FDD Cell switch- CellShutdown. Energy The progress of

TDD off based on CellShutdown Conservatio virtual grid model
automatic Switch set to n and building will be
co-coverage ON_CO_COV_A Emission affected after cell
identificatio UTO_IDENT Reduction switch-off based on
n automatic co-
coverage
identification takes
effect.
FDD UL CellRfShutdow Multi-RAT The progress of

coordinated n.MultiRatJoin Coordinate virtual grid model
channel tChnShutdown d Energy building will be
shutdown Sw Saving affected after UL
coordinated channel
shutdown takes
effect.
TDD RF module RRU.DORMAN Multi-RAT The progress of

deep CYSW Coordinate virtual grid model
dormancy d Energy building will be
Saving affected after RF
module deep
dormancy takes
effect.
FDD RF channel RF_CHN_DYN_ Energy Sample collection for

TDD dynamic MUTING_SW Conservatio virtual grid models of
muting option of the n and neighboring cells will
CellRfChnDyn Emission be affected after RF
Muting.RfChn Reduction channel dynamic
DynMutingAlg muting takes effect.
oSwitch
parameter
FDD Dynamic CellPwrSaving Energy The progress of

TDD carrier Algo.CarrierDy Conservatio virtual grid model
shutdown nShutdownPh n and building will be
phase 2 2Sw Emission affected after
Reduction dynamic carrier
shutdown phase 2
takes effect.
4.2.2.2 Ultra-Low-Latency Scheduling for Intra-eNodeB CA
Network Impacts
Ultra-low-latency scheduling for intra-eNodeB CA has the following impacts on
the network:

eRAN
● The traffic distribution across frequency bands changes. Therefore, the values
of band-specific performance indicators also change.
● The traffic distribution between CA UEs and non-CA UEs changes. Therefore,
performance indicators specific to CA UEs and those specific to non-CA UEs
also change.
● The CPU usage of the BBP increases. If the average CPU usage of the BBP
exceeds 50% or the maximum CPU usage of the BBP exceeds 65%, it is
recommended that this function not be enabled.
● The number of UEs for which CA is activated increases. In the case of inter-
base-station CA, the amount of scheduling information exchanged between
the PCC and inter-base-station SCCs increases, causing the usage of inter-
base-station transmission resources to increase correspondingly. The values of
the following related counters increases: L.TRPIP.X2UTxBytes and
L.TRPIP.X2URxBytes, which respectively measure the numbers of bytes
transmitted and received on the user plane of the X2 interface;
VS.FEGE.TxBytes and VS.FEGE.RxBytes, which respectively measure the
numbers of bytes transmitted and received over the FE/GE ports;
VS.FEGE.TxMaxSpeed and VS.FEGE.RxMaxSpeed, which respectively measure
the maximum Tx and Rx rates over the FE/GE ports. When the proportion of
UEs in the inter-base-station CA state is high, the usage of transmission
resources increases significantly.
● The volume of data distributed to SCells increases, which causes the following
impacts:
– The overhead of uplink and downlink control channels slightly increases.
– In some scenarios, NACKs and DTXs in feedback from CA UEs cannot be
distinguished from each other. As a result, the RBLER and service drop
rate increase.
● After this function is enabled, the downlink rate on the LTE side increases. As
a result, in EN-DC scenarios, more data is distributed from the PDCP layer to
the LTE side, causing changes in the downlink rates on the NR side.
Function Impacts
Name Switch
FDD MCS CellDlschAlgo.R Scheduling Ultra-low-latency

TDD selection BPriMcsSelectSt scheduling for intra-
with rategy eNodeB CA changes
prioritized the proportion of CA
RBs UE data packets
distributed to each CC.
With the change in the
number of transport
blocks (TBs), which
affects MCS selection
with prioritized RBs,
the MCS changes.

eRAN

Name Switch
FDD Inter-eNodeB FreqCfgCaOver Carrier Ultra-low-latency

TDD CA based on BBUsSwitch Aggregation scheduling for intra-
eNodeB option of the eNodeB CA changes
coordination ENodeBAlgoSwi the proportion of CA
tch.OverBBUsS UE data packets
witch distributed to each CC.
parameter Therefore, the
transport load
changes.
FDD Inter-eNodeB RelaxedBackha Carrier Ultra-low-latency

TDD CA based on ulCaSwitch Aggregation scheduling for intra-
relaxed option of the eNodeB CA changes
backhaul ENodeBAlgoSwi the proportion of CA
tch.CaAlgoSwit UE data packets
ch parameter distributed to each CC.
Therefore, the
transport load
changes.

eRAN

Name Switch
FDD Energy SymbolPwrSavi Energy If the PCell is not

TDD saving based ng.TrigBndlSch Conservatio heavily loaded and
on proactive DlAvgPrbThld n and both energy saving
scheduling set to a non- Emission based on proactive
zero value Reduction scheduling and precise
scheduling for CA UEs
FDD Precise CaEnhancedPre Carrier have taken effect,
TDD scheduling AllocSwitch Aggregation enabling ultra-low-
for CA UEs option of the latency scheduling for
ENodeBAlgoSwi intra-eNodeB CA may
tch.CaAlgoExtS slow down data
witch transmission for CA
parameter UEs, leading to a
decrease in the
downlink user-
perceived rate. The
specific causes are as
follows:
● After energy saving
based on proactive
scheduling takes
effect, scheduling in
the PCell may be
delayed.
● Compared with
precise scheduling
for CA UEs, data
split with ultra-low
latency reduces the
amount of data
distributed to SCells.
4.2.2.3 Ultra-Low-Latency Scheduling for Inter-eNodeB CA Based on Relaxed

Backhaul
Network Impacts
Ultra-low-latency scheduling for inter-eNodeB CA based on relaxed backhaul has
the following impacts on the network:
● The traffic distributions on frequency bands change. As a result, the values of
band-specific performance indicators also change.
● The CPU usage of the BBP slightly increases. When the CPU usage of the BBP
is greater than 60%, this function is not recommended.
● This function is not recommended when the entire network is heavily loaded,
for example, when the downlink PRB usage in each of the PCell and SCells
exceeds 70%.

eRAN
● When the load of SCells for inter-eNodeB CA based on relaxed backhaul is not
heavy, the volume of data distributed to the SCells increases, which has the
following impacts:
– The uplink and downlink control channel resource consumption increases
slightly. As a result, fewer resources are available for unidentified UEs
performing full buffer services, and the throughput of these UEs may
decrease slightly.
rate increase.
● When the load of SCells for inter-eNodeB CA based on relaxed backhaul is
heavy, the traffic volumes in these SCells decrease.
Function Impacts
None
4.2.2.4 Multi-Frequency Optimal Carrier Scheduling
Network Impacts
Multi-frequency optimal carrier scheduling has the following impacts on the
network:
● The traffic distribution across frequency bands changes. Therefore, the values
of band-specific performance indicators also change.
● The traffic distribution between CA UEs and non-CA UEs changes. Therefore,
performance indicators specific to CA UEs and those specific to non-CA UEs
also change.
● The volume of data distributed to SCells increases, which causes the following
impacts:
– The uplink and downlink control channel resource consumption increases
slightly. As a result, fewer resources are available for unidentified UEs
performing full buffer services, and the throughput of these UEs may
decrease slightly.
rate increase.

eRAN
Function Impacts
RAT Function Function Switch Reference Description
Name
FDD Basic CellDlschAlgo.D Scheduling When scheduling

TDD Scheduling lschStrategy priority optimization
for CA is enabled, it is
recommended that
the
CellDlschAlgo.DlschS
trategy parameter be
set to
DLSCH_PRI_TYPE_EPF
for both the PCell and
SCells. Otherwise,
user-perceived rates
may be affected.
FDD Dynamic LTE_DYN_POWE Dynamic When multi-carrier

TDD Power R_SHARING_SW Power unified scheduling for
Sharing option of the Sharing CA and Dynamic
Between LTE CellDynPowerS Between LTE Power Sharing
Carriers haring.Dynamic Carriers Between LTE Carriers
PowerSharingS are both enabled, it is
witch parameter possible that their
benefits cannot be all
obtained.
FDD Extreme LTE_EXTREME_P Dynamic When multi-carrier

power OWER_SHARIN Power unified scheduling for
sharing G_SW option of Sharing CA and extreme
the Between LTE power sharing are
CellDynPowerS Carriers both enabled, it is
haring.Dynamic possible that their
PowerSharingS benefits cannot be all
witch parameter obtained.

eRAN

Name
FDD Downlink FreqSelSwitch Scheduling If a high proportion of

TDD frequency option of the PRBs on the network
selective CellAlgoSwitch. are used for frequency
scheduling DlSchSwitch selective scheduling,
parameter the benefits of multi-
carrier unified
scheduling for CA
decrease.
For FDD, the
MultiCarrUnifiedSch.
FssPrbRatioThld
parameter specifies
the threshold, which is
the proportion of
PRBs used for
frequency selective
scheduling, used in
multi-carrier unified
scheduling for CA. If
the proportion of
PRBs used for
frequency selective
scheduling is less than
or equal to this
threshold, the eNodeB
is allowed to schedule
data based on the
scheduling capabilities
of CCs in real time
during multi-carrier
unified scheduling for
CA. If the proportion
of PRBs used for
frequency selective
scheduling is greater
than this threshold,
the eNodeB is not
allowed to schedule
data based on the
scheduling capabilities
of CCs in real time
during multi-carrier
unified scheduling for
CA.

eRAN

Name
FDD CCE-usage- CellDlschAlgo.D Carrier When both multi-

based ataSplitCceUsag Aggregation carrier unified
downlink eHighThld scheduling for CA and
data split for CCE-usage-based
CA UEs downlink data split for
CA UEs are enabled,
CCE-usage-based
downlink data split for
CA UEs preferentially
takes effect in
downlink data split for
CA UEs, decreasing
the benefits of multi-
carrier unified
scheduling for CA.
FDD Downlink EmimoMuMimo eMIMO If a high proportion of

MU-MIMO Switch and (FDD) UEs are paired for
4TxTM9MuMim MU-MIMO, the
oSwitch options benefits of multi-
of the carrier unified
CellAlgoSwitch. scheduling for CA
EmimoSwitch decrease.
parameter
4.3 Requirements
4.3.1 Licenses
Multi-carrier Unified Scheduling requires the feature licenses listed in Table 4-10
and capacity licenses listed in Table 4-11.
Table 4-10 Feature licenses

RAT Feature ID Feature Name Model Sales Unit
FDD LNOFD-151332 Multi-carrier LT1SMCUSP1 per eNodeB

Unified 00
Scheduling
TDD TDLNOFD-1515 Multi-carrier LT4SMCUSPT per eNodeB

06 Unified DD
Scheduling

eRAN
Table 4-11 Capacity licenses

RAT Description Model Sales Unit
FDD Vertical SuperBAND LT1SVSBAND00 per eNodeB

(FDD)
TDD Vertical SuperBAND LT4SVSPBDTDD per eNodeB

(TDD)
NOTE
If both FDD and TDD cells exist on the base station, apply for licenses for both FDD and
TDD.
4.3.2 Software

Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated, if there are any.
For detailed operations, see the relevant feature documents.
Prerequisite Functions
RAT Function Name Function Switch Reference
FDD Downlink CA Downlink CA works in Carrier Aggregation

TDD multiple scenarios
where different
numbers of CCs are
aggregated. Its function
switch varies depending
on the scenarios. Smart
carrier selection
requires that CA work
in adaptive
configuration mode
rather than CA-group-
based configuration
mode. For details, see
Carrier Aggregation.

eRAN
Mutually Exclusive Functions

FDD Intelligent selection CaSmartSelectionS- Carrier Aggregation

TDD of serving cell witch option of the
combinations ENodeBAlgoSwitch.Ca
AlgoSwitch parameter
4.3.2.2 Ultra-Low-Latency Scheduling for Intra-eNodeB CA

FDD Downlink CA Downlink CA works in Carrier Aggregation

TDD multiple scenarios
where different
numbers of CCs are
aggregated. Its function
switch varies depending
on the scenarios. For
details about the
function switches and
their configurations, see

None
4.3.2.3 Ultra-Low-Latency Scheduling for Inter-eNodeB CA Based on Relaxed

Backhaul

eRAN
FDD Ultra-low-latency ULTRA_LOW_LATENCY Multi-carrier Unified

TDD scheduling for intra- _SCH_SW option of the Scheduling
eNodeB CA MultiCarrUnifiedSch.M
ultiCarrierUnifiedSchS
w parameter
FDD Inter-eNodeB CA RelaxedBackhaulCaS- Carrier Aggregation
TDD based on relaxed witch option of the
backhaul ENodeBAlgoSwitch.Ca
TDDRelaxedBackhaul-
CaSwitch option of the
ENodeBAlgoSwitch.Ca
FreqBaseIntereNBSccS-
witch option of the
ENodeBAlgoSwitch.Ca
AlgoExtSwitch
parameter

FDD TDM TDM_SWITCH option NSA Networking

of the based on EPC
NsaDcMgmtConfig.Ns
aDcAlgoSwitch
parameter
TDD None None None
4.3.2.4 Multi-Frequency Optimal Carrier Scheduling


eRAN
Name
FDD Ultra-low- ULTRA_LOW_LATENCY Multi-carrier Before

TDD latency _SCH_SW option of the Unified scheduling
scheduling MultiCarrUnifiedSch. Scheduling priority
for intra- MultiCarrierUni- optimization
eNodeB CA fiedSchSw parameter for CA and
multi-carrier
unified
scheduling
for CA
(subfunctions
of multi-
frequency
optimal
carrier
scheduling)
can be
enabled,
ultra-low-
latency
scheduling
for intra-
eNodeB CA
must be
enabled.

eRAN

Name
FDD Scheduling CA_SCH_PRIORITY_OP Multi-carrier Before multi-

priority T_SW option of the Unified carrier
optimization MultiCarrUnifiedSch. Scheduling unified
for CA MultiCarrierUnified- scheduling
SchEnSw parameter for CA (a
subfunction
of multi-
frequency
optimal
carrier
scheduling)
cab be
enabled,
scheduling
priority
optimization
for CA
(another
subfunction
of multi-
frequency
optimal
carrier
scheduling)
must be
enabled.
FDD Downlink CA Downlink CA works in Carrier None

TDD multiple scenarios Aggregation
where different
numbers of CCs are
aggregated. Its
function switch varies
depending on the
scenarios. For details
about the function
switches and their
configurations, see

None

eRAN
4.3.3 Hardware
Base Station Models

● 3900 and 5900 series base stations (macro base stations)
● DBS3900 LampSite and DBS5900 LampSite
Boards
● Smart carrier selection
– Main control boards: UMPTb series or later boards are required.
– BBPs: no requirements
● Ultra-low-latency scheduling for intra-eNodeB CA
– BBPs: The LBBP is incompatible with ultra-low-latency scheduling for
intra-eNodeB CA. In a base station equipped with both the UBBP and
LBBP, some CCs may be served by the UBBP while others by the LBBP.
This decreases the performance gains brought by this function.
● Ultra-low-latency scheduling for inter-eNodeB CA based on relaxed backhaul
– BBPs: Ultra-low-latency scheduling for inter-eNodeB CA based on relaxed
backhaul does not take effect on any base station equipped with both
the UBBP and LBBP.
● Multi-frequency optimal carrier scheduling
– BBPs:
Multi-carrier unified scheduling for CA takes effect only for CA UEs whose
SCells are configured on the same BBP as the PCell.
In TDD, multi-carrier unified scheduling for CA does not take effect when
the UBBPd or LBBP is used.
In FDD, multi-carrier unified scheduling for CA does not take effect when
the LBBP is used.
However, when the UBBPe is used, multi-carrier unified scheduling for CA
does not take effect for CA UEs in the FDD+TDD CA state even if the
serving FDD and TDD cells are all configured on the UBBPe.
RF Modules
No requirements
4.3.4 Networking
The network has at least two carriers.
The X2 interface between eNodeBs must be working properly, as this interface is

required for load information transfer.

eRAN
4.3.5 Others
Smart carrier selection based on virtual grid is not recommended in the following
scenarios:
● In high-speed mobility scenarios such as high-speed railway dedicated
networks, it is recommended that this function be disabled. This is to prevent
network performance deterioration because of inaccurate cell capability
evaluation due to fast UE mobility.
● During key event assurance, it is recommended that this function be disabled.
This is to prevent network performance deterioration due to the increase in
the CPU usage and SRB traffic.
● During long-term network reconstruction, it is recommended that this
function be disabled or both the
MultiCarrUnifiedSch.VgModelPredHoMeasRsrpThld and
MultiCarrUnifiedSch.VgMdlPredNecHoMeasRsrpThld parameters be set to
ACCURACY100_OFFSET0 to prevent network performance deterioration
caused by a decrease in the prediction accuracy of virtual grid models.
● On a network where cells are frequently activated and deactivated, it is
recommended that the VG_MODEL_FORBID_BUILD_FLAG option of the
EutranInterNFreq.AggregationAttribute parameter be selected to forbid
virtual grid model building.
4.4.1 Data Configuration
4.4.1.1 Data Preparation

Table 4-12 describes the parameters used for function activation.
Table 4-12 Parameters used for activation
Parameter Parameter Option Setting Notes

Name ID
Multi-Carrier MultiCarrUn SMART_CARRI Select this option.

Unified Sch ifiedSch.Mul ER_SELECTIO
Switch tiCarrierUnif N_SW
iedSchSw
Multi-Carrier MultiCarrUn SMART_CARRI Select this option.
Unified Sch ifiedSch.Mul ER_SELECTIO
Switch tiCarrierUnif N_ENH_SW
iedSchSw
Multi-Carrier MultiCarrUn SPECTRUM_E Select this option.
Unified Sch ifiedSch.Mul FF_EVALUATI
Switch tiCarrierUnif ON_OPT_SW
iedSchSw

eRAN

Name ID
Multi-Carrier MultiCarrUn DL_UU_CAPB_ Select this option.

Unified Sch ifiedSch.Mul EVAL_OPT_S
Switch tiCarrierUnif W
iedSchSw
Multi-Carrier MultiCarrUn VG_MDL_PRE Select this option.
Unified Sch ifiedSch.Mul D_NCELL_EN
Switch tiCarrierUnif H_SW
iedSchSw
Multi-Carrier MultiCarrUn VG_MDL_CO Select this option.
Unified Sch ifiedSch.Mul ORDINATE_T
Switch tiCarrierUnif RAIN_SW
iedSchSw
Multi-Carrier MultiCarrUn VG_MDL_ACC Select this option.
Unified Sch ifiedSch.Mul URACY_ADAP
Switch tiCarrierUnif T_SW
iedSchSw
Multi-Carrier MultiCarrUn INTER_ENB_V Set this parameter based on
Unified Sch ifiedSch.Mul G_MDL_PRI_B the network plan.
Switch tiCarrierUnif UILD_SW
iedSchSw
Multi-Carrier MultiCarrUn INTRAF_EFF_ Select this option.
Unified Sch ifiedSch.Mul MDL_PRI_BUI
Switch tiCarrierUnif LD_SW
iedSchSw
Multi-Carrier MultiCarrUn INTER_ENB_U Select this option.
Unified ifiedSch.Mul LTRA_LOW_L
Scheduling Enh tiCarrierUnif ATENCY_SW
Switch iedSchEnSw
Multi-Carrier MultiCarrUn CA_SCH_PRIO Select this option.
Unified ifiedSch.Mul RITY_OPT_SW
Scheduling Enh tiCarrierUnif
Switch iedSchEnSw
Multi-Carrier MultiCarrUn CA_MULTI_CA Select this option.
Unified ifiedSch.Mul RR_UNIFIED_
Scheduling Enh tiCarrierUnif SCH_SW
Switch iedSchEnSw
Network EnodebAlgo UBBPD_SCH_ Select this option when a
Performance ExtSwitch.N FUNCTION_E UBBPd is used. This option
Optimization etworkPrfm NH_SWITCH applies only to FDD cells.
Switch OptSwitch

eRAN

Name ID
Multi-Carrier MultiCarrUn UL_CARR_SEL Select this option. This option

Unified ifiedSch.Mul _ENH_SW applies only to TDD cells.
Switch iedSchEnSw
Multi-Carrier MultiCarrUn LOAD_BASED Select this option.
Unified ifiedSch.Mul _CARR_SEL_O
Scheduling Enh tiCarrierUnif PT_SW
Switch iedSchEnSw
Multi-Carrier MultiCarrUn HIGH_LOAD_ Select this option.
Unified ifiedSch.Mul CELL_FILTER_
Scheduling Enh tiCarrierUnif SW
Switch iedSchEnSw
Service Mode eNodeBRes UMPTB_ENH Select this option when the
ModeAlgo.S ANCEMENT_S main control board of the
erviceMode WITCH base station is UMPTb.
Service Mode eNodeBRes AI_ENHANCE Select this option when the

ModeAlgo.S MENT_OPT_S main control board of the
erviceMode WITCH base station is UMPTe or
UMPTga.
Service Mode eNodeBRes UMPTG_ENH Select this option when the

ModeAlgo.S ANCEMENT_S main control board of the
erviceMode WITCH base station is UMPTg.
Application ID Application. None After the eNodeB service

AID running mode is set, the
corresponding application
must be restarted to make the
setting take effect.
CA Algorithm ENodeBAlgo FreqCfgSwitch Select this option.

Switch Switch.CaAl
goSwitch
CA and MIMO CaMgtCfg.C None Use the recommended value.
Priority aMimoPriori
Strategy Switch tyStrategyS
w
CA Traffic CaMgtCfg.C None Use the recommended value.
Direction aTrafficDire
Preference ctionPref
Min DL CaMgtCfg.M None It is recommended that this
Average To-Be- inDlAvgToB parameter be set to 255 when
Scheduled UE eScheduled the Multi-carrier Unified
Number UeNum Scheduling feature is enabled.

eRAN

Name ID
Virtual Grid MultiCarrUn None It is recommended that this

Mdl Pred ifiedSch.Vg parameter be set to
Unnec HO ModelPredH ACCURACY100_ENH to
Meas RSRP oMeasRsrpT reduce the impact of the
Thld hld Multi-carrier Unified
Scheduling feature on the
handover success rate.

Mdl Pred Nec ifiedSch.Vg parameter be set to
HO Meas RSRP MdlPredNec ACCURACY100_ENH to
Thld HoMeasRsr reduce the impact of the
pThld Multi-carrier Unified
Scheduling feature on the
handover success rate.

Model Pred ifiedSch.Vg parameter be set to
SCC Meas ModelPredS ACCURACY80_OFFSET5 to
RSRP Thld ccMeasRsrp reduce the number of gap-
Thld assisted measurements
introduced after the Multi-
carrier Unified Scheduling
feature is enabled.
Intra-Freq MultiCarrUn None It is recommended that this

Measurement ifiedSch.Intr parameter be set to 160MS
A3 Time-to- aFreqMeasA when the Multi-carrier Unified
Trigger 3TimeToTrig Scheduling feature is enabled.
Cell Level CA CaMgtCfg.C RcvA2CfgSccS When smart carrier selection

Algorithm ellCaAlgoS witch is enabled, it is recommended
Switch witch that this option be deselected
to reduce the service drop rate
of CA UEs under weak
coverage.
RsvSw10 eNBCellRsv BIT2 When smart carrier selection

dPara.RsvdS is enabled, it is recommended
wPara10 that this option be selected to
reduce the service drop rate of
non-CA UEs under weak
coverage.
MLB Match CellMlbHo. HoAdmitSwitc Deselect this option.

Other Feature MlbMatchO h
Mode therFeature
Mode

eRAN

Name ID
MLB Match CellMlbHo. X2RoHoAdmit Deselect this option.

Other Feature MlbMatchO Switch
Mode therFeature
Mode
CQI Adjust CellAlgoSwi RptCqiFltInitS Select this option.
Algorithm tch.CqiAdjAl witch
Switch goSwitch
Carrier MultiCarrUn None The value 20 is recommended.
Capability ifiedSch.Car
Hysteresis rierCapabilit
yHysteresis
Bandwidth MultiCarrUn None The value 50 is recommended.
Hysteresis ifiedSch.Ban
dwidthHyst
eresis
SCC CaMgtCfg.S None The value 30 is recommended.
Configuration ccCfgInterva If this parameter is set to a
Interval l smaller value, the number of
signaling messages may
significantly increase, and
therefore the service drop rate
increases, but SCells can be
configured in a more timely
manner for fast-moving UEs.
Uplink CellAlgoSwi SrbProbeSchS Select this option.

Schedule tch.UlSchExt witch
Extended Switch
Switch
Protocol GlobalProcS HoWithSccMi Select this option.

Compatibility witch.Protoc moModifySwi
Switch olCompatibi tch
litySw
Multi-Carrier MultiCarrUn ULTRA_LOW_ Select this option.
Unified Sch ifiedSch.Mul LATENCY_SC
Switch tiCarrierUnif H_SW
iedSchSw
SCell CellMultiCa None It is recommended that this
Deactivation rrUniSch.Sce parameter be set to 10 to
Waiting Timer llDeactvWai increase the probability that
tingTimer ultra-low-latency scheduling
for CA takes effect.

eRAN

Name ID
Service CellAlgoSwi VoiceDataDiff It is recommended that this

Differentiated tch.ServiceD erentiationSwi option be selected to reduce
Switch iffSwitch tch the voice packet loss rate.
VoLTE Packet CellDrxPara. None The value 3 is recommended

Loss Rate Thld VoltePlrThld to reduce the voice packet loss
for Exiting DRX ForExitingDr rate.
x
CA DRX CellDrxPara. PCC_SCC_DRX Select this option.
Optimization CaDrxOptS _STATE_SYNC
Switch witch _SW
CA Algorithm ENodeBAlgo SmartCaPccSe It is recommended that this

Extend Switch Switch.CaAl lSwitch option be deselected.
goExtSwitch
G Factor Thld MultiCarrUn None Set this parameter based on
for Handover ifiedSch.GFa the network plan.
Target Cell ctorThldFor
HoTrgCell
A1 RSRP CaMgtCfg.E None Set this parameter based on
Threshold for nhancedScc the network plan.
Enhanced SCC SelA1ThldRs
Selection rp
Multi-Carrier MultiCarrUn SCC_CARR_CA Set this option based on the
Unified Sch ifiedSch.Mul PB_WITH_MM network plan.
Switch tiCarrierUnif _GAIN_SW
iedSchSw
Massive MIMO CaMgtCfg.M None Use the recommended value.
Gain assiveMimo
Coefficient GainCoeffici
ent
PUCCH CellAlgoSwi Dl2CCAckResS Select this option.
algorithm tch.PucchAl hareSw
switch goSwitch
SRI Algorithm CellPucchAl SriPeriodCfgO Select this option.
Switch go.SriAlgoS ptSW
witch
Cell Level CA CaMgtCfg.C CaInstantlyJu Select this option.
Algorithm ellCaAlgoS dgeSwitch
Switch witch

eRAN

Name ID
Cell Level CA CaMgtCfg.C 2CCDlCaEnha Select this option if there are

Algorithm ellCaAlgoS nceSwitch no UE compatibility issues. If
Switch witch there are such issues, you are
advised to deselect this option
to prevent the service drop
rate from increasing.
CA Active CaMgtCfg.A None It is recommended that this

Buffer Length ctiveBufferL parameter be set to 1 to
Threshold enThd increase the probability that
ultra-low-latency scheduling
CA Active CaMgtCfg.A None It is recommended that this

Buffer Delay ctiveBufferD parameter be set to 3 to
Threshold elayThd increase the probability that
ultra-low-latency scheduling
Multi-Carrier MultiCarrUn NON_CA_SCS Set this option based on the

Unified Sch ifiedSch.Mul _SCOPE_SW network plan.
Switch tiCarrierUnif
iedSchSw
Multi-Carrier MultiCarrUn TRAFFIC_AWA Set this option based on the
Unified Sch ifiedSch.Mul RENESS_SCS_ network plan.
Switch tiCarrierUnif SW
iedSchSw
Multi-Carrier MultiCarrUn TRAFFIC_AWA Set this option based on the
Unified Sch ifiedSch.Mul RENESS_SCS_ network plan.
Switch tiCarrierUnif OPT_SW
iedSchSw
Multi-Carrier MultiCarrUn INTER_ENB_U Set this option based on the
Unified Sch ifiedSch.Mul L_UU_CAPB_E network plan.
Switch tiCarrierUnif VAL_SW
iedSchSw
Uplink Carrier MultiCarrUn None The value 20 is recommended.
Capability ifiedSch.UlC
Hysteresis arrierCapabi
lityHyst
Multi-Carrier MultiCarrUn FAST_TRAFFIC Set this option based on the
Unified ifiedSch.Mul _AWARENESS network plan.
Scheduling Enh tiCarrierUnif _SCS_SW
Switch iedSchEnSw

eRAN

Name ID
Traffic Mode CellMultiCa None Use the recommended value.

Exit Period rrUniSch.Traff
Number icModeExitP
eriodNum
Uplink Traffic CellMultiCa None Use the recommended value.
Volume rrUniSch.UlT
Threshold rafficVolum
eThld
Downlink CellMultiCa None Use the recommended value.
Traffic Volume rrUniSch.DlT
Threshold rafficVolum
eThld
Virtual Grid CellMultiCa None Use the recommended value.
Model Build UL rrUniSch.Vg
Traffic Thld MdlBuildUlT
rafficThld
Predictive MultiCarrUn None Use the recommended value.
Capability Gain ifiedSch.Pre
Threshold dictiveCapb
GainThld
Multi-Carrier MultiCarrUn SCC_ADAPT_C Select this option.
Unified Sch ifiedSch.Mul OV_THLD_SW
Switch tiCarrierUnif
iedSchSw
SCC Adapt Cov CellMultiCa None Set this parameter based on
RSRP Thld rrUniSch.Scc the network plan.
AdaptCovRs
rpThld
Cell Multi- CellMultiCa INB_SCELL_DL Select this option.
Carrier Unified rrUniSch.Cel Y_DEACTV_F
Sch Switch lMultiCarrU ORBID_SW
nifiedSchSw
CA Flexible EnodebAlgo None Use the recommended value.
Control Opt ExtSwitch.C
Thld Offset aFlexCtrlOp
tThldOffset
Aggregation SpidCfg.Agg SCS_FORBID_ Set this option based on the
Attribute regationAttr SW network plan.
ibute

eRAN

Name ID
Blacklist UeCompat.B SCS_FORBID_ Set this option based on the

Control lacklistCont SW network plan.
Extension rolExtSwitch
Switch 2 2
Aggregation QciPara.Agg SCS_FORBID_ Set this option based on the
Attribute regationAttr SW network plan.
ibute
Multi-Carrier MultiCarrUn REEST_SCS_F Set this option based on the
Unified ifiedSch.Mul ORBID_SW network plan.
Switch iedSchEnSw
Rsv7 eNBRsvdPar BIT13 Set this option based on the
a.RsvdSwPa network plan.
ra7
FSS PRB Ratio MultiCarrUn None Use the recommended value.
Threshold ifiedSch.Fss This parameter applies only to
PrbRatioThl FDD cells.
d
Rsv62 eNBRsvdPar None The value 11 is recommended
a.RsvdPara6 if some split cells in 8T DSS
2 scenarios have the same PCI-
modulo-3 results.
RsvU8 67 eNBCellRsv None The value 81 is recommended

dPara.RsvdU if some split cells in 8T DSS
8Para67 scenarios have the same PCI-
modulo-3 results.
4.4.1.2 Using MML Commands

Before using MML commands, refer to 4.2.2 Impacts and 4.3.2 Software and
complete the parameter configurations for related functions based on the impact,
dependency, and mutually exclusive relationships between the functions, as well
as the actual network scenario.
Before using MML commands, confirm the related parameter modification
precautions by referring to the fields including "Service Interrupted After
Modification" and "Caution" for the corresponding parameters in the parameter
reference.

eRAN
Activation Command Examples

NOTE
To enable or disable the main control board enhancement mode:

● If the main control board model is known, you are advised to select or deselect the
corresponding option.
● If the main control board model is unknown, you are advised to select or deselect all the
AI_ENHANCEMENT_OPT_SWITCH, UMPTB_ENHANCEMENT_SWITCH, and
UMPTG_ENHANCEMENT_SWITCH options. The base station automatically identifies
the main control board model and activates or deactivates the enhancement mode of
only the identified model.
//Turning on the switch for UMPTb enhancement mode when the UMPTb is used
MOD ENODEBRESMODEALGO: ServiceMode=UMPTB_ENHANCEMENT_SWITCH-1;
//Turning on the switch for optimized AI enhancement mode when the UMPTe or UMPTga is used
MOD ENODEBRESMODEALGO:
ServiceMode=AI_ENHANCEMENT_SWITCH-0&AI_ENHANCEMENT_OPT_SWITCH-1;
//(Optional) Turning on the switch for UMPTg enhancement mode when the UMPTg is used
MOD ENODEBRESMODEALGO: ServiceMode=UMPTG_ENHANCEMENT_SWITCH-1;
//Turning on the switches for smart carrier selection based on virtual grids, and setting related parameters
MOD ENODEBALGOSWITCH:
CaAlgoSwitch=CaSmartSelectionSwitch-0&FreqCfgSwitch-1&SccA2RmvSwitch-1&CaTrafficTriggerSwitch-0,
CaAlgoExtSwitch=SmartCaFastSccCfgSwitch-0&SmartCaPccSelSwitch-0;
MOD CAMGTCFG: LocalCellId=0, CaMimoPriorityStrategySw=CA_PRIOR, CaTrafficDirectionPref=DL_FIRST,
SccCfgInterval=30, EnhancedSccSelA1ThldRsrp=-40, MassiveMimoGainCoefficient=12;
MOD MULTICARRUNIFIEDSCH:
MultiCarrierUnifiedSchSw=SMART_CARRIER_SELECTION_SW-1&SMART_CARRIER_SELECTION_ENH_SW-1&SP
ECTRUM_EFF_EVALUATION_OPT_SW-1&DL_UU_CAPB_EVAL_OPT_SW-1&SPECIAL_UE_MEAS_OPT_SW-1&SC
C_ADAPT_COV_THLD_SW-1&VG_MDL_PRED_NCELL_ENH_SW-1&VG_MDL_ACCURACY_ADAPT_SW-1&VG_M
DL_COORDINATE_TRAIN_SW-1&TRAFFIC_AWARENESS_SCS_SW-1&TRAFFIC_AWARENESS_SCS_OPT_SW-1&I
NTER_ENB_UL_UU_CAPB_EVAL_SW-1&SCC_CARR_CAPB_WITH_MM_GAIN_SW-1&INTRAF_EFF_MDL_PRI_BUI
LD_SW-1, MultiCarrierUnifiedSchEnSw=FAST_TRAFFIC_AWARENESS_SCS_SW-1&REEST_SCS_FORBID_SW-1,
VgModelPredHoMeasRsrpThld=ACCURACY100_ENH, VgMdlPredNecHoMeasRsrpThld=ACCURACY100_ENH,
VgModelPredSccMeasRsrpThld=ACCURACY80_OFFSET5, IntraFreqMeasA3TimeToTrig=160MS,
CarrierCapabilityHysteresis=20, BandwidthHysteresis=50, GFactorThldForHoTrgCell=30,
PredictiveCapbGainThld=30, UlCarrierCapabilityHyst=20;
MOD CAMGTCFG: LocalCellId=0, MinDlAvgToBeScheduledUeNum=255;
MOD CELLMULTICARRUNISCH: LocalCellId=0, SccAdaptCovRsrpThld=-125, VgMdlBuildUlTrafficThld=3000,
UlTrafficVolumeThld=1000, DlTrafficVolumeThld=100, TrafficModeExitPeriodNum=10;
MOD ENBRSVDPARA: RsvdSwPara7=BIT13-1;
//Enabling prohibition of smart carrier selection for UEs under weak coverage
MOD CAMGTCFG: LocalCellId=0, CellCaAlgoSwitch=RcvA2CfgSccSwitch-0;
MOD ENBCELLRSVDPARA: LocalCellId=0, RsvdSwPara10=BIT2-1;
//Turning off the handover admission switches
MOD CELLMLBHO: LocalCellId=0, MlbMatchOtherFeatureMode=HoAdmitSwitch-0&X2RoHoAdmitSwitch-0;
//Turning on RptCqiFltInitSwitch and SrbProbeSchSwitch
MOD CELLALGOSWITCH: LocalCellId=0, CqiAdjAlgoSwitch=RptCqiFltInitSwitch-1,
UlSchExtSwitch=SrbProbeSchSwitch-1;
//Turning on HoWithSccMimoModifySwitch
MOD GLOBALPROCSWITCH: ProtocolCompatibilitySw=HoWithSccMimoModifySwitch-1;
//Enabling ultra-low-latency scheduling for intra-eNodeB CA and setting related parameters
MOD MULTICARRUNIFIEDSCH: MultiCarrierUnifiedSchSw=ULTRA_LOW_LATENCY_SCH_SW-1;
MOD CELLMULTICARRUNISCH: LocalCellId=0, ScellDeactvWaitingTimer=10,
CellMultiCarrUnifiedSchSw=INB_SCELL_DLY_DEACTV_FORBID_SW-1;
MOD CELLALGOSWITCH: LocalCellId=0,
ServiceDiffSwitch=VoiceDataDifferentiationSwitch-1,PucchAlgoSwitch=Dl2CCAckResShareSw-1;
MOD CELLDRXPARA: LocalCellId=0, VoltePlrThldForExitingDrx=3,
CaDrxOptSwitch=PCC_SCC_DRX_STATE_SYNC_SW-1;
MOD CAMGTCFG: LocalCellId=0, CellCaAlgoSwitch=CaInstantlyJudgeSwitch-1, ActiveBufferLenThd=1,
ActiveBufferDelayThd=3;
MOD NSADCMGMTCONFIG: LocalCellId=0, NsaDcLteScellActBfrLenThld=1, NsaDcLteScellActBfrDelThld=3;
MOD CELLPUCCHALGO: LocalCellId=0, SriAlgoSwitch=SriPeriodCfgOptSW-1;
MOD ENODEBALGOEXTSWITCH: CaFlexCtrlOptThldOffset=1;
//Enabling multi-frequency optimal carrier scheduling
MultiCarrierUnifiedSchEnSw=CA_SCH_PRIORITY_OPT_SW-1&CA_MULTI_CARR_UNIFIED_SCH_SW-1;

eRAN
//Selecting the UBBPD_SCH_FUNCTION_ENH_SWITCH option when the UBBPd is used (FDD)

MOD ENODEBALGOEXTSWITCH: NetworkPrfmOptSwitch=UBBPD_SCH_FUNCTION_ENH_SWITCH-1;
//(Optional) Enabling ultra-low-latency scheduling for inter-eNodeB CA based on relaxed backhaul
MOD MULTICARRUNIFIEDSCH: MultiCarrierUnifiedSchEnSw=INTER_ENB_ULTRA_LOW_LATENCY_SW-1;
//(Optional) Setting parameters for optimization in high-load scenarios
MultiCarrierUnifiedSchEnSw=LOAD_BASED_CARR_SEL_OPT_SW-1&HIGH_LOAD_CELL_FILTER_SW-1;
//(Optional, supported in TDD only) Enabling enhanced uplink carrier selection
MOD MULTICARRUNIFIEDSCH: MultiCarrierUnifiedSchEnSw=UL_CARR_SEL_ENH_SW-1;
MOD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=1500, UlEarfcnCfgInd=CFG, UlEarfcn=19500,
AggregationAttribute=UL_LOAD_TRNSFR_TARGET_FLAG-1;
//(Optional) Enabling cell capability adjustment if some split cells in 8T DSS scenarios have the same PCI-
modulo-3 results
MOD ENBRSVDPARA: RsvdPara62=11;
MOD ENBCELLRSVDPARA: LocalCellId=0, RsvdU8Para67=81;
MOD ENBCELLRSVDPARA: LocalCellId=1, RsvdU8Para67=81;
//Resetting the eNodeB application if related options of the ServiceMode parameter are selected (*
indicates the AID of the eNodeB, which can be queried by running the DSP APP command)
RST APP: AID=*;
Deactivation Command Examples

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Turning off the switch for the ultra-low-latency scheduling for inter-eNodeB CA based on relaxed
backhaul function
MOD MULTICARRUNIFIEDSCH: MultiCarrierUnifiedSchEnSw=INTER_ENB_ULTRA_LOW_LATENCY_SW-0;
//Disabling multi-frequency optimal carrier scheduling
MultiCarrierUnifiedSchEnSw=CA_MULTI_CARR_UNIFIED_SCH_SW-0&CA_SCH_PRIORITY_OPT_SW-0;
//Deselecting the UBBPD_SCH_FUNCTION_ENH_SWITCH option when the UBBPd is used (FDD)
MOD ENODEBALGOEXTSWITCH: NetworkPrfmOptSwitch=UBBPD_SCH_FUNCTION_ENH_SWITCH-0;
//Disabling ultra-low-latency scheduling for intra-eNodeB CA
MOD CELLMULTICARRUNISCH: LocalCellId=0, ScellDeactvWaitingTimer=0;
//Turning off the switches for smart carrier selection based on virtual grids
MOD CAMGTCFG: LocalCellId=0, MinDlAvgToBeScheduledUeNum=0;
MOD CAMGTCFG: LocalCellId=0, CellCaAlgoSwitch=RcvA2CfgSccSwitch-1;
MOD ENBCELLRSVDPARA: LocalCellId=0, RsvdSwPara10=BIT2-0;
MultiCarrierUnifiedSchSw=SMART_CARRIER_SELECTION_SW-0&SMART_CARRIER_SELECTION_ENH_SW-0&SP
ECTRUM_EFF_EVALUATION_OPT_SW-0&DL_UU_CAPB_EVAL_OPT_SW-0&SPECIAL_UE_MEAS_OPT_SW-0&SC
C_ADAPT_COV_THLD_SW-0&VG_MDL_PRED_NCELL_ENH_SW-0&VG_MDL_ACCURACY_ADAPT_SW-0&VG_M
DL_COORDINATE_TRAIN_SW-0&TRAFFIC_AWARENESS_SCS_SW-0&TRAFFIC_AWARENESS_SCS_OPT_SW-0&I
NTER_ENB_UL_UU_CAPB_EVAL_SW-0&INTRAF_EFF_MDL_PRI_BUILD_SW-0,
MultiCarrierUnifiedSchEnSw=REEST_SCS_FORBID_SW-0&FAST_TRAFFIC_AWARENESS_SCS_SW-0;
//Disabling the building of virtual grid models, including RSRP prediction models and spectral efficiency
prediction models
MultiCarrierUnifiedSchSw=SMART_CARRIER_SELECTION_SW-0&LOW_FREQ_SCS_OPT_SW-0&LTE_RSRP_VG_
MDL_BUILD_SW-0;
//Disabling the building of spectral efficiency prediction models
MultiCarrierUnifiedSchSw=SMART_CARRIER_SELECTION_ENH_SW-0&LTE_SPEC_EFF_VG_MDL_BUILD_SW-0;
//Restoring related parameter settings (The related parameter settings must be the same as before
functions of Multi-carrier Unified Scheduling are enabled.)
MOD CAMGTCFG: LocalCellId=0, CaMimoPriorityStrategySw=CA_PRIOR, CaTrafficDirectionPref=DL_FIRST,
SccCfgInterval=60;
MOD CELLMLBHO: LocalCellId=0, MlbMatchOtherFeatureMode=HoAdmitSwitch-0&X2RoHoAdmitSwitch-0;
MOD CELLALGOSWITCH: LocalCellId=0, CqiAdjAlgoSwitch=RptCqiFltInitSwitch-1,
UlSchExtSwitch=SrbProbeSchSwitch-0;
MOD GLOBALPROCSWITCH: ProtocolCompatibilitySw=HoWithSccMimoModifySwitch-0;
MOD CAMGTCFG: LocalCellId=0, EnhancedSccSelA1ThldRsrp=-40, MassiveMimoGainCoefficient=10;
MOD CAMGTCFG: LocalCellId=0, CellCaAlgoSwitch=CaInstantlyJudgeSwitch-0&2CCDlCaEnhanceSwitch-0,
ActiveBufferLenThd=9, ActiveBufferDelayThd=50;
MOD CELLDRXPARA: LocalCellId=0, CaDrxOptSwitch=PCC_SCC_DRX_STATE_SYNC_SW-0;

eRAN
MOD CELLALGOSWITCH: LocalCellId=0, PucchAlgoSwitch=Dl2CCAckResShareSw-1;

MOD CELLPUCCHALGO: LocalCellId=0, SriAlgoSwitch=SriPeriodCfgOptSW-1;
MOD ENBRSVDPARA: RsvdPara62=0;
//Turning off the switch for UMPTb enhancement mode when the UMPTb is used (The switch setting must
be the same as before smart carrier selection based on virtual grids is enabled.)
MOD ENODEBRESMODEALGO: ServiceMode=UMPTB_ENHANCEMENT_SWITCH-0;
//Turning off the switch for UMPTg enhancement mode when the UMPTg is used (The switch setting must
be the same as before smart carrier selection based on virtual grids is enabled.)
MOD ENODEBRESMODEALGO: ServiceMode=UMPTG_ENHANCEMENT_SWITCH-0;
//Turning off the switch for optimized AI enhancement mode when the UMPTe or UMPTga is used (The
switch setting must be the same as the setting before smart carrier selection based on virtual grids is
enabled.)
MOD ENODEBRESMODEALGO: ServiceMode=AI_ENHANCEMENT_OPT_SWITCH-0;
//Resetting the eNodeB application (* indicates the AID of the eNodeB, which can be queried by running
the DSP APP command)
RST APP: AID=*;
4.4.1.3 Using the MAE-Deployment

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

To verify activation of virtual grid model building and use, use one of the
following methods:
● Check the values of the L.AiGrid.RsrpPred.Model.AverNum and

L.VirtualGrid.Model.InterFreq.MeasFree.Times counters. If either of them
produces a non-zero value, virtual grid models have taken effect. It takes at
least 24 hours to build a virtual grid model. Therefore, you can observe these
counters at least 24 hours after the feature is activated.
● Run the DSP AIGRIDMOD command to query the status of all models on the
eNodeB. The status is indicated by the Good RSRP Forecast Status, Poor
RSRP Forecast Status, and Spectral Efficiency Forecast Status parameters.
The value AVAILABLE of Good RSRP Forecast Status indicates that the
model can predict whether the RSRP of a UE on the corresponding
neighboring E-UTRA frequency will satisfy entering condition 2 for event A5
or the entering condition for event A4. The value AVAILABLE of Poor RSRP
Forecast Status indicates that the model can predict whether the RSRP of a
UE on the corresponding neighboring E-UTRA frequency will satisfy leaving
condition 2 for event A5 or the leaving condition for event A4.
For details about entering condition 2 and leaving condition 2 for event A5,
see section 5.5.4.6 "Event A5 (PCell/ PSCell becomes worse than threshold1
and neighbour becomes better than threshold2)" in 3GPP TS 36.331 V12.8.0.
For details about the entering and leaving conditions for event A4, see section
5.5.4.5 "Event A4 (Neighbour becomes better than threshold)" in 3GPP TS
36.331 V12.8.0.
The value AVAILABLE of Spectral Efficiency Forecast Status indicates that
the model can predict the spectral efficiency of a UE on the corresponding
frequency. If the EARFCN of a cell identified by Local Cell ID is the same as
the value of Frequency Info, the model is used to predict intra-frequency
spectral efficiency. In this case, the values of both Good RSRP Forecast Status
and Poor RSRP Forecast Status are N/A.
To verify activation of smart carrier selection, use one of the following methods:

eRAN
● Check the values of the L.SCS.Exection and L.SCS.Exection.CA counters. If

either of them produces a non-zero value, smart carrier selection has taken
effect.
● Check the value of the L.SCS.Exection.TrafficAwareness counter. If the
counter produces a non-zero value, traffic model-aware smart carrier
selection has taken effect.
● Run the DSP SMARTCARRIERSELECTIONFREQ command to query the list of
frequencies sorted for smart carrier selection. If the result is not empty, smart
carrier selection has taken effect.
● On the MAE-Access, start the Multi-carrier Unified Scheduling Monitoring and
User Common Monitoring tasks for a UE. If the input parameters are correctly
configured, the results of User Common Monitoring are not empty. In
addition, if the results of Multi-carrier Unified Scheduling Monitoring are not
empty, smart carrier selection has taken effect for the UE.
To verify activation of ultra-low-latency scheduling for intra-eNodeB CA, check

whether the related performance indicators change as follows:
● The L.Thrp.bits.DL.CAUser counter value increases.

● The result of L.CA.Traffic.bits.DL.SCell/(L.CA.Traffic.bits.DL.PCell +
L.CA.Traffic.bits.DL.SCell) increases.
To verify activation of ultra-low-latency scheduling for inter-eNodeB CA based on

relaxed backhaul, check the L.CA.Traffic.bits.RelaxedBackhaulCAUsed.DL.Scell
counter value, which is expected to increase.
To verify activation of multi-frequency optimal carrier scheduling, check the result

of (L.Thrp.bits.DL – L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI, which is
expected to increase. The higher the proportion of CA UEs whose SCells are
configured on the same BBP as the PCell, the more significant the increase. The
proportion is equal to L.Traffic.User.SCell.SameBBPWithPCell.DL.Avg divided by
L.Traffic.User.SCell.DL.Avg.
To verify activation of scheduling priority optimization for CA in medium- or

heavy-load scenarios, check the result of L.Thrp.bits.DL divided by
L.ChMeas.PRB.DL.DrbUsed.Avg, which is expected to increase.
4.4.3 Network Monitoring

The accuracy of a model built based on 24-hour data is relatively low. To ensure
the model accuracy, you are advised to monitor the following indicators as of the
second week after Multi-carrier Unified Scheduling is enabled:
● Average downlink data rate of UEs, which is equal to (L.Thrp.bits.DL –

L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI
● Downlink throughput of UEs in the relaxed-backhaul-based inter-eNodeB CA
state, which is represented by the result of
L.Thrp.bits.DL.RelaxedBackhaulCAUser divided by
L.Thrp.Time.DL.RelaxedBackhaulCAUser. The monitoring is required after
ultra-low-latency scheduling for inter-eNodeB CA based on relaxed backhaul
is enabled.

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

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

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

eRAN
Description 8 Reference Documents
8 Reference Documents
1. Carrier Aggregation
2. Mobility Management in Connected Mode
3. Licensed Assisted Access (TDD)
4. Intra-RAT Mobility Load Balancing
5. Multi-band Optimal Carrier Selection
6. Intra-RAT Mobility Load Balancing
7. SFN
8. High Speed Mobility
9. Extended Cell Range
10. Massive MIMO (FDD)
11. eMTC
12. Energy Conservation and Emission Reduction
13. Scheduling

Multi-Carrier Unified Scheduling (eRAN19.1 - 07)

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

Multi-Carrier Unified Scheduling (eRAN19.1 - 07)

Uploaded by

Copyright:

Available Formats

eRAN

Multi-carrier Unified Scheduling

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. i

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. ii

2 About This Document.............................................................................................................8

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. iii

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. iv

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

1.1 eRAN19.1 07 (2024-01-05)

1.2 eRAN19.1 06 (2023-11-30)

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 1

For FDD, added recommendations on the functions to be enabled together with

Corrected the RAT of the prerequisite function "scheduling priority optimization

Added descriptions related to cell load in "Carrier or Carrier Combination Priority

1.3 eRAN19.1 05 (2023-09-27)

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 2

1.4 eRAN19.1 04 (2023-08-23)

1.5 eRAN19.1 03 (2023-06-29)

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 3

1.6 eRAN19.1 02 (2023-04-28)

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 4

Optimized the Added the FDD ● 3900 and 5900

1.7 eRAN19.1 01 (2023-03-09)

Added descriptions of the impact relationships between multi-carrier unified

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 5

● Dynamic power sharing between LTE carriers

1.8 eRAN19.1 Draft A (2022-12-30)

Added support for Modified parameter: FDD ● 3900 and 5900

Optimized the criteria Modified parameter: FDD ● 3900 and 5900

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 6

Change Description Parameter Change RAT Base Station

Added multi-carrier Modified parameter: FDD ● 3900 and 5900

Replaced the reserved Modified parameter: FDD ● 3900 and 5900

Added support for None TDD ● 3900 and 5900

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 7

2 About This Document

2.1 General Statements

Feature Differences Between RATs

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 8

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Chapter/Section

LNOFD-15133 Multi-carrier Unified See the corresponding sections of the

LNOFD-15133 Smart Carrier Selection 4.1.1 Virtual Grid Function

LNOFD-16133 Ultra-Low-Latency 4.1.3 Ultra-Low-Latency Scheduling

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 9

Feature ID Feature Name Chapter/Section

LNOFD-18130 Ultra-Low-Latency 4.1.4 Ultra-Low-Latency Scheduling

LNOFD-18130 Multi-Frequency 4.1.5 Multi-Frequency Optimal

This document describes the following TDD features.

Feature ID Feature Name Chapter/Section

TDLNOFD-151 Multi-carrier Unified See the corresponding sections of the

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 10

Feature ID Feature Name Chapter/Section

TDLNOFD-151 Smart Carrier 4.1.1 Virtual Grid Function

TDLNOFD-161 Ultra-Low-Latency 4.1.3 Ultra-Low-Latency Scheduling

TDLNOFD-181 Ultra-Low-Latency 4.1.4 Ultra-Low-Latency Scheduling

Issue 07 (2024-01-05) Copyright © Huawei Technologies Co., Ltd. 11

Feature ID Feature Name Chapter/Section

TDLNOFD-191 Multi-Frequency 4.1.5 Multi-Frequency Optimal