NSA Networking Based On EPC (SRAN15.1 - 04)

SingleRAN
NSA Networking based on EPC

Feature Parameter Description
Issue 04
Date 2019-09-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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: http://www.huawei.com
Email: support@huawei.com
Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. i

SingleRAN
NSA Networking based on EPC Feature Parameter
Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 SRAN15.1 04 (2019-09-10)........................................................................................................................................... 1
1.2 SRAN15.1 03 (2019-07-20)........................................................................................................................................... 2
1.3 SRAN15.1 02 (2019-06-29)........................................................................................................................................... 2
1.4 SRAN15.1 01 (2019-06-06)........................................................................................................................................... 2
1.5 SRAN15.1 Draft E (2019-05-10)................................................................................................................................... 4
1.6 SRAN15.1 Draft D (2019-04-10)................................................................................................................................... 5
1.7 SRAN15.1 Draft C (2019-03-18)................................................................................................................................... 5
1.8 SRAN15.1 Draft B (2019-02-24)................................................................................................................................... 6
1.9 SRAN15.1 Draft A (2018-12-30)................................................................................................................................... 7
2 About This Document.................................................................................................................. 9

2.1 General Statements......................................................................................................................................................... 9
2.2 Applicable RAT.............................................................................................................................................................. 9
2.3 Features in This Document.............................................................................................................................................9
3 Overview....................................................................................................................................... 11
3.1 Introduction...................................................................................................................................................................11
3.2 Related Concept............................................................................................................................................................11
3.3 Architecture.................................................................................................................................................................. 13
4 Principles.......................................................................................................................................15
4.1 Carrier Management in NSA DC................................................................................................................................. 16
4.1.1 MCG Carrier Management........................................................................................................................................ 16
4.1.2 SCG Carrier Management......................................................................................................................................... 20
4.1.2.1 Measurement-based PSCell Configuration............................................................................................................ 20
4.1.2.2 Blind PSCell Configuration....................................................................................................................................24
4.1.2.3 SMTC Configuration of the PSCell........................................................................................................................25
4.2 Mobility Management in NSA DC...............................................................................................................................26
4.2.1 Mobility Policies in NSA DC.................................................................................................................................... 26
4.2.2 Mobility Procedures in NSA DC...............................................................................................................................27
4.3 NSA DC Data Split.......................................................................................................................................................39
4.3.1 Data Split Policy Selection........................................................................................................................................ 39
4.3.1.1 Downlink Data Split............................................................................................................................................... 40
4.3.1.2 Uplink Data Split.................................................................................................................................................... 41
Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. ii

SingleRAN
Description Contents
4.3.2 CP/UP Data Separation............................................................................................................................................. 42

4.3.3 Uplink and Downlink Separation.............................................................................................................................. 43
4.3.4 Uplink Fallback to LTE............................................................................................................................................. 44
4.3.5 NSA DC UE Scheduling Protection Based on MCG Cell Load............................................................................... 45
4.4 Uplink Power Control in NSA DC............................................................................................................................... 45
4.4.1 Initial Power Control................................................................................................................................................. 46
4.4.2 TDM Power Control.................................................................................................................................................. 46
4.5 Interference Avoidance in NSA DC............................................................................................................................. 49
4.5.1 UE Interference Types............................................................................................................................................... 49
4.5.2 Interference Avoidance.............................................................................................................................................. 50
4.6 NR Data Volume Reporting..........................................................................................................................................51
4.7 S-KgNB Update..............................................................................................................................................................54
4.8 Relationships Between NSA DC and LTE Features.....................................................................................................55
5 Network Analysis........................................................................................................................ 57
5.1 Benefits......................................................................................................................................................................... 57
5.2 Impacts..........................................................................................................................................................................57
6 Requirements............................................................................................................................... 67
6.1 Licenses........................................................................................................................................................................ 67
6.2 Software........................................................................................................................................................................68
6.3 Hardware...................................................................................................................................................................... 68
6.4 Networking................................................................................................................................................................... 69
6.5 Others............................................................................................................................................................................72
7 Operation and Maintenance......................................................................................................73

7.1 When to Use................................................................................................................................................................. 73
7.2 Data Configuration....................................................................................................................................................... 73
7.2.1 Data Preparation........................................................................................................................................................ 73
7.2.2 Using MML Commands............................................................................................................................................ 84
7.2.3 Using the CME.......................................................................................................................................................... 86
7.3 Activation Verification................................................................................................................................................. 86
7.4 Network Monitoring..................................................................................................................................................... 90
8 Parameters..................................................................................................................................... 92
9 Counters........................................................................................................................................ 93
10 Glossary....................................................................................................................................... 94
11 Reference Documents............................................................................................................... 95
Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. iii

SingleRAN
Description 1 Change History
1 Change History
This section describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 SRAN15.1 04 (2019-09-10)

This issue includes the following changes.
Technical Changes
Change Description Parameter Change
Supported independent control of PCC Activated RsvdSwPara6_bit28 of the

anchoring for NSA DC UEs in idle mode. eNBCellRsvdPara.RsvdSwPara6
For details, see 4.1.1 MCG Carrier parameter.
Management.
Added support for independent control of Activated RsvdSwPara6_bit29 of the

PCC anchoring for NSA DC-capable UEs in eNBCellRsvdPara.RsvdSwPara6
idle mode when PLMN priorities for cell parameter.
reselection are configured on the eNodeB.
For details, see 4.1.1 MCG Carrier
Management.
Added support for NSA DC PCC priorities Activated RsvdSwPara6_bit25 of the

by the BTS3202E, BTS3203E, and eNBCellRsvdPara.RsvdSwPara6
BTS3205E. For details, see 4.1.1 MCG parameter.
Carrier Management.
Optimized adaptive PSCell management None

policies for VoLTE UEs. For details, see
7.2.1 Data Preparation.
Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 1

SingleRAN
Editorial Changes
Optimized the architecture of the 4.2 Mobility Management in NSA DC section.
1.2 SRAN15.1 03 (2019-07-20)

Technical Changes
Optimized S1-based inter-MeNB handover None

without an SgNB change triggered by the
MeNB. For details, see S1-based Inter-
MeNB Handover Without an SgNB
Change Initiated by the MeNB.
Editorial Changes
l Added descriptions of how to check whether data split takes effect in NSA DC. For
details, see 7.3 Activation Verification.
l Revised the description of network monitoring on the gNodeB side. For details, see 7.4
Network Monitoring.
l Added descriptions of DRX parameter decoupling in NSA networking. For details, see
SgNB Addition Initiated by the MeNB.
l Updated the setting notes for the parameters in the CellQciPara, NsaDCMgmtConfig,
and gNBPdcpParamGroup MOs. For details, see 7.2.1 Data Preparation.
l Added the description of the scenarios of blind SCG configuration. For details, see
4.1.2.2 Blind PSCell Configuration.
1.3 SRAN15.1 02 (2019-06-29)

Technical Changes
None
Editorial Changes
Added the description of how to calculate the SSB offset on the LTE side. For details, see
7.2.1 Data Preparation.
1.4 SRAN15.1 01 (2019-06-06)


SingleRAN
Technical Changes
Supported the decoupling of handover Added the following parameters:

thresholds for NSA DC UEs from those for l CellQciPara.NsaDcInterFreqHoGrou-
LTE-only UEs. For details, see 4.2 Mobility pId
Management in NSA DC.
l InterFreqHoGroup.InterFreqHOGrou
pId
l CellQciPara.NsaDcIntraFreqHoGrou-
pId
l CellQciPara.NsaDcInterFreqHoGrou-
pId
l CellQciPara.NsaDcInterRatHoComm-
GroupId
l CellQciPara.NsaDcUtranHoGroupId
l CellQciPara.NsaDcGeranHoGroupId
Enhanced the NSA DC PCC anchoring l Added the

function. For details, see 4.1.1 MCG PccFreqCfg.NSADcPccA4RsrpThld
Carrier Management. parameter.
l Added the
PERIODIC_PCC_ANCHORING_SW
option to the
NsaDcMgmtConfig.NsaDcAlgoSwitch
parameter.
l Added the
VOLUME_BASED_PERIODIC_TRI
G_SW option to the
parameter.
l Added the
NSA_DC_STATE_PCC_ANCHORIN
G_SW option to the
parameter.
Added support for S1-based inter-MeNB Added the

handover without an SgNB change initiated S1_HO_DATA_FORWARDING_SW
by the MeNB. For details, see 4.2 Mobility option to the
Management in NSA DC. NsaDcMgmtConfig.NsaDcAlgoSwitch
parameter.
Added the relationships between NSA DC None

and LTE features. For details, see 4.8
Relationships Between NSA DC and LTE
Features.

SingleRAN
Supported selection of neighboring NR cells Added the

in NSA networking in hybrid NSA&SA NrExternalCell.NrNetworkingOption
networking scenarios. For details, see 4.1.2 parameter.
SCG Carrier Management.
Editorial Changes
l Added the description of whether NSA DC UEs perform PCC anchoring after accessing
cells served by non-candidate PCCs. For details, see PCC Anchoring.
l Added the description of PSCell management for VoLTE UEs. For details, see PSCell
for VoLTE UEs.
l Modified the description of function impacts related to carrier aggregation (CA). For
details, see 5.2 Impacts.
l Modified the description of NR data volume reporting. For details, see 4.6 NR Data
Volume Reporting.
l Modified the description of independent NSA DC PCC anchoring policies. For details,
see PCC Anchoring.
l Optimized the description of selection of LTE-NR user-plane data transmission paths.
For details, see 6.4 Networking.
l Added the description of SSB measurement timing configuration (SMTC). For details,
see 7.2.1 Data Preparation.
1.5 SRAN15.1 Draft E (2019-05-10)

Technical Changes
Added configuration requirements for LTE None

cells in which TDM power control is
required. For details, see 4.4.2 TDM Power
Control.
Supported the configuration of whether the Added the

MeNB triggers SgNB addition based on NSA_DC_VOLUME_BASED_SCG_AD
traffic volume during initial access, D_SW option to the
incoming RRC connection reestablishment, NsaDcMgmtConfig.NsaDcAlgoSwitch
or incoming handover of NSA DC UEs. For parameter.
details, see 4.1.2.1 Measurement-based
PSCell Configuration.

SingleRAN
Supported decoupling of the parameter Added the following parameters:

thresholds for activating or periodically l NsaDcMgmtConfig.NsaDcLteScellAct
adding LTE CA SCCs from those for BfrLenThld
periodically adding NR SCG applicable to
NSA DC UEs. For details, see SCC l NsaDcMgmtConfig.NsaDcLteScellAct
Management. BfrDelThld
Editorial Changes
Revised descriptions of intra-MeNB handover without an SgNB change initiated by the
MeNB and inter-MeNB handover without SgNB change initiated by the MeNB. For details,
see 4.2 Mobility Management in NSA DC.
1.6 SRAN15.1 Draft D (2019-04-10)

Technical Changes
Added automatic generation of scripts for None

simplified NSA deployment and X2
interface consistency check in NSA DC to
the online CME. For details, see 7.2.3 Using
the CME.
Editorial Changes
l Added the description of parameters related to SCG split bearer setup for GBR services.
For details, see 7.2.1 Data Preparation.
l Added impacted functions. For details, see 5.2 Impacts.
l Added mutually exclusive functions. For details, see Mutually Exclusive Functions.
l Added the application scenario for blind SCG addition. For details, see 4.1.2 SCG
Carrier Management.
l Revised the description of configuring the frequency band for a frequency that can map
to multiple frequency bands. For details, see 7.2.1 Data Preparation and 7.2.2 Using
MML Commands.
l Added configuration restrictions for LTE-NR co-MPT and LTE-NR co-BBU separate-
MPT co-transmission through backplane interconnection. For details, see 4.8
Relationships Between NSA DC and LTE Features.
1.7 SRAN15.1 Draft C (2019-03-18)


SingleRAN
Technical Changes
Added support for TDM power control. For LTE side:

details, see 4.4.2 TDM Power Control. l NsaDcMgmtConfig.NsaTdmPcTrigSin
rThld
l NsaDcMgmtConfig.NsaDcUeMcgUlM
aximumPower
l NsaDcMgmtConfig.NsaDcUeScgUlMa
ximumPower
NR side:
Added the
NSA_DC_ENH_UL_POWER_CONTRO
L_SW option to the
NRCellNsaDcConfig.NsaDcAlgoSwitch
parameter.
Optimized NR data volume reporting. For None

details, see 4.6 NR Data Volume
Reporting.
Supported separate measurement of KPIs None

for NSA DC UEs and LTE-only UEs. For
details, see 7.4 Network Monitoring.
Supported delivery of the None

upperLayerIndication IE based on the NR
neighbor relationship configuration. For
details, see 7.2.2 Using MML Commands.
Added support for NR by 3900 series base None

stations and DBS3900 LampSite configured
with the BBU3910. For details, see 6.3
Hardware. For details, see 6.3 Hardware.
Added the UMPTg board that supports LTE None

and NR. For details, see 6.3 Hardware.
Editorial Changes
l Added the description of observing whether TDM power control takes effect. For details,
see 7.3 Activation Verification.
l Revised descriptions in 4.3.1 Data Split Policy Selection.
l Revised descriptions in 6.3 Hardware.
1.8 SRAN15.1 Draft B (2019-02-24)


SingleRAN
Technical Changes
Added support for configuring the Added the NrScgFreqConfig.ScgDlArfcn

frequency band for a frequency that can parameter to the LTE side.
map to multiple frequency bands. For
details, see 4.1.2 SCG Carrier
Management.
Supported the SgNB change during an None

MeNB handover based on blind SCG
addition. For details, see 4.2 Mobility
Management in NSA DC.
Editorial Changes
l Optimized the description of the SgNB addition procedure triggered by the MeNB. For
details, see 4.2 Mobility Management in NSA DC.
l Added the description about whether the interference avoidance function takes effect.
For details, see 7.3 Activation Verification.
l Added the description of the times of event B1 measurement triggered by an NSA DC
UE for PSCell addition after automatic neighboring cell addition or X2 self-setup in
NSA DC. For details, see 4.1.2 SCG Carrier Management.
1.9 SRAN15.1 Draft A (2018-12-30)

This issue introduces the following changes to SRAN15.0 01 (2018-10-10).
Technical Changes
Added license control on the LTE and NR None

sides. For details, see 6.1 Licenses.
Added support for selection of QCI- Added the following parameter:

specific data split bearers. For details, see CellQciPara.NsaDcDefaultBearerMode
4.3.1 Data Split Policy Selection.
Added the following parameter to the
parameter disuse list:
NsaDcMgmtConfig.NsaDcDefaultBearer-
Mode, which is replaced by
CellQciPara.NsaDcDefaultBearerMode. In
later versions, the former parameter will be
deleted. Therefore, avoid using this parameter.

SingleRAN
Optimized the SINR threshold parameters Added the following parameters to the
used in uplink fallback to LTE. For parameter disuse list:
details, see 4.3.4 Uplink Fallback to l NRDUCellSrsMeasSinr.SrsSinrThld,
LTE. which is replaced by
NRDUCellSrsMeas.NsaUlFackToLteSinr
Thld. The former parameter will be
deleted in later versions.
l NRDUCellSrsMeasSinr.SrsSinrHyst,
which is replaced by
NRDUCellSrsMeas.NsaUlFackToLteSin
rHyst. In later versions, the former
parameter will be deleted.
Added support for this feature by the None

following micro base stations: BTS3911E
and BTS3912E. For details, see 6.3
Hardware.
Added NSA DC UE scheduling protection Added the following parameter:

based on the MCG cell load. For details, CellDlschAlgo.McgHighLoadThreshold
see 4.3.5 NSA DC UE Scheduling
Protection Based on MCG Cell Load.
Added the processing procedure when a None

UE supports both NSA networking and
SA networking. For details, see 4.1.2
SCG Carrier Management.
Added support for blind PSCell None

configuration. For details, see:
l 4.1 Carrier Management in NSA DC
l 7.2.1 Data Preparation
l 7.2.2 Using MML Commands
Added support for NSA DC PCC Added the

configuration. For details, see: NSA_PCC_ANCHORING_SWITCH
l 4.1 Carrier Management in NSA DC option to the
l 7.2.1 Data Preparation parameter.
l 7.2.2 Using MML Commands
Editorial Changes
Optimized the document structure.

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

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

This document applies to LTE FDD, LTE TDD, and NR.
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
2.3 Features in This Document

This document describes the following features.

SingleRAN
Description 2 About This Document
Feature ID Feature Name Section
MRFD-131122 NSA Networking based on l 4.1.1 MCG Carrier

EPC (LTE FDD) Management
l 4.1.2.1 Measurement-based
MRFD-131132 NSA Networking based on
PSCell Configuration
EPC (LTE TDD)
l 4.2 Mobility Management in
MRFD-131162 NSA Networking based on NSA DC
EPC (NR) l 4.3 NSA DC Data Split
l 4.4.1 Initial Power Control
l 4.5 Interference Avoidance
in NSA DC
l 4.6 NR Data Volume
Reporting
l 4.7 S-KgNB Update
MRFD-151223 EN-DC Performance 4.4.2 TDM Power Control

Enhancement (LTE FDD) 4.3.5 NSA DC UE Scheduling
MRFD-151233 EN-DC Performance Protection Based on MCG Cell
Enhancement (LTE TDD) Load
MRFD-151263 EN-DC Performance 4.4.2 TDM Power Control

Enhancement (NR)
LNOFD-151333 EN-DC Optimal Carrier 4.1.2.2 Blind PSCell

Selection Configuration
TDLNOFD-151504 EN-DC Optimal Carrier

Selection

SingleRAN
Description 3 Overview
3 Overview
3.1 Introduction
In EPC-based NSA networking, if a UE supports both LTE and New Radio (NR) non-
standalone (NSA) dual connectivity (DC), it can connect to both an LTE eNodeB and an NR
gNodeB, and use radio resources provided by these base stations for data transmission. Data
can be split between the two base stations. DC can be implemented after component carriers
(CCs) are aggregated separately on the eNodeB and gNodeB sides, as shown in Figure 3-1.
Figure 3-1 EPC-based NSA networking
3.2 Related Concept

MeNB
The master eNodeB (MeNB) of an NSA DC UE is the LTE eNodeB that serves the cell on
which a UE is currently camping. In this version, only an LTE eNodeB can be configured as
an MeNB.

SingleRAN
SgNB
The secondary gNodeB (SgNB) of an NSA DC UE is the NR gNodeB configured for the UE
through an RRC message sent by the MeNB. In this version, only an NR gNodeB can be
configured as an SgNB.
MCG
The master cell group (MCG) of an NSA DC UE is an LTE cell group configured on the LTE
side.
SCG
The secondary cell group (SCG) of an NSA DC UE is the NR cell group configured on the
NR side.
PSCell
The primary secondary cell (PSCell) of an NSA DC UE is a primary cell that is served by the
SgNB and configured for the UE through an RRC message sent by the MeNB. The PSCell
stays active so long as it is configured successfully.
PCell
The primary cell (PCell) of an NSA DC UE is a cell that is served by the MeNB and that the
UE is camping on.
CC
Component carriers (CCs) are the carriers that are aggregated for a UE.
PCC
The primary component carrier (PCC) is the carrier of the PCell.
PSCC
The primary secondary component carrier (PSCC) is the carrier of the PSCell.
SCC
A secondary component carrier (SCC) is a secondary carrier of the MeNB or SgNB.
SCell
A secondary cell (SCell) of an NSA DC UE is a cell configured for the UE through an RRC
message sent by the MeNB. This cell works at an SCC and provides the UE with additional
radio resources.
There is a PUCCH in each PCell and PSCell, but a PUCCH is not available in any SCell.

SingleRAN
Related Events
l Event A1
The signal quality of the serving cell becomes better than a specific threshold.
l Event A2
The signal quality of the serving cell becomes worse than a specific threshold.
l Event A3
The signal quality of a PCell's neighboring cell becomes offset better than the signal
quality of the PCell.
l Event A5
The signal quality of the serving cell becomes worse than threshold 1, and the signal
quality of a neighboring cell becomes better than threshold 2.
l Event B1
The signal quality of an inter-RAT neighboring cell becomes better than a threshold.
The threshold for event B1 is specified by the NrScgFreqConfig.NsaDcB1ThldRsrp
parameter.
3.3 Architecture
This feature can be deployed in the areas where LTE and NR network coverage overlaps. The
current version supports two network architectures: Option 3 and Option 3x. The network
architecture used depends on how the eNodeB/gNodeB and the EPC are interconnected.
Figure 3-2 Network architectures defined by 3GPP specifications
In Figure 3-2, the eNodeB is an MeNB, and the gNodeB is an SgNB. The user-plane data
supports both Option 3 and Option 3x architectures.
l In Option 3, the eNodeB is the data split anchor. As shown in Figure 3-3, data is split at
the PDCP layer of the MeNB to the RLC layer of the MeNB and the RLC layer of the
SgNB, and then aggregated at the PDCP layer of the UE side.

SingleRAN
– If only the eNodeB transmits the user-plane data, the data bearer is referred to as the
MCG bearer or MCG_Bearer_EUTRA_PDCP.
– If the eNodeB splits some of the user-plane data to the gNodeB and transmits the
remaining user-plane data, the data bearer is referred to as the master cell group
(MCG) split bearer.
Figure 3-3 MCG split bearer
l In Option 3x, the gNodeB is the data split anchor. The gNodeB can distribute the user-
plane data to the eNodeB and itself, which is referred to as the secondary cell group
(SCG) split bearer. As shown in Figure 3-4, data is split at the PDCP layer of the SgNB
to the RLC layer of the MeNB and the RLC layer of the SgNB, and then aggregated at
the PDCP layer of the UE side.
Figure 3-4 SCG split bearer

SingleRAN
Description 4 Principles
4 Principles
This feature is controlled by the NSA_DC_CAPABILITY_SWITCH option of the

NsaDcMgmtConfig.NsaDcAlgoSwitch parameter on the eNodeB side and the
NRCellAlgoSwitch.NsaDcSwitch parameter on the gNodeB side. This feature takes effect
only when both the eNodeB and gNodeB switches are turned on. To enable some UEs in idle
mode to display the NR indication, SIB2 on the LTE side needs to contain the
upperLayerIndication IE. The NsaDcMgmtConfig.UpperLayerIndicationSwitch parameter
specifies whether SIB2 contains this IE.
Table 4-1 lists the uplink and downlink frequency band combinations supported by NR in this
version.
Table 4-1 Uplink and downlink frequency band combinations supported by NR
RAT Uplink Frequency Band Downlink Frequency Band (MHz)

(MHz)
NR 3300–4200 3300–4200
TDD
NR 2496–2690 2496–2690
TDD
Table 4-2 provides an example of an NR and LTE frequency band combination. For details
about other frequency band combinations, see 3GPP TS 38.101: "NR; User Equipment (UE)
radio transmission and reception".
Table 4-2 Example of an NR and LTE frequency band combination (DC_1A-n77A

combination)
E-UTRA E-UTRA Uplink Frequency Downlink Frequency RAT

and NR and NR Band (MHz) Band (MHz)
DC Band Band
DC_1A- 1 1920–1980 2110–2170 LTE

n77A FDD

SingleRAN
E-UTRA E-UTRA Uplink Frequency Downlink Frequency RAT

and NR and NR Band (MHz) Band (MHz)
DC Band Band
n77 3300–4200 3300–4200 NR

TDD
4.1 Carrier Management in NSA DC

NSA DC transmits PDCP data to the RLC layers of the eNodeB and gNodeB. Different CCs
can be aggregated within the eNodeB. Carrier management in NSA DC involves MCG carrier
management and SCG carrier management.
4.1.1 MCG Carrier Management

MCG carrier management involves PCC Anchoring and SCC Management.
PCC Anchoring
The following descriptions apply only to the BTS3900, BTS5900, and Micro BTS3900.
The NSA DC PCC anchoring policy is specified by the
NSA_PCC_ANCHORING_SWITCH option of the NsaDcMgmtConfig.NsaDcAlgoSwitch
parameter and RsvdSwPara6_bit28 of the eNBCellRsvdPara.RsvdSwPara6 parameter. For
details about this reserved parameter, see 3900 & 5900 Series Base Station eNodeBFunction
Used Reserved Parameter List in 3900 & 5900 Series Base Station Product Documentation.
l When the NSA_PCC_ANCHORING_SWITCH option is deselected, the PCC
anchoring policy (priority) is the same as that for LTE carrier management. For details,
see the following sections in Carrier Aggregation in eRAN feature documentation:
– PCC Anchoring
– Carrier Management for RRC_IDLE UEs
– Duplex-Mode-Priority-based PCC Anchoring
– Load-based PCC Anchoring
l When the NSA_PCC_ANCHORING_SWITCH option is selected:
– When a UE switches from idle mode to connected mode or performs a necessary
incoming handover (for example, coverage-based inter-frequency handover) or
RRC connection reestablishment, the eNodeB determines whether the NSA DC
PCC priority (specified by the PccFreqCfg.NsaPccAnchoringPriority parameter)
of the LTE cell accessed by the UE is the highest. If the NSA DC PCC priority is
not the highest, a PCC anchoring procedure is triggered. If it is the highest, a PCC
anchoring procedure is not triggered.
The eNodeB delivers measurement configurations for PCC anchoring, based on the
setting of the eNBCellRsvdPara.RsvdU8Para35 parameter. If the parameter is set
to a value other than 255, the eNodeB delivers the A1 measurement configuration
to the UE. If the parameter is set to 255, the eNodeB delivers the A5 measurement
configuration without sending the A1 measurement configuration. For details about
this reserved parameter, see 3900 & 5900 Series Base Station eNodeBFunction
Used Reserved Parameter List in 3900 & 5900 Series Base Station Product
Documentation.

SingleRAN
n If the UE sends an A1 measurement report, the eNodeB selects the LTE

frequencies with higher NSA DC PCC priorities to deliver the A5 inter-
frequency measurement configuration. The event A5 threshold 1 is always –
43 dBm, and the threshold 2 is specified by the
PccFreqCfg.NsaDcPccA4RsrpThld parameter.
n If the UE sends an A5 measurement report, the eNodeB triggers a PCC
anchoring procedure to hand the UE over to a neighboring cell with a higher
NSA DC PCC priority.
○ If the NSA DC PCC is configured with an SCC, an SCC addition
procedure for carrier aggregation (CA) is performed.
○ If the NSA DC PCC is not configured with an SCC, CA cannot be
performed.
– When a UE switches from connected mode to idle mode:
n If RsvdSwPara6_bit28 of the eNBCellRsvdPara.RsvdSwPara6 parameter is
set to 1, the eNodeB sorts the candidate NSA DC PCCs in descending order by
priority, considers the priorities as dedicated priorities, and sends the priority
information to the UE through the IMMCI IE in the RRC Release message. For
details about this reserved parameter, see 3900 & 5900 Series Base Station
eNodeBFunction Used Reserved Parameter List in 3900 & 5900 Series Base
Station Product Documentation.
If dedicated cell reselection priorities based on the PLMN of the serving cell
are configured on the eNodeB, the NSA DC PCC anchoring policy for UEs in
idle mode is specified by RsvdSwPara6_bit29 of the
eNBCellRsvdPara.RsvdSwPara6 parameter. If this parameter is set to 0,
PLMN priorities are used for NSA DC PCC anchoring for UEs in idle mode.
For details about cell reselection based on PLMN priorities, see RAN Sharing
in eRAN Feature Documentation. If this parameter is set to 1, the NSA DC
PCC anchoring policy is used for NSA DC UEs in idle mode. For details about
this reserved parameter, see 3900 & 5900 Series Base Station eNodeBFunction
Used Reserved Parameter List in 3900 & 5900 Series Base Station Product
Documentation.
n If RsvdSwPara6_bit28 of the eNBCellRsvdPara.RsvdSwPara6 parameter is
set to 0, the eNodeB sends the priorities determined by carrier management for
UEs in idle mode through the IMMCI IE of the RRC Release message to the
UE. For details about this reserved parameter, see 3900 & 5900 Series Base
Station eNodeBFunction Used Reserved Parameter List in 3900 & 5900 Series
Base Station Product Documentation.
Upon reception of the dedicated frequency priority information, the UE
preferentially reselects the frequency with the highest priority based on the
dedicated priority information. For details about cell reselection based on dedicated
priorities, see Idle Mode Management in eRAN Feature Documentation.
– When an NSA DC-capable UE camps on a non-candidate PCC or a low-priority
PCC, it can quickly return to a high-priority candidate PCC if the
PERIODIC_PCC_ANCHORING_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is selected, which controls
periodic PCC anchoring. The period and UE traffic threshold settings are the same
as those for periodic SCG configuration based on UE traffic volume. For details,
see 4.1.2.1 Measurement-based PSCell Configuration. If the
VOLUME_BASED_PERIODIC_TRIG_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is deselected, the eNodeB

SingleRAN
triggers periodic PCC anchoring when a period arrives, without considering the UE
traffic volume.
– When a UE in NSA DC camps on a low-priority PCC and the
NSA_DC_STATE_PCC_ANCHORING_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is deselected, the UE will not be
handed over to a high-priority PCC.
NOTE
l During a PCC anchoring procedure, if the target cell does not meet the requirements of
NSA DC, NSA DC is unusable after the UE is handed over to the target cell.
l When an NSA DC-capable UE accesses a non-anchor cell with the NSA DC function
disabled, if the NSA_PCC_ANCHORING_SWITCH option is selected, the eNodeB
initiates a UE capability query to obtain the E-UTRA-NR Dual Connectivity (EN-DC)
capability of the UE. The NrScgFreqConfig MO defines the association between the
eNodeB PCC and SCG ARFCN information. The eNodeB determines the intersection of
the EN-DC band combinations obtained from the UE and the association combinations
between the eNodeB PCC and SCG ARFCN information. If the intersection is not
empty, the PCC anchoring decision-making procedure is triggered. If the intersection is
empty, no PCC anchoring is triggered.
l If dedicated priorities are required in the RRC Release message sent by the MeNB to a
UE, and the SPID-specific dedicated priorities, NSA DC PCC priorities, and mobility
load balancing (MLB) priorities are configured on the MeNB, the MeNB sorts these
priorities in descending order (SPID-specific dedicated priorities > NSA DC PCC
priorities > MLB priorities) and fills them in the RRC Release message.
l If the eNodeB has not obtained the NSA DC capability information of the UE when
sending the RRC Release message, the RRC Release message will not carry the NSA
DC PCC priorities. An example scenario is that the eNodeB releases the RRC
connection after a UE in idle mode initiates a tracking area update (TAU).
l If periodic PCC anchoring and LTE MLB are both enabled, the eNodeB may hand over
an NSA DC UE to a cell of a lower-priority PCC by means of MLB and then
periodically triggers PCC anchoring. In this case, ping-pong handovers may occur.
Therefore, when periodic PCC anchoring is enabled, it is recommended that the
CellMlbUeSel.NsaDcUeSelectionStrategy parameter (UE selection by MLB) be set to
LTE_UE_PREFERRED, or a high load balancing handover threshold be set for NSA
DC UEs in the handover policy group. In this way, NSA DC UEs will not be handed
over to cells with low-priority PCCs by means of MLB.
The following descriptions apply only to the SRAN13.1 BTS3202E, BTS3203E, and
BTS3205E.
The NSA DC PCC anchoring policy is specified by RsvdSwPara6_bit25 of the
eNBCellRsvdPara.RsvdSwPara6 parameter. For details about this reserved parameter, see
3900 & 5900 Series Base Station eNodeBFunction Used Reserved Parameter List in 3900 &
5900 Series Base Station Product Documentation.
l When RsvdSwPara6_bit25 is set to 0, the PCC anchoring policy (priority) is the same
as that for LTE carrier management. For details, see the following sections in Carrier
Aggregation in eRAN feature documentation:
– PCC Anchoring
– Carrier Management for RRC_IDLE UEs
– Duplex-Mode-Priority-based PCC Anchoring
– Load-based PCC Anchoring
l When RsvdSwPara6_bit25 is set to 1:
– When a UE switches from idle mode to connected mode, the eNodeB determines
whether the UE supports NSA DC based on UE capabilities en-DC-r15:supported.

SingleRAN
If the UE supports NSA DC, the eNodeB performs NSA DC PCC anchoring for the
UE.
The eNodeB delivers to the UE inter-frequency measurement configurations related
to event A5 for a maximum of three LTE frequencies configured as candidate NSA
DC PCCs. When the UE sends event A5 measurement reports, the eNodeB triggers
a PCC anchoring procedure to hand over the UE to the neighboring cell on the
target NSA DC PCC frequency.
The downlink EARFCNs of candidate NSA DC PCCs are specified by the
eNBRsvdPara.RsvdPara79, eNBRsvdPara.RsvdPara80, and
eNBRsvdPara.RsvdPara81 parameters. The event A5 threshold 1 is always –43
dBm, and the threshold 2 is specified by the eNBRsvdPara.RsvdPara72 parameter.
For details about these reserved parameters, see 3900 & 5900 Series Base Station
eNodeBFunction Used Reserved Parameter List in 3900 & 5900 Series Base
Station Product Documentation.
– When a UE switches from connected mode to idle mode, the eNodeB sorts the
candidate NSA DC PCCs in descending order of priority, considers the priorities as
dedicated priorities, and sends the priority information to the UE through the
IMMCI IE in the RRC Release message. Upon reception of the dedicated frequency
priority information, the UE preferentially reselects to the frequency with the
highest NSA DC PCC priority based on the dedicated priority information. For
details about cell reselection based on dedicated priorities, see Idle Mode
Management in eRAN feature documentation.
NOTE
l During a PCC anchoring procedure, if the target cell does not meet the requirements of NSA
DC, NSA DC is unusable after the UE is handed over to the target cell.
l If dedicated priorities are required in the RRC Release message sent by the eNodeB to a UE,
and the SPID-specific dedicated priorities, NSA DC PCC priorities, and mobility load
balancing (MLB) priorities are configured on the eNodeB, the eNodeB sorts these priorities in
descending order (SPID-specific dedicated priorities > NSA DC PCC priorities > MLB
priorities) and fills them in the RRC Release message.
l For NSA DC UEs, the eNodeB does not deliver inter-frequency or inter-RAT MR/MDT
measurement configurations. This prevents the impact on NSA DC PCC measurement for the
UEs.
SCC Management
The MCG's SCC selection is the same as that for LTE carrier management. For details, see
Carrier Aggregation in eRAN feature documentation.
When an NSA DC-capable UE is not in the NSA DC state:
Both of the following conditions must be met to trigger the activation or periodic addition of
LTE CA SCCs:
l Data volume buffered at the RLC layer > max (Uu data rate at the RLC layer x
CaMgtCfg.ActiveBufferDelayThd, CaMgtCfg.ActiveBufferLenThd)
l Delay of the first RLC PDU > CaMgtCfg.ActiveBufferDelayThd
When an NSA DC-capable UE is in the NSA DC state:
Both of the following conditions must be met to trigger the activation of LTE CA SCCs:
l Data volume buffered at the RLC layer > max (Uu data rate at the RLC layer x
NsaDcMgmtConfig.NsaDcLteScellActBfrDelThld,
NsaDcMgmtConfig.NsaDcLteScellActBfrLenThld)

SingleRAN
l Delay of the first RLC PDU > NsaDcMgmtConfig.NsaDcLteScellActBfrDelThld
4.1.2 SCG Carrier Management

SCG carrier management involves only PSCell configuration. After the MeNB PCC
anchoring procedure is completed, PSCell configuration will be triggered for an NSA DC UE
not configured with a PSCell if the UE is not making any emergency call. After the PSCell is
added, the SgNB does not proactively trigger handovers for PSCell switching and only
performs coverage-based PSCell changes.
NOTE
If the UE supports both NSA and SA, the UE preferentially performs LTE-NR interoperability based on
SA networking and returns to the NR cell. For details about LTE-NR interoperability procedures, see
Interoperability Between E-UTRAN and NG-RAN.
This version does not support direct signaling exchange between the SgNB and a UE, and
signaling needs to be forwarded by the MeNB. PSCell configuration is triggered by the
MeNB. The MeNB performs measurement-based PSCell configuration or blind PSCell
configuration.
l If the NSA_BLIND_SCG_ADDITION_SWITCH option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is deselected, measurement-based
PSCell configuration is performed.
l If the NSA_BLIND_SCG_ADDITION_SWITCH option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is selected and the
NrNRelationship.BlindConfigIndicator parameter is set to TRUE for a neighboring
NR cell, the eNodeB directly sends an SCG addition request to trigger blind PSCell
configuration during initial UE access, during the preparation for an inter-MeMB
handover, or after a handover from an LTE-only cell to an NSA DC cell. In this case, the
eNodeB does not send a B1 measurement configuration message to the UE.
NOTE
l It is recommended that the NrNRelationship.BlindConfigIndicator parameter be set to

TRUE when the LTE cell and the neighboring NR cell are co-sited and cover the same area or
when the coverage area of the neighboring NR cell is larger than that of the LTE cell.
Otherwise, it is recommended that this parameter not be set to TRUE to prevent NR access
failure due to no NR coverage.
l During initial network access, a measurement-based or blind SCG addition can be triggered
only if the QCI for the default bearer specified in the Initial Context Setup Req message
supports MCG split bearer or SCG split bearer. If the QCIs for subsequently established
bearers support MCG split bearer or SCG split bearer, SCG additions can be triggered
periodically based on the traffic volume.
l The RcvA2CfgSccSwitch option of the CaMgtCfg.CellCaAlgoSwitch parameter specifies
whether the eNodeB triggers an SCG addition during a coverage-based inter-frequency
handover initiated after receiving an A2 measurement report from an NSA DC UE. If this
option is selected, an SCG addition is triggered. If this option is deselected, an SCG addition is
not triggered.
4.1.2.1 Measurement-based PSCell Configuration

Figure 4-1 shows the measurement-based PSCell configuration procedure.

SingleRAN
Figure 4-1 Measurement-based PSCell configuration procedure
Measurement Configuration Delivery

After the MeNB filters frequencies based on UE capabilities, it can configure multiple
frequencies for the SCG. The NrScgFreqConfig.ScgDlArfcn and
NrScgFreqConfig.ScgDlArfcnPriority parameters specify the ARFCN and priority,
respectively, for a frequency. The rules for filling in measurement frequencies are as follows:
l If the frequencies have different priorities, the highest-priority frequency is set as the
first measurement frequency, the second-highest-priority frequency is set as the second
measurement frequency, and so on.
l If the frequencies are set with the same priority or are not set with any priority, the
frequency sequence in measurement configuration messages is specified randomly.
l If some frequencies are set with priority while others are not, the frequencies whose
priorities are not set have the lowest priorities by default.
NOTE
If the frequency specified by NrScgFreqConfig.ScgDlArfcn can belong to multiple NR frequency

bands and is not configured with a frequency band through the NrMfbiFreq MO, the MeNB filters out
this frequency.
In hybrid NSA&SA networking, the MeNB filters out the SCG frequencies serving the
neighboring NR cells only in SA networking based on the setting of the
NrExternalCell.NrNetworkingOption parameter.
Measurement Reporting
A UE performs measurement according to the neighboring NR frequency measurement
configuration message delivered by the MeNB. If the measured RSRP value is greater than
the value of NrScgFreqConfig.NsaDcB1ThldRsrp and the time-to-trigger exceeds
NrScgFreqConfig.NrB1TimeToTrigger, the UE sends an event B1 measurement report to
the MeNB.

SingleRAN
X2-based PSCell Addition

After receiving the event B1 measurement report about neighboring NR frequencies, the
MeNB triggers an X2-based PSCell addition procedure.
1. After the MeNB delivers a neighboring NR frequency measurement configuration
message, the MeNB starts a waiting timer to wait for reporting of measurement reports
of neighboring NR frequencies.
– If the measurement reports of all the neighboring NR frequencies are received
before the timer expires, the MeNB filters out neighboring NR cells in SA
networking based on the setting of NrExternalCell.NrNetworkingOption. Then,
from the remaining neighboring NR cells, the MeNB identifies the SgNB serving
the neighboring NR cell with the strongest signal quality and using the highest-
priority frequency, and fills the measurement results of all the neighboring NR
frequencies under this SgNB in the candidateCellInfoListMN field of the MeNB to
SgNB Container IE in the SGNB ADDITION REQUEST message for reporting.
– If only the measurement reports of some neighboring NR frequencies are received
before the timer expires, the MeNB filters out neighboring NR cells in SA
networking based on the setting of NrExternalCell.NrNetworkingOption. Then,
from the remaining neighboring NR cells, the MeNB identifies the SgNB serving
the neighboring NR cell with the strongest signal quality and using the highest-
priority frequency, and fills the received measurement results of neighboring NR
frequencies under this SgNB in the candidateCellInfoListMN field of the MeNB to
SgNB Container IE in the SGNB ADDITION REQUEST message for reporting.
For an NSA DC-capable UE, the NR neighbor relationship needs to be added or the NSA
DC X2 interface needs to be automatically established when NSA DC is initiated for the
first time. This results in longer time required than that in the case of manual
configuration. In addition, the PSCell addition cannot be completed in one event B1
measurement. For a UE that initiates NSA DC for the first time, PSCell addition can be
implemented only after multiple measurements are triggered:
– If either the NR neighbor relationship is not added or the NSA DC X2 interface is
not set up, event B1 measurement needs to be performed twice. The first
measurement is used to add the NR neighbor relationship or set up the NSA DC X2
interface, and the second measurement is used to add the PSCell.
– When neither the NR neighbor relationship is added nor the NSA DC X2 interface
is set up, event B1 measurement needs to be performed for three times. The first
measurement is used to add the NR neighbor relationship, the second measurement
is used to set up the NSA DC X2 interface, and the third measurement is used to
add the PSCell.
After the NR neighbor relationship is added and the NSA DC X2 interface is
automatically set up, only one event B1 measurement needs to be triggered to add the
PSCell. For details about automatic neighboring cell addition, see ANR in eRAN feature
documentation. For details about NSA DC X2 self-setup, see X2 and S1 Self-
Management in NSA Networking.
2. The SgNB selects the cell with the strongest signal quality from the NR cells carried by
the candidateCellInfoListMN field as the PSCell.
If no cell in the sCellToAddModListSCG and measResultsForNR IEs meets requirements, the

SgNB notifies the MeNB that no PSCell can be added.
The NSA_DC_VOLUME_BASED_SCG_ADD_SW option of the

NsaDcMgmtConfig.NsaDcAlgoSwitch parameter specifies whether the MeNB triggers an

SingleRAN
SgNB addition based on the data volume when an NSA DC UE performs initial access,
incoming RRC connection reestablishment, or incoming handover.
To prevent SgNB configurations from not being triggered after an initial SgNB configuration
failure or an SgNB deletion, the MeNB starts the SgNB addition interval timer (specified by
NsaDcMgmtConfig.ScgAdditionInterval) to trigger SgNB configurations based on UE data
volume. Whether the UE data volume meets requirements is determined by
NsaDcMgmtConfig.ScgAdditionBufferLenThld and
NsaDcMgmtConfig.ScgAdditionBufferDelayThld.
l When the NsaDcMgmtConfig.ScgAdditionBufferLenThld parameter is set to 0 and the
UE is transmitting data, an SgNB configuration will be triggered.
l When the NsaDcMgmtConfig.ScgAdditionBufferLenThld parameter is set to a value
other than 0 and both the following conditions are met, an SgNB configuration will be
triggered:
– Data volume buffered at the RLC layer > max (Uu data rate at the RLC layer x
NsaDcMgmtConfig.ScgAdditionBufferDelayThld,
NsaDcMgmtConfig.ScgAdditionBufferLenThld)
– Delay of the first RLC protocol data unit (PDU) >
NsaDcMgmtConfig.ScgAdditionBufferDelayThld
If the SgNB configuration fails, the SCG addition interval timer is restarted to trigger another
SgNB configuration. The process is repeated until the SgNB configuration succeeds. Then,
the MeNB stops the timer, which automatically resets.
It is recommended that NsaDcMgmtConfig.ScgAdditionInterval be set to a value greater
than NRDUCellQciBearer.UeInactivityTimer or
NsaDcMgmtConfig.ScgAdditionBufferLenThld be set to a value greater than the buffer data
volume of PDCP status report packets on the MeNB. The purpose is to avoid SgNB addition
and release attempts when no data is transmitted on the LTE and NR sides. After the SgNB is
released due to the expiry of the inactivity timer on the NR side, the MeNB sends PDCP
status report data packets to the UE. When the buffer size of the PDCP status report data
packets at the RLC layer of the MeNB exceeds
NsaDcMgmtConfig.ScgAdditionBufferLenThld, SgNB addition based on the data volume is
triggered.
If SgNBs need to be added for services with a small traffic volume (such as web page
browsing), the VOLUME_BASED_PERIODIC_TRIG_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter should be deselected. In this case, periodic
SgNB addition will be triggered without considering the UE traffic volume.
NOTE
When the VOLUME_BASED_PERIODIC_TRIG_SW option of the

NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is deselected and the UE inactivity timer on the NR
side (specified by the NRDUCellQciBearer.UeInactivityTimer parameter) expires, SgNB addition and
release may be performed repeatedly. To avoid this problem, it is recommended that
NRDUCellQciBearer.UeInactivityTimer be set to 0.
PSCell for VoLTE UEs

For VoLTE UEs, three independent PSCell management modes are supported. The PSCell
management mode to be used is specified by the
NsaDcMgmtConfig.VolteUeScgMgmtStrategy parameter.
l If this parameter is set to VOLTE_PREFERRED and the SgNB has been configured,
the eNodeB releases the SgNB immediately after a VoLTE service is initiated. If no

SingleRAN
SgNB is configured, the eNodeB will not trigger an SgNB addition before the VoLTE
service is released. If the NSA_DC_VOLUME_BASED_SCG_ADD_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is deselected, the eNodeB will trigger
an SgNB addition immediately after the VoLTE service is released.
l If this parameter is set to ADAPTIVE and the SINR of a newly initiated VoLTE service
is smaller than the value of NsaDcMgmtConfig.UlQualityThldForScgRelease or the
uplink/downlink packet loss rate of the VoLTE service of QCI 1 is greater than the value
of NSADCMGMTCONFIG.VoltePlrThldForScgRelease, the eNodeB immediately
releases the SgNB if it has been added. If no SgNB has been configured, the eNodeB
will not trigger an SgNB addition before the VoLTE service is released. If the
NSA_DC_VOLUME_BASED_SCG_ADD_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is deselected, the eNodeB will trigger
an SgNB addition immediately after the VoLTE service is released.
l If this parameter is set to VOLTE_SCG_COEXISTENCE, the eNodeB does not
perform the processing in the preceding two scenarios for VoLTE services.
When NsaDcMgmtConfig.VolteUeScgMgmtStrategy is set to
VOLTE_SCG_COEXISTENCE, the VOLTE_NSA_DC_IF_NR_MEAS_SW option
of the NsaDcMgmtConfig.NsaDcAlgoSwitch parameter specifies whether the eNodeB
delivers NR B1 measurement configuration for SgNB addition to UEs running VoLTE
services. If this option is deselected, the eNodeB does not deliver NR B1 measurement
configuration for SgNB addition, thereby preventing VoLTE services from being
affected. If this option is selected, the eNodeB delivers NR B1 measurement
configuration for SgNB addition.
4.1.2.2 Blind PSCell Configuration

The bind PSCell configuration procedure works as follows:
1. If there is a blind-configurable neighboring NR cell on a high-priority neighboring NR
frequency configured on the eNodeB, the eNodeB selects the gNodeB serving this NR
cell to initiate an SgNB addition request. If there are multiple blind-configurable
neighboring NR cells on a high-priority neighboring NR frequency configured on the
eNodeB, the eNodeB selects the gNodeB serving the cell ranking at the top to initiate an
SgNB addition request.
2. If there is no blind-configurable neighboring NR cell on a high-priority neighboring NR
frequency but there is one on a low-priority neighboring NR frequency configured on the
eNodeB, the eNodeB selects the high-priority neighboring NR frequency and delivers
measurement configuration to the UE. If the UE does not send a measurement report on
the high-priority neighboring NR frequency before the timer expires, the eNodeB selects
the blind-configurable neighboring NR cells served by the low-priority neighboring NR
frequency to initiate blind PSCell configuration.
3. If blind PSCell configuration fails, the eNodeB selects a frequency without a blind-
configurable neighboring NR cell to initiate a measurement-based PSCell configuration
procedure. If no qualified frequency is available for measurement, the eNodeB does not
check whether neighboring NR cells support blind PSCell configuration when a PSCell
configuration is triggered next time based on UE data volume. Instead, a measurement-
based PSCell configuration procedure is directly performed. For details, see 4.1.2.1
Measurement-based PSCell Configuration.

SingleRAN
NOTE
In Option 3x, data forwarding is not supported in the following scenarios:

l After a UE performing NSA DC services completes an S1-based inter-MeNB handover, blind
PSCell configuration is performed.
l After an NSA DC-capable UE not performing NSA DC services completes an S1-based inter-MeNB
handover, blind PSCell configuration is performed.
4.1.2.3 SMTC Configuration of the PSCell

The NrNFreq MO on the eNodeB side is used to configure the SSB information
corresponding to an NR frequency. The information is contained in B1 measurement
configuration to instruct a UE to correctly scan the SSB. It is also used to calculate the GAP
position for B1 measurement to ensure that the GAP period contains the SSB. SSB
information includes SSB Period and SSB Offset.
NOTE
If there are multiple NR frequencies, they must have the same gNodeBParam.FrameOffset setting.
SSB Period
The SSB period is specified by the NRDUCell.SsbPeriod parameter. If multiple neighboring
NR cells work on the same frequency in the NR network and have different SSB periods, it is
recommended that the eNodeB use the maximum SSB period as the SSB period of the NR
frequency.
If the duration specified by this parameter is longer than 20 ms, some NSA DC UEs may have
compatibility problems and fail to find the NR network. RsvdSwPara3_bit24 of the
eNBRsvdPara.RsvdSwPara3 parameter can be set to 1 to solve this problem. In this case, the
eNodeB sends an RRC Connection Reconfiguration message to an NSA DC UE to assist in
NR network search. For details about this reserved parameter, see 3900 & 5900 Series Base
Station eNodeBFunction Used Reserved Parameter List in 3900 & 5900 Series Base Station
Product Documentation.
SSB Offset
This parameter can be set in two scenarios: LTE time synchronization and LTE frequency
asynchronization. The LST CLKSYNCMODE command can be executed to query the clock
synchronization mode of a base station.
l LTE time synchronization
a. The SSB offset is calculated based on the gNodeB frame offset.
i. If gNodeBParam.FrameOffset is less than or equal to 261120, the SSB offset
is calculated as follows: SSB offset = (gNodeBParam.FrameOffset/30720)
MOD NrNFreq.SsbPeriod
ii. If gNodeBParam.FrameOffset is greater than or equal to 275943, the SSB
offset is calculated as follows: SSB offset = (gNodeBParam.FrameOffset/
30720 – 10 + NrNFreq.SsbPeriod) MOD NrNFreq.SsbPeriod
b. The SSB offset is corrected based on the eNodeB frame offset.
On the eNodeB side, if the value of Frame Offset Effect Value in the DSP
CELLFRAMEOFFSET command output is not 0, the SSB offset is calculated as
follows: SSB offset = (SSB offset – 0.5 + NrNFreq.SsbPeriod) MOD
NrNFreq.SsbPeriod

SingleRAN
c. The previous calculation result is rounded down to obtain the SSB offset.
l LTE frequency synchronization
Retain the default value 0.
4.2 Mobility Management in NSA DC
4.2.1 Mobility Policies in NSA DC

This version supports data forwarding during SgNB modification, change, and release. For
details, see 3GPP TS 37.340 "E-UTRA and NR; Multi-connectivity; Stage-2".
The MeNB handover triggering and decision-making mechanisms for NSA DC UEs are the
same as those for LTE-only UEs. Separate intra-frequency/inter-frequency/inter-RAT
handover thresholds can be configured for NSA DC UEs. For example, in an inter-frequency
handover scenario, QCI-specific independent handover policy groups must be first specified
using the CellQciPara.NsaDcInterFreqHoGroupId parameter, and then inter-frequency
handover thresholds must be configured for the corresponding handover policy groups
(specified by the InterFreqHoGroup.InterFreqHOGroupId parameter). Then, independent
coverage-based inter-frequency handover thresholds for A2 and A4 can be configured for
NSA DC UEs in a handover policy group specified by the
InterFreqHoGroup.InterFreqHOGroupId parameter. The configurations for intra-frequency
handover are similar to those for inter-RAT handover. Different policy group IDs can be
configured for LTE-only UEs and NSA DC UEs, as listed in the following table. Accordingly,
different handover thresholds can be configured for LTE-only UEs and NSA DC UEs.
Handover Policy Group on QCI-specific Handover Policy Group for NSA DC

the LTE side UEs
Intra-frequency handover CellQciPara.NsaDcIntraFreqHoGroupId

policy group
Inter-frequency handover CellQciPara.NsaDcInterFreqHoGroupId

policy group
Inter-RAT common policy CellQciPara.NsaDcInterRatHoCommGroupId

group
LTE-to-UTRAN handover CellQciPara.NsaDcUtranHoGroupId

policy group
LTE-to-GERAN handover CellQciPara.NsaDcGeranHoGroupId

policy group
For details about the common procedures for LTE mobility management, see Mobility
Management in Connected Mode in eRAN feature documentation.
For details about the common procedures for NR mobility management, see Mobility
Management in 5G RAN feature documentation.

SingleRAN
4.2.2 Mobility Procedures in NSA DC

Figure 4-2 and Table 4-3 provide NSA DC mobility management overview and
corresponding procedures. The SgNB is responsible for its mobility management, including
measurement control and RRC connection reconfiguration. The MeNB forwards signaling
messages between the UE and the SgNB.
Figure 4-2 Overview of NSA DC mobility management
Table 4-3 Procedures for NSA DC mobility

Mobility Scenario Procedure
SgNB addition SgNB Addition Initiated by the MeNB
SgNB modification SgNB Modification Initiated by the SgNB and SgNB

Modification Initiated by the MeNB
MeNB handovera Intra-MeNB Handover Without an SgNB Change Initiated by

the MeNB
SgNB change SgNB Change Initiated by the SgNB
MeNB handoverb Inter-MeNB Handover Without an SgNB Change Initiated by

the MeNB
SgNB release SgNB Release Initiated by the MeNB/SgNB
SgNB Addition Initiated by the MeNB

Figure 4-3 shows the procedure for adding an SgNB. For details about the triggering
conditions and configuration, see 4.1.2 SCG Carrier Management.

SingleRAN
Figure 4-3 SgNB addition procedure
1. After receiving the B1 measurement report, the MeNB triggers an SgNB addition
procedure. The MeNB adds the NR cells in the measurement report to the SgNB Addition
Request message and sends this message to the SgNB. The SgNB selects the NR cell with the
highest RSRP from the report. The request message carries the bearer type (MCG split bearer
or SCG split bearer) and E-RAB information (E-RAB parameters and TNL transport address).
The SCG-ConfigInfo IE in this message also includes the MCG configuration (DRB
configuration, cell configuration, and SCG bearer encryption algorithm) and UE capabilities.
The SgNB may reject the request. If the request is accepted, the corresponding radio bearer is
established.
2. After the admission is complete and the SgNB allocates resources, the SgNB returns an
SgNB Addition Request Acknowledge message to the MeNB. The SCG-Config IE in this
message carries the SCG radio resource configuration. For the MCG split bearer type, this IE
contains the SgNB GTP Tunnel Endpoint address. For the SCG split bearer type, this IE
contains the S1 DL TNL of the E-RAB.
3. The MeNB sends an RRC Connection Reconfiguration message to the UE. This message
contains the NR RRC configuration message.
4. After receiving the RRC Connection Reconfiguration message, the UE completes

reconfigurations. It then returns an RRC Connection Reconfiguration Complete message to
the MeNB, including an NR RRC response message. If the UE fails to complete the

SingleRAN
configurations specified in the RRC Connection Reconfiguration message, it performs the

reconfiguration failure procedure.
5. The MeNB informs the SgNB that the UE has completed the reconfiguration procedure
successfully through an SgNB Reconfiguration Complete message. This message includes the
NR RRC response message.
6. If the bearers configured for the UE require SCG radio resources, the UE performs
synchronization towards the SgNB PSCell and initiates random access to the SgNB PSCell.
7-8. In a bearer type change scenario, data forwarding is implemented between the MeNB and
the SgNB to reduce the service interruption duration.
9-12. For the SCG split bearer type, the user-plane path between the SgNB and the EPC is
updated. Specifically, the MeNB sends an E-RAB Modification Indication message to the
MME, instructing the MME to set up the E-RAB S1-U interface with the SgNB.
For details about the signaling procedure, see 3GPP TS 37.340 "E-UTRA and NR; Multi-
connectivity; Stage-2".
NOTE
l When the eNodeB sends an E-RAB Modification Indication message to the MME, if the MME does
not respond or replies with a failure message, the UE network connection rolls back to LTE only
after the timer for waiting for an S1 message expires. The eNodeB initiates an SgNB addition again
only when the conditions for adding an SgNB are met.
l In NSA networking, LTE DRX and NR DRX of NSA DC UEs work separately. After an SgNB is
successfully added, LTE DRX parameters are set through the DRXPARAGROUP MO specified by
CellQciPara.NsaDcDrxParaGroupId. After the SgNB is released, LTE DRX parameters for this
UE are set through the DRXPARAGROUP MO specified by CellQciPara.DrxParaGroupId.
Intra-MeNB Handover Without an SgNB Change Initiated by the MeNB

As shown in Figure 4-4, for an intra-MeNB handover, if NSA DC is enabled in the target
MeNB cell and an X2 link has been established between the target MeNB and the SgNB, an
intra-MeNB handover without an SgNB change will be performed.

SingleRAN
Figure 4-4 Intra-MeNB handover without an SgNB change initiated by the MeNB
1-2. The MeNB delivers an LTE intra-frequency or inter-frequency measurement control

message to the UE. The UE sends an intra-frequency or inter-frequency measurement report
to the MeNB. After receiving the measurement report, the MeNB decides to trigger an intra-
MeNB handover. The MeNB sends an SgNB Modification Request message to the SgNB,
instructing the SgNB to update the encryption parameters. This message contains the change
in UE context information such as encryption parameters used after an LTE cell handover.
The SgNB completes reconfigurations and returns a response.
3-5. The UE is handed over to the new primary LTE cell.
6-7. The UE initiates random access to the source SgNB cell according to the reconfiguration
information delivered by the MeNB.
Inter-MeNB Handover Without an SgNB Change Initiated by the MeNB

As shown in Figure 4-5, for an X2-based inter-MeNB handover, if NSA DC is enabled in the
target MeNB cell and an X2 link has been established between the target MeNB and the
SgNB, an X2-based inter-MeNB handover without an SgNB change will be performed.

SingleRAN
Figure 4-5 Inter-MeNB handover without an SgNB change initiated by the MeNB
1-2. The S-MeNB delivers an LTE A3/A4 measurement configuration message to the UE.
The UE sends an A3/A4 measurement report to the S-MeNB. After receiving the
measurement report, the S-MeNB decides to initiate an inter-MeNB handover.
3-8. The S-MeNB sends a handover request to the T-MeNB. The T-MeNB performs SgNB
addition. After the SgNB addition is completed, the S-MeNB releases the SgNB. If blind
PSCell configuration is enabled on the T-MeNB and the blind PSCell configuration conditions
are met, the T-MeNB directly sends an SgNB Add Req message to the SgNB that serves the
blind-configurable neighboring NR cell. If this SgNB is different from the source SgNB, the
procedure is called the inter-MeNB handover with an SgNB change.
9-13. The S-MeNB sends an inter-eNodeB handover command to the UE. The UE accesses
the target LTE cell and initiates random access to the SgNB. The T-MeNB returns a
configuration complete message to the SgNB.
14-16. The T-MeNB initiates a path switch to the core network and sends a context release
request to the S-MeNB. The S-MeNB sends a context release request to the SgNB.
S1-based Inter-MeNB Handover Without an SgNB Change Initiated by the

MeNB
As shown in Figure 4-6, during an S1-based inter-MeNB handover without an SgNB change,
if the target MeNB does not support NSA DC or does not support DC setup with the source
SgNB cell, an SgNB addition procedure will not be initiated. This function is controlled by
the S1_HO_DATA_FORWARDING_SW option of the

SingleRAN
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter. If this option is selected, this function

takes effect. By default, this option is selected.
Figure 4-6 S1-based inter-MeNB handover without an SgNB change initiated by the MeNB
1-2. The S-MeNB delivers an LTE A3/A4 measurement configuration message to the UE.
The UE sends an A3/A4 measurement report to the S-MeNB. After receiving the
measurement report, the S-MeNB decides to initiate an inter-MeNB handover.
3-10. The S-MeNB sends an S1-based handover request to the core network. The T-MeNB
performs SgNB addition. After the SgNB addition is completed, the S-MeNB releases the
SgNB. If blind PSCell configuration is enabled on the T-MeNB and the blind PSCell
configuration conditions are met, the T-MeNB directly sends an SgNB Add Req message to
the SgNB that serves the blind-configurable neighboring NR cell. If this SgNB is different
from the source SgNB, the procedure is called the inter-MeNB handover with an SgNB
change. If the T-MeNB fails to add the SgNB in steps 5 and 6, data forwarding from the
SgNB to the T-MeNB is performed for bearers in Option 3x.

SingleRAN
11-15. The S-MeNB sends an inter-eNodeB handover command to the UE. The UE accesses
the target LTE cell and initiates random access to the SgNB. The T-MeNB returns a
configuration complete message to the SgNB.
16-17. The T-MeNB sends a context release request to the S-MeNB. The S-MeNB forwards
the context release request to the SgNB.
NOTE
If the S-GW GTP information (that is, S1 UL GTP Tunnel Endpoint) has changed during an SgNB
addition, the SgNB addition request will be rejected.
SgNB Modification Initiated by the SgNB

An SgNB modification procedure initiated by the SgNB is used to change and release bearers
and to change the PSCell within the SgNB. This version does not support direct signaling
exchange between an SgNB and a UE. The RRC messages on the SgNB side must be sent to
the MeNB and then to the UE by triggering an SgNB modification procedure. After receiving
an event A3 measurement report, the SgNB triggers an intra-gNodeB cell change procedure if
the measured cell is served by the current SgNB.
Figure 4-7 SgNB modification initiated by the SgNB
1. The SgNB sends an SgNB Modification Required message to the MeNB. This message
contains the NR RRC configuration message and information related to a bearer release or
change.

SingleRAN
2-3. If the SgNB requests to release the bearers and the MeNB decides to reconfigure the
MCG bearer, the MeNB triggers an SgNB modification procedure. The SgNB responds with
an SgNB Modification Request Acknowledge message upon agreement.
4-5. Operations identical with steps 3 and 4 of SgNB Addition Initiated by the MeNB are
performed.
6. After the UE completes reconfigurations, the MeNB sends an SgNB Modification Confirm
message to the SgNB. This message contains the encoded NR RRC response message.
7. If the bearers configured for the UE require SCG radio resources, the UE synchronizes with
the SgNB PSCell and initiates random access to the SgNB PSCell. Otherwise, the UE initiates
uplink transmission after the new configuration takes effect.
NOTE
If an LTE handover is ongoing when the MeNB receives an SgNB Modification Required message from
the SgNB, the LTE handover is preferentially processed, as stipulated in 3GPP TS 36.423. In this case,
the MeNB returns an SgNB Modification Refuse message with the cause value "Message not
Compatible with Receiver State" to the SgNB.
SgNB Modification Initiated by the MeNB

An SgNB modification procedure initiated by the MeNB is used to establish, change, or
release bearers.
During an intra-MeNB handover, the MeNB triggers an SgNB modification by sending an

SgNB Modification Request message to notify the SgNB PDCP layer of using the new key.
Figure 4-8 SgNB modification triggered by the MeNB

SingleRAN
1. The MeNB sends an SgNB Modification Request message to the SgNB. This message
contains information related to the bearer establishment, change, or release on the NR side,
and a new key to be used by the SgNB PDCP layer in case of a security key update.
NOTE
If the UE Context Modification Request message sent by the MME contains only the NR UE Security
Capabilities IE, the MeNB records the IE and will not trigger the SgNB modification procedure
immediately. In a future inter-MeNB handover, it will send the capabilities to the target MeNB.
2-3. After completing the bearer establishment, change or release, or PDCP configuration by
using the new key, the SgNB sends an SgNB Modification Request Acknowledge message to
the MeNB. The MeNB sends a reconfiguration message to the UE. This message contains an
LTE handover command and an NR PDCP reconfiguration message.
4-6. Upon reception of the reconfiguration message, the UE initiates random access to the
target LTE cell and sends an RRC Connection Reconfiguration Complete message to the
MeNB. The MeNB sends an SgNB Reconfiguration Complete message to the SgNB.
7. The UE initiates random access to the PSCell of the SgNB.
SgNB Change Initiated by the SgNB

If the PSCell coverage worsens, only handovers to intra-frequency cells of a neighboring base
station is supported in this version, and the event A3 measurement threshold is used.

SingleRAN
Figure 4-9 SgNB change procedure
1. After receiving an event A3 measurement report, the source SgNB selects an NR cell with
the highest RSRP as the target NR cell for handover. The SgNB then triggers an SgNB change
procedure by sending an SgNB Change Required message to the MeNB. This message
contains the target SgNB ID and the measurement result.
2-3. The MeNB sends an SgNB Addition Request message to the target SgNB, requesting the
target SgNB to allocate resources to the UE. The message contains the measurement results of
the target SgNB measured by the source SgNB.
performed.
6. If the target SgNB successfully allocates resources to the UE, the MeNB sends an SgNB
Change Confirm message to the source SgNB after the MeNB confirms that the resources of
the source SgNB have been released.
7. If the RRC connection reconfiguration procedure is complete, the MeNB sends an SgNB
Reconfiguration Complete message to the target SgNB to confirm reconfiguration
completion. The message contains the encoded NR RRC message.

SingleRAN
8. Operations identical with step 7 of SgNB Modification Initiated by the SgNB are
performed.
9-10. In a bearer type change scenario, data forwarding is implemented between the MeNB
and the SgNB to reduce the service interruption duration.
11. The SgNB reports the NR data volume to the MeNB.
12-16. Operations identical with steps 9 to 12 of SgNB Addition Initiated by the MeNB are
performed.
17. After receiving a UE Context Release message, the source SgNB releases the UE context.
SgNB Release Initiated by the MeNB/SgNB

Both the MeNB and the SgNB may trigger an SgNB release. Different scenarios involve
different triggering sources. For details, see Figure 4-10 and Figure 4-11.
The MeNB initiates an SgNB release when either of the following conditions is met:
l The SCG link is faulty.

l Packets on the GTPU control plane are lost.
Figure 4-10 SgNB release initiated by the MeNB
1. The MeNB sends an SgNB Release Request message to initiate an SgNB release
procedure.
2. The SgNB sends an SgNB Release Request Acknowledge message to the MeNB to
confirm that the SgNB can be released.

SingleRAN
performed.
5-6. In a bearer type change scenario, data forwarding is implemented between the MeNB and
the SgNB to reduce the service interruption duration.
7. Operations identical with step 10 of SgNB Modification Initiated by the SgNB are
performed.
8. A path update procedure is performed, which is required by the core network.
9. After receiving a UE Context Release message, the SgNB releases the UE context.
The SgNB initiates an SgNB release when any of the following conditions is met:
l When the signal quality of the PSCell keeps decreasing and no suitable neighboring cell
is found for a PSCell handover, the PSCell is deleted if the measured RSRP of the
PSCell is lower than the value of the NRCellNsaDcConfig.PscellA2RsrpThld
parameter.
l The UE is released due to the expiry of the inactivity timer on the NR side. The timer is
specified by the NRDUCellQciBearer.UeInactivityTimer parameter.
l Packets on the GTPU control plane are lost.
Figure 4-11 SgNB release initiated by the SgNB
1. The SgNB sends an SgNB Release Required message to initiate an SgNB release
procedure.
2. The MeNB sends an SgNB Release Confirm message to the SgNB to confirm that the
SgNB is released. After receiving this message, the SgNB stops sending data to the UE.
3-9. Operations identical with steps 4 to 10 of SgNB Addition Initiated by the MeNB are
performed.

SingleRAN
4.3 NSA DC Data Split

Data split at the PDCP layer starts after the MeNB receives an
SGNB_ADDITION_REQUEST_ACKNOWLEDGE message from the SgNB, indicating that
an X2 tunnel has been set up between the MeNB and the SgNB.
In this version, all types of services, except the following, support MCG bearer,
MCG_Bearer_EUTRA_PDCP, MCG split bearer, and SCG split bearer:
l Voice services that use the ROHC function: support only MCG bearer or
MCG_Bearer_EUTRA_PDCP.
l E-RABs with QCIs of 1 or 5: support only MCG bearer or
MCG_Bearer_EUTRA_PDCP.
l E-RABs with QCIs of 2–4, 65–67, 75, or 82–85: support only MCG bearer,
MCG_Bearer_EUTRA_PDCP, and SCG split bearer. In the case of SCG split bearer, the
uplink and downlink data is distributed only to the SCG.
NOTE
l In the Option 3x architecture, if data distribution only to MCG is configured in the downlink or
uplink, it is recommended that NRDUCellQciBearer.UeInactivityTimer be set to 0 on the gNodeB
side. This prevents the SCG release triggered by the expiry of the UE inactivity timer when there is
no traffic at the RLC layer on the NR side.
l The PDCP layer will discard timeout data packets and the data split performance will be affected in
the following situations:
l In Option 3, RlcPdcpParaGroup.DiscardTimer is set to a value other than
DiscardTimer_Infinity.
l In Option 3x, gNBPdcpParamGroup.DlPdcpDiscardTimer is set to a value other than
DiscardTimer_Infinity.
l In NSA DC, data transmission delay is not guaranteed.
4.3.1 Data Split Policy Selection

The CellQciPara.NsaDcDefaultBearerMode parameter specifies the bearer type:
l When this parameter is set to MCG_SPLIT_BEARER, the data split architecture is
Option 3.
l When this parameter is set to SCG_SPLIT_BEARER, the data split architecture is
Option 3x.
l When this parameter is set to MCG_BEARER or MCG_Bearer_EUTRA_PDCP, data
is transmitted only on the LTE side.
For services of QCIs 1-5, it is recommended that
CellQciPara.NsaDcDefaultBearerMode be set to MCG_Bearer_EUTRA_PDCP.
NOTE
l The NsaDcMgmtConfig.NsaDcDefaultBearerMode parameter is replaced by the

CellQciPara.NsaDcDefaultBearerMode parameter. In later versions, the former parameter will be
removed. Therefore, avoid using this parameter.
l To ensure inter-eNodeB consistency of experience for services with identical QCIs, it is
recommended that the same QCI-based data split policies be configured for different eNodeBs.

SingleRAN
4.3.1.1 Downlink Data Split
Downlink Data Split Policy in Option 3

In Option 3, the downlink data split policy is specified by the cell-level
NsaDcMgmtConfig.DlDataMcgSplitBearerMode parameter on the LTE side. If this
parameter is:
l Set to MCG_ONLY
All downlink PDCP PDUs are distributed to the MCG.
l Set to SCG_ONLY
All downlink PDCP PDUs are distributed to the SCG.
l Set to SCG_AND_MCG
Downlink data is dynamically distributed.
The PDCP layer splits data based on the LTE and NR air interface status (such as the
RLC-layer transmission rate, air interface transmission delay, and RLC buffer size) and
X2 interface status (such as transmission delay and congestion status). The UE PDCP
layer re-orders the downlink PDCP PDUs and then transmits the data to the upper layer.
Downlink Data Split Policy in Option 3x

In Option 3x, the downlink data split policy is specified by the
gNBPdcpParamGroup.DlDataPdcpSplitMode parameter for QCI-specific service types on
the NR side. If this parameter is:
l Set to MCG_ONLY
All downlink PDCP PDUs for QCI-specific service types are distributed to the MCG.
l Set to SCG_ONLY
All downlink PDCP PDUs for QCI-specific service types are distributed to the SCG.
l Set to SCG_AND_MCG
Downlink data for QCI-specific service types is dynamically distributed.
The PDCP layer splits data based on the LTE and NR air interface status (such as the
RLC-layer transmission rate, air interface transmission delay, and RLC buffer size) and
X2 interface status (such as transmission delay and congestion status). For details about
X2 interface status, see Transmission Resource Management in 5G RAN feature
documentation. The UE PDCP layer re-orders the downlink PDCP PDUs and then
transmits the data to the upper layer.
NOTE
l In NSA DC, an IP PM session is automatically created over the X2 interface. The X2 interface
status information required by the PDCP layer data split is obtained through the IP PM
session.
l A QCI-specific service type is associated with a PDCP parameter group by adding an
NRCELLQCIBEARER MO.

SingleRAN
4.3.1.2 Uplink Data Split
Uplink Data Split Policy in Option 3

When Option 3 is used, different data split policies are used based on the settings of the cell-
level parameters NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio and
NsaDcMgmtConfig.UlDataSplitThreshold on the LTE side:
l Uplink data is distributed only to the MCG when
The NsaDcMgmtConfig.UlDataSplitThreshold parameter is set to INFINITY, and the
NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio parameter is set to a value greater than
or equal to 50%.
l Uplink data is distributed only to the SCG when
The NsaDcMgmtConfig.UlDataSplitThreshold parameter is set to INFINITY, and the
NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio parameter is set to a value less than
50%.
l Uplink data is dynamically distributed in either of the following scenarios:
– The NsaDcMgmtConfig.UlDataSplitThreshold parameter is set to a value other
than INFINITY, and the UE PDCP buffer data size is greater than or equal to the
value of NsaDcMgmtConfig.UlDataSplitThreshold.
– If the NsaDcMgmtConfig.UlDataSplitThreshold parameter is set to a value other
than INFINITY and the UE PDCP buffer data size is less than the value of
NsaDcMgmtConfig.UlDataSplitThreshold, the specific uplink data split policy is
determined by the NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio parameter.
n If the value of NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio is greater than
or equal to 50%, uplink data is transmitted on the MCG.
n If the value of NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio is less than
50%, uplink data is transmitted on the SCG.
Uplink Data Split Policy in Option 3x

When Option 3x is used, the uplink data split policy is controlled by the NR side based on
QCI-specific service types.
Different data split policies are used based on the settings of the QCI-level
gNBPdcpParamGroup.UlDataSplitPrimaryPath and
gNBPdcpParamGroup.UlDataSplitThreshold parameters.
l Uplink data is distributed only to the MCG when
gNBPdcpParamGroup.UlDataSplitThreshold is set to INFINITY and
gNBPdcpParamGroup.UlDataSplitPrimaryPath is set to MCG.
l Uplink data is distributed only to the SCG when
gNBPdcpParamGroup.UlDataSplitThreshold is set to INFINITY and
gNBPdcpParamGroup.UlDataSplitPrimaryPath is set to SCG.
l Uplink data is dynamically distributed in either of the following scenarios:
– The UE PDCP buffer data size is greater than or equal to the value of
gNBPdcpParamGroup.UlDataSplitThreshold, and the
gNBPdcpParamGroup.UlDataSplitPrimaryPath parameter is set to MCG or
SCG.

SingleRAN
– When the UE PDCP buffer data size is less than the value of
gNBPdcpParamGroup.UlDataSplitThreshold, data is transmitted according to the
value of gNBPdcpParamGroup.UlDataSplitPrimaryPath.
Uplink AMBR Control for Data Split

l During initial SCG configuration, the aggregate maximum bit rates (AMBRs) of the
MeNB and SgNB are allocated by proportion, which is specified by the
NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio parameter.
l The MAC layers of the MeNB and SgNB schedule data based on the configured
AMBRs.
NOTE
l When the uplink data split policy is UL dynamic data split or UL data distribution only to the SCG,
NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio cannot be set to 100.
l When the uplink data split policy is UL dynamic data split or UL data distribution only to the MCG,
NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio cannot be set to 0.
4.3.2 CP/UP Data Separation

In the initial phase of NR deployment, 3.5 GHz or 28 GHz is generally used. Their coverage
ranges are far less than those of LTE frequencies. However, NR can provide higher-rate
services. Therefore, LTE can be used to carry control-plane (CP) data to ensure mobility,
while NR carries user-plane (UP) data, rendering higher throughput and larger capacity.
Figure 4-12 CP/UP data separation
l Parameter configurations for downlink CP/UP data separation

Data Split CP UP Parameter Setting
Architecture
Option 3 LTE NR On the LTE side:

l Set CellQciPara.NsaDcDefaultBearerMode to
MCG_SPLIT_BEARER.
l Set NsaDcMgmtConfig.DlDataMcgSplitBearer-
Mode to SCG_ONLY.

SingleRAN

Architecture
Option 3x LTE NR On the LTE side:

l Set CellQciPara.NsaDcDefaultBearerMode to
SCG_SPLIT_BEARER.
On the NR side:
l Set gNBPdcpParamGroup.DlDataPdcpSplit-
Mode to SCG_ONLY.
l Parameter configurations for uplink CP/UP data separation

Architecture
Option 3 LTE NR On the LTE side:

l Set NsaDcMgmtConfig.UlDataSplitThreshold
to INFINITY.
l Set NsaDcMgmtConfig.NsaDcUeMcgUlAmbr-
Ratio to a value less than 50%.
Option 3x LTE NR On the NR side:

l Set gNBPdcpParamGroup.UlDataSplitThres-
hold to INFINITY.
l Set gNBPdcpParamGroup.UlDataSplitPrimar-
yPath to SCG.
4.3.3 Uplink and Downlink Separation

In NSA DC, when NR coverage is limited and LTE coverage is not limited, the uplink and
downlink services on the UP are carried respectively on the LTE side and NR side. LTE
uplink coverage is used to compensate for the insufficient NR uplink coverage.
Uplink and downlink separation (UL/DL separation) can be implemented by setting the
parameters listed in the following table.
Data Split Uplink MCG Transmission Downlink SCG Transmission

Architecture
Option 3 On the LTE side: On the LTE side:

l Set l Set
NsaDcMgmtConfig.UlDataSplit CellQciPara.NsaDcDefaultBe
Threshold to INFINITY. arerMode to
l Set MCG_SPLIT_BEARER.
NsaDcMgmtConfig.NsaDcUeM l Set
cgUlAmbrRatio to a value NsaDcMgmtConfig.DlDataM
greater than or equal to 50%. cgSplitBearerMode to
SCG_ONLY.

SingleRAN
Data Split Uplink MCG Transmission Downlink SCG Transmission

Architecture
Option 3x On the NR side: On the LTE side:

l Set l Set
gNBPdcpParamGroup.UlData CellQciPara.NsaDcDefaultBe
SplitThreshold to INFINITY. arerMode to
l Set SCG_SPLIT_BEARER.
gNBPdcpParamGroup.UlData On the NR side:
SplitPrimaryPath to MCG. l Set
gNBPdcpParamGroup.DlDat
aPdcpSplitMode to
SCG_ONLY.
4.3.4 Uplink Fallback to LTE

In NSA DC scenarios, when CellQciPara.NsaDcDefaultBearerMode is set to
SCG_SPLIT_BEARER, the network side controls the UE to dynamically send uplink data
to the gNodeB or eNodeB based on the NR's uplink SINR. In this way, the uplink coverage
capability of the LTE network can be used to compensate for the insufficient NR uplink
coverage. It is recommended that this function be enabled when LTE and NR cells are co-
sited and the uplink data split policy is uplink data distributed only to the SCG. After this
function takes effect, the uplink data transmission of cell edge users (CEUs) in the NR cell is
switched to the LTE network to improve their experience.
This function is controlled by the UL_FALLBACK_TO_LTE_SWITCH option of the
NRCellNsaDcConfig.NsaDcAlgoSwitch parameter. When this option is selected:
l When the uplink signal quality on the NR side deteriorates, that is, once detecting that
the uplink SINR on the NR side is less than or equal to
NRDUCellSrsMeas.NsaUlFackToLteSinrThld minus
NRDUCellSrsMeas.NsaUlFackToLteSinrHyst for five consecutive seconds, the
gNodeB sends an SgNB Modification Required message to the eNodeB to trigger a
change in the uplink data split policy. The eNodeB sends an RRC reconfiguration
message to the UE, instructing the UE to transmit data on the LTE side.
l When the uplink signal quality on the NR side becomes better, that is, once detecting that
the uplink SINR on the NR side is greater than
NRDUCellSrsMeas.NsaUlFackToLteSinrThld plus
NRDUCellSrsMeas.NsaUlFackToLteSinrHyst for five consecutive seconds, the
gNodeB sends an SgNB Modification Required message to the eNodeB to trigger a
change in the uplink data split policy. The eNodeB sends an RRC reconfiguration
message to the UE, notifying the UE to implement the original uplink data split policy.
NOTE
If the NRDUCellSrsMeas.NsaUlFackToLteSinrThld parameter is set to a too large value, uplink

fallback to LTE may be triggered too early. At that moment if the LTE uplink throughput is lower than
the NR uplink throughput before the fallback, the uplink throughput of NSA DC may decrease. When
the uplink data of NSA DC UEs is transmitted only on the LTE side, the uplink load of LTE cells
increases.

SingleRAN
4.3.5 NSA DC UE Scheduling Protection Based on MCG Cell

Load
In NSA DC, when the MSG cell load is high and the LTE UEs are not fully scheduled due to
preemption of PRB resources by NSA DC UEs, NSA DC UE scheduling protection based on
MCG cell load can be used to reduce the impact on LTE services and increase LTE user
experienced data rates.
For example, the total data rate in MCG cells is 100 Mbit/s, and the expected data rates of
both LTE-only UEs and NSA DC UEs are 70 Mbit/s. If
CellDlschAlgo.McgHighLoadThreshold is set to 100 and this function is disabled, the data
rates of LTE-only UEs and NSA DC UEs are both 50 Mbit/s. If
CellDlschAlgo.McgHighLoadThreshold is set to a value other than 100, LTE-only UEs are
preferentially scheduled and their total data rate is 70 Mbit/s, and the data rate of NSA DC
UEs is only 30 Mbit/s.
l When the eNodeB determines that the PRB usage of the current LTE cell is greater than
or equal to the value of CellDlschAlgo.McgHighLoadThreshold, the eNodeB adjusts
the downlink scheduling priority of non-GBR services of NSA DC UEs in the current
LTE cell to the lowest.
l When the eNodeB determines that the PRB usage of the current LTE cell is less than the
value of CellDlschAlgo.McgHighLoadThreshold minus 10%, the eNodeB restores the
downlink scheduling priority of non-GBR services of NSA DC UEs in the current LTE
cell.
NOTE
l Scheduling priority adjustment is performed only for non-GBR services except those of QCI 5 or
QCI 69. The scheduling priorities of GBR services are not adjusted.
l To prevent ping-pong priority adjustment, the offset value 10% is added when the eNodeB
determines whether the PRB usage of the current LTE cell is less than the specified threshold.
4.4 Uplink Power Control in NSA DC

Figure 4-13 illustrates how the uplink power control applies to UEs in NSA DC. 4.4.1 Initial
Power Control describes the power control for UEs initially accessing the network in NSA
DC. When the triggering conditions for TDM power control are met, TDM power control is
triggered in the uplink to improve the uplink coverage, as described in 4.4.2 TDM Power
Control.

SingleRAN
Figure 4-13 Uplink power control in NSA DC
Currently, the maximum uplink transmit power of an NSA DC UE is 23 dBm. The following
parameters can be configured on the LTE side to specify the UE's maximum transmit power
on the LTE and NR sides in NSA DC:
l NsaDcMgmtConfig.NsaDcUeMcgUlMaximumPower
l NsaDcMgmtConfig.NsaDcUeScgUlMaximumPower
The sum of the configured maximum MCG uplink transmit power (specified by
NsaDcMgmtConfig.NsaDcUeMcgUlMaximumPower) and maximum SCG uplink transmit
power (specified by NsaDcMgmtConfig.NsaDcUeScgUlMaximumPower) cannot exceed
the NSA DC UE's maximum uplink transmit power.
NOTE
After a UE accesses the network, the gNodeB configures a maximum transmit power for the UE. The
total simultaneous power on uplink channels cannot exceed the maximum transmit power. For details
about power control on each channel, see Power Control in 5G RAN feature documentation.
4.4.1 Initial Power Control

For an NSA DC UE that initially accesses the network, the maximum uplink transmit power
on the LTE and NR sides delivered to the UE is specified by the
NsaDcMgmtConfig.NsaDcUeMcgUlMaximumPower and
NsaDcMgmtConfig.NsaDcUeScgUlMaximumPower parameters. The sum of the configured
parameter values cannot exceed 23 dBm.
4.4.2 TDM Power Control

This function takes effect only for LTE FDD.
When the NSA_DC_ENH_UL_POWER_CONTROL_SW and TDM_SWITCH options of

the NsaDcMgmtConfig.NsaDcAlgoSwitch parameter on the LTE side and the
NSA_DC_ENH_UL_POWER_CONTROL_SW option of the
NRCellNsaDcConfig.NsaDcAlgoSwitch parameter on the NR side are selected, the LTE and
NR sides determine whether the UE is at the cell edge. If either side determines that the UE is
located at the cell edge and the UE supports time division multiplexing (TDM), TDM power
control is triggered. The UE can use all the power to send data to LTE and NR in TDM mode,
thereby improving the uplink coverage in NSA DC.

SingleRAN
The judgment method is as follows:
l On the LTE side, when the LTE uplink SINR of the UE is less than or equal to the value
of NsaDcMgmtConfig.NsaTdmPcTrigSinrThld, the eNodeB determines that the UE is
located at the cell edge and triggers uplink TDM power control.
l On the NR side, when the NR uplink SINR of the UE plus
NRDUCellSrsMeas.NsaTdmPcTrigSinrHyst is less than or equal to
NRDUCellSrsMeas.NsaTdmPcTrigSinrThld, the gNodeB determines that the UE is
located at the cell edge and triggers uplink TDM power control.
No matter whether TDM power control is triggered on the LTE or NR side, the TDM-Pattern
is determined by the NR side and can only be selected from SA0-SA6 of LTE TDD. For
details about the TDM-Pattern, see 3GPP TS 36.331 "E-UTRA; Radio Resource Control
(RRC) Protocol specification". The NR side sends the TDM-Pattern to the LTE side through
an SgNB Modification Request Acknowledge or SgNB Modification Required message.
Upon reception of this message, the eNodeB sends the TDM-Pattern to the UE. The TDM
power control function takes effect simultaneously on the UE and the base station sides.
NOTE
l In NSA DC, after TDM power control takes effect in an LTE FDD cell, the PUCCH in the cell
always uses format3, which increases the number of RBs occupied by the PUCCH. As a result, the
number of RBs available for the PUSCH decreases, and the overall cell throughput may decrease.
l If Cell.UePowerMax configured on the LTE side is less than the maximum transmit power
supported by the UE (for example, 23 dBm), the UE's maximum transmit power on the LTE side
cannot reach 23 dBm in TDM power control mode. As a result, the uplink coverage gain for LTE
from TDM power control in NSA DC decreases.
TDM power control requires time synchronization between the LTE FDD cell and the NR cell
providing NSA DC. The relative frame offsets of 0 ms and 3 ms between LTE FDD and NR
cells are supported. The NR side selects the corresponding TDM-Pattern based on the related
parameters.
After TDM power control takes effect for a UE, the UE can send data on the LTE side only on
the uplink subframes corresponding to the configured TDM-Pattern. If the LTE PRACH time-
domain position is not in the configured TDM-Pattern uplink subframes, the UE cannot
perform random access on the LTE side, and resynchronization between the LTE network and
the UE and handover are affected. Therefore, TDM is disabled when a UE is performing a
handover between LTE cells. If the UE is out of synchronization in TDM mode and the LTE
PRACH time-domain position is not in the configured TDM-Pattern uplink subframes,
resynchronization cannot be performed. In such case, the UE re-accesses the LTE network
through RRC reestablishment.
In the following TDM-Patterns, subframe 1 is configured to allow data transmission. To

implement resynchronization in TDM mode, the LTE PRACH time-domain position must
include subframe 1. The corresponding LTE cell must meet the following requirements:
RachCfg.PrachConfigIndexCfgInd is set to NOT_CFG, or
RachCfg.PrachConfigIndexCfgInd is set to CFG and RachCfg.PrachConfigIndex is set to
0, 3, 6, 9, 13, 14, 16, 19, 22, 25, 29, 32, 35, 38, 41, 45, 48, 51, 54, or 57.
NOTE
In the following figures, indicates "Prohibited".

l As shown in Figure 4-14, Figure 4-15, and Figure 4-16, when the relative frame offset
between LTE FDD and NR cells is 0 ms, gNodeBParam.NsaDcResCoordScenario
must be set to SYNC_NSA_DC_0_FRAME_OFT. In this case, if TDM power control

SingleRAN
is triggered, the gNodeB configures the TDM-Pattern based on the relative frame offset
of 0 ms.
Figure 4-14 Example of TDM-Pattern when NR uses 4:1 slot assignment (relative frame
offset of 0 ms)
offset of 0 ms)
offset of 0 ms)
l As shown in Figure 4-17, Figure 4-18, and Figure 4-19, when the relative frame offset
between LTE FDD and NR cells is 3 ms, gNodeBParam.NsaDcResCoordScenario
must be set to SYNC_NSA_DC_3Pl2Mi_FRAME_OFT. In this case, if TDM power
control is triggered, the gNodeB configures the TDM-Pattern based on the relative frame
offset of 3 ms.
offset of 3 ms)

SingleRAN
offset of 3 ms)
offset of 3 ms)
NOTE
If time is not synchronized between LTE FDD and NR cells, LTE and NR data may be transmitted
in the uplink at the same time. In this case, LTE and NR services may be affected because the UE
behavior cannot be predicted.
4.5 Interference Avoidance in NSA DC

In NSA DC, simultaneous LTE and NR uplink transmission on the UE side incurs secondary
intermodulation interference signals whose range falls within the LTE downlink frequency
band range. The secondary intermodulation interference signals interfere UE's reception of
LTE downlink signals, decreasing the UE receiver sensitivity by a maximum of 28.6 dB. The
LTE uplink transmission on the UE side incurs secondary harmonic interference signals
whose range falls within the NR downlink frequency band range. As a result, interference to
UE downlink reception from the NR occurs and the sensitivity decreases by a maximum of
23.9 dB.
4.5.1 UE Interference Types

l Parameters required for determining the interference type
LTE_UL_low (minimum value of the LTE uplink frequency range): LTE uplink center
frequency - LTE bandwidth/2
LTE_UL_high (maximum value of the LTE uplink frequency range): LTE uplink center
frequency + LTE bandwidth/2
LTE_DL_low (minimum value of the LTE downlink frequency range): LTE downlink
center frequency - LTE bandwidth/2
LTE_DL_high (maximum value of the LTE downlink frequency range): LTE downlink
center frequency + LTE bandwidth/2
NR_UL_low (minimum value of the NR uplink frequency range): NR uplink center
frequency - NR bandwidth/2
NR_UL_high (maximum value of the NR uplink frequency range): NR uplink center
frequency + NR bandwidth/2

SingleRAN
NR_Dl_low (minimum value of the NR downlink frequency range): NR downlink center

frequency - NR bandwidth/2
NR_Dl_high (maximum value of the NR downlink frequency range): NR downlink
center frequency + NR bandwidth/2
l Method for determining whether secondary intermodulation interference exists
Condition 1: LTE_DL_low > NR_UL_high - LTE_UL_low
Condition 2: LTE_DL_high < NR_UL_low - LTE_UL_high
If neither condition is met, secondary intermodulation interference exists.
l Method for determining whether secondary harmonic interference exists
Condition 1: NR_DL_low > LTE_UL_high x 2
Condition 2: NR_DL_high < LTE_UL_low x 2
If neither condition is met, secondary harmonic interference exists.
4.5.2 Interference Avoidance

Interference avoidance policies in this version are implemented by using time division
scheduling on the base station side in the time and frequency domains.
Interference Avoidance Policies

l Secondary intermodulation interference avoidance policy
In secondary intermodulation interference avoidance, TDM is used on the LTE side to
avoid colliding with the NR uplink control channels and data channels.
As shown in Figure 4-20, the LTE FDD+NR TDD scenario is used as an example.
Assume that the uplink-downlink subframe configuration of NR TDD is DDDSU and
the scheduling unit is 0.5 ms. When an LTE U subframe collides with an NR U
subframe, LTE signals will not be transmitted in this subframe.
Figure 4-20 TDM for intermodulation interference avoidance
NOTE
Intermodulation interference avoidance requires time synchronization between the LTE and NR
cells in NSA networking. TDM triggered by secondary intermodulation interference supports the
relative frame offset of 0 ms or 3 ms between LTE FDD and NR cells. The NR side selects the
TDM-Pattern based on the value of gNodeBParam.NsaDcResCoordScenario. The TDM-Pattern
is the same as that selected when TDM is triggered by power control.
l Secondary harmonic interference avoidance policy
In secondary harmonic interference avoidance, the TDM and frequency division
multiplexing (FDM) are used in the uplink on the LTE side to stagger NR downlink
common channels (PBCH and common PDCCH).

SingleRAN
Implementation Principles
In NSA DC, the NR side determines the interference type based on the frequency ranges of
the PCell and PSCell. Based on the interference type, the NR side sends an LTE-NR joint
scheduling pattern to the LTE side for interference avoidance.
l (On the NR side) When the CROSS_MDLT_INTRF_AVOID_SW option of the
NRDUCellAlgoSwitch.NsaDcAlgoSwitch parameter or the
HARMONIC_INTRF_AVOID_SW option of the
NRDUCellAlgoSwitch.NsaDcAlgoSwitch parameter is selected, the NR side determines
the interference type according to the methods described in 4.5.1 UE Interference
Types.
– When the interference type is secondary intermodulation interference and the
CROSS_MDLT_INTRF_AVOID_SW option of the
NRDUCellAlgoSwitch.NsaDcAlgoSwitch parameter is selected, the NR side sends
the LTE-NR joint scheduling time sequence to the LTE side through a pattern.
– When the interference type is secondary harmonic interference and the
HARMONIC_INTRF_AVOID_SW option of the
NRDUCellAlgoSwitch.NsaDcAlgoSwitch parameter is selected, the NR side sends
the time-frequency positions of NR common channels to the LTE side through a
pattern.
l (On the LTE side) When the INTERFERENCE_AVOID_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is selected, the LTE side performs
uplink and downlink scheduling based on the pattern received from the NR side. To
support intermodulation interference avoidance, the TDM_SWITCH option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter must be selected.
4.6 NR Data Volume Reporting

According to 3GPP TS 37.340, in NSA DC, the RAN reports the NR data volumes to the core
network for independent charging of 5G RAN data volume, as shown in Figure 4-21.

SingleRAN
Figure 4-21 NR data volume reporting on the RAN side
As shown in Figure 4-21, the NR uplink and downlink data volumes are reported on a per
bearer basis. The base station counts the air-interface data volume by the number of bytes in
SDU packets distributed to the gNodeB and reports the data volume in the Secondary RAT
Data Usage Report message or another message containing the Secondary RAT Usage Report
List IE.
l In Option 3, the data split anchor is on the MeNB. Therefore, the MeNB directly counts
the air-interface data volume distributed to the NR side and does not require data volume
reporting by the SgNB over the X2 interface. Then, the MeNB directly sends the data
volume to the MME on the core network.
l In Option 3x, the SgNB counts the air-interface data volume distributed to the NR side
and sends the data volume to the MeNB over the X2 interface. Then, the MeNB sends
the data volume to the MME on the core network. If the
NsaDcMgmtConfig.NrDataVolumeRptCfg parameter is set to a value other than 0 on
the LTE side, the MeNB transfers the data volume received from the SgNB to the core
network.
Both the SgNB and MeNB support event-triggered NR data volume reporting and periodic
NR data volume reporting.
NOTE
The internal timer of the eNodeB or gNodeB has a deviation of one period, and therefore the time for the
SgNB or MeNB to report the data volume possibly has a deviation.
l In Option 3, the reporting method is specified by the
NsaDcMgmtConfig.NrDataVolumeRptCfg parameter on the LTE side.
– Event-triggered NR data volume reporting
If this parameter is set to 65535, the eNodeB reports NR data volume only based on
events. After MCG split bearer setup, the eNodeB starts timing and counts NR data

SingleRAN
volume. Upon a bearer change or release, the eNodeB records the end time,
calculates the total data volume distributed to the NR side, and reports the uplink
and downlink NR data volumes to the core network through the Secondary RAT
Usage Report List IE in a Secondary RAT Data Usage Report, Context Release
Req, Context Release Complete, E-RAB Modification Indication, E-RAB Release
Indication, or E-RAB Release Response message.
– Periodic NR data volume reporting
If this parameter is set to a value within the range of 60 to 36000, the eNodeB
reports NR data volume not only based on events but also periodically at the
interval specified by this parameter. That is, the eNodeB periodically reports the NR
data volume to the core network through the Secondary RAT Data Usage Report
message after the timing starts.
l In Option 3x, the reporting method is specified by the
NRCellNsaDcConfig.NrDataVolumeRptCfg parameter on the NR side.
– Event-triggered NR data volume reporting
If this parameter is set to 65535, the gNodeB reports NR data volume based on
events. After SCG split bearer setup, the gNodeB starts timing and counts NR data
volume. Upon a bearer change (due to inter-gNodeB handover) or SCG release
(including SCG release triggered by inter-MeNB handover), the gNodeB records
the end time, calculates the total data volume distributed to the NR side, and reports
the data volume to the eNodeB through the Secondary RAT Data Usage Report
message over the X2 interface. The eNodeB reports uplink and downlink NR data
volumes to the core network through the Secondary RAT Usage Report List IE in a
Secondary RAT Data Usage Report, Context Release Req, Context Release
Complete, E-RAB Modification Indication, E-RAB Release Indication, or E-RAB
Release Response message.
– Periodic NR data volume reporting
If this parameter is set to a value within the range of 60 to 36000, the gNodeB
reports NR data volume not only based on events but also periodically at the
interval specified by this parameter. That is, the gNodeB periodically reports the
NR data volume to the eNodeB through the Secondary RAT Data Usage Report
message after the timing starts. After receiving the message, the eNodeB forwards it
to the MME.
In Option 3x, if NR data volume reporting is required, set
NsaDcMgmtConfig.NrDataVolumeRptCfg on the LTE side to a value other than 0.
NOTE
In Option 3x, the NR data volume reporting functions on the LTE and NR sides must be both
disabled or enabled. The following situations must be avoided:
l This function is enabled on the NR side but disabled on the LTE side. In this case, the gNodeB
sends data volume information to the eNodeB, but the eNodeB cannot process the data volume
information.
l This function is disabled on the NR side but enabled on the LTE side. In this case, when an
inter-gNodeB handover is performed, the eNodeB starts a timer to wait for NR data volume
reporting but the gNodeB does not report the information. However, in the waiting period, the
bearer path is not switched to the target SgNB, and therefore the UE has no data transmission
on the target SgNB side.
If the UE has multiple E-RABs that use different data split bearers (MCG split bearer or SCG split
bearer), NR data volume is reported on the basis of the bearer according to the methods specified
in Option 3 and Option 3x, respectively.

SingleRAN
4.7 S-KgNB Update

To improve security in data transmission in NSA DC, the S-KgNB at the PDCP layer needs to
be changed. When detecting that the number of data packets transmitted by NSA DC reaches
a specified threshold, the SgNB sends an S-KgNB update request to the MeNB, as shown in
Figure 4-22. After completing the S-KgNB update, the MeNB sends an SgNB Modification
Request message containing the S-KgNB to the SgNB and reconfigures the UE.
Figure 4-22 S-KgNB update
1. The SgNB sends an SgNB Modification Required message to the MeNB. This message
carries the PDCP Change Indication, indicating that the S-KgNB needs to be updated.
2-3. Upon reception of the SgNB Modification Required message, the MeNB automatically
increases the SCG counter by 1 and calculates a new S-KgNB. The MeNB then sends an SgNB
Modification Request message to the SgNB, containing the new S-KgNB. After receiving the
message from the MeNB, the SgNB obtains the new key and returns an SgNB Modification
Request Acknowledge message.
4. The MeNB sends an RRC Connection Reconfiguration message to the UE. The message
contains the new SCG counter.
5. Upon reception of the new SCG counter, the UE calculates a new S-KgNB and a new user-
plane cipher key. The UE returns an RRC Connection Reconfiguration Complete message to
the MeNB.
6. The MeNB sends an SgNB Modification Confirm message to the SgNB. The new user-
plane cipher key takes effect on both the UE and SgNB sides.

SingleRAN
For details about the procedure, see section 10.3 "Secondary Node Modification (MN/SN
initiated)" in 3GPP TS 37.340. For details about the S-KgNB and security key, see 3GPP TS
33.401.
4.8 Relationships Between NSA DC and LTE Features

Frequency-Priority-based Inter-Frequency Handover
If the frequency priorities configured for frequency-priority-based handover are different from
NSA DC PCC priorities, it is recommended that RsvdSwPara6_bit18 of the
eNBCellRsvdPara.RsvdSwPara6 parameter be set to 1. For details about this reserved
parameter, see 3900 & 5900 Series Base Station eNodeBFunction Used Reserved Parameter
List in 3900 & 5900 Series Base Station Product Documentation. With this setting, frequency-
priority-based inter-frequency handover does not take effect for NSA DC UEs. In this manner,
after being handed over to frequencies with higher NSA DC PCC priorities, NSA DC UEs
will not be switched back to frequencies with lower NSA DC PCC priorities through
frequency-priority-based inter-frequency handovers. For details about frequency-priority-
based inter-frequency handover, see Mobility Management in Connected Mode in eRAN
feature documentation.
Service-based Inter-Frequency Handover

If service-based inter-frequency handover is enabled at LTE, the
SERV_BASED_INTER_FREQ_HO_SW option of the CellQciPara.NsaDcOptSwitch
parameter can be deselected for a specific QCI to disable service-based inter-frequency
handover for NSA DC UEs, thereby, for example, preventing NSA DC UEs from being
handed over from PCCs to non-PCCs.
If service-based inter-frequency handover is required for a specific QCI (for example, VoLTE
services need to be carried only on specific frequencies), select this option. For NSA DC UEs
that are handed over from a PCC to a non-candidate PCC to perform services of a specific
QCI, the QCI_REL_BASED_PCC_ANCHORING_SW option of the
CellQciPara.NsaDcOptSwitch parameter can be selected to enable such UEs to perform
NSA DC PCC anchoring after the bearers of the QCI are released. For details about service-
based inter-frequency handover, see Mobility Management in Connected Mode in eRAN
feature documentation.
Load Balancing
The intra-LTE load balancing mechanism differs between NSA DC UEs and LTE-only UEs as
follows: The target frequency to which an NSA DC UE is handed over must be a candidate
NSA DC PCC (that is, the PCC priority is not 0). If the target frequency is not a candidate
NSA DC PCC, a handover procedure will not be initiated for the NSA DC UE.
To prevent NSA DC UEs from being handed over from PCCs to non-candidate PCCs, inter-
RAT load balancing does not take effect for NSA DC UEs.
For details about LTE load balancing, see Intra-RAT Mobility Load Balancing and Inter-RAT
Mobility Load Balancing in eRAN feature documentation.
Multi-band Optimal Carrier Selection (MBOCS)

After the MBOCS feature is enabled at LTE, RsvdSwPara6_bit19 of the
eNBCellRsvdPara.RsvdSwPara6 parameter can be set to 1 to disable the MBOCS feature for

SingleRAN
NSA DC UEs, thereby preventing NSA DC UEs from being handed over from PCCs to non-
candidate PCCs. For details about this reserved parameter, see 3900 & 5900 Series Base
Station eNodeBFunction Used Reserved Parameter List in 3900 & 5900 Series Base Station
Product Documentation. For details about MBOCS, see Multi-band Optimal Carrier
Selection in eRAN feature documentation.
Spectrum Coordination
After LTE spectrum coordination is enabled, the RsvdSwPara6_bit20 option of the
ENBCELLRSVDPARA.RsvdSwPara6 parameter can be selected to disable spectrum
coordination for NSA DC UEs, that is, to prevent NSA DC UEs from being handed over from
PCCs to non-candidate PCCs. For details about this reserved parameter, see 3900 & 5900
Series Base Station eNodeBFunction Used Reserved Parameter List in 3900 & 5900 Series
Base Station Product Documentation. For details about spectrum coordination, see LTE
Spectrum Coordination in eRAN feature documentation.

SingleRAN
Description 5 Network Analysis
5 Network Analysis
5.1 Benefits
l Overall throughput for the entire network
NSA DC does not directly affect network capacity. However, when resources on a
network have not been used up, NSA DC increases the resource efficiency and overall
throughput in the network.
l Data rates of NSA DC UEs
When resources on a network have not been used up, NSA DC increases the data rates of
NSA DC UEs.
l Overall PRB usage for the network
Most UE services on commercial networks are burst services, and there is a very low
probability that physical resource blocks (PRBs) in all the CCs of a UE are used up
simultaneously. When NSA DC is enabled, loads can be balanced rapidly using data split
policies and scheduling, effectively utilizing idle resources on the network and
increasing the overall PRB usage of the network.
5.2 Impacts
Network Impacts
If a UE is configured with NSA DC, the UE has an RRC connection with the MeNB and
another RRC connection with the SgNB.
NSA DC performance factor = NSA DC rate/(LTE_ONLY rate + NR_ONLY rate). The

greater the NSA DC performance factor, the better the NSA DC data split performance. When
the delay on the X2 interface increases, the NSA DC performance factor decreases. In the
preceding formula, LTE_ONLY indicates that services are carried only on the LTE network;
NR_ONLY indicates that services are carried only on the NR network; NSA DC indicates that
services are carried on both the LTE and NR networks.
After TDM power control takes effect, the UE can send data on the LTE side only on the
uplink subframes corresponding to the configured TDM-Pattern. If the LTE PRACH time-
domain position is not in the configured TDM-Pattern uplink subframes, the UE cannot

SingleRAN
perform random access on the LTE side, and resynchronization between the LTE network and
the UE and handover are affected. Therefore, TDM is disabled when a UE is performing a
handover between LTE cells. If the UE is out of synchronization in TDM mode and the LTE
PRACH time-domain position is not in the configured TDM-Pattern uplink subframes,
resynchronization cannot be performed. In such case, the UE re-accesses the LTE network
through RRC reestablishment.
If frequency synchronization is configured on the LTE side, some downlink data on the NR
side may be discarded because gap-assisted measurement positions may not be aligned
between LTE and NR. As a result, the downlink throughput on the NR side decreases.
Function Impacts
Function Function Switch Reference Description
Name
Traffic UlPacketLenAwareSchSw Scheduling in The throughput of LTE

model-based option of the eRAN UEs decreases, and the
performance CellAlgoSwitch.UlSchExtSwitc Feature throughput of NSA
optimization h parameter Documentati DC UEs increases.
on
Downlink NonGbrBundlingSwitch option Scheduling in The throughput of LTE

non-GBR of the eRAN UEs increases, and the
packet CellAlgoSwitch.DlSchSwitch Feature throughput of NSA
bundling parameter Documentati DC UEs decreases.
on
Delay-based QciPara.DlPdbForExtendedQci QoS

Differentiate Management
d Scheduling in eRAN
for Extended Feature
QCIs Documentati
on
Emergency None Emergency When a UE is

Call Call in eRAN identified as an
Feature emergency call UE, it
Documentati cannot perform NSA
on DC.

SingleRAN

Name
Breathing BreathingPilotSwitch option of Breathing After this feature is

Pilot the Pilot in eRAN enabled, the data
CellDlschAlgo.BreathingPilotA Feature volume of an NSA DC
lgoSwitch parameter Documentati UE may be lower than
on the downlink data
volume threshold for
large-packet services
and consequently the
NSA DC UE is
considered as a non-
large-packet UE. As a
result, the gains
brought by this feature
are affected.
UL and DL NRDUCellAlgoSwitch.UlDlDe UL and DL If UL and DL

Decoupling couplingSwitch Decoupling Decoupling is enabled
in an NR cell, the
uplink fallback to LTE
function does not take
effect.

SingleRAN

Name
Downlink CaDl5CCSwitch option of the Carrier In TDM, the ACK/

5CC CaMgtCfg.CellCaAlgoSwitch Aggregation NACK for multiple
aggregation parameter in eRAN downlink subframes
Feature needs to be sent in the
Documentati same uplink subframe.
on The ACK/NACK
cannot be sent for all
carriers in 5CC CA.
Therefore, the
following restrictions
are imposed: If TDM
is enabled, the
mapping between the
uplink-downlink
subframe
configuration and the
maximum number of
CCs that can be
aggregated in
downlink CA is as
follows: SA0: 5; SA1:
5; SA2: 4; SA3: 3;
SA4: 3; SA5: 2; SA6:
5. If the number of
CCs that can be
aggregated exceeds the
maximum number of
CCs allowed in the
mapping and if TDM
is required, secondary
carriers will be
deleted. Secondary
carriers can be added
later based on the
traffic volume.
However, the
maximum number of
CCs that can be
aggregated in the
downlink cannot
exceed that specified
in the mapping.

SingleRAN

Name
Intelligent CaSmartSelectionSwitch Carrier After the NSA DC

selection of option of the Aggregation PCC anchoring
serving cell ENodeBAlgoSwitch.CaAlgoSwi in eRAN function is enabled,
combinations tch parameter Feature the PCC anchoring for
Documentati intelligent selection of
on serving cell
combinations does not
take effect. After the
NSA DC PCC is
selected, intelligent
selection of serving
cell combinations is
used to select the SCC.
Air interface SRI_PERIOD_OPT_SW Air Interface After TDM takes

latency option of the Latency effect, the SR period is
optimization CELLQCIPARA.QciAlgoSwitc Optimization fixed at 80 ms.
h parameter in eRAN However, in the
LowDelayServiceOptSwitch Feature following scenarios,
option of the Documentati TDM does not take
CellAlgoSwitch.ServiceDiffSwit on effect:
ch parameter l The
SRI_PERIOD_OP
T_SW option of
the
CELLQCIPARA.
QciAlgoSwitch
parameter is
selected.
l The
LowDelayService
OptSwitch option
of the
CellAlgoSwitch.Se
rviceDiffSwitch
parameter is
selected, and the
CellQciPara.LowL
atencyFlag
parameter
corresponding to
the QCI is set to
TRUE.

SingleRAN

Name
Physical l PUCCHCfg.FixedSriPeriod Physical After TDM takes

Channel l PUCCHCfg.SriPeriodAdapt Channel effect, the SR period is
Resource ive Resource fixed at 80 ms.
Management Management However, in the
l Cell.DlBandWidth in eRAN following scenarios,
Feature TDM does not take
Documentati effect:
on l The
PUCCHCfg.Fixed
SriPeriod
parameter is
configured.
l The
PUCCHCfg.SriPe
riodAdaptive
parameter is set to
QCIADAPTIVE.
TDM does not take
effect when the LTE
cell bandwidth is 1.4
MHz.
l The
Cell.DlBandWidth
parameter is set to
CELL_BW_N6.
ROHC CellAlgoSwitch.RohcSwitch ROHC in The ROHC function

eRAN will not take effect
Feature when a UE is
Documentati performing NSA DC
on services.
TTI TtiBundlingSwitch option of VoLTE in TTI bundling and

Bundling the eRAN TDM cannot take
CellAlgoSwitch.UlSchSwitch Feature effect simultaneously.
parameter Documentati
on
Video
Experience
Optimization
in eRAN
Feature
Documentati
on

SingleRAN

Name
Semi- SpsSchSwitch option of the VoLTE in Semi-persistent

persistent CellAlgoSwitch.UlSchSwitch eRAN scheduling and TDM
scheduling parameter Feature cannot take effect
SpsSchSwitch option of the Documentati simultaneously.
CellAlgoSwitch.UlSchSwitch on
parameter PTT in eRAN
Feature
Documentati
on
Short TTI SHORT_TTI_SW option of the Short TTI Short TTI and TDM
CellShortTtiAlgo.SttiAlgoSwitc (FDD) in cannot take effect
h parameter eRAN simultaneously.
Feature
Documentati
on
Virtual 4T4R Virtual4T4RSwitch option of Virtual 4T4R If virtual 4T4R has

the (FDD) in taken effect, TDM will
CellAlgoSwitch.EmimoSwitch eRAN not take effect.
parameter Feature
Documentati
on
Uplink MU- UlVmimoSwitch option of the MIMO in l When TDM power

MIMO CellAlgoSwitch.UlSchSwitch eRAN control has taken
parameter Feature effect, uplink MU-
Documentati MIMO will not
on take effect.
l If TDM needs to be
triggered while
uplink MU-MIMO
is in progress,
uplink MU-MIMO
must be disabled
first.
Uplink SU- ULSUMIMO2LayersSwitch MIMO in l If uplink SU-

MIMO option of the eRAN MIMO has taken
CellAlgoSwitch.UlSuMimoAlg Feature effect, TDM will
oSwitch parameter Documentati not take effect.
on

SingleRAN

Name
UL CoMP UlJointReceptionSwitch option UL CoMP in l When TDM has

of the eRAN taken effect, UL
CellAlgoSwitch.UplinkCompS Feature CoMP will not take
witch parameter Documentati effect.
on l If TDM needs to be
triggered while UL
CoMP is in
progress, UL
CoMP must be
disabled first.
eMBMS CellMBMSCfg.MBMSSwitch eMBMS in When eMBMS has

eRAN taken effect, TDM will
Feature not take effect.
Documentati
on
Uplink UL_FALLBACK_TO_LTE_S NSA If TDM has taken

Fallback to WITCH option of the Networking effect, uplink Fallback
LTE NRCellNsaDcConfig.NsaDcAlg based on to LTE will not take
oSwitch parameter EPC effect.
UL and DL NRDUCellAlgoSwitch.UlDlDe UL and DL If UL and DL

Decoupling couplingSwitch Decoupling Decoupling has taken
effect, TDM power
control will not take
effect. In this case, the
TDM-Pattern
corresponding to UL
and DL Decoupling is
used.
IP None IP If the IP PM function

Performance Performance is abnormal, the base
Monitor Monitor station cannot obtain
the X2 interface delay.
As a result, the
downlink data split
performance of NSA
DC is poor or
downlink data cannot
be split.

SingleRAN

Name
Carrier CaUl2CCSwitch option of the Carrier l When NSA DC is

Aggregation CaMgtCfg.CellCaAlgoSwitch Aggregation being performed,
for Uplink parameter in eRAN the uplink 2CC
2CC Feature aggregation
Documentati function cannot
on take effect.
l When uplink 2CC
aggregation is
being performed,
the uplink
secondary carrier
will be removed if
NSA DC is
required.
FDD+TDD InterFddTddCaSwitch option Carrier l When NSA DC is

Uplink of the Aggregation being performed,
Carrier CaMgtCfg.CellCaAlgoSwitch in eRAN the uplink FDD
Aggregation parameter Feature +TDD CA function
Documentati cannot take effect.
on l When uplink FDD
+TDD CA is being
performed, the
uplink secondary
carrier will be
removed if NSA
DC is required.
Super SuperCombCellSwitch option Super The LTE coverage area

Combined of the Combined is larger than the NR
Cell CellAlgoSwitch.SfnAlgoSwitch Cell (FDD) coverage area. When a
parameter in eRAN UE is located in an
Feature LTE cell but not in any
Documentati NR cell, the UE cannot
on measure NR cells.
eMTC EMTC_SWITCH option of the eMTC in eMTC terminals do

Introduction CellEmtcAlgo.EmtcAlgoSwitch eRAN not support NR.
parameter Feature
Documentati
on

SingleRAN

Name
In-Band InBandRelayDeNbSwitch and Relay in In-band relay requires

Relay InBandRelayReNbSwitch eRAN the support of Huawei
options of the Feature customized UEs.
CellAlgoSwitch.RelaySwitch Documentati Huawei customized
parameter on UEs supporting in-
band relay do not
support
MRFD-131122 NSA
Networking based on
EPC (LTE FDD) or
MRFD-131132 NSA
Networking based on
EPC (LTE TDD).
VoLTE ENodeBAlgoSwitch.EutranVoi VoLTE in If an SCG is added for

pSupportSwitch eRAN a UE running VoLTE
Feature services, the UE
Documentati transmits power on the
on NR side, which
decreases the available
power on the LTE side
and affects the VoLTE
uplink coverage.
LTE WbbCaMultiCarrierCoordSw LTE NSA DC PCC

spectrum option of the Spectrum anchoring takes
coordination CaMgtCfg.CellCaAlgoSwitch Coordination precedence over LTE
enhancement parameter in eRAN spectrum coordination
Feature enhancement. When
Documentati both of these functions
on are enabled, only NSA
DC PCC anchoring
takes effect.

SingleRAN
Description 6 Requirements
6 Requirements
6.1 Licenses
LTE:
RAT Feature Feature Name Model Sales Unit

ID
LTE MRFD-151 EN-DC Performance LT1SENDCCE0F Per Cell

FDD 223 Enhancement (LTE
FDD)
LTE MRFD-151 EN-DC Performance LT1SENDCCE0T Per Cell

TDD 233 Enhancement (LTE
TDD)
LTE LNOFD-15 EN-DC Optimal LT1S0EDOCS00 Per Cell

FDD 1333 Carrier Selection
LTE TDLNOFD EN-DC Optimal LT4SENDCSTDD Per Cell

TDD -151504 Carrier Selection
NR:
RAT Feature Feature Name Model Sales Unit

ID
NR MRFD-151 EN-DC Performance NR0SENDCCE00 Per Cell

263 Enhancement (NR)
If a UE is configured with LTE-NR NSA DC, the UE has one RRC connection with the
MeNB and another RRC connection with the SgNB. Therefore, an RRC Connected User
License needs to be applied for on both the LTE side and the NR side. The licensing principle
for the number of RRC connected users on the LTE side in NSA DC networking is the same

SingleRAN
as that in LTE-only scenarios. For details, see License Management in eRAN feature
documentation. For the licensing principle for the number of RRC connected users on the NR
side, see License Management in 5G RAN feature documentation.
6.2 Software
Before activating this function, ensure that its prerequisite functions have been activated and
mutually exclusive functions have been deactivated. For detailed operations, see the relevant
feature documents.
Prerequisite Functions
Name
X2 self- LTE: X2 and S1 Self- NSA DC services can be

setup LTE_NR_X2_SON_SE Management in performed only after an X2
TUP_SW option of the NSA Networking link has been set up
GlobalProcSwitch.Inter between the source/target
faceSetupPolicySw MeNB and the source/
parameter target SgNB in the
NR: following scenarios: an
X2SON_SETUP_SWI SgNB addition, an SgNB
TCH option of the change initiated by the
gNBX2SonConfig.X2S SgNB, and an inter-MeNB
onConfigSwitch handover without an SgNB
parameter change initiated by the
MeNB.
Mutually Exclusive Functions

None
6.3 Hardware
Base Station Models
For LTE, the following base stations are compatible with this function:
l 3900 and 5900 series base stations
l DBS3900 LampSite and DBS5900 LampSite
l BTS3911E
l BTS3912E
The BTS3911E/BTS3912E supports only the Option 3x architecture and does not
support the Option 3 architecture.
For NR, the following base stations are compatible with this function:
l 3900 and 5900 series base stations. 3900 series base stations must be configured with the
BBU3910.

SingleRAN
l DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be configured

with the BBU3910.
Boards
l LTE
Only the following boards support this function.
Board Type Board Name Option 3 Option 3x
Main control UMPTb Supported Supported

board
Main control UMPTe Supported Supported

board
Main control UMPTg Supported Supported

board
Baseband All UBBP boards Supported Supported

processing unit
NOTE
The LMPT does not support EN-DC optimal carrier selection.

l NR
– The UMPTe/UMPTg boards are the only main control boards that support this
function.
– The UBBPg/UBBPfw1 boards are the only baseband processing units that support
this function.
RF Modules
N/A
6.4 Networking
The following networking scenarios and interconnection modes in NSA DC:
l In co-site co-BBU or separate-BBU scenarios, the LTE and NR base stations in NSA
networking support CI interconnection, intra-BBU backplane interconnection, and IP
transmission interconnection. Different transmission paths can be selected for LTE-NR
user-plane data in different networking scenarios, including IP transmission
interconnection, CI interconnection, intra-BBU backplane interconnection.
In this version, the transmission path of LTE-NR user-plane data is specified by the
gNodeBParam.X2uTransmissionType parameter on the NR side:
– If this parameter is set to ROUTING_TRANS, LTE-NR user-plane data is
transmitted through IP transmission interconnection.
– In co-site separate-BBU CI interconnection scenarios, if this parameter is set to
INTRA_TRANS, LTE-NR user-plane data is transmitted through CI
interconnection.

SingleRAN
– In co-site co-BBU scenarios, if this parameter is set to INTRA_TRANS, LTE-NR

user-plane data is transmitted through intra-BBU backplane interconnection.
NOTE
In LTE-NR co-MPT and co-BBU separate-MPT using co-transmission through backplane

interconnection scenarios, the gNodeBParam.X2uTransmissionType parameter must be set to
INTRA_TRANS. Otherwise, SCG additions will fail in NSA DC. This restriction does not apply to
other scenarios.
l In inter-site scenarios, LTE- and NR-only base stations in NSA networking support only
IP transmission interconnection.
LTE BBU and NR BBU

LTE BBU and NR BBU networking scenarios are classified into LTE-NR separate-BBU
separate-MPT, LTE-NR co-BBU separate-MPT and LTE-NR co-BBU co-MPT, and IP
transmission interconnection between LTE- and NR-only base stations.
l LTE-NR separate-BBU separate-MPT
Figure 6-1 shows an NR base station using a BBU5900 and an LTE base station using
another BBU. The NR and LTE base stations use different main control boards. In this
scenario, use a CI interconnection cable to connect the main control boards, and
configure a CTRLLNK MO for interconnected UMPT boards to implement
infrastructure interconnection between separate-MPT base stations. For details, see BBU
Interconnection in 3900 Series Base Station Product Documentation. X2 control-plane
data between LTE and NR is transmitted through IP transmission interconnection, and
X2 user-plane data is transmitted through CI interconnection or IP transmission
interconnection, depending on the setting of gNodeBParam.X2uTransmissionType.
Figure 6-1 LTE-NR separate-BBU networking
l LTE-NR co-BBU separate-MPT and LTE-NR co-BBU co-MPT

As shown in Figure 6-2 and Figure 6-3, the LTE and NR base stations share the same
BBU5900. They can use different main control boards or share the same main control
board.
– As shown in Figure 6-2, X2 control-plane data between LTE and NR is transmitted
through IP transmission interconnection, and X2 user-plane data is transmitted
through the backplane or IP transmission interconnection.

SingleRAN
Figure 6-2 LTE-NR co-BBU separate-MPT networking
– As shown in Figure 6-3, X2 control-plane and user-plane data between LTE and
NR is exchanged within the UMPT.
Figure 6-3 LTE-NR co-BBU co-MPT networking
l IP transmission interconnection between LTE- and NR-only base stations

As shown in Figure 6-4, the NR base station uses a BBU5900, LTE and NR use different
BBUs, and both NR and LTE base stations are single-mode ones.
X2 control-plane and user-plane data between LTE and NR is transmitted through IP
transmission interconnection.
Figure 6-4 IP transmission interconnection between LTE- and NR-only base stations
LTE Cloud BB and NR BBU

Figure 6-5 shows a newly deployed NR network using a BBU5900 and the existing LTE
network using Cloud BB. In this scenario, only transmission interconnection is supported.

SingleRAN
Figure 6-5 LTE Cloud BB and NR BBU networking
6.5 Others
l UE requirements
– The UE must support NSA DC specified in 3GPP Release 15.
– The UE must have subscribed to LTE and NR services.
– The UE must match the gNodeB and eNodeB versions.
– The UE must support TDM so as to support TDM triggered by intermodulation
interference or power control.
– The uplink dynamic data split requires the support from the UE.
l EPC requirements
– The CloudEPC must support Option 3 and Option 3x.
– The EPC must support NSA DC. If the core network is provided by Huawei, see
WSFD-021101 5G NSA (Opt.3) Dual Connectivity Management for details.
– If NSA DC is enabled on an eNodeB, the connected MMEs must support NSA DC.
If a connected MME does not support NSA DC, the
MmeCapInfo.MmeNsaDcCapability parameter for this MME must be set to
NOT_SUPPORT.
l Clock requirements
TDM requires time synchronization between LTE FDD and NR.

SingleRAN
Description 7 Operation and Maintenance
7 Operation and Maintenance
7.1 When to Use

NSA DC is recommended when operators require aggregation of cells under an eNodeB and a
gNodeB for DC or when gNodeB services are required. For details about NSA DC in case of
RAN sharing, see RAN Sharing on the LTE side and Multi-Operator Sharing on the NR side.
7.2 Data Configuration
7.2.1 Data Preparation

The following table describes the parameters that must be set in the NsaDCMgmtConfig and
NRCellAlgoSwitch MOs to configure the NSA DC switches on the LTE and NR sides,
respectively.
Parameter Parameter ID Setting Notes

Name
NSA DC LTE: Select the

Algorithm NsaDCMgmtConfig.NsaDcAlgoS NSA_DC_CAPABILITY_SWIT
Switch witch CH option.
NSA DC NR: Set this parameter to ON.

Switch NRCellAlgoSwitch.NsaDcSwitch
The following table describes the parameter that must be set in the NsaDCMgmtConfig and
eNBCellRsvdPara MOs on the LTE side to set an independent camping priority for NSA DC
UEs.

SingleRAN

Name
NSA DC NsaDCMgmtConfig.NsaDcAlgoS Select the

Algorithm witch NSA_PCC_ANCHORING_SWI
Switch TCH option.
RsvSw6 eNBCellRsvdPara.RsvdSwPara6 Set RsvdSwPara6_bit28 to 1.
The following table describes the parameter that must be set in the NsaDCMgmtConfig MO
to enable blind SCG configuration on the LTE side.

Name
NSA DC NsaDCMgmtConfig.NsaDcAlgoS Select the

Algorithm witch NSA_BLIND_SCG_ADDITION
Switch _SWITCH option, and set
NrNRelationship.BlindConfigInd
icator to TRUE.
The following table describes the parameters that must be set in the PccFreqCfg MO to
configure the PCC on the LTE side.
NOTE
This MO and PCC priority do not need to be configured for non-PCC frequencies.

Name
PCC Downlink PccFreqCfg.PccDlEarfcn Set this parameter based on the

EARFCN operator's network plan.
NSA PCC PccFreqCfg.NsaPccAnchoring- Set this parameter based on the

Anchoring Priority network plan if an independent
Priority camping policy needs to be
configured for NSA DC UEs.
NSA DC PCC PccFreqCfg.NsaDcPccA4RsrpTh It is recommended that this

A4 RSRP ld parameter be set to a value greater
Threshold than or equal to the coverage-
based inter-frequency handover
threshold for event A2 in the target
cell. This prevents ping-pong
handovers after a handover to the
target cell, for example, PCC
anchoring triggered after a
coverage-based inter-frequency
handover or an outgoing RRC
connection reestablishment.

SingleRAN
The following table describes the parameters that must be set in the NrScgFreqConfig MO to
configure the association between the PCC and SCG frequencies on the LTE side.

Name
PCC DL NrScgFreqConfig.PccDlEarfcn Set this parameter based on the

EARFCN operator's network plan.
SCG DL NrScgFreqConfig.ScgDlArfcn Set this parameter based on the

ARFCN operator's network plan.
SCG DL NrScgFreqConfig.ScgDlArfcnPri Set this parameter based on the

ARFCN ority operator's network plan.
Priority
NSA DC B1 NrScgFreqConfig.NsaDcB1Thld It is recommended that this

Event RSRP Rsrp parameter be set to a value greater
Threshold than or equal to the threshold for
coverage-based PSCell release or
handover on the NR side.
Otherwise, PSCell release or
handover will be triggered
immediately after an SgNB is
added.
NR B1 Time To NrScgFreqConfig.NrB1TimeToT A smaller value of this parameter

Trigger rigger leads to faster event B1
measurement reports. A larger
value of this parameter leads to the
opposite effect.
The following table describes the parameters that must be set in the NrExternalCell MO to
configure external NR cells on the LTE side.

Name
Downlink NrExternalCell.DlArfcn Set this parameter based on the

ARFCN operator's network plan.
Uplink ARFCN NrExternalCell.UlArfcn Set this parameter based on the

operator's network plan.
Physical Cell NrExternalCell.PhyCellId Set this parameter based on the

ID operator's network plan.
Tracking Area NrExternalCell.Tac Set this parameter based on the

Code operator's network plan.

SingleRAN
The following table describes the parameters that must be set in the NrNFreq MO to
configure neighboring NR frequencies on the LTE side.

Name
Downlink NrNFreq.DlArfcn This frequency is the NR SSB

ARFCN frequency. Set this parameter
based on the operator's network
plan.
Uplink ARFCN NrNFreq.UlArfcn Set this parameter based on the

SSB Period NrNFreq.SsbPeriod Set this parameter to the same

value as NRDUCell.SsbPeriod. If
multiple neighboring NR cells
work on the same frequency in the
NR network and have different
SSB periods, it is recommended
that the eNodeB use the maximum
SSB period as the SSB period of
the NR frequency.
If the duration specified by this
parameter is longer than 20 ms,
some NSA DC UEs may have
compatibility problems and fail to
find the NR network. In this case,
if RsvdSwPara3_bit24 of the
ENBRSVDPARA.RsvdSwPara3
parameter is set to 1, the eNodeB
will send an RRC Connection
Reconfiguration message to such
NSA DC UEs to assist them in
searching for the NR network.
SSB Offset NrNFreq.SsbOffset l If gNodeBParam.FrameOffset

is less than or equal to 261120,
the SSB offset is calculated as
follows: SSB offset = Round
((gNodeBParam.FrameOffset/
30720) MOD
NrNFreq.SsbPeriod)
l If gNodeBParam.FrameOffset
is greater than or equal to
275943, the SSB offset is
calculated as follows: SSB
offset = Round
((gNodeBParam.FrameOffset/
30720 – 10 +
NrNFreq.SsbPeriod) MOD
NrNFreq.SsbPeriod)

SingleRAN

Name
Subcarrier NrNFreq.SubcarrierSpacing Set this parameter to the same

Spacing value as
NRDUCell.SubcarrierSpacing.
According to 3GPP TS 38.104 "NR; Base Station (BS) radio transmission and reception", a
neighboring NR frequency belongs to multiple NR frequency bands when its NR-ARFCN
falls into any of the following ranges: 158200-160600, 285400-303400, 386000-398000,
402000-404000, 422000-434000, 514000-537999, 620000-653333, and 2054166-2084999. In
this case, a frequency band must be configured for this neighboring NR frequency through the
NrMfbiFreq MO on the LTE side.
NOTE
This MO needs to be configured when a neighboring NR frequency belongs to multiple frequency

bands. This MO does not need to be configured when a neighboring NR frequency belongs only to one
frequency band.
For example, when the NR-ARFCN of a neighboring NR frequency is within the range of
620000-653333, the frequency belongs to both n77 and n78. In this case, the corresponding frequency
band n77 or n78 must be configured for the neighboring NR frequency on the LTE side through the
NrMfbiFreq MO according to the NR network plan.

Name
Downlink NrMfbiFreq.DlArfcn This frequency is the NR SSB

ARFCN frequency. Set this parameter
based on the operator's network
plan.
Frequency Band NrMfbiFreq.FrequencyBand Set this parameter based on the

The following table describes the parameters that must be set in the NrNRelationship MO to
configure neighboring NR cells on the LTE side.

Name
gNodeB ID NrNRelationship.GnodebId Set this parameter based on the

Local cell ID NrNRelationship.LocalCellId Set this parameter based on the


SingleRAN

Name
Blind NrNRelationship.BlindConfigIn It is recommended that this

Configuration dicator parameter be set to TRUE if the
Indicator LTE cell and the neighboring NR
cell are co-sited and cover the
same area or if the coverage area
of the neighboring NR cell is
larger than that of the LTE cell.
Otherwise, set this parameter to
FALSE.
On an NR frequency, only one
neighboring NR cell has the same
coverage as an LTE cell. If
multiple neighboring NR cells are
configured on one NR frequency,
SgNB additions may fail.
NOTE
NR cells with the same NR-ARFCN and PCI cannot be configured as neighboring cells of the same LTE
cell.
The following table describes the parameters that must be set in the NsaDCMgmtConfig MO
to configure the period and traffic volume threshold parameters for periodic SCG addition
based on the traffic volume on the LTE side.

Name
SCG Addition NsaDCMgmtConfig.ScgAddition The default value is 60. If quicker

Interval Interval SCG additions are required,
decrease the value of this
parameter.
SCG Addition NsaDCMgmtConfig.ScgAddition The default value is 0. It is

Buffer Length BufferLenThld recommended that this parameter
Threshold be set to a value greater than 0 to
avoid frequent SCG additions
triggered by small-packet services.
SCG Addition NsaDCMgmtConfig.ScgAddition The recommended value is 5.

Buffer Delay BufferDelayThld
Threshold
The following table describes the parameters that must be set in the CellQciPara and
NsaDCMgmtConfig MOs on the LTE side and the gNBPdcpParamGroup MO on the NR
side to configure downlink data split policies.

SingleRAN

Name
NSA DC LTE: Set this parameter based on the

Default Bearer CellQciPara.NsaDcDefaultBear- operator's network plan.
Mode erMode
DL Data MCG LTE: It is recommended that this

Split Bearer NsaDCMgmtConfig.DlDataMcg parameter be set to SCG_ONLY.
Mode SplitBearerMode
Downlink Data NR: It is recommended that this

PDCP Split gNBPdcpParamGroup.DlDataP parameter be set to SCG_ONLY.
Mode dcpSplitMode
Board Resource LTE: If the

Assignment BRDRESASSIGNMENT.BRDA CellQciPara.NsaDcDefaultBear-
Mode SSIGNMENT erMode parameter is set to
MCG_SPLIT_BEARER, set this
parameter to MODE3.
The change in the value of this
parameter may change the
transmission specifications and
signaling specifications of the
main control board.
The following table describes the parameters that must be set in the NsaDCMgmtConfig and
gNBPdcpParamGroup MOs to configure uplink data split policies on the LTE and NR sides,
respectively.

Name
UL Data Split LTE: The value INFINITY is

Threshold NsaDCMgmtConfig.UlDataSplit recommended.
Threshold
NSA DC UE LTE: The value 49 is recommended.

MCG UL NsaDCMgmtConfig.NsaDcUeM
AMBR Ratio cgUlAmbrRatio
Uplink Data NR: The value INFINITY is

Split Threshold gNBPdcpParamGroup.UlDataS recommended.
plitThreshold
Uplink Data NR: The value SCG_ONLY is

Split Primary gNBPdcpParamGroup.UlDataS recommended.
Path plitPrimaryPath

SingleRAN
NOTE
Uplink data is transmitted over the X2 link. When packet loss occurs on the X2 link, the transmission
rate of TCP services decreases. If the packet loss rate over the X2 link (the proportion of the number of
lost packets to the total number of packets in a certain period over the X2 link) is greater than 0.0001%,
it is recommended that the uplink data split policy be set to MCG_ONLY in the Option 3 architecture
and be set to SCG_ONLY in the Option 3x architecture.
The PDCP SNs configured for the dedicated bearers with the same QCI on the LTE and NR
sides must be the same. Otherwise, the dedicated bearer establishment fails.
The NSA DC feature splits data at the PDCP layer. It is recommended that the PDCP SN size
be set to 18 bits on both the LTE and NR sides to avoid data transmission interruption caused
by PDCP SN size insufficiency. The configuration method is as follows:
l On the LTE side, the QciPara.NsaDcRlcPdcpParamGroupId parameter specifies the
group ID of the RLC PDCP parameters used in NSA DC scenarios. Set the
RlcPdcpParaGroup.AmPdcpSnSize parameter in the parameter group to
AmPdcpSnSize_18bits(18).
l On the NR side, set gNBPdcpParamGroup.DlPdcpSnSize to PdcpSnSize_18bits(18).
The LTE and NR sides must be configured with the same RLC mode for bearers with the
same QCI. Otherwise, an SgNB cannot be added.
The following table describes the parameters that must be set in the NRCellNsaDcConfig and
NRDUCellSrsMeas MOs to configure uplink fallback to LTE on the NR side.

Name
NSA DC NRCellNsaDcConfig.NsaDcAlgo Select the

Algorithm Switch UL_FALLBACK_TO_LTE_SW
Switch ITCH option.
NSA Uplink NRDUCellSrsMeas.NsaUlFackT The recommended value is -30.

Fallback to LTE oLteSinrThld
SINR Thld
NSA Uplink NRDUCellSrsMeas.NsaUlFackT The recommended value is 30.

Fallback to LTE oLteSinrHyst
SINR Hyst
The following table describes the parameters that must be set in the LTE NsaDCMgmtConfig
MO and NR NRCellNsaDcConfig and NRDuCellSrsMeas MOs to configure uplink power
control.

SingleRAN

Name
NSA DC LTE: LTE: Select the

Algorithm NsaDCMgmtConfig.NsaDcAlgoS NSA_DC_ENH_UL_POWER_
Switch witch CONTROL_SW and
TDM_SWITCH options.
NR:
NR: Select the
NRCellNsaDcConfig.NsaDcAlgo NSA_DC_ENH_UL_POWER_
Switch CONTROL_SW option.
NSA TDM LTE: LTE: The recommended value is

Power Control NsaDCMgmtConfig.NsaTdmPcT -62.
Trigger SINR rigSinrThld NR: The recommended value is
Thld -60.
NR:
NRDUCellSrsMeas.NsaTdmPcTr
igSinrThld
NSA TDM NR: The recommended value is 30.

Power Control NRDUCellSrsMeas.NsaTdmPcTr
Trigger SINR igSinrHyst
Hyst
The following table describes the parameters that must be set in NSADCMGMTCONFIG
and NRDUCELLALGOSWITCH MOs to configure the interference avoidance function on
the LTE and NR sides, respectively. To activate this function, turn on the corresponding
switches on both the LTE and NR sides. To deactivate this function, turn off the switches on
both sides.

Name
NSA DC LTE: Select the

Algorithm NsaDCMgmtConfig.NsaDcAlgoS INTERFERENCE_AVOID_S
Switch witch W and TDM_SWITCH options.
NSA DC NR: l If the interference type is

Algorithm NRDUCellAlgoSwitch.NsaDcAlg secondary intermodulation
Switch oSwitch interference, select the
CROSS_MDLT_INTRF_AV
OID_SW option.
l If the interference type is
secondary harmonic
interference, select the
HARMONIC_INTRF_AVO
ID_SW option.
The following table describes the parameter that must be set in the NRCellNsaDcConfig MO
on the NR side to specify the NR data volume reporting policy in Option 3x.

SingleRAN

Name
NR Data NRCellNsaDcConfig.NrDataVolu l The recommended value is

Volume meRptCfg 65535 if only event-triggered
Reporting NR data volume reporting is
Config required.
l The recommended value is
600 if both event-triggered
and periodic NR data volume
reporting is required.
The following table describes the parameter that must be set in the CellDlSchAlgo MO to
configure NSA DC UE scheduling protection based on the MCG cell load on the LTE side.

Name
MCG High CellDlSchAlgo.McgHighLoadThr The recommended value is 60.

Load Threshold eshold
The following table describes the parameter that must be set in the NsaDcMgmtConfig MO
to specify whether to broadcast the upperLayerIndication IE in SIB2 on the LTE side.

Name
Upper Layer NsaDcMgmtConfig.UpperLayerI The recommended value is

Indication ndicationSwitch NR_NCELL_BASED_BROAD
Switch CAST. It is recommended that
this parameter be set to OFF if
there are UEs not supporting the
R15 upperLayerIndication IE in
the network.
The following table describes the parameters that must be set in the NRCELLQCIBEARER
MO to add the AM or UM PDCP parameter group ID for the corresponding QCI on the NR
side.

Name
AM PDCP NRCellQciBearer.AmPdcpParam Set this parameter based on the

Parameter GroupId operator's network plan.
Group ID

SingleRAN

Name
UM PDCP NRCellQciBearer.UmPdcpParam Set this parameter based on the

Parameter GroupId operator's network plan.
Group ID
The following table describes the parameter that must set in the GNBPDCPPARAMGROUP
MO to specify the PDCP parameter group ID.

Name
PDCP gNBPdcpParamGroup.PdcpPara Set this parameter based on the

Parameter mGroupId value of
Group ID NRCellQciBearer.AmPdcpPara
mGroupId or
NRCellQciBearer.UmPdcpPara
mGroupId configured for the
corresponding QCI.
The following table describes the parameters that must be set in the RlcPdcpParaGroup MO
to allow SCG split bearer setup for GBR services.

Name
RLC-UM or RlcPdcpParaGroup.RlcMode Select the RLC UM or AM mode

RLC-AM mode based on the QCI.
AM Mode RlcPdcpParaGroup.AmPdcpSnSi The recommended value of this

PDCP SN ze parameter is
Length AmPdcpSnsize_18bits when
RlcPdcpParaGroup.RlcMode is
set to RlcMode_AM.
UM PDCP-SN RlcPdcpParaGroup.PdcpSnSize The recommended value of this

size parameter is PdcpSnsize_18bits
when
RlcPdcpParaGroup.RlcMode is
set to RlcMode_UM.
NOTE
In Option 3x, uplink and downlink data of GBR services can be transmitted only on the SCG side.
The following table describes the parameter that must be set in an NrExternalCell MO to
configure the networking mode of an external NR cell on the LTE side in hybrid NSA&SA
networking,

SingleRAN

Name
NR Networking NrExternalCell.NrNetworkingOpt Set this parameter based on the

Option ion operator's network plan.
The following table describes the parameter that must be set in the NsaDcMgmtConfig MO
to configure an adaptive PSCell management policy for VoLTE UEs on the LTE side.

Name
VoLTE Packet NsaDcMgmtConfig.VoltePlrThld The default value is 5%. If this

Loss Rate Thld ForScgRelease parameter is set to a large value,
for SCG voice quality deteriorates.
Release Therefore, it is recommended that
this parameter be set to a value
less than or equal to 5%.
7.2.2 Using MML Commands

Activation Command Examples
On the eNodeB side
//Adding a neighboring NR frequency
ADD NRNFREQ: LocalCellId=21, DlArfcn=636666, UlArfcnConfigInd=NOT_CFG,
SsbOffset=0, SsbPeriod=20MS, SubcarrierSpacing=30KHZ;
//Configuring the frequency band for a neighboring NR frequency whose NR-ARFCN
falls within the following ranges: 158200-160600, 285400-303400, 386000-398000,
402000-404000, 422000-434000, 514000-537999, 620000-653333, and 2054166-2084999
//Setting the frequency band to which the neighboring NR frequency belongs
ADD NRMFBIFREQ: DlArfcn=636666, FrequencyBand=n78;
//Adding an external NR cell
ADD NREXTERNALCELL: Mcc="262", Mnc="01", GnodebId=255, CellId=7, DlArfcn=636666,
UlArfcnConfigInd=NOT_CFG, PhyCellId=1, Tac=1;
//Adding a neighbor relationship with the NR cell
ADD NRNRELATIONSHIP: LocalCellId=21, Mcc="262", Mnc="01", GnodebId=1, CellId=7;
//Adding a candidate PCC
ADD PCCFREQCFG: PccDlEarfcn=1500;
//Adding a candidate SCC to an NR SCG
ADD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=636666, ScgDlArfcnPriority=6,
NsaDcB1ThldRsrp=-105, NrB1TimeToTrigger=40MS;
//Modifying NSA DC management configuration
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoSwitch=NSA_DC_CAPABILITY_SWITCH-1;
MOD CELLQCIPARA: LocalCellId=21, Qci=9, NsaDcDefaultBearerMode=SCG_SPLIT_BEARER;
MOD QCIPARA: Qci=9, NsaDcRlcPdcpParamGroupId=223;
MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=223, RlcMode=RlcMode_AM,
AmPdcpSnSize=AmPdcpSnsize_18bits;
//(Optional) Modifying the period or traffic volume thresholds for periodic SCG
addition
MOD NSADCMGMTCONFIG: LocalCellId=21, ScgAdditionInterval=60,
ScgAdditionBufferLenThld=0, ScgAdditionBufferDelayThld=5;
//(Optional) Enabling intermodulation interference avoidance
MOD NSADCMGMTCONFIG: LocalCellId=21,
NsaDcAlgoSwitch=INTERFERENCE_AVOID_SW-1&TDM_SWITCH-1;
//(Optional) Enabling the configuration of an independent camping policy for NSA

SingleRAN
DC UEs
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoSwitch=NSA_PCC_ANCHORING_SWITCH-1;
MOD PCCFREQCFG: PccDlEarfcn=2950, NsaPccAnchoringPriority=2,
NsaDcPccA4RsrpThld=-105;
//(Optional) Enabling blind SCG addition
NsaDcAlgoSwitch=NSA_BLIND_SCG_ADDITION_SWITCH-1;
MOD NRNRELATIONSHIP: LocalCellId=21, Mcc="262", Mnc="01", GnodebId=1, CellId=7,
BlindConfigIndicator=TRUE;
//(Optional) Enabling power control enhancement in NSA networking
NsaDcAlgoSwitch=NSA_DC_ENH_UL_POWER_CONTROL_SW-1&TDM_SWITCH-1,
NsaTdmPcTrigSinrThld=-62;
//(Optional) Enabling NSA DC UE scheduling protection based on the MCG cell load
MOD CELLDLSCHALGO: LocalCellId=21, McgHighLoadThreshold=60;
//(Optional) Enabling upperLayerIndication broadcast in SIB2
MOD NSADCMGMTCONFIG: LocalCellId=21, UpperLayerIndicationSwitch=ON;
//(Optional) Configuring the networking mode of an external NR cell in hybrid
NSA&SA networking based on the NR network plan
MOD NREXTERNALCELL: Mcc="262", Mnc="01", GnodebId=1, CellId=7,
NrNetworkingOption=NSA;
//(Optional) Configuring an adaptive PSCell management policy for VoLTE UEs
MOD NSADCMGMTCONFIG: LocalCellId=21, VolteUeScgMgmtStrategy="ADAPTIVE",
UlQualityThldForScgRelease=0, VoltePlrThldForScgRelease=5;
On the gNodeB side

//Modifying the downlink data split mode for NR cells
MOD GNBPDCPPARAMGROUP: PdcpParamGroupId=1, DlDataPdcpSplitMode=SCG_ONLY;
//Modifying the settings of Uplink Data Split Primary Path and Uplink Data Split
Threshold
MOD GNBPDCPPARAMGROUP: PdcpParamGroupId=1, UlDataSplitPrimaryPath=SCG,
UlDataSplitThreshold=INFINITY, DlPdcpSnSize=BITS18;
//Setting NR cell algorithm switches
MOD NRCELLALGOSWITCH: NrCellId=7, NsaDcSwitch=ON;
//Modifying the bearer configuration of an NR cell with RLC Mode set to AM and
AmPdcpParamGroupId set to the same value as PdcpParamGroupId
MOD NRCELLQCIBEARER: NrCellId=7, Qci=9, AmPdcpParamGroupId=1, RlcMode=AM;
//(Optional) Configuring event-triggered NR data volume reporting in Option 3x on
the NR side
MOD NRCELLNSADCCONFIG: NrCellId=7, NrDataVolumeRptCfg=65535;
//(Optional) Enabling fallback to LTE and setting the uplink SINR threshold
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=UL_FALLBACK_TO_LTE_SWITCH-1;
MOD NRDUCELLSRSMEAS: NrDuCellId=120, NsaUlFackToLteSinrThld=-30,
NsaUlFackToLteSinrHyst=30;
//(Optional) Turning on the intermodulation interference avoidance switch
MOD NRDUCELLALGOSWITCH: NrDuCellId=120,
NsaDcAlgoSwitch=CROSS_MDLT_INTRF_AVOID_SW-1;
//(Optional) Turning on the harmonic interference avoidance switch
MOD NRDUCELLALGOSWITCH: NrDuCellId=120, NsaDcAlgoSwitch=HARMONIC_INTRF_AVOID_SW-1;
//(Optional) Enabling power control enhancement in NSA networking
MOD NRCELLNSADCCONFIG: NrCellId=7,
NsaDcAlgoSwitch=NSA_DC_ENH_UL_POWER_CONTROL_SW-1;
MOD NRDUCELLSRSMEAS: NrDuCellId=120, NsaTdmPcTrigSinrThld=-60,
NsaTdmPcTrigSinrHyst=30;
Deactivation Command Examples

On the eNodeB side
//Turning off the NSA DC switch on the LTE side
MOD NSADCMGMTCONFIG: LocalCellId=120, NsaDcAlgoSwitch=NSA_DC_CAPABILITY_SWITCH-0;
//(Optional) Disabling event-triggered NR data volume reporting in Option 3 on
the LTE side
MOD NSADCMGMTCONFIG: LocalCellId=0, NrDataVolumeRptCfg=0;
//(Optional) Turning off the interference avoidance switch
MOD NSADCMGMTCONFIG: LocalCellId=120, NsaDcAlgoSwitch=INTERFERENCE_AVOID_SW-0;
//(Optional) Enabling the configuration of an independent camping policy for NSA
DC UEs

SingleRAN
MOD NSADCMGMTCONFIG: LocalCellId=120, NsaDcAlgoSwitch= NSA_PCC_ANCHORING_SWITCH-0;

//(Optional) Disabling power control enhancement in NSA networking
//(Optional) Disabling NSA DC UE scheduling protection based on the MCG cell load
MOD CELLDLSCHALGO: LocalCellId=120, McgHighLoadThreshold=100;
//(Optional) Disabling blind SCG addition
MOD NSADCMGMTCONFIG: LocalCellId=120, NsaDcAlgoSwitch=
NSA_BLIND_SCG_ADDITION_SWITCH-0;
//(Optional) Disabling upperLayerIndication broadcast in SIB2
MOD NSADCMGMTCONFIG: LocalCellId=0, UpperLayerIndicationSwitch=OFF;
On the gNodeB side

//Turning off the NSA DC switch on the NR side
MOD NRCELLALGOSWITCH: NrCellId=7, NsaDcSwitch=OFF;
//(Optional) Disabling fallback to LTE
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=UL_FALLBACK_TO_LTE_SWITCH-0;
//(Optional) Disabling event-triggered NR data volume reporting in Option 3x on
the NR side
MOD NRCELLNSADCCONFIG: NrCellId=7, NrDataVolumeRptCfg=0;
//(Optional) Turning off the intermodulation interference avoidance switch
MOD NRDUCELLALGOSWITCH: NRDUCellId=120,
NsaDcAlgoSwitch=CROSS_MDLT_INTRF_AVOID_SW-0;
//(Optional) Turning off the harmonic interference avoidance switch
MOD NRDUCELLALGOSWITCH: NRDUCellId=120, NsaDcAlgoSwitch=HARMONIC_INTRF_AVOID_SW-0;
//(Optional) Disabling power control enhancement in NSA networking
MOD NRCELLNSADCCONFIG: NrCellId=7,
7.2.3 Using the CME

l Fast batch activation
This function can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/batch configuration
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME.
For detailed operations, see CME-based Feature Configuration.
NOTE
LTE supports batch activation, whereas NR does not.

l Simplified automatic generation of NSA deployment scripts
You can use the CME to quickly generate a summary data file for base station
deployment in NSA DC. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Managing a Summary Data File > Editing a
Summary Data File.
7.3 Activation Verification

Monitoring Counters
Fast subscription to NSA DC-related counters is supported. You can select this feature on the
U2020 to subscribe to the counters corresponding to this feature in one-click mode.

SingleRAN
l After activating NSA DC, observe the counters listed in the following tables. On a
network with NSA DC UEs, NSA DC has taken effect only if all the counters produce
non-zero values.
On the eNodeB side
Counter ID Counter Name
1526747850 L.Traffic.User.NsaDc.PCell.Avg
On the gNodeB side
1911816745 N.User.NsaDc.PSCell.Avg
l After the NSA DC PCC anchoring function is enabled, observe the following counters to
determine whether the function has taken effect and calculate the handover success rate:
If all the following counters produce non-zero values, the feature has taken effect. If any
counter produces a zero value, check that the NSA_PCC_ANCHORING_SWITCH
option of the NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is selected,
PccFreqCfg.PccDlEarfcn and PccFreqCfg.NsaPccAnchoringPriority are set to non-
zero values, and the UE capability (the DC combination in the UE-MRDC-Capability IE
of the UECapabilityInformation message) supports NSA DC with the target frequency.
1526749449 L.NsaDC.PCCAnchor.HHO.PrepAttOut
1526749450 L.NsaDC.PCCAnchor.HHO.ExecAttOut
1526749451 L.NsaDC.PCCAnchor.HHO.ExecSuccOut
l Observe whether NSA DC UE scheduling protection based on the MCG cell load has
taken effect.
Assume that the downlink PRBs of the current cell are occupied by both LTE UEs and
NSA DC UEs. If the number of PRBs required by LTE UEs increases and is greater than
the number of remaining downlink PRBs, this function takes effect.
After this feature takes effect, if the downlink PRB usage of an LTE cell (indicated by
L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail x 100%) becomes greater
than the preset threshold, the traffic distributed to the LTE side (measured by
N.PDCP.Vol.DL.X2U.TrfPDU.Tx) decreases.
l Observe whether data split takes effect in NSA DC.
– The counter N.PDCP.Vol.DL.X2U.TrfPDU.Tx indicates the total downlink data
volume split for NSA DC UEs over the X2 interface. If the counter value is greater
than 0, downlink data split has taken effect.
– The counter N.PDCP.Vol.UL.X2U.TrfPDU.Rx indicates the total uplink data
volume split for NSA DC UEs over the X2 interface. If the counter value is greater
than 0, uplink data split has taken effect.

SingleRAN
Message Tracing
1. Log in to the U2020, and then choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree on the left of the Signaling Trace Management tab
page, choose Trace Type > LTE > Application Layer > Uu Interface Trace.
2. Select the eNodeB and gNodeB, set trace task parameters as described in 7.2.1 Data
Preparation, and then click Finish to start signaling tracing over the Uu interface.
3. Trace UE random access.
Log in to the Web LMT, and choose Trace > LTE Services > Uu Interface Trace. The
trace result shows an RRC_CONN_SETUP_CMP message sent from the UE to the
eNodeB for network access.
4. (Optional) It is traced that the eNodeB delivers an NR measurement configuration
message to the UE.
trace result shows an RRC_CONN_RECFG message with the EventB1 IE sent from the
eNodeB to the UE.
5. (Optional) It is traced that the UE reports measurement results.

trace result shows an RRC_MEAS_RPRT message reported by the UE, containing IEs
related to the measured PCI and signal strength of the NR cell.

SingleRAN
NOTE
If blind SCG configuration is enabled, the eNodeB does not deliver measurement control
messages for neighboring NR frequencies after entering the blind configuration procedure.
Therefore, signaling messages for measurement control delivery and measurement report reporting
in 4 and 5 cannot be traced over the Uu interface.
If blind PSCell configuration is performed and the UE attempts to access a target cell without NR
coverage, the access will fail. In this case, the UE sends an SCG Failure Information message to
the eNodeB. The value of the L.NsaDc.ScgFailure counter increases. If the SgNB addition
success rate (indicated by L.NsaDc.SgNB.Add.Succ/L.NsaDc.SgNB.Add.Att) is less than 98%
before or after blind PSCell configuration is enabled, blind PSCell configuration is not
recommended.
6. It is traced that the SgNB is added on the LTE side.
Log in to the Web LMT, and choose Trace > LTE Services > X2 Interface Trace. You
can view that the eNodeB sends an SGNB_ADD_REQ message to the gNodeB over the
X2 interface. The gNodeB responds with an SGNB_ADD_REQ_ACK message. The
eNodeB sends an SGNB_RECONFIG_CMP message, indicating that the SCG addition
procedure is complete.
7. The eNodeB configures the SCG for the UE. The UE returns a message indicating that
the configuration is complete.
Log in to the Web LMT, and choose Trace > LTE Services > Uu Interface Trace. You
can view that the eNodeB sends an RRC_CONN_RECFG message to the UE. This
message contains the nr-config-r15 IE.
8. The eNodeB sends an ERAB MOD message to the core network over an S1 interface.
Log in to the Web LMT, and choose Trace > LTE Services > S1 Interface Trace. You
can view that the eNodeB sends an S1AP_E_RAB_MOD_IND message to the core
network, instructing the core network to send the UE's downlink data to the gNodeB.

SingleRAN
NOTE
For LTE-NR joint tracing, joint tracing must be started before the UE accesses the network.
9. (Optional) Check whether uplink fallback to LTE takes effect.
Log in to the Web LMT, and choose Trace > LTE Services > X2 Interface Trace. You
can view that the value of primaryPath in the SgNB to MeNB Container > CG-
Config > scg-RB-Config > drb-ToAddModList > pdcp-Config IE of the SgNB
Modification Required message sent from the gNodeB to the eNodeB is 0 (that is,
MCG), and the value of ul-DataSplitThreshold is infinity.
10. (Optional) Check whether the interference avoidance function has taken effect.
Log in to the Web LMT, and choose Trace > LTE Services > X2 Interface Trace.
Check whether the bits in the UL Coordination Information IE of the SgNB Resource
Coordination Information IE in the SGNB ADDITION REQUEST ACKNOWLEDGE
or SGNB MODIFICATION REQUEST ACKNOWLEDGE message sent from the
gNodeB to the eNodeB are not all 0s. If the bits are not all 0s, this function has taken
effect. If the bits are all 0s, this function has not taken effect.
11. (Optional) Check whether TDM power control has taken effect.
Log in to the Web LMT, and choose Trace > LTE Services > Uu Interface Trace.
Check whether the RRC_CONN_RECFG message sent from the eNodeB to the UE
carries the tdm-pattern-config-R15 IE and whether P-maxEUTRA and P-maxNR-FR1
are set to 23. Choose Trace > LTE Services > X2 Interface Trace. The bitmap in the
UL Coordination Information IE of the SgNB Resource Coordination Information IE in
the SGNB ADDITION REQUEST ACKNOWLEDGE, SGNB MODIFICATION
REQUEST ACKNOWLEDGE, or SGNB MODIFICATION REQUIRED message sent
from the gNodeB to the eNodeB indicates the TDM-Pattern.
12. (Optional) Observe whether the SIB2 contains the upperLayerIndication IE.
Log in to the Web LMT, and choose Trace > LTE Services > Uu Interface Trace. You
can view that the SIB2 sent by the base station contains the upperLayerIndication IE.
7.4 Network Monitoring

Monitor the counters listed in the following table and compare them against the network plan
to evaluate the feature performance. In Option 3, user-plane data is split at the PDCP layer of
the MeNB. Therefore, the monitoring results are observed on the eNodeB side. In Option 3x,
user-plane data is split at the PDCP layer of the SgNB. Therefore, the monitoring results are

SingleRAN
observed on the gNodeB side. The counters related to the user plane at the LTE PDCP layer
do not measure the throughput of NSA DC UEs.
l On the eNodeB side
– After NSA DC is enabled, observe the following counters to determine whether the
handover success rate and service drop rate of NSA DC UEs are different from
those of LTE-only UEs:
n Outgoing handover success rate of NSA DC UEs =
L.NsaDc.HHO.ExecSuccOut/L.NsaDc.HHO.ExecAttOut x 100%
n Incoming handover success rate of NSA DC UEs =
L.NsaDc.PCell.Change.Exec/L.NsaDc.PCell.Change.Succ x 100%
n Abnormal service drop rate of NSA DC UEs = L.NsaDc.E-RAB.AbnormRel/
L.NsaDc.E-RAB.NormRel x 100%
– The total downlink data split volume of NSA DC UEs equals the sum of
L.Thpt.bits.DL.McgSplit.MeNB and L.Thpt.bits.DL.McgSplit.SgNB. If the total
downlink data split volume is greater than the total downlink data volume of non-
NSA DC UEs, this feature is running properly.
– The total uplink data split volume of NSA DC UEs equals the sum of
L.Thpt.bits.UL.McgSplit.MeNB and L.Thpt.bits.UL.McgSplit.SgNB. If the total
uplink data split volume is greater than the total uplink data volume of non-NSA
DC UEs, this feature is running properly.
– Observe the values of the L.Thrp.bits.DL and L.Thrp.bits.UL counters to
determine the total uplink and downlink data volumes of non-NSA DC UEs.
– Observe the values of the L.ChMeas.PRB.DL.NsaDc.Used.Avg and
L.ChMeas.PRB.UL.NsaDc.Used.Avg counters to determine the PRB usage of
NSA DC UEs on the LTE side.
– Observe the L.Thrp.bits.DL.NsaDc, L.Thrp.bits.DL.LastTTI.NsaDc, and
L.Thrp.Time.DL.RmvLastTTI.NsaDc counters to determine the downlink
throughput of NSA DC UEs on the LTE side.
– Observe the L.Thrp.bits.UL.NsaDc and L.Thrp.Time.UL.NsaDc counters to
determine the uplink throughput of NSA DC UEs on the LTE side.
NOTE
A non-NSA DC UE refers to an LTE-only UE or an NSA DC-capable UE whose data is

transmitted only on the MCG side or on the SCG side.
l On the gNodeB side
– The counter N.PDCP.Vol.DL.X2U.TrfPDU.Tx indicates the total downlink data
volume split for NSA DC UEs over the X2 interface. If the value of this counter
increases continuously, this feature is working properly.
– The counter N.PDCP.Vol.UL.X2U.TrfPDU.Rx indicates the total uplink data
volume split for NSA DC UEs over the X2 interface. If the value of this counter
increases continuously, this feature is working properly.

SingleRAN
Description 8 Parameters
8 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l 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-020100.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

SingleRAN
Description 9 Counters
9 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l 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-020100.
Step 3 Click OK. All counters related to the feature are displayed.
----End

SingleRAN
Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
Description 11 Reference Documents
11 Reference Documents
l 3GPP TS 38.101: "NR; User Equipment (UE) radio transmission and reception"
l 3GPP TS 37.340: "E-UTRA and NR; Multi-connectivity; Stage-2"
l 3GPP TS 36.331: "E-UTRA; Radio Resource Control (RRC) Protocol specification"
l Transmission Resource Management in 5G RAN Feature Documentation
l Power Control in 5G RAN Feature Documentation
l Carrier Aggregation in eRAN Feature Documentation
l Idle Mode Management in eRAN Feature Documentation
l Scheduling in eRAN Feature Documentation
l QoS Management in eRAN Feature Documentation
l Breathing Pilot in eRAN Feature Documentation
l Air Interface Latency Optimization in eRAN Feature Documentation
l UL and DL Decoupling
l X2 and S1 Self-Management in NSA Networking
l BBU Interconnection in 3900 & 5900 Series Base Station Product Documentation

NSA Networking Based On EPC (SRAN15.1 - 04)

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

NSA Networking Based On EPC (SRAN15.1 - 04)

Uploaded by

Copyright:

Available Formats

SingleRAN

NSA Networking based on EPC

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 9

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. ii

4.3.2 CP/UP Data Separation............................................................................................................................................. 42

7 Operation and Maintenance......................................................................................................73

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. iii

1.1 SRAN15.1 04 (2019-09-10)

Supported independent control of PCC Activated RsvdSwPara6_bit28 of the

Added support for independent control of Activated RsvdSwPara6_bit29 of the

Added support for NSA DC PCC priorities Activated RsvdSwPara6_bit25 of the

Optimized adaptive PSCell management None

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 1

1.2 SRAN15.1 03 (2019-07-20)

Optimized S1-based inter-MeNB handover None

1.3 SRAN15.1 02 (2019-06-29)

1.4 SRAN15.1 01 (2019-06-06)

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 2

Supported the decoupling of handover Added the following parameters:

Enhanced the NSA DC PCC anchoring l Added the

Added support for S1-based inter-MeNB Added the

Added the relationships between NSA DC None

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 3

Change Description Parameter Change

Supported selection of neighboring NR cells Added the

1.5 SRAN15.1 Draft E (2019-05-10)

Added configuration requirements for LTE None

Supported the configuration of whether the Added the

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 4

Change Description Parameter Change

Supported decoupling of the parameter Added the following parameters:

1.6 SRAN15.1 Draft D (2019-04-10)

Added automatic generation of scripts for None

1.7 SRAN15.1 Draft C (2019-03-18)

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 5

Added support for TDM power control. For LTE side:

Optimized NR data volume reporting. For None

Supported separate measurement of KPIs None

Supported delivery of the None

Added support for NR by 3900 series base None

Added the UMPTg board that supports LTE None

1.8 SRAN15.1 Draft B (2019-02-24)

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 6

Added support for configuring the Added the NrScgFreqConfig.ScgDlArfcn

Supported the SgNB change during an None

1.9 SRAN15.1 Draft A (2018-12-30)

Added license control on the LTE and NR None

Added support for selection of QCI- Added the following parameter:

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 7

Change Description Parameter Change

Added support for this feature by the None

Added NSA DC UE scheduling protection Added the following parameter:

Added the processing procedure when a None

Added support for blind PSCell None

Added support for NSA DC PCC Added the

Issue 04 (2019-09-10) Copyright © Huawei Technologies Co., Ltd. 8

2 About This Document

2.1 General Statements

2.2 Applicable RAT