Mobility Management (5G RAN6.1 - Draft A)

5G RAN
Mobility Management Feature

Parameter Description
Issue Draft A
Date 2021-12-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2022. 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 Draft A Copyright © Huawei Technologies Co., Ltd. i

(2021-12-30)
5G RAN
Mobility Management Feature Parameter
Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 5G RAN6.1 Draft A (2021-12-30)...................................................................................................................................... 1
2 About This Document...........................................................................................................13

2.1 General Statements..............................................................................................................................................................13
2.2 Features in This Document................................................................................................................................................ 13
2.3 Differences Between NR FDD and NR TDD.................................................................................................................14
2.4 Differences Between NSA and SA................................................................................................................................... 15
2.5 Differences Between High Frequency Bands and Low Frequency Bands..........................................................16
3 Overview................................................................................................................................. 19
4 SA Mobility Management in Connected Mode.............................................................. 23
4.1 Basic Functions of Mobility Management in Connected Mode............................................................................26
4.1.1 Principles.............................................................................................................................................................................. 26
4.1.1.1 Basic Procedure............................................................................................................................................................... 26
4.1.1.2 Handover Function Start Decision........................................................................................................................... 28
4.1.1.3 Processing Mode Selection......................................................................................................................................... 28
4.1.1.4 Measurement Configuration Delivery..................................................................................................................... 28
4.1.1.4.1 Measurement Object................................................................................................................................................. 29
4.1.1.4.2 Reporting Configuration...........................................................................................................................................31
4.1.1.4.3 Other Configurations.................................................................................................................................................46
4.1.1.5 Measurement Reporting.............................................................................................................................................. 52
4.1.1.6 Target Cell or Frequency Decision............................................................................................................................ 53
4.1.1.7 Handover Execution...................................................................................................................................................... 57
4.1.1.8 Handover Failure Penalty............................................................................................................................................ 61
4.1.2 Network Analysis............................................................................................................................................................... 62
4.1.2.1 Benefits.............................................................................................................................................................................. 62
4.1.2.2 Impacts.............................................................................................................................................................................. 63
4.1.3 Requirements...................................................................................................................................................................... 64
4.1.3.1 Licenses.............................................................................................................................................................................. 64
4.1.3.2 Software............................................................................................................................................................................ 64
4.1.3.3 Hardware.......................................................................................................................................................................... 64
4.1.3.4 Others................................................................................................................................................................................ 65
4.1.4 Operation and Maintenance......................................................................................................................................... 66
Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

(2021-12-30)
5G RAN
4.1.4.1 Data Configuration........................................................................................................................................................ 66

4.1.4.1.1 Data Preparation.........................................................................................................................................................66
4.1.4.1.2 Using MML Commands............................................................................................................................................ 73
4.1.4.1.3 Using the MAE-Deployment................................................................................................................................... 76
4.1.4.2 Activation Verification.................................................................................................................................................. 76
4.1.4.3 Network Monitoring..................................................................................................................................................... 76
4.2 Coverage-based Intra-Frequency Handover................................................................................................................ 76
4.2.1 Principles.............................................................................................................................................................................. 76
4.2.2.1 Benefits.............................................................................................................................................................................. 78
4.2.2.2 Impacts.............................................................................................................................................................................. 78
4.2.3 Requirements...................................................................................................................................................................... 78
4.2.3.1 Licenses.............................................................................................................................................................................. 78
4.2.3.2 Software............................................................................................................................................................................ 78
4.2.3.3 Hardware.......................................................................................................................................................................... 78
4.2.3.4 Others................................................................................................................................................................................ 79
4.2.4.1.3 Using the MAE-Deployment................................................................................................................................... 81
4.2.4.2 Activation Verification.................................................................................................................................................. 81
4.2.4.3 Network Monitoring..................................................................................................................................................... 81
4.3 Coverage-based Inter-Frequency Handover................................................................................................................ 81
4.3.1 Principles.............................................................................................................................................................................. 81
4.3.1.1 Basic Procedure............................................................................................................................................................... 82
4.3.1.2 Blind Redirection Optimization................................................................................................................................. 88
4.3.2.1 Benefits.............................................................................................................................................................................. 89
4.3.2.2 Impacts.............................................................................................................................................................................. 89
4.3.3 Requirements...................................................................................................................................................................... 91
4.3.3.1 Licenses.............................................................................................................................................................................. 91
4.3.3.2 Software............................................................................................................................................................................ 91
4.3.3.3 Hardware.......................................................................................................................................................................... 92
4.3.3.4 Others................................................................................................................................................................................ 92
4.3.4.1.3 Using the MAE-Deployment.................................................................................................................................100
4.3.4.2 Activation Verification................................................................................................................................................100
4.3.4.3 Network Monitoring................................................................................................................................................... 100
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

(2021-12-30)
5G RAN
4.4 Frequency-Priority-based Inter-Frequency Handover............................................................................................ 101

4.4.1 Principles............................................................................................................................................................................ 101
4.4.2 Network Analysis............................................................................................................................................................ 107
4.4.2.1 Benefits............................................................................................................................................................................107
4.4.2.2 Impacts............................................................................................................................................................................ 107
4.4.3 Requirements.................................................................................................................................................................... 109
4.4.3.1 Licenses........................................................................................................................................................................... 109
4.4.3.2 Software.......................................................................................................................................................................... 110
4.4.3.3 Hardware........................................................................................................................................................................ 110
4.4.3.4 Networking.................................................................................................................................................................... 110
4.4.3.5 Others.............................................................................................................................................................................. 111
4.4.4 Operation and Maintenance....................................................................................................................................... 112
4.4.4.1 Data Configuration..................................................................................................................................................... 112
4.4.4.1.1 Data Preparation...................................................................................................................................................... 112
4.4.4.1.2 Using MML Commands......................................................................................................................................... 116
4.5 Operator-specific-Priority-based Inter-Frequency Handover.............................................................................. 120
4.5.1 Principles............................................................................................................................................................................ 120
4.5.2.1 Benefits............................................................................................................................................................................123
4.5.2.2 Impacts............................................................................................................................................................................ 124
4.5.3 Requirements.................................................................................................................................................................... 124
4.5.3.1 Licenses........................................................................................................................................................................... 125
4.5.3.2 Software.......................................................................................................................................................................... 125
4.5.3.3 Hardware........................................................................................................................................................................ 125
4.5.3.4 Networking.................................................................................................................................................................... 125
4.5.3.5 Others.............................................................................................................................................................................. 126
4.6 Service-based Inter-Frequency Handover.................................................................................................................. 134
4.6.1 Principles............................................................................................................................................................................ 134
4.6.2.1 Benefits............................................................................................................................................................................137
4.6.2.2 Impacts............................................................................................................................................................................ 137
4.6.3 Requirements.................................................................................................................................................................... 139
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iv

(2021-12-30)
5G RAN
4.6.3.1 Licenses........................................................................................................................................................................... 139

4.6.3.2 Software.......................................................................................................................................................................... 139
4.6.3.3 Hardware........................................................................................................................................................................ 139
4.6.3.4 Networking.................................................................................................................................................................... 140
4.6.3.5 Others.............................................................................................................................................................................. 140
4.7 Uplink-Interference-based Inter-Frequency Handover.......................................................................................... 148
4.7.1 Principles............................................................................................................................................................................ 148
4.7.2.1 Benefits............................................................................................................................................................................152
4.7.2.2 Impacts............................................................................................................................................................................ 152
4.7.3 Requirements.................................................................................................................................................................... 153
4.7.3.1 Licenses........................................................................................................................................................................... 153
4.7.3.2 Software.......................................................................................................................................................................... 154
4.7.3.3 Hardware........................................................................................................................................................................ 154
4.7.3.4 Networking.................................................................................................................................................................... 155
4.7.3.5 Others.............................................................................................................................................................................. 155
4.8 SSB SINR-based Inter-Frequency Handover.............................................................................................................. 162
4.8.1 Principles............................................................................................................................................................................ 163
4.8.2.1 Benefits............................................................................................................................................................................167
4.8.2.2 Impacts............................................................................................................................................................................ 167
4.8.3 Requirements.................................................................................................................................................................... 167
4.8.3.1 Licenses........................................................................................................................................................................... 168
4.8.3.2 Software.......................................................................................................................................................................... 168
4.8.3.3 Hardware........................................................................................................................................................................ 168
4.8.3.4 Networking.................................................................................................................................................................... 168
4.8.3.5 Others.............................................................................................................................................................................. 169
Issue Draft A Copyright © Huawei Technologies Co., Ltd. v

(2021-12-30)
5G RAN

5 SA Mobility Management in Idle Mode........................................................................ 176

5.1 Principles............................................................................................................................................................................... 176
5.1.1 Cell Search and PLMN Selection................................................................................................................................176
5.1.2 Cell Selection.................................................................................................................................................................... 178
5.1.3 Cell Reselection................................................................................................................................................................ 180
5.1.3.1 Cell Reselection Priority............................................................................................................................................. 180
5.1.3.2 Blacklisting Cells for Cell Reselection................................................................................................................... 181
5.1.3.3 Neighboring Cell Measurement for Cell Reselection...................................................................................... 182
5.1.3.4 Intra-Frequency or Equal-Priority Inter-Frequency Cell Reselection.......................................................... 183
5.1.3.5 Different-Priority Inter-Frequency Cell Reselection......................................................................................... 185
5.1.3.6 Speed-based Cell Reselection.................................................................................................................................. 187
5.2 Network Analysis................................................................................................................................................................ 189
5.2.1 Benefits............................................................................................................................................................................... 189
5.2.2 Impacts............................................................................................................................................................................... 189
5.3 Requirements....................................................................................................................................................................... 189
5.3.1 Licenses............................................................................................................................................................................... 189
5.3.2 Software............................................................................................................................................................................. 190
5.3.3 Hardware........................................................................................................................................................................... 190
5.3.4 Others................................................................................................................................................................................. 190
5.4 Operation and Maintenance.......................................................................................................................................... 191
5.4.1 Data Configuration......................................................................................................................................................... 191
5.4.1.1 Data Preparation..........................................................................................................................................................191
5.4.1.2 Using MML Commands............................................................................................................................................. 195
5.4.1.3 Using the MAE-Deployment.................................................................................................................................... 197
5.4.2 Activation Verification................................................................................................................................................... 197
5.4.3 Network Monitoring...................................................................................................................................................... 198
6 SA Mobility Management in Inactive Mode.................................................................199

6.1 Principles............................................................................................................................................................................... 199
6.1.1 RNA Introduction............................................................................................................................................................ 200
6.1.2 RNA Update...................................................................................................................................................................... 201
6.1.3 State Transition from RRC_INACTIVE....................................................................................................................... 203
6.1.4 UE Context Retrieval...................................................................................................................................................... 204
6.2 Network Analysis................................................................................................................................................................ 204
6.2.1 Benefits............................................................................................................................................................................... 204
6.2.2 Impacts............................................................................................................................................................................... 204
6.3 Requirements....................................................................................................................................................................... 205
Issue Draft A Copyright © Huawei Technologies Co., Ltd. vi

(2021-12-30)
5G RAN
6.3.1 Licenses............................................................................................................................................................................... 206

6.3.2 Software............................................................................................................................................................................. 206
6.3.3 Hardware........................................................................................................................................................................... 206
6.3.4 Others................................................................................................................................................................................. 206
6.4 Operation and Maintenance.......................................................................................................................................... 208
6.4.1 Data Configuration......................................................................................................................................................... 208
6.4.1.1 Data Preparation..........................................................................................................................................................208
6.4.1.2 Using MML Commands............................................................................................................................................. 209
6.4.1.3 Using the MAE-Deployment.................................................................................................................................... 210
6.4.2 Activation Verification................................................................................................................................................... 210
6.4.3 Network Monitoring...................................................................................................................................................... 211
7 NSA Mobility Management in Connected Mode.........................................................212

8 Appendix............................................................................................................................... 218
8.1 Intra-Base-Station Handover.......................................................................................................................................... 218
8.2 Xn-based Handover........................................................................................................................................................... 222
8.3 NG-based Handover.......................................................................................................................................................... 224
8.4 RNA Update..........................................................................................................................................................................226
8.5 State Transition from RRC_INACTIVE.......................................................................................................................... 229
9 Parameters............................................................................................................................232
10 Counters.............................................................................................................................. 233
11 Glossary............................................................................................................................... 234
12 Reference Documents...................................................................................................... 235
Issue Draft A Copyright © Huawei Technologies Co., Ltd. vii

(2021-12-30)
5G RAN
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 5G RAN6.1 Draft A (2021-12-30)

This issue introduces the following changes to 5G RAN5.1 07 (2021-11-27).
Technical Changes
Change Description Parameter Change RAT Base Station Model
Added support for Modified parameters: FDD ● 3900 and 5900

operator-specific ● Added the Low- series base
neighboring OPERATOR_NR_FRE freque stations
frequency Q_CFG_SW option to ncy ● DBS3900
configuration. For the TDD LampSite and
details, see: NRCellOpPolicy.Freq DBS5900
High-
● 4.1.1.4.1 ConfigPolicySwitch freque LampSite
Measurement parameter. ncy
Object ● Deleted TDD
● 4.1.1.6 Target RSVDSWPARAM0_BI
Cell or T20 of the reserved
Frequency parameter
Decision NRCellRsvd.RsvdSwP
aram0.
Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

(2021-12-30)
5G RAN
Added support for Added the FDD ● 3900 and 5900

QCI priority gNBQciBearer.QciPriori Low- series base
configuration for tyForHo parameter. freque stations
handovers. For ncy ● DBS3900
details, see 4.1.1.4.2 TDD LampSite and
Reporting DBS5900
Configuration. High-
freque LampSite
ncy
TDD
Added the SMTC Modified parameter: FDD ● 3900 and 5900

offset compatibility Added the Low- series base
function. For details, SMTC_OFFSET_COMPA freque stations
see 4.1.1.4.3 Other T_SW option to the ncy ● DBS3900
Configurations. NRDUCellAlgoSwitch.Al TDD LampSite and
goCompatibilitySwitch- DBS5900
Ext parameter. LampSite
Added a None FDD ● 3900 and 5900

neighboring cell Low- series base
filtering rule that freque stations
the neighboring cells ncy ● DBS3900
whose uplink and TDD LampSite and
downlink DBS5900
bandwidths are not High-
freque LampSite
supported by UEs
are filtered out. For ncy
details, see 4.1.1.6 TDD
Target Cell or
Frequency Decision.

(2021-12-30)
5G RAN
Simplified the switch Modified parameters: FDD ● 3900 and 5900

for EPLMN-based ● Added the Low- series base
intra-RAT inter- INTRA_RAT_HO_WIT freque stations
PLMN handover. For H_AMF_EPLMN_SW ncy ● DBS3900
details, see 4.1.1.6 option of the TDD LampSite and
Target Cell or gNodeBParam.EqvPl DBS5900
Frequency Decision. High-
mnAlgoSwitch freque LampSite
parameter to the ncy
parameter disuse list TDD
and replaced this
option with the
INTRA_RAT_HO_WIT
H_GNB_EPLMN_SW
option.
● Changed the name of
the
INTRA_RAT_HO_WIT
H_GNB_EPLMN_SW
option of the
gNodeBParam.EqvPl
mnAlgoSwitch
parameter from
"Intra-RAT Inter-
PLMN HO with gNB
EPLMN" to "EPLMN-
based Intra-RAT
Inter-PLMN HO Sw".
Added the impact None FDD ● 3900 and 5900

relationship Low- series base
between EPLMN- freque stations
based intra-RAT ncy ● DBS3900
inter-PLMN TDD LampSite and
handover and DBS5900
experience-based LampSite
smart carrier
selection. For details,
see 4.1.2.2 Impacts.

(2021-12-30)
5G RAN
Added support for Added parameters: FDD ● 3900 and 5900

coverage-based ● NRCellFreqRelation.I Low- series base
inter-frequency nterFreqHoEvent- freque stations
handover execution Type ncy ● DBS3900
based on event A3. TDD LampSite and
For details, see 4.3 ● NRCellInterFHoMea
Grp.A3InterFreqHoA DBS5900
Coverage-based LampSite
Inter-Frequency 2RsrpThld
Handover. ● NRCellInterFHoMea
Grp.A3InterFreqHoA
1RsrpThld
● NRCellInterFHoMea
Grp.InterFreqHoA3Of
fset
Modified parameters:
the
NRCellInterFHoMea
Grp.InterFreqA4A5H
yst parameter from
"Inter-frequency
A4A5 Hysteresis" to
"Inter-freq
Measurement Event
Hysteresis".
the
NRCellInterFHoMea
Grp.InterFreqA4A5Ti
meToTrig parameter
from "Inter-frequency
A4A5 Time to
Trigger" to "Inter-freq
Measurement Event
Time to Trigger".
Added support for Modified parameter: FDD ● 3900 and 5900

blind redirection Added the Low- series base
optimization. For A2_BLIND_REDIRECT_C freque stations
details, see 4.3.1.2 TRL_SW option to the ncy ● DBS3900
Blind Redirection NRCellAlgoSwitch.Proc TDD LampSite and
Optimization. essSwitch parameter. DBS5900
High-
freque LampSite
ncy
TDD

(2021-12-30)
5G RAN

RFSP-specific ● gNBFreqPriorityGrou Low- series base
frequency-priority- p.TrafficPriority freque stations
based inter- ncy ● DBS3900
frequency handover. ● gNBRfspConfig.Freq
PriHoA1A2RsrpThld TDD LampSite and
For details, see 4.4 DBS5900
Frequency-Priority- Ofs High-
freque LampSite
based Inter- Modified parameter:
Frequency Added the ncy
Handover. FREQ_PRIORITY_BASED TDD
_HO_SW option to the
NRCellAlgoSwitch.Rfsp
AlgoSwitch parameter.
inter-frequency NRCellMobilityCon- Low- series base
measurement fig.InterFreqMeasWait- freque stations
waiting time Time parameter. ncy ● DBS3900
configuration for TDD LampSite and
frequency-priority- DBS5900
based inter- High-
freque LampSite
frequency handover.
For details, see 4.4 ncy
Frequency-Priority- TDD
based Inter-
Frequency
Handover.
Added support for Modified parameter: FDD DBS3900 LampSite

SSB SINR-based Added the Low- and DBS5900
inter-frequency SSB_SINR_BASED_HO freque LampSite
handover. For option to the ncy
details, see 4.8 SSB NRCellAlgoSwitch.Inter TDD
SINR-based Inter- FreqHoSwitch
Frequency parameter.
Handover. Added parameters:
Grp.SsbSinrInterFreq
HoA1Thld
Grp.SsbSinrInterFreq
HoA2Thld
● gNBMobilityComm-
Param.SsbSinrInterF
HoPunishTimer

(2021-12-30)
5G RAN

between inter- freque stations
frequency ncy ● DBS3900
measurement and TDD LampSite and
the function of low DBS5900
latency and high LampSite
reliability. For
details, see 4.1.2.2
Impacts.

between frequency- freque stations
priority-based inter- ncy ● DBS3900
frequency handover TDD LampSite and
and experience- DBS5900
based smart carrier LampSite
selection. For details,
see 4.4.2.2 Impacts.

between the policy freque stations
of RFSP-based inter- ncy ● DBS3900
frequency handover TDD LampSite and
back to the HPLMN DBS5900
and operator- High-
freque LampSite
specific-priority-
based inter- ncy
frequency handover. TDD
For details, see
4.5.2.2 Impacts.

(2021-12-30)
5G RAN

measurement event NRCellMobilityCon- Low- series base
type configuration fig.InterFreqMeasEvent freque stations
for unnecessary Config parameter. ncy ● DBS3900
inter-frequency Modified parameters: TDD LampSite and
handovers. DBS5900
Measurement events ● Revised the meaning High-
of the freque LampSite
used by UEs in the
execution phase of NRCellInterFHoMea ncy
the following Grp.FreqPriInterFA4 TDD
handovers can be RsrpThld parameter.
configured: This parameter now
frequency-priority- indicates the RSRP
based inter- threshold for event
frequency A4 related to
handovers, frequency-priority-
operator-specific- based inter-frequency
priority-based inter- handover and RSRP
frequency threshold 2 for event
handovers, and A5 related to
service-based inter- frequency-priority-
frequency based inter-frequency
handovers. For handover.
details, see: ● Revised the meaning
● 4.1.1.4.2 of the
Reporting NRCellInterFHoMea
Configuration Grp.OpDedPriHoA4R
srpThld parameter.
● 4.4 Frequency- This parameter now
Priority-based indicates the RSRP
Inter-Frequency threshold for event
Handover A4 related to
● 4.5 Operator- operator-specific-
specific-Priority- priority-based inter-
based Inter- frequency handover
Frequency and RSRP threshold 2
Handover for event A5 related
● 4.6 Service- to operator-specific-
based Inter- priority-based inter-
Frequency frequency handover.
Handover ● Revised the meaning
of the
NRCellInterFHoMea
Grp.SrvInterFreqA4R
srpThld parameter.
This parameter now
indicates the RSRP
threshold for event
A4 related to service-
based inter-frequency

(2021-12-30)
5G RAN
handover and RSRP

threshold 2 for event
handover.
Added the function Modified parameter: FDD ● 3900 and 5900

of subscription to Added the Low- series base
uplink interference INTER_FREQ_UL_INTRF freque stations
information about _SW option to the ncy ● DBS3900
inter-frequency NRCellAlgoSwitch.NCel TDD LampSite and
neighboring cells. lInfoCtrlSwitch DBS5900
For details, see: parameter. LampSite
● 4.4.1 Principles

between protection freque stations
of UEs under weak ncy ● DBS3900
coverage in the TDD LampSite and
uplink and uplink- DBS5900
interference-based LampSite
inter-frequency
handover. For
details, see 4.7.2.2
Impacts.

inter-frequency Added the Low- series base
handover INTER_FREQ_HO_COLL freque stations
collaboration. For ABORATION_SW option ncy ● DBS3900
details, see: to the TDD LampSite and
● 4.4.1 Principles NRCellAlgoSwitch.Inter DBS5900
FreqHoSwitch LampSite
● 4.5.1 Principles parameter.

(2021-12-30)
5G RAN
Added the target Modified parameter: FDD ● 3900 and 5900

cell load decision Added the Low- series base
switch for operator- TARGET_CELL_LOAD_EV freque stations
specific-priority- AL_SW option of the ncy ● DBS3900
based inter- gNBRfspConfig.HoPolic TDD LampSite and
frequency handover y parameter to the DBS5900
to the parameter parameter disuse list. High-
freque LampSite
disuse list and
deleted related ncy
descriptions. For TDD
details, see 4.5.1
Principles.

blacklisting intra- ● gNBCellBlackList.Cel Low- series base
frequency cells for lBlacklistId freque stations
cell reselection. For ncy ● DBS3900
details, see 5.1.3.2 ● gNBCellBlackList.Sta
rtPhysicalCellId TDD LampSite and
Blacklisting Cells DBS5900
for Cell ● gNBCellBlackList.Ph High-
freque LampSite
Reselection. ysicalCellIdRange
ncy
● NRCellMobilityCon- TDD
fig.IntraFReselCell-
BlacklistId

(2021-12-30)
5G RAN
Added speed-based Modified parameters: FDD ● 3900 and 5900

cell reselection. For ● Added the Low- series base
details, see 5.1.3.6 SPEED_BASED_RESEL freque stations
Speed-based Cell _SW option to the ncy ● DBS3900
Reselection. NRCellReselConfig.Si TDD LampSite and
bOptionalIeInd High- DBS5900
parameter. freque LampSite
● Added the ncy
INTER_FREQ_RAT_SP TDD
EED_RESEL_SW
option to the
NRCellReselConfig.Si
bOptionalIeInd
parameter.
Added parameters:
● NRCellReselConfig.
MobStateEvalPeriod
● NRCellReselConfig.R
eselThldForMedium-
Mob
eselThldForHighMob
eselTimeSfForMe-
diumMob
● NRCellReselConfig.A
ddlHystForMedium-
Mob
eselTimeSfForHigh-
Mob
● NRCellReselConfig.A
ddlHystForHighMob
protocol Added the Low- series base
compatibility XN_UE_SECURITY_CAP_ freque stations
processing for UE PROC_SW option to the ncy ● DBS3900
Security Capabilities gNodeBParam.Compati TDD LampSite and
exchanged between bilityAlgoSwitch DBS5900
base stations. For parameter. High-
freque LampSite
details, see:
ncy
● 4.1.3.4 Others TDD
● 6.3.4 Others

(2021-12-30)
5G RAN

uplink-interference- Added the Low- series base
based inter- NSA_UL_INTRF_BASED_ freque stations
frequency PSCell HO option to the ncy ● DBS3900
change in NSA NRCellAlgoSwitch.Inter TDD LampSite and
networking. For FreqHoSwitch DBS5900
details, see 7 NSA parameter. LampSite
Mobility
Management in
Connected Mode.

operator-specific NRDUCellOp.RanNotifi Low- series base
RAN area code cationAreaId parameter. freque stations
configuration in ncy ● DBS3900
multi-operator TDD LampSite and
sharing scenarios. DBS5900
For details, see 6.1.1 LampSite
RNA Introduction.

configuring the gNBConnStateTim- Low- series base
length of the er.UeInactiveToIdle- freque stations
inactive-to-idle Timer parameter. ncy ● DBS3900
timer. For details, TDD LampSite and
see 6.1.3 State DBS5900
Transition from LampSite
RRC_INACTIVE.

(2021-12-30)
5G RAN
Added the function Added the FDD ● 3900 and 5900

of configuring QCI- NRCellQciBearer.NsaInt Low- series base
specific erFreqHoMeasGroupId freque stations
measurement parameter. ncy ● DBS3900
parameters related TDD LampSite and
to inter-frequency DBS5900
measurements High-
freque LampSite
separately for SA
UEs and NSA UEs. ncy
For details, see: TDD
● 4.1.1.4.2
Reporting
Configuration
● 4.3.4.1 Data
Configuration
● 4.4.4.1 Data
Configuration
● 4.5.4.1 Data
Configuration
● 4.6.4.1 Data
Configuration
● 4.7.4.1 Data
Configuration
Editorial Changes
Optimized descriptions of principles of measurement configuration delivery for
frequency-priority-based inter-frequency handover. For details, see Measurement
Configuration Delivery.
Modified the conditions for determining neighboring cells exposed to low uplink
interference specific to uplink-interference-based inter-frequency handover. For
details, see Target Cell or Frequency Decision.
Added the signaling procedures for mobility management in SA networking. For
details, see 8 Appendix.
Revised descriptions in this document.

(2021-12-30)
5G RAN
Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are 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.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
2.2 Features in This Document

This document describes the following features.

(2021-12-30)
5G RAN
Feature ID Feature Name Chapter/Section
FBFD-010014 Mobility Management 4 SA Mobility

Management in
Connected Mode
5 SA Mobility
Management in
Idle Mode
7 NSA Mobility
Management in
Connected Mode
FBFD-031102 Inactive State 6 SA Mobility

Management in
Inactive Mode
2.3 Differences Between NR FDD and NR TDD

Function Name Difference Chapter/Section
SA mobility None 4 SA Mobility

management in Management in
connected mode Connected Mode

idle mode Idle Mode

inactive mode Inactive Mode
NSA mobility None 7 NSA Mobility


(2021-12-30)
5G RAN
2.4 Differences Between NSA and SA

SA mobility Supported only in SA networking, 4 SA Mobility

management in with the following differences from Management in
connected mode NSA mobility management: Connected Mode
● NSA networking involves PCell
change and PSCell change, while
SA networking involves only
serving cell change. For details
about the mechanism for PCell
change in NSA networking, see
NSA Networking based on EPC.
This document details the
mechanism for PSCell change in
NSA networking and serving cell
change in SA networking.
● PSCell change in NSA networking
and serving cell change in SA
networking have different
mechanisms.
In NSA networking, the per UE or
per FR1 measurement gap is
calculated on the LTE side based
on the NR cell's SSB-based
measurement timing
configuration (SMTC) information
carried in X2 interface messages.
For details, see NSA Networking
based on EPC. In SA networking,
the measurement gap is
calculated for UEs by the gNodeB.
● EPLMN-based intra-RAT inter-
PLMN handover is supported only
in SA networking, not in NSA
networking.
● Coverage-based inter-frequency
handover: In NSA networking,
PSCell change supports
measurement-based inter-
frequency handover and blind
inter-frequency handover, not
redirection.
The change mechanism for
measurement-based inter-
frequency handover is the same
as that for serving cell change in
SA networking.

(2021-12-30)
5G RAN
Blind inter-frequency handover is

supported only in NSA
networking, not in SA networking.
● Uplink-interference-based inter-
frequency PSCell change is
implemented in the same way
between SA networking and NSA
networking, except for the
starting condition.
● SSB SINR-based inter-frequency
handover is supported only in SA
networking, not in NSA
networking.
SA mobility Supported only in SA networking 5 SA Mobility

idle mode Idle Mode
SA mobility Supported only in SA networking 6 SA Mobility

NSA mobility Supported only in NSA networking 7 NSA Mobility

2.5 Differences Between High Frequency Bands and

Low Frequency Bands
This document refers to frequency bands belonging to FR1 (410–7125 MHz) as
low frequency bands, and those belonging to FR2 (24250–52600 MHz) as high
frequency bands. For details about FR1 and FR2, see section 5.1 "General" in 3GPP
TS 38.104 V15.5.0.

(2021-12-30)
5G RAN
SA mobility Supported in both low and high 4.1 Basic

management in frequency bands, with the following Functions of
connected mode differences: Mobility
● SA networking is supported only Management in
in FWA scenarios in high Connected Mode
frequency bands and is supported
in all scenarios in low frequency
bands.
● SMTC offset compatibility is
supported only in low frequency
bands.
● The function of non-overlapping
between gap and NR resources is
supported only in low frequency
bands.
● Uplink-interference-based inter-
frequency handover is supported
only in low frequency bands.
● SSB SINR-based inter-frequency
handover is supported only in low
frequency bands.
● Subscription to uplink interference
information about inter-frequency
neighboring cells is supported
only in low frequency bands.
● Inter-frequency handover
collaboration is supported only in
low frequency bands.
SA mobility Supported in both low and high 5 SA Mobility

management in frequency bands, with the following Management in
idle mode differences: Idle Mode
SA networking is supported only in
FWA scenarios in high frequency
bands and is supported in all
scenarios in low frequency bands.
SA mobility Supported only in low frequency 6 SA Mobility

management in bands Management in

(2021-12-30)
5G RAN
NSA mobility Supported in both low and high 7 NSA Mobility

management in frequency bands, with the following Management in
connected mode differences: Connected Mode
● In low frequency bands, the SMTC
duration is configurable. In high
frequency bands, it is
automatically calculated by the
system.
● Delivery of synchronization signal
and PBCH block (SSB)
measurement positions of
neighboring cells is supported in
high frequency bands. For details,
see SSB Measurement Position
Delivery Configuration.
● Coverage-based inter-frequency
handover: Measurement-based
inter-frequency handover is
supported only between low
frequencies as well as between
high and low frequencies, not
between high frequencies. Blind
inter-frequency handover is
supported only from high
frequencies to low frequencies,
not between high frequencies,
between low frequencies, and
from low frequencies to high
frequencies.

(2021-12-30)
5G RAN
Description 3 Overview
3 Overview
Mobility management is a basic function used to ensure that services stay

uninterrupted as UEs move through mobile networks.
In an NR network, a UE at any time is in one of the following radio resource

control (RRC) states: RRC_CONNECTED, RRC_IDLE, and RRC_INACTIVE states.
Figure 3-1 provides the details about the RRC states.
Figure 3-1 RRC states
● RRC_CONNECTED: An RRC connection is established between the UE and the

gNodeB.
● RRC_IDLE: No RRC connection is established between the UE and the gNodeB.
● RRC_INACTIVE: In this state, the UE suspends data processing. However, the
gNodeB still maintains the UE's context information, and as a result, the core
network considers that the UE remains in the CM-CONNECTED state (as if it
were still in the RRC_CONNECTED state). When data transmission is required,
the UE can quickly transit to the RRC_CONNECTED state.

(2021-12-30)
5G RAN
NOTE
RRC connection release is performed for transition from RRC_CONNECTED to RRC_IDLE or

from RRC_CONNECTED to RRC_INACTIVE. The state (RRC_IDLE or RRC_INACTIVE) that a UE
has entered can be checked based on whether suspendConfig is included in the RRCRelease
message. If suspendConfig is included in the RRCRelease message, the UE has entered the
RRC_INACTIVE state. If suspendConfig is not included in the RRCRelease message, the UE
has entered the RRC_IDLE state.
For details about the RRC states, see section 4.2.1 "UE states and state transitions
including inter RAT" in 3GPP TS 38.331 V15.5.1.
5G supports standalone (SA) and non-standalone (NSA) networking options.

Therefore, mobility management is classified into SA networking mobility
management and NSA networking mobility management. This document
describes the mobility management of UEs in different RRC states in these
networking options.
SA Mobility Management
An SA network uses an end-to-end 5G network architecture, where the terminals,
base stations, and core network comply with 5G specifications. Figure 3-2 shows
SA networking. For details, see 5G Networking and Signaling.
Figure 3-2 SA networking (Option 2 as an example)
In SA networking, mobility management is classified into intra-RAT mobility

management and inter-RAT mobility management, depending on whether a
serving cell changes between two networks of different radio access technologies
(RATs). This document details SA intra-RAT mobility management. For details
about SA inter-RAT mobility management, see Interoperability Between E-UTRAN
and NG-RAN.
In the current version, SA intra-RAT mobility management is categorized based on

the UE's RRC state as follows:

(2021-12-30)
5G RAN
● Mobility management in the RRC_CONNECTED state (also referred to as

connected mode). For details, see 4 SA Mobility Management in Connected
Mode.
● Mobility management in the RRC_IDLE state (also referred to as idle mode).
For details, see 5 SA Mobility Management in Idle Mode.
● Mobility management in the RRC_INACTIVE state (also referred to as inactive
mode). For details, see 6 SA Mobility Management in Inactive Mode.
NSA Mobility Management

In NSA networking, terminals supporting E-UTRA-NR Dual Connectivity (EN-DC)
connect to both an LTE base station and a 5G New Radio (NR) base station, using
the radio resources of both of the base stations for transmission. The cell served
by the LTE base station (eNodeB) is the primary cell (PCell), and the cell served by
the 5G NR base station (gNodeB) is the primary SCG cell (PSCell). Figure 3-3
shows the NSA EN-DC networking. For details about NSA networking, see NSA
Networking based on EPC.
Figure 3-3 NSA EN-DC networking (Option 3x as an example)
NSA networking does not support the RRC_INACTIVE state. Therefore, in the
current version, NSA mobility management is categorized based on the UE's RRC
state as follows:
● Mobility management in the RRC_CONNECTED state: UEs are connected to

both the PCell and PSCell. Therefore, mobility management is categorized as
PCell change and PSCell change. This document describes PSCell change in 7
NSA Mobility Management in Connected Mode. For details about PCell
change, see NSA Networking based on EPC.
● Mobility management in the RRC_IDLE state: UEs camp on LTE cells. For
details, see Idle Mode Management in eRAN Feature Documentation.
In NSA and SA hybrid networking, the mobility management of UEs moving

between NSA and SA networks is the same as that of UEs moving between E-

(2021-12-30)
5G RAN
UTRAN and NG-RAN. For details, see Interoperability Between E-UTRAN and NG-
RAN.

(2021-12-30)
5G RAN
Description 4 SA Mobility Management in Connected Mode
4 SA Mobility Management in Connected

Mode
Mobility management in connected mode is a process during which a gNodeB

monitors air interface status, determines serving cell change, and changes serving
cells for RRC_CONNECTED UEs. Generally termed as handover, this process ensures
that the UEs receive uninterrupted services from networks while on the move.
5G supports multiple handover functions (listed in Table 4-1) to guarantee UE
mobility in various scenarios. Handover functions have the same basic procedure,
as described in 4.1 Basic Functions of Mobility Management in Connected
Mode. In addition, Table 4-1 summarizes the differences between these functions;
for more detailed descriptions, see the sections corresponding to each function.
Table 4-1 Principles of handover functions

Handover Starting Condition Stopping Execution
Function Condition Condition
4.2 Coverage- This function starts by default. N/A ● Event A3a is

based Intra- received.
Frequency ● The serving
Handover cell is
configured
with
neighboring
cells.

(2021-12-30)
5G RAN

4.3 Coverage- ● The specific function switch is turned on. Event A1 is ● Event A5 or
based Inter- – Handover: The COVERAGE_BASED_HO received. A3 is
Frequency option of the received.
Handover NRCellAlgoSwitch.InterFreqHoSwitch ● The serving
parameter is selected. cell is
– Redirectionb: The REDIRECTION option configured
of the with
NRCellAlgoSwitch.InterFreqHoSwitch neighboring
parameter is selected. cellsc.
● Event A2 is received.
4.4 ● The FREQ_PRIORITY_BASED_HO option Event A2 is ● Event A4 or

Frequency- of the received. A5 is
Priority-based NRCellAlgoSwitch.InterFreqHoSwitch received.
Inter- parameter is selected. ● The serving
Frequency ● Event A1 is received. cell is
Handover configured
with
neighboring
cells.
4.5 Operator- ● The OP_DED_PRI_BASED_HO option of N/A ● Event A4 or

specific- the A5 is
Priority-based NRCellAlgoSwitch.InterFreqHoSwitch received.
Inter- parameter is selected. ● The serving
Frequency ● A UE accesses, is handed over to, or has its cell is
Handover RRC connection reestablished in a cell configured
whose NR frequency is not an operator- with
desired target frequency. neighboring
cells.
4.6 Service- ● A UE initiates a service with a QCI that has N/A ● Event A4 or
based Inter- the highest priority. A5 is
Frequency ● The SERVICE_BASED_HO option of the received.
Handover NRCellAlgoSwitch.InterFreqHoSwitch ● The serving
parameter is selected. cell is
● The base station checks the priority of a configured
QoS flow when deciding whether to start with
service-based inter-frequency handover. neighboring
cells.
● The service with this QCI is associated with
a target frequency group.
● The serving frequency of the UE is not
within the target frequency range desired
for this service.

(2021-12-30)
5G RAN

4.7 Uplink- ● The UL_INTRF_BASED_HO option of the N/A ● Event A3 is

Interference- NRCellAlgoSwitch.InterFreqHoSwitch received.
based Inter- parameter is selected. ● The serving
Frequency ● The strength of uplink interference in the cell is
Handover serving cell is greater than the uplink configured
interference threshold (specified by the with
NRDUCellIntrfIdent.UlIntrfThld neighboring
parameter). cells.
4.8 SSB SINR- ● The SSB_SINR_BASED_HO option of the Event A1 is ● Event A3 is

based Inter- NRCellAlgoSwitch.InterFreqHoSwitch received. received.
Frequency parameter is selected. ● The serving
Handover ● Event A2 is received. cell is
configured
with
neighboring
cells.
Note:
a: For details about the events, see Measurement Event.
b: Handover policies consist of handover and redirection. For details, see Determination of a
Handover Policy.
c: Blind redirection does not have requirements for neighboring cell configurations. For details, see
4.3 Coverage-based Inter-Frequency Handover.
NOTE
Coverage-based intra-frequency handovers and coverage-based inter-frequency handovers

are also referred to as necessary handovers. Other types of handovers are referred to as
unnecessary handovers.
Mobility management policies for special services or scenarios are not described in this
document. Examples are as follows:
● Inter-RAT handover processing: Interoperability Between E-UTRAN and NG-RAN
● Load-based handover: Mobility Load Balancing
● Handover processing specific to VoNR: VoNR
● Handover processing specific to some UEs: Flexible User Steering
● Handover enhancement for high speed mobility: High Speed Mobility
● Handover processing in the case of carrier shutdown: Energy Conservation and Emission
Reduction
Inter-frequency handovers depend on inter-frequency measurements, which decrease UE
throughput, especially for cell edge users (CEUs). In addition, due to inter-frequency
measurement delay, an optimal carrier cannot be promptly selected for UEs. To address this
situation, virtual grid models are introduced to predict inter-frequency RSRP so that inter-
frequency measurements are not required, improving user experience. For details, see
Virtual Grid-based Multi-Frequency Coordination.

(2021-12-30)
5G RAN
4.1 Basic Functions of Mobility Management in

Connected Mode
4.1.1 Principles
This section describes the basic principles and mechanisms of SA mobility
management in connected mode. The detailed signaling procedure complies with
3GPP specifications. For details, see:
● Section 9.2.3 "Mobility in RRC_CONNECTED" in 3GPP TS 38.300 V15.6.0
● Sections 5.3.5 "RRC reconfiguration" and 5.3.7 "RRC connection re-
establishment" in 3GPP TS 38.331 V15.5.1
● Section 8.4 "UE Mobility Management Procedures" in 3GPP TS 38.413 V15.3.0
4.1.1.1 Basic Procedure

Figure 4-1 shows the basic handover procedure in SA networking.

(2021-12-30)
5G RAN
Figure 4-1 Basic handover procedure
1. 4.1.1.2 Handover Function Start Decision describes the conditions for

starting handover functions.
2. 4.1.1.3 Processing Mode Selection describes processing mode selection
(blind mode or measurement-based mode).
3. 4.1.1.4 Measurement Configuration Delivery describes the method and
contents of measurement configurations sent by the gNodeB to UEs.
4. 4.1.1.5 Measurement Reporting describes the requirements for UEs to send
measurement reports to the gNodeB.

(2021-12-30)
5G RAN
5. 4.1.1.6 Target Cell or Frequency Decision describes how the gNodeB selects
a handover policy and generates target cells or frequencies for a handover.
6. 4.1.1.7 Handover Execution describes how the gNodeB and UEs execute the
handover based on the handover policy.
7. 4.1.1.8 Handover Failure Penalty describes the penalty mechanism for UE
handover failures.
4.1.1.2 Handover Function Start Decision

Handover function start decision is a process of determining whether to start a
handover function based on its starting conditions (provided in Table 4-1). The
process depends on whether:
● The switch of the handover function is turned on.

● The signal quality of the serving cell meets the conditions.
4.1.1.3 Processing Mode Selection

After a handover function is started, the gNodeB selects a processing mode based
on the signal quality of the serving cell and related events.
Depending on whether UEs measure the signal quality of candidate target cells
before a handover, the processing mode is classified into measurement-based
mode and blind mode.
● Measurement-based mode: UEs measure the signal quality of a measurement
object on the per-frequency basis and report the results to the gNodeB based
on the measurement configurations delivered from the gNodeB. The gNodeB
then uses the measurement report to generate a target cell list.
● Blind mode: The gNodeB generates a target cell or frequency list based on
priority parameter configurations without instructing UEs to measure the
signal quality of candidate target cells.
NOTE
In blind mode, accessing a target cell has a high risk of failure due to the uncertain signal
quality of the target cell. As such, blind mode is not recommended in most cases. This
mode is only used when a quick handover is needed. Blind mode is widely used in high-
frequency scenarios. In these scenarios, mmWave signals attenuate quickly during
transmission and provide a limited coverage range due to high frequencies and short
wavelengths. When a UE moves at a high speed (for example, in high-speed railway
scenarios), the UE may have moved out of the source cell before the measurement of the
target cell or frequency is completed in measurement-based mode. Consequently, the
service drop rate increases. To prevent this, blind mode can be used, in which case a
handover is quickly implemented for the UE. However, blind mode has high requirements
on neighboring cell planning. In the case of improper neighboring cell planning, the UE
may experience an access failure.
4.1.1.4 Measurement Configuration Delivery

Measurement configuration delivery is a process during which the gNodeB sends
measurement configurations to UEs.
The gNodeB delivers measurement configurations as follows:

(2021-12-30)
5G RAN
● When a UE enters the RRC_CONNECTED state, the gNodeB includes

measurement configurations in an RRCReconfiguration message and sends
the message to the UE.
● After a UE enters the RRC_CONNECTED state or a handover is completed, in
case of any updates to its measurement configurations, the gNodeB includes
the updated measurement configurations in an RRCReconfiguration message
and sends the message to the UE. This section describes measurement
configuration delivery in this scenario.
Measurement configurations are configured by the gNodeB and then delivered to
UEs. They include the following information:
● Measurement objects, which include the RATs and frequencies (or cells) to be
measured.
They specify the frequencies or cells where UEs measure signal quality. The
cells to be measured can be the serving cell or neighboring cells, for which
the measurement procedures are the same. This section uses neighboring cell
measurement as an example to describe measurement configuration delivery.
For details, see 4.1.1.4.1 Measurement Object.
● Reporting configurations, which include measurement event information and
the triggering quantity of the measurement reports.
They specify the conditions and criteria for UEs to report measurement
results. For details, see 4.1.1.4.2 Reporting Configuration.
● Other configurations, which include SMTC, measurement gap, and
measurement filtering.
They specify the duration and interval for a UE to perform measurements as
well as other information. For details, see 4.1.1.4.3 Other Configurations.
4.1.1.4.1 Measurement Object

The attributes of measurement objects include RATs and frequencies (or cells) to
be measured, and key attributes are different in different RATs. Inter-RAT
measurement objects are described in Interoperability Between E-UTRAN and NG-
RAN. The key attributes of intra-RAT measurement objects include frequencies (or
cells) to be measured.
The gNodeB determines an RAT for measurement first and then selects the
frequencies from the cell-specific frequency relationships (or cells from the NRT)
of this RAT.
RAT Selection for Measurement

The gNodeB selects a RAT for measurement based on measurement events.
● For events A1 to A6, NR is selected.
● For events B1 and B2, a non-NR RAT (for example, E-UTRAN) is selected.
For details about the events, see Measurement Event.
Frequency Selection for Measurement

The gNodeB obtains the information about the SSB frequencies to be measured
from the cell configurations or cell-specific frequency relationships of the selected
RAT.

(2021-12-30)
5G RAN
Intra-frequency measurement refers to measuring cells that have the same SSB
frequency and SSB frequency subcarrier spacing (SCS) as the serving cell,
regardless of whether their bandwidths are the same or not. Inter-frequency
measurement refers to measuring cells that have different SSB frequencies from
the serving cell, or those that have the same SSB frequency as the serving cell but
different SSB frequency SCS.
● For intra-frequency measurement, the gNodeB sends the NR frequencies
determined by the NRDUCell.SsbDescMethod and NRDUCell.SsbFreqPos
parameters for measurement.
● For inter-frequency measurement:
– Common policy for inter-frequency measurement: If no RFSP-based inter-
frequency measurement policy is configured, the gNodeB selects the
frequencies to be sent for measurement based on the following common
policy (RFSP is short for RAT/Frequency Selection Priority):
▪ If the NRCellOpPolicy.gNBFreqPriorityGroupId parameter is set to

a value in the range of 0 to 254, the frequencies to be sent for
measurement are selected as follows:
○ If the OPERATOR_NR_FREQ_CFG_SW option of the
NRCellOpPolicy.FreqConfigPolicySwitch parameter is selected,
the gNodeB selects NR frequencies in the intersection of NR
frequencies determined by
gNBFreqPriorityGroup.SsbDescMethod and
gNBFreqPriorityGroup.SsbFreqPos and those determined by
NRCellFreqRelation.SsbDescMethod and
NRCellFreqRelation.SsbFreqPos for measurement.
○ If the OPERATOR_NR_FREQ_CFG_SW option of the
NRCellOpPolicy.FreqConfigPolicySwitch parameter is
deselected, the gNodeB selects NR frequencies determined by
NRCellFreqRelation.SsbFreqPos for measurement.
▪ If the NRCellOpPolicy MO is not configured or the

NRCellOpPolicy.gNBFreqPriorityGroupId parameter is set to 255,
the NR frequencies to be sent by the gNodeB for measurement are
determined by the NRCellFreqRelation.SsbDescMethod and
NRCellFreqRelation.SsbFreqPos parameters.
For details about the NRCellOpPolicy MO and its configuration, see
Multi-Operator Sharing.
NOTE
When configuring the gNBFreqPriorityGroup MO associated with the serving

PLMN of a UE, ensure that all neighboring frequencies of this operator are
configured. Those that are not will not be delivered to the UE, and the UE will
not be handed over to cells working on these frequencies.
– RFSP-based inter-frequency measurement policy: If the
INTER_FREQ_LIST_CTRL_SW option of the
NRCellAlgoSwitch.RfspAlgoSwitch parameter is selected, the
frequencies to be sent by the gNodeB for measurement are selected
based on the RFSP-based inter-frequency measurement policy. For details
about RFSP-based inter-frequency handover, see Flexible User Steering.

(2021-12-30)
5G RAN
Cell Selection for Measurement

The value of the NRCellRelation.CellIndividualOffset parameter for a cell
determines whether the cell's information (PCI and CIO) is sent.
● If this parameter is not set to 0, the cell information selected from the NRT is
sent for the measurement object.
Table 4-2 lists the protocol-defined maximum number of neighboring cells
that can be delivered for each measurement object. For details, see section 6.4
"RRC multiplicity and type constraint values" in 3GPP TS 38.331 V16.5.0.
Table 4-2 Maximum number of neighboring cells that can be delivered for
each measurement object
Neighbor Relationship Maximum Number of IE

Type Neighboring Cells
Intra-frequency 32a maxNrofCellMeas

neighboring cell
Inter-frequency 32b maxNrofCellMeas

neighboring cell
Neighboring E-UTRAN 32c maxCellMeasEUTRA

cell
a: Currently, a maximum of eight intra-frequency neighboring cells can be

delivered for each measurement object.
b: Currently, a maximum of eight inter-frequency neighboring cells can be
delivered for each measurement object.
c: Currently, a maximum of 32 neighboring E-UTRAN cells can be delivered
for each measurement object. This complies with 3GPP specifications.
● If this parameter is set to 0, the cell information is not sent for the
measurement object.
4.1.1.4.2 Reporting Configuration

Reporting configurations include:
● Measurement event, which can be A1, A2, A3, A4, A5, A6, B1, or B2. Handover
functions determine the measurement events to be used. For details, see the
sections corresponding to each handover function. For details about the
definition, entering conditions, and leaving conditions for each event, see
Measurement Event.
● Triggering quantity, which specifies the policy used to trigger event reporting
and can be reference signal received power (RSRP), reference signal received
quality (RSRQ), or signal to interference plus noise ratio (SINR). This version
supports SSB RSRP or RSRQ. For details, see Triggering Quantity.
Measurement Event
An event indicates signal quality. Table 4-3 lists the definition of each event.

(2021-12-30)
5G RAN
Table 4-3 Event definition

Event Type Event Definition
A1 The signal quality of the serving cell exceeds a specific threshold.
A2 The signal quality of the serving cell is below a specific threshold.
A3 The signal quality of a neighboring cell is higher than that of the

serving cell by a certain offset.
A4 The signal quality of a neighboring cell exceeds a specific

threshold.
A5 The signal quality of the serving cell is below threshold 1 and the
signal quality of a neighboring cell exceeds threshold 2.
A6 The signal quality of a neighboring cell is higher than that of the

secondary cell by a certain offset.
B1 The signal quality of an inter-RAT neighboring cell exceeds a

specific threshold.
B2 The signal quality of the serving cell is below threshold 1 and the
signal quality of an inter-RAT neighboring cell exceeds threshold
2.
The mechanisms for measurement configuration delivery and measurement

reporting are the same for all these events.
● Events A1 and A2 are used to evaluate the signal quality of the serving cell in
the handover function start decision phase and determine whether to start or
stop a handover function.
● The other events (A3, A4, A5, A6, B1, and B2) are used to evaluate the signal
quality of neighboring cells in the target cell or frequency decision phase and
determine whether to initiate handover execution.
Table 4-4 lists the entering and leaving conditions for these events. For details,
see section 5.5.4 "Measurement report triggering" in 3GPP TS 38.331 V15.5.1.
Table 4-4 Entering and leaving conditions for events

Event Entering Condition Leaving Condition Setting Notes
Type
A1 (Ms – Hys > Thresh) is (Ms + Hys < Thresh) is See Table 4-5.
true during the time true during the time
specified by TimeToTrig. specified by TimeToTrig.
A2 (Ms + Hys < Thresh) is (Ms – Hys > Thresh) is See Table 4-6.

(2021-12-30)
5G RAN
Event Entering Condition Leaving Condition Setting Notes

Type
A3 (Mn + Ofn + Ocn – Hys > (Mn + Ofn + Ocn + Hys < See Table 4-7.
Ms + Ofs + Ocs + Off) is Ms + Ofs + Ocs + Off) is
A4 (Mn + Ofn + Ocn – Hys > (Mn + Ofn + Ocn + Hys < See Table 4-8.
Thresh) is true during the Thresh) is true during the
time specified by time specified by
TimeToTrig. TimeToTrig.
A5 (Ms + Hys < Thresh1) (Ms – Hys > Thresh1) or See Table 4-9.
and (Mn + Ofn + Ocn – (Mn + Ofn + Ocn + Hys <
Hys > Thresh2) are true Thresh2) is true during
during the time specified the time specified by
by TimeToTrig. TimeToTrig.
A6 (Mn + Ocn – Hys > Ms + (Mn + Ocn + Hys < Ms + Applicable to
Ocs + Off) is true during Ocs + Off) is true during carrier
the time specified by the time specified by aggregation
TimeToTrig. TimeToTrig. (CA). For
details, see
Carrier
Aggregation.
B1 (Mn + Ofn + Ocn – Hys > (Mn + Ofn + Ocn + Hys < Applicable to
Thresh) is true during the Thresh) is true during the inter-RAT
time specified by time specified by scenarios. For
TimeToTrig. TimeToTrig. details, see
Interoperability
Between E-
UTRAN and
NG-RAN.
B2 (Ms + Hys < Thresh1) (Ms – Hys > Thresh1) or Applicable to
and (Mn + Ofn + Ocn – (Mn + Ofn + Ocn + Hys < inter-RAT
Hys > Thresh2) are true Thresh2) is true during scenarios. For
during the time specified the time specified by details, see
by TimeToTrig. TimeToTrig. Interoperability
Between E-
UTRAN and
NG-RAN.
The variables in the preceding formulas are defined as follows:
● Ms and Mn: measurement results of the serving cell and a neighboring cell,
respectively
● Hys: hysteresis for an event
● TimeToTrig: duration during which a condition is met before the event can be
triggered

(2021-12-30)
5G RAN
● Thresh, Thresh1, and Thresh2: thresholds

● Ofs and Ofn: frequency-specific offsets for the serving cell and a neighboring
cell, respectively
● Ocs and Ocn: CIO for the serving cell and a neighboring cell, respectively
● Off: offset for an event
Variable configuration is event specific. The following describes the entering
conditions and parameters for variables of each event.
Entering condition for event A1: (Ms – Hys > Thresh) is true throughout the
duration specified by TimeToTrig. Table 4-5 describes the parameters for the
variables.
Table 4-5 Variable configuration of event A1

Variable Parameter Parameter ID Remarks
Name
Hys Inter- NRCellInterFHo This variable represents the

frequency MeaGrp.InterFre hysteresis for events A1/A2
A1A2 qA1A2Hyst related to inter-frequency
Hysteresis measurements and is
configured through this
parameter.
Thresh Cov Inter- NRCellInterFHo This variable represents the

freq MeaGrp.CovInter RSRP threshold for event A1
Handover A1 FreqA1RsrpThld related to coverage-based
RSRP inter-frequency
Threshold measurements and is
parameter.

freq HO A1 MeaGrp.CovInter RSRQ threshold for event A1
RSRQ FreqA1RsrqThld related to coverage-based
Threshold inter-frequency
measurements and is
parameter.

(2021-12-30)
5G RAN

Name
Thresh Freq Priority NRCellInterFHo ● If the threshold for event

Inter-freq A1 MeaGrp.FreqPriIn A1 related to frequency-
RSRP terFA1RsrpThld priority-based handover is
Threshold not customized for a UE's
RFSP, the threshold is
equal to the value of the
NRCellInterFHoMeaGrp.F
reqPriInterFA1RsrpThld
parameter.
● If the threshold for event
A1 related to frequency-
priority-based handover is
customized for a UE's
equal to the sum of the
values for the
and
gNBRfspConfig.FreqPriHo
A1A2RsrpThldOfs
parameters.
Thresh A3 Inter-freq NRCellInterFHo This variable represents the

Handover A1 MeaGrp.A3InterF RSRP threshold for event A1
RSRP reqHoA1RsrpThl related to event A3-based
Threshold d coverage-based inter-
frequency handover and is
parameter.
Thresh SSB SINR NRCellInterFHo This variable represents the

Inter-freq HO MeaGrp.SsbSinrI threshold for event A1
A1 Threshold nterFreqHoA1Thl related to SSB SINR-based
d inter-frequency handover and
is configured through this
parameter.
TimeToTrig Inter- NRCellInterFHo This variable represents the

frequency MeaGrp.InterFre time-to-trigger for events
A1A2 Time to qA1A2TimeToTri A1/A2 related to inter-
Trigger g frequency measurements and
parameter.
Entering condition for event A2: (Ms + Hys < Thresh) is true throughout the
duration specified by TimeToTrig. Table 4-6 describes the parameters for the
variables.

(2021-12-30)
5G RAN

Name
Hys Inter- NRCellInterFHo This variable represents the

frequency MeaGrp.InterFre hysteresis for events A1/A2
A1A2 qA1A2Hyst related to inter-frequency
parameter.

freq MeaGrp.CovInter RSRP threshold for event A2
Handover A2 FreqA2RsrpThld related to coverage-based
Threshold measurements and is
parameter.

freq HO A2 MeaGrp.CovInter RSRQ threshold for event A2
RSRQ FreqA2RsrqThld related to coverage-based
Threshold inter-frequency
measurements and is
parameter.
Thresh Cov HO to E- NRCellInterRHo This variable represents the

UTRAN Blind MeaGrp.CovHoTo RSRP threshold for event A2
A2 RSRP Thld EutranBlindA2Th related to inter-frequency
ld blind redirection and is
parameter (also used for
inter-RAT blind redirection).
Thresh Cov HO to E- NRCellInterRHo This variable represents the

UTRAN Blind MeaGrp.CovHoTo RSRQ threshold for event A2
A2 RSRQ LteBlindA2RsrqT related to inter-frequency
Thld hld blind redirection and is
parameter (also used for
inter-RAT blind redirection).

(2021-12-30)
5G RAN

Name
Thresh Freq Priority NRCellInterFHo ● If the threshold for event

Inter-freq A2 MeaGrp.FreqPriIn A2 related to frequency-
RSRP terFA2RsrpThld priority-based handover is
Threshold not customized for a UE's
equal to the value of the
parameter.
● If the threshold for event
A2 related to frequency-
priority-based handover is
customized for a UE's
equal to the sum of the
values for the
and
gNBRfspConfig.FreqPriHo
A1A2RsrpThldOfs
parameters.
Thresh A3 Inter-freq NRCellInterFHo This variable represents the

Handover A2 MeaGrp.A3InterF RSRP threshold for event A2
RSRP reqHoA2RsrpThl related to event A3-based
Threshold d coverage-based inter-
parameter.
Thresh SSB SINR NRCellInterFHo This variable represents the

Inter-freq HO MeaGrp.SsbSinrI threshold for event A2
A2 Threshold nterFreqHoA2Thl related to SSB SINR-based
d inter-frequency handover and
parameter.
TimeToTrig Inter- NRCellInterFHo This variable represents the

frequency MeaGrp.InterFre time-to-trigger for events
A1A2 Time to qA1A2TimeToTri A1/A2 related to inter-
Trigger g frequency measurements and
parameter.
Entering condition for event A3: (Mn + Ofn + Ocn – Hys > Ms + Ofs + Ocs + Off) is
true throughout the duration specified by TimeToTrig. Table 4-7 describes the
parameters for the variables.

(2021-12-30)
5G RAN

Name
Ofn None None This variable is fixed at 0.
Ocn Cell NRCellRelation.C This variable represents the

Individual ellIndividualOff- CIO of a neighboring cell.
Offset set ● If the value is not DB0,
this parameter is included
in measurement
configurations.
● If the value is DB0, this
parameter is not included
in measurement
configurations and 0 is
used for calculation by
default.
Hys Intra- NRCellIntraFHo This variable represents the

frequency MeaGrp.IntraFre hysteresis for event A3
Handover A3 qHoA3Hyst related to intra-frequency
parameter.
Hys Inter-freq NRCellInterFHo This variable represents the

Measuremen MeaGrp.InterFre hysteresis for event A3
t Event qA4A5Hyst related to inter-frequency
Hysteresis handover and is configured
through this parameter.
Hys None None In the case of uplink-

interference-based inter-
frequency handovers, the
hysteresis for event A3
related to inter-frequency
measurements is fixed at 1
dB.
Ofs None None This variable is fixed at 0.
Ocs None None This variable is fixed at 0.
Off Intra- NRCellIntraFHo This variable represents the

frequency MeaGrp.IntraFre offset for event A3 related to
Handover A3 qHoA3Offset intra-frequency
Offset measurements and is
parameter.

(2021-12-30)
5G RAN

Name
Off Intrf-based NRCellInterFHo This variable represents the

Inter-Freq MeaGrp.IntrfInte RSRP offset for event A3
HO A3 RSRP rFreqHoA3RsrpO related to uplink-
Offset fs interference-based inter-
parameter. If the RSRP of a
neighboring cell minus the
RSRP of the serving cell is
greater than the offset, event
A3 will be reported.
Off Inter- NRCellInterFHo This variable represents the

frequency MeaGrp.InterFre offset for event A3 related to
Handover A3 qHoA3Offset inter-frequency handover and
Offset is configured through this
parameter.
TimeToTrig Intra- NRCellIntraFHo This variable represents the

frequency MeaGrp.IntraFre time-to-trigger for event A3
Handover A3 qHoA3TimeToTri related to intra-frequency
Time To g measurements and is
Trigger configured through this
parameter.
TimeToTrig Inter-freq NRCellInterFHo This variable represents the

Measuremen MeaGrp.InterFre time-to-trigger for event A3
t Event Time qA4A5TimeToTri related to inter-frequency
to Trigger g handover and is configured
through this parameter.
TimeToTrig None None In the case of uplink-

interference-based inter-
frequency handovers, the
time-to-trigger for event A3
related to inter-frequency
measurements is fixed at 320
ms.
Entering condition for event A4: (Mn + Ofn + Ocn – Hys > Thresh) is true
throughout the duration specified by TimeToTrig. Table 4-8 describes the
parameters for the variables.

(2021-12-30)
5G RAN

Name
Ofn Frequency NRCellFreqRelati This variable represents the

Offset for on.ConnFreqOffs connected-mode frequency-
Connected et specific offset of a non-
Mode serving frequency and is
parameter.

in measurement
configurations.
in measurement
default.

parameter.
Thresh Freq Priority NRCellInterFHo This variable represents the

Inter-freq A4 MeaGrp.FreqPriIn RSRP threshold for event A4
RSRP terFA4RsrpThld related to frequency-priority-
Threshold based inter-frequency
measurements and is
parameter.
Thresh Operator Ded NRCellInterFHo This variable represents the

Pri Inter-freq MeaGrp.OpDedPr RSRP threshold for event A4
HO A4 RSRP iHoA4RsrpThld related to operator-specific-
Thld priority-based inter-frequency
measurements and is
parameter.
Thresh Srv-Based NRCellInterFHo This variable represents the

Inter-freq A4 MeaGrp.SrvInter RSRP threshold for event A4
RSRP FreqA4RsrpThld related to service-based inter-
Threshold frequency measurements and
parameter.

(2021-12-30)
5G RAN

Name

to Trigger g measurements and is
parameter.
Entering condition for event A5: (Ms + Hys < Thresh1) and (Mn + Ofn + Ocn – Hys
> Thresh2) are true throughout the duration specified by TimeToTrig. Table 4-9
describes the parameters for the variables.

Name

parameter.
Thresh1 Cov Inter- NRCellInterFHo This variable represents RSRP

freq MeaGrp.CovInter threshold 1 for event A5
Handover A5 FreqA5RsrpThld1 related to coverage-based
Threshold1 measurements and is
parameter.
Thresh1 RSRP None This variable is fixed at –43

threshold 1 dBm.
for event A5
related to
frequency-
priority-
based inter-
frequency
measuremen
ts

(2021-12-30)
5G RAN

Name

threshold 1 dBm.
for event A5
related to
operator-
specific-
priority-
based inter-
frequency
measuremen
ts

threshold 1 dBm.
for event A5
related to
service-based
inter-
frequency
measuremen
ts
Thresh2 Cov Inter- NRCellInterFHo This variable represents RSRP

freq MeaGrp.CovInter threshold 2 for event A5
Handover A5 FreqA5RsrpThld2 related to coverage-based
Threshold2 measurements and is
parameter.
Thresh2 RSRP NRCellInterFHo This variable represents RSRP

threshold 2 MeaGrp.FreqPriIn threshold 2 for event A5
for event A5 terFA4RsrpThld related to frequency-priority-
related to based inter-frequency
frequency- measurements and is
priority- configured through this
based inter- parameter.
frequency
measuremen
ts

(2021-12-30)
5G RAN

Name

threshold 2 MeaGrp.OpDedPr threshold 2 for event A5
for event A5 iHoA4RsrpThld related to operator-specific-
related to priority-based inter-frequency
operator- measurements and is
specific- configured through this
priority- parameter.
based inter-
frequency
measuremen
ts

threshold 2 MeaGrp.SrvInter threshold 2 for event A5
for event A5 FreqA4RsrpThld related to service-based inter-
related to frequency measurements and
service-based is configured through this
inter- parameter.
frequency
measuremen
ts
Ofn Frequency NRCellFreqRelati This variable represents the

Offset for on.ConnFreqOffs connected-mode frequency-
Connected et specific offset of a non-
Mode serving frequency and is
parameter.

in measurement
configurations.
in measurement
default.

to Trigger g measurements and is
parameter.

(2021-12-30)
5G RAN
QCI-specific Measurement Parameter Configuration

QoS defines the performance level of a service and indicates the level of customer
satisfaction. QCIs indicate the QoS levels of DRBs.
A measurement parameter group can be configured separately for each QCI. If a
UE has multiple radio bearers (in the case of combined services), each of the
bearers has a QCI and measurement parameters can be configured separately for
each QCI. Further details are as follows:
● Intra-frequency measurement: The same method of QCI-specific
measurement parameter configuration applies to SA UEs and NSA UEs. The
details are as follows: The NRCellIntraFHoMeaGrp MO is configured to
specify a measurement parameter group
(NRCellIntraFHoMeaGrp.IntraFreqHoMeasGroupId) related to intra-
frequency handovers for an NR cell. The group is then bound to a QCI using
the NRCellQciBearer.IntraFreqHoMeasGroupId and NRCellQciBearer.Qci
parameters. Through such configuration, intra-frequency measurement
parameters are configured separately for services with different QCIs.
● Inter-frequency measurement: The method of QCI-specific measurement
parameter configuration is different between SA UEs and NSA UEs. The
details are as follows:
– SA UEs: The NRCellInterFHoMeaGrp MO is configured to specify a
measurement parameter group
(NRCellInterFHoMeaGrp.InterFreqHoMeasGroupId) related to inter-
frequency handovers for an NR cell. The group is then bound to a QCI
using the NRCellQciBearer.InterFreqHoMeasGroupId and
NRCellQciBearer.Qci parameters. Through such configuration, inter-
frequency measurement parameters are configured separately for services
with different QCIs.
– NSA UEs: The NRCellInterFHoMeaGrp MO is configured to specify a
measurement parameter group
(NRCellInterFHoMeaGrp.InterFreqHoMeasGroupId) related to inter-
frequency handovers for an NR cell. The group is then bound to a QCI
using the NRCellQciBearer.NsaInterFreqHoMeasGroupId and
NRCellQciBearer.Qci parameters. Through such configuration, inter-
frequency measurement parameters are configured separately for services
with different QCIs.
In the case of combined services, the gNodeB sends a group of measurement
parameters configured for the QCI that has the highest priority for handovers. The
priority of a QCI for handovers is configured by the
gNBQciBearer.QciPriorityForHo parameter and a smaller value of this parameter
indicates a higher QCI priority for handovers. When
gNBQciBearer.QciPriorityForHo is set to 255, the priority of a QCI for handovers
equals the value of gNBQciBearer.PriorityLevel and a smaller value indicates a
higher QCI priority for handovers.
If the priorities of different QCIs for handovers obtained based on the preceding
principle are the same, the gNodeB sorts the QCIs and sends a group of
measurement parameters configured for the smallest QCI. For details, see section
6.1.7 "Standardized QoS characteristics" in 3GPP TS 23.203 V15.4.0.

(2021-12-30)
5G RAN
Triggering Quantity
Triggering quantity specifies the policy used to trigger event reporting and can be
RSRP, RSRQ, or SINR. This version supports SSB RSRP, SINR, or RSRQ. Further
details are as follows:
● Only RSRP: Measurement is triggered and stopped based only on the RSRP.
The gNodeB sends only the RSRP-indicating measurement configuration
related to an event to a UE, based on which the UE performs measurements.
When determining that the measured RSRP of a frequency (or cell) meets the
entering conditions (as indicated in Table 4-4) for the event, the UE sends a
measurement report to the gNodeB.
● RSRP and RSRQ: Measurement is triggered and stopped based on both the
RSRP and RSRQ, and the RSRP-based process is independent of the RSRQ-
based process. The gNodeB sends both RSRP- and RSRQ-indicating
measurement configurations related to an event to a UE, based on which the
UE performs measurements. When determining that the measured RSRP or
RSRQ of a frequency (or cell) meets the entering conditions (as indicated in
Table 4-4) for the event, the UE sends a measurement report to the gNodeB.
● RSRP combined with RSRQ-based filtering: Measurement is triggered and
stopped based only on the RSRP, but a measurement report includes both the
measured RSRP and RSRQ. Specific neighboring cells are filtered out based on
the measured RSRQ. The gNodeB sends both RSRP- and RSRQ-indicating
measurement configurations related to an event to a UE, based on which the
UE performs measurements. When determining that the measured RSRP of a
frequency (or cell) meets the entering conditions (as indicated in Table 4-4)
for the event, the UE sends the gNodeB a measurement report including the
measured RSRP and RSRQ. Then, the gNodeB generates a candidate cell list
or a candidate frequency list based on the measured RSRP, and filters out
specific candidate cells based on the measured RSRQ. For details about RSRQ-
based filtering, see Generation of a Target Cell or Frequency List.
● Only SINR: Measurement is triggered and stopped based only on the SINR.
The gNodeB sends only the SINR-indicating measurement configuration
related to an event to a UE, based on which the UE performs measurements.
When determining that the measured SINR of a frequency (or cell) meets the
entering conditions (as indicated in Table 4-4) for the event, the UE sends a
measurement report to the gNodeB.
Table 4-10 lists the triggering quantities specific to handover functions. For
details, see the sections corresponding to each handover function.
Table 4-10 Event triggering quantities specific to handover functions

Handover Function Event That Triggers Event That Stops a Event That Triggers the
the Start of a Handover Function Execution of a
Handover Function Handover
4.2 Coverage-based N/A N/A Event A3: only RSRP

Intra-Frequency
Handover

(2021-12-30)
5G RAN
Handover Function Event That Triggers Event That Stops a Event That Triggers the
the Start of a Handover Function Execution of a
Handover Function Handover
4.3 Coverage-based Event A2: Event A1: Event A5:

Inter-Frequency ● Only RSRP ● Only RSRP ● Only RSRP
Handover
● RSRP and RSRQ ● RSRP and RSRQ ● RSRP combined with
RSRQ-based filtering
Event A3: only RSRP
4.4 Frequency- Event A1: only RSRP Event A2: only RSRP Event A4: only RSRP
Priority-based Event A5: only RSRP
Inter-Frequency
Handover
4.5 Operator- N/A N/A Event A4: only RSRP

specific-Priority- Event A5: only RSRP
based Inter-
Frequency
Handover
4.6 Service-based N/A N/A Event A4: only RSRP

Inter-Frequency Event A5: only RSRP
Handover
4.7 Uplink- N/A N/A Event A3: only RSRP

Interference-based
Inter-Frequency
Handover
4.8 SSB SINR-based Event A2: only SINR Event A1: only SINR Event A3: only RSRP
Inter-Frequency
Handover
4.1.1.4.3 Other Configurations
SMTC Measurement Configuration

An SMTC is a measurement configuration that the gNodeB sends to a UE, which
includes an SMTC period, SMTC duration, and SMTC offset. These serve as the
instructions for the UE to perform SSB measurements in a cell. For details, see
section 5.5.2.10 "Reference signal measurement timing configuration" and section
6.3.2 "Radio resource control information elements" in 3GPP TS 38.331 V15.5.1.
● The SMTC period determines the interval at which the UE starts SSB
measurements. It is configured by the NRDUCell.SmtcPeriod parameter for
intra-frequency measurements and by the NRCellFreqRelation.SmtcPeriod
parameter for inter-frequency measurements.

(2021-12-30)
5G RAN
NOTE
SMTC is specific to frequencies. If the cells on the same frequency have different SSB
periods (configured by the NRDUCell.SsbPeriod parameter), SSB measurements may
be inaccurate for the cells whose SSB periods are longer than the corresponding SMTC
period. To prevent this, ensure that the cells on the same frequency use the same SSB
period (configured by the NRDUCell.SsbPeriod parameter) according to the network
plan.
● The SMTC duration determines the time during which the UE performs SSB
measurements in each SMTC period. It is configured by the
NRDUCell.SmtcDuration parameter for intra-frequency measurements and
by the NRCellFreqRelation.SmtcDuration parameter for inter-frequency
measurements.
The NRDUCell.SmtcDuration and NRCellFreqRelation.SmtcDuration
parameters take effect only for low frequency bands. The system
automatically calculates the SMTC duration for high frequency bands.
● The SMTC offset determines the time offset for the UE to start SSB
measurements in each SMTC period. The offset is calculated by the gNodeB to
ensure accurate SSB measurements by the UE. The following configurations
affect the SMTC offset calculation. If they do not meet the corresponding
requirements, the SSB measurement result may be inaccurate.
The frame offsets (specified by the gNBFreqBandConfig.FrameOffset
parameter) of frequency bands must meet all of the following conditions:
– The frame offset of a frequency band must be the same for all base
stations on the entire network.
– If the frame offsets for the to-be-measured frequency bands differ, the
maximum difference must not exceed 3 ms.
– If the frame offsets for the serving and to-be-measured frequency bands
differ, the maximum difference must not exceed 4 ms.
– If the frame offset of a frequency band is configured on a base station on
the network, the frame offset of this band must also be specified on
neighboring base stations, even if these neighboring base stations do not
serve any cell in this band. This ensures that this frequency band is
accurately measured by UEs served by these neighboring base stations.
NOTE
If frame offsets are different between frequency bands, the measurement gap
configured for a UE must be sufficient to include the SMTC duration of cells in
different frequency bands, reducing the throughput during inter-frequency
measurements. If the maximum difference between said frame offsets exceeds 3 ms,
the measurement gap is insufficient to include the SMTC duration of all cells. As a
result, inter-frequency measurement is incomplete, affecting the handover success
rate.
In cases where the frame offsets for the serving and to-be-measured frequency bands
differ and the maximum difference exceeds 4 ms, the gNodeB cannot send a
measurement gap. As a result, inter-frequency measurement is incomplete, affecting
the handover success rate. For details, see Measurement Gap Configuration.
For details about frame offsets of frequency bands, see Standards Compliance.
Time synchronization between the serving cell and the cell to be measured
affects the calculation of the SMTC offset. The following applies only when
the cell to be measured is an NR FDD cell and the serving cell is an NR FDD
cell or NR TDD cell:

(2021-12-30)
5G RAN
– If time synchronization is configured with its precision being +/- 1.5 μs,
you are advised to set the intra-frequency SMTC duration (specified by
NRDUCell.SmtcDuration) and the inter-frequency SMTC duration
(specified by NRCellFreqRelation.SmtcDuration) to their recommended
values.
– If time synchronization is configured with its precision being +/- 500 μs
(indicating that 1588V2 loose time synchronization takes effect), you are
advised to set both the intra-frequency SMTC duration (specified by
NRDUCell.SmtcDuration) and the inter-frequency SMTC duration
(specified by NRCellFreqRelation.SmtcDuration) to 4 ms or 5ms.
If both the intra- and inter-frequency SMTC durations are set to 5 ms, UE
compatibility issues may occur. In this context, Huawei introduces the
SMTC offset compatibility function, which is controlled by the
SMTC_OFFSET_COMPAT_SW option of the
NRDUCellAlgoSwitch.AlgoCompatibilitySwitchExt parameter. This
function can be enabled when the serving cell is an NR FDD cell or a low-
frequency NR TDD cell.
▪ If this option is deselected for the serving cell and 1588V2 loose time
synchronization takes effect, UE compatibility issues may occur when
both the intra- and inter-frequency SMTC durations are set to 5 ms.
UEs with compatibility issues may encounter the following situations:
repeated SgNB addition and release in NSA networking; service drops
in SA networking.
▪ If this option is selected for the serving cell and 1588V2 loose time
synchronization takes effect, UE compatibility issues do not occur
when both the intra- and inter-frequency SMTC durations are set to
5 ms. In this case, however, incomplete intra-frequency SSB
measurements may decrease the RRC connection setup success rate
and handover success rate, and incomplete inter-frequency SSB
measurements may decrease the handover success rate.
– If time synchronization is not configured, inter-base-station handovers
may fail due to exceptions in neighboring cell measurements. Therefore,
the clock synchronization mode of the gNodeB must be set to time
synchronization.
For details about time synchronization or frequency synchronization, see
Synchronization.
Measurement Gap Configuration

A measurement gap is a period during which a UE performs measurements on a
non-serving frequency, and is only used for inter-frequency measurements.
There are 24 protocol-defined gap patterns, with each specific to a measurement
gap length and a measurement gap repetition period. Measurement gap
configurations are sent to UEs through measurement configurations. In the
current version, the gNodeB supports gap pattern adaptation based on UE
capabilities and SMTC to minimize the overhead of gap-assisted measurements.
For details about measurement gaps, see section 9.1.2 "Measurement gap" in
3GPP TS 38.133 V15.5.0.
When an inter-frequency measurement is required, the gNodeB determines
whether to send a measurement gap as follows:

(2021-12-30)
5G RAN
● If a measurement gap has been configured, a new measurement gap is not

sent.
● If no measurement gap has been configured, a measurement gap is sent.
To ensure the complete measurement of a non-serving frequency, the actual
measurement duration within a measurement gap must cover the entire SMTC
duration of this frequency. The actual measurement duration equals the
measurement gap minus the time required for a frequency switch before and after
the measurement. Figure 4-2 shows an example for TDD.
Figure 4-2 Example of measurement gap and SMTC duration configuration
If a UE needs to start both intra-frequency and inter-frequency measurements,

and the SMTC period for the intra-frequency measurement is greater than or
equal to the measurement gap repetition period, the SMTC duration for the intra-
frequency measurement is entirely included in the inter-frequency measurement
gap. As a result, the intra-frequency measurement cannot be performed. In this
case, the gNodeB configures equal-opportunity intra-frequency and inter-
frequency measurements, allowing the UE to alternatively perform such
measurements through gap sharing.
If a UE needs to initiate inter-frequency measurements, frame offsets must be
configured in accordance with the following requirements for the serving and to-
be-measured frequency bands:
● The difference in the frame offsets (gNBFreqBandConfig.FrameOffset)
between the serving and to-be-measured frequency bands must not exceed 4
ms. If it exceeds 4 ms, the gNodeB cannot send a measurement gap. As a
result, inter-frequency measurement is incomplete, affecting the handover
success rate.
● If the UE needs to measure multiple frequency bands with different frame
offsets, the gNodeB selects the maximum gap to cover the SMTC durations of
all the frequency bands to be measured. The protocol-defined maximum gap
is 6 ms, but when the frame offsets for multiple to-be-measured frequency
bands differ by more than 3 ms, the maximum gap may not cover the SMTC
durations of all the to-be-measured frequency bands. As a result, inter-
frequency measurement is incomplete, affecting the handover success rate.
For this reason, when the frame offsets (gNBFreqBandConfig.FrameOffset)
for frequency bands are different, it is recommended that these frame offsets
not differ by more than 3 ms.
UEs cannot transmit uplink signals or receive downlink signals on the serving
frequency throughout the measurement gap (for inter-frequency measurements),

(2021-12-30)
5G RAN
which reduces the uplink and downlink throughput of those UEs. In addition,
when the PUCCH SR period is greater than or equal to the gap repetition period,
PUCCH SR may conflict with gap-assisted measurement in the time domain. As a
result, service drops occur. In this version, the function of non-overlapping
between gap and NR resources is now supported in low-frequency SA networking,
which staggers the channel resources of specific signals (SRS, PUCCH SR, CSI-RS
for CM, and CSI-RS for CM measurement reporting) from the measurement gap in
the time domain. The GAP_AVOID_NR_RES_SW option of the
gNBMobilityCommParam.MeasAlgoSwitch parameter specifies whether to
enable the function of non-overlapping between gap and NR resources.
● If this option is deselected, the channel resources of the said signals are not
staggered from the measurement gap in the time domain. In this case, the
measurement gap preferentially takes effect on UEs, which do not transmit or
receive signals during the measurement gap.
● If this option is selected, the channel resources of the said signals are
staggered from the measurement gap in the time domain. This setting
reduces the loss in uplink and downlink UE throughput caused by gap-
assisted measurement and the rate of service drops caused by conflicts
between PUCCH SR and gap-assisted measurement but prolongs the
measurement duration.
SSB Measurement Position Delivery Configuration

3GPP specifications define SSB patterns in the time domain. Given a certain
pattern, the number of SSBs can be changed for high-frequency cells to adjust cell
capacity and coverage capability. For details, see mmWave Beam Management
(High-Frequency TDD). After SSB beam adjustment, SSB beam positions must be
signaled to UEs for SSB measurements. The SSB measurement positions are sent
to UEs through the ssb-ToMeasure IE, and the UEs then perform SSB
measurements at the corresponding positions.
In the case of neighboring cell measurements, the base station not only sends the
SSB measurement positions of the serving cell, but may also send the SSB
measurement positions of neighboring cells (depending on the
SSB_MEAS_POS_POLICY_SW option of the NRCellAlgoSwitch.MeasPolicySwitch
parameter).
● If this option is deselected, the gNodeB sends only the SSB measurement
positions of the serving cell to UEs.
● If this option is selected, the gNodeB sends the SSB measurement positions of
both the serving and neighboring cells to UEs.
– If an Xn interface is available between base stations, the SSB
measurement positions of neighboring cells can be directly obtained over
this interface.
– If no Xn interface is available between base stations, an Xn interface self-
setup is triggered before the SSB measurement positions of neighboring
cells can be obtained.
This function applies only to high-frequency cells in NSA networking. The Xn
interface created in NSA networking can serve only this function.

(2021-12-30)
5G RAN
Optimized Configuration for deriveSSB-IndexFromCell

The gNodeB includes the deriveSSB-IndexFromCell IE (either set to TRUE or
FALSE) in measurement configurations. For intra-frequency neighboring cell
measurements, the value of this IE indicates whether UEs derive the SSB indexes
of all intra-frequency neighboring cells based on the timing information of the
serving cell. For inter-frequency neighboring cell measurements, it indicates
whether UEs derive the SSB indexes of all neighboring cells on the frequency of
any detected inter-frequency cell based on the timing information of that cell. If
all cells on a frequency are time-synchronized, you can improve the efficiency and
accuracy of detecting neighboring cells' SSB indexes by setting this IE to TRUE.
Optimized configuration for deriveSSB-IndexFromCell has been introduced, and is
enabled if the PROTOCOL_IE_OPT_SW option the
NRCellAlgoSwitch.HoCompatibilitySwitch parameter is selected. When this
function is enabled, the value of the deriveSSB-IndexFromCell IE in the
measurement configurations sent from the gNodeB varies with the RATs
corresponding to the frequencies that are to be measured. If an NR TDD frequency
is to be measured, the value of the deriveSSB-IndexFromCell IE is TRUE. If an NR
FDD frequency is to be measured, the value of the deriveSSB-IndexFromCell IE is
FALSE.
Configuration of SSB Beam Measurement Result Selection and Combination

A UE needs to combine the SSB beam-level measurement results of a cell when
calculating the cell-level SSB measurement result. These beam-level results must
meet the SSB combination threshold requirement. The SSB combination threshold
is specified by the NRCellMobilityConfig.SsbConsolidationThld parameter. Upon
detecting that multiple SSB beams in a cell meet the combination threshold
requirement, the UE combines the measurement results of these SSB beams into a
cell-level result. The maximum number of SSB beams whose measurement results
can be combined is specified by the NRCellMobilityConfig.SsbNumToAverage
parameter.
Measurement Filtering Configuration

Before evaluating the conditions for entering or leaving an event and sending
measurement reports, the UE filters measurement results based on filtering
coefficients as follows:
● Beam-level filtering, in which the filtering coefficient is specified by the
NRCellMobilityConfig.BeamRsrpFilterCoeff parameter.
● Cell-level filtering, in which the filtering coefficient is specified by the
NRCellMobilityConfig.CellRsrpFilterCoeff parameter.
Measurement ID Preemption
A measurement ID links a measurement object with a reporting configuration as a
set. Given a measurement ID, a UE measures the associated measurement object
according to the reporting configuration. With multiple measurement IDs
configured, it is possible to link multiple measurement objects to the same
reporting configuration, as well as to link multiple reporting configurations to the
same measurement object. Figure 4-3 provides an example, in which both
measObjectID 1 and measObjectID 2 are linked to reportConfigID 1, and

(2021-12-30)
5G RAN
measObjectID 2 is linked to both reportConfigID 1 and reportConfigID 2. A UE

includes a measurement ID in a measurement report sent to the base station,
which then identifies the corresponding measurement object and reporting
configuration based on this measurement ID.
Figure 4-3 Measurement ID
The base station sends measurement configurations to UEs on a per measurement

ID basis and in sequence based on the triggering time until the number of sent
measurement IDs reaches the upper limit. Once this limit is reached, the base
station cannot send new measurement configurations to UEs. Consequently, some
high-priority measurement configurations (such as those for coverage-based
handovers) may fail to be sent, leading to service drops or handover failures. To
prevent this, measurement ID preemption is introduced. This function is controlled
by the MEAS_ID_PREEMPTION_SW option of the
gNBMobilityCommParam.MeasAlgoSwitch parameter.
● If this option is selected, measurement ID preemption is enabled. If the
number of sent measurement IDs has reached the upper limit, a UE's high-
priority measurement IDs can preempt the measurement resources of its low-
priority measurement IDs. This mechanism ensures that high-priority
measurement configurations, such as mobility-related measurement
configurations, can be successfully sent. If the number of sent measurement
IDs has not reached the upper limit, measurement IDs are not preempted and
measurement configurations are sent to UEs in sequence based on the
triggering time.
● If this option is deselected, measurement ID preemption is disabled.
Measurement IDs are not preempted and measurement configurations are
sent to UEs in sequence based on the triggering time.
4.1.1.5 Measurement Reporting

A UE performs measurements based on the measurement configuration received
from the gNodeB, and filters the measurement results based on filtering
coefficients. When determining that the entering conditions for the corresponding

(2021-12-30)
5G RAN
event are met, the UE periodically sends measurement reports to the gNodeB. In
this version, UEs send reports at fixed intervals of 240 ms in SSB SINR-based inter-
frequency handover and 320 ms in other handover functions, as indicated by the
reportInterval IE (MeasConfig > ReportConfigToAddModList) in the
RRCReconfiguration message.
4.1.1.6 Target Cell or Frequency Decision

The gNodeB selects target cells or frequencies and checks whether a new suitable
serving cell is available. If it is, the gNodeB continues to execute the handover.
Otherwise, the gNodeB waits for the next measurement report.
The process includes:
● Measurement report processing (needed only in measurement-based mode)

● Determination of a handover policy
● Generation of a target cell or frequency list
Measurement Report Processing

The gNodeB processes measurement reports in a first-come-first-handled manner,
meaning that the cells included in the first measurement report to arrive are
evaluated first. Based on the results, the gNodeB generates a candidate cell list or
a candidate frequency list.
Determination of a Handover Policy

The gNodeB selects a handover policy for a UE based on information about
candidate cells or frequencies, the UE's current service type, and UE capabilities.
Handover policies include:
● Handover: When referred to as a handover policy, it means that the gNodeB,

while retaining the RRC connections of a UE, transfers the UE from the source
cell to the target cell to ensure service continuity.
● Redirection: The gNodeB releases the RRC connections of a UE and instructs
the UE to access a cell working on a certain frequency.
NOTE
● Unless otherwise stated, handover is used in this chapter as a generic term that covers
procedures related to mobility management in connected mode.
● When referred to as a handover policy, handover is a specific term in contrast to
redirection and describes a procedure in which the serving cell of a UE changes.
● To perform a medium-priority blocking for a cell, the RRC_CONNECTED UEs in the cell
must be migrated out. The gNodeB selects redirection for transferring UEs out of the
cell.
Generation of a Target Cell or Frequency List

A target cell or frequency list is generated based on the processing mode,
measurement report, and neighboring cell filtering rule. The process is as follows:
1. A candidate cell or frequency list is generated based on the following

processing modes (measurement-based mode and blind mode):

(2021-12-30)
5G RAN
– Measurement-based mode: The gNodeB generates a candidate cell list or

a candidate frequency list based on measurement reports. For details, see
Measurement Report Processing.
– Blind mode:
The gNodeB does not instruct UEs to measure the signal quality of
candidate cells. Instead, it performs filtering based on UE capabilities and
the frequencies associated with the specific operator, and then generates
a candidate cell list or a candidate frequency list based on the configured
priorities (RAT priority, neighboring cell priority, and frequency priority).
The frequencies associated with a specific operator are filtered as follows:
▪ If the NRCellOpPolicy.gNBFreqPriorityGroupId parameter is set to

a value in the range of 0 to 254, the gNodeB performs filtering as
follows:
○ If OPERATOR_NR_FREQ_CFG_SW of
NRCellOpPolicy.FreqConfigPolicySwitch is selected, the
gNodeB filters out frequencies outside the intersection of NR
frequencies determined by
gNBFreqPriorityGroup.SsbDescMethod and
gNBFreqPriorityGroup.SsbFreqPos and those determined by
NRCellFreqRelation.SsbFreqPos.
○ If OPERATOR_NR_FREQ_CFG_SW of
NRCellOpPolicy.FreqConfigPolicySwitch is deselected, the
gNodeB filters out frequencies that do not belong to NR
frequencies determined by NRCellFreqRelation.SsbDescMethod
and NRCellFreqRelation.SsbFreqPos.
▪ If the NRCellOpPolicy MO is not configured or the

NRCellOpPolicy.gNBFreqPriorityGroupId parameter is set to 255,
the gNodeB does not perform filtering based on the frequencies
associated with a specific operator.
2. A final target cell list is generated in accordance with the following
neighboring cell filtering rules:
– The gNodeB filters out neighboring cells for which the
NRCellRelation.NoHoFlag parameter is set to FORBID_HO.
– The gNodeB filters out neighboring cells that do not support the
networking option of the current serving cell. For example, if the
networking option of the serving cell is SA, the candidate neighboring
cells for which the networking option is NSA are filtered out. If the
networking option of the serving cell is SA, the candidate neighboring
cells for which the networking option is SA or SA_NSA are retained.
The serving cell's networking option is indicated by the NR Networking
Option value in the command output of LST GNBOPERATOR or LST
NRDUCELLOP. If NR Networking Option indicates a valid networking
option in the command output of both LST GNBOPERATOR and LST
NRDUCELLOP, the networking option indicated in the LST NRDUCELLOP
command takes precedence.
The networking option of a neighboring cell is specified by
NRExternalNCell.NrNetworkingOption (applicable in scenarios other
than multi-operator sharing) or

(2021-12-30)
5G RAN
NRExternalNCellPlmn.NrNetworkingOption (applicable in multi-

operator sharing scenarios). The networking options of neighboring cells
can be automatically managed through ANR when the NR_NR_ANR_SW
option of the NRCellAlgoSwitch.AnrSwitch parameter is selected. For
details about ANR, see ANR.
– If NRCellFreqRelation.FreqIntrfFlag is set to INTRF for a frequency, the
gNodeB filters the cells working on this frequency based on the following
rules:
▪ Coverage-based inter-frequency handover: The gNodeB filters

candidate cells based on the measured RSRQ. That is, the gNodeB
determines whether the RSRQ of a cell meets the following
condition. If it is met, the gNodeB filters out the cell. Otherwise, the
gNodeB does not filter out the cell.
Mn + Ofn + Ocn + Hys < Thresh2
In the above formula:
○ Mn is the measured RSRQ of the neighboring cell.
○ Ofn is the frequency-specific offset for RRC_CONNECTED UEs,
and is specified by the NRCellFreqRelation.ConnFreqOffset
parameter.
○ Ocn is the CIO, and is specified by the
NRCellRelation.CellIndividualOffset parameter. If the value is
not DB0, this parameter is included in measurement
configurations. If the value is DB0, this parameter is not included
in measurement configurations and 0 is used for calculation by
default.
○ Hys is the hysteresis for events related to inter-frequency
measurements, and is specified by the
NRCellInterFHoMeaGrp.InterFreqA4A5Hyst parameter.
○ Thresh2 is the RSRQ threshold for events related to coverage-
based inter-frequency measurements, and is specified by the
NRCellInterFHoMeaGrp.CovInterFreqA5RsrqThld2 parameter.
▪ For other unnecessary inter-frequency handover functions, the

gNodeB filters out all cells working on the frequency.
– When the MOBILITY_RESTRICTION_SW option of the
gNBMobilityCommParam.MobilityAlgoSwitch parameter is selected,
the gNodeB filters out the cells that handover restrictions apply to
according to the Mobility Restriction List IE in the INITIAL CONTEXT
SETUP REQUEST message sent from the AMF.
– The gNodeB filters out neighboring cells with PLMNs not included in the
list of those allowed for UE handovers. If the target cell supports multiple
PLMNs (including the current serving PLMN), the source gNodeB
preferentially selects the current serving PLMN as that used after the
handover.
Table 4-11 lists the PLMNs allowed for UE intra-RAT handovers in SA
networking given different settings of the
INTRA_RAT_HO_WITH_GNB_EPLMN_SW option (specifying whether to
enable EPLMN-based intra-RAT inter-PLMN handover) of the
gNodeBParam.EqvPlmnAlgoSwitch parameter.

(2021-12-30)
5G RAN
Table 4-11 PLMNs allowed for UE handovers
EPLMN-based Intra-RAT Inter- PLMN Allowed for UE Handovers

PLMN Handover Switch
Deselected Current serving PLMN
Selected ● Current serving PLMN

● EPLMNs obtained by the
gNodeB from the Mobility
Restriction List IE
● EPLMNs configured using the
gNBEqvPlmn MO
Note:
● When configuring the gNBEqvPlmn MO, ensure that there is a
roaming agreement between the PLMN corresponding to
gNBEqvPlmn.OperatorId and the EPLMN collectively determined by
gNBEqvPlmn.EquivalentMcc and gNBEqvPlmn.EquivalentMnc.
● The PLMNs that are graylisted or blacklisted using the PLMN ID
management function are excluded from those allowed for UE
handovers. For details about the PLMN ID management function,
see ANR.
– The gNodeB filters out the neighboring cells whose uplink and downlink
bandwidths are not supported by UEs. The conditions for this are as
follows:
▪ Intra-base-station handover: If the minimum bandwidth supported

by a UE is greater than the downlink bandwidth and uplink
bandwidth of an intra-base-station neighboring cell, the gNodeB
filters out the neighboring cell.
▪ Inter-base-station handover:
○ If an Xn interface is set up between the gNodeB and a
neighboring base station, the gNodeB can obtain the uplink and
downlink bandwidths of inter-base-station neighboring cells. In
this scenario, if the minimum bandwidth supported by a UE is
greater than the downlink bandwidth and uplink bandwidth of
an inter-base station neighboring cell, the gNodeB filters out the
neighboring cell.
○ If an Xn interface is not set up between the gNodeB and a
neighboring base station, the gNodeB cannot obtain the uplink
and downlink bandwidths of inter-base-station neighboring cells.
In this scenario, the gNodeB does not filter out such neighboring
cells based on UE bandwidth capabilities.
The minimum bandwidths supported by a UE can be obtained from the
channelBWs-UL, channelBWs-DL, channelBWs-UL-v1590, and
channelBWs-DL-v1590 IEs in the UECapabilityInformation IE signaled over
the Uu interface. For details, see section 4.2 "UE Capability Parameters"
in 3GPP TS 38.306 V16.5.0.

(2021-12-30)
5G RAN
– SSB SINR-based inter-frequency handover: If this function (controlled by

the SSB_SINR_BASED_HO option of
NRCellAlgoSwitch.InterFreqHoSwitch) is enabled, and measurement-
based inter-frequency handover (controlled by the
COVERAGE_BASED_HO option of
NRCellAlgoSwitch.InterFreqHoSwitch) or measurement-based inter-
frequency redirection (controlled by the REDIRECTION option of
NRCellAlgoSwitch.InterFreqHoSwitch) is also enabled, the gNodeB
further filters out the following cells to generate a target cell or
frequency list.
▪ If only RSRP is used as the triggering quantity for event A2 related to

coverage-based inter-frequency measurements, the gNodeB filters
out the cells whose RSRP is less than the result of
"NRCellInterFHoMeaGrp.CovInterFreqA2RsrpThld –
NRCellInterFHoMeaGrp.InterFreqA1A2Hyst".
▪ If both RSRP and RSRQ are used as the triggering quantities for
event A2 related to coverage-based inter-frequency measurements,
the gNodeB filters out the cells whose RSRP is less than the result of
NRCellInterFHoMeaGrp.InterFreqA1A2Hyst" and the cells whose
RSRQ is less than the result of
"NRCellInterFHoMeaGrp.CovInterFreqA2RsrqThld –
The RSRP_AND_RSRQ_SW option of the
NRCellMobilityConfig.A1A2MeasTrigQty parameter determines the
triggering quantity for event A2.
4.1.1.7 Handover Execution

After determining the target cell or frequency list, the gNodeB executes a
handover based on the selected handover policy, which can be handover or
redirection.
Handover
Figure 4-4 shows the procedure when the handover policy is handover.

(2021-12-30)
5G RAN
Figure 4-4 Handover procedure
1. Inter-AMF-region determination: The source gNodeB selects the cell with the
best quality from the target cell or frequency list and then starts inter-AMF-
region determination.
If the gNodeB serving the source cell and the gNodeB serving the target cell
belong to different AMF regions, an NG-based handover request is sent. In
this case, the procedure goes to 4.
If the gNodeB serving the source cell and the gNodeB serving the target cell
belong to the same AMF region, the procedure goes to 2.
2. Target gNodeB determination: The source gNodeB determines whether the
target cell is served by a different base station.

(2021-12-30)
5G RAN
– If the source cell and the target cell are served by the same gNodeB,
handover execution is performed. In this case, the procedure goes to 5.
– If the target cell is served by a different gNodeB from the source cell, the
procedure goes to 3.
3. Handover link selection: The source gNodeB initiates an Xn- or NG-based
handover request.
– If an Xn link exists between the gNodeB serving the source cell and the
gNodeB serving the target cell, the source gNodeB initiates an Xn-based
handover request. In this case, the procedure goes to 4.
– If no Xn link is present between the gNodeB serving the source cell and
the gNodeB serving the target cell, the source gNodeB initiates an NG-
based handover request. In this case, the procedure goes to 4.
4. Handover preparation: After receiving the handover request, the target
gNodeB prepares for the handover and responds with the preparation result.
– If the admission to the target gNodeB succeeds, the target gNodeB sends
a Handover Request Acknowledge or Handover Command message to
the source gNodeB. As such, the source gNodeB considers the handover
preparation to have succeeded and initiates handover execution. In this
case, the procedure goes to 5.
– If the admission to the target gNodeB fails, the target gNodeB sends a
Handover Preparation Failure message to the source gNodeB.
▪ If the failure cause value is "Invalid AMF Set ID" or "Unknown

GUAMI ID", the source gNodeB resends a handover request over the
NG link.
▪ If another failure cause value is received, the source gNodeB

considers the handover preparation to have failed and applies a
penalty. For details, see Handover Preparation Failure Penalty.
NOTE
For details about AMF regions, see NG-flex.

Upon receiving a handover request message from the source gNodeB, the target
gNodeB automatically determines whether it complies with a protocol version earlier
than that of the source gNodeB. If it does, it includes the fullConfig IE in the handover
command sent to the source gNodeB, which then sends the handover command to
the UE.
If the source and target gNodeBs are provided by different vendors, or there are
abnormal UEs on live networks, the INTER_GNB_HO_FULL_CONFIG_SW option of the
NRCellAlgoSwitch.HoCompatibilitySwitch parameter must be selected. In this case,
when the target gNodeB receives a handover request message from the source
gNodeB, the target gNodeB includes the fullConfig IE in the handover command sent
to the source gNodeB, which then sends the handover command to the UE.
5. Handover execution: The source gNodeB sends the handover command to the
UE, instructing it to execute the handover.
– If the handover is successfully executed, the source gNodeB releases
resources after receiving the Release Resource message from the target
gNodeB.
In the case of an Xn-based handover, the target gNodeB forwards the
uplink data of the UE to the core network after the handover is
completed. This process interrupts uplink data transmission. To reduce the

(2021-12-30)
5G RAN
interruption duration, the function of Xn-based handover interruption

duration optimization has been introduced. This function is controlled by
the XN_HO_INTERRUPT_DUR_OPT_SW option of the
gNBMobilityCommParam.ProtocolCompatibilitySw parameter.
▪ If this option is deselected, the target gNodeB starts to forward

uplink data to the core network after receiving a PATH SWITCH
REQUEST ACKNOWLEDGE message from the AMF.
▪ If this option is selected, the target gNodeB starts to forward uplink

data to the core network after receiving an
RRCReconfigurationComplete message from the UE. This shortens
the duration of uplink data transmission interruption during an Xn-
based handover.
– If the handover execution fails, the handover execution failure penalty
begins. For details, see Handover Execution Failure Penalty.
Redirection
If the handover policy is redirection, the gNodeB selects the cell of the highest-
priority frequency from the target cell or frequency list, and sends it to the UE
through an RRC Release message. The UE then performs redirection.
Conflict Handling Between Handover and Voice Fallback

Assume that the gNodeB is preparing for an intra-RAT outgoing handover. During
the preparation, if the core network initiates a procedure for setting up a bearer
with 5QI 1 for voice services, and the gNodeB decides to perform voice fallback,
the handover procedure conflicts with the voice fallback procedure. Alternatively, if
the core network initiates an emergency call fallback procedure during the
preparation, the handover procedure conflicts with the emergency call fallback
procedure. The VOICE_FB_FIRST_SWITCH option of the
gNBMobilityCommParam.HoPduSessConflHandlingSw parameter determines
how to handle the preceding conflict between handover and PDU session.
● If the VOICE_FB_FIRST_SWITCH option of this parameter is selected, the

gNodeB preferentially handles voice fallback or emergency call fallback and
sends a handover cancellation request.
● If the VOICE_FB_FIRST_SWITCH option of this parameter is deselected, the
gNodeB preferentially handles the handover procedure and responds with a
message, notifying the core network that the voice fallback or emergency call
fallback fails as the gNodeB is performing an intra-RAT handover. After the
handover is completed, the core network re-initiates a voice fallback or
emergency call fallback procedure, as specified in 3GPP TS 23.501. If the core
network does not support re-initiation of the said procedure, the voice
fallback or emergency call fallback procedure will fail.
Conflict Handling Between Handover and QoS Procedures

Assume that the gNodeB is preparing for an intra-RAT outgoing handover. During
the preparation, if the gNodeB receives PDU session setup or modification
signaling indicating the addition or modification of a QoS flow, the handover
procedure conflicts with the QoS procedure. The QOS_FLOW_FIRST_SW option of

(2021-12-30)
5G RAN
the NRCellQciBearer.HoQosFlowConflProcStrat parameter determines how to

handle the preceding conflict between handover and PDU session.
● When the QOS_FLOW_FIRST_SW option of this parameter is selected, the

gNodeB preferentially handles the QoS procedure and initiates a handover
cancellation request. It is recommended that this option be selected when the
core network does not support PDU session setup or modification in the
target cell during a handover procedure.
● When the QOS_FLOW_FIRST_SW option of this parameter is deselected, the
gNodeB preferentially handles the handover procedure and notifies the core
network that the gNodeB is performing an intra-RAT handover. After the
handover is completed, the core network re-initiates a QoS procedure, as
specified in 3GPP TS 23.501. If the core network does not support the re-
initiation of the said procedure, the QoS procedure will fail.
NOTE
This function applies to all 5QI-specific QoS flow procedures. It can be enabled for a specific
5QI by binding the 5QI to the NRCellQciBearer.Qci parameter. Note that among services
carried on bearers with 5QI 1 (with the NRCellQciBearer.Qci parameter set to 1), this
function is only applicable to bearers carrying VoNR services. For details about the conflict
handling between 5QI-1-based voice fallback and handover, see Conflict Handling
Between Handover and Voice Fallback.
4.1.1.8 Handover Failure Penalty

The handover failure penalty mechanism aims to reduce the number of ineffective
retries that follow a handover failure. Depending on the execution phase in which
the handover failure occurs, handover failure penalties are classified into handover
preparation failure penalties and handover execution failure penalties.
Handover Preparation Failure Penalty

Depending on the causes, handover preparation failures are categorized as
resource-caused handover preparation failures and non-resource-caused handover
preparation failures.
● For resource-caused handover preparation failures, a penalty timer is

configured to impose penalties on the target cell. A retry cannot be initiated
to the cell for the UE until the penalty timer expires.
– For coverage-based intra-frequency and inter-frequency handovers, the
penalty timer is specified by the
gNBMobilityCommParam.NecHoPrepFailPunishTimer parameter.
– For other handover functions, the penalty timer is specified by the
gNBMobilityCommParam.OptHoPrepFailPunishTimer parameter.
NOTE
For handover preparation failures with the cause value "Transport resource
unavailable", the following applies within the penalty time:
● If the UE involved is an NSA DC UE, the NSA DC UEs that are connected to
the same eNodeB and served by the same PLMN as this NSA DC UE cannot
initiate handover attempts to the target cell.
● If the UE involved is an SA UE, the SA UEs that are served by the same PLMN
as this SA UE cannot initiate handover attempts to the target cell.

(2021-12-30)
5G RAN
● For non-resource-caused handover preparation failures, the number of

penalty times is configured to impose penalties on the target cell. A retry
cannot be initiated to the cell for the UE until the number of penalty times is
reached. If the handover preparation continues to fail after the retry, the UE
can no longer initiate a handover to the cell.
The number of penalty times is specified by the
gNBMobilityCommParam.NonResHoPrepFailPunishTimes parameter.
NOTE
● After cell A enters the penalty state, the number of penalty times is incremented by one
each time the measurement result indicates that cell A meets the handover condition.
● Retry means that a request for a handover to cell A is sent again when this cell meets
the handover condition after the specified penalties imposed on it have ended.
● Resource-caused handover preparation failures are only those whose failure causes are
as follows:
● No radio resources available in target cell
● Transport resource unavailable
● Not enough User Plane Processing Resources
● Radio resources not available
● Control Processing Overload
Handover Execution Failure Penalty

For a handover execution failure, the UE has its RRC connection reestablished in
the source cell. When a handover attempt is initiated to cell A again and the
handover preparation attempt succeeds, the source gNodeB initiates a handover
retry to the cell. If the retries to the target cell continue to fail after 10 attempts,
the source gNodeB no longer sends requests for handovers to cell A for the UE to
prevent service drops caused by exceptions.
4.1.2 Network Analysis
4.1.2.1 Benefits
This function selects the cell with the best quality for UEs in RRC_CONNECTED
mode to transmit data, ensuring continuous coverage and providing users with
seamless service experience.
Non-overlapping between gap and NR resources reduces the loss in uplink and
downlink UE throughput caused by gap-assisted measurement and the rate of
service drops caused by conflicts between PUCCH SR and gap-assisted
measurement but prolongs the measurement duration. Due to cell-level
measurement, the values of the following indicators may also change after the
function of non-overlapping between gap and NR resources is enabled.
Specifically, the values of N.ThpTime.UL.Cell (duration of uplink data
transmission at the MAC layer in a cell) and N.ThpTime.DL.Cell (duration of
downlink data transmission at the MAC layer in a cell) may increase, and those of
Cell Uplink Average Throughput (DU) (average uplink cell throughput) and Cell
Downlink Average Throughput (DU) (average downlink cell throughput) may
decrease.
Enabling optimized configuration for deriveSSB-IndexFromCell results in the
following impacts: In TDD, the efficiency and accuracy of detecting neighboring

(2021-12-30)
5G RAN
cells' SSB indexes is improved as cells working on TDD frequencies are time-
synchronized. In FDD, network performance is not affected.
Enabling the SMTC offset compatibility function resolves UE compatibility issues

when 1588V2 loose time synchronization takes effect. However, this function may
decrease the RRC connection setup success rate and handover success rate.
Measurement ID preemption results in the following impacts: If measurement

resources are insufficient, the rate of service drops due to such insufficiency
decreases and voice service experience improves. If measurement resources are
sufficient, network performance is not affected.
The function of Xn-based handover interruption duration optimization shortens

the duration of uplink data transmission interruption during Xn-based handovers,
but can also cause service drops due to incompatibility with the core network.
4.1.2.2 Impacts
Network Impacts
The values of the following counters (related to canceled handovers) will increase
if a handover procedure conflicts with a voice fallback procedure or an emergency
call voice fallback procedure and the VOICE_FB_FIRST_SWITCH option of the
gNBMobilityCommParam.HoPduSessConflHandlingSw parameter is selected. It
is recommended that the handover cancellation times indicated by such counters
be deducted during the calculation of the outgoing handover success rate.
● N.HO.IntraFreq.Prep.FailOut.HOCancel
● N.HO.IntraFreq.FailOut.HOCancel
● N.HO.InterFreq.Prep.FailOut.HOCancel
● N.HO.InterFreq.FailOut.HOCancel
Function Impacts
RAT Function Function Reference Description
Name Switch
Low- Low HIGH_RELIABI URLLC Inter-frequency

freque latency LITY_BASIC_S measurements require the
ncy and high W option of use of measurement gaps,
TDD reliability the causing high reliability
FDD NRDUCellAlg performance to deteriorate
oSwitch.High during UE inter-frequency
ReliabilitySwi measurements. UEs perform
tch parameter inter-frequency
measurements in scenarios
such as coverage-based
inter-frequency handovers,
frequency-priority-based
inter-frequency handovers,
and service-based inter-
frequency handovers.

(2021-12-30)
5G RAN

Name Switch
FDD Experience MULTI_FREQ_ Multi- When both the EPLMN-

Low- -based SMART_SEL_S Frequency based intra-RAT inter-PLMN
freque smart W option of Convergen handover function and the
ncy carrier the ce experience-based smart
TDD selection NRCellAlgoS carrier selection function
witch.MultiFr (controlled by the
eqAlgoSwitch MULTI_FREQ_SMART_SEL_
parameter SW option of the
NRCellAlgoSwitch.MultiFr
eqAlgoSwitch parameter)
are enabled, the PLMN list
to which UEs can be
handed over includes only
the current serving PLMN.
High- None None None None

freque
ncy
TDD
4.1.3 Requirements
4.1.3.1 Licenses
There are no license requirements.
4.1.3.2 Software
Prerequisite Functions
None
Mutually Exclusive Functions

None
4.1.3.3 Hardware
Base Station Models

3900 and 5900 series base stations. 3900 series base stations must be configured
with the BBU3910.
DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be

configured with the BBU3910.

(2021-12-30)
5G RAN
Boards
All NR-capable main control boards and baseband processing units support this
function. For details, see the BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.
RF Modules
All NR-capable RF modules support this function. For details, see the technical
specifications of RF modules in 3900 & 5900 Series Base Station Product
Documentation.
4.1.3.4 Others
● If there are multiple AMFs, the core network must support inter-AMF
handovers.
● If an AMF region is planned on the core network, the gNodeB must support
at least one network slice in the AMF region and connect to all AMFs in the
AMF set corresponding to the network slice.
● For an intra-base-station handover, if the source cell and target cell are in the
same PLMN, they cannot belong to different AMFs in the same AMF region.
Otherwise, the UE registration update fails after the intra-base-station
handover is complete, resulting in a service drop. As such, during network
planning, cells in the same PLMN under a base station need to be mapped to
the same AMF through the TACs.
● In NR FDD, the clock synchronization mode of the gNodeB must be set to
time synchronization. For details about time synchronization, see
Synchronization.
● During the configuration of external cells (through the NRExternalNCell
MO):
– If the NRExternalNCell.NrNetworkingOption parameter is set to NSA,
no tracking area code (TAC) needs to be planned. In this case, you are
advised to set the TAC to an invalid value (4294967295).
– If the NRExternalNCell.NrNetworkingOption parameter is set to SA or
SA_NSA, a TAC equal to the actual TAC of the external cell must be
configured. Otherwise, handovers may fail.
● Xn-based handovers have the following requirements for the target gNodeB:
The target gNodeB must comply with 3GPP TS 38.423 V15.5.0 or later.
Otherwise, Xn-based handovers will fail as the source gNodeB complies with
3GPP TS 38.423 V15.5.0 or later. Consequently, the function of protocol
compatibility processing for Service Area Information exchanged between
base stations has been introduced. This function is controlled by the
XN_SERVICE_AREA_INFO_PROC_SW option of the
gNodeBParam.CompatibilityAlgoSwitch parameter. It is recommended that
this option be deselected when the source and target gNodeBs comply with
different protocol versions.
– If this option is selected, Huawei base stations signal the Service Area
Information IE and process this IE in compliance with 3GPP TS 38.423
V15.5.0 or later.
– If this option is deselected, Huawei base stations do not signal the Service
Area Information IE and they process this IE after receiving it in

(2021-12-30)
5G RAN
compliance with 3GPP TS 38.423 V15.4.0 or earlier. With this setting, Xn-
based handovers can succeed, but UEs may be handed over to the
forbidden cells indicated by the Mobility Restriction List IE in the INITIAL
CONTEXT SETUP REQUEST message sent from the AMF.
● Compared with 3GPP TS 38.423 V16.6.0, 3GPP TS 38.423 V16.7.0 introduced a
non-compatibility change in the definition of the UE Security Capabilities IE.
For details, see section 9.2.3.49 "UE Security Capabilities" in 3GPP TS 38.423
V16.7.0. During an Xn-based handover, the target gNodeB processes the UE
Security Capabilities IE in the Handover Request message sent by the source
gNodeB to select a ciphering algorithm. If the two base stations comply with
different protocols during the processing, a protocol compatibility issue
occurs. To prevent handover failures due to protocol inconsistency between
the source and target gNodeBs, Huawei gNodeBs have optimized the
compatibility processing in accordance with 3GPP TS 38.423 V16.7.0. This
optimization is controlled by the XN_UE_SECURITY_CAP_PROC_SW option of
the gNodeBParam.CompatibilityAlgoSwitch parameter. It is recommended
that this option be selected when a Huawei gNodeB is connected to a non-
Huawei gNodeB over the Xn interface and the non-Huawei gNodeB signals
the Handover Request message containing the UE Security Capabilities IE in
compliance with 3GPP TS 38.423 V16.7.0.
– When this option is selected, Huawei gNodeBs signal the UE Security
Capabilities IE and process this IE in compliance with 3GPP TS 38.423
V16.7.0.
– When this option is deselected, Huawei gNodeBs signal the UE Security
V16.6.0.
4.1.4 Operation and Maintenance
4.1.4.1 Data Configuration
4.1.4.1.1 Data Preparation

Parameter settings vary among handover functions. Before setting the parameters
for a handover function, refer to this section to complete the common
configurations of all handover functions.
Mobility management in connected mode depends on neighboring cell
configurations. Before using this function, ensure that the parameters related to
neighboring cells have been configured. Table 4-12 lists the parameters related to
neighboring cells involved in mobility management in connected mode. Table
4-13 lists the parameters related to cell-specific frequency relationships involved in
inter-frequency handovers. If ANR is enabled, neighboring cells do not require
manual configuration. For details, see ANR.

(2021-12-30)
5G RAN
Table 4-12 Parameters used to configure neighboring cells

Parameter Parameter ID Setting Notes
Name
Mobile NRExternalNCell.Mcc Set this parameter

Country Code based on the network
plan.
Mobile NRExternalNCell.Mnc Set this parameter

Network Code based on the network
plan.
gNodeB ID NRExternalNCell.gNBId Set this parameter

based on the network
plan.
Cell ID NRExternalNCell.CellId Set this parameter

plan.
Physical Cell NRExternalNCell.PhysicalCellId Set this parameter

ID based on the network
plan.
Cell Name NRExternalNCell.CellName Set this parameter

plan.
Tracking Area NRExternalNCell.Tac Set this parameter

Code based on the network
plan.
SSB NRExternalNCell.SsbDescMethod Set this parameter to

Frequency its recommended
Position value.
Describe
Method
SSB NRExternalNCell.SsbFreqPos Set this parameter

Frequency based on the network
Position plan.
Frequency NRExternalNCell.FrequencyBand Set this parameter

Band based on the network
plan.
NR NRExternalNCell.NrNetworkingOpti Set this parameter

Networking on based on the network
Option plan.
NR Cell ID NRCellRelation.NrCellId Set this parameter

plan.

(2021-12-30)
5G RAN

Name
Mobile NRCellRelation.Mnc Set this parameter

Network Code based on the network
plan.
Mobile NRCellRelation.Mcc Set this parameter

Country Code based on the network
plan.
gNodeB ID NRCellRelation.gNBId Set this parameter

plan.
Cell ID NRCellRelation.CellId Set this parameter

plan.
Cell Individual NRCellRelation.CellIndividualOffset Set this parameter to

Offset its recommended
value.
NOTE
● Maximum number of external NR cells that can be configured for a gNodeB: Maximum
number of cells supported by the gNodeB x 32
● Maximum number of neighboring NR cells that can be configured for an NR cell: 384
● Maximum number of neighboring NR cells that can be configured for a gNodeB:
Maximum number of cells supported by the gNodeB x 256
The NRExternalNCell MO defines external NR cells, and the NRCellRelation MO defines
neighboring NR cells. For details about the maximum number of cells supported by a
gNodeB, see "Capacity Specifications" in the corresponding BBU technical specifications in
3900 & 5900 Series Base Station Product Documentation.
Table 4-13 Parameters used to configure frequency relationships for NR cells

Name
NR Cell ID NRCellFreqRelation.NrCellId Set this parameter

plan.
SSB NRCellFreqRelation.SsbFreqPos Set this parameter

Position plan.
SSB NRCellFreqRelation.SsbDescMethod Set this parameter to

Position value.
Describe
Method

(2021-12-30)
5G RAN

Name
Frequency NRCellFreqRelation.FrequencyBand Set this parameter

plan.
Subcarrier NRCellFreqRelation.SubcarrierSpacin Set this parameter

Spacing g based on the network
plan.
Table 4-14 Common parameters used for optimization

Parameter Parameter ID Option Setting Notes
Name
Necessary gNBMobilityC None Set this parameter to its

HO ommParam.N recommended value.
Prepare ecHoPrepFailP
Fail Punish unishTimer
Timer
Optimized gNBMobilityC None Set this parameter to its

HO ommParam.O recommended value.
Prepare ptHoPrepFailP
Fail Punish unishTimer
Timer
Non-Res gNBMobilityC None Set this parameter to its

HO ommParam.N recommended value.
Prepare onResHoPrepF
Fail Punish ailPunishTime
Times s
SMTC NRDUCell.Smt None Set this parameter to its
Period cPeriod recommended value.
SMTC NRDUCell.Smt None Set this parameter to its

Duration cDuration recommended value.
SMTC NRCellFreqRel None Set this parameter to its

Period ation.SmtcPeri recommended value.
od
SMTC NRCellFreqRel None Set this parameter to its
Duration ation.SmtcDur recommended value.
ation
Measurem gNBMobilityC GAP_AVOID_N It is recommended that this
ent ommParam.M R_RES_SW option be selected in the case
Algorithm easAlgoSwitch of inter-frequency
Switch measurement in low-frequency
SA networking.

(2021-12-30)
5G RAN

Name
Measurem gNBMobilityC MEAS_ID_PREE It is recommended that this

ent ommParam.M MPTION_SW option be selected.
Algorithm easAlgoSwitch
Switch
Algorithm NRDUCellAlgo SMTC_OFFSET_ It is recommended that this

Compatibil Switch.AlgoCo COMPAT_SW option be selected.
ity Switch mpatibilitySwi
Extension tchExt
Handover NRCellAlgoSw PROTOCOL_IE_ It is recommended that this
Compatibil itch.HoCompa OPT_SW option be selected.
ity Switch tibilitySwitch
Handover NRCellAlgoSw INTER_GNB_H It is recommended that this
Compatibil itch.HoCompa O_FULL_CONFI option be selected if full
ity Switch tibilitySwitch G_SW configurations are required in
an RRCReconfiguration
message during an inter-base-
station handover.
Compatibil gNodeBParam XN_UE_SECURI It is recommended that this

ity .Compatibility TY_CAP_PROC_ option be selected when a
Algorithm AlgoSwitch SW Huawei gNodeB is connected
Switch to a non-Huawei gNodeB over
the Xn interface and the non-
Huawei gNodeB signals the
Handover Request message
containing the UE Security
Capabilities IE in compliance
with 3GPP TS 38.423 V16.7.0.
In other scenarios, it is
recommended that this option
be deselected.
Measurem NRCellAlgoSw SSB_MEAS_PO Configuration is required in

ent Policy itch.MeasPolic S_POLICY_SW high-frequency scenarios. It is
Switch ySwitch recommended that this option
be selected.
Protocol gNBMobilityC XN_HO_INTER Set this parameter to its

Compatibil ommParam.Pr RUPT_DUR_OP recommended value.
ity Switch otocolCompat T_SW
ibilitySw

(2021-12-30)
5G RAN

Name
Equivalent gNodeBParam INTRA_RAT_H Set this parameter based on

PLMN .EqvPlmnAlgo O_WITH_GNB_ the network plan.
Algorithm Switch EPLMN_SW It is recommended that the
Switch INTRA_RAT_HO_WITH_GNB_E
PLMN_SW option be selected
if EPLMN-based intra-RAT
inter-PLMN handover in SA
networking needs to be
supported. For details about
the PLMNs allowed for UE
handovers given different
switch settings, see Table 4-11.
SSB NRCellMobilit None Set this parameter to its

Consolidati yConfig.SsbCo recommended value.
on nsolidationThl
Threshold d
SSB NRCellMobilit None Set this parameter to its
Number To yConfig.SsbNu recommended value.
Average mToAverage
Beam NRCellMobilit None Set this parameter to its
RSRP Filter yConfig.Beam recommended value.
Coefficient RsrpFilterCoef
f
Cell RSRP NRCellMobilit None Set this parameter to its
Filter yConfig.CellRs recommended value.
Coefficient rpFilterCoeff
Operator gNBEqvPlmn. None Set this parameter based on
IDa OperatorId the network plan.
Equivalent gNBEqvPlmn.E None Set this parameter based on

Mobile quivalentMcc the network plan.
Country
Code
Equivalent gNBEqvPlmn.E None Set this parameter based on

Mobile quivalentMnc the network plan.
Network
Code
HO and gNBMobilityC VOICE_FB_FIRS It is recommended that this

PDU ommParam.H T_SWITCH option be selected if voice
Session oPduSessConfl fallback needs to be
Conflict HandlingSw preferentially handled when a
Handling voice fallback request is
Sw received during outgoing
handover preparation.

(2021-12-30)
5G RAN

Name
HO and NRCellQciBear QOS_FLOW_FI It is recommended that this

QoS Flow er.HoQosFlow RST_SW option be selected if the QoS
Conflict ConflProcStrat flow procedure needs to be
Proc preferentially handled when
Strategy PDU session setup or
modification signaling
indicating the addition or
modification of a QoS flow is
received during outgoing
handover preparation.
Mobility gNBMobilityC MOBILITY_RES It is recommended that this

Algorithm ommParam.M TRICTION_SW option be selected if the
Switch obilityAlgoSwi INITIAL CONTEXT SETUP
tch REQUEST message sent from
the core network includes the
Mobility Restriction List IE.
Frequency NRCellFreqRel None Set this parameter based on
Interferenc ation.FreqIntrf the network plan.
e Flag Flag

(2021-12-30)
5G RAN

Name
Frequency NRCellOpPolic OPERATOR_NR The policy on frequency

Configurati y.FreqConfigP _FREQ_CFG_S delivery for inter-frequency
on Policy olicySwitch W measurement is configured as
Switch follows: Select
OPERATOR_NR_FREQ_CFG_S
W if NR frequencies in the
intersection of NR frequencies
configured in the
gNBFreqPriorityGroup MO
and those configured in the
NRCellFreqRelation MO are to
be sent. Deselect
W if NR frequencies configured
in the NRCellFreqRelation MO
are to be sent.
Frequency filtering in blind
mode is configured as follows:
Select
W if frequencies outside the
intersection of NR frequencies
configured in the
gNBFreqPriorityGroup MO
and those configured in the
NRCellFreqRelation MO need
to be filtered out. Deselect
W if frequencies that do not
belong to NR frequencies
configured in the
NRCellFreqRelation MO need
to be filtered out.
Set this parameter to its
recommended value.
a: When configuring the gNBEqvPlmn MO, ensure that there is a roaming

agreement between the PLMN corresponding to gNBEqvPlmn.OperatorId and
the EPLMN collectively determined by gNBEqvPlmn.EquivalentMcc and
gNBEqvPlmn.EquivalentMnc.
4.1.4.1.2 Using MML Commands
Activation Command Examples

TDD configuration examples
//Configuring a frequency relationship with a neighboring frequency
//Adding a frequency relationship for an NR cell

(2021-12-30)
5G RAN
ADD NRCELLFREQRELATION: NrCellId=0, SsbFreqPos=8000, SsbDescMethod=SSB_DESC_TYPE_GSCN,

FrequencyBand=N77, SubcarrierSpacing=30KHZ, ConnFreqPriority=1;
//Configuring a neighbor relationship if it is not configured
//Adding an external cell
ADD NREXTERNALNCELL: Mcc="302", Mnc="220", gNBId=1, CellId=0, CellName="A", PhysicalCellId=0,
Tac=0, SsbDescMethod=SSB_DESC_TYPE_GSCN, SsbFreqPos=6300, FrequencyBand=N41,
NrNetworkingOption=SA;
//(Optional, required only when the external cell is shared) Adding the secondary-operator information to
the NR external-cell PLMN list
ADD NREXTERNALNCELLPLMN: Mcc="302", Mnc="220", gNBId=1, CellId=0, SharedMcc="302",
SharedMnc="200", Tac=0, NrNetworkingOption=SA;
//Adding a relationship with the NR cell
ADD NRCELLRELATION: NrCellId=0, Mcc="302", Mnc="220", gNBId=1, CellId=0, CellIndividualOffset=DB0;
FDD configuration examples

//Configuring a frequency relationship with a neighboring frequency
FrequencyBand=N3, SubcarrierSpacing=15KHZ, ConnFreqPriority=1;
Optimization Command Examples

//Modifying common gNodeB mobility parameters
MOD GNBMOBILITYCOMMPARAM: NecHoPrepFailPunishTimer=0, OptHoPrepFailPunishTimer=0,
NonResHoPrepFailPunishTimes=10;
//Configuring the policy on frequency delivery for inter-frequency measurement with NR frequencies in the
intersection of NR frequencies configured in the gNBFreqPriorityGroup MO and those configured in the
NRCellFreqRelation MO to be sent as well as frequency filtering in blind mode with frequencies outside the
NRCellFreqRelation MO to be filtered out
MOD NRCELLOPPOLICY: NrCellId=0, OperatorId=0,
FreqConfigPolicySwitch=OPERATOR_NR_FREQ_CFG_SW-1;
//Modifying SMTC configuration
MOD NRDUCELL: NrDuCellId=0, DuplexMode=CELL_TDD, SmtcPeriod=MS20, SmtcDuration=MS2;
MOD NRCELLFREQRELATION: NrCellId=0, SsbFreqPos=7853, FrequencyBand=N78, SmtcPeriod=MS20,
SmtcDuration=MS3;
//Modifying the configuration for SSB beam measurement result selection and combination
MOD NRCELLMOBILITYCONFIG: NrCellId=0, SsbConsolidationThld=70, SsbNumToAverage=8;
//Modifying the measurement filtering configuration
MOD NRCELLMOBILITYCONFIG: NrCellId=0, BeamRsrpFilterCoeff=FC4, CellRsrpFilterCoeff=FC4;
//Enabling the function of non-overlapping between gap and NR resources in low-frequency SA networking
MOD GNBMOBILITYCOMMPARAM: MeasAlgoSwitch=GAP_AVOID_NR_RES_SW-1;
//Turning on the measurement ID preemption switch
MOD GNBMOBILITYCOMMPARAM: MeasAlgoSwitch=MEAS_ID_PREEMPTION_SW-1;
//Turning on the protocol IE optimization switch
MOD NRCELLALGOSWITCH: NrCellId=0, HoCompatibilitySwitch=PROTOCOL_IE_OPT_SW-1;
//Turning on the Xn UE security capability processing switch
MOD GNODEBPARAM: CompatibilityAlgoSwitch=XN_UE_SECURITY_CAP_PROC_SW-1;
//Turning on the SSB measurement position policy switch (only for high frequency bands)
MOD NRCELLALGOSWITCH: NrCellId=0, MeasPolicySwitch=SSB_MEAS_POS_POLICY_SW-1;
//Enabling the sending of full configurations during inter-base-station handovers
MOD NRCELLALGOSWITCH: NrCellId=0, HoCompatibilitySwitch=INTER_GNB_HO_FULL_CONFIG_SW-1;
//Enabling preferential handling of voice fallback
MOD GNBMOBILITYCOMMPARAM: HoPduSessConflHandlingSw=VOICE_FB_FIRST_SWITCH-1;
//Enabling preferential handling of QoS procedures (QCI 1 used as an example)

(2021-12-30)
5G RAN
MOD NRCELLQCIBEARER: NrCellId=0, Qci=1, HoQosFlowConflProcStrat=QOS_FLOW_FIRST_SW-1;

//Turning on the mobility restriction switch
MOD GNBMOBILITYCOMMPARAM: MobilityAlgoSwitch=MOBILITY_RESTRICTION_SW-1;
//Turning on the EPLMN-based intra-RAT inter-PLMN handover switch
MOD GNODEBPARAM: EqvPlmnAlgoSwitch=INTRA_RAT_HO_WITH_GNB_EPLMN_SW-1;
//Adding an EPLMN for an operator of the gNodeB (In this example, OperatorId is set to 0, EquivalentMcc
is set to 520, and EquivalentMnc is set to 15. The configuration depends on the actual requirements.)
ADD GNBEQVPLMN: OperatorId=0, EquivalentMcc="520", EquivalentMnc="15";
//Setting the frequency interference flag if RSRP needs to be used as the triggering quantity with RSRQ-
based filtering
MOD NRCELLFREQRELATION: NrCellId=0, SsbFreqPos=7853, FrequencyBand=N78, FreqIntrfFlag=INTRF;
//Selecting XN_HO_INTERRUPT_DUR_OPT_SW
MOD GNBMOBILITYCOMMPARAM: ProtocolCompatibilitySw=XN_HO_INTERRUPT_DUR_OPT_SW-1;
//Turning on the SMTC offset compatibility switch
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, AlgoCompatibilitySwitchExt=SMTC_OFFSET_COMPAT_SW-1;

//Modifying common gNodeB mobility parameters
MOD GNBMOBILITYCOMMPARAM: NecHoPrepFailPunishTimer=0, OptHoPrepFailPunishTimer=0,
NonResHoPrepFailPunishTimes=10;
//Configuring the policy on frequency delivery for inter-frequency measurement with NR frequencies in the
NRCellFreqRelation MO to be sent as well as frequency filtering in blind mode with frequencies outside the
NRCellFreqRelation MO to be filtered out
MOD NRCELLOPPOLICY: NrCellId=0, OperatorId=0,
FreqConfigPolicySwitch=OPERATOR_NR_FREQ_CFG_SW-1;
//Modifying SMTC configuration
MOD NRDUCELL: NrDuCellId=0, DuplexMode=CELL_FDD, SmtcPeriod=MS20, SmtcDuration=MS2;
MOD NRCELLFREQRELATION: NrCellId=0, SsbFreqPos=6600, FrequencyBand=N7, SmtcPeriod=MS20,
SmtcDuration=MS3;
//Modifying the configuration for SSB beam measurement result selection and combination
//Modifying the measurement filtering configuration
MOD NRCELLMOBILITYCONFIG: NrCellId=0, BeamRsrpFilterCoeff=FC4, CellRsrpFilterCoeff=FC4;
//Enabling the function of non-overlapping between gap and NR resources in low-frequency SA networking
MOD GNBMOBILITYCOMMPARAM: MeasAlgoSwitch=GAP_AVOID_NR_RES_SW-1;
//Turning on the measurement ID preemption switch
MOD GNBMOBILITYCOMMPARAM: MeasAlgoSwitch=MEAS_ID_PREEMPTION_SW-1;
//Enabling the sending of full configurations during inter-base-station handovers
MOD NRCELLALGOSWITCH: NrCellId=0, HoCompatibilitySwitch=INTER_GNB_HO_FULL_CONFIG_SW-1;
//Enabling preferential handling of voice fallback
MOD GNBMOBILITYCOMMPARAM: HoPduSessConflHandlingSw=VOICE_FB_FIRST_SWITCH-1;
//Enabling preferential handling of QoS procedures (QCI 1 used as an example)
MOD NRCELLQCIBEARER: NrCellId=0, Qci=1, HoQosFlowConflProcStrat=QOS_FLOW_FIRST_SW-1;
//Turning on the mobility restriction switch
MOD GNBMOBILITYCOMMPARAM: MobilityAlgoSwitch=MOBILITY_RESTRICTION_SW-1;
//Turning on the EPLMN-based intra-RAT inter-PLMN handover switch
MOD GNODEBPARAM: EqvPlmnAlgoSwitch=INTRA_RAT_HO_WITH_GNB_EPLMN_SW-1;
//Adding an EPLMN for an operator of the gNodeB (In this example, OperatorId is set to 0, EquivalentMcc
is set to 520, and EquivalentMnc is set to 15. The configuration depends on the actual requirements.)
ADD GNBEQVPLMN: OperatorId=0, EquivalentMcc="520", EquivalentMnc="15";
//Setting the frequency interference flag if RSRP needs to be used as the triggering quantity with RSRQ-
based filtering
//Selecting XN_HO_INTERRUPT_DUR_OPT_SW
MOD GNBMOBILITYCOMMPARAM: ProtocolCompatibilitySw=XN_HO_INTERRUPT_DUR_OPT_SW-1;
//Turning on the SMTC offset compatibility switch
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, AlgoCompatibilitySwitchExt=SMTC_OFFSET_COMPAT_SW-1;

(2021-12-30)
5G RAN
Deactivation Command Examples

MML commands are not required for deactivating this function. You can
determine whether to restore the settings of other parameters based on actual
network conditions.
4.1.4.1.3 Using the MAE-Deployment

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

To verify the activation of a function, see section "Activation Verification" of the
corresponding function.
4.1.4.3 Network Monitoring

To perform network monitoring for a function, see section "Network Monitoring"
of the corresponding function.
4.2 Coverage-based Intra-Frequency Handover

On a network with continuous coverage, a coverage-based handover is triggered
for a UE moving towards the cell edge, where it receives higher-quality signals
from neighboring cells than from the serving cell. This prevents service drops
caused by signal quality deterioration. Figure 4-5 illustrates a coverage-based
handover.
Figure 4-5 Coverage-based handover
Coverage-based handovers are classified into intra-frequency handovers and inter-

frequency handovers. This section describes coverage-based intra-frequency
handovers. For details about coverage-based inter-frequency handovers, see 4.3
Coverage-based Inter-Frequency Handover.
4.2.1 Principles
Coverage-based intra-frequency handover is a basic function that ensures
continuous coverage. Measurement configurations are sent after RRC connections
are set up. A handover is executed when a target cell that meets the specific
requirement is available, requiring no handover function start decision. This
handover function does not apply to the blind mode. Figure 4-6 shows the
procedure of coverage-based intra-frequency handover. This section describes the

(2021-12-30)
5G RAN
differences between this function and the basic handover functions presented in
4.1 Basic Functions of Mobility Management in Connected Mode.
Figure 4-6 Procedure of coverage-based intra-frequency handover
This function differs from the basic handover functions as follows:

● Measurement configuration delivery: The measurement event in the reporting
configuration of this function is event A3 (indicating the signal quality of a
neighboring cell is higher than that of the serving cell by a certain threshold).
● Measurement reporting: Upon determining that the measurement results
meet the criteria for reporting event A3, UEs send the measurement reports
to the gNodeB.
● Target cell or frequency decision: The gNodeB generates a target cell list or a
target frequency list based on the measurement reports of event A3 and
selects the cell with the best quality for the handover.

(2021-12-30)
5G RAN
For details about the definition, entering conditions, and leaving conditions for
event A3, see Measurement Event. For the variable configurations for event A3,
see Table 4-7.
4.2.2.1 Benefits
Coverage-based intra-frequency handovers reduce interference caused by intra-
frequency neighboring cells in SA intra-frequency networking, thereby reducing
the service drop rate and providing users with seamless service experience.
4.2.2.2 Impacts
Network Impacts
During a handover, the UE needs to synchronize with the target cell and initiate
random access. This increases delay due to service interruption, affecting
throughput.
Function Impacts
None
4.2.3 Requirements
4.2.3.1 Licenses
4.2.3.2 Software
None

None
4.2.3.3 Hardware
Base Station Models

with the BBU3910.


(2021-12-30)
5G RAN
Boards
RF Modules
Documentation.
4.2.3.4 Others
None

The effectiveness of this function depends on neighbor relationships. For details
about neighbor relationship configurations, see 4.1.4.1 Data Configuration.
Table 4-15 describes the parameters used for function optimization.
Table 4-15 Parameters used for optimization

Name
NR Cell ID NRCellIntraFHoMeaGrp.NrCellId Set this parameter

plan.
Intra-freq NRCellIntraFHoMeaGrp.IntraFreqHo Set this parameter

Handover MeasGroupId based on the network
Measurement plan.
Group ID
Intra- NRCellIntraFHoMeaGrp.IntraFreqHo Set this parameter to

frequency A3TimeToTrig its recommended
Handover A3 value.
Time To
Trigger

frequency A3Hyst its recommended
Handover A3 value.
Hysteresis

(2021-12-30)
5G RAN

Name

frequency A3Offset its recommended
Handover A3 value.
Offset
QoS Class NRCellQciBearer.Qci Set this parameter

Identifier based on the network
plan.
Intra-freq NRCellQciBearer.IntraFreqHoMeas- Set this parameter

Handover GroupId based on the network
Measurement plan.
Group ID
QoS Class gNBQciBearer.Qci Set this parameter

plan.
QCI Priority gNBQciBearer.QciPriorityForHo Set this parameter

for Handover based on the network
plan.



(2021-12-30)
5G RAN

//Configuring measurement parameters for intra-frequency handovers
MOD NRCELLINTRAFHOMEAGRP: NrCellId=0, IntraFreqHoMeasGroupId=0, IntraFreqHoA3Offset=2,
IntraFreqHoA3Hyst=2, IntraFreqHoA3TimeToTrig=320MS;
//(Optional) QCI-specific measurement parameter configuration
MOD NRCELLQCIBEARER: NrCellId=0, Qci=1, IntraFreqHoMeasGroupId=0;
//Configuring QCI priorities for handovers
MOD GNBQCIBEARER: Qci=1, QciPriorityForHo=1;

//Configuring measurement parameters for intra-frequency handovers

network conditions.


If any of the following counters have a value other than 0, coverage-based intra-
frequency handover has taken effect:
● N.HO.IntraFreq.Ng.IntergNB.PrepAttOut
● N.HO.IntraFreq.Xn.IntergNB.PrepAttOut
● N.HO.IntraFreq.IntragNB.PrepAttOut

This function provides basic assurance for intra-frequency handovers and can be
monitored using the Intra-Frequency Handover Out Success Rate (CU) KPI.
4.3 Coverage-based Inter-Frequency Handover
4.3.1 Principles

(2021-12-30)
5G RAN
4.3.1.1 Basic Procedure

Figure 4-7 shows the procedure of coverage-based inter-frequency handover. This
section describes the differences between this function and the basic handover
functions presented in 4.1 Basic Functions of Mobility Management in
Connected Mode.
Figure 4-7 Procedure of coverage-based inter-frequency handover

(2021-12-30)
5G RAN
NOTE
In low frequency bands, event A5 or A3 can be used to trigger execution of coverage-based

inter-frequency handovers, depending on the value EVENT_A5 or EVENT_A3 configured for
the NRCellFreqRelation.InterFreqHoEventType parameter. Assume that spectrums overlap
between cells and the configured SSB frequency-domain positions are different. If event A5
is used to trigger handover execution, handovers may not be executed promptly due to
severe interference between the cells, causing service drops. Therefore, it is recommended
that event A3 be used to quickly trigger handover execution in such scenarios. In other
scenarios, it is recommended that event A5 be used to trigger handover execution.
In high frequency bands, event A5 is used to trigger execution of coverage-based inter-
frequency handovers. That is, the NRCellFreqRelation.InterFreqHoEventType parameter
can only be set to EVENT_A5.
Handover Function Start Decision

Coverage-based inter-frequency handover includes the following sub-functions,
and their start conditions are as follows:
● Measurement-based inter-frequency handover, which is started when all of
the following conditions are met:
– The COVERAGE_BASED_HO option of the
NRCellAlgoSwitch.InterFreqHoSwitch parameter is selected.
– The gNodeB receives a measurement report indicating that the measured
RSRP or RSRQ of a frequency (or cell) meets the entering conditions for
event A2 related to coverage-based inter-frequency measurements.
▪ Only RSRP is used as the triggering quantity for event A2 related to

coverage-based inter-frequency measurements.
The gNodeB receives a measurement report indicating that the
measured RSRP of a frequency (or cell) meets the entering
conditions for event A2 (indicating the signal quality of the serving
cell drops below a specific threshold) related to coverage-based
inter-frequency measurements.
RSRP threshold for event A2: If the
NRCellFreqRelation.InterFreqHoEventType parameter is set to
EVENT_A5 for a frequency, this threshold is specified by the
NRCellInterFHoMeaGrp.CovInterFreqA2RsrpThld parameter. If
NRCellFreqRelation.InterFreqHoEventType is set to EVENT_A3 for
a frequency, this threshold is specified by the
NRCellInterFHoMeaGrp.A3InterFreqHoA2RsrpThld parameter.
▪ Both RSRP and RSRQ are used as the triggering quantities for event
A2 related to coverage-based inter-frequency measurements.
conditions for event A2 (indicating the signal quality of the serving
cell drops below a specific threshold) related to coverage-based
inter-frequency measurements. Alternatively, it receives a
measurement report indicating that the measured RSRQ of a
frequency (or cell) meets the entering conditions for event A2
(indicating the signal quality of the serving cell drops below a
specific threshold) related to coverage-based inter-frequency
measurements.

(2021-12-30)
5G RAN

NRCellFreqRelation.InterFreqHoEventType is set to EVENT_A3 for
a frequency, this threshold is specified by the
RSRQ threshold for event A2: This threshold is specified by the
NRCellInterFHoMeaGrp.CovInterFreqA2RsrqThld parameter.
– UEs support inter-frequency measurement and inter-frequency handover.
● Redirection, which can be implemented in two modes:
– Blind mode when all of the following conditions are met:
▪ The REDIRECTION option of the

▪ The gNodeB receives a measurement report indicating that the

measured RSRP or RSRQ of a frequency (or cell) meets the entering
conditions for event A2 related to the blind mode.
○ Only RSRP is used as the triggering quantity for event A2 related
to the blind mode.
conditions for event A2 (indicating the signal quality of the
serving cell drops below a specific threshold, which is specified
by the NRCellInterRHoMeaGrp.CovHoToEutranBlindA2Thld
parameter) related to the blind mode.
○ Both RSRP and RSRQ are used as the triggering quantities for
event A2 related to the blind mode.
serving cell drops below a specific threshold, which is specified
by the NRCellInterRHoMeaGrp.CovHoToEutranBlindA2Thld
parameter) related to the blind mode. Alternatively, it receives a
measurement report indicating that the measured RSRQ of a
frequency (or cell) meets the entering conditions for event A2
(indicating the signal quality of the serving cell drops below a
specific threshold, which is specified by the
NRCellInterRHoMeaGrp.CovHoToLteBlindA2RsrqThld
parameter) related to the blind mode.
– Measurement-based mode when all of the following conditions are met:
▪ The REDIRECTION option of the

▪ The gNodeB receives a measurement report indicating that the

measured RSRP or RSRQ of a frequency (or cell) meets the entering
conditions for event A2 related to coverage-based inter-frequency
measurements.
○ Only RSRP is used as the triggering quantity for event A2 related
to coverage-based inter-frequency measurements.

(2021-12-30)
5G RAN

serving cell drops below a specific threshold) related to
coverage-based inter-frequency measurements.
NRCellFreqRelation.InterFreqHoEventType is set to EVENT_A3
for a frequency, this threshold is specified by the
○ Both RSRP and RSRQ are used as the triggering quantities for
event A2 related to coverage-based inter-frequency
measurements.
serving cell drops below a specific threshold) related to
coverage-based inter-frequency measurements. Alternatively, it
receives a measurement report indicating that the measured
RSRQ of a frequency (or cell) meets the entering conditions for
event A2 (indicating the signal quality of the serving cell drops
below a specific threshold) related to coverage-based inter-
frequency measurements.
NRCellFreqRelation.InterFreqHoEventType is set to EVENT_A3
for a frequency, this threshold is specified by the
RSRQ threshold for event A2: This threshold is specified by the
NRCellInterFHoMeaGrp.CovInterFreqA2RsrqThld parameter.
▪ UEs support inter-frequency measurement but do not support inter-

frequency handover.

NRCellMobilityConfig.A1A2MeasTrigQty parameter determines the triggering
quantity for event A2.
● If this option is deselected, only RSRP is used as the triggering quantity. The
gNodeB sends only the RSRP-indicating measurement configuration related to
event A2 to a UE, based on which the UE performs measurements. When
determining that the measured RSRP of a frequency (or cell) meets the
entering conditions for the event, the UE sends a measurement report to the
gNodeB to trigger a handover or redirection.
● If this option is selected, both RSRP and RSRQ are used as the triggering
quantities. The gNodeB sends both RSRP- and RSRQ-indicating measurement
configurations related to event A2 to a UE, based on which the UE performs
measurements. When determining that the measured RSRP or RSRQ of a

(2021-12-30)
5G RAN
frequency (or cell) meets the entering conditions for the event, the UE sends
a measurement report to the gNodeB to trigger a handover or redirection.
see Table 4-6.
Measurement Configuration Delivery

After measurement-based inter-frequency handover or measurement-based
redirection is started, the gNodeB sends related measurement configurations.
● If the NRCellFreqRelation.InterFreqHoEventType parameter is set to
EVENT_A5 for a frequency, the gNodeB sends measurement configurations
for event A5 (indicating the signal quality of the serving cell drops below
threshold 1 and the signal quality of a neighboring cell exceeds threshold 2)
related to coverage-based inter-frequency measurements and for event A1
(indicating the signal quality of the serving cell exceeds a specific threshold)
related to coverage-based inter-frequency measurements.
● If the NRCellFreqRelation.InterFreqHoEventType parameter is set to
EVENT_A3 for a frequency, the gNodeB sends measurement configurations
for event A3 (indicating the signal quality of a neighboring cell is higher than
that of the serving cell by a certain offset) related to coverage-based inter-
frequency measurements and for event A1 (indicating the signal quality of
the serving cell exceeds a specific threshold) related to coverage-based inter-
frequency measurements.
quantity for event A1 related to coverage-based inter-frequency measurements.
● If this option is deselected, only RSRP is used as the triggering quantity. The
gNodeB sends only the RSRP-indicating measurement configuration related to
entering conditions for the event, the UE sends a measurement report to the
gNodeB. After event A1 reports that correspond to previous event A2 reports
are all received, the handover or redirection is stopped.
● If this option is selected, both RSRP and RSRQ are used as the triggering
quantities. The gNodeB sends both RSRP- and RSRQ-indicating measurement
configurations related to event A1 to a UE, based on which the UE performs
measurements. When determining that the measured RSRP or RSRQ of a
frequency (or cell) meets the entering conditions for the event, the UE sends
a measurement report to the gNodeB. After RSRP- and RSRQ-triggered event
A1 reports that respectively correspond to previous RSRP- and RSRQ-triggered
event A2 reports are all received, the handover or redirection function is
stopped.
The triggering quantity for event A5 related to coverage-based inter-frequency
measurements is determined by the NRCellFreqRelation.FreqIntrfFlag parameter.
● If this parameter is set to NO_INTRF for a frequency, only RSRP is used as the
triggering quantity. The gNodeB sends only the RSRP-indicating measurement
configuration related to event A5 to a UE, based on which the UE performs
measurements. When determining that the RSRP meets the entering

(2021-12-30)
5G RAN
conditions for the event, the UE sends a measurement report to the gNodeB.
The gNodeB then determines the target cells or frequencies based on the
measurement report.
● If this parameter is set to INTRF for a frequency, RSRP is used as the
triggering quantity, combined with RSRQ-based filtering. The gNodeB sends
both RSRP- and RSRQ-indicating measurement configurations related to
entering conditions for event A5, the UE sends the gNodeB a measurement
report including the measured RSRP and RSRQ. Then, the gNodeB generates a
candidate cell list or a candidate frequency list based on the measured RSRP,
and filters out specific candidate cells based on the measured RSRQ. For
details about RSRQ-based filtering, see Generation of a Target Cell or
Frequency List.
Only RSRP is used as the triggering quantity for event A3 related to coverage-
based inter-frequency measurements. The gNodeB sends only the RSRP-indicating
measurement configuration related to event A3 to a UE, based on which the UE
performs measurements. When determining that the RSRP meets the entering
conditions for the event, the UE sends a measurement report to the gNodeB. The
gNodeB then determines the target cells or frequencies based on the
measurement report.
For details about the definitions, entering conditions, and leaving conditions for
events A5/A3/A1, see Measurement Event. For details about the variable
configurations for event A5, see Table 4-9. For details about the variable
configurations for event A1, see Table 4-5.
Measurement Reporting
A UE performs measurements based on the event measurement configuration and
reports the event based on the results.
● If event A5 (indicating the signal quality of the serving cell drops below
threshold 1 and the signal quality of a neighboring cell exceeds threshold 2)
related to coverage-based inter-frequency measurements is reported, the
gNodeB determines the target cells or frequencies based on the measurement
report. If RSRP is used as the triggering quantity with RSRQ-based filtering,
the gNodeB further filters candidate cells based on the measured RSRQ. For
details about RSRQ-based filtering, see Generation of a Target Cell or
Frequency List.
● If event A3 (indicating the signal quality of a neighboring cell is higher than
that of the serving cell by a certain offset) related to coverage-based inter-
frequency measurements is reported, the gNodeB determines the target cells
or frequencies based on the measurement report.
● If event A1 (indicating the signal quality of the serving cell exceeds a specific
threshold) related to coverage-based inter-frequency measurements is
reported, the gNodeB instructs the UE to stop coverage-based inter-frequency
measurements for event A5, and the UE then stops related event A5
measurements, which results in the corresponding function being stopped. If
both RSRP and RSRQ are used as the triggering quantities, coverage-based
inter-frequency measurements for event A5 are stopped only after RSRP- and

(2021-12-30)
5G RAN
RSRQ-triggered event A1 reports that respectively correspond to previous

RSRP- and RSRQ-triggered event A2 reports are all received, which results in
the corresponding function being stopped.
Target Cell or Frequency Decision

The gNodeB performs target cell or frequency decision based on handover
functions.
● For measurement-based inter-frequency handover, after event A5 or A3
related to coverage-based inter-frequency measurements is received:
– Inter-frequency handover is performed if it is supported by the UE. In this
case, the gNodeB sorts measurement reports based on the order in which
they are reported and the target cells contained in the measurement
reports based on the RSRP values of the target cells in descending order,
and then attempts handover to the target cells one by one.
– If the UE does not support inter-frequency handover, redirection is
performed.
● The target frequency decision for redirection depends on the processing
modes.
– Blind mode: After an event A2 related to the blind mode is received,
frequencies are sorted according to their connected-mode priorities
(configured by the NRCellFreqRelation.ConnFreqPriority parameter)
and the frequency with a higher connected-mode priority is preferentially
selected for redirection.
NOTE
As access to a supplementary cell is not supported, it is recommended that the

NRCellFreqRelation.ConnFreqPriority parameter be set to 0 for the frequency
at which the supplementary cell operates. This setting prevents blind redirection
to this frequency from being initiated. For details about supplementary cells, see
Cell Management.
– Measurement-based mode: After event A5 or A3 related to coverage-
based inter-frequency measurements is received, if the UE does not
support inter-frequency handover, the gNodeB selects the frequency of
the cell with the highest signal quality for redirection.
4.3.1.2 Blind Redirection Optimization

This section describes blind redirection optimization. This function is enabled when
the A2_BLIND_REDIRECT_CTRL_SW option of the
NRCellAlgoSwitch.ProcessSwitch parameter is selected. After this function is
enabled, the gNodeB preferentially triggers a blind redirection procedure in
specific scenarios. Further details are as follows:
● After a UE sends a blind event A2 report, if the gNodeB initiates an RRC
connection release procedure due to an air interface-related exception (for
example, RRC reconfiguration timeout), the gNodeB performs subsequent
operations based on the setting of the A2_BLIND_REDIRECT_CTRL_SW
option of the NRCellAlgoSwitch.ProcessSwitch parameter.
– If this option is deselected, the gNodeB triggers an RRC connection
release procedure to release the UE. As a result, the UE experiences a
service drop.

(2021-12-30)
5G RAN
– If this option is selected, the gNodeB triggers an RRC connection release

procedure for blind redirection.
● After the gNodeB sends an RRCReconfiguration message to a UE, if the
gNodeB receives blind event A2 and measurement-based event A2 reports
before receiving an RRCReconfigurationComplete message from the UE, upon
receipt of the RRCReconfigurationComplete message, the gNodeB performs
subsequent operations based on the setting of the
A2_BLIND_REDIRECT_CTRL_SW option of the
NRCellAlgoSwitch.ProcessSwitch parameter.
– If this option is deselected, the gNodeB processes the measurement
reports according to the time sequence in which they are received.
– If this option is selected, the gNodeB preferentially processes the blind
event A2 report.
● After receiving a measurement-based event A2 report from a UE, the gNodeB
performs subsequent operations based on the setting of the
A2_BLIND_REDIRECT_CTRL_SW option of the
NRCellAlgoSwitch.ProcessSwitch parameter.
– If this option is deselected, the gNodeB directly processes the
measurement-based event A2 report.
– If this option is selected, the gNodeB checks whether the signal quality of
the serving cell is lower than the value of
NRCellInterRHoMeaGrp.CovHoToEutranBlindA2Thld. If so, the gNodeB
triggers a blind redirection procedure. If not, the gNodeB processes the
measurement-based event A2 report.
4.3.2.1 Benefits
Coverage-based inter-frequency handovers ensure that coverage is continuous and
service experience is consistent for moving UEs.
The service drop rate decreases after the blind redirection optimization function is
enabled. The service drop rate is indicated by counters such as Service‧Call‧Drop‧
Rate‧(CU), Service‧Call‧Drop‧Rate‧(CU,‧Inactive), and Call‧Drop‧Rate‧(CU,‧
VoNR).
4.3.2.2 Impacts
Network Impacts
This function results in the following network impacts:
● During a handover, the UE needs to synchronize with the target cell and
initiate random access. This increases delay due to service interruption,
affecting throughput.
● Inter-frequency measurements require the use of measurement gaps, leading
to decreased throughput.

(2021-12-30)
5G RAN
Function Impacts
Name Switch
Low- Slot None Standards When a UE simultaneously

freque Configurati Complianc measures multiple non-
ncy on e serving frequencies, it is
TDD recommended that the
High- frame offset difference
freque between any two
ncy frequencies be less than or
TDD equal to 3 ms so that they
can be correctly measured.
The frame offset is specified
by the
gNBFreqBandConfig.Fram
eOffset parameter.
FDD Intra-RAT AUTO_NR_FR ANR If measurement-based
Low- ANR EQ_RELATION inter-frequency handover is
freque _SW option of disabled, intra-RAT ANR will
ncy the not be triggered by
TDD NRCellAlgoS measurement-based inter-
witch.AnrSwit frequency handover
High- ch parameter because such handover
freque does not take effect.
ncy
TDD If redirection is disabled,
intra-RAT ANR will not be
triggered by measurement-
based redirection because
such redirection does not
take effect.
FDD UE- INTER_FREQ_ Mobility If both coverage-based

Low- number- CONNECTED_ Load inter-frequency handover
freque based MLB_SW Balancing and connected mode MLB
ncy connected option of the are enabled, coverage-
TDD mode MLB NRCellAlgoS based inter-frequency
witch.MlbAlg handovers are triggered by
oSwitch event A5, and the value of
parameter NRCellInterFHoMeaGrp.Int
erFreqMlbA4RsrpThld is
less than or equal to the
value of
NRCellInterFHoMeaGrp.Co
vInterFreqA5RsrpThld2,
ping-pong between
coverage-based handovers
and MLB-based handovers
will occur.

(2021-12-30)
5G RAN

Name Switch
FDD Spectral- INTER_FREQ_ Mobility If both coverage-based

Low- efficiency- CONNECTED_ Load inter-frequency handover
freque based MLB_SW Balancing and connected mode MLB
ncy connected option of the are enabled, coverage-
TDD mode MLB NRCellAlgoS based inter-frequency
witch.MlbAlg handovers are triggered by
oSwitch event A5, and the value of
value of
ping-pong between
will occur.
Low- 5QI- INTER_FREQ_ Mobility If both coverage-based

freque specific CONNECTED_ Load inter-frequency handover
ncy UE- MLB_SW Balancing and connected mode MLB
TDD number- option of the are enabled, coverage-
based NRCellAlgoS based inter-frequency
connected witch.MlbAlg handovers are triggered by
mode MLB oSwitch event A5, and the value of
value of
ping-pong between
will occur.
4.3.3 Requirements
4.3.3.1 Licenses
4.3.3.2 Software
None

(2021-12-30)
5G RAN

None
4.3.3.3 Hardware
Base Station Models

with the BBU3910.

Boards
RF Modules
Documentation.
4.3.3.4 Others
UE support is required for inter-frequency intra-FR1 FDD handover/inter-frequency
intra-FR1 TDD handover/inter-frequency intra-FR2 TDD handover, and indicated by
the handoverInterF IE in the UECapabilityInformation message over the Uu
interface.
UE support is required for inter-frequency FDD-TDD handover, and indicated by

the handoverFDD-TDD IE in the UECapabilityInformation message over the Uu
interface.
UE support is required for inter-frequency FR1-FR2 handover, and indicated by the

handoverFR1-FR2 IE in the UECapabilityInformation message over the Uu
interface.
The handoverInterF IE can be included in the measAndMobParametersXDD-Diff/

measAndMobParametersFRX-Diff/fdd-Add-UE-NR-Capabilities/tdd-Add-UE-NR-
Capabilities/fr1-Add-UE-NR-Capabilities/fr2-Add-UE-NR-Capabilities IEs. For this
reason, whether UEs support inter-frequency handover is evaluated based on the
value of handoverInterF in those IEs. For details on evaluation based on
handoverInterF/handoverFDD-TDD/handoverFR1-FR2, see section 4.2 "UE
Capability Parameters" in 3GPP TS 38.306 V15.9.0.
Since the values of handoverInterF in the said IEs may differ, the methods to
evaluate whether UEs support inter-frequency handover may vary among vendors.
In this context, 3GPP TS 38.306 V16.1.0 updates the definition of the inter-
frequency handover capability of UEs and defines the method of checking the
capability based on the combination of handoverInterF values in different IEs. For

(2021-12-30)
5G RAN
details, see "Annex B: UE capability indication for UE capabilities with both

FDD/TDD and FR1/FR2 differentiations" in 3GPP TS 38.306 V16.1.0.
To ensure UE compatibility and improve the accuracy of UE capability evaluation,

compatibility processing optimization has been made in accordance with the latest
definition in 3GPP specifications. The INTER_FREQ_HO_CAPB_IND_OPT_SW
option of the gNBMobilityCommParam.ProtocolCompatibilitySw parameter
determines whether to enable the optimization. It is recommended that this
option be selected. If this option is selected, the number of NR inter-frequency
handovers due to protocol incompatibility of UEs decreases, that is, the number of
invalid inter-frequency handover attempts decreases.
● If this option is selected:

During evaluation of UE support for inter-frequency handover, the gNodeB
checks the handoverInterF IE in compliance with the new definition of
checking the inter-frequency handover capability of UEs in 3GPP TS 38.306
V16.1.0.
During evaluation of UE support for inter-frequency FDD-TDD handover and
inter-frequency FR1-FR2 handover, the gNodeB first checks the
handoverInterF IE to determine whether outgoing handovers from the current
cell are allowed. It then checks the handoverFDD-TDD IE to determine
whether UEs support inter-frequency FDD-TDD handover and the
handoverFR1-FR2 IE to determine whether UEs support inter-frequency FR1-
FR2 handover.
● If this option is deselected:
checks the handoverInterF IE in compliance with the old definition of checking
the inter-frequency handover capability of UEs in 3GPP TS 38.306 V16.1.0.
inter-frequency FR1-FR2 handover, the gNodeB directly checks the
handoverFDD-TDD IE to determine whether UEs support inter-frequency FDD-
TDD handover and the handoverFR1-FR2 IE to determine whether UEs
support inter-frequency FR1-FR2 handover, without first checking the
handoverInterF IE.

The NR cell's frequency relationships and neighbor relationships must be
configured before this function is activated. For details about the NR cell's
frequency relationship configurations, see Table 4-16. For details about neighbor
relationship configurations, see Table 4-12.
Table 4-17 describes the function switch.
Table 4-18 describes other parameters used for function optimization.

(2021-12-30)
5G RAN

Name
NR Cell ID NRCellFreqRelati Set this parameter based on the network

on.NrCellId plan.
SSB NRCellFreqRelati Set this parameter based on the network

Frequency on.SsbFreqPos plan.
Position
SSB NRCellFreqRelati Set this parameter to its recommended

Frequency on.SsbDescMeth value.
Position od
Describe
Method
Frequency NRCellFreqRelati Set this parameter based on the network

Band on.FrequencyBan plan.
d
Subcarrier NRCellFreqRelati Set this parameter based on the network
Spacing on.SubcarrierSpa plan.
cing
Frequency NRCellFreqRelati It is recommended that this parameter be
Priority for on.ConnFreqPrior set to a non-zero value for frequencies
Connected ity providing continuous coverage, with a
Mode larger value set for a frequency in a lower
frequency band. It is recommended that
this parameter be set to 0 for frequencies
providing non-continuous coverage, which
means that such a frequency will not be
selected as the target frequency.
Inter-Freq HO NRCellFreqRelati In low frequency bands, it is recommended

Event Type on.InterFreqHoEv that this parameter be set to EVENT_A3 if
entType spectrums overlap between cells and the
configured SSB frequency-domain
positions are different and to EVENT_A5 in
other scenarios.
In high frequency bands, set this
parameter to EVENT_A5.

(2021-12-30)
5G RAN
Table 4-17 Inter-frequency handover algorithm switch

Name
Inter- NRCellAlgoSwitc Select COVERAGE_BASED_HO if coverage-

Frequency h.InterFreqHoSwi based inter-frequency handover needs to
Handover tch be enabled.
Switch Select REDIRECTION if inter-frequency
redirection needs to be enabled.
Table 4-18 Parameters related to inter-frequency handover measurement

configurations of NR cells
Name
NR Cell ID NRCellInterFHo Set this parameter based on the network

MeaGrp.NrCellId plan.
Inter-freq NRCellInterFHo Set this parameter based on the network

Handover MeaGrp.InterFre plan.
Measurement qHoMeasGroupId
Group ID
Inter- NRCellInterFHo Set this parameter to its recommended

frequency MeaGrp.InterFre value.
A1A2 Time to qA1A2TimeToTri
Trigger g
A1A2 qA1A2Hyst
Hysteresis
Cov Inter-freq NRCellInterFHo Set this parameter to its recommended

Handover A2 MeaGrp.CovInter value.
RSRP FreqA2RsrpThld
Threshold
A3 Inter-freq NRCellInterFHo Set this parameter to its recommended

Handover A2 MeaGrp.A3InterF value.
RSRP reqHoA2RsrpThl
Threshold d
RSRP FreqA1RsrpThld
Threshold

(2021-12-30)
5G RAN

Name
A3 Inter-freq NRCellInterFHo Set this parameter to its recommended

Handover A1 MeaGrp.A3InterF value.
RSRP reqHoA1RsrpThl
Threshold d
Cov HO to E- NRCellInterRHo Set this parameter to its recommended
UTRAN Blind MeaGrp.CovHoTo value.
A2 RSRP Thld EutranBlindA2Th
ld
A1A2 NRCellMobilityC Select the RSRP_AND_RSRQ_SW option if
Measurement onfig.A1A2MeasT both RSRP and RSRQ need to be used as
Trigger rigQty the triggering quantities for events A1/A2.
Quantity

HO A1 RSRQ MeaGrp.CovInter value.
Threshold FreqA1RsrqThld
HO A2 RSRQ MeaGrp.CovInter value.
Threshold FreqA2RsrqThld
Cov HO to E- NRCellInterRHo Set this parameter to its recommended
UTRAN Blind MeaGrp.CovHoTo value.
A2 RSRQ Thld LteBlindA2RsrqT
hld
Frequency NRCellFreqRelati ● Set this parameter to INTRF if RSRP
Interference on.FreqIntrfFlag needs to be used as the triggering
Flag quantity with RSRQ-based filtering for
event A5.
● Set this parameter to NO_INTRF if only
RSRP needs to be used as the triggering

HO RSRQ MeaGrp.CovInter value.
Threshold FreqA5RsrqThld2
Inter-freq NRCellInterFHo Set this parameter to its recommended
Measurement MeaGrp.InterFre value.
Event Time to qA4A5TimeToTri
Trigger g
Inter-freq NRCellInterFHo Set this parameter to its recommended
Measurement MeaGrp.InterFre value.
Event qA4A5Hyst
Hysteresis

(2021-12-30)
5G RAN

Name

RSRP FreqA5RsrpThld1
Threshold1

RSRP FreqA5RsrpThld2
Threshold2

Handover A3 qHoA3Offset
Offset
QoS Class NRCellQciBearer. Set this parameter based on the network

Identifier Qci plan.
Inter-freq NRCellQciBearer. Set this parameter based on the network

Handover InterFreqHoMeas plan.
Measurement GroupId
Group ID
Inter-RAT NRCellQciBearer. Set this parameter based on the network

Handover InterRatHoMeas plan.
Measurement GroupId
Group ID
NSA UE Inter- NRCellQciBearer. Set this parameter based on the network

freq HO NsaInterFreqHo plan.
Measurement MeasGroupId
Group ID
QoS Class gNBQciBearer.Qc Set this parameter based on the network

Identifier i plan.
QCI Priority gNBQciBearer.Qc Set this parameter based on the network

for Handover iPriorityForHo plan.
Protocol gNBMobilityCom It is recommended that the

Compatibility mParam.Protocol INTER_FREQ_HO_CAPB_IND_OPT_SW
Switch CompatibilitySw option be selected.
Process NRCellAlgoSwitc To enable blind redirection optimization,

Switch h.ProcessSwitch select the A2_BLIND_REDIRECT_CTRL_SW
option.

Before using MML commands, refer to 4.3.2.2 Impacts and complete the
parameter configurations for related functions based on the impact relationships
between the functions, as well as the actual network scenario.

(2021-12-30)
5G RAN

//Low frequency band: Adding a frequency relationship for an NR cell (In most scenarios, event A5 is used
to trigger handover execution.)
FrequencyBand=N77, SubcarrierSpacing=30KHZ, ConnFreqPriority=1, InterFreqHoEventType=EVENT_A5;
//Low frequency band: Adding a frequency relationship for an NR cell (Event A3 is used to trigger handover
execution when spectrums overlap between the serving cell and a neighboring cell and the configured SSB
frequency-domain positions are different.)
//High frequency band: Adding a frequency relationship for an NR cell (Only event A5 can be used to
trigger handover execution.)
//Activating coverage-based inter-frequency handover (including coverage-based inter-frequency handover
and inter-frequency redirection)
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=COVERAGE_BASED_HO-1&REDIRECTION-1;

//Adding a frequency relationship for an NR cell (In most scenarios, event A5 is used to trigger handover
execution.)
//Adding a frequency relationship for an NR cell (Event A3 is used to trigger handover execution when
spectrums overlap between the serving cell and a neighboring cell and the configured SSB frequency-
domain positions are different.)
//Activating coverage-based inter-frequency handover (including coverage-based inter-frequency handover
and inter-frequency redirection)

//Configuring a group of measurement parameters for inter-frequency handovers
MOD NRCELLINTERFHOMEAGRP: NrCellId=0, InterFreqHoMeasGroupId=0,
InterFreqA4A5TimeToTrig=320MS, InterFreqA4A5Hyst=2, InterFreqA1A2TimeToTrig=320MS,
InterFreqA1A2Hyst=2, CovInterFreqA5RsrpThld1=-110, CovInterFreqA5RsrpThld2=-106,
CovInterFreqA2RsrpThld=-110, CovInterFreqA2RsrqThld=-30, CovInterFreqA1RsrpThld=-106,
CovInterFreqA1RsrqThld=-26, CovInterFreqA5RsrqThld2=-24, A3InterFreqHoA1RsrpThld=-96,
A3InterFreqHoA2RsrpThld=-100, InterFreqHoA3Offset=2;

(2021-12-30)
5G RAN

//Configuring CovHoToEutranBlindA2Thld in the measurement parameter group related to inter-RAT
handover for an NR cell (CovHoToEutranBlindA2Thld for inter-frequency and inter-RAT blind redirection)
MOD NRCELLINTERRHOMEAGRP: NrCellId=0, InterRatHoMeasGroupId=0, CovHoToEutranBlindA2Thld=-126;
//Configuring CovHoToLteBlindA2RsrqThld in the measurement parameter group related to inter-RAT
handover for an NR cell (CovHoToLteBlindA2RsrqThld for inter-frequency and inter-RAT blind redirection)
MOD NRCELLINTERRHOMEAGRP: NrCellId=0, InterRatHoMeasGroupId=0, CovHoToLteBlindA2RsrqThld=-38;
//(Optional) QCI-specific measurement parameter configuration for SA UEs
MOD NRCELLQCIBEARER: NrCellId=0, Qci=1, InterFreqHoMeasGroupId=0, InterRatHoMeasGroupId=0;
//(Optional) QCI-specific measurement parameter configuration for NSA UEs
MOD NRCELLQCIBEARER: NrCellId=0, Qci=1, NsaInterFreqHoMeasGroupId=2;
//Selecting the RSRP_AND_RSRQ_SW option if both RSRP and RSRQ need to be used as the triggering
quantities for events A1/A2
MOD NRCELLMOBILITYCONFIG: NrCellId=0, A1A2MeasTrigQty=RSRP_AND_RSRQ_SW-1;
//Setting the frequency interference flag to INTRF if RSRP needs to be used as the triggering quantity with
RSRQ-based filtering for event A5
//Selecting INTER_FREQ_HO_CAPB_IND_OPT_SW
MOD GNBMOBILITYCOMMPARAM: ProtocolCompatibilitySw=INTER_FREQ_HO_CAPB_IND_OPT_SW-1;
//Turning on the A2-based blind redirection control switch if blind redirection optimization needs to be
enabled
MOD NRCELLALGOSWITCH: NrCellId=0, ProcessSwitch=A2_BLIND_REDIRECT_CTRL_SW-1;

//Configuring CovHoToEutranBlindA2Thld in the measurement parameter group related to inter-RAT
handover for an NR cell (CovHoToEutranBlindA2Thld for inter-frequency and inter-RAT blind redirection)
//Configuring CovHoToLteBlindA2RsrqThld in the measurement parameter group related to inter-RAT
handover for an NR cell (CovHoToLteBlindA2RsrqThld for inter-frequency and inter-RAT blind redirection)
//Selecting the RSRP_AND_RSRQ_SW option if both RSRP and RSRQ need to be used as the triggering
quantities for events A1/A2
MOD NRCELLMOBILITYCONFIG: NrCellId=0, A1A2MeasTrigQty=RSRP_AND_RSRQ_SW-1;
//Setting the frequency interference flag to INTRF if RSRP needs to be used as the triggering quantity with

(2021-12-30)
5G RAN
RSRQ-based filtering for event A5

//Turning on the A2-based blind redirection control switch if blind redirection optimization needs to be
enabled
MOD NRCELLALGOSWITCH: NrCellId=0, ProcessSwitch=A2_BLIND_REDIRECT_CTRL_SW-1;

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.

//Deactivating coverage-based inter-frequency handover (including coverage-based inter-frequency
handover and inter-frequency redirection)

//Deactivating coverage-based inter-frequency handover (including coverage-based inter-frequency
handover and inter-frequency redirection)


If any of the following counters have a value other than 0, coverage-based inter-
● N.HO.InterFreq.Coverage.PrepAttOut
● N.HO.InterFreq.Coverage.ExecAttOut
● N.HO.InterFreq.Coverage.ExecSuccOut
After optimized configuration for deriveSSB-IndexFromCell is enabled, perform the

following operations to check whether it has taken effect:
● If the serving frequency is an NR TDD frequency and the frequency to be
measured is an NR FDD frequency, check whether the value of the deriveSSB-
IndexFromCell IE corresponding to the frequency to be measured in the
RRCReconfiguration message sent by the gNodeB is TRUE, which shows that
the function has taken effect.
● If the serving frequency is an NR FDD frequency and the frequency to be
measured is an NR TDD frequency, check whether the value of the deriveSSB-

This function provides basic assurance for inter-frequency handovers and can be
monitored using the Inter-Frequency Handover Out Success Rate (CU) KPI.

(2021-12-30)
5G RAN
4.4 Frequency-Priority-based Inter-Frequency Handover

In multi-band co-coverage scenarios, frequency-priority-based inter-frequency
handover allows the higher frequency band to carry services as much as possible
to spare the lower frequency band for continuous coverage. Figure 4-8 illustrates
a frequency-priority-based inter-frequency handover.
Figure 4-8 Frequency-priority-based inter-frequency handover in multi-band co-

coverage scenarios
4.4.1 Principles
Figure 4-9 shows the procedure of frequency-priority-based inter-frequency
handover. This section describes the differences between this function and the
basic handover functions presented in 4.1 Basic Functions of Mobility
Management in Connected Mode.

(2021-12-30)
5G RAN
Figure 4-9 Procedure of frequency-priority-based inter-frequency handover

Frequency-priority-based inter-frequency handover supports only the
measurement-based mode, meaning this function does not support the blind
mode. This function is started when all of the following conditions are met:
● The FREQ_PRIORITY_BASED_HO option of the
● An event A1 (indicating that the signal quality of the serving cell exceeds a
specific threshold configured) report related to frequency-priority-based
measurements is received.

(2021-12-30)
5G RAN

After frequency-priority-based inter-frequency handover is started, the gNodeB
selects frequencies for which the traffic priority is not 0 and sends related
measurement configurations.
● If NRCellMobilityConfig.InterFreqMeasEventConfig is set to EVENT_A4, the
gNodeB sends measurement configurations for event A4 (indicating the signal
quality of a neighboring cell exceeds a specific threshold) related to
frequency-priority-based inter-frequency measurements and event A2
(indicating the signal quality of the serving cell drops below a specific
threshold) related to frequency-priority-based inter-frequency measurements.
quality of the serving cell drops below threshold 1 and the signal quality of a
neighboring cell exceeds threshold 2) related to frequency-priority-based
inter-frequency measurements and event A2 (indicating the signal quality of
the serving cell drops below a specific threshold) related to frequency-priority-
based inter-frequency measurements.
If no neighboring cell is reported after a UE has performed frequency-priority-
based A4 or A5 measurement for a period specified by
NRCellMobilityConfig.InterFreqMeasWaitTime (indicating the inter-frequency
measurement waiting time), the gNodeB releases the measurement configuration,
enabling the UE to stop the measurement for this event A4 or A5. The gNodeB
then periodically sends measurement configurations for event A4 or A5 related to
frequency-priority-based measurements to the UE at an interval specified by
NRCellMobilityConfig.FreqPriInterFHoRetryIntvl (indicating the retry period for
frequency-priority-based inter-frequency handover) plus
NRCellMobilityConfig.InterFreqMeasWaitTime (indicating the inter-frequency
measurement waiting time).
● A smaller retry period for frequency-priority-based inter-frequency handover
results in a higher probability of triggering frequency-priority-based inter-
frequency handover. When the signal quality of the target cell is poor, UEs
frequently perform inter-frequency measurements, decreasing user-perceived
throughput.
● A larger retry period for frequency-priority-based inter-frequency handover
results in a lower probability of triggering frequency-priority-based inter-
frequency handover. When the signal quality of the target cell is poor, the
number of unnecessary inter-frequency measurements decreases, increasing
user-perceived throughput.
NOTE
If the source gNodeB receives a measurement report from the UE and sends a Handover
Request message to the target gNodeB but does not receive a response from the target
gNodeB during a period specified by NRCellMobilityConfig.InterFreqMeasWaitTime, the
source gNodeB will again send measurement configurations for event A4 or A5 related to
frequency-priority-based measurements to the UE.

(2021-12-30)
5G RAN
● If event A4 (indicating the signal quality of a neighboring cell exceeds a

specific threshold) or A5 (indicating the signal quality of the serving cell drops
below threshold 1 and the signal quality of a neighboring cell exceeds
threshold 2) related to frequency-priority-based measurements is reported,
the gNodeB determines the target cells or frequencies based on the
measurement report.
● If event A2 (indicating the signal quality of the serving cell drops below a
specific threshold) related to frequency-priority-based measurements is
reported, the gNodeB instructs the UE to stop frequency-priority-based
measurements for event A4 or A5, and the UE then stops related event A4 or
A5 measurements, which results in the corresponding function being stopped.

After receiving event A4 (indicating the signal quality of a neighboring cell
exceeds a specific threshold) or A5 (indicating the signal quality of the serving cell
drops below threshold 1 and the signal quality of a neighboring cell exceeds
threshold 2) related to frequency-priority-based measurements, the gNodeB
obtains frequency information from the event A4 or A5 report related to
frequency-priority-based measurements and determines the target frequency as
follows:
● If the frequency has the highest traffic priority, the gNodeB chooses this
frequency as the target frequency and instructs the UE to perform a handover
to the target cell (that is, the best cell running on the frequency with the
highest traffic priority in the measurement report). The traffic priority is
specified by the NRCellFreqRelation.TrafficPriority parameter.
Wherein:
When the function of subscription to uplink interference information about
inter-frequency neighboring cells is enabled (by selecting the
INTER_FREQ_UL_INTRF_SW option of the
NRCellAlgoSwitch.NCellInfoCtrlSwitch parameter) for the serving cell, the
serving cell obtains uplink interference information about intra- or inter-base-
station neighboring cells, based on which the serving cell determines whether
to instruct the UE to initiate a handover. Specifically, the UE is instructed to
do so if the serving cell determines that the target cell is exposed to low
uplink interference. Otherwise, the UE is not instructed to perform a handover.
NOTE
For details about how the serving cell determines whether a neighboring cell is
exposed to low uplink interference, see Target Cell or Frequency Decision.
If frequency-priority-based inter-frequency handover is enabled for the serving cell and
uplink-interference-based inter-frequency handover is enabled for the target cell, you
are advised to enable the function of subscription to uplink interference information
about inter-frequency neighboring cells for the serving cell, avoiding ping-pong
handover.
When the inter-frequency handover collaboration function is enabled (by
selecting the INTER_FREQ_HO_COLLABORATION_SW option of the
NRCellAlgoSwitch.InterFreqHoSwitch parameter) for the serving cell, the
serving cell further determines whether to instruct the UE to initiate a
handover as follows:
– If the serving cell identifies that the target cell has entered the MLB state
through inter-cell load information exchange, the gNodeB does not

(2021-12-30)
5G RAN
instruct the UE to perform a handover to the target cell, avoiding ping-

pong handover.
– The serving cell checks whether the UE has a voice bearer.
▪ If so, the gNodeB does not instruct the UE to perform a handover to

the target cell, avoiding ping-pong handover.
▪ If not, the gNodeB proceeds to instruct the UE to perform a

handover to the target cell.
NOTE
When frequency-priority-based inter-frequency handover is enabled for the serving

cell, you are advised to enable the inter-frequency handover collaboration function to
avoid ping-pong handover if either MLB by transferring UEs in connected mode
between inter-frequency cells (specified by the INTER_FREQ_CONNECTED_MLB_SW
option of the NRCellAlgoSwitch.MlbAlgoSwitch parameter) or voice-quality-based
inter-frequency handover (specified by the VONR_QLTY_INTER_FREQ_HO_SW option
of the NRCellAlgoSwitch.VoiceStrategySwitch parameter) is enabled for the target
cell.
For details about MLB by transferring UEs in connected mode, see Mobility Load
Balancing. For details about voice-quality-based inter-frequency handover, see VoNR.
● If the frequency does not have the highest traffic priority, the gNodeB starts a
timer (fixed at 2s) and waits for the next measurement report. After the timer
expires, the gNodeB chooses the inter-frequency neighboring cell with the
highest traffic priority among those reported in this period for handover.
Parameter Configuration
The following table describes the parameters related to frequency-priority-based
inter-frequency handover.
● Traffic priority
The gNodeB selects traffic priority-related parameters based on whether
RFSP-specific frequency-priority-based inter-frequency handover is enabled
(as specified by the FREQ_PRIORITY_BASED_HO_SW option of the
NRCellAlgoSwitch.RfspAlgoSwitch parameter).
– If RFSP-specific frequency-priority-based inter-frequency handover is
disabled, the value of the NRCellFreqRelation.TrafficPriority parameter
is used as the traffic priority. In this case, the gNodeB sends all UEs in the
cell the frequencies whose traffic priorities are not 0 and higher than the
serving frequency.
– If RFSP-specific frequency-priority-based inter-frequency handover is
enabled, the parameters related to traffic priority are configured as
follows:
The gNodeB attempts to obtain the RFSP index of a UE from the core
network, and then sends the UE measurement configurations including
the frequency that is selected based on the RFSP index.
▪ If the gNodeB has obtained the UE's RFSP index from the core
network and the RFSP-index-specific gNBRfspConfig.RfspIndex
parameter (bound to a valid
gNBRfspConfig.gNBFreqPriorityGroupId parameter, which has a
non-255 value) has been configured on the gNodeB, the traffic
priority will be specified by the

(2021-12-30)
5G RAN
gNBFreqPriorityGroup.TrafficPriority parameter, which is bound to

the gNBRfspConfig.RfspIndex parameter. In this case, the gNodeB
sends the UE the RFSP-index-specific frequencies whose traffic
priorities are not 0 and higher than the serving frequency.
In this scenario, thresholds for RFSP-specific frequency-priority-based
event A1 and RFSP-specific frequency-priority-based event A2 can be
customized for UEs.
▪ If the gNodeB has obtained the UE's RFSP index from the core
network and the RFSP-index-specific gNBRfspConfig.RfspIndex
parameter has not been configured but a 0-value
gNBRfspConfig.RfspIndex parameter (bound to a valid
gNBRfspConfig.gNBFreqPriorityGroupId parameter, which has a
non-255 value) has been configured on the gNodeB, the traffic
priority will be specified by the
the 0-value gNBRfspConfig.RfspIndex parameter. In this case, the
gNodeB sends the UE the 0-value gNBRfspConfig.RfspIndex-specific
frequencies whose traffic priorities are not 0 and higher than the
serving frequency.
customized for UEs.
▪ If the gNodeB has failed to obtain the UE's RFSP index from the core
network and a 0-value gNBRfspConfig.RfspIndex parameter (bound
to a valid gNBRfspConfig.gNBFreqPriorityGroupId parameter,
which has a non-255 value) has been configured on the gNodeB, the
traffic priority will be specified by the
the 0-value gNBRfspConfig.RfspIndex parameter. In this case, the
gNodeB sends the UE the 0-value gNBRfspConfig.RfspIndex-specific
frequencies whose traffic priorities are not 0 and higher than the
serving frequency.
customized for UEs.
▪ In other scenarios, the value of the

NRCellFreqRelation.TrafficPriority parameter is used as the traffic
priority. The gNodeB sends the UE the frequencies whose traffic
priorities are not 0 and higher than the serving frequency.
In addition, thresholds for RFSP-specific frequency-priority-based
event A1 and RFSP-specific frequency-priority-based event A2 cannot
be customized for UEs.
● Threshold for frequency-priority-based event A1
– If the threshold for RFSP-specific frequency-priority-based event A1 is not
customized for a UE, the threshold for frequency-priority-based event A1
equals the value of the
NRCellInterFHoMeaGrp.FreqPriInterFA1RsrpThld parameter.
– If the threshold for RFSP-specific frequency-priority-based event A1 is

(2021-12-30)
5G RAN
equals the sum of the parameter values of

NRCellInterFHoMeaGrp.FreqPriInterFA1RsrpThld plus
gNBRfspConfig.FreqPriHoA1A2RsrpThldOfs.
For more information, see Table 4-5.
● Threshold for frequency-priority-based event A2
– If the threshold for RFSP-specific frequency-priority-based event A2 is not
equals the value of the
– If the threshold for RFSP-specific frequency-priority-based event A2 is
equals the sum of the parameter values of
NRCellInterFHoMeaGrp.FreqPriInterFA2RsrpThld plus
gNBRfspConfig.FreqPriHoA1A2RsrpThldOfs.
● The threshold for frequency-priority-based event A4 is specified by the
● The threshold 2 for frequency-priority-based event A5 is specified by the
NOTE
In NSA networking, the gNodeB uses the SPIDs to customize the frequency-priority-
based traffic priority, threshold for frequency-priority-based event A1, and threshold
for frequency-priority-based event A2 for UEs. After receiving the SPIDs from the
eNodeB, the gNodeB processes the SPIDs in the same way as in SA networking.
4.4.2.1 Benefits
This function provides a method to hand over UEs and allows for flexible
networking to help operators implement service steering.
4.4.2.2 Impacts
Network Impacts
● Networking of the existing network and the impact relationship between
frequency-priority-based inter-frequency handover and other handover
functions (such as service-based inter-frequency handover) must be

(2021-12-30)
5G RAN
considered to prevent ping-pong handovers and ensure user experience. For

details about networking requirements, see 4.4.3.4 Networking.
Function Impacts
Name Switch
FDD Intra-RAT AUTO_NR_FR ANR If frequency-priority-based

Low- ANR EQ_RELATION inter-frequency handover is
ncy the not be triggered by
TDD NRCellAlgoS frequency-priority-based
witch.AnrSwit inter-frequency handover
High- ch parameter because such handover
freque does not take effect.
ncy
TDD
FDD UE- INTER_FREQ_ Mobility If both UE-number-based

Low- number- CONNECTED_ Load connected mode MLB and
freque based MLB_SW Balancing frequency-priority-based
ncy connected option of the inter-frequency handover
TDD mode MLB NRCellAlgoS are enabled, the following
witch.MlbAlg are true: If a target cell
oSwitch rejects MLB-based
parameter handovers from a source
cell, the source cell may not
be allowed to initiate
frequency-priority-based
inter-frequency handovers
to the target cell in a short
period of time. The reverse
is also applicable.
FDD Spectral- INTER_FREQ_ Mobility If both spectral-efficiency-

Low- efficiency- CONNECTED_ Load based connected mode MLB
freque based MLB_SW Balancing and frequency-priority-
ncy connected option of the based inter-frequency
TDD mode MLB NRCellAlgoS handover are enabled, the
witch.MlbAlg following are true: If a
oSwitch target cell rejects MLB-
parameter based handovers from a
source cell, the source cell
may not be allowed to
initiate frequency-priority-
handovers to the target cell
in a short period of time.
The reverse is also
applicable.

(2021-12-30)
5G RAN

Name Switch
FDD Experience MULTI_FREQ_ Multi- When the smart carrier

Low- -based SMART_SEL_S Frequency selection policy (specified
freque smart W option of Convergen by the
ncy carrier the ce NRCellCaMgmtConfig.Sma
TDD selection NRCellAlgoS rtCarrSelPolicy parameter)
witch.MultiFr is set to
eqAlgoSwitch EXPERIENCE_FIRST, you
parameter are not advised to enable
experience-based smart
carrier selection (controlled
by the
MULTI_FREQ_SMART_SEL_
SW option of the
eqAlgoSwitch parameter)
or frequency-priority-based
inter-frequency handover
(controlled by the
FREQ_PRIORITY_BASED_H
O option of the
NRCellAlgoSwitch.InterFre
qHoSwitch parameter).
Otherwise, ping-pong
handover may occur.
4.4.3 Requirements
4.4.3.1 Licenses

(2021-12-30)
5G RAN
4.4.3.2 Software
Name Switch
FDD RFSP- INTER_FREQ_ Flexible If RFSP-specific frequency-

Low- based NR LIST_CTRL_S User priority-based inter-
freque inter- W option of Steering frequency handover is
ncy frequency the enabled (by selecting the
TDD handover NRCellAlgoS FREQ_PRIORITY_BASED_H
policy witch.RfspAlg O_SW option of the
High- oSwitch NRCellAlgoSwitch.RfspAlg
freque parameter oSwitch parameter), the
ncy RFSP-based NR inter-
TDD frequency handover policy
must also be enabled.

None
4.4.3.3 Hardware
Base Station Models

with the BBU3910.
Boards
RF Modules
Documentation.
4.4.3.4 Networking
During network planning, if an unnecessary handover function needs to be
enabled for multiple cells, a UE must be prevented from being handed over back
to the source cell after several unnecessary handovers of the same or different
types. Otherwise, the UE experiences repeated handovers and user experience is

(2021-12-30)
5G RAN
poor. Handovers other than coverage-based intra-frequency handovers and

coverage-based inter-frequency handovers are called unnecessary handovers.
Following are examples:
● During network planning, avoid the following situation: After a UE is handed
over from cell 1 to cell 2 through a frequency-priority-based handover, the UE
is handed over from cell 2 back to cell 1 through a frequency-priority-based
handover.
over from cell 1 to cell 2 through a frequency-priority-based inter-frequency
handover, the UE is handed over from cell 2 back to cell 1 through a service-
based inter-frequency handover.
● During network planning, avoid the following situation: A UE is handed over
from cell 1 to cell 2 through an uplink-interference-based inter-frequency
handover, then from cell 2 to cell 3 through a service-based inter-frequency
handover, and finally from cell 3 to cell 1 through a frequency-priority-based
handover.
4.4.3.5 Others
interface.
interface.
interface.

(2021-12-30)
5G RAN

V16.1.0.
FR2 handover.
handoverInterF IE.


Name

plan.

(2021-12-30)
5G RAN

Name

Position plan.

Position value.
Describe
Method

plan.

plan.
Traffic Priority NRCellFreqRelation.TrafficPriority Set this parameter

plan.

Name
Inter- NRCellAlgoSwitch.InterFreqHoSwitc Select the

Frequency h FREQ_PRIORITY_BAS
Handover ED_HO option.
Switch
Inter- NRCellAlgoSwitch.InterFreqHoSwitc To enable RFSP-

Frequency h specific frequency-
Handover priority-based inter-
Switch frequency handover,
select the
FREQ_PRIORITY_BAS
ED_HO_SW option.

(2021-12-30)
5G RAN

Name
Inter- NRCellAlgoSwitch.InterFreqHoSwitc To enable frequency-

Frequency h priority-based inter-
Handover frequency handover, it
Switch is recommended that
the
INTER_FREQ_HO_CO
LLABORATION_SW
option be selected
when either MLB by
transferring UEs in
connected mode
between inter-
frequency cells or
voice-quality-based
inter-frequency
handover is also
enabled.
Table 4-21 Parameters related to inter-frequency handover measurement

configurations of NR cells
Name
NR Cell ID NRCellInterFHoMeaGrp.NrCellId Set this parameter

plan.
Inter-freq NRCellInterFHoMeaGrp.InterFreqHo Set this parameter

Measurement plan.
Group ID
Inter- NRCellInterFHoMeaGrp.InterFreqA1 Set this parameter to

frequency A2TimeToTrig its recommended
A1A2 Time to value.
Trigger
Inter- NRCellInterFHoMeaGrp.InterFreqA1 Set this parameter to

frequency A2Hyst its recommended
A1A2 value.
Hysteresis
Freq Priority NRCellInterFHoMeaGrp.FreqPriInterF Set this parameter to

Inter-freq A1 A1RsrpThld its recommended
RSRP value.
Threshold

(2021-12-30)
5G RAN

Name
Freq Priority NRCellInterFHoMeaGrp.FreqPriInterF Set this parameter to

Inter-freq A2 A2RsrpThld its recommended
RSRP value.
Threshold
Inter-Freq NRCellMobilityCon- Set this parameter to

Measurement fig.InterFreqMeasEventConfig its recommended
Event value.
Configuration
Inter-freq NRCellInterFHoMeaGrp.InterFreqA4 Set this parameter to

Measurement A5TimeToTrig its recommended
Event Time to value.
Trigger

Measurement A5Hyst its recommended
Event value.
Hysteresis
Freq Priority NRCellInterFHoMeaGrp.FreqPriInterF This parameter

Inter-freq A4 A4RsrpThld indicates the RSRP
RSRP threshold for event A4
Threshold related to frequency-
priority-based inter-
frequency handover
and RSRP threshold 2
for event A5 related
to frequency-priority-
handover.
Set this parameter to
its recommended
value.

plan.
Inter-freq NRCellQciBearer.InterFreqHoMeas- Set this parameter

Measurement plan.
Group ID
NSA UE Inter- NRCellQciBearer.NsaInterFreqHoMe Set this parameter

freq HO asGroupId based on the network
Measurement plan.
Group ID

plan.

(2021-12-30)
5G RAN

Name

plan.
Protocol gNBMobilityCommPar- It is recommended

Compatibility am.ProtocolCompatibilitySw that the
Switch INTER_FREQ_HO_CA
PB_IND_OPT_SW
option be selected.
Freq Priority NRCellMobilityCon- Set this parameter to

Inter-Freq HO fig.FreqPriInterFHoRetryIntvl its recommended
Retry Intvl value.

Measurement fig.InterFreqMeasWaitTime its recommended
Wait Time value.
Traffic Priority gNBFreqPriorityGroup.TrafficPriority Set this parameter

plan.
Freq Priority gNBRfspConfig.FreqPriHoA1A2RsrpT Set this parameter

HO A1A2 hldOfs based on the network
RSRP Thld plan.
Offset
Neighboring NRCellAlgoSwitch.NCellInfoCtrlSwitc The

Cell h INTER_FREQ_UL_INT
Information RF_SW option
Control specifies whether to
Switch enable subscription to
uplink interference
information about
inter-frequency
neighboring cells.
its recommended
value.


ADD NRCELLFREQRELATION: NrCellId=0, SsbFreqPos=8000, FrequencyBand=N77,

(2021-12-30)
5G RAN
SubcarrierSpacing=30KHZ, TrafficPriority=1, SsbDescMethod=SSB_DESC_TYPE_GSCN;

//Activating frequency-priority-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=FREQ_PRIORITY_BASED_HO-1;
//Activating RFSP-specific frequency-priority-based inter-frequency handover (Note that the RFSP-based NR
inter-frequency handover policy must have been activated.)
MOD NRCELLALGOSWITCH: NrCellId=0, RfspAlgoSwitch=INTER_FREQ_LIST_CTRL_SW-1;
MOD NRCELLALGOSWITCH: NrCellId=0, RfspAlgoSwitch=FREQ_PRIORITY_BASED_HO_SW-1;

ADD NRCELLFREQRELATION: NrCellId=0, SsbFreqPos=4625, FrequencyBand=N3, SubcarrierSpacing=15KHZ,
TrafficPriority=1, SsbDescMethod=SSB_DESC_TYPE_GSCN;
//Activating frequency-priority-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=FREQ_PRIORITY_BASED_HO-1;
//Activating RFSP-specific frequency-priority-based inter-frequency handover (Note that the RFSP-based NR
inter-frequency handover policy must have been activated.)
MOD NRCELLALGOSWITCH: NrCellId=0, RfspAlgoSwitch=INTER_FREQ_LIST_CTRL_SW-1;

InterFreqA1A2Hyst=2, FreqPriInterFA2RsrpThld=-89, FreqPriInterFA1RsrpThld=-86,
FreqPriInterFA4RsrpThld=-104;
MOD NRCELLQCIBEARER: NrCellId=0, Qci=1, InterFreqHoMeasGroupId=0;
//Configuring the type of measurement event for unnecessary inter-frequency handovers (event A5 as an
example)
MOD NRCELLMOBILITYCONFIG: NrCellId=0, InterFreqMeasEventConfig=EVENT_A5;
//Modifying the retry period for frequency-priority-based inter-frequency handover
MOD NRCELLMOBILITYCONFIG: NrCellId=0, FreqPriInterFHoRetryIntvl=S60;

(2021-12-30)
5G RAN
//Modifying the inter-frequency measurement waiting time

MOD NRCELLMOBILITYCONFIG: NrCellId=0, InterFreqMeasWaitTime=6;
//(Recommended) Turning on the inter-frequency handover collaboration switch if frequency-priority-based
inter-frequency handover is enabled for the serving cell while either MLB by transferring UEs in connected
mode between inter-frequency cells or voice-quality-based inter-frequency handover is also enabled
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=INTER_FREQ_HO_COLLABORATION_SW-1;
//(Recommended) Turning on the switch for subscription to uplink interference information about inter-
frequency neighboring cells for the serving cell if frequency-priority-based inter-frequency handover is
enabled for the serving cell and uplink-interference-based inter-frequency handover is enabled for the
target cell
MOD NRCELLALGOSWITCH: NrCellId=0, NCellInfoCtrlSwitch=INTER_FREQ_UL_INTRF_SW-1;
//Configuring parameters related to RFSP-specific frequency-priority-based inter-frequency handover
//Configuring a frequency priority group and the traffic priority of an NR frequency in the frequency priority
group
ADD GNBFREQPRIORITYGROUP: gNBFreqPriorityGroupId=0, FreqIndex=2, RatType=NR, SsbFreqPos=26639,
TrafficPriority=1;
TrafficPriority=2;
//Binding an RFSP index to the configured frequency priority group
ADD GNBRFSPCONFIG: OperatorId=0, RfspIndex=2, gNBFreqPriorityGroupId=0;
//Modifying the A1 or A2 RSRP threshold offset for RFSP-specific frequency-priority-based handover
MOD GNBRFSPCONFIG: OperatorId=0, RfspIndex=2, FreqPriHoA1A2RsrpThldOfs=-10;

example)
//Modifying the retry period for frequency-priority-based inter-frequency handover
MOD NRCELLMOBILITYCONFIG: NrCellId=0, FreqPriInterFHoRetryIntvl=S60;
//Modifying the inter-frequency measurement waiting time
MOD NRCELLMOBILITYCONFIG: NrCellId=0, InterFreqMeasWaitTime=6;
//(Recommended) Turning on the inter-frequency handover collaboration switch if frequency-priority-based
inter-frequency handover is enabled for the serving cell while either MLB by transferring UEs in connected
mode between inter-frequency cells or voice-quality-based inter-frequency handover is also enabled
target cell
//Configuring parameters related to RFSP-specific frequency-priority-based inter-frequency handover
//Configuring the frequency priority group and the traffic priority of an NR frequency in the frequency
priority group
TrafficPriority=1;
TrafficPriority=2;
//Binding an RFSP index to the configured frequency priority group
ADD GNBRFSPCONFIG: OperatorId=0, RfspIndex=2, gNBFreqPriorityGroupId=0;

(2021-12-30)
5G RAN
//Modifying the A1 or A2 RSRP threshold offset for RFSP-specific frequency-priority-based handover

MOD GNBRFSPCONFIG: OperatorId=0, RfspIndex=2, FreqPriHoA1A2RsrpThldOfs=-10;

conditions.

//Deactivating frequency-priority-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0,InterFreqHoSwitch=FREQ_PRIORITY_BASED_HO-0;
//Deactivating RFSP-specific frequency-priority-based inter-frequency handover

//Deactivating frequency-priority-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0,InterFreqHoSwitch=FREQ_PRIORITY_BASED_HO-0;
//Deactivating RFSP-specific frequency-priority-based inter-frequency handover


If any of the following counters have a value other than 0, frequency-priority-
based inter-frequency handover has taken effect:
● N.HO.InterFreq.FreqPri.PrepAttOut
● N.HO.InterFreq.FreqPri.ExecAttOut
● N.HO.InterFreq.FreqPri.ExecSuccOut


This function can be monitored using the Inter-Frequency Handover Out Success
Rate (CU) KPI.

(2021-12-30)
5G RAN
4.5 Operator-specific-Priority-based Inter-Frequency

Handover
In network sharing scenarios, operator-specific-priority-based inter-frequency
handover allows the priority of a frequency to vary among operators, achieving
networking flexibility. As shown in Figure 4-10, cells 1 and 2 are shared by
operators. The frequency of cell 1 has a higher priority for operator A, whereas the
frequency of cell 2 has a higher priority for operator B. This function transfers each
operator's UEs to cells on the higher-priority frequency of that operator.
Figure 4-10 Operator-specific-priority-based inter-frequency handover in network

sharing scenarios
4.5.1 Principles
Figure 4-11 shows the procedure of operator-specific-priority-based inter-
frequency handover. This section describes the differences between this function
and the basic handover functions presented in 4.1 Basic Functions of Mobility
Management in Connected Mode.

(2021-12-30)
5G RAN
Figure 4-11 Operator-specific-priority-based inter-frequency handover

Operator-specific-priority-based inter-frequency handover supports only the
● The OP_DED_PRI_BASED_HO option of the
● A UE accesses, is handed over to, or has its RRC connection reestablished in a
cell whose NR frequency is not an operator-desired target frequency.
A frequency for which the gNBFreqPriorityGroup.ConnDedFreqPriority
parameter associated with the NRCellOPPolicy MO is set to a value other
than 0 is an operator-desired target frequency. Frequency priority policies can

(2021-12-30)
5G RAN
vary among operators. The base station determines which operator's

frequency priority policy is applied to a UE based on the UE's PLMN
information.

After operator-specific-priority-based inter-frequency handover is started, the
gNodeB selects frequencies for which the dedicated frequency priority in
connected mode is not 0 and then sends related measurement configurations.
quality of a neighboring cell exceeds a specific threshold) related to operator-
specific-priority-based inter-frequency measurements.
neighboring cell exceeds threshold 2) related to operator-specific-priority-
Following are required parameters:
● The dedicated frequency priority in connected mode is specified by the
gNBFreqPriorityGroup.ConnDedFreqPriority parameter associated with the
NRCellOPPolicy MO.
● The threshold for event A4 related to operator-specific-priority-based
measurements is specified by the
NRCellInterFHoMeaGrp.OpDedPriHoA4RsrpThld parameter. For details, see
Table 4-8.
● Threshold 2 for event A5 related to operator-specific-priority-based
measurements is specified by the
NRCellInterFHoMeaGrp.OpDedPriHoA4RsrpThld parameter. For details, see
Table 4-9.
If no neighboring cell is reported 6s after the operator-specific-priority-based
measurement of event A4 or A5 has started, the gNodeB releases the
measurement configuration, enabling the UE to stop measurements for this event
A4 or A5. In this scenario, if the UE is always in connected mode, the gNodeB no
longer sends the same measurement configuration.
A UE performs measurements based on the event indicated in the measurement
configuration and reports the event based on the measurement results. If event A4
(indicating the signal quality of a neighboring cell exceeds a specific threshold) or
A5 (indicating the signal quality of the serving cell drops below threshold 1 and
the signal quality of a neighboring cell exceeds threshold 2) related to operator-
specific-priority-based measurements is reported, the gNodeB determines the
target cells or frequencies based on the measurement report.

After the gNodeB receives a measurement report of event A4 (indicating that the
signal quality of a neighboring cell exceeds a specific threshold) or A5 (indicating

(2021-12-30)
5G RAN
that the signal quality of the serving cell drops below threshold 1 and the signal
quality of a neighboring cell exceeds threshold 2) related to operator-specific-
priority-based measurements, the gNodeB selects the best cell from the reported
cells as the target cell for handover execution.
Wherein:
When the function of subscription to uplink interference information about inter-
frequency neighboring cells is enabled (by selecting the
station neighboring cells, based on which the serving cell determines whether to
instruct the UE to initiate a handover. Specifically, the UE is instructed to do so if
the serving cell determines that the target cell is exposed to low uplink
interference. Otherwise, the UE is not instructed to perform a handover.
NOTE
For details about how the serving cell determines whether a neighboring cell is exposed to
low uplink interference, see Target Cell or Frequency Decision.
If operator-specific-priority-based inter-frequency handover is enabled for the serving cell
and uplink-interference-based inter-frequency handover is enabled for the target cell, you
are advised to enable the function of subscription to uplink interference information about
inter-frequency neighboring cells for the serving cell, avoiding ping-pong handover.
When the inter-frequency handover collaboration function is enabled (by selecting

the INTER_FREQ_HO_COLLABORATION_SW option of the
NRCellAlgoSwitch.InterFreqHoSwitch parameter) for the serving cell, the serving
cell further determines whether to instruct the UE to initiate a handover as
follows: If the serving cell identifies that the target cell has entered the MLB state
through inter-cell load information exchange, the gNodeB does not instruct the UE
to perform a handover to the target cell, avoiding ping-pong handover.
NOTE
When operator-specific-priority-based inter-frequency handover is enabled for the serving

cell, you are advised to enable the inter-frequency handover collaboration function to avoid
ping-pong handover if MLB by transferring UEs in connected mode between inter-frequency
cells is enabled (by selecting the INTER_FREQ_CONNECTED_MLB_SW option of the
NRCellAlgoSwitch.MlbAlgoSwitch parameter) for the target cell.
For details about MLB by transferring UEs in connected mode, see Mobility Load Balancing.
4.5.2.1 Benefits
In network sharing scenarios, this function facilitates the transfer of each
operator's UEs to cells on the higher-priority frequency of that operator, providing
flexible networking for operators.

(2021-12-30)
5G RAN
4.5.2.2 Impacts
Network Impacts
operator-specific-priority-based inter-frequency handover and other handover
functions (such as frequency-priority-based inter-frequency handover) must
be considered to prevent ping-pong handovers and ensure user experience.
For details about networking requirements, see 4.5.3.4 Networking.
Function Impacts
Name Switch
FDD Intra-RAT AUTO_NR_FR ANR If operator-specific-priority-

Low- ANR EQ_RELATION based inter-frequency
freque _SW option of handover is disabled, intra-
ncy the RAT ANR will not be
TDD NRCellAlgoS triggered by operator-
witch.AnrSwit specific-priority-based inter-
High- ch parameter frequency handover
freque because such handover
ncy does not take effect.
TDD
FDD Policy of BACK_TO_HP Flexible When both the policy of

Low- RFSP- LMN_INTER_F User RFSP-based inter-frequency
freque based REQ_HO_SW Steering handover back to the
ncy Inter- option of the HPLMN function and the
TDD Frequency NRCellAlgoS operator-specific-priority-
Handover witch.RfspAlg based inter-frequency
High- Back to oSwitch handover function are
freque the parameter enabled, only the policy of
ncy HPLMN RFSP-based inter-frequency
TDD handover back to the
HPLMN function, not the
operator-specific-priority-
handover function, can be
triggered for a roaming UE.
4.5.3 Requirements

(2021-12-30)
5G RAN
4.5.3.1 Licenses
4.5.3.2 Software
None

None
4.5.3.3 Hardware
Base Station Models

with the BBU3910.
Boards
RF Modules
Documentation.
4.5.3.4 Networking
over from cell 1 to cell 2 through an operator-specific-priority-based inter-
frequency handover, the UE is handed over from cell 2 back to cell 1 through
an operator-specific-priority-based inter-frequency handover.
over from cell 1 to cell 2 through an operator-specific-priority-based inter-

(2021-12-30)
5G RAN
frequency handover, the UE is handed over from cell 2 back to cell 1 through
a frequency-priority-based handover.
from cell 1 to cell 2 through an operator-specific-priority-based inter-
frequency handover, then from cell 2 to cell 3 through a service-based inter-
frequency handover, and finally from cell 3 to cell 1 through a frequency-
priority-based handover.
4.5.3.5 Others
interface.
interface.
interface.
V16.1.0.

(2021-12-30)
5G RAN

FR2 handover.
handoverInterF IE.

The NR cell's frequency relationships (Table 4-22), neighbor relationships (Table
4-12), frequency priorities (Table 4-23), and the NR cell's operator-specific
policies (Table 4-24) must be configured before this function is activated.

Name

plan.

Position plan.

Position value.
Describe
Method

plan.

(2021-12-30)
5G RAN

Name

plan.
Table 4-23 Parameters used to configure frequency priority groups of the gNodeB
Name
gNodeB gNBFreqPriorityGroup.gNBFreqPriori Set this parameter

Frequency tyGroupId based on the network
Priority Group plan.
ID
Frequency gNBFreqPriorityGroup.FreqIndex Set this parameter

Index based on the network
plan.
RAT Type gNBFreqPriorityGroup.RatType Set this parameter

plan.
SSB gNBFreqPriorityGroup.SsbFreqPos Set this parameter

Position plan.
Dedicated gNBFreqPriorityGroup.ConnDedFreq Set this parameter

Freq Priority Priority based on the network
for Connected plan.
Mode
Table 4-24 Parameters used to configure operator-specific policies for NR cells

Name
NR Cell ID NRCellOpPolicy.NrCellId Set this parameter

plan.
Operator ID NRCellOpPolicy.OperatorId Set this parameter

plan.
gNodeB NRCellOpPolicy.gNBFreqPriority- Set this parameter

Frequency GroupId based on the network
Priority Group plan.
ID

(2021-12-30)
5G RAN

Name
Inter- NRCellAlgoSwitch.InterFreqHoSwitc The

Frequency h OP_DED_PRI_BASED_
Handover HO option determines
Switch whether to enable
operator-specific-
frequency handover.
Set this parameter
plan.
Inter- NRCellAlgoSwitch.InterFreqHoSwitc To enable operator-

Frequency h specific-priority-based
Handover inter-frequency
Switch handover, it is
recommended that
the
INTER_FREQ_HO_CO
LLABORATION_SW
option be selected
when either MLB by
transferring UEs in
connected mode
between inter-
frequency cells or
voice-quality-based
inter-frequency
handover is also
enabled.
Table 4-26 Other related parameters

Name
NR Cell ID NRCellInterFHoMeaGrp.NrCellId Set this parameter

plan.

Measurement plan.
Group ID

(2021-12-30)
5G RAN

Name

Event value.
Configuration

Trigger

Event value.
Hysteresis
Operator Ded NRCellInterFHoMeaGrp.OpDedPriHo This parameter

Pri Inter-freq A4RsrpThld indicates the RSRP
HO A4 RSRP threshold for event A4
Thld related to operator-
specific-priority-based
inter-frequency
handover and RSRP
A5 related to
operator-specific-
frequency handover.
its recommended
value.

plan.

Measurement plan.
Group ID

Measurement plan.
Group ID

plan.

plan.

(2021-12-30)
5G RAN

Name

PB_IND_OPT_SW
option be selected.

uplink interference
information about
inter-frequency
neighboring cells.
its recommended
value.


FrequencyBand=N77, SubcarrierSpacing=30KHZ, TrafficPriority=0;
NrNetworkingOption=UNLIMITED;
//Adding a record to the NR external-cell PLMN list
//Adding a gNodeB frequency priority group
CellReselPri=1, CellReselSubPri=0DOT2, ConnDedFreqPriority=1;
//Configuring an operator-specific policy for an NR cell
ADD NRCELLOPPOLICY: NrCellId=1, OperatorId=1, gNBFreqPriorityGroupId=1;
//Activating operator-specific-priority-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=OP_DED_PRI_BASED_HO-1;


(2021-12-30)
5G RAN

//Adding a record to the NR external-cell PLMN list
//Adding a gNodeB frequency priority group
//Configuring an operator-specific policy for an NR cell
ADD NRCELLOPPOLICY: NrCellId=1, OperatorId=1, gNBFreqPriorityGroupId=1;
//Activating operator-specific-priority-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=OP_DED_PRI_BASED_HO-1;

InterFreqA4A5TimeToTrig=320MS, InterFreqA4A5Hyst=2, OpDedPriHoA4RsrpThld=-104;
example)
//(Recommended) Turning on the inter-frequency handover collaboration switch if operator-specific-priority-
based inter-frequency handover is enabled for the serving cell while either MLB by transferring UEs in
connected mode between inter-frequency cells or voice-quality-based inter-frequency handover is also
enabled
frequency neighboring cells for the serving cell if operator-specific-priority-based inter-frequency handover
is enabled for the serving cell and uplink-interference-based inter-frequency handover is enabled for the
target cell


(2021-12-30)
5G RAN

example)
//(Recommended) Turning on the inter-frequency handover collaboration switch if operator-specific-priority-
enabled
target cell

conditions.
//Deactivating operator-specific-priority-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0,InterFreqHoSwitch=OP_DED_PRI_BASED_HO-0;

//Deactivating operator-specific-priority-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0,InterFreqHoSwitch=OP_DED_PRI_BASED_HO-0;


If any of the following counters have a value other than 0, operator-specific-
priority-based inter-frequency handover has taken effect:
● N.HO.InterFreq.OpDedPri.PrepAttOut
● N.HO.InterFreq.OpDedPri.ExecAttOut
● N.HO.InterFreq.OpDedPri.ExecSuccOut

(2021-12-30)
5G RAN

Rate (CU) KPI.
4.6 Service-based Inter-Frequency Handover

In multi-frequency networking scenarios, service-based inter-frequency handover
allows services with different QCIs to be carried on different frequencies, achieving
flexible networking and service steering, as shown in Figure 4-12.
NOTE
In SA networking, the 5G Core Network (5GC) notifies the gNodeB of the 5QI
corresponding to each QoS flow. For detailed description about QCI and 5QI, see QoS
Management.
Figure 4-12 Service-based inter-frequency handover
4.6.1 Principles
With service-based inter-frequency handover, a target frequency group for
handover can be configured for each QCI. After service-based inter-frequency
handover is enabled, the gNodeB continuously monitors a UE's service status. If
the UE's QCI changes, the gNodeB sends the measurement configuration for the
specified frequency group to the UE, which then performs inter-frequency
measurement accordingly. After receiving a measurement report from the UE, the
gNodeB determines the optimal candidate target cell for handover execution. This
handover function does not apply to the blind mode. Figure 4-13 shows the
procedure of service-based inter-frequency handover. This section describes the
differences between this function and the basic handover functions presented in
4.1 Basic Functions of Mobility Management in Connected Mode.

(2021-12-30)
5G RAN
Figure 4-13 Procedure of service-based inter-frequency handover

If a UE initiates a service with a QCI that has the highest priority, this function is
initiated when all the following conditions are met:
● The SERVICE_BASED_HO option of the
● The gNBQciBearer.SrvInterFHoPriJudgeFlag parameter is set to TRUE,
indicating that the base station checks the priority of a QoS flow when
deciding whether to start a service-based inter-frequency handover.
● The QCI is associated with a target frequency group. That is, the ID of the
frequency group for service-based inter-frequency handover associated with
gNBOperatorQciParam.gNBSrvInterFHoFreqGroupId is not 255.

(2021-12-30)
5G RAN
● The serving frequency of the UE is not within the target frequency range
desired for the service. That is, the serving frequency is not contained in the
frequency group specified by the gNBSrvInterHoFreqGrp MO associated with
this QCI.
NOTE
For details about the priority configuration for each QCI, see QoS Management.

After service-based inter-frequency handover is started, the gNodeB selects the
target frequencies for service-based inter-frequency handover and sends related
measurement configurations.
quality of a neighboring cell exceeds a specific threshold) related to service-
neighboring cell exceeds threshold 2) related to service-based inter-frequency
measurements.
Following are required parameters:
● The frequencies included in the measurement configurations are determined
by the gNBSrvInterHoFreqGrp MO associated with the
gNBOperatorQciParam.gNBSrvInterFHoFreqGroupId value for the QCI, and
the number of frequencies to be delivered is subject to the maximum number
allowed for delivery.
● The threshold for service-based event A4 is specified by the
NRCellInterFHoMeaGrp.SrvInterFreqA4RsrpThld parameter. For details, see
Table 4-8.
● Threshold 2 for service-based event A5 is specified by the
NRCellInterFHoMeaGrp.SrvInterFreqA4RsrpThld parameter. For details, see
Table 4-9.
The UE performs measurements based on the event configuration included in the
measurement configuration. If neighboring cells that meet the requirements are
detected, a measurement report is sent to the gNodeB, which then uses the report
to determine the target cells or frequencies.
If no neighboring cell is reported 6s after the measurement of event A4 or A5
related to service-based inter-frequency handover has started, the gNodeB
releases the measurement configuration, enabling the UE to stop measurements
for this event A4 or A5. In this scenario, if the UE is always in connected mode, the
gNodeB no longer sends the same measurement configuration.

After the gNodeB receives a measurement report of event A4 (indicating that the
signal quality of a neighboring cell exceeds a specific threshold) or A5 (indicating

(2021-12-30)
5G RAN
that the signal quality of the serving cell drops below threshold 1 and the signal
quality of a neighboring cell exceeds threshold 2) related to service-based inter-
frequency handover, the gNodeB selects the best cell from the reported cells as
the target cell for handover execution.
Wherein:
NOTE
If service-based inter-frequency handover is enabled for the serving cell and uplink-
interference-based inter-frequency handover is enabled for the target cell, you are advised
to enable the function of subscription to uplink interference information about inter-
frequency neighboring cells for the serving cell, avoiding ping-pong handover.

cell further determines whether to instruct the UE to initiate a handover as
NOTE
When service-based inter-frequency handover is enabled for the serving cell, you are
advised to enable the inter-frequency handover collaboration function to avoid ping-pong
handover if MLB by transferring UEs in connected mode between inter-frequency cells is
enabled (by selecting the INTER_FREQ_CONNECTED_MLB_SW option of the
4.6.2.1 Benefits
This function provides a method for handing over UEs based on services and
allows flexible networking, thereby helping operators implement service steering.
4.6.2.2 Impacts
Network Impacts

(2021-12-30)
5G RAN
service-based inter-frequency handover and other handover functions (such
as frequency-priority-based inter-frequency handover) must be considered to
prevent ping-pong handovers and ensure user experience. For details about
networking requirements, see 4.6.3.4 Networking.
Function Impacts
Name Switch
FDD Intra-RAT AUTO_NR_FR ANR If service-based inter-

Low- ANR EQ_RELATION frequency handover is
ncy the not be triggered by service-
TDD NRCellAlgoS based inter-frequency
witch.AnrSwit handover because such
High- ch parameter handover does not take
freque effect.
ncy
TDD
FDD UE- INTER_FREQ_ Mobility If both UE-number-based

Low- number- CONNECTED_ Load connected mode MLB and
freque based MLB_SW Balancing service-based inter-
ncy connected option of the frequency handover are
TDD mode MLB NRCellAlgoS enabled, the following are
witch.MlbAlg true: If a target cell rejects
oSwitch MLB-based handovers from
parameter a source cell, the source cell
initiate service-based inter-
frequency handovers to the
target cell in a short period
of time. The reverse is also
applicable.

(2021-12-30)
5G RAN

Name Switch
FDD Spectral- INTER_FREQ_ Mobility If both spectral-efficiency-

Low- efficiency- CONNECTED_ Load based connected mode MLB
freque based MLB_SW Balancing and service-based inter-
ncy connected option of the frequency handover are
TDD mode MLB NRCellAlgoS enabled, the following are
witch.MlbAlg true: If a target cell rejects
oSwitch MLB-based handovers from
parameter a source cell, the source cell
initiate service-based inter-
frequency handovers to the
target cell in a short period
of time. The reverse is also
applicable.
4.6.3 Requirements
4.6.3.1 Licenses
4.6.3.2 Software
None

None
4.6.3.3 Hardware
Base Station Models

with the BBU3910.
Boards

(2021-12-30)
5G RAN
RF Modules
Documentation.
4.6.3.4 Networking
over from cell 1 to cell 2 through a service-based inter-frequency handover,
the UE is handed over from cell 2 back to cell 1 through a service-based inter-
frequency handover.
over from cell 1 to cell 2 through a service-based inter-frequency handover,
the UE is handed over from cell 2 back to cell 1 through a frequency-priority-
based handover.
handover.
4.6.3.5 Others
interface.
interface.
interface.

(2021-12-30)
5G RAN


V16.1.0.
FR2 handover.
handoverInterF IE.

The NR cell's frequency relationships (Table 4-27), neighbor relationships (Table
4-12), frequency priorities (Table 4-28), and the NR cell's operator-specific
policies (Table 4-29) must be configured before this function is activated.

(2021-12-30)
5G RAN

Name

plan.

Position plan.

Position value.
Describe
Method

plan.

plan.
Table 4-28 Parameters used to configure frequency groups for service-based inter-
frequency handover
Name
gNodeB Srv- gNBSrvInterHoFreqGrp.gNBSrvInterF Set this parameter

Based Inter- HoFreqGroupId based on the network
Freq HO Freq plan.
Group ID
SSB gNBSrvInterHoFreqGrp.SsbFreqIndex Set this parameter

Index plan.
SSB gNBSrvInterHoFreqGrp.SsbDescMeth Set this parameter

Frequency od based on the network
Position plan.
Describe
Method
SSB gNBSrvInterHoFreqGrp.SsbFreqPos Set this parameter

Position plan.

(2021-12-30)
5G RAN
Table 4-29 Parameters related to NR operator-specific QCI configurations

Name
Operator ID gNBOperatorQciParam.OperatorId Set this parameter

plan.
QoS Class gNBOperatorQciParam.Qci Set this parameter

plan.
gNodeB Srv- gNBOperatorQciPar- Set this parameter

Based Inter- am.gNBSrvInterFHoFreqGroupId based on the network
Freq HO Freq plan.
Group ID

Name

Frequency h SERVICE_BASED_HO
Handover option determines
service-based inter-
frequency handover.
Set this parameter
plan.
Inter- NRCellAlgoSwitch.InterFreqHoSwitc To enable service-

Frequency h based inter-frequency
Handover handover, it is
Switch recommended that
the
INTER_FREQ_HO_CO
LLABORATION_SW
option be selected
when either MLB by
transferring UEs in
connected mode
between inter-
frequency cells or
voice-quality-based
inter-frequency
handover is also
enabled.

(2021-12-30)
5G RAN

Name
Srv-Based gNBQciBearer.SrvInterFHoPriJudge- Set this parameter

Inter-Freq HO Flag based on the network
Priority Judge plan.
Flag

Event value.
Configuration

Measurement plan.
Group ID

Trigger

Event value.
Hysteresis
Srv-Based NRCellInterFHoMeaGrp.SrvInterFreq This parameter

Inter-freq A4 A4RsrpThld indicates the RSRP
RSRP threshold for event A4
Threshold related to service-
handover and RSRP
handover.
its recommended
value.

plan.

Measurement plan.
Group ID

(2021-12-30)
5G RAN

Name

Measurement plan.
Group ID

plan.

plan.

PB_IND_OPT_SW
option be selected.

uplink interference
information about
inter-frequency
neighboring cells.
its recommended
value.


//(Optional) Adding a record to the NR external-cell PLMN list in RAN sharing with common carrier mode

(2021-12-30)
5G RAN

//Configuring a frequency group for service-based inter-frequency handover
ADD GNBSRVINTERHOFREQGRP: gNBSrvInterFHoFreqGroupId=1, SsbFreqIndex=0, SsbFreqPos=8000,
SsbDescMethod=SSB_DESC_TYPE_GSCN;
//Configuring operator-specific QCI parameters (QCI 1 used as an example)
MOD GNBOPERATORQCIPARAM: OperatorId=1, Qci=1, gNBSrvInterFHoFreqGroupId=1;
//Activating service-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=SERVICE_BASED_HO-1;

//Configuring a frequency group for service-based inter-frequency handover
ADD GNBSRVINTERHOFREQGRP: gNBSrvInterFHoFreqGroupId=1, SsbFreqIndex=1, SsbFreqPos=4625,
SsbDescMethod=SSB_DESC_TYPE_GSCN;
//Configuring operator-specific QCI parameters (QCI 1 used as an example)
MOD GNBOPERATORQCIPARAM: OperatorId=1, Qci=1, gNBSrvInterFHoFreqGroupId=1;
//Activating service-based inter-frequency handover

InterFreqA4A5TimeToTrig=320MS, InterFreqA4A5Hyst=2, SrvInterFreqA4RsrpThld=-104;
example)
//Reconfiguring Srv-Based Inter-Freq HO Priority Judge Flag
MOD GNBQCIBEARER: Qci=1, SrvInterFHoPriJudgeFlag=TRUE;
//(Recommended) Turning on the inter-frequency handover collaboration switch if service-based inter-
frequency handover is enabled for the serving cell while either MLB by transferring UEs in connected mode
between inter-frequency cells or voice-quality-based inter-frequency handover is also enabled
frequency neighboring cells for the serving cell if service-based inter-frequency handover is enabled for the
serving cell and uplink-interference-based inter-frequency handover is enabled for the target cell


(2021-12-30)
5G RAN

example)
//Reconfiguring Srv-Based Inter-Freq HO Priority Judge Flag
MOD GNBQCIBEARER: Qci=1, SrvInterFHoPriJudgeFlag=TRUE;
//(Recommended) Turning on the inter-frequency handover collaboration switch if service-based inter-
frequency neighboring cells for the serving cell if service-based inter-frequency handover is enabled for the
serving cell and uplink-interference-based inter-frequency handover is enabled for the target cell

conditions.
//Deactivating service-based inter-frequency handover

//Deactivating service-based inter-frequency handover


If any of the following counters have a value other than 0, service-based inter-
● N.HO.InterFreq.Service.PrepAttOut
● N.HO.InterFreq.Service.ExecAttOut
● N.HO.InterFreq.Service.ExecSuccOut

(2021-12-30)
5G RAN


Rate (CU) KPI.
4.7 Uplink-Interference-based Inter-Frequency

Handover
In multi-frequency networking, if a frequency has uplink interference, the uplink
user experience on this frequency will be affected. In this case, uplink-interference-
based inter-frequency handovers can be performed to hand over UEs from the
serving cell to inter-frequency neighboring cells, ensuring the uplink user
experience (Figure 4-14). Currently, supported inter-frequency handovers include
inter-frequency intra-FR1 FDD/intra-FR1 TDD/FR1 FDD-FR1 TDD handovers.
Figure 4-14 Uplink-interference-based inter-frequency handover
4.7.1 Principles
The gNodeB determines whether to start uplink-interference-based inter-
frequency handover based on the strength of uplink interference in the serving
cell. Specifically, if the uplink interference strength is greater than a specified
threshold, the gNodeB sends inter-frequency measurement configurations to low-
SRS-SINR UEs performing large packet services in the serving cell's uplink. The UEs
then perform inter-frequency measurements. After receiving measurement reports
from the UEs, the gNodeB determines the optimal candidate target cells for
handover execution. This function does not apply to the blind mode. Figure 4-15
shows how uplink-interference-based inter-frequency handover works. This section
describes the differences between this function and the basic handover functions
presented in 4.1 Basic Functions of Mobility Management in Connected Mode.

(2021-12-30)
5G RAN
Figure 4-15 Procedure for uplink-interference-based inter-frequency handover

Uplink-interference-based inter-frequency handover supports only the
● The switch for uplink-interference-based inter-frequency handover is turned
on.
– In SA networking, the UL_INTRF_BASED_HO option of the
NRCellAlgoSwitch.InterFreqHoSwitch parameter has been selected.
– In NSA networking, the UL_INTRF_BASED_HO and
NSA_UL_INTRF_BASED_HO options of the
NRCellAlgoSwitch.InterFreqHoSwitch parameter are both selected.

(2021-12-30)
5G RAN
● The strength of uplink interference in the serving cell is greater than the
uplink interference threshold (specified by the
NRDUCellIntrfIdent.UlIntrfThld parameter).

After uplink-interference-based inter-frequency handover is started, the gNodeB
sends measurement configuration to a UE when the UE in the serving cell meets
all of the following conditions:
● The UE has a low SRS SINR (less than the threshold specified by
NRDUCellIntrfIdent.SrsSinrThld).
● The UE is transmitting large packets in the uplink. This is the case when all of
the following conditions are met:
– Amount of data in the uplink data buffer (indicated in the buffer status
report, also known as BSR) sent by the UE to the scheduler + Amount of
uplink data already sent by the UE > 4 MB
– Proportion of TTIs in which the UE is scheduled in the uplink within 1s
(Number of TTIs in which the UE is scheduled in the uplink within 1s/
Number of TTIs in the uplink in the cell within 1s) ≥ 80%
– Uplink PRB usage of the UE ≥ 30%
Measurement configurations include the target frequencies for uplink-
interference-based inter-frequency handovers and the corresponding event A3
configuration.
● Target frequencies for uplink-interference-based inter-frequency handovers:
The frequencies included in the measurement configurations are those for
which the interference-based frequency priority (specified by
NRCellFreqRelation.IntrfFreqPriority) is set to a value other than 0, and the
number of frequencies to be sent is subject to the maximum allowed number
for sending.
● Event A3 related to uplink-interference-based inter-frequency handovers: The
RSRP offset for event A3 is specified by the
NRCellInterFHoMeaGrp.IntrfInterFreqHoA3RsrpOfs parameter.
After receiving the measurement configuration from the gNodeB, the UE performs
measurements in descending order of interference-based frequency priority
(specified by NRCellFreqRelation.IntrfFreqPriority). If the UE detects a
neighboring cell that meets the specific requirements, it reports the measurement
result to the gNodeB and stops measurements for this event A3. The gNodeB then
determines the target cells or frequencies based on the measurement report.
If no neighboring cell is reported 6s after the measurement of event A3 related to
uplink-interference-based inter-frequency handover has started, the gNodeB
releases the measurement configuration, enabling the UE to stop measurements
for this event A3. To prevent the UE from experiencing continued failures in
outgoing handovers from the serving cell, cell-level supplementary selection in
polling mode is performed. Specifically, the gNodeB periodically (at a fixed
interval of 30s) selects a maximum of five low-SRS-SINR UEs performing large
packet services in the serving cell's uplink in polling mode and sends measurement

(2021-12-30)
5G RAN
configurations to them, enabling them to start measurements for uplink-

interference-based inter-frequency handover.

When receiving an event A3 (indicating that the signal quality of a neighboring
cell is higher than that of the serving cell by a certain offset) measurement report
related to uplink-interference-based inter-frequency handover, the gNodeB selects
the best cell from the reported cells as the target cell for handover execution. In
addition, the gNodeB determines whether to instruct the UE to perform a
handover to the target cell based on the information such as the target cell load,
uplink interference of the target cell, and bearers of the UE.
Before the gNodeB determines whether to instruct the UE to perform a handover
to the target cell, the serving cell needs to obtain the load or uplink interference
information about the target cell in the following ways:
● When a function of MLB by transferring UEs in connected mode (for example,
UE-number-based connected mode MLB) involving exchange of inter-cell load
and interference status information is enabled,
– the gNodeB triggers load information exchange between intra-base-
station cells by default, so that the serving cell obtains load and uplink
interference information about intra-base-station neighboring cells.
– if there are candidate inter-base-station neighboring cells, the gNodeB
triggers load information exchange between inter-base-station cells so
that the serving cell obtains load and uplink interference information
about inter-base-station neighboring cells.
● When the INTER_FREQ_UL_INTRF_SW option of the
NRCellAlgoSwitch.NCellInfoCtrlSwitch parameter is selected to enable the
subscription to uplink interference information about inter-frequency
neighboring cells,
– the serving cell can directly obtain uplink interference information about
intra-base-station neighboring cells.
– the serving cell can directly obtain uplink interference information about
inter-base-station neighboring cells if there are candidate inter-base-
station neighboring cells.
After the serving cell obtains load or uplink interference information about the
target cell, the gNodeB determines whether to instruct the UE to perform a
handover to the target cell based on the following conditions.
● If the serving cell obtains load and uplink interference information about the
target cell:
In the case that the RSRP value of the lightly-loaded, low-uplink-interference
target cell is greater than the value of
NRCellInterFHoMeaGrp.IntrfInterFreqHoRsrpThld, the UE will be handed
over to the target cell. Otherwise, the UE continues to camp on the serving
cell and handover is not performed.
Wherein,
– A neighboring cell is regarded as a low-uplink-interference cell when its
uplink interference strength is less than or equal to
NRDUCellIntrfIdent.UlIntrfThld.

(2021-12-30)
5G RAN
– A neighboring cell is regarded as a lightly-loaded cell when it does not

meet the conditions for entering the MLB state.
● If the serving cell obtains only uplink interference information about the
target cell:
In the case that the RSRP value of the low-uplink-interference target cell is
greater than the value of NRCellInterFHoMeaGrp.IntrfInterFreqHoRsrpThld,
the UE will be handed over to the target cell. Otherwise, the UE continues to
camp on the serving cell and handover is not performed.
In this case, a neighboring cell is regarded as a low-uplink-interference cell
when its uplink interference strength is less than or equal to
NRDUCellIntrfIdent.UlIntrfThld.
● If the serving cell does not obtain uplink interference information about the
target cell:
In the case that the RSRP value of the target cell is greater than the value of
NRCellInterFHoMeaGrp.IntrfInterFreqHoRsrpThld, the UE will be handed
over to the target cell. Otherwise, the UE continues to camp on the serving
cell and handover is not performed.
cell further determines whether to instruct the UE to perform a handover as
NOTE
When uplink-interference-based inter-frequency handover is enabled for the serving cell,

you are advised to enable the inter-frequency handover collaboration function to avoid
ping-pong handover if MLB by transferring UEs in connected mode between inter-frequency
cells is enabled (by selecting the INTER_FREQ_CONNECTED_MLB_SW option of the
4.7.2.1 Benefits
Uplink-interference-based inter-frequency handovers are performed to ensure
uplink user experience when the serving cell has strong uplink interference.
4.7.2.2 Impacts
Network Impacts
Uplink-interference-based inter-frequency handover results in the following
impacts on the network:

(2021-12-30)
5G RAN

uplink-interference-based inter-frequency handover and other handover
functions (such as frequency-priority-based inter-frequency handover) must
be considered to prevent ping-pong handovers and ensure user experience.
For details about networking requirements, see 4.7.3.4 Networking.
Function Impacts
Name Switch
FDD Protection UL_WEAK_CO Multi- In a multi-frequency

Low- of UEs V_UE_PROTEC Frequency network, ping-pong
freque under T_SW option Convergen handover may easily occur
ncy weak of the ce between a cell enabled with
TDD coverage NRCellAlgoS uplink-interference-based
in the witch.MultiFr inter-frequency handover
uplink eqAlgoSwitch and an inter-frequency cell
parameter enabled with protection of
UEs under weak coverage in
the uplink (controlled by
the
UL_WEAK_COV_UE_PROTE
CT_SW option of the
eqAlgoSwitch parameter).
As such, you are advised to
further select the
INTER_FREQ_UL_INTRF_S
W option of the
NRCellAlgoSwitch.NCellInf
oCtrlSwitch parameter, so
that handover to cells
exposed to high
interference is not triggered
during handover decision-
making.

freque
ncy
TDD
4.7.3 Requirements
4.7.3.1 Licenses
This function is not under license control.

(2021-12-30)
5G RAN
4.7.3.2 Software
None

RAT Function Function Switch Reference Description
Name
FDD LTE FDD LTE_NR_FDD_SPCT_ LTE FDD LTE FDD and NR Flash
and NR SHR_SW option of and NR Dynamic Spectrum
Flash the Spectrum Sharing is mutually
Dynamic NRDUCellAlgoSwitc Sharing exclusive with uplink-
Spectrum h.SpectrumCloudSw interference-based
Sharing itch parameter inter-frequency
handover.
Low- None None None None

freq
uenc
y
TDD
High
-
freq
uenc
y
TDD
4.7.3.3 Hardware
Base Station Models

● 3900 and 5900 series base stations. 3900 series base stations must be
● DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
Boards
RF Modules
All NR-capable RF modules that work in low frequency bands support this
function. For details, see the technical specifications of RF modules in 3900 & 5900
Series Base Station Product Documentation.

(2021-12-30)
5G RAN
4.7.3.4 Networking
over from cell 1 to cell 2 through an uplink-interference-based inter-frequency
handover, the UE is handed over from cell 2 back to cell 1 through an uplink-
interference-based inter-frequency handover.
over from cell 1 to cell 2 through an uplink-interference-based inter-frequency
handover, the UE is handed over from cell 2 back to cell 1 through a
frequency-priority-based handover.
handover.
4.7.3.5 Others
intra-FR1 TDD handover, and indicated by the handoverInterF IE in the
UECapabilityInformation message over the Uu interface.
interface.
Capabilities/fr1-Add-UE-NR-Capabilities IEs. For this reason, whether UEs support
inter-frequency handover is evaluated based on the value of handoverInterF in
those IEs. For details on evaluation based on handoverInterF/handoverFDD-TDD,
see section 4.2 "UE Capability Parameters" in 3GPP TS 38.306 V15.9.0.

(2021-12-30)
5G RAN

V16.1.0.
During evaluation of UE support for inter-frequency FDD-TDD handover, the
gNodeB first checks the handoverInterF IE to determine whether outgoing
handovers from the current cell are allowed. It then checks the handoverFDD-
TDD IE to determine whether UEs support inter-frequency FDD-TDD handover.
During evaluation of UE support for inter-frequency FDD-TDD handover, the
gNodeB directly checks the handoverFDD-TDD IE to determine whether UEs
support inter-frequency FDD-TDD handover, without first checking the
handoverInterF IE.

The NR cell's frequency relationships (including frequency priorities) and neighbor
relationships must be configured before this function is activated. For details
about the NR cell's frequency relationship configurations, see Table 4-32. For
details about neighbor relationship configurations, see Table 4-12.
Table 4-33 and Table 4-35 describe other parameters used for function
optimization.

Name

plan.

Position plan.

(2021-12-30)
5G RAN

Name

Position value.
Describe
Method

plan.

plan.
Intrf-based NRCellFreqRelation.IntrfFreqPriority Set this parameter

Priority plan.
Table 4-33 Parameters used to configure frequency groups for uplink-interference-

based inter-frequency handover
Name

Measurement plan.
Group ID
Intrf-based NRCellInterFHoMeaGrp.IntrfInterFre Set this parameter to

Inter-Freq HO qHoA3RsrpOfs its recommended
A3 RSRP value.
Offset
Intrf-based NRCellInterFHoMeaGrp.IntrfInterFre It is good practice to

Inter-Freq HO qHoRsrpThld set this parameter to
RSRP Thld a value greater than
the value of
NRCellInterFHoMeaG
rp.CovInterFreqA2Rsr
pThld to prevent
ping-pong with
coverage-based inter-
frequency handover.

plan.

(2021-12-30)
5G RAN

Name

Measurement plan.
Group ID

Measurement plan.
Group ID

plan.

plan.

Name
Inter- NRCellAlgoSwitch.InterFreqHoSwitc In SA networking,

Frequency h select the
Handover UL_INTRF_BASED_HO
Switch option to enable
uplink-interference-
handover.
In NSA networking,
select the
UL_INTRF_BASED_HO
and
NSA_UL_INTRF_BASE
D_HO options to
enable uplink-
interference-based
inter-frequency
handover.
Set this parameter
plan.

(2021-12-30)
5G RAN

Name
Inter- NRCellAlgoSwitch.InterFreqHoSwitc To enable uplink-

Frequency h interference-based
Handover inter-frequency
Switch handover, it is
recommended that
the
INTER_FREQ_HO_CO
LLABORATION_SW
option be selected
when either MLB by
transferring UEs in
connected mode
between inter-
frequency cells or
voice-quality-based
inter-frequency
handover is also
enabled.

Name
Uplink NRDUCellIntrfIdent.UlIntrfThld Set this parameter to

Interference its recommended
Threshold value.
SRS SINR NRDUCellIntrfIdent.SrsSinrThld Set this parameter to

Threshold its recommended
value.

uplink interference
information about
inter-frequency
neighboring cells.
its recommended
value.

(2021-12-30)
5G RAN

Before using MML commands, refer to 4.7.3.2 Software and complete the
parameter configurations for related functions based on the mutually exclusive
relationships between the functions, as well as the actual network scenario.

FrequencyBand=N77, SubcarrierSpacing=30KHZ, IntrfFreqPriority=16;
//Activating uplink-interference-based inter-frequency handover in SA networking
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=UL_INTRF_BASED_HO-1;
//Activating uplink-interference-based inter-frequency handover in NSA networking
MOD NRCELLALGOSWITCH: NrCellId=0,
InterFreqHoSwitch=UL_INTRF_BASED_HO-1&NSA_UL_INTRF_BASED_HO-1;

FrequencyBand=N3, SubcarrierSpacing=15KHZ, IntrfFreqPriority=16;
//Activating uplink-interference-based inter-frequency handover in SA networking
//Activating uplink-interference-based inter-frequency handover in NSA networking
MOD NRCELLALGOSWITCH: NrCellId=0,
InterFreqHoSwitch=UL_INTRF_BASED_HO-1&NSA_UL_INTRF_BASED_HO-1;

MOD NRCELLINTERFHOMEAGRP: NrCellId=0, InterFreqHoMeasGroupId=0, IntrfInterFreqHoA3RsrpOfs=3,
IntrfInterFreqHoRsrpThld=-104;

(2021-12-30)
5G RAN
//Turning on the switch for subscription to uplink interference information about inter-frequency
neighboring cells
//Modifying the interference identification configuration of the NR DU cell
MOD NRDUCELLINTRFIDENT: NrDuCellId=0, UlIntrfThld=-100, SrsSinrThld=-4;
//(Recommended) Turning on the inter-frequency handover collaboration switch if uplink-interference-
enabled

//Turning on the switch for subscription to uplink interference information about inter-frequency
neighboring cells
//Modifying the interference identification configuration of the NR DU cell
MOD NRDUCELLINTRFIDENT: NrDuCellId=0, UlIntrfThld=-100, SrsSinrThld=-4;
//(Recommended) Turning on the inter-frequency handover collaboration switch if uplink-interference-
enabled

conditions.

//Deactivating uplink-interference-based inter-frequency handover in SA networking
//Deactivating uplink-interference-based inter-frequency handover in NSA networking
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=NSA_UL_INTRF_BASED_HO-0;

//Deactivating uplink-interference-based inter-frequency handover in SA networking
//Deactivating uplink-interference-based inter-frequency handover in NSA networking
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=NSA_UL_INTRF_BASED_HO-0;


(2021-12-30)
5G RAN

If INTRF_BASED is displayed for HoCause in the external CHR event
PRIVATE_INTRA_RAT_HO_OUT, uplink-interference-based inter-frequency
handover has taken effect.

Rate (CU) KPI.
4.8 SSB SINR-based Inter-Frequency Handover

For LampSite base stations intended for high capacity scenarios, cell splitting can
be used to split a congested cell into multiple smaller cells for capacity expansion.
In traditional cell splitting networking as shown in Figure 4-16, cells on different
frequencies have the same cell center and similar cell edges. This means that user
experience at the cell edge is poor. Cell splitting heterogeneous networking is
recommended to meet high requirements on cell edge user experience. In this
networking, the cell centers of cells on different frequencies are staggered. That is,
the cell edge area of a cell on a frequency is aligned with the cell center area of a
cell on a different frequency.
Figure 4-16 Traditional cell splitting networking and cell splitting heterogeneous
networking
In cell splitting heterogeneous networking as shown in Figure 4-17, SSB SINR-

based inter-frequency handover can be used to hand over UEs from the edge of a
cell on a frequency to the center of another cell on a different frequency. This

(2021-12-30)
5G RAN
reduces interference between intra-frequency cells and improves user experience

and system capacity. SSB SINR-based inter-frequency handover is supported only
by LampSite base stations.
Figure 4-17 SSB SINR-based inter-frequency handover
4.8.1 Principles
Figure 4-18 shows the procedure for SSB SINR-based inter-frequency handover.
This section describes the differences between this function and the basic
handover functions presented in 4.1 Basic Functions of Mobility Management in
Connected Mode.

(2021-12-30)
5G RAN
Figure 4-18 Procedure of SSB SINR-based inter-frequency handover

SSB SINR-based inter-frequency handover supports only the measurement-based
mode, meaning this function does not support the blind mode. This function is
started when all of the following conditions are met:
● The SSB_SINR_BASED_HO option of the
● The gNodeB receives a measurement report indicating that the measured
SINR of a frequency (or cell) meets the entering conditions for event A2
related to inter-frequency measurements. Event A2 involves SSB SINR
measurements and the SINR threshold for event A2 is specified by the
NRCellInterFHoMeaGrp.SsbSinrInterFreqHoA2Thld parameter.

(2021-12-30)
5G RAN
see Table 4-6.

After SSB SINR-based inter-frequency handover is started, the gNodeB sends the
measurement configuration to instruct the UE to stop event A2 inter-frequency
measurements and the measurement configuration to instruct the UE to start
event A3 and event A1 inter-frequency measurements. Event A3 involves SSB RSRP
measurements, and event A1 involves SSB SINR measurements.
For details about the definitions, entering conditions, and leaving conditions for
events A3 and A1, see Measurement Event. For details about the variable
configurations for event A1, see Table 4-5.
● If event A3 related to inter-frequency measurements is reported, the gNodeB

determines the target cells or frequencies based on the measurement report.
If no neighboring cell is reported 6s after the event A3 inter-frequency
measurement has started, the gNodeB releases the measurement
configurations for events A3 and A1 related to inter-frequency measurements
to enable the UE to stop measurements for this event A3 and event A1, and
starts the SSB SINR-based inter-frequency handover penalty timer specified by
gNBMobilityCommParam.SsbSinrInterFHoPunishTimer.
Before the inter-frequency handover penalty timer expires, if the UE always
remains in the RRC_CONNECTED state, the gNodeB no longer sends
measurement configurations for event A2 related to inter-frequency
measurements. After the inter-frequency handover penalty timer expires, if
the UE always remains in the RRC_CONNECTED state, the gNodeB re-sends
measurement configurations for event A2 related to inter-frequency
measurements, and after SSB SINR-based inter-frequency handover is started,
the gNodeB sends measurement configurations for events A3 and A1 related
to inter-frequency measurements.
● If event A1 related to inter-frequency measurements is reported, the gNodeB
sends the measurement configuration to instruct the UE to stop event A3 and
event A1 inter-frequency measurements and the measurement configuration
to instruct the UE to restart event A2 inter-frequency measurements. This
means that the UE will stop measurements for this event A3 and event A1
and restart event A2 inter-frequency measurements.

After receiving event A3 related to inter-frequency measurements, the gNodeB
generates a target cell or frequency list based on the filtering rules described in
4.1.1.6 Target Cell or Frequency Decision and selects the best cell from the
reported cells as the target cell for handover execution.

(2021-12-30)
5G RAN
The following filtering rules, which are dedicated to the SSB SINR-based inter-
frequency handover function, are also considered: If this function (controlled by
the SSB_SINR_BASED_HO option of NRCellAlgoSwitch.InterFreqHoSwitch) is
enabled, and measurement-based inter-frequency handover (controlled by the
COVERAGE_BASED_HO option of NRCellAlgoSwitch.InterFreqHoSwitch) or
measurement-based inter-frequency redirection (controlled by the REDIRECTION
option of NRCellAlgoSwitch.InterFreqHoSwitch) is also enabled, the gNodeB
further filters out the following cells to generate a target cell or frequency list.
● If only RSRP is used as the triggering quantity for event A2 related to
coverage-based inter-frequency measurements, the gNodeB filters out the
cells whose RSRP is less than the result of
● If both RSRP and RSRQ are used as the triggering quantities for event A2
related to coverage-based inter-frequency measurements, the gNodeB filters
out the cells whose RSRP is less than the result of
NRCellInterFHoMeaGrp.InterFreqA1A2Hyst" and the cells whose RSRQ is
less than the result of "NRCellInterFHoMeaGrp.CovInterFreqA2RsrqThld –
NOTE
If SSB SINR-based inter-frequency handover is enabled for the serving cell and uplink-
interference-based inter-frequency handover is enabled for the target cell, you are advised
to enable the function of subscription to uplink interference information about inter-
frequency neighboring cells for the serving cell, avoiding ping-pong handover.

cell further determines whether to instruct the UE to perform a handover as

(2021-12-30)
5G RAN
NOTE
When SSB SINR-based inter-frequency handover is enabled for the serving cell, you are
advised to enable the inter-frequency handover collaboration function to avoid ping-pong
handover if MLB by transferring UEs in connected mode between inter-frequency cells is
enabled (by selecting the INTER_FREQ_CONNECTED_MLB_SW option of the
4.8.2.1 Benefits
In cell splitting heterogeneous networking, SSB SINR-based inter-frequency
handover reduces interference between intra-frequency cells and improves user
experience and system capacity.
4.8.2.2 Impacts
Network Impacts
● Networking of the existing network and the impact relationship between SSB
SINR-based inter-frequency handover and other handover functions (such as
frequency-priority-based inter-frequency handover) must be considered to
prevent ping-pong handovers and ensure user experience. For details about
networking requirements, see 4.8.3.4 Networking.
Function Impacts
Name Switch
FDD Intra-RAT AUTO_NR_FR ANR If SSB SINR-based inter-

Low- ANR EQ_RELATION frequency handover is
ncy the not be triggered by SSB
TDD NRCellAlgoS SINR-based inter-frequency
witch.AnrSwit handover because such
ch parameter handover does not take
effect.
4.8.3 Requirements

(2021-12-30)
5G RAN
4.8.3.1 Licenses
4.8.3.2 Software
None

None
4.8.3.3 Hardware
Base Station Models

Boards
RF Modules
4.8.3.4 Networking

over from cell 1 to cell 2 through an SSB SINR-based inter-frequency
handover, the UE is handed over from cell 2 back to cell 1 through an SSB
SINR-based inter-frequency handover.
over from cell 1 to cell 2 through an SSB SINR-based inter-frequency
handover, the UE is handed over from cell 2 back to cell 1 through a
frequency-priority-based handover.

(2021-12-30)
5G RAN

from cell 1 to cell 2 through an SSB SINR-based inter-frequency handover,
then from cell 2 to cell 3 through a service-based inter-frequency handover,
and finally from cell 3 to cell 1 through a frequency-priority-based handover.
4.8.3.5 Others
interface.
interface.
interface.
V16.1.0.

(2021-12-30)
5G RAN

FR2 handover.
handoverInterF IE.
To support SSB SINR-based inter-frequency handover, UEs must further support
SSB SINR measurements, which can be checked based on the
measAndMobParameters IE in the UECapabilityInformation message over the Uu
interface.
● If ss-SINR-Meas is included in measAndMobParameters, the UE supports
FR1/FR2 ss-SINR measurements.
● If ss-SINR-Meas is included in fr1-Add-UE-NR-Capabilities, the UE supports
FR1 ss-SINR measurements.
● If ss-SINR-Meas is included in fr2-Add-UE-NR-Capabilities, the UE supports
FR2 ss-SINR measurements.

Table 4-38 describes the parameters for other configurations of this function.

Name

plan.

Position plan.

(2021-12-30)
5G RAN

Name

Position value.
Describe
Method

plan.

plan.

Name

Frequency h SSB_SINR_BASED_HO
Handover option determines
SSB SINR-based inter-
frequency handover.
Set this parameter
plan.
Inter- NRCellAlgoSwitch.InterFreqHoSwitc To enable SSB SINR-

Frequency h based inter-frequency
Handover handover, it is
Switch recommended that
the
INTER_FREQ_HO_CO
LLABORATION_SW
option be selected
when either MLB by
transferring UEs in
connected mode
between inter-
frequency cells or
voice-quality-based
inter-frequency
handover is also
enabled.

(2021-12-30)
5G RAN

Name

Measurement plan.
Group ID
SSB SINR NRCellInterFHoMeaGrp.SsbSinrInter Set this parameter

Inter-freq HO FreqHoA1Thld based on the network
A1 Threshold plan.
SSB SINR NRCellInterFHoMeaGrp.SsbSinrInter Set this parameter

Inter-freq HO FreqHoA2Thld based on the network
A2 Threshold plan.
Inter- NRCellInterFHoMeaGrp.InterFreqHo Set this parameter

frequency A3Offset based on the network
Handover A3 plan.
Offset

plan.

Measurement plan.
Group ID

plan.

plan.
SSB SINR gNBMobilityCommPar- Set this parameter to

Inter-freq HO am.SsbSinrInterFHoPunishTimer its recommended
Punish Timer value.

uplink interference
information about
inter-frequency
neighboring cells.
its recommended
value.

(2021-12-30)
5G RAN


//Activating SSB SINR-based inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=SSB_SINR_BASED_HO-1;

//Activating SSB SINR-based inter-frequency handover

InterFreqA1A2Hyst=2, SsbSinrInterFreqHoA1Thld=10, SsbSinrInterFreqHoA2Thld=8, InterFreqHoA3Offset=2;
//Modifying the SSB SINR-based inter-frequency handover penalty timer (Infinity is used as an example.)
MOD GNBMOBILITYCOMMPARAM: SsbSinrInterFHoPunishTimer=INFINITY;

(2021-12-30)
5G RAN
//(Recommended) Turning on the inter-frequency handover collaboration switch if SSB SINR-based inter-
frequency neighboring cells for the serving cell if SSB SINR-based inter-frequency handover is enabled for
the serving cell and uplink-interference-based inter-frequency handover is enabled for the target cell

//Modifying the SSB SINR-based inter-frequency handover penalty timer (Infinity is used as an example.)
MOD GNBMOBILITYCOMMPARAM: SsbSinrInterFHoPunishTimer=INFINITY;
//(Recommended) Turning on the inter-frequency handover collaboration switch if SSB SINR-based inter-
frequency neighboring cells for the serving cell if SSB SINR-based inter-frequency handover is enabled for
the serving cell and uplink-interference-based inter-frequency handover is enabled for the target cell

conditions.

//Deactivating SSB SINR-based inter-frequency handover

//Deactivating SSB SINR-based inter-frequency handover


If any of the following counters have a value other than 0, SSB SINR-based inter-
● N.HO.InterFreq.SSB.SINR.PrepAttOut
● N.HO.InterFreq.SSB.SINR.ExecAttOut

(2021-12-30)
5G RAN
● N.HO.InterFreq.SSB.SINR.ExecSuccOut

Rate (CU) KPI.

(2021-12-30)
5G RAN
Description 5 SA Mobility Management in Idle Mode
5 SA Mobility Management in Idle Mode
Mobility management in idle mode typically refers to cell reselection. After

camping on a cell, an RRC_IDLE UE measures the signal quality of the cell and
that of neighboring cells, and reselects a higher-quality cell to camp on based on
the cell reselection criteria.
5.1 Principles
In mobility management in idle mode, the following terms and definitions apply:
● Acceptable cell: A cell that a UE obtains only limited services (such as
emergency calls) from when camping on it.
A cell can be an acceptable cell only when:
– It is not barred.
– It meets the cell selection criteria (see 5.1.2 Cell Selection).
● Suitable cell: A cell that a UE obtains normal services from when camping on
it.
A cell can be a suitable cell only when:
– It is not barred.
– It meets the cell selection criteria (see 5.1.2 Cell Selection).
– It belongs to the UE-selected PLMN or a PLMN on the equivalent PLMN
list.
– It supports the PLMN selected or registered by the UE.
● Barred cell: A cell that is barred from providing services. If it is a single-
operator cell, the master information block (MIB) is used to indicate its barred
status. If it is a multi-operator cell, the SIB1 is used to indicate its barred
status for each of the operators.
5.1.1 Cell Search and PLMN Selection

Cell Search
Cell search is a procedure for a UE to achieve time and frequency synchronization
with a cell, obtain the physical cell identifier (PCI) of the cell, and learn the signal
quality and other information about the cell based on the PCI.

(2021-12-30)
5G RAN
In NR, two synchronization signals are used in cell search: primary synchronization
signals (PSSs) and secondary synchronization signals (SSSs).
A UE performs cell search as follows:
1. The UE detects the PSS to achieve clock synchronization and acquires an ID in
a PCI group based on the mapping with the PSS.
2. The UE detects the SSS to achieve time synchronization (frame
synchronization) and acquires a PCI group ID based on the mapping with the
SSS.
3. The UE determines the cell's PCI based on the PCI group ID and the ID in the
PCI group.
4. The UE detects the downlink SSB signal to determine the cell's signal quality.
5. The UE reads the MIB and SIB1 to obtain other information about the cell,
such as the operator information.
PLMN Selection
After completing cell search, the UE selects and registers with a PLMN. After the
PLMN registration succeeds, the UE displays the information about the PLMN and
prepares to obtain services from the operator.
Figure 5-1 shows the procedure for the UE to select a PLMN.
Figure 5-1 Selecting a PLMN

(2021-12-30)
5G RAN
5.1.2 Cell Selection

During a transition from RRC_CONNECTED to RRC_IDLE or after selecting a PLMN,
the UE performs cell selection to choose a suitable cell to camp on.
A UE performs cell selection as follows:
1. The UE selects and camps on a suitable cell on the frequency indicated in the
RRC Release message.
2. If a suitable cell is not found, the UE attempts to select the most recent cell it
camped on while in connected mode as the suitable cell and camps on the
cell.
3. If a suitable cell is still not found, the UE performs the Stored Information Cell
Selection procedure to find and camp on a suitable cell.
4. If a suitable cell is still not found, the UE initiates the Initial Cell Selection
procedure to find and camp on a suitable cell.
5. If the UE fails to find a suitable cell through the Initial Cell Selection
procedure, it enters the Any Cell Selection State.
In the Any Cell Selection State, the UE attempts to find an acceptable cell to
camp on. After finding an acceptable cell, the UE camps on the cell and
obtains limited services from it while periodically performing the Initial Cell
Selection procedure to search for a suitable cell. For details on the tasks UEs
perform in the Any Cell Selection State, see section 5.2.7 "Any Cell Selection
state" in 3GPP TS 38.304 V15.4.0.
The details of the Stored Information Cell Selection and Initial Cell Selection
procedures are as follows:
● Stored Information Cell Selection
The UE performs cell selection based on information about the frequencies
and cell parameters in the Stored Information (retrieved from previously
received measurement configurations or detected system information),
attempting to find a suitable cell. This information helps accelerate cell
selection.
● Initial Cell Selection
The UE scans all frequencies in the supported RATs to search for a suitable
cell. On each frequency, the UE searches for the cell with the strongest signal
and camps on the first suitable cell that it finds.
Cell Selection Criteria

During cell selection, the UE determines whether a cell meets the cell selection
criteria.
The cell selection criteria (referred to as criterion S) are as follows:
Srxlev > 0 and Squal > 0

(2021-12-30)
5G RAN
NOTE
For details about cell selection criteria, see section 5.2.3.2 "Cell Selection Criterion" in 3GPP
TS 38.304 V15.4.0.
In the cell selection criteria, Squal must be greater than 0 only if the SIB1_RSRQ_SW option
of the NRDUCellSelConfig.SibOptionalIeInd parameter is selected; only Srxlev must be
greater than 0 in other cases.
Srxlev = Qrxlevmeas - (Qrxlevmin + Qrxlevminoffset) - Pcompensation - Qoffsettemp

● Srxlev is the cell selection RX level value (dB).
● Qrxlevmeas is the measured cell RX level value (RSRP).
● Qrxlevmin is the minimum required RX level (dBm) in the cell, which is
broadcast in SIB1 and specified by the NRDUCellSelConfig.MinimumRxLevel
parameter.
● Qrxlevminoffset is the offset to the signaled Qrxlevmin (broadcast in SIB1). In this
version, it is not sent to UEs, which consider it to be 0 dB by default.
● Pcompensation = max(PEMAX1 – PPowerClass, 0). PEMAX1 is the SIB1-signaled
maximum TX power that a cell allows for a UE (corresponding to the P-Max
IE) and PPowerClass is the UE's maximum RF output power.
● Qoffsettemp is the offset (dB) temporarily applied to a cell and indicated by the
connEstFailOffset sub-IE in the ConnEstFailureControl IE broadcast in SIB1.
Qoffsettemp indicates an optional calculation factor. In this version, the value of
Qoffsettemp is always 1 dB. For details about the definition of Qoffsettemp, see
section 5.3.3.7 "T300 expiry" in 3GPP TS 38.331.
Assume that a UE fails to access a cell (indicated by the expiration of the
T300 timer, which is specified by NRDUCellUeTimerConst.T300) and the
number of consecutive failures exceeds a specific threshold (indicated by the
ConnEstFailCount sub-IE — fixed at 1 in the current version — in the
ConnEstFailureControl IE broadcast in SIB1 in the serving cell). If the UE
performs cell selection evaluation before the expiration of the period
indicated by the connEstFailOffsetValidity sub-IE in the ConnEstFailureControl
IE broadcast in SIB1 in the serving cell (the sub-IE is fixed at 30s in the current
version), Qoffsettemp is applied for calculating the cell's Srxlev.
Squal = Qqualmeas - (Qqualmin + Qqualminoffset) - Qoffsettemp

● Squal is the cell selection quality value (dB).
● Qqualmeas is the measured cell quality value (RSRQ).
● Qqualmin is the minimum required quality level (dB) in the cell, which is
broadcast in SIB1. It is specified by the NRDUCellSelConfig.MinimumRxQlty
parameter.
● Qqualminoffset is the offset to the signaled Qqualmin (broadcast in SIB1). It is not
signaled in this version.
● Qoffsettemp is the offset (dB) temporarily applied to a cell and indicated by the
connEstFailOffset sub-IE in the ConnEstFailureControl IE broadcast in SIB1.

(2021-12-30)
5G RAN
Qoffsettemp indicates an optional calculation factor. In this version, the value of

Qoffsettemp is always 1 dB. For details about the definition of Qoffsettemp, see
section 5.3.3.7 "T300 expiry" in 3GPP TS 38.331.
number of consecutive failures exceeds a specific threshold (indicated by the
ConnEstFailCount sub-IE — fixed at 1 in the current version — in the
performs cell selection evaluation before the expiration of the period
indicated by the connEstFailOffsetValidity sub-IE in the ConnEstFailureControl
IE broadcast in SIB1 in the serving cell (the sub-IE is fixed at 30s in the current
version), Qoffsettemp is applied for calculating the cell's Srxlev.
5.1.3 Cell Reselection

After camping on a cell, the UE measures the signal quality of the cell and that of
neighboring cells, and selects a higher-quality cell to camp on based on the cell
reselection criteria.
A UE performs cell reselection as follows:
1. Determines whether to start measuring neighboring cells based on the

serving cell's Srxlev and Squal and the cell reselection priorities of the
frequencies where the neighboring cells work. For details, see 5.1.3.1 Cell
Reselection Priority and 5.1.3.3 Neighboring Cell Measurement for Cell
Reselection.
2. Performs cell reselection based on the measurement results of neighboring
cells and the cell reselection criteria, which are related to the cell reselection
priorities of the frequencies where the neighboring cells work.
– For equal-priority frequencies, see 5.1.3.4 Intra-Frequency or Equal-
Priority Inter-Frequency Cell Reselection.
– For different-priority frequencies, see 5.1.3.5 Different-Priority Inter-
Frequency Cell Reselection.
NOTE
To perform medium-priority blocking for a cell, the RRC_IDLE UEs in the cell must be
migrated out. The gNodeB selects cell reselection for transferring UEs out of the cell.
5.1.3.1 Cell Reselection Priority

During measurements and cell reselection, UEs consider the cell reselection
priorities of neighboring frequencies. Cell reselection priorities are classified into
common cell reselection priorities and dedicated cell reselection priorities. This
document details the common cell reselection priorities. Dedicated cell reselection
priorities can be further classified into operator-specific cell reselection priorities
and RFSP-specific cell reselection priorities. For details about operator-specific cell
reselection priorities, see Multi-Operator Sharing. For details about RFSP-specific
cell reselection priorities, see Flexible User Steering.
● Common cell reselection priorities are delivered to UEs through SIB2

broadcast and can be used by all UEs in the cell.

(2021-12-30)
5G RAN
– For the serving frequency:
▪ The cell reselection priority is configured by the

NRCellReselConfig.CellReselPriority parameter. A larger value of
this parameter indicates a higher priority.
▪ The cell reselection sub-priority is configured by the

NRCellReselConfig.CellReselSubPriority parameter. A larger value
of this parameter indicates a higher priority. If this parameter is set
to 0DOT0, the cell reselection sub-priority is not delivered.
The UE adds up the cell reselection priority and cell reselection sub-
priority of a frequency and uses the sum as the frequency's final cell
reselection priority for cell reselection.
– For non-serving frequencies:
▪ The cell reselection priority is configured by the

NRCellFreqRelation.CellReselPriority parameter. A larger value of
this parameter indicates a higher priority.
▪ The cell reselection sub-priority is configured by the

NRCellFreqRelation.CellReselSubPriority parameter. A larger value
of this parameter indicates a higher priority. If this parameter is set
to 0DOT0, the cell reselection sub-priority is not delivered.
The UE adds up the cell reselection priority and cell reselection sub-
priority of a frequency and uses the sum as the frequency's final cell
reselection priority for cell reselection.
For intra-frequency cell reselection, UEs ignore the priority information as the
intra-frequency cells have the same cell reselection priority.
● Dedicated cell reselection priorities are delivered through the
CellReselectionPriorities IE of the RRCRelease message during RRC connection
release.
5.1.3.2 Blacklisting Cells for Cell Reselection

During cell reselection, UEs do not measure or reselect to the blacklisted cells
broadcast in system information.
● Information about blacklisted intra-frequency cells is delivered in
IntraFreqBlackCellList of SIB3.
● Information about blacklisted inter-frequency cells is delivered in
IntraFreqBlackCellList of SIB4. In this version, blacklisted inter-frequency cells
cannot be configured.
Blacklisting Intra-Frequency Cells

During blacklisted intra-frequency cell configuration, multiple intra-frequency cell
blacklists are configured on the base station and then an intra-frequency cell
blacklist is associated with a cell.
1. The gNBCellBlacklist MO is configured on the gNodeB to specify an intra-
frequency cell blacklist.
a. An intra-frequency cell blacklist is specified by the
gNBCellBlackList.CellBlacklistId parameter.

(2021-12-30)
5G RAN
b. A maximum of 16 blacklisted cell ranges can be configured in each intra-

frequency cell blacklist. A blacklisted cell range is specified by the
gNBCellBlackList.StartPhysicalCellId and
gNBCellBlackList.PhysicalCellIdRange parameters. The cells of N
consecutive PCIs starting from the PCI specified by
gNBCellBlackList.StartPhysicalCellId are blacklisted, where N is a
positive integer to which the value of
gNBCellBlackList.PhysicalCellIdRange is mapped.
2. The NRCellMobilityConfig.IntraFReselCellBlacklistId parameter is
configured for an NR cell. A blacklist is applied to this cell through the
gNBCellBlackList.CellBlacklistId parameter. That is, if the IDs match, UEs in
this cell do not reselect to the cells in the blacklist during intra-frequency cell
reselection.
5.1.3.3 Neighboring Cell Measurement for Cell Reselection

Based on the Srxlev and Squal of the serving cell and the cell reselection priorities of
neighboring frequencies, a UE determines whether to measure the frequencies
broadcast in the system information.
● Intra-frequency measurement
– If the Srxlev of the serving cell is greater than the value of the
NRCellReselConfig.IntraFreqMeasStartThld parameter, the UE does not
start neighboring cell measurements for intra-frequency cell reselection.
– If the Srxlev of the serving cell is less than or equal to the value of the
NRCellReselConfig.IntraFreqMeasStartThld parameter, the UE starts
neighboring cell measurements for intra-frequency cell reselection.
● Inter-frequency measurement
– If a non-serving frequency has a higher priority than the serving
frequency, the UE starts neighboring cell measurements for cell
reselection regardless of the serving cell's signal quality.
– If a non-serving frequency has an equal or lower priority than the serving
frequency:
▪ If the Srxlev of the serving cell is greater than the value of

NRCellReselConfig.NonIntraFreqMeasRsrpThld and the Squal is
greater than the value of
NRCellReselConfig.NonIntraFreqMeasRsrqThld, the UE does not
start neighboring cell measurements for inter-frequency cell
reselection.
▪ If the Srxlev of the serving cell is less than or equal to the value of
NRCellReselConfig.NonIntraFreqMeasRsrpThld or the Squal is less
than or equal to the value of
NRCellReselConfig.NonIntraFreqMeasRsrqThld, the UE starts
neighboring cell measurements for inter-frequency cell reselection.
Configuration of SSB Beam Measurement Result Selection and Combination

A UE needs to combine the SSB beam-level measurement results of a cell when
calculating the cell-level SSB measurement result. These beam-level results must
meet the SSB combination threshold requirement.

(2021-12-30)
5G RAN
● Intra-frequency cell measurement: The SSB combination threshold is specified

by the NRCellReselConfig.SsbConsolidationThld parameter. Upon detecting
that multiple SSB beams in a cell meet the combination threshold
requirement, the UE combines the measurement results of these SSB beams
into a cell-level result. The maximum number of SSB beams whose
measurement results can be combined is specified by the
NRCellReselConfig.SsbNumToAverage parameter.
● Inter-frequency cell measurement: The SSB combination threshold is specified
by the NRCellMobilityConfig.SsbConsolidationThld parameter. Upon
detecting that multiple SSB beams in a cell meet the combination threshold
requirement, the UE combines the measurement results of these SSB beams
into a cell-level result. The maximum number of SSB beams whose
measurement results can be combined is specified by the
NRCellMobilityConfig.SsbNumToAverage parameter.
Optimized Configuration for deriveSSB-IndexFromCell

The gNodeB includes the deriveSSB-IndexFromCell IE (either set to TRUE or
FALSE) in SIB2 or SIB4. For intra-frequency neighboring cell measurements, the
value of this IE indicates whether UEs derive the SSB indexes of all intra-frequency
neighboring cells based on the timing information of the serving cell. For inter-
frequency neighboring cell measurements, it indicates whether UEs derive the SSB
indexes of all neighboring cells on the frequency of any detected inter-frequency
cell based on the timing information of that cell. If all cells on a frequency are
time-synchronized, you can improve the efficiency and accuracy of detecting
neighboring cells' SSB indexes by setting this IE to TRUE.
Optimized configuration for deriveSSB-IndexFromCell has been introduced. This
function is enabled if the PROTOCOL_IE_OPT_SW option the
NRCellAlgoSwitch.HoCompatibilitySwitch parameter is selected. When this
function is enabled, the value of the deriveSSB-IndexFromCell IE in SIB2 or SIB4
sent from the gNodeB varies with the RATs corresponding to the frequencies that
are to be measured. If an NR TDD frequency is to be measured, the value of the
deriveSSB-IndexFromCell IE is TRUE. If an NR FDD frequency is to be measured,
the value of the deriveSSB-IndexFromCell IE is FALSE.
5.1.3.4 Intra-Frequency or Equal-Priority Inter-Frequency Cell Reselection

After measuring neighboring cells for reselection, the UE performs intra-frequency
or equal-priority inter-frequency cell reselection as follows:
1. The UE selects the neighboring cells that meet the cell selection criteria
(criteria S, which is described in Cell Selection Criteria). The parameters
related to intra- and inter-frequency neighboring cells are as follows:
– The Srxlev of an intra-frequency neighboring cell is calculated using the
Qrxlevmin that is equal to the minimum cell receive level (configured by
the NRCellReselConfig.MinimumRxLevel parameter) broadcast in SIB2.
– The Srxlev of an inter-frequency neighboring cell is calculated using the
Qrxlevmin that is equal to the minimum cell receive level (configured by
the NRCellFreqRelation.MinimumRxLevel parameter) broadcast in SIB4.
– The Squal of an inter-frequency neighboring cell is calculated using the
Qqualmin that is equal to the minimum required quality level in the cell

(2021-12-30)
5G RAN
(configured by the NRCellFreqRelation.MinimumRxQlty parameter)

broadcast in SIB4.
2. Among the serving cell and the neighboring cells that meet the cell selection
criteria, the UE selects the cell with the highest signal quality ranking as the
highest ranked cell.
The signal quality ranking of a cell is calculated as follows:
– Signal quality ranking of a neighboring cell: Rn = Qmeas,n – Qoffset –
Qoffsettemp
– Signal quality ranking of the serving cell: Rs = Qmeas,s + Qhyst – Qoffsettemp
In the above formulas:
– Qmeas,n is the SSB-based measured receive level, which is also known as
RSRP, of the neighboring cell.
– Qoffset is the offset for reselection to the neighboring cell.
▪ The Qoffset of an intra-frequency neighboring cell is equal to q-

OffsetCell (configured by the NRCellRelation.NCellReselOffset
parameter) broadcast in SIB3.
▪ The Qoffset of an inter-frequency neighboring cell is equal to the sum

of the values of q-OffsetCell and q-OffestFreq broadcast in SIB4.
○ q-OffsetCell is configured by the
NRCellRelation.NCellReselOffset parameter.
○ q-OffestFreq is configured by the
NRCellFreqRelation.FreqOffset parameter.
– Qmeas,s is the SSB-based measured receive level, which is also known as
RSRP, of the serving cell.
– Qhyst is the hysteresis for cell reselection. It is configured by the
NRCellReselConfig.CellReselHysteresis parameter.
– Qoffsettemp is the offset (dB) temporarily applied to a cell and indicated by
the connEstFailOffset sub-IE in the ConnEstFailureControl IE broadcast in
SIB1 in the serving cell. Qoffsettemp indicates an optional calculation factor.
In this version, the value of Qoffsettemp is always 1 dB. For details about
the definition of Qoffsettemp, see section 5.3.3.7 "T300 expiry" in 3GPP TS
38.331.
number of consecutive failures exceeds a specific threshold (indicated by
the ConnEstFailCount sub-IE — fixed at 1 in the current version — in the
performs cell reselection evaluation before the expiration of the period
indicated by the connEstFailOffsetValidity sub-IE in the
ConnEstFailureControl IE broadcast in SIB1 in the serving cell (the sub-IE
is fixed at 30s in the current version), Qoffsettemp is applied for calculating
the signal quality ranking of only that cell.
3. Among the serving cell and the neighboring cells that meet the cell selection
criteria, the UE identifies the cells whose signal quality ranking meets the
following condition:

(2021-12-30)
5G RAN
Rhighest ranked cell – R ≤ rangeToBestCell

– Rhighest ranked cell is the signal quality ranking of the highest ranked cell.
For calculation details, see 2.
– R is the signal quality ranking of the serving cell or the neighboring cells
that meet the cell selection criteria. For calculation details, see 2.
– rangeToBestCell is fixed at 3 dB and indicated in SIB2.
4. Among the highest ranked cell and the cells that meet the preceding
condition, the UE selects the cell with the maximum number of beams whose
beam-level RSRP is greater than the SSB combination threshold as the best
cell. If there are multiple such cells, the UE selects the cell with the highest
signal quality ranking as the best cell. If none of the cells has a beam whose
beam-level RSRP is greater than the SSB combination threshold, the UE
directly selects the cell with the highest signal quality ranking among the
highest ranked cell and the cells that meet the preceding condition as the
best cell.
– For intra-frequency neighboring cells, the SSB combination threshold is
specified by the NRCellReselConfig.SsbConsolidationThld parameter
and sent to the UE through the absThreshSS-BlocksConsolidation IE in
SIB2.
– For inter-frequency neighboring cells, the SSB combination threshold is
specified by the NRCellMobilityConfig.SsbConsolidationThld parameter
and sent to the UE through the absThreshSS-BlocksConsolidation IE in
SIB4.
5. If the cell selected as the best cell is not the serving cell, the UE checks
whether the best cell meets specific conditions. If it does, the UE reselects to
the cell. Otherwise, the UE continues to camp on the original cell. The specific
conditions are as follows:
– The best cell meets the preceding cell reselection criteria (that is, the
descriptions in steps 1 through 4) throughout the period specified by
TreselectionNR (fixed at 1s).
– The UE has camped on the serving cell for more than 1s.
5.1.3.5 Different-Priority Inter-Frequency Cell Reselection

After measuring neighboring cells for reselection, the UE selects an inter-frequency
neighboring cell that meets the cell selection criteria (criteria S, which is described
in Cell Selection Criteria) if different priorities are configured for the frequencies
of inter-frequency neighboring cells.
● The Srxlev of an inter-frequency neighboring cell is calculated using the

Qrxlevmin that is equal to the minimum cell receive level (configured by the
NRCellFreqRelation.MinimumRxLevel parameter) broadcast in SIB4.
● The Squal of an inter-frequency neighboring cell is calculated using the
Qqualmin that is equal to the minimum required quality level in the cell
(configured by the NRCellFreqRelation.MinimumRxQlty parameter)
broadcast in SIB4.

(2021-12-30)
5G RAN
With different-priority inter-frequency cell reselection, the UE can reselect to the

cells on frequencies with higher or lower cell reselection priorities. For details
about cell reselection priority configuration, see 5.1.3.1 Cell Reselection Priority.
● If all of the following conditions are met, the UE reselects to a cell on a non-
serving frequency with a higher priority:
– Condition 1: The UE has camped on the serving cell for more than 1s.
– Condition 2:
▪ If the RSRQ_BASED_RESEL_SW option of the

NRCellReselConfig.SibOptionalIeInd parameter is deselected and
SIB2 does not include threshServingLowQ, the Srxlev of the
neighboring cell that is evaluated is greater than threshX-HighP
(configured by the NRCellFreqRelation.HighPriReselThld
parameter) broadcast in SIB4 throughout the period specified by
TreselectionNR (fixed at 1s) broadcast in SIB4.

NRCellReselConfig.SibOptionalIeInd parameter is selected and SIB2
includes threshServingLowQ (configured by the
NRCellReselConfig.ServFreqLowPriRsrqReselThd parameter), the
Squal of the neighboring cell that is evaluated is greater than threshX-
HighQ (configured by the
NRCellFreqRelation.HighPriReselRsrqThld parameter) broadcast in
SIB4 throughout the period specified by TreselectionNR (fixed at 1s)
broadcast in SIB4.
If multiple cells meet the preceding conditions, the neighboring cell with the
highest Rn (signal quality ranking, as determined in 2 of 5.1.3.4 Intra-
Frequency or Equal-Priority Inter-Frequency Cell Reselection) is selected
for cell reselection.
● If all of the following conditions are met, the UE reselects to a cell on a non-
serving frequency with a lower priority:
– Condition 1: No neighboring cells on non-serving frequencies with a
higher priority meet the criteria for reselecting to a cell on a frequency
with a higher priority.
– Condition 2: The UE has camped on the serving cell for more than 1s.
– Condition 3:

NRCellReselConfig.SibOptionalIeInd parameter is deselected and
SIB2 does not include threshServingLowQ, the following constraints
must be satisfied throughout the period specified by TreselectionNR
(fixed at 1s) broadcast in SIB4:
○ The Srxlev of the serving cell is less than threshServingLowP
(configured by the
NRCellReselConfig.ServFreqLowPriRsrpReselThd parameter)
broadcast in SIB2.
○ The Srxlev of the neighboring cell that is evaluated is greater than
threshX-LowP (configured by the
NRCellFreqRelation.LowPriReselThld parameter) broadcast in
SIB4.

(2021-12-30)
5G RAN

NRCellReselConfig.SibOptionalIeInd parameter is selected and SIB2
includes threshServingLowQ (configured by the
NRCellReselConfig.ServFreqLowPriRsrqReselThd parameter), the
following constraints must be satisfied throughout the period
specified by TreselectionNR (fixed at 1s) broadcast in SIB4:
○ The Squal of the serving cell is less than threshServingLowQ
(configured by the
NRCellReselConfig.ServFreqLowPriRsrqReselThd parameter)
broadcast in SIB2.
○ The Squal of the neighboring cell that is evaluated is greater than
threshX-LowQ (configured by the
NRCellFreqRelation.LowPriReselRsrqThld parameter)
broadcast in SIB4.
5.1.3.6 Speed-based Cell Reselection

Moving UEs are classified, by speed, into normal-mobility UEs, medium-mobility
UEs, and high-mobility UEs. A UE may start at a normal speed and then
accelerate. When the UE is moving at a medium or high speed, it quickly reselects
to a cell and its cell reselection parameters need to be adjusted accordingly. In
such a situation, speed-based cell reselection is introduced. This function is
controlled by the SPEED_BASED_RESEL_SW option of the
NRCellReselConfig.SibOptionalIeInd parameter. To enable speed-based cell
reselection to inter-frequency or inter-RAT cells, further select the
INTER_FREQ_RAT_SPEED_RESEL_SW option of the
NRCellReselConfig.SibOptionalIeInd parameter. This requirement does not apply
to speed-based cell reselection to intra-frequency cells.
When speed-based cell reselection is enabled, a UE can determine its speed based
on the system information (SI) broadcast by the gNodeB and then use appropriate
cell reselection parameters adaptive to its speed for cell reselection.
● A UE determines its speed based on the SI broadcast by the gNodeB. The

determination criteria are as follows:
– Normal-mobility UE
The number of reselected cells is less than or equal to n-
CellChangeMedium within a t-Evaluation duration and the number of
reselected cells is less than or equal to n-CellChangeMedium within the
subsequent t-HystNormal duration (fixed at 30s).
– Medium-mobility UE
The number of reselected cells is greater than n-CellChangeMedium but
less than or equal to n-CellChangeHigh within a t-Evaluation duration.
– High-mobility UE
The number of reselected cells is greater than n-CellChangeHigh within a
t-Evaluation duration.
Where,
– t-Evaluation is the UE mobility state evaluation period, which is specified
by the NRCellReselConfig.MobStateEvalPeriod parameter.

(2021-12-30)
5G RAN
– n-CellChangeMedium is the threshold expressed as a number of cell

reselections for evaluating whether UEs enter the medium-mobility state,
which is specified by the NRCellReselConfig.ReselThldForMediumMob
parameter.
– n-CellChangeHigh is the threshold expressed as a number of cell
reselections for evaluating whether UEs enter the high-mobility state,
which is specified by the NRCellReselConfig.ReselThldForHighMob
parameter.
● A UE selects appropriate cell reselection parameters adaptive to its speed for
cell reselection.
– Normal-mobility UE
Cell reselection is implemented according to the cell reselection
parameters described in 5.1.3.4 Intra-Frequency or Equal-Priority Inter-
Frequency Cell Reselection or 5.1.3.5 Different-Priority Inter-
Frequency Cell Reselection.
– Medium-mobility UE
The cell reselection parameters described in 5.1.3.4 Intra-Frequency or
Equal-Priority Inter-Frequency Cell Reselection or 5.1.3.5 Different-
Priority Inter-Frequency Cell Reselection are modified as follows:
Calculation of the reselection time in the cell reselection principle
(described in 5.1.3.4 Intra-Frequency or Equal-Priority Inter-Frequency
Cell Reselection or 5.1.3.5 Different-Priority Inter-Frequency Cell
Reselection): reselection time = TreselectionNR x (sf-Medium IE in the
SpeedStateScaleFactors IE)
Calculation of the reselection hysteresis used to calculate the signal
quality level of the current serving cell in the cell reselection principle
Cell Reselection): reselection hysteresis = Qhyst + (sf-Medium IE in the q-
HystSF IE)
Where,
▪ TreselectionNR is fixed at 1s.
▪ Qhyst is the hysteresis for cell reselection, which is configured by the

▪ sf-Medium IE in the SpeedStateScaleFactors IE is the scaling factor

for the cell reselection time of medium-mobility UEs, which is
specified by the NRCellReselConfig.ReselTimeSfForMediumMob
parameter.
▪ sf-Medium IE in the q-HystSF IE is the additional hysteresis for cell

reselection by medium-mobility UEs, which is specified by the
NRCellReselConfig.AddlHystForMediumMob parameter.
– High-mobility UE
The cell reselection parameters described in 5.1.3.4 Intra-Frequency or
Equal-Priority Inter-Frequency Cell Reselection or 5.1.3.5 Different-
Priority Inter-Frequency Cell Reselection are modified as follows:
Calculation of the reselection time in the cell reselection principle

(2021-12-30)
5G RAN
Cell Reselection or 5.1.3.5 Different-Priority Inter-Frequency Cell

Reselection): reselection time = TreselectionNR x (sf-High IE in the
SpeedStateScaleFactors IE)
Calculation of the reselection hysteresis used to calculate the signal
quality level of the current serving cell in the cell reselection principle
Cell Reselection): reselection hysteresis = Qhyst + (sf-High IE in the q-
HystSF IE)
Where,
▪ TreselectionNR is fixed at 1s.
▪ Qhyst is the hysteresis for cell reselection, which is configured by the

▪ sf-High IE in the SpeedStateScaleFactors IE is the scaling factor for

the cell reselection time of high-mobility UEs, which is specified by
the NRCellReselConfig.ReselTimeSfForHighMob parameter.
▪ sf-High IE in the q-HystSF IE is the additional hysteresis for cell

reselection by high-mobility UEs, which is specified by the
NRCellReselConfig.AddlHystForHighMob parameter.
5.2 Network Analysis
5.2.1 Benefits
This function allows UEs in RRC_IDLE mode to camp on a cell with a higher signal
quality, ensuring continuous coverage and providing users with seamless service
experience.
5.2.2 Impacts
Network Impacts
None
Function Impacts
None
5.3 Requirements
5.3.1 Licenses

(2021-12-30)
5G RAN
5.3.2 Software
RAT Function Function Switch Reference Description
Name
FDD Including INTER_FREQ_RAT_S None The speed-based cell

Low- the scale- PEED_RESEL_SW reselection function
freq related IE option of the must be enabled
uenc for speed- NRCellReselConfig.S before the function of
y based ibOptionalIeInd including the scale-
TDD reselectio parameter related IE for speed-
n to inter- based reselection to
High frequency inter-frequency or
- or inter- inter-RAT cells is
freq RAT cells enabled.
uenc
y
TDD

None
5.3.3 Hardware
Base Station Models

with the BBU3910.

Boards
RF Modules
5.3.4 Others
Speed-based cell reselection: UEs must support speed-based cell reselection.

(2021-12-30)
5G RAN
5.4 Operation and Maintenance
5.4.1 Data Configuration
5.4.1.1 Data Preparation

This function is enabled by default and does not need activation.
Table 5-1 describes the parameters used for function optimization.

Name
Cell NRCellReselConfig.CellReselHystere- Set this parameter to

Reselection sis its recommended
Hysteresis value.
Intra-Freq NRCellReselConfig.IntraFreqMeasSta Set this parameter to

Measurement rtThld its recommended
Start value.
Threshold
Minimum RX NRCellReselConfig.MinimumRxLevel Set this parameter to

Level its recommended
value.
Cell NRCellReselConfig.CellReselPriority Set this parameter to

Reselection its recommended
Priority value.
Cell NRCellReselConfig.CellReselSubPrior Set this parameter to

Reselection ity its recommended
Sub-Priority value.
SSB NRCellReselConfig.SsbConsolidation Set this parameter to

Consolidation Thld its recommended
Threshold value.
SSB Number NRCellReselConfig.SsbNumToAverag Set this parameter to

To Average e its recommended
value.
Handover NRCellAlgoSwitch.HoCompatibility- It is recommended

Compatibility Switch that the
Switch PROTOCOL_IE_OPT_S
W option be selected.

(2021-12-30)
5G RAN

Name
Non-Intra- NRCellReselConfig.NonIntraFreqMea Set this parameter to

Freq sRsrpThld its recommended
Measurement value.
RSRP
Threshold
Non-Intra- NRCellReselConfig.NonIntraFreqMea Set this parameter to

Freq sRsrqThld its recommended
Measurement value.
RSRQ
Threshold
Serving Freq NRCellReselConfig.ServFreqLowPriRs Set this parameter to

Low Priority rpReselThd its recommended
RSRP Resel value.
Thld
Minimum RX NRDUCellSelConfig.MinimumRxLeve Set this parameter to

Level l its recommended
value.
SIB Optional NRDUCellSelConfig.SibOptionalIeInd Select the

IE Indicator SIB1_RSRQ_SW
option if RSRQ-based
cell selection is
required.
Minimum RX NRDUCellSelConfig.MinimumRxQlty Set this parameter to

Quality its recommended
value.
Neighboring NRCellRelation.NCellReselOffset Set this parameter to

Cell its recommended
Reselection value.
Offset
Frequency NRCellFreqRelation.FreqOffset Set this parameter to

Offset its recommended
value.
Cell NRCellFreqRelation.CellReselPriority Set this parameter to

Priority value.
Cell NRCellFreqRelation.CellReselSubPrio Set this parameter to

Reselection rity its recommended
Sub-Priority value.
Cell Blacklist gNBCellBlacklist.CellBlacklistId Set this parameter

ID based on the network
plan.

(2021-12-30)
5G RAN

Name
Start Physical gNBCellBlacklist.StartPhysicalCellId Set this parameter

Cell ID based on the network
plan.
Physical Cell gNBCellBlacklist.PhysicalCellIdRange Set this parameter

ID Range based on the network
plan.
Intra- NRCellMobilityCon- Set this parameter

Frequency fig.IntraFReselCellBlacklistId based on the network
Resel Cell plan.
Blacklist ID
SSB NRCellMobilityCon- Set this parameter to

Consolidation fig.SsbConsolidationThld its recommended
Threshold value.
SSB Number NRCellMobilityCon- Set this parameter to

To Average fig.SsbNumToAverage its recommended
value.
Minimum RX NRCellFreqRelation.MinimumRxLeve Set this parameter to

Level l its recommended
value.
Minimum RX NRCellFreqRelation.MinimumRxQlty Set this parameter to

Quality its recommended
value.
High Priority NRCellFreqRelation.HighPriReselThl Set this parameter to

Reselection d its recommended
Threshold value.

(2021-12-30)
5G RAN

Name
SIB Optional NRCellReselConfig.SibOptionalIeInd Select the

IE Indicator RSRQ_BASED_RESEL_
SW option if RSRQ-
based cell reselection
is required.
To enable speed-
based cell reselection,
select the
SPEED_BASED_RESEL
_SW option. To enable
speed-based cell
reselection to inter-
frequency or inter-RAT
cells, further select
the
INTER_FREQ_RAT_SP
EED_RESEL_SW
option of the
NRCellReselConfig.Si
bOptionalIeInd
parameter. This
requirement does not
apply to speed-based
reselection to intra-
frequency cells.
Serving Freq NRCellReselConfig.ServFreqLowPriRs Set this parameter to

Low Priority rqReselThd its recommended
RSRQ Resel value.
Thld
High Priority NRCellFreqRelation.HighPriReselRsr Set this parameter to

Reselection qThld its recommended
RSRQ value.
Threshold
Low Priority NRCellFreqRelation.LowPriReselThld Set this parameter to

Threshold value.
Low Priority NRCellFreqRelation.LowPriReselRsrq Set this parameter to

Reselection Thld its recommended
RSRQ value.
Threshold
Mobility State NRCellReselConfig.MobStateEvalPer- Use the recommended

Evaluation iod value.
Period

(2021-12-30)
5G RAN

Name
Resel Count NRCellReselConfig.ReselThldForMedi Use the recommended

Threshold for umMob value.
Medium
Mobility
Resel Count NRCellReselConfig.ReselThldForHigh Use the recommended

Threshold for Mob value.
High Mobility
Resel Time NRCellReselConfig.ReselTimeSfForM Use the recommended

Scale Factor ediumMob value.
for Medium
Mobility
Additional NRCellReselConfig.AddlHystForMedi Use the recommended

Hysteresis for umMob value.
Medium
Mobility
Resel Time NRCellReselConfig.ReselTimeSfForHi Use the recommended

Scale Factor ghMob value.
for High
Mobility
Additional NRCellReselConfig.AddlHystForHigh- Use the recommended

Hysteresis for Mob value.
High Mobility
5.4.1.2 Using MML Commands

MML commands are not required for activating this function.

//Optimizing cell reselection parameters
MOD NRCELLRESELCONFIG: NrCellId=0, MinimumRxLevel=-64, IntraFreqMeasStartThld=29,
CellReselHysteresis=DB4, CellReselPriority=7, CellReselSubPriority=0DOT0, SsbConsolidationThld=70,
SsbNumToAverage=8, NonIntraFreqMeasRsrpThld=9, NonIntraFreqMeasRsrqThld=2,
ServFreqLowPriRsrpReselThd=7, SibOptionalIeInd=RSRQ_BASED_RESEL_SW-1,
ServFreqLowPriRsrqReselThd=1;
//Optimizing cell selection parameters
MOD NRDUCELLSELCONFIG: NrDuCellId=0, MinimumRxLevel=-64, SibOptionalIeInd=SIB1_RSRQ_SW-1,
MinimumRxQlty=-34;
//Optimizing cell relationship parameters
MOD NRCELLRELATION: NrCellId=0, Mcc="302", Mnc="220", gNBId=1, CellId=0, NCellReselOffset=DB0;
//Modifying the frequency relationship configurations of an NR cell
MOD NRCELLFREQRELATION: NrCellId=0, SsbFreqPos=6300, FrequencyBand=N41, CellReselPriority=1,
CellReselSubPriority=0DOT0, MinimumRxLevel=-64, HighPriReselThld=11, LowPriReselThld=11,
FreqOffset=DB0, MinimumRxQlty=-34, HighPriReselRsrqThld=3, LowPriReselRsrqThld=3;

(2021-12-30)
5G RAN
//Modifying the SSB combination threshold and the number of SSBs allowed for calculating the average
value for inter-frequency neighboring cell measurement
//Adding a cell blacklist for the gNodeB
ADD GNBCELLBLACKLIST: CellBlacklistId=1, StartPhysicalCellId=231, PhysicalCellIdRange=N4;
//Modifying the cell blacklist ID for intra-frequency reselection
MOD NRCELLMOBILITYCONFIG: NrCellId=0, IntraFReselCellBlacklistId=1;
//Configuration for enabling speed-based cell reselection
//Setting the UE mobility state evaluation period, threshold expressed as a number of cell reselections for
evaluating whether UEs enter the medium-mobility state, threshold expressed as a number of cell
reselections for evaluating whether UEs enter the high-mobility state, scaling factor for the cell reselection
time of medium-mobility UEs, scaling factor for the cell reselection time of high-mobility UEs, additional
hysteresis for cell reselection by medium-mobility UEs, and additional hysteresis for cell reselection by high-
mobility UEs
MOD NRCELLRESELCONFIG: NrCellId=0, MobStateEvalPeriod=S60, ReselThldForMediumMob=4,
ReselThldForHighMob=8, ReselTimeSfForMediumMob=1DOT0, ReselTimeSfForHighMob=0DOT75,
AddlHystForMediumMob=DB0, AddlHystForHighMob=DB0;
//Enabling speed-based cell reselection
MOD NRCELLRESELCONFIG: NrCellId=0, SibOptionalIeInd=SPEED_BASED_RESEL_SW-1;
//Enabling speed-based cell reselection to inter-frequency or inter-RAT neighboring cells
MOD NRCELLRESELCONFIG: NrCellId=0, SibOptionalIeInd=INTER_FREQ_RAT_SPEED_RESEL_SW-1;

//Optimizing cell reselection parameters
MOD NRCELLRESELCONFIG: NrCellId=0, MinimumRxLevel=-64, IntraFreqMeasStartThld=29,
CellReselHysteresis=DB4, CellReselPriority=7, CellReselSubPriority=0DOT0, SsbConsolidationThld=70,
SsbNumToAverage=8, NonIntraFreqMeasRsrpThld=9, NonIntraFreqMeasRsrqThld=2,
ServFreqLowPriRsrpReselThd=7, SibOptionalIeInd=RSRQ_BASED_RESEL_SW-1,
ServFreqLowPriRsrqReselThd=1;
//Optimizing cell selection parameters
MOD NRDUCELLSELCONFIG: NrDuCellId=0, MinimumRxLevel=-64, SibOptionalIeInd=SIB1_RSRQ_SW-1,
MinimumRxQlty=-34;
//Optimizing cell relationship parameters
MOD NRCELLRELATION: NrCellId=0, Mcc="302", Mnc="220", gNBId=1, CellId=0, NCellReselOffset=DB0;
//Modifying the frequency relationship configurations of an NR cell
MOD NRCELLFREQRELATION: NrCellId=0, SsbFreqPos=4625, FrequencyBand=N3, CellReselPriority=1,
CellReselSubPriority=0DOT0, MinimumRxLevel=-64, HighPriReselThld=11, LowPriReselThld=11,
FreqOffset=DB0, MinimumRxQlty=-34, HighPriReselRsrqThld=3, LowPriReselRsrqThld=3;
//Modifying the SSB combination threshold and the number of SSBs allowed for calculating the average
value for inter-frequency neighboring cell measurement
//Adding a cell blacklist for the gNodeB
ADD GNBCELLBLACKLIST: CellBlacklistId=1, StartPhysicalCellId=231, PhysicalCellIdRange=N4;
//Modifying the cell blacklist ID for intra-frequency reselection
MOD NRCELLMOBILITYCONFIG: NrCellId=0, IntraFReselCellBlacklistId=1;
//Configuration for enabling speed-based cell reselection
//Setting the UE mobility state evaluation period, threshold expressed as a number of cell reselections for
evaluating whether UEs enter the medium-mobility state, threshold expressed as a number of cell
reselections for evaluating whether UEs enter the high-mobility state, scaling factor for the cell reselection
time of medium-mobility UEs, scaling factor for the cell reselection time of high-mobility UEs, additional
hysteresis for cell reselection by medium-mobility UEs, and additional hysteresis for cell reselection by high-
mobility UEs
MOD NRCELLRESELCONFIG: NrCellId=0, MobStateEvalPeriod=S60, ReselThldForMediumMob=4,
ReselThldForHighMob=8, ReselTimeSfForMediumMob=1DOT0, ReselTimeSfForHighMob=0DOT75,
AddlHystForMediumMob=DB0, AddlHystForHighMob=DB0;
//Enabling speed-based cell reselection
MOD NRCELLRESELCONFIG: NrCellId=0, SibOptionalIeInd=SPEED_BASED_RESEL_SW-1;
//Enabling speed-based cell reselection to inter-frequency or inter-RAT neighboring cells
MOD NRCELLRESELCONFIG: NrCellId=0, SibOptionalIeInd=INTER_FREQ_RAT_SPEED_RESEL_SW-1;

(2021-12-30)
5G RAN

network conditions.
5.4.1.3 Using the MAE-Deployment

5.4.2 Activation Verification

Basic Functions of Mobility Management in Idle Mode
After the related configurations are complete on the gNodeB, check SIB2 or SIB4
in the NR cell.
Step 1 Start Uu signaling tracing: Log in to the MAE-Access and choose Monitor >
Signaling Trace > Signaling Trace Management. On the displayed page, choose
Trace Type > NR > Application Layer > Uu Interface Trace.
Step 2 Check whether the cellReselectionPriority and CellReselectionSubPriority IEs
corresponding to the NG-RAN cell are contained in SIB2 sent by the gNodeB. If
they are contained and share the same values as the
NRCellReselConfig.CellReselPriority and
NRCellReselConfig.CellReselSubPriority parameters, respectively, cell reselection
has taken effect.
Step 3 In inter-frequency networking, check whether the cellReselectionPriority and
CellReselectionSubPriority IEs corresponding to a non-serving frequency are
contained in SIB4 sent by the gNodeB. If they are contained and share the same
values as the NRCellFreqRelation.CellReselPriority and
NRCellFreqRelation.CellReselSubPriority parameters, respectively, inter-
frequency cell reselection has taken effect.
----End
Optimization to Mobility Management in Idle Mode

Optimized configuration for deriveSSB-IndexFromCell
After the related configurations are complete on the gNodeB, check SIB2 or SIB4
in the current serving cell.
1. Start Uu signaling tracing: Log in to the MAE-Access and choose Monitor >
Signaling Trace > Signaling Trace Management. On the displayed page,
choose Trace Type > NR > Application Layer > Uu Interface Trace.
2. If the serving cell is an NR TDD cell and the value of the deriveSSB-
IndexFromCell IE in SIB2 sent by the gNodeB is TRUE, optimized configuration
for deriveSSB-IndexFromCell has taken effect.
3. In inter-frequency networking, if the value of the deriveSSB-IndexFromCell IE
corresponding to an NR TDD frequency in SIB4 sent by the gNodeB is TRUE,
optimized configuration for deriveSSB-IndexFromCell has taken effect.
Speed-based cell reselection

(2021-12-30)
5G RAN
After the related configurations are complete on the gNodeB, check SIB2, SIB4, or
SIB5 in the current serving cell.
1. Start Uu signaling tracing: Log in to the MAE-Access and choose Monitor >
Signaling Trace > Signaling Trace Management. On the displayed page,
choose Trace Type > NR > Application Layer > Uu Interface Trace.
2. When the speed-based cell reselection function is enabled by selecting the
SPEED_BASED_RESEL_SW option of the
NRCellReselConfig.SibOptionalIeInd parameter, this function has taken
effect if the gNodeB-delivered SIB2 contains the IEs t-Evaluation, n-
CellChangeMedium, n-CellChangeHigh, sf-Medium in q-HystSF, sf-High in q-
HystSF, sf-Medium in SpeedStateScaleFactors, and sf-High in
SpeedStateScaleFactors, with their values the same as the settings of
parameters NRCellReselConfig.MobStateEvalPeriod,
NRCellReselConfig.ReselThldForMediumMob,
NRCellReselConfig.ReselThldForHighMob,
NRCellReselConfig.AddlHystForMediumMob,
NRCellReselConfig.AddlHystForHighMob,
NRCellReselConfig.ReselTimeSfForMediumMob, and
NRCellReselConfig.ReselTimeSfForHighMob, respectively.
3. In inter-frequency or inter-RAT networking, when the
INTER_FREQ_RAT_SPEED_RESEL_SW option of the
NRCellReselConfig.SibOptionalIeInd parameter is selected, the function of
speed-based cell reselection to inter-frequency or inter-RAT neighboring cells
has taken effect if the gNodeB-delivered SIB4 or SIB5 contains the IEs sf-
Medium and sf-High in SpeedStateScaleFactors, with their values the same as
the settings of parameters NRCellReselConfig.ReselTimeSfForMediumMob
and NRCellReselConfig.ReselTimeSfForHighMob, respectively.
Other sub-functions: No activation verification method is available.
5.4.3 Network Monitoring

This function is a basic function that ensures basic service performance. Separate
monitoring is not required.

(2021-12-30)
5G RAN
Description 6 SA Mobility Management in Inactive Mode
6 SA Mobility Management in Inactive

Mode
This chapter describes SA mobility management policies for UEs in the inactive
state.
6.1 Principles
The RRC_INACTIVE state is introduced to NR. A UE in this state suspends data
processing and, when moving inside a RAN-based Notification Area (RNA), does
not need to exchange information with the gNodeB. (For details about RNA, see
6.1.1 RNA Introduction.) As the gNodeB continues to maintain the UE's context
information, the core network considers that the UE remains in the CM-
CONNECTED state (as if it were still in the RRC_CONNECTED state). When data
transmission is required, the UE can quickly transit to the RRC_CONNECTED state.
The UE in the RRC_INACTIVE state can maintain the similar level of power
consumption as it did in the RRC_IDLE state while resuming data transmission
after a short delay.
The RRC_INACTIVE state is configured by selecting the RRC_INACTIVE_SWITCH

option of the NRCellAlgoSwitch.InactiveStrategySwitch parameter.
An RRC_CONNECTED UE enters the RRC_INACTIVE state when all of the following

conditions are met:
● The switch for the RRC_INACTIVE state is turned on, and the UE supports this
state.
● The no-data-transmission duration of the UE exceeds the value of the
NRDUCellQciBearer.UeInactivityTimer parameter. If the UE has multiple
data radio bearers (DRBs), the maximum
NRDUCellQciBearer.UeInactivityTimer parameter value among all DRBs is
used.
● The RNA ID of the serving cell has been planned. That is, the
NRDUCell.RanNotificationAreaId parameter is set to a valid value (not
65535).
An RRC_INACTIVE UE performs cell search, PLMN selection, cell selection, cell

reselection, RNA update, and state transition during its movement.

(2021-12-30)
5G RAN
● Cell search, PLMN selection, cell selection, and cell reselection: Their
mechanisms are the same as those in idle mode. For details, see 5 SA
Mobility Management in Idle Mode.
● RNA update: This procedure helps acquire the correct RNA of the moving UE.
For details, see 6.1.2 RNA Update.
● State transition: The UE changes its state to RRC_CONNECTED or RRC_IDLE in
response to the change in service status. For details, see 6.1.3 State
Transition from RRC_INACTIVE.
6.1.1 RNA Introduction

An RNA covers a single cell or multiple cells belonging to the same tracking area
(TA). As illustrated in Figure 6-1, a UE belongs to RNA1. In RAN paging, paging
messages are sent to all external cells that are served by gNodeBs having Xn
connections with the last serving gNodeB and for which the RNA ID is RNA1 (the
RNA IDs of external cells are sent to the serving cell over the Xn interface). Paging
messages will not be sent to other cells. Therefore, Xn interfaces must be set up
between gNodeBs in the same RNA, and proper RNA IDs must be configured for
the external cells as planned.
NOTE
For details about RAN paging, see 5G Networking and Signaling.
Figure 6-1 RNA
When a UE enters the RRC_INACTIVE state, the last serving gNodeB allocates an
RNA ID to the UE. The RNA ID consists of the TAC and RAN area code. In scenarios
other than multi-operator sharing, the RAN area code is specified by the

(2021-12-30)
5G RAN
NRDUCell.RanNotificationAreaId parameter. In multi-operator sharing scenarios,

the RAN area code can be configured separately for operators through the
NRDUCellOp.RanNotificationAreaId parameter.
The UE obtains the RNA ID in either of the following ways:
● If the UE transits from the RRC_CONNECTED state to the RRC_INACTIVE state,
it obtains the RNA ID of the current cell through the RAN-AreaConfig IE in the
RRCRelease message sent from the base station.
● If cell reselection is completed for the RRC_INACTIVE UE, it obtains the RNA
ID of the current cell from the RAN area code IE in SIB1. The UE then
compares the RNA ID with the last-acquired RNA ID. If the two RNA IDs are
different, the UE initiates an RNA update procedure by sending an
RRCResume message to notify the gNodeB of the RNA ID of the current cell.
6.1.2 RNA Update

RNA update helps acquire the correct RNA of a moving UE. RNA update is
triggered in any of the following scenarios:
● A UE periodically sends an RRCResumeRequest1 message with the cause
value "RNA Update" to the gNodeB. This enables the gNodeB to determine
whether the UE is disconnected from the network.
● Once the UE discovers that the RNA ID of the current cell after cell reselection
differs from the last-acquired RNA ID, it notifies the gNodeB by sending an
RRCResumeRequest1 message with the "Resume Cause" being "RNA Update".
After receiving an RRCResumeRequest1 message with the "Resume Cause" being
"RNA Update" from a UE, the gNodeB starts an RNA update procedure as
illustrated in Figure 6-2.

(2021-12-30)
5G RAN
Figure 6-2 RNA update procedure
RNA update is classified into intra-gNodeB RNA update and inter-gNodeB RNA
update, depending on whether the gNodeB currently serving the UE is the last
serving gNodeB.
● In the case of intra-gNodeB RNA update (when the current gNodeB is the last
serving gNodeB), the gNodeB sends the UE an RRCRelease message
containing the suspendConfig IE to complete the RNA update.
● In the case of inter-gNodeB RNA update (when the current gNodeB is not the
last serving gNodeB), the gNodeB sends a RETRIEVE UE CONTEXT REQUEST
message to the last serving gNodeB over the Xn interface to retrieve the UE
context. For details, see 6.1.4 UE Context Retrieval.

(2021-12-30)
5G RAN
– If the gNodeB successfully retrieves the UE context information from the

last serving gNodeB before the T319 timer expires, the gNodeB sends the
UE an RRCRelease message containing the suspendConfig IE to complete
the RNA update.
– If the gNodeB does not receive any feedback from the last serving
gNodeB before the T319 timer expires, the gNodeB sends an RRCSetup
message to the UE.
– If the gNodeB receives a RETRIEVE UE CONTEXT FAILURE message from
the last serving gNodeB before the T319 timer expires, it performs as
follows:
▪ If the message contains an encapsulated RRCRelease message, the

gNodeB sends the RRCRelease message to the UE. However, the
gNodeB does not know whether the encapsulated RRCRelease
message contains the suspendConfig IE. Based on whether the
received RRCRelease message contains the suspendConfig IE, the UE
determines whether to transit to the RRC_IDLE state, or stay in the
RRC_INACTIVE state and complete the RNA update.
▪ If the message does not contain an encapsulated RRCRelease

message, the gNodeB sends an RRCSetup message to the UE.
The T319 timer length is specified by the NRDUCellUeTimerConst.T319
parameter.
NOTE
During an inter-gNodeB RNA update, the RETRIEVE UE CONTEXT REQUEST message

sent over the Xn interface carries the PLMN, gNBID, CellId, PCI, and DL ARFCN IEs
corresponding to the target cell, in accordance with a Huawei proprietary protocol.
These IEs help the last serving gNodeB derive keys.
For details about the signaling procedure for RNA update, see section 9.2.2.5 "RNA
update" in 3GPP TS 38.300.
6.1.3 State Transition from RRC_INACTIVE

An RRC_INACTIVE UE can transit to the RRC_CONNECTED or RRC_IDLE state.
● Transition to RRC_CONNECTED: When a UE receives a RAN paging message
or has data to send to the network, the UE transits from RRC_INACTIVE to
RRC_CONNECTED. For details, see section 9.2.2.4 "State Transitions" in 3GPP
TS 38.300 V15.6.0.
● Transition to RRC_IDLE: After transition to RRC_INACTIVE, if a UE does not
perform any services throughout the period specified by
gNBConnStateTimer.UeInactiveToIdleTimer (UE inactive-to-idle timer) and
the serving gNodeB remains unchanged, the last serving gNodeB triggers the
UE to transit from RRC_INACTIVE to RRC_IDLE and sends a context release
message to the core network.

(2021-12-30)
5G RAN
NOTE
If the RAN paging fails due to reasons such as no available Xn connection to the last
serving gNodeB, the gNodeB triggers the UE to transit to RRC_IDLE after 10s and waits for
the core network to initiate a 5GC paging.
During an inter-gNodeB state transition for an RRC_INACTIVE UE, the RETRIEVE UE
CONTEXT REQUEST message sent over the Xn interface carries the PLMN, gNBID, CellId,
PCI, and DL ARFCN IEs corresponding to the target cell, in accordance with a Huawei
proprietary protocol. These IEs help the last serving gNodeB derive keys.
6.1.4 UE Context Retrieval

During an inter-gNodeB RNA update or transition from RRC_INACTIVE to
RRC_CONNECTED, the target gNodeB needs to retrieve UE context information
from the last serving gNodeB over the Xn interface as follows:
1. When a UE transits from RRC_CONNECTED to RRC_INACTIVE, the last serving

gNodeB sends an RRCRelease message containing an Inactive radio network
temporary identifier (I-RNTI) to the UE. The I-RNTI consists of the 20 least
significant bits of the gNodeB ID of the last serving gNodeB and a temporarily
generated UE ID.
2. When the UE sends the target gNodeB an RRCResumeRequest1 message
containing the I-RNTI allocated by the source gNodeB, the target gNodeB
resolves the I-RNTI to obtain the 20 least significant bits of the gNodeB ID of
the last serving gNodeB. Then the target gNodeB sends a RETRIEVE UE
CONTEXT REQUEST message to the last serving gNodeB over the Xn interface
to retrieve UE context information.
To ensure that the target gNodeB can send the request to the correct last serving
gNodeB, the least significant 20 bits of each gNodeB ID must be unique in the
contiguous coverage areas. If the least significant 20 bits of gNodeB IDs are not
unique, the target gNodeB may find and send Retrieve UE Context Request
messages to multiple gNodeBs meeting the requirements, causing context
retrieval failures.
6.2 Network Analysis
6.2.1 Benefits
UEs in the RRC_INACTIVE state can maintain the similar level of power
consumption as they did in the RRC_IDLE state while resuming data transmission
after a short delay because less signaling is exchanged over the air interface and
with the core network. The specific delay varies with factors such as UE processing
and core network capabilities.
6.2.2 Impacts
Network Impacts
After the RRC_INACTIVE state function is enabled, messaging over the Uu and Xn
interfaces may undergo the following changes:

(2021-12-30)
5G RAN
● The signaling over the Uu interface changes, which is mainly caused by state
transitions and periodic RNA updates.
● The number of paging messages over the Uu interface may increase. This is
mainly because RRC_INACTIVE UEs are paged when the network needs to
send data to these UEs.
● The number of messages over the Xn interface may increase, which is mainly
caused by RAN paging for RRC_INACTIVE UEs.
● The numbers of RRC connection setups, security mode setups, and RRC
connection reconfigurations decrease, whereas the number of RRC connection
resumptions increases. Such signaling changes cause a change in the number
of scheduling times, a slight increase in the average modulation and coding
scheme (MCS) index, and a decrease in the average control channel element
(CCE) aggregation level.
● The first packet delay indicated by the N.Traffic.DL.RlcFirstPktDelay.Time
counter increases because the data from the core network arrives at
RRC_INACTIVE UEs faster than at RRC_IDLE UEs.
● Due to the differences in UE processing capabilities, the timing for reporting
CSI-RS measurement results may change. As a result, the service delay
decreases, the HARQ retransmission rate for data transmission of the cell
decreases, and the throughput slightly increases.
● As RRCResume and RRCReconfiguration messages are scheduled differently,
the SRB HARQ retransmission rate changes, and the values of the
N.DL.SCH.QPSK.TB and N.DL.SCH.QPSK.TB.Retrans counters slightly
increase.
● As the number of RNA update messages increases, the uplink resource
overhead increases and the uplink block error rate (BLER) slightly increases.
As a result, the value of Cell Uplink Average Throughput (DU) slightly
decreases.
Function Impacts
Name Switch
FDD Fast RRC RRC_RELEASE Device- When the RRC_INACTIVE

Low- connection _QUICK_SW Pipe state function is enabled,
freque release option of the Synergy fast RRC connection release
ncy NRCellAlgoS allows UEs to quickly switch
TDD witch.UePwrS from the RRC_CONNECTED
avingSwitch state to the RRC_INACTIVE
parameter state.

freque
ncy
TDD
6.3 Requirements

(2021-12-30)
5G RAN
6.3.1 Licenses
6.3.2 Software
None

None
6.3.3 Hardware
Base Station Models
with the BBU3910.
Boards
RF Modules
6.3.4 Others
● UE requirements:
UEs for which SUL takes effect do not enter the RRC_INACTIVE state due to
restrictions defined in 3GPP specifications.
UEs must support the RRC_INACTIVE state. The inactiveState IE in the
UECapabilityInformation message over the Uu interface indicates support for
the state.
● Networking requirements:
– An Xn interface must be set up between gNodeBs in an RNA and
between gNodeBs in adjacent RNAs so that the target gNodeB can
retrieve context information from the last serving gNodeB over the Xn
interface during an RNA update.
– gNodeB IDs of long lengths, if required, must be properly planned on the
live network so that the least significant 20 bits of each gNodeB ID are
unique in contiguous coverage areas.

(2021-12-30)
5G RAN
– The gNodeBs in an RNA must belong to the same TA.

– The target gNodeB must meet the following requirements for obtaining
UE context:
The target gNodeB must comply with 3GPP TS 38.423 V15.5.0 or later.
Otherwise, UE context will fail to be obtained as the last serving gNodeB
complies with 3GPP TS 38.423 V15.5.0 or later. Consequently, the function
of protocol compatibility processing for Service Area Information
exchanged between base stations has been introduced. This function is
controlled by the XN_SERVICE_AREA_INFO_PROC_SW option of the
gNodeBParam.CompatibilityAlgoSwitch parameter. It is recommended
that this option be deselected when different base stations comply with
different protocol versions.
▪ If this option is selected, Huawei base stations signal the Service Area
Information IE and process this IE in compliance with 3GPP TS 38.423
V15.5.0 or later.
▪ If this option is deselected, Huawei base stations do not signal the

Service Area Information IE and they process this IE after receiving it
in compliance with 3GPP TS 38.423 V15.4.0 or earlier. With this
setting, the target gNodeB can obtain the UE context, but in the case
of handovers initiated after transition to the RRC_CONNECTED state,
UEs may be handed over to the forbidden cells indicated by the
Mobility Restriction List IE in the INITIAL CONTEXT SETUP REQUEST
message sent from the AMF.
– Compared with 3GPP TS 38.423 V16.6.0, 3GPP TS 38.423 V16.7.0
introduced a non-compatibility change in the definition of the UE
Security Capabilities IE. For details, see section 9.2.3.49 "UE Security
Capabilities" in 3GPP TS 38.423 V16.7.0. During an RNA update, the
gNodeB processes the UE Security Capabilities IE in the Retrieve UE
Context Response message sent by the last serving gNodeB to select a
ciphering algorithm. If the two base stations comply with different
protocols during the processing, a protocol compatibility issue occurs. To
prevent service restoration failures due to protocol inconsistency between
the gNodeB and the last serving gNodeB, Huawei gNodeBs have
optimized the compatibility processing in accordance with 3GPP TS
38.423 V16.7.0. This optimization is controlled by the
XN_UE_SECURITY_CAP_PROC_SW option of the
gNodeBParam.CompatibilityAlgoSwitch parameter. It is recommended
that this option be selected when a Huawei gNodeB is connected to a
non-Huawei gNodeB over the Xn interface and the non-Huawei gNodeB
signals the Retrieve UE Context Response message containing the UE
Security Capabilities IE in compliance with 3GPP TS 38.423 V16.7.0.
▪ When this option is selected, Huawei gNodeBs signal the UE Security

V16.7.0.
▪ When this option is deselected, Huawei gNodeBs signal the UE

Security Capabilities IE and process this IE in compliance with 3GPP
TS 38.423 V16.6.0.
● Core network requirements: The core network must support the
RRC_INACTIVE state. The Core Network Assistance Information for RRC

(2021-12-30)
5G RAN
INACTIVE IE in the INITIAL CONTEXT SETUP REQUEST or UE CONTEXT

MODIFICATION REQUEST message over the NG interface indicates support
for the state.
6.4 Operation and Maintenance
6.4.1 Data Configuration

Activating this function requires the RNA IDs and neighbor relationships to have
been configured for NR cells. For details about how to configure neighbor
relationships, see 4.1.4.1 Data Configuration. If ANR is enabled, neighboring cells
do not require manual configuration. For details, see ANR.
6.4.1.1 Data Preparation

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

Name
RAN NRDUCell.RanNotifica Set this parameter based on the

Notification tionAreaId network plan.
Area ID
RAN NRDUCellOp.RanNotif Set this parameter based on the

Notification icationAreaId network plan.
Area ID
INACTIVE NRCellAlgoSwitch.Ina Select the RRC_INACTIVE_SWITCH

Strategy ctiveStrategySwitch option.
Switch

Name
UE Inactivity NRDUCellQciBear- Set this parameter based on the

Timer er.UeInactivityTimer network plan.
Timer 319 NRDUCellUeTimer- Set this parameter to its

Const.T319 recommended value.
UE Inactive To gNBConnStateTim- Set this parameter to its

Idle Timer er.UeInactiveToIdle- recommended value.
Timer

(2021-12-30)
5G RAN

Name
Compatibility gNodeBParam.Compa It is recommended that the

Algorithm tibilityAlgoSwitch XN_UE_SECURITY_CAP_PROC_SW
Switch option be selected when a Huawei
gNodeB is connected to a non-
Huawei gNodeB over the Xn interface
and the non-Huawei gNodeB signals
the Handover Request message
containing the UE Security
Capabilities IE in compliance with
3GPP TS 38.423 V16.7.0. In other
scenarios, it is recommended that the
XN_UE_SECURITY_CAP_PROC_SW
option be deselected.
6.4.1.2 Using MML Commands

Before using MML commands, refer to 6.2.2 Impacts and complete the parameter
configurations for related functions based on the impact relationships between
the functions, as well as the actual network scenario.

//Configuring RNA IDs for local cells (without operator-specific configuration)
MOD NRDUCELL: NrDuCellId=0, DuplexMode=CELL_TDD, CellId=0, TrackingAreaId=0,
RanNotificationAreaId=1;
MOD NRDUCELL: NrDuCellId=1, DuplexMode=CELL_TDD, CellId=1, TrackingAreaId=0,
//Configuring RNA IDs for local cells (with operator-specific configuration)
MOD NRDUCELLOP: NrDuCellId=0, OperatorId=0, RanNotificationAreaId=1;
//(Optional, required when no neighbor relationship has been configured) Adding a neighbor relationship
with an NR cell
//Turning on the RRC_INACTIVE state switch
MOD NRCELLALGOSWITCH: NrCellId=0, InactiveStrategySwitch=RRC_INACTIVE_SWITCH-1;

//Configuring RNA IDs for local cells (without operator-specific configuration)
MOD NRDUCELL: NrDuCellId=0, DuplexMode=CELL_FDD, CellId=0, TrackingAreaId=0,
MOD NRDUCELL: NrDuCellId=1, DuplexMode=CELL_FDD, CellId=1, TrackingAreaId=0,
//Configuring RNA IDs for local cells (with operator-specific configuration)
//(Optional, required when no neighbor relationship has been configured) Adding a neighbor relationship
with an NR cell
//Turning on the RRC_INACTIVE state switch

(2021-12-30)
5G RAN

//Changing the UE inactivity timer length to 10s, which should be adjusted based on the network plan
MOD NRDUCELLQCIBEARER: NrDuCellId=0, Qci=9, UeInactivityTimer=10;
//Changing the T319 timer length to 1s
MOD NRDUCELLUETIMERCONST: NrDuCellId=0, T319=MS1000;
//Changing the UE inactive-to-idle timer to 1500s
MOD GNBCONNSTATETIMER: UeInactiveToIdleTimer=1500;

//Changing the UE inactivity timer length to 10s, which should be adjusted based on the network plan
MOD NRDUCELLQCIBEARER: NrDuCellId=0, Qci=9, UeInactivityTimer=10;
//Changing the T319 timer length to 1s
MOD NRDUCELLUETIMERCONST: NrDuCellId=0, T319=MS1000;
//Changing the UE inactive-to-idle timer to 1500s
MOD GNBCONNSTATETIMER: UeInactiveToIdleTimer=1500;

conditions.
//Turning off the RRC_INACTIVE state switch

//Turning off the RRC_INACTIVE state switch
6.4.1.3 Using the MAE-Deployment

6.4.2 Activation Verification

Feature Activation Observation:
Step 1 Start Uu signaling tracing for the cell that is enabled with RRC_INACTIVE state
function as follows: Log in to the MAE-Access and choose Monitor > Signaling
Trace > Signaling Trace Management. On the displayed page, choose Trace Type
> NR > Application Layer > Uu Interface Trace.
Step 2 Check for the suspendConfig IE in the RRC_REL messages of the tracing result. If
the IE is found, the UE has entered the RRC_INACTIVE state and this function has
taken effect.
Step 3 Check for the resumeCause IE in the RRC_RESUME_REQ_1 messages of the tracing
result. If the IE with the value rna-update is found, the RNA has been updated.
----End
Service Setup Delay Observation:

(2021-12-30)
5G RAN
The service setup delay of a UE in the RRC_INACTIVE state is shorter than that in
the RRC_IDLE state due to less signaling being exchanged over the air interface
and with the core network.
Step 1 When a UE is in the RRC_INACTIVE state, observe its service setup duration from
the time when the UE sends a preamble to the time when the UE sends an
RRCResumeComplete message.
Step 2 When the UE is in the RRC_IDLE state, observe the service setup duration from the
time when the UE sends a preamble to the time when the bearer setup is
complete (indicated by the RRCReconfigurationComplete message).
----End
6.4.3 Network Monitoring

This function can be monitored using the following KPIs:
● RRC Setup Success Rate (CU, Inactive)
● QoS Flow Setup Success Rate (CU, Inactive)
● Service Call Drop Rate (CU, Inactive)

(2021-12-30)
5G RAN
Description 7 NSA Mobility Management in Connected Mode
7 NSA Mobility Management in

Connected Mode
This chapter describes PSCell change in NSA networking.

In NSA networking, the gNodeB sends NR measurement configurations to the
eNodeB through the X2 interface and the eNodeB then delivers these
configurations to UEs.
NOTE
According to 3GPP specifications, EN-DC UEs must support all the following types of inter-
frequency handovers in NSA networking: intra-FR1 FDD inter-frequency handover, intra-FR1
TDD inter-frequency handover, intra-FR2 TDD inter-frequency handover, FDD-TDD inter-
frequency handover, and FR1-FR2 inter-frequency handover. For details, see section 4.2.9
"MeasAndMobParameters" in 3GPP TS 38.306 V15.9.0. As such, the gNodeB does not use
the information indicated by the UECapabilityInformation IE reported by a UE over the Uu
interface to determine the inter-frequency handover capability of the UE. Instead, the
gNodeB considers that the UE supports all types of inter-frequency handovers by default.
In NSA networking, measurement gap configuration varies with UE capabilities.
The per UE or per FR1 measurement gap is calculated on the LTE side based on the NR
cell's SMTC information carried in the messages sent over the X2 interface. Therefore, SMTC
parameters must be set to the same values for intra-frequency cells on the NR side to
ensure that the NR cells can be measured. For details, see NSA Networking based on EPC.
The per FR2 measurement gap is calculated on the NR side and forwarded to the eNodeB
over the X2 interface. Then, the eNodeB delivers it to UEs.
For details about UE measurement gap capabilities, see section 9 "Measurement Procedure"
in 3GPP TS 38.133 V15.5.0.
In NSA networking, UEs send measurement reports to the eNodeB or gNodeB

through the Uu interface.
● If the UEs support SRB3 and the NSA_DC_SRB3_SWITCH option of the
gNodeBParam.NsaDcOptSwitch parameter is selected, measurement reports
can be sent to the gNodeB through SRB3.
● If the UEs do not support SRB3 or the NSA_DC_SRB3_SWITCH option of the
gNodeBParam.NsaDcOptSwitch parameter is not selected, measurement
reports are sent to the eNodeB, which then transfers the related measurement
reports to the gNodeB over the X2 interface.
NSA networking supports the following types of PSCell change:

(2021-12-30)
5G RAN
● Coverage-based intra-frequency PSCell change

● Coverage-based inter-frequency PSCell change
● Frequency-priority-based inter-frequency PSCell change
● Operator-specific-priority-based inter-frequency PSCell change
● Service-based inter-frequency PSCell change
● Uplink-interference-based inter-frequency PSCell change
The principles and configurations for the PSCell change mechanisms in different
scenarios are similar to those in SA networking. Therefore, this chapter will only
describe the principles and configurations that are different. For detailed signaling
procedures for PSCell change, see NSA Networking based on EPC. Inter-frequency
PSCell change must be performed within the EN-DC band combinations supported
by the UE's EN-DC capability.
Coverage-based Intra-Frequency PSCell Change

Coverage-based intra-frequency PSCell change in NSA networking is implemented
in the same way as SA mobility management in connected mode. For details, see
4.2 Coverage-based Intra-Frequency Handover.
After coverage-based intra-frequency PSCell change is enabled, this function has

taken effect if the value of any of the following counters is not 0:
● N.NsaDc.InterSgNB.IntraFreq.PSCell.Change.Att, which indicates the

number of coverage-based inter-gNodeB intra-frequency PSCell change
attempts
● N.NsaDc.InterSgNB.IntraFreq.PSCell.Change.Succ, which indicates the
number of successful coverage-based inter-gNodeB intra-frequency PSCell
changes
● N.NsaDc.IntraSgNB.IntraFreq.PSCell.Change.Att, which indicates the
number of coverage-based intra-gNodeB intra-frequency PSCell change
attempts
● N.NsaDc.IntraSgNB.IntraFreq.PSCell.Change.Succ, which indicates the
number of successful coverage-based intra-gNodeB intra-frequency PSCell
changes
Coverage-based Inter-Frequency PSCell Change

In NSA networking, coverage-based inter-frequency PSCell change can be
implemented in measurement-based mode or blind mode, but redirection is not
supported. Measurement-based inter-frequency PSCell change can be
implemented from high frequency bands to low frequency bands, from low
frequency bands to high frequency bands and between low frequency bands. Blind
inter-frequency PSCell change can only be implemented from high frequency
bands to low frequency bands.
After coverage-based inter-frequency PSCell change (in measurement-based mode

or blind mode) is enabled, this function has taken effect if the value of any of the
following results is not 0:
● N.NsaDc.InterFreq.Coverage.PSCell.Change.Att, which indicates the number

of coverage-based inter-frequency PSCell change attempts

(2021-12-30)
5G RAN
● N.NsaDc.InterFreq.Coverage.PSCell.Change.Succ, which indicates the

number of successful coverage-based inter-frequency PSCell changes
After blind inter-frequency PSCell change is enabled, this function has taken effect
if the value of any of the following counters is not 0:
● N.NsaDc.InterFreq.Blind.Coverage.PSCell.Change.Att, which indicates the
number of blind inter-frequency PSCell change attempts
● N.NsaDc.InterFreq.Blind.Coverage.PSCell.Change.Succ, which indicates the
number of successful blind inter-frequency PSCell changes
Currently, there is no counter that directly measures the number of measurement-
based inter-frequency PSCell changes. If any of the results of the following
formulas is not 0, measurement-based inter-frequency PSCell change has taken
effect.
● Number of measurement-based inter-frequency PSCell change attempts =
Number of coverage-based inter-frequency PSCell change attempts – Number
of blind inter-frequency PSCell change attempts
● Number of successful measurement-based inter-frequency PSCell changes =
Number of successful coverage-based inter-frequency PSCell changes –
Number of successful blind inter-frequency PSCell changes
Measurement-based inter-frequency PSCell change is implemented in the same
way as SA mobility management in connected mode. For details, see 4.3
Coverage-based Inter-Frequency Handover. The following describes only the
implementation of blind inter-frequency PSCell change distinct from SA mobility
management in connected mode (which is described in 4.1 Basic Functions of
Mobility Management in Connected Mode).
The principles of blind inter-frequency PSCell change in NSA networking are as
follows:
● Handover function start decision
Blind inter-frequency PSCell change starts when all of the following conditions
are met:
– The COVERAGE_BASED_BLIND_HO option of the
– An event A2 related to coverage-based inter-frequency measurements is
received. Event A2 indicates that the signal quality of the serving cell
drops below a specific threshold, which is specified by the
NRCellInterFHoMeaGrp.CovInterFreqA2RsrpThld parameter.
NOTE
The blind mode and measurement-based mode share the same parameters for
event A2 related to coverage-based inter-frequency measurements. If a UE
reports an event A2 related to coverage-based inter-frequency measurements
and neighboring cells for blind handover are configured, the blind mode, instead
of the measurement-based mode, is triggered.
● Target cell or frequency decision
After receiving an event A2 report related to coverage-based inter-frequency
measurements:
– The neighboring cell with the COV_BASED_BLIND_HO_FLAG option of
the NRCellRelation.BlindHoFlag selected is selected for blind handover.

(2021-12-30)
5G RAN
If there are multiple such cells, the cell on the frequency with a higher
connected-mode priority (specified by the
NRCellFreqRelation.ConnFreqPriority parameter) is preferentially
selected.
– If there are no neighboring cells configured for blind handover (with the
COV_BASED_BLIND_HO_FLAG option of the
NRCellRelation.BlindHoFlag parameter deselected), measurement-
based inter-frequency handover, instead of blind handover, is performed.
The operation and maintenance of blind inter-frequency PSCell change in NSA
networking is as follows:
● Data preparation
Activating blind inter-frequency PSCell change requires that neighboring cells
for blind handover be already configured. For details, see Table 7-1.
Table 7-1 Configuring neighboring cells and the switch for blind handover
Name
NR Cell ID NRCellRelation.NrCel Set this parameter based on the

lId network plan.
Mobile NRCellRelation.Mnc Set this parameter based on the

Network network plan.
Code
Mobile NRCellRelation.Mcc Set this parameter based on the

Country network plan.
Code
gNodeB ID NRCellRelation.gNBI Set this parameter based on the

d network plan.
Cell ID NRCellRelation.CellId Set this parameter based on the

network plan.
Blind NRCellRelation.Blind It is recommended that this

Handover HoFlag parameter be set only for
Flag neighboring cells whose coverage
includes that of the serving cell.
Inter- NRCellAlgoSwitch.Int To enable coverage-based blind

Frequency erFreqHoSwitch inter-frequency handover, select
Handover the
Switch COVERAGE_BASED_BLIND_HO
option.
● Using MML commands

– Activation command examples
//Setting the blind handover flag for a neighboring cell
MOD NRCELLRELATION: NrCellId=0, Mcc="302", Mnc="220", gNBId=1, CellId=0,
BlindHoFlag=COV_BASED_BLIND_HO_FLAG-1;
//Activating coverage-based blind inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=COVERAGE_BASED_BLIND_HO-1;

(2021-12-30)
5G RAN
– 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.
//Deactivating coverage-based blind inter-frequency handover
MOD NRCELLALGOSWITCH: NrCellId=0, InterFreqHoSwitch=COVERAGE_BASED_BLIND_HO-0;
Frequency-Priority-based Inter-Frequency PSCell Change

Frequency-priority-based inter-frequency PSCell change in NSA networking is
implemented in the same way as SA mobility management in connected mode.
For details, see 4.4 Frequency-Priority-based Inter-Frequency Handover.
After frequency-priority-based inter-frequency PSCell change is enabled, this

function has taken effect if the value of any of the following counters is not 0:
● N.NsaDc.InterFreq.FreqPri.PSCell.Change.Att, which indicates the number of

frequency-priority-based inter-frequency PSCell change attempts
● N.NsaDc.InterFreq.FreqPri.PSCell.Change.Succ, which indicates the number
of successful frequency-priority-based inter-frequency PSCell changes
Operator-specific-Priority-based Inter-Frequency PSCell Change

Operator-specific-priority-based inter-frequency PSCell change in NSA networking
is implemented in the same way as SA mobility management in connected mode.
For details, see 4.5 Operator-specific-Priority-based Inter-Frequency Handover.
Currently, there is no counter that directly measures the number of operator-

specific-priority-based inter-frequency PSCell changes. If any of the results of the
following formulas is not 0, operator-specific-priority-based inter-frequency PSCell
change has taken effect:
● Number of operator-specific-priority-based inter-frequency PSCell change

attempts = (Total number of inter-gNodeB PSCell change attempts indicated
by N.NsaDc.InterSgNB.PSCell.Change.Att + Total number of intra-gNodeB
PSCell change attempts indicated by N.NsaDc.IntraSgNB.PSCell.Change.Att)
– (Number of coverage-based intra-frequency PSCell change attempts +
Number of frequency-priority-based inter-frequency PSCell change attempts +
Number of service-based inter-frequency PSCell change attempts)
● Number of successful operator-specific-priority-based inter-frequency PSCell
changes = (Total number of successful inter-gNodeB PSCell changes indicated
by N.NsaDc.InterSgNB.PSCell.Change.Succ + Total number of successful
intra-gNodeB PSCell changes indicated by
N.NsaDc.IntraSgNB.PSCell.Change.Succ) – (Number of successful coverage-
based intra-frequency PSCell changes + Number of successful frequency-
priority-based inter-frequency PSCell changes + Number of successful service-
based inter-frequency PSCell changes)
Service-based Inter-Frequency PSCell Change

Service-based inter-frequency PSCell change in NSA networking is implemented in
the same way as SA mobility management in connected mode. For details, see 4.6
Service-based Inter-Frequency Handover.

(2021-12-30)
5G RAN
After service-based inter-frequency PSCell change is enabled, this function has

taken effect if the value of any of the following counters is not 0:
● N.NsaDc.InterFreq.Service.PSCell.Change.Att, which indicates the number of
service-based inter-frequency PSCell change attempts
● N.NsaDc.InterFreq.Service.PSCell.Change.Succ, which indicates the number
of successful service-based inter-frequency PSCell changes
Uplink-Interference-based Inter-Frequency PSCell Change

The descriptions of principles, network analysis, requirements, and operation and
maintenance for uplink-interference-based inter-frequency PSCell change in NSA
networking are the same as those of SA mobility management in connected
mode. For details, see 4.7 Uplink-Interference-based Inter-Frequency Handover.
The conditions for starting uplink-interference-based inter-frequency PSCell
change in NSA networking are as follows:
● The UL_INTRF_BASED_HO and NSA_UL_INTRF_BASED_HO options of the
NRCellAlgoSwitch.InterFreqHoSwitch parameter are both selected.
● The strength of uplink interference in the serving cell is greater than the
uplink interference threshold (specified by the
NRDUCellIntrfIdent.UlIntrfThld parameter).
After the uplink-interference-based inter-frequency PSCell change function is
enabled, if INTRF_BASED is displayed for HoCause in the external CHR event
PRIVATE_INTRA_RAT_HO_OUT, this function has taken effect.

(2021-12-30)
5G RAN
Description 8 Appendix
8 Appendix
This chapter describes the signaling procedures for mobility management in SA

networking. For details about the signaling procedures for mobility management
in NSA networking, see NSA Networking based on EPC.
● Idle-mode mobility in SA networking: Cell selection and reselection mainly
occur on UEs and do not involve signaling exchange between UEs and the
gNodeB.
● Connected-mode mobility in SA networking
– For details about the signaling procedure for an intra-base-station
handover, see 8.1 Intra-Base-Station Handover.
– For details about the signaling procedure for an Xn-based handover, see
8.2 Xn-based Handover.
– For details about the signaling procedure for an NG-based handover, see
8.3 NG-based Handover.
● Inactive-mode mobility in SA networking
– For details about the signaling procedure for an RNA update, see 8.4
RNA Update.
– For details about the signaling procedure for a state transition from
RRC_INACTIVE, see 8.5 State Transition from RRC_INACTIVE.
8.1 Intra-Base-Station Handover

An intra-base-station handover is a process where a UE is handed over from one
cell to another cell served by the same gNodeB.

(2021-12-30)
5G RAN
Figure 8-1 Intra-gNodeB-DU handover
1. The gNodeB-CU delivers measurement configurations to the UE through an

2. The UE sends an RRCReconfigurationComplete message to the gNodeB-CU.
3. The UE sends a measurement report to the gNodeB-CU.
4. The target cell performs handover decision and admission control.
5. The gNodeB-CU sends a UE CONTEXT SETUP REQUEST message to the
gNodeB-DU, requesting new UE resources for the target cell.
6. If the gNodeB-DU successfully allocates resources, it sends a UE CONTEXT
SETUP RESPONSE message to the gNodeB-CU.
7. The gNodeB-CU sends a UE CONTEXT MODIFICATION REQUEST message to
the gNodeB-DU.

(2021-12-30)
5G RAN
8. The gNodeB-DU sends a UE CONTEXT MODIFICATION RESPONSE message to

the gNodeB-CU.
9. The gNodeB-CU sends an RRCReconfiguration message to the UE, instructing
the UE to perform a handover.
10. The UE initiates a non-contention-based random access procedure in the
target cell and sends an MSG1 message to the gNodeB-DU.
11. The gNodeB-DU replies with an MSG2 message.
12. The UE sends an RRCReconfigurationComplete message to the gNodeB-CU,
notifying the gNodeB-CU that the UE has accessed the target cell.
13. The gNodeB-CU sends a UE CONTEXT RELEASE COMMAND message to the
gNodeB-DU. The source cell releases the UE that has been handed over.
14. After the UE is handed over to the target cell, the gNodeB-CU sends the UE
an RRCReconfiguration message containing the measurement configurations
of the target cell.
15. After receiving the new measurement configurations from the gNodeB-CU,
the UE returns an RRCReconfigurationComplete message to the gNodeB-CU.

(2021-12-30)
5G RAN
Figure 8-2 Inter-gNodeB-DU handover
1. The gNodeB-CU delivers measurement configurations to the UE through an

2. The UE sends an RRCReconfigurationComplete message to the gNodeB-CU.
3. The UE sends a measurement report to the gNodeB-CU.
4. The target cell performs handover decision and admission control.
5. The gNodeB-CU sends a UE CONTEXT SETUP REQUEST message to the target
gNodeB-DU, requesting new UE resources for the target cell.
6. If the target gNodeB-DU successfully allocates resources, it sends a UE
CONTEXT SETUP RESPONSE message to the gNodeB-CU.
7. The gNodeB-CU sends a UE CONTEXT MODIFICATION REQUEST message to
the target gNodeB-DU.

(2021-12-30)
5G RAN
8. The target gNodeB-DU sends a UE CONTEXT MODIFICATION RESPONSE

message to the gNodeB-CU.
9. The gNodeB-CU sends an RRCReconfiguration message to the UE, instructing
the UE to perform a handover.
target cell of the target gNodeB-DU and sends an MSG1 message to the
target gNodeB-DU.
11. The target gNodeB-DU replies with an MSG2 message.
12. The UE sends an RRCReconfigurationComplete message to the gNodeB-CU,
notifying the gNodeB-CU that the UE has accessed the target cell.
13. The gNodeB-CU sends a UE CONTEXT RELEASE COMMAND message to the
source gNodeB-DU. After receiving this message, the source cell served by the
source gNodeB-DU releases the UE which has been handed over to the target
cell.
14. After the UE is handed over to the target cell, the gNodeB-CU sends the UE
an RRCReconfiguration message containing the measurement configurations
of the target cell.
15. After receiving the new measurement configurations from the gNodeB-CU,
the UE returns an RRCReconfigurationComplete message to the gNodeB-CU.
8.2 Xn-based Handover

During an Xn-based handover, the source cell and the target cell are served by
different gNodeBs that belong to the same AMF region, and an Xn interface exits
between the source and target gNodeBs.

(2021-12-30)
5G RAN
Figure 8-3 Xn-based handover
1. The source gNodeB delivers measurement configurations to the UE through

an RRCReconfiguration message.
2. The UE sends an RRCReconfigurationComplete message to the source
gNodeB.

(2021-12-30)
5G RAN
3. The UE sends a measurement report to the source gNodeB.

4. The source gNodeB performs the handover decision.
5. The source gNodeB sends a HANDOVER REQUEST message to the target
gNodeB serving the target cell over the Xn interface to initiate a handover
request.
6. After receiving the handover request, the target gNodeB performs admission
control.
7. The target gNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message
to the source gNodeB, indicating that the incoming handover is allowed.
8. The source gNodeB sends an RRCReconfiguration message to the UE,
instructing the UE to perform a handover.
9. The source gNodeB sends a PDCP SN to the target gNodeB through an SN
STATUS TRANSFER message.
target cell of the target gNodeB and sends an MSG1 message to the target
gNodeB.
11. The target gNodeB replies with an MSG2 message.
12. The UE sends an RRCReconfigurationComplete message to the target
gNodeB, notifying the target gNodeB that the UE has accessed the target cell.
13. The target gNodeB sends a PATH SWITCH REQUEST message to the AMF,
notifying the AMF that the serving cell of the UE has changed.
14. The AMF sends a PATH SWITCH REQUEST ACKNOWLEDGE message to the
target gNodeB.
15. The target gNodeB sends a UE CONTEXT RELEASE message to the source
gNodeB. After receiving this message, the source gNodeB releases the UE
which has been handed over to the target cell.
16. After the UE is handed over to the target cell, the target gNodeB sends the
UE an RRCReconfiguration message containing the measurement
configurations of the target cell.
17. After receiving the new measurement configurations from the target gNodeB,
the UE sends an RRCReconfigurationComplete message to the target gNodeB.
8.3 NG-based Handover

During an NG-based handover, the source cell and the target cell are served by
different gNodeBs that belong to different AMF regions, or the source gNodeB
and target gNodeB belong to the same AMF region but no Xn interface exits
between them.

(2021-12-30)
5G RAN
Figure 8-4 NG-based handover
1. The source gNodeB delivers measurement configurations to the UE through

an RRCReconfiguration message.

(2021-12-30)
5G RAN
2. The UE sends an RRCReconfigurationComplete message to the source

gNodeB.
3. The UE sends a measurement report to the source gNodeB.
4. The source gNodeB performs the handover decision.
5. The source gNodeB sends a HANDOVER REQUIRED message to the AMF over
the NG link to initiate a handover request.
6. The AMF sends a HANDOVER REQUEST message to the target gNodeB
serving the specified target cell to initiate a handover request.
7. After receiving the handover request, the target gNodeB performs admission
control.
8. The target gNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message
to the AMF, indicating that the incoming handover is allowed.
9. The AMF sends a HANDOVER COMMAND message to the source gNodeB.
10. The source gNodeB sends an RRCReconfiguration message to the UE,
instructing the UE to perform a handover.
11. The source gNodeB sends a PDCP SN to the AMF through an UPLINK RAN
STATUS TRANSFER message.
12. The AMF transfers the PDCP SN to the target gNodeB through a DOWNLINK
RAN STATUS TRANSFER message.
target cell of the target gNodeB and sends an MSG1 message to the target
gNodeB.
14. The target gNodeB replies with an MSG2 message.
15. The UE sends an RRCReconfigurationComplete message to the target
gNodeB, notifying the target gNodeB that the UE has accessed the target cell.
16. The target gNodeB sends a HANDOVER NOTIFY message to the AMF,
notifying the AMF that the UE has accessed the target cell.
17. The AMF sends a UE CONTEXT RELEASE COMMAND message to the source
gNodeB. After receiving this message, the source gNodeB releases the UE
which has been handed over to the target cell.
18. The source gNodeB sends a UE CONTEXT RELEASE COMPLETE message to
the AMF.
19. After the UE is handed over to the target cell, the target gNodeB sends the
UE an RRCReconfiguration message containing the measurement
configurations of the target cell.
20. After receiving the new measurement configurations from the target gNodeB,
the UE sends an RRCReconfigurationComplete message to the target gNodeB.
8.4 RNA Update

Upon receiving an RRCResumeRequest1 message with the resume cause "RNA
Update" from a UE, the gNodeB starts RNA update. RNA update can occur in the
following scenarios.
● RNA update with UE context relocation
The last serving gNodeB determines whether a UE has moved out of the
configured RNA based on the I-RNTI. When the UE moves out of the

(2021-12-30)
5G RAN
configured RNA, the last serving gNodeB sends the UE context to the gNodeB
which then manages the UE context. This is referred to as UE context
relocation. Figure 8-5 illustrates the procedure for RNA update in this case.
Figure 8-5 Procedure for RNA update with UE context relocation
a. The UE resumes from the RRC_INACTIVE state, and provides the I-RNTI
assigned by the last serving gNodeB and an appropriate cause value, for
example, RNA update.
b. The gNodeB, if able to resolve the last serving gNodeB's identity
contained in the I-RNTI, requests the last serving gNodeB to provide the
UE context.
c. The last serving gNodeB provides the UE context.
d. The gNodeB instructs the UE to transit back to the RRC_INACTIVE state.
e. The gNodeB provides forwarding addresses if the loss of the downlink
user data buffered in the last serving gNodeB should be prevented. That
is, the gNodeB sends an XN-U ADDRESS INDICATION message to the last
serving gNodeB.
f. The gNodeB performs path switching. That is, the gNodeB sends a PATH
SWITCH REQUEST message to the AMF.
g. The AMF returns a PATH SWITCH REQUEST Acknowledge message to the
gNodeB.

(2021-12-30)
5G RAN
h. The gNodeB sends an RRCRelease message with a suspend indication to

keep the UE in the RRC_INACTIVE state.
i. The gNodeB triggers the release of the UE resources at the last serving
gNodeB.
● Periodic RNA update without UE context relocation
The last serving gNodeB determines whether a UE has moved out of the
configured RNA based on the I-RNTI. When the UE is still within the
configured RNA, the last serving gNodeB does not provide the UE context to
the gNodeB but continues to manage it. That is, no UE context relocation
occurs. Figure 8-6 illustrates the procedure for RNA update in this case.
Figure 8-6 Procedure for periodic RNA update without UE context relocation
UE context, providing the cause value received in step 1.
c. The last serving gNodeB stores received information (such as C-RNTI and
PCI related to the resumption cell) for use in the next resume attempt,
and responds to the gNodeB with a RETRIEVE UE CONTEXT FAILURE
message that includes an encapsulated RRCRelease message. The
RRCRelease message includes the suspendConfig IE.
d. The gNodeB forwards the RRCRelease message to the UE. The UE then
updates the RNA based on the received RRCRelease message including
the suspendConfig IE.
● RNA update with transition to the RRC_IDLE state
If a UE in the RRC_INACTIVE state does not perform any service for a long
time (specified by the UE inactive-to-idle timer
gNBConnStateTimer.UeInactiveToIdleTimer) and the serving gNodeB
remains unchanged, the last serving gNodeB decides to push the UE to the

(2021-12-30)
5G RAN
RRC_IDLE state. Figure 8-7 illustrates the procedure for RNA update in this
case. Particularly, when RAN paging fails for reasons such as no Xn connection
to the last serving gNodeB, the gNodeB also pushes the UE to the RRC_IDLE
state after 10s. The UE then waits for 5GC paging. The procedure for RNA
update for this case is the same as that illustrated in Figure 8-7.
Figure 8-7 Procedure for RNA update with transition to the RRC_IDLE state
UE context, providing the cause value received in step 1.
c. Instead of providing the UE context, the last serving gNodeB provides an
RRCRelease message that does not include the suspendConfig IE to push
the UE to the RRC_IDLE state.
d. The last serving gNodeB deletes the UE context.
e. The gNodeB sends an RRCRelease message (not including the
suspendConfig IE) which triggers the UE to transit from the
RRC_INACTIVE state to the RRC_IDLE state.
8.5 State Transition from RRC_INACTIVE

This section describes the signaling procedure for a state transition from
RRC_INACTIVE to RRC_CONNECTED. For details about the signaling procedure for
a state transition from RRC_INACTIVE to RRC_IDLE, see Figure 8-7.

(2021-12-30)
5G RAN
Figure 8-8 illustrates the procedure for UE-triggered transition from

RRC_INACTIVE to RRC_CONNECTED.
Figure 8-8 Procedure for UE-triggered transition from RRC_INACTIVE to

RRC_CONNECTED
1. The UE resumes from the RRC_INACTIVE state and provides the I-RNTI
assigned by the last serving gNodeB.
2. The gNodeB, if able to resolve the last serving gNodeB's identity contained in
the I-RNTI, requests the last serving gNodeB to provide the UE context.
3. The last serving gNodeB provides the UE context.
4. The gNodeB instructs the UE to resume the RRC_CONNECTED state. That is,
the gNodeB sends an RRCResume message to the UE.
5. The UE enters the RRC_CONNECTED state and returns an
RRCResumeComplete message to the gNodeB.
6. The gNodeB provides forwarding addresses if the loss of the downlink user
data buffered in the last serving gNodeB should be prevented. That is, the
gNodeB sends an XN-U ADDRESS INDICATION message to the last serving
gNodeB.

(2021-12-30)
5G RAN
7. The gNodeB performs path switching. That is, the gNodeB sends a PATH
SWITCH REQUEST message to the AMF.
8. The AMF returns a PATH SWITCH REQUEST RESPONSE message to the
gNodeB.
9. The gNodeB triggers the release of the UE resources at the last serving
gNodeB.
Figure 8-9 illustrates the procedure for network-triggered transition from
RRC_INACTIVE to RRC_CONNECTED.
Figure 8-9 Procedure for network-triggered transition from RRC_INACTIVE to

RRC_CONNECTED
1. A RAN paging-triggering event (such as incoming downlink user-plane data

or downlink signaling from the 5GC) occurs.
2. RAN paging is triggered; either only in the cells served by the last serving
gNodeB or also by means of Xn RAN paging in cells served by other gNodeBs,
configured to the UE in the RNA.
3. The UE is paged based on the I-RNTI.
4. If the UE has been successfully reached, it attempts to resume from the
RRC_INACTIVE state. For details about this process, see Figure 8-8.

(2021-12-30)
5G RAN
Description 9 Parameters
9 Parameters
The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● gNodeBFunction Parameter Reference: contains all parameters 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 parameter reference for the software version used on the
live network from the product documentation delivered with that version.
FAQ: 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, FBFD-010011.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

(2021-12-30)
5G RAN
Description 10 Counters
10 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.
● gNodeBFunction 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, FBFD-010011.
Step 3 Click OK. All counters related to the feature are displayed.
----End

(2021-12-30)
5G RAN
Description 11 Glossary
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

(2021-12-30)
5G RAN
Description 12 Reference Documents
12 Reference Documents
● 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description"

● 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification"
● 3GPP TS 38.133: "NR; Requirements for support of radio resource
management"
● 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC
"
● 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities"
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage 2"
● 3GPP TS 38.423: "NG-RAN; Xn application protocol (XnAP)"
● 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)"
● 3GPP TS 23.203: "Policy and charging control architecture"
● 5G Networking and Signaling
● NSA Networking based on EPC
● Interoperability Between E-UTRAN and NG-RAN
● ANR
● Flexible User Steering
● Mobility Load Balancing
● QoS Management
● Synchronization
● Multi-Operator Sharing
● Carrier Aggregation
● Cell Management
● mmWave Beam Management (High-Frequency TDD)
● NG-flex
● Device-Pipe Synergy
● LTE FDD and NR Spectrum Sharing
● Standards Compliance
● Energy Conservation and Emission Reduction

(2021-12-30)
5G RAN
Description 12 Reference Documents
● High Speed Mobility

● VoNR
● URLLC
● Multi-Frequency Convergence
● Idle Mode Management in eRAN Feature Documentation
● Technical Specifications in 3900 & 5900 Series Base Station Product
Documentation

(2021-12-30)

Mobility Management (5G RAN6.1 - Draft A)

Uploaded by

Copyright:

Available Formats

Mobility Management (5G RAN6.1 - Draft A)

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

Mobility Management (5G RAN6.1 - Draft A)

Uploaded by

Copyright:

Available Formats

What are some of the main features discussed in the document?

What are some of the main features discussed in the document?

What are the main differences between NSA and SA mentioned in the document?

What are the main differences between NSA and SA mentioned in the document?

5G RAN

Mobility Management Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

2 About This Document...........................................................................................................13

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

4.1.4.1 Data Configuration........................................................................................................................................................ 66

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

4.4 Frequency-Priority-based Inter-Frequency Handover............................................................................................ 101

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

4.6.3.1 Licenses........................................................................................................................................................................... 139

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

4.8.4.1 Data Configuration..................................................................................................................................................... 170

5 SA Mobility Management in Idle Mode........................................................................ 176

6 SA Mobility Management in Inactive Mode.................................................................199

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

6.3.1 Licenses............................................................................................................................................................................... 206

7 NSA Mobility Management in Connected Mode.........................................................212

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

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

1.1 5G RAN6.1 Draft A (2021-12-30)

Added support for Modified parameters: FDD ● 3900 and 5900

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

Change Description Parameter Change RAT Base Station Model

Added support for Added the FDD ● 3900 and 5900

Added the SMTC Modified parameter: FDD ● 3900 and 5900

Added a None FDD ● 3900 and 5900

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

Change Description Parameter Change RAT Base Station Model

Simplified the switch Modified parameters: FDD ● 3900 and 5900

Added the impact None FDD ● 3900 and 5900

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

Change Description Parameter Change RAT Base Station Model

Added support for Added parameters: FDD ● 3900 and 5900

Added support for Modified parameter: FDD ● 3900 and 5900

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

Change Description Parameter Change RAT Base Station Model

Added support for Added parameters: FDD ● 3900 and 5900

Added support for Modified parameter: FDD DBS3900 LampSite

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

Change Description Parameter Change RAT Base Station Model

Added the impact None FDD ● 3900 and 5900

Added the impact None FDD ● 3900 and 5900

Added the impact None FDD ● 3900 and 5900

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

Change Description Parameter Change RAT Base Station Model

Added support for Added the FDD ● 3900 and 5900

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

Change Description Parameter Change RAT Base Station Model

handover and RSRP

Added the function Modified parameter: FDD ● 3900 and 5900

Added the impact None FDD ● 3900 and 5900

Added support for Modified parameter: FDD ● 3900 and 5900