SingleRAN

EPC-based NSA Basics Feature

Parameter Description

Issue 01
Date 2024-03-09

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2024. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: https://www.huawei.com
Email: [email protected]

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. i

Security Declaration
Vulnerability
Huawei's regulations on product vulnerability management are subject to the Vul. Response Process. For
details about this process, visit the following web page:
https://www.huawei.com/en/psirt/vul-response-process
For vulnerability information, enterprise customers can visit the following web page:
https://securitybulletin.huawei.com/enterprise/en/security-advisory

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. ii

SingleRAN
EPC-based NSA Basics Feature Parameter
Description Contents

Contents

1 Change History.........................................................................................................................1
2 About This Document.............................................................................................................6
2.1 General Statements................................................................................................................................................................ 6
2.2 Applicable RAT......................................................................................................................................................................... 7
2.3 Features in This Document.................................................................................................................................................. 7

3 Overview....................................................................................................................................9
3.1 Introduction............................................................................................................................................................................... 9
3.2 Related Concepts..................................................................................................................................................................... 9
3.3 Architecture............................................................................................................................................................................. 11
3.4 EN-DC Band Combinations............................................................................................................................................... 13

4 NSA Networking Based on EPC..........................................................................................19

4.1 Principles.................................................................................................................................................................................. 19
4.1.1 Carrier Management in NSA DC.................................................................................................................................. 19
4.1.1.1 MCG Carrier Management......................................................................................................................................... 19
4.1.1.1.1 SCC Management....................................................................................................................................................... 19
4.1.1.1.2 Uplink CA in EN-DC................................................................................................................................................... 22
4.1.1.2 SCG Carrier Management........................................................................................................................................... 23
4.1.1.2.1 Measurement-based PSCell Configuration........................................................................................................ 29
4.1.1.2.2 PSCell Management for VoLTE UEs......................................................................................................................33
4.1.1.2.3 PSCell SMTC on the LTE Side.................................................................................................................................. 34
4.1.1.2.4 PSCell Addition Based on Virtual Grid Models................................................................................................. 36
4.1.1.2.5 SPID-based SCG Frequency Priority Configuration......................................................................................... 37
4.1.1.2.6 Operator-specific SCG Frequency Priority Configuration.............................................................................. 38
4.1.1.2.7 Differentiated SCG Addition and Deletion Threshold Configuration for NR CA-capable UEs.........38
4.1.1.3 SPID/QCI-specific Carrier Management................................................................................................................. 39
4.1.1.3.1 SPID-specific NSA PCC Anchoring and PSCell Management Policies.......................................................39
4.1.1.3.1.1 Multi-Carrier Configuration Group................................................................................................................... 39
4.1.1.3.1.2 SPID-specific SCG Addition at Short Intervals Without Considering Traffic Volume....................... 42
4.1.1.3.2 QCI-specific NSA PCC Anchoring and PSCell Management Policies.........................................................42
4.1.1.3.2.1 Multi-Carrier Configuration Group................................................................................................................... 42
4.1.1.3.2.2 QCI-specific SCG Addition at Short Intervals Without Considering Traffic Volume.........................45
4.1.2 Data Split in NSA DC........................................................................................................................................................45

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. iii

SingleRAN
EPC-based NSA Basics Feature Parameter
Description Contents

4.1.2.1 Data Split Policy Selection.......................................................................................................................................... 46

4.1.2.1.1 Downlink Data Split................................................................................................................................................... 47
4.1.2.1.2 Uplink Data Split.........................................................................................................................................................51
4.1.2.2 Uplink Fallback to LTE.................................................................................................................................................. 54
4.1.2.3 Fast Retransmission for Downlink Data Split....................................................................................................... 55
4.1.2.4 CP/UP Separation........................................................................................................................................................... 55
4.1.2.5 UL/DL Separation........................................................................................................................................................... 57
4.1.2.6 NSA UE Data Split Based on CCE Usage............................................................................................................... 57
4.1.2.7 SPID-based NSA Uplink Primary Path Configuration........................................................................................ 60
4.1.3 Uplink Power Control in NSA DC................................................................................................................................. 61
4.1.4 Interference Avoidance in NSA DC.............................................................................................................................. 62
4.1.4.1 Interference Type Identification................................................................................................................................ 63
4.1.4.2 Interference Avoidance Policies.................................................................................................................................64
4.1.4.3 Implementation of Interference Avoidance.......................................................................................................... 64
4.1.5 NSA DC Virtual Grid Models..........................................................................................................................................66
4.1.6 Other Functions in NSA DC........................................................................................................................................... 71
4.1.6.1 NR Data Volume Reporting........................................................................................................................................ 71
4.1.6.2 S-KgNB Update................................................................................................................................................................. 73
4.1.6.3 gNodeB and UE Signaling Exchange on SRB3..................................................................................................... 73
4.1.6.4 Uplink Single-Side Transmission (Trial).................................................................................................................. 74
4.1.6.5 Uplink Preallocation...................................................................................................................................................... 76
4.1.6.6 SCG Release and Addition Based on UE Overheating Status Reporting.................................................... 78
4.1.6.7 Intra-Band EN-DC.......................................................................................................................................................... 79
4.1.6.8 EN-DC Band Combination Blacklist Function...................................................................................................... 82
4.1.6.9 RRC Connection Reestablishment Optimization for Defective NSA UEs.................................................... 83
4.1.6.10 Scheduling Protection Against the Impact of NR SRS Antenna Switching on LTE Bands.................. 84
4.1.6.11 NCGI Measurement Optimization in EN-DC......................................................................................................85
4.2 Network Analysis.................................................................................................................................................................. 86
4.2.1 Benefits................................................................................................................................................................................. 86
4.2.2 Impacts.................................................................................................................................................................................. 88
4.3 Requirements....................................................................................................................................................................... 103
4.3.1 Licenses............................................................................................................................................................................... 103
4.3.2 Software............................................................................................................................................................................. 103
4.3.3 Hardware........................................................................................................................................................................... 108
4.3.4 Networking....................................................................................................................................................................... 110
4.3.5 Others................................................................................................................................................................................. 112
4.4 Operation and Maintenance.......................................................................................................................................... 113
4.4.1 When to Use..................................................................................................................................................................... 113
4.4.2 Data Configuration......................................................................................................................................................... 113
4.4.2.1 Data Preparation..........................................................................................................................................................113
4.4.2.2 Using MML Commands............................................................................................................................................. 149
4.4.2.3 Using the MAE-Deployment.................................................................................................................................... 155

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. iv

SingleRAN
EPC-based NSA Basics Feature Parameter
Description Contents

4.4.3 Activation Verification................................................................................................................................................... 155

4.4.4 Network Monitoring...................................................................................................................................................... 160

5 Parameters............................................................................................................................163
6 Counters................................................................................................................................ 165
7 Glossary................................................................................................................................. 166
8 Reference Documents........................................................................................................ 167

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. v

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 1 Change History

1 Change History

The following describes the specific changes in different issues.

SRAN20.1 01 (2024-03-09)
This issue includes the following changes.
● Technical changes
None
● Editorial changes
– Revised the descriptions of some impacted functions. For details, see
4.2.2 Impacts.
– Added the mutually exclusive relationship of collaboration between
ROHC and NR PDCP with the NSA DC capability switch. For details, see
4.3.2 Software.
– Revised the MML command examples related to data split on the
gNodeB side. For details, see 4.4.2.2 Using MML Commands.
– Revised descriptions in this document.

SRAN20.1 Draft B (2024-02-06)

This issue includes the following changes.
● Technical changes
Change Description Parameter Change Base Station
Model

Optimized the specified Added parameter on ● 3900 and 5900

band configuration function the LTE side: Added the series base
in EN-DC band combination OperatorBand.BandAtt stations (macro
capability query. For details, ribute parameter. base stations)
see Specified Band ● DBS3900
Configuration in 3.4 EN- LampSite and
DC Band Combinations. DBS5900
LampSite

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 1

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 1 Change History

● Editorial changes
– Added the mutually exclusive relationship between TDM and ultra-low-
latency scheduling for inter-eNodeB CA based on relaxed backhaul. For
details, see 4.3.2 Software.
– Revised descriptions in this document.

SRAN20.1 Draft A (2023-12-31)

This issue is the first release. This document is derived from NSA Networking
based on EPC in SRAN19.1 and describes the basic principles and functions of NSA
networking based on EPC. This issue introduces the following changes to
SRAN19.1 06 (2023-11-30).
● Technical changes
Change Description Parameter Change Base Station
Model

Added the preferential Modified parameters on ● 3900 and 5900

selection of a band the LTE side: series base
combination with only one ● Added the stations (macro
NR carrier for NSA UEs NSA_NR_SINGLE_BC base stations)
function. For details, see: _PREFER_SW option ● DBS3900
● 4.1.1.2 SCG Carrier to the LampSite and
Management EnodebAlgoExtSwit DBS5900
● 4.2.1 Benefits ch.MultiNetworking LampSite
OptionOptSw
● 4.3.2 Software parameter.
● 4.4.2.1 Data ● Added the
Preparation NSA_NR_SINGLE_BC
● 4.4.2.2 Using MML _PREFER_SW option
Commands to the
UeCompat.Whitelist
CtrlExtSwitch1
parameter.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 2

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 1 Change History

Change Description Parameter Change Base Station

Model

Enabled differentiated SCG Modified parameter on ● 3900 and 5900

addition and deletion the LTE side: Added the series base
threshold configuration for SCG_ADD_B1_THLD_DI stations (macro
NR CA-capable UEs. For FF_SW option to the base stations)
details, see: NsaDcAlgoParam.NsaD ● DBS3900
● 4.1.1.2.7 Differentiated cAlgoExtSwitch LampSite and
SCG Addition and parameter. DBS5900
Deletion Threshold Added parameter on LampSite
Configuration for NR the LTE side: Added the
CA-capable UEs NrScgFreqConfig.CaUe
● 4.2.1 Benefits ScgAddRsrpThldOffset
parameter.
● 4.2.2 Impacts
Added parameter on
● 4.3.2 Software the NR side: Added the
● 4.4.2.1 Data NRCellNsaDcConfig.Ca
Preparation CapUePscellA2RsrpThl
● 4.4.2.2 Using MML dOfs parameter.
Commands

Added blacklist control for Modified parameter on ● 3900 and 5900

SCC management in NSA the LTE side: Added the series base
networking. For details, see: NSA_CA_FORBID_SW stations (macro
● 4.1.1.1.1 SCC option to the base stations)
Management UeCompat.BlacklistCo ● DBS3900
ntrolExtSwitch2 LampSite and
● 4.4.2.1 Data parameter.
Preparation DBS5900
LampSite
● 4.4.2.2 Using MML
Commands

Added a counter to the None ● 3900 and 5900

"Number of Times Virtual series base
Grid Models Take Effect" stations (macro
function subset. For details, base stations)
see 4.4.3 Activation ● DBS3900
Verification. LampSite and
DBS5900
LampSite

Added descriptions of the None ● 3900 and 5900

BBU5910. For details, see: series base
● 4.3.3 Hardware stations (macro
base stations)
● 4.3.4 Networking
● DBS3900
LampSite and
DBS5900
LampSite

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 3

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 1 Change History

Change Description Parameter Change Base Station

Model

Added the function of Modified parameter on ● 3900 and 5900

measurement and penalty the LTE side: Added the series base
for SCG addition based on VG_SCG_ADD_MEAS_A stations (macro
virtual grids. For details, ND_PUNISH_SW option base stations)
see: to the LnrCarrierSelec- ● DBS3900
● 4.1.1.2.4 PSCell tion.LnrCarrierSelec- LampSite and
Addition Based on tionSw parameter. DBS5900
Virtual Grid Models LampSite
● 4.2.2 Impacts
● 4.4.2.1 Data
Preparation
● 4.4.2.2 Using MML
Commands

Revised the impact None ● 3900 and 5900

relationship between uplink series base
fallback to LTE and Cell stations (macro
Combination, as Cell base stations)
Combination in DPS ● DBS3900
transmission mode is now LampSite and
supported. For details, see DBS5900
4.2.2 Impacts. LampSite

Added the impact None ● 3900 and 5900

relationship of DSS and NR series base
Flexible Refarming with stations (macro
NSA networking based on base stations)
EPC. For details, see 4.2.2 ● DBS3900
Impacts. LampSite and
DBS5900
LampSite

Added the impact None 3900 and 5900

relationship of PC2 UE series base stations
uplink NR power (macro base
configuration maximization stations)
with initial power control in
NSA DC. For details, see
4.2.2 Impacts.

● Editorial changes
– Reorganized this document and reworded the information.
Split NSA Networking based on EPC into EPC-based NSA Basics, EPC-
based NSA Performance Enhancement, and EPC-based NSA Experience
Improvement. This document focuses on EPC-based NSA basics.
– Revised the names of some mutually exclusive functions to be consistent
with those in reference documents. For details, see 4.3.2 Software.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 4

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 1 Change History

– Added the mutually exclusive relationship between PSCell management

for VoLTE UEs and blind PSCell addition for EPS fallback UEs. For details,
see 4.3.2 Software.
– Renamed the function of fast PSCell addition based on virtual grid
models as PSCell addition based on virtual grid models. For details, see
4.1.1.2.4 PSCell Addition Based on Virtual Grid Models.
– Changed Multi-Frequency Convergence to Multi-Frequency Smart
Aggregation in 5G RAN feature documentation. For details, see 4.2.2
Impacts and 8 Reference Documents.
– Moved a prerequisite function of NSA PCC anchoring based on virtual
grids to EPC-based NSA Performance Enhancement from 4.3.2 Software.
– Revised the setting notes for the Virtual Grid Mdl Pred NR SCG Meas
RSRP Thld parameter in PSCell addition based on virtual grid models. For
details, see 4.4.2.1 Data Preparation.
– Added descriptions of data preparation and command examples for
functions related to NSA DC virtual grid models. For details, see 4.4.2.1
Data Preparation and 4.4.2.2 Using MML Commands.
– Added descriptions of the counter for measuring the number of times NR
measurement configurations are delivered in NSA DC scenarios. For
details, see 4.4.3 Activation Verification.
– Added a counter to measure the number of times NR gap-free
measurement configurations are delivered in NSA DC scenarios. For
details, see 4.4.3 Activation Verification.
– Revised MML command examples. For details, see 4.4.2.2 Using MML
Commands.
– Revised the name of the reference document Scheduling because the
document is split into Uplink Scheduling and Downlink Scheduling in 5G
RAN feature documentation. The involved sections are not listed here.
– Revised descriptions in this document.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 5

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 2 About This Document

2 About This Document

2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE

This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Functions mentioned in this document work properly only when enabled in the
specified applicable scenarios (such as RAT and networking). If a function not
mentioned in this document is enabled or a function is enabled in a scenario not
specified as applicable, exceptions or other impacts may occur.

Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.

Trial Features
Trial features are features that are not yet ready for full commercial release for
certain reasons. For example, the industry chain (terminals/CN) may not be
sufficiently compatible. However, these features can still be used for testing

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 6

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 2 About This Document

purposes or commercial network trials. Anyone who desires to use the trial
features shall contact Huawei and enter into a memorandum of understanding
(MoU) with Huawei prior to an official application of such trial features. Trial
features are not for sale in the current version but customers may try them for
free.
Customers acknowledge and undertake that trial features may have a certain
degree of risk due to absence of commercial testing. Before using them, customers
shall fully understand not only the expected benefits of such trial features but also
the possible impact they may exert on the network. In addition, customers
acknowledge and undertake that since trial features are free, Huawei is not liable
for any trial feature malfunctions or any losses incurred by using the trial features.
Huawei does not promise that problems with trial features will be resolved in the
current version. Huawei reserves the rights to convert trial features into
commercial features in later R/C versions. If trial features are converted into
commercial features in a later version, customers shall pay a licensing fee to
obtain the relevant licenses prior to using the said commercial features. If a
customer fails to purchase such a license, the trial feature(s) will be invalidated
automatically when the product is upgraded.

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.

2.3 Features in This Document

This document describes the following features.

RAT Feature ID Feature Name Chapter/Section

LTE FDD MRFD-131 NSA Networking based ● 4.1.1 Carrier

122 on EPC (LTE FDD) Management in NSA
DC
LTE TDD MRFD-131 NSA Networking based
● 4.1.2 Data Split in NSA
132 on EPC (LTE TDD)
DC
● 4.1.3 Uplink Power
Control in NSA DC
● 4.1.4 Interference
Avoidance in NSA DC
● 4.1.5 NSA DC Virtual
Grid Models
● 4.1.6 Other Functions
in NSA DC
● 4.2 Network Analysis
● 4.3 Requirements
● 4.4 Operation and
Maintenance

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 7

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 2 About This Document

RAT Feature ID Feature Name Chapter/Section

NR MRFD-131 NSA Networking based ● 4.1.2 Data Split in NSA

162 on EPC (NR) DC
● 4.1.4 Interference
Avoidance in NSA DC
● 4.1.6 Other Functions
in NSA DC
● 4.2 Network Analysis
● 4.3 Requirements
● 4.4 Operation and
Maintenance

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 8

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

3 Overview

3.1 Introduction
In non-standalone (NSA) networking based on evolved packet core (EPC), UEs
that support NSA dual connectivity (DC) can connect to both an LTE eNodeB
and a New Radio (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 NSA networking based on EPC

3.2 Related Concepts

Figure 3-2 is used as an example to illustrate concepts involved in NSA
networking and Table 3-1 describes these concepts. In the figure, cells 1 and 3 are
co-coverage cells under the eNodeB, and cells 2 and 4 are co-coverage cells under
the gNodeB. Each cell corresponds to a carrier. DC is provided for the NSA UE after
two carriers are aggregated on the eNodeB and two carriers are aggregated on
the gNodeB.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 9

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

Figure 3-2 NSA networking

Table 3-1 Related concepts

Cate Conce Description
gory pt

Base MeNB The master eNodeB (MeNB) of an NSA UE in the DC state is

statio an LTE base station that serves the cell on which the UE is
n currently camping. Only an eNodeB can be configured as a
master base station.

SgNB The secondary gNodeB (SgNB) of the NSA UE is an NR base

station configured for the UE through an RRC message sent by
the MeNB. Only a gNodeB can be configured as a secondary
base station.

Cell MCG The master cell group (MCG) of the NSA UE is an LTE cell
grou group configured on the LTE side. In Figure 3-2, cells 1 and 3
p form the MCG.

SCG The secondary cell group (SCG) of the NSA UE is an NR cell

group configured on the NR side. In Figure 3-2, cells 2 and 4
form the SCG.

Cell PCell The primary cell (PCell) of the NSA UE is a cell that is served
by the MeNB and that the UE is camping on. In Figure 3-2, cell
1 is the PCell.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 10

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

Cate Conce Description

gory pt

PSCell The primary SCG cell (PSCell) of the NSA 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
once it is configured successfully. In Figure 3-2, cell 2 is the
PSCell.

SCell A secondary cell (SCell) of the NSA UE is a cell served by the

MeNB or SgNB and configured for the UE through an RRC
message sent by the MeNB. This cell can provide the UE with
additional radio resources. In Figure 3-2, cells 3 and 4 are
SCells.
The PUCCH is available in each PCell and PSCell but not
available in any SCell.

Carri CC CCs are the carriers that are aggregated for the UE.
er
PCC The primary component carrier (PCC) is the carrier of the PCell.
In Figure 3-2, the carrier of cell 1 is the PCC.

PSCC The primary secondary component carrier (PSCC) is the carrier

of the PSCell. In Figure 3-2, the carrier of cell 2 is the PSCC.

SCC A secondary component carrier (SCC) is the carrier of an SCell.

In Figure 3-2, the carriers of cells 3 and 4 are SCCs.

Event Event The signal quality of the serving cell becomes higher than a
A1 threshold.

Event The signal quality of the serving cell becomes lower than a
A2 threshold.

Event The signal quality of a neighboring cell of the PCell is offset

A3 better than the signal quality of the PCell.

Event The signal quality of the serving cell becomes lower than
A5 threshold 1, while the signal quality of a neighboring cell
becomes higher than threshold 2.

Event The signal quality of an inter-RAT neighboring cell becomes

B1 higher than a threshold.

3.3 Architecture
NSA networking based on EPC can be deployed in areas where LTE coverage
and NR coverage overlap. The current version supports two network
architectures: Option 3 and Option 3x. The specific network architecture
depends on how the eNodeB, gNodeB, and EPC are interconnected.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 11

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

Figure 3-3 Network architectures defined by 3GPP specifications

The eNodeB is an MeNB, the gNodeB is an SgNB, user-plane data can be

transmitted in either Option 3 or Option 3x, as shown in Figure 3-3.

● In Option 3, data split is performed on the MeNB. The supported bearers

include MCG bearer, MCG_Bearer_EUTRA_PDCP, and MCG split bearer.
– MCG bearer and MCG_Bearer_EUTRA_PDCP: indicating that user-plane
data is carried by the MeNB.
– MCG split bearer: indicating that user-plane data is split at the PDCP
layer of the MeNB, distributed to the RLC layers of the SgNB and MeNB,
as shown in Figure 3-4, and then aggregated at the PDCP layer of the
UE.

Figure 3-4 MCG split bearer

● In Option 3x, data split is performed on the SgNB. The supported bearers
include SCG split bearer and SN-terminated MCG bearer.
– SCG split bearer: indicating that user-plane data is split at the PDCP layer
of the SgNB, distributed to the RLC layers of the MeNB and SgNB, as
shown in Figure 3-5, and then aggregated at the PDCP layer of the UE.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 12

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

Figure 3-5 SCG split bearer

– SN-terminated MCG bearer: indicating that all user-plane data is

distributed at the PDCP layer of the SgNB to the RLC layer of the MeNB,
as shown in Figure 3-6. For details about the SN-terminated MCG bearer,
see EPC-based NSA Performance Enhancement.

Figure 3-6 SN-terminated MCG bearer

3.4 EN-DC Band Combinations

Supported Band Combinations
In NSA networking, the E-UTRA-NR dual connectivity (EN-DC) combinations of
NR frequency bands and the corresponding LTE frequency bands are specified in
3GPP specifications. The DC_13A-n66A combination is used as an example. Table
3-2 lists the LTE and NR frequency bands included in this combination. For details
about EN-DC band combinations defined in 3GPP specifications, see section 5.5B
"Configuration for DC" in 3GPP TS 38.101-3 V16.6.0.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 13

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

Table 3-2 EN-DC band combination example (DC_13A-n66A combination)

EN-DC LTE or Uplink Frequency Downlink Frequency RAT
Band NR Band (MHz) (MHz)
Combinati
on

DC_13A_n B13 777 to 787 746 to 756 LTE

66A FDD

n66 1710 to 1780 2110 to 2200 NR

FDD

Specified Band Configuration

When querying the EN-DC band combination capability of an NSA UE, the
eNodeB will send the requestedFreqBandsNR-MRDC-r15 IE to the NSA UE so that
the NSA UE reports only the EN-DC band combinations consisting of the
frequency bands specified by this IE. This IE contains the bandEUTRA and bandNR
fields, which specify the LTE and NR bands in the EN-DC band combinations,
respectively. As described in Table 3-3, the values of bandEUTRA and bandNR are
determined by the frequencies configured on the eNodeB or independently
configured bands. An independently configured band is specified using the
OperatorBand MO. The OperatorBand.BandId, OperatorBand.BandType,
OperatorBand.CnOperatorList, and OperatorBand.BandAttribute parameters in
this MO specify the ID, type (RAT), operator list, and attribute of a band,
respectively. The OperatorBand.BandAttribute parameter is valid only when the
OperatorBand.BandType parameter is set to LTE.
If no OperatorBand MO is configured, the values of bandEUTRA and bandNR are
determined by the frequencies configured on the eNodeB. When the frequencies
configured on neighboring eNodeBs are different, the bands specified by the
neighboring eNodeBs may be different.
If OperatorBand MOs are configured, the values of bandEUTRA and bandNR are
determined by whether bands of the corresponding RATs are configured in the
OperatorBand MOs and whether the INDEP_UE_BAND_ENQUIRY_SW option of
the GlobalProcSwitch.ProtocolMsgOptExtSwitch parameter is selected.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 14

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

Table 3-3 Sources and descriptions of the bandEUTRA and bandNR values
Field Value When Sourced from When Sourced from
Frequencies Configured Independently
on the eNodeB Configured Bands

Value of bandEUTRA Determined by the LTE Determined by the

bands to which the independently
following frequencies configured bands
belong: identified by the IDs in
● Frequencies identified the OperatorBand MOs
by with Band Type set to
PccFreqCfg.PccDlEarf LTE.
cn corresponding to The bands are further
NrScgFreqConfig.Scg filtered as follows:
DlArfcn ● The bands with Band
● Frequencies identified Attribute set to CA
by are filtered out.
SccFreqCfg.SccDlEarf ● The bands that do not
cn corresponding to belong to the
the previous PCC operator of the UE
downlink EARFCNs (indicated by CN
Operator List) are
filtered out.
If all LTE bands are
filtered out, the value of
this field is empty. In this
case, the UE will not
report any EN-DC band
combination, and the
NSA DC function will not
take effect.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 15

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

Field Value When Sourced from When Sourced from

Frequencies Configured Independently
on the eNodeB Configured Bands

Value of bandNR Determined by the NR Determined by the

bands to which the independently
frequencies identified by configured bands
NrScgFreqConfig.ScgDl identified by the IDs in
Arfcn belong. the OperatorBand MOs
with Band Type set to
NR.
For the preceding bands
that are configured with
an operator list, the
eNodeB will filter out the
bands that do not
belong to the operator
of a UE. If all NR bands
are filtered out, the
value of this field is
empty. In this case, the
UE will not report any
EN-DC band
combination, and the
NSA DC function will not
take effect.

If the OperatorBand MOs have been configured, the final sources of the
bandEUTRA and bandNR values are illustrated in Figure 3-7.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 16

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

Figure 3-7 Final sources of the bandEUTRA and bandNR values

The procedure is described as follows:

1. For bandEUTRA and bandNR, the eNodeB checks whether the bands of the
corresponding RATs are configured in the OperatorBand MOs.
– If so, the procedure goes to 2.
– If not, the values of bandEUTRA or bandNR are determined by the
frequencies configured on the eNodeB. The procedure ends.
2. The eNodeB checks whether the INDEP_UE_BAND_ENQUIRY_SW option is
selected.
– If this option is selected, the values of bandEUTRA or bandNR are
determined by the independently configured bands. The procedure ends.
In this scenario, the bands specified by neighboring eNodeBs can be the
same even if the frequencies configured on the neighboring eNodeBs are
different.
– If this option is deselected, the values of bandEUTRA or bandNR are
determined preferentially by the frequencies configured on the eNodeB
and then by the independently configured bands. The procedure ends.
If the QUERY_SPEC_BAND_UE_CAP_SW option of the
UeCompat.WhitelistCtrlExtSwitch1 parameter is selected, OperatorBand MOs

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 17

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 3 Overview

can be used to specify bands only for whitelisted UEs. If this option is deselected,
OperatorBand MOs can be used to specify bands for all UEs. If both this option
and the CaBandCombQueryOptSwitch option of the
GlobalProcSwitch.ProtocolMsgOptSwitch parameter are selected, the eNodeB
cannot identify whether a UE is whitelisted when the UE performs initial access
and the core network does not deliver E-UTRAN capability information. Therefore,
the eNodeB considers that the UE is not whitelisted, and does not specify bands
for it using the OperatorBand MOs.

NOTE

If the OperatorBand.BandType parameter is set, network-requested CA band combination

capability signaling for CA UEs will be affected. For details, see Carrier Aggregation in eRAN
feature documentation.
If an LTE or NR band in an EN-DC band combination is not configured using the
OperatorBand.BandId parameter, NSA DC cannot take effect for a UE when the UE moves
to an area covered only by this band.
If the INDEP_UE_BAND_ENQUIRY_SW option of the
GlobalProcSwitch.ProtocolMsgOptExtSwitch parameter is deselected, the bandEUTRA
value is preferentially sourced from the frequencies configured on the eNodeB and then
from the independently configured bands. As such, the value of bandEUTRA may include
the bands with OperatorBand.BandAttribute set to CA.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 18

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

4 NSA Networking Based on EPC

NSA networking based on EPC can implement basic functions such as carrier
management, data split, uplink power control, and interference avoidance in
NSA DC.
NSA networking based on EPC is controlled by the NSA_DC_CAPABILITY_SWITCH
option of the NsaDcMgmtConfig.NsaDcAlgoSwitch parameter on the eNodeB
side and by the NRCellAlgoSwitch.NsaDcSwitch parameter on the gNodeB side.
It takes effect when both of the switches are turned on.

4.1 Principles

4.1.1 Carrier Management in NSA DC

Carrier management in NSA DC includes carrier addition, change, removal,
and frequency configuration. It is classified into MCG carrier management
and SCG carrier management. It can be performed based on subscriber profile
ID (SPID) or QoS class identifier (QCI). This document describes the basic
functions of carrier management in NSA DC. For details about NSA PCC anchoring
and blind PSCell addition, see EPC-based NSA Performance Enhancement.

4.1.1.1 MCG Carrier Management

4.1.1.1.1 SCC Management

SCC Frequency Selection

SCC frequency selection for an MCG is the same as that in LTE carrier
management. For details, see Carrier Aggregation in eRAN feature documentation.

SCell Activation
The eNodeB triggers LTE SCell activation based on events or at intervals when an
NSA UE is in a specific state and certain conditions are met.
● If the NSA UE is not in the NSA DC state, all the following conditions must be
met:

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 19

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– Data volume buffered at the RLC layer > max (Uu data rate at the RLC
layer x CaMgtCfg.ActiveBufferDelayThd,
CaMgtCfg.ActiveBufferLenThd)
– First packet delay at the RLC layer > CaMgtCfg.ActiveBufferDelayThd
In this scenario, the interval for triggering periodic LTE SCell activation is
specified by the CaMgtCfg.SccCfgInterval parameter.
● If the NSA UE is in the NSA DC state, all the following conditions must be
met:
– Data volume buffered at the RLC layer > max (Uu data rate at the RLC
layer x NsaDcMgmtConfig.NsaDcLteScellActBfrDelThld,
NsaDcMgmtConfig.NsaDcLteScellActBfrLenThld)
– First packet delay at the RLC layer >
NsaDcMgmtConfig.NsaDcLteScellActBfrDelThld
In this scenario, the interval for triggering periodic LTE SCell activation is
specified by the NsaDcMgmtConfig.NsaDcLteScellConfigIntvl parameter.
The duration of a single round of LTE SCell measurement is specified by the
NsaDcMgmtConfig.NsaDcLteScellMeasDuration parameter.

SCC Removal
It is possible that SCCs cannot be added together with an SCG for an NSA UE with
compatibility issues. For such an NSA UE, the NSA_CA_FORBID_SW option of the
UeCompat.BlacklistControlExtSwitch2 parameter can be used to specify whether
to enable blacklist control for SCC management in NSA networking. If this option
is selected and the NSA UE is in the corresponding blacklist, all configured SCCs
must be removed when an SCG is added for this UE, and no SCCs can be added
after an SCG is added and before the SCG is released.
If this option is deselected or the NSA UE is not in the corresponding blacklist, the
SCC removal policy depends on the setting of the
SCC_RMV_AFT_SCG_ADD_OPT_SW option of the
NsaDcAlgoParam.NsaDcAlgoSwitch parameter when an SCG is added for this
UE.
● Assume that the option is deselected. If the combination of LTE CA bands and
NR bands does not support NSA DC, LTE CA SCCs need to be removed;
otherwise, SCG addition is triggered directly. If SCCs need to be removed, the
base station checks whether intelligent selection of serving cell combinations
has taken effect. If this function has taken effect, all LTE CA SCCs are removed
and an SCG is added; after the addition, SCCs in the selected EN-DC
combination are added (if not added yet). For details about intelligent
selection of serving cell combinations, see Carrier Aggregation in eRAN
feature documentation. If intelligent selection of serving cell combinations has
not taken effect, SCCs not belonging to the selected EN-DC combination are
removed and an SCG is added; after the addition, SCCs in the selected EN-DC
combination are added (if not added yet). Figure 4-1 shows the procedure.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 20

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-1 Cooperation between intelligent selection of serving cell

combinations and SCG addition in NSA networking

● Assume that the option is selected. If the combination of LTE CA bands and
NR bands does not support NSA DC, LTE CA SCCs need to be removed;
otherwise, SCG addition is triggered directly. If SCCs need to be removed, the
base station follows the principle that the LTE CA combination in the currently
supported EN-DC combination is the optimal combination. Based on this
principle, SCCs are removed, and then SCCs in the selected EN-DC
combination are added (if not added yet).

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 21

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

During SCC removal, the base station does not consider whether the LTE CA combination in
the currently supported EN-DC combination is the optimal combination. After an SCG is
added for an NSA UE, the selected LTE CA combination may not be the optimal one,
affecting user experience.

4.1.1.1.2 Uplink CA in EN-DC

Uplink CA in EN-DC means that an NR SCG and uplink LTE CA can be both
configured for an NSA UE. This function is enabled when the
NSA_LTE_UL_2CC_SW option of the NsaDcMgmtConfig.NsaDcAlgoExtSwitch
parameter is selected. This function allows for only uplink FDD+FDD CA. Event-
based or periodic LTE SCC configuration or activation can be performed in
different conditions, depending on the NSA UE's state.

If the NSA UE is not in the EN-DC state, uplink 2CC aggregation is performed as
described in Carrier Aggregation in eRAN feature documentation.

If the NSA UE is in the EN-DC state, the following functions are supported:
● Uplink SCC addition
– Triggered based on events, including SCG addition, change, and removal
– Triggered at intervals and based on data volume

▪ If the NSA UE in the EN-DC state has no data split bearer, all the
following conditions must be met:
○ Data volume buffered at the RLC layer > max (Uu data rate at
the RLC layer x CaMgtCfg.ActiveBufferDelayThd,
CaMgtCfg.ActiveBufferLenThd)
○ First packet delay at the RLC layer >
CaMgtCfg.ActiveBufferDelayThd
The interval is specified by the CaMgtCfg.SccCfgInterval parameter.

▪ If the NSA UE in the EN-DC state has a data split bearer, all the
following conditions must be met:
○ Data volume buffered at the RLC layer > max (Uu data rate at
the RLC layer x
NsaDcMgmtConfig.NsaDcLteScellActBfrDelThld,
NsaDcMgmtConfig.NsaDcLteScellActBfrLenThld)
○ First packet delay at the RLC layer >
NsaDcMgmtConfig.NsaDcLteScellActBfrDelThld
The interval is specified by the
NsaDcMgmtConfig.NsaDcLteScellConfigIntvl parameter. The
duration of a single round of LTE SCell measurement is specified by
the NsaDcMgmtConfig.NsaDcLteScellMeasDuration parameter.
● Uplink SCC removal
– This function is the same as uplink 2CC aggregation in LTE. For details,
see Carrier Aggregation in eRAN feature documentation.
– If the EN-DC band combinations supported by the UE cannot be used for
uplink CA and the configuration of uplink CA has been completed for the
UE, the uplink SCC will be released after the SCG is added again.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 22

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● Uplink SCC activation, which requires that all of the following conditions be
met:
– Data volume buffered at the RLC layer > max (Uu data rate at the RLC
layer x NsaDcMgmtConfig.NsaDcLteScellActBfrDelThld,
NsaDcMgmtConfig.NsaDcLteScellActBfrLenThld)
– First packet delay at the RLC layer >
NsaDcMgmtConfig.NsaDcLteScellActBfrDelThld
● Uplink SCC deactivation, which requires that all of the following conditions be
met:
– Buffered data volume in the BSR reported by the NSA UE ≤
NsaDcMgmtConfig.NsaLteSCellDeactBfrLenThld
– Uplink Uu data rate on the NSA UE at the RLC layer ≤
NsaDcMgmtConfig.NsaLteSCellDeactThptThld
The NSA_LTE_UL_CA_SW option of the UeCompat.BlacklistControlExtSwitch1
parameter can be used to disable this function for defective UEs. The
NSA_LTE_UL_CA_DIFF_DPS_SW option of the
UeCompat.BlacklistControlExtSwitch2 parameter can be used to prohibit UEs
from occupying all power on their LTE side if the UEs have no power reserved on
their NR side.
Uplink CA in EN-DC depends on uplink LTE CA and therefore requires that the
following uplink CA functions be enabled:
● Uplink 2CC aggregation: controlled by the CaUl2CCSwitch option of the
CaMgtCfg.CellCaAlgoSwitch parameter
● Inter-eNodeB CA based on relaxed backhaul: controlled by the
RelaxedBackhaulCaSwitch option of the ENodeBAlgoSwitch.CaAlgoSwitch
parameter
● Inter-eNodeB CA based on eNodeB coordination: controlled by the
FreqCfgCaOverBBUsSwitch option of the
ENodeBAlgoSwitch.OverBBUsSwitch parameter
The following NSA functions take effect preferentially if they are enabled together
with uplink CA in EN-DC:
● TDM power control
● Uplink single-side transmission (trial)
● Interference avoidance in NSA DC

4.1.1.2 SCG Carrier Management

SCG addition is triggered if an NSA UE in the LTE-only state requests NSA DC
services. SCG carrier management mainly includes PSCell configuration. For details
on the SCG addition procedure, see Figure 4-2.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 23

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

● If a UE supports both NSA networking and SA networking, the UE preferentially returns

to an NR cell through an LTE-NR interoperability procedure in SA networking. For details
about LTE-NR interoperability, see Interoperability Between E-UTRAN and NG-RAN in
Connected Mode.
● In the current version, the MeNB supports only RSRP-based B1 measurement for SCG
addition. Therefore, the NRCellMobilityConfig.MeasTrigQuantity parameter must be
set to RSRP in NSA networking. Otherwise, after an SCG is added, it is likely that the UE
immediately reports RSRQ-based event A2 and the SgNB immediately triggers a
coverage-based inter-frequency handover.
● A UE cannot receive and send data at the same time in the EN-DC band combination of
B41 and N41 according to 3GPP TS 38.101-3. Therefore, if the
NrScgFreqConfig.PccDlEarfcn parameter indicates a band in B41, then the
NrScgFreqConfig.ScgDlArfcn parameter can be set to a frequency in N41 only when
the uplink subframes and downlink subframes of B41 and N41 are aligned.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 24

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-2 SCG addition procedure

The procedure is described as follows:

1. Checks whether an NSA UE meets SCG addition conditions.
SCG addition is triggered when the NSA UE in the LTE-only state meets all the
following conditions:

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 25

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– There are QCIs that are supported by the MCG split bearer or SCG split
bearer. For the relationships between QCIs and bearers, see 4.1.2 Data
Split in NSA DC.
– The UE is not running any emergency call.
– If the UE has VoLTE services:

▪ If the NsaDcMgmtConfig.VolteUeScgMgmtStrategy parameter is

set to VOLTE_SCG_COEXISTENCE, the
VOLTE_NSA_DC_IF_NR_MEAS_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is also selected.

▪ If the NsaDcMgmtConfig.VolteUeScgMgmtStrategy parameter is

set to ADAPTIVE, the uplink SINR of the VoLTE UE is greater than or
equal to the value of
NsaDcMgmtConfig.UlQualityThldForScgRelease and the uplink or
downlink packet loss rate with QCI 1 is less than or equal to the
value of NsaDcMgmtConfig.VoltePlrThldForScgRelease.
2. Determines whether to trigger SCG addition based on events or at intervals.
– Event-based triggering
SCG addition is triggered when an NSA UE performs initial access,
incoming handover, or incoming RRC connection reestablishment. The
NSA_DC_VOLUME_BASED_SCG_ADD_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter specifies whether the
MeNB triggers SCG addition based on data volume. The data volume is
evaluated in the same way as that for periodic SCG addition.
NOTE

If the NsaDcMgmtConfig.ScgAddPenaltyPeriodCount parameter is set to a

non-zero value and an incoming RRC connection reestablishment is triggered for
an NSA UE during an SCG addition procedure, this UE can be barred from
entering the SCG addition procedure again within a period. This period equals
NsaDcMgmtConfig.ScgAddPenaltyPeriodCount x
NsaDcMgmtConfig.ScgAdditionInterval.
– Periodic triggering
An SCG may fail to be added initially, or cannot be added due to no
trigger source after SCG release. To trigger SCG addition for an NSA UE in
the LTE-only state, the MeNB can start an SCG addition timer and trigger
the addition at intervals specified by the
NsaDcMgmtConfig.ScgAdditionInterval parameter.
Whether to check data volume for periodic triggering of SCG addition is
specified by the VOLUME_BASED_PERIODIC_TRIG_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter. If this option is
selected, SCG addition is triggered based on data volume. If this option is
deselected, SCG addition is not triggered based on data volume.
Whether data volume meets requirements is determined by the SCG
addition buffer length threshold (specified by
NsaDcMgmtConfig.ScgAdditionBufferLenThld) and the SCG addition
buffer delay threshold (specified by
NsaDcMgmtConfig.ScgAdditionBufferDelayThld).

▪ If the SCG addition buffer length threshold is set to 0, SCG addition is

triggered when the UE is transmitting data.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 26

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

▪ If the SCG addition buffer length threshold is set to a value other

than 0, SCG addition is triggered when the following conditions are
met:
○ Data volume buffered at the RLC layer > max (Air interface data
rate at the RLC layer x SCG addition buffer delay threshold, SCG
addition buffer length threshold)
○ First packet delay at the RLC layer > SCG addition buffer delay
threshold
If the UE inactivity timer (specified by
NRDUCellQciBearer.UeInactivityTimer) on the NR side expires, the SCG
will be released. When there is no data transmission on the LTE and NR
sides, the following two issues may arise:

▪ SCG addition is triggered periodically with data volume not

considered.
The MeNB may repeatedly add an SCG and release it. To prevent this
issue, it is recommended that the UE inactivity timer on the NR side
be set to 0.

▪ SCG addition is triggered periodically with data volume considered.

The MeNB sends PDCP status report packets to the UE. When the
data volume of such packets buffered at the RLC layer of the MeNB
exceeds the SCG addition buffer length threshold, the MeNB triggers
SCG addition based on data volume. As a result, the MeNB may
repeatedly add an SCG and release it. To prevent this issue, it is
recommended that at least one of the following operations be
performed:
○ Set the SCG addition interval to a value greater than the value
of the UE inactivity timer on the NR side.
○ Set the SCG addition buffer length threshold to a value greater
than the data volume of PDCP status report packets buffered at
the RLC layer of the MeNB.
○ Select the SCG_ADD_PCC_ANCHOR_VOL_OPT_SW option of
the NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter so that
the MeNB deducts the data volume of PDCP status report
packets during data volume evaluation.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 27

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

● The INSTANT_JUDGEMENT_SW option of the

NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter specifies whether
instantaneous millisecond-level values or filtered second-level values are used
for estimating the data volume buffered at the RLC layer during data-volume-
based SCG addition. If both this option and the
VOLUME_BASED_SCG_ADD_OPT_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter are selected, the eNodeB
automatically determines whether to use the SCG addition buffer delay
threshold when checking whether an NSA UE meets the conditions for data-
volume-based SCG addition.
● The A2_HO_SCG_ADD_PCC_ANCHOR_SW option of the
NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter specifies whether to
allow SCG addition triggering after receiving A2 measurement reports related
to coverage-based handovers from NSA UEs. If this option is selected, SCG
addition triggering is allowed. If this option is deselected, SCG addition
triggering is not allowed.
3. Performs the SCG addition procedure.
Measurement-based PSCell configuration (described in 4.1.1.2.1
Measurement-based PSCell Configuration) or blind PSCell addition
(described in EPC-based NSA Performance Enhancement) can be performed,
depending on the setting of the NSA_BLIND_SCG_ADDITION_SWITCH option
of the NsaDcMgmtConfig.NsaDcAlgoSwitch parameter.
– If this option is deselected, measurement-based PSCell configuration is
performed and an SCG is added.
– If this option is selected and the NrNRelationship.BlindConfigIndicator
parameter is set to TRUE, B1 measurement configurations are not
delivered; instead, an SCG addition request is directly sent for blind PSCell
addition and SCG addition in the following scenarios:

▪ A UE initially accesses the network.

▪ In the preparation for a handover from the source MeNB to the

target MeNB, the target MeNB meets the conditions for blind SCG
addition.

▪ A UE has just been handed over from an LTE-only cell to an NSA

anchor cell.
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 not
recommended that this parameter be set to TRUE to prevent NR access
failure due to no NR coverage.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 28

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

● When the MeNB triggers SCG addition, it performs flow control based on its CPU usage.
That is, the MeNB limits the probability of SCG addition to prevent the CPU from being
overloaded. The NSA flow control policy is specified by the
eNodeBFlowCtrlPara.NsaFlowCtrlStrategy parameter. When the CPU usage reaches or
exceeds 80%, flow control is performed.
● When the CPU usage reaches 80%, the MeNB starts to limit the probability of SCG
addition. When the CPU usage is 80%, 81%, 82%, 83%, or 84%, the probability of
SCG addition is 80%, 60%, 40%, 20%, or 10%, respectively.
● When the CPU usage reaches or exceeds 85%, the MeNB does not add any SCG,
except for VIP users.
● When the CPU usage falls below 80% but reaches or exceeds 70%, the probability
of SCG addition is 95%.
● When the CPU usage falls below 70%, flow control is not performed.
● The NSA_NR_SINGLE_BC_PREFER_SW option of the
EnodebAlgoExtSwitch.MultiNetworkingOptionOptSw parameter specifies whether to
enable the preferential selection of a band combination with only one NR carrier for
NSA UEs function. If this option is selected, a band combination that involves only one
NR carrier is preferentially selected for SCG addition. This function can take effect only
for whitelisted UEs if the NSA_NR_SINGLE_BC_PREFER_SW option of the
UeCompat.WhitelistCtrlExtSwitch1 parameter is selected.

When delivering NR frequency measurement configurations or adding NR cells in

a blind manner for a UE, the MeNB preferentially considers NR frequencies or NR
cells that belong to the same PLMN as the UE. If LTE and NR belong to different
PLMNs, the INTER_PLMN_ADD_SCG_SW or EQUIVALENT_PLMN_ADD_SCG_SW
option of the EnodebAlgoExtSwitch.NsaDcAlgoSwitch parameter can be
selected. Under this setting, when delivering B1 measurement configurations or
adding NR cells in a blind manner, the MeNB can select NR frequencies or NR cells
in a PLMN that is in the equivalent PLMN list or inter-PLMN list (configured using
the InterPlmnHoList MO). To allow the SgNB to perform admission control when
LTE and NR belong to different PLMNs, the SCG_ADD_PLMN_SELECT_POLICY_SW
option of the gNodeBParam.NsaDcOptSwitch parameter also needs to be
selected. Under this setting, the SgNB performs admission decision based on the
Selected PLMN IE in the SgNB Addition Request message sent by the MeNB to the
SgNB.

4.1.1.2.1 Measurement-based PSCell Configuration

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

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 29

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-3 Measurement-based PSCell configuration procedure

Measurement Configuration Delivery

After filtering frequencies based on UE capabilities, the MeNB can configure
multiple frequencies and the corresponding priorities for an SCG using the
NrScgFreqConfig.ScgDlArfcn and NrScgFreqConfig.ScgDlArfcnPriority
parameters. The validation rules are as follows:
● If different priorities are set for the frequencies, 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.
● If the same priority or no priority is set for the frequencies, the frequency
sequence in measurement configurations is random.
● If priorities are set for some frequencies but not for others, the frequencies
with no priorities configured have the lowest priority by default.
NOTE

● Assume that the frequency indicated by the NrScgFreqConfig.ScgDlArfcn parameter

belongs to multiple NR frequency bands and no frequency band is configured in the
NrMfbiFreq MO for this frequency. Then, the frequency band specified in NR
measurement configurations is the NR frequency band in the first EN-DC-capable band
combination indicated in the supportedBandCombinationList IE reported by the UE.
● When selecting NR frequencies for measurement configuration delivery, the eNodeB
filters out the NR frequencies for which the NR_DL_SCC_FREQ_ONLY_IND option of the
NrNFreq.AggregationAttribute parameter is selected.
● In NSA mmWave networking, if there are multiple co-sector co-coverage NR FR2 SCG
downlink frequencies (specified by NrScgFreqConfig.ScgDlArfcn), the
NR_FR2_MEAS_POLLING_FLAG option of the NrScgFreqConfig.AggregationAttribute
parameter on the eNodeB can be selected for these frequencies. Under this setting, the
eNodeB can randomly select an SCG downlink frequency for measurement from these
frequencies for the same downlink EARFCN of the PCC (specified by
NrScgFreqConfig.PccDlEarfcn).

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 30

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

In NSA and SA hybrid 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 or
NrExternalCellPlmn.NrNetworkingOption parameter. In this scenario, it is
recommended that the UPT_NR_EXT_CELL_NW_OPT_CFG_SW option of the
GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter be selected so that the
value of NrExternalCell.NrNetworkingOption can be automatically updated
based on received X2 messages, without the need for manual configuration.
On the LTE side, the NrScgFreqConfig.ForbiddenSpidGrpId parameter can be
used to specify an SPID group for which a specified SCG frequency cannot be
added as the frequency of an NR SCC. The NrScgFreqConfig.ForbiddenSpidGrpId
parameter setting takes effect only when NR SCCs are added for UEs. If NR SCCs
have been added, the setting does not take effect. As the same NR frequency can
be configured in the NrScgFreqConfig MOs of different PCCs, the same
NrScgFreqConfig.ForbiddenSpidGrpId parameter setting is recommended for this
NR frequency.
If the NR_B1_NO_GAP_SW option of the
EnodeBAlgoExtSwitch.MultiNetworkingOptionOptSw parameter is selected and
a UE reports that it supports non-gap-assisted measurement of an NR frequency,
the eNodeB does not include gap configurations when it delivers B1 measurement
configurations for this frequency to the UE.

NOTE

An NR frequency can be included in measurement configurations delivered to UEs only if

the FREQ_MEAS_FLAG option of the NrNFreq.AggregationAttribute parameter is
selected.

Measurement Reporting and Processing

The NsaDcQciParamGroup.NsaDcB1RsrpThldOffset and
SpidCfg.NsaDcSpidB1RsrpThldOffset parameters can be set on the MeNB to
configure the QCI- and SPID-specific RSRP threshold offsets, respectively, for NSA
DC event B1. Then, these offsets are included in the measurement configurations
and delivered to a UE through the SgNB. The UE performs measurement
according to the SgNB measurement configurations. If the measured RSRP value is
greater than the RSRP threshold for event B1 (which is equal to
NrScgFreqConfig.NsaDcB1ThldRsrp plus the preceding two offsets) throughout a
period that exceeds the NrScgFreqConfig.NrB1TimeToTrigger parameter value,
the UE reports the B1 measurement result. If an NR cell is shared by multiple
operators, the offset specified by CellOp.NsaDcB1RsrpThldOffset can be added
to the preceding RSRP threshold for event B1 so that different RSRP thresholds for
event B1 can be set for different operators.
A UE supporting both NSA and SA is likely to report NSA DC B1 measurement
results first as the NrScgFreqConfig.NrB1TimeToTrigger parameter of NSA DC B1
has a smaller default value than the
InterRatHoNrParamGrp.NrB1B2TimeToTrigger parameter of NR B1. To prioritize
NR SA network measurement, select the NrB1TimeToTrigAdjSw option of the
CellHoParaCfg.CellHoAlgoSwitch parameter. Under this setting, when the
delivery of both NR B1 and NSA DC B1 measurement configurations is supported
and the time to trigger for NR B1 is greater than that for NSA DC B1, the time to
trigger for NSA DC B1 is adjusted to be consistent with that for NR B1. If the time

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 31

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

to trigger for NR B1 is shorter than that for NSA DC B1, adjustment to the same
value is not required.

If multiple QCIs exist, the MeNB selects the B1 threshold configured for the QCI
with the highest priority (specified by CellQciPara.QciPriorityForHo)
corresponding to the data split bearer when delivering B1 measurement
configurations for SCG addition to the UE.

After the MeNB delivers neighboring NR frequency measurement configurations, it

starts a waiting timer (specified by NrScgFreqConfig.NrB1ReportWaitingTimer)
for measurement reporting. If the NsaDcMgmtConfig.NsaDcScgAdditionPolicy
parameter is set to HIGHEST_PRIORITY_FREQ, the base station waits for the
measurement report of only the highest-priority NR frequency. If this parameter is
set to ALL_FREQ, the base station waits for the measurement results of all
delivered NR frequencies.

● If the MeNB receives the measurement results of all the neighboring NR

frequencies before the timer expires or receives the measurement results of
only some neighboring NR frequencies before the timer expires, it processes
the received results as follows:
a. It filters out some neighboring NR cells as follows:

▪ First, it filters out neighboring NR cells in SA networking mode based

on the setting of NrExternalCell.NrNetworkingOption or
NrExternalCellPlmn.NrNetworkingOption.

▪ Then, it filters out neighboring NR cells whose frequency bands and

additional frequency bands are not supported by the UE, based on
the UE MR-DC capability and external NR cell configurations.

▪ After that, it filters out neighboring NR cells for which the

OVER_DISTANCE_FLAG option of the
NrNRelationship.AggregationAttribute parameter is selected.

▪ It filters out NR cells that do not support the uplink mode when the
NR_SCG_UL_NO_CHECK_SW option of the
NsaDcAlgoParam.NsaDcAlgoExtSwitch parameter is deselected.

▪ In Option 3x, it filters out neighboring NR cells under any SgNB

whose S1-U interface is unavailable.
When both the S1U_STATUS_BASED_SCG_ADD_SW option of the
EnodebAlgoExtSwitch.NsaDcAlgoSwitch parameter of the MeNB
and the S1U_STATUS_SEND_SW option of the
gNodeBParam.NsaDcOptSwitch parameter of an SgNB are selected,
the SgNB periodically updates S1-U status information and sends it
to the MeNB. After receiving the SI-U status information, the MeNB
filters out the neighboring NR cells under the SgNB if the S1-U
interface of the SgNB is unavailable.
b. Among the filtered neighboring NR cells, the MeNB identifies the cell
with the strongest signal quality and highest frequency priority. It selects
the SgNB that serves this cell, and fills the measurement results for the
frequencies of the filtered neighboring NR cells served by this SgNB in the
candidateCellInfoListMN field of the MeNB to SgNB Container IE in the
SgNB Addition Request message for reporting.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 32

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● If the MeNB does not receive any neighboring NR frequency measurement

report until the timer expires, the MeNB does not initiate an SgNB addition
request.

PSCell Addition
1. The MeNB sends an SgNB Addition Request message to the target SgNB.
For the first UE that initiates NSA DC, the NR neighbor relationship needs to
be added or the EN-DC X2 interface needs to be automatically set up, which
requires a longer time than manual configuration. For this UE, PSCell addition
can be implemented only after multiple B1 measurements are performed.
– If the NR neighbor relationship is not added or the EN-DC X2 interface is
not set up, two B1 measurements need to be performed. The first
measurement is used to add the NR neighbor relationship or set up the
X2 interface, and the second is used to add the PSCell.
– If neither the NR neighbor relationship is added nor the EN-DC X2
interface is set up, three B1 measurements need to be performed. The
first measurement is used to add the NR neighbor relationship, the
second is used to set up the X2 interface, and the third is used to add the
PSCell.
In other scenarios where the NR neighbor relationship has been added and
the EN-DC X2 interface has been automatically set up, only one B1
measurement needs to be triggered for an NSA UE to add the PSCell. For
details about automatic neighboring cell addition, see ANR Management in
eRAN feature documentation. For details about EN-DC X2 self-setup, see X2
and S1 Self-Management in NSA Networking.
2. The gNodeB selects the NR cell with the highest signal quality from the
candidateCellInfoListMN IE in the SgNB Addition Request message as the
PSCell. Then, the gNodeB sends an SgNB Addition Ack message to the MeNB,
indicating that the SgNB is successfully added.
If the MeasResult2NR IE in the SgNB Addition Request message does not
contain a cell that meets the conditions for PSCell addition, the gNodeB sends
an SgNB Addition Reject message to notify the MeNB that the SgNB addition
fails.

4.1.1.2.2 PSCell Management 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.

● If the NsaDcMgmtConfig.VolteUeScgMgmtStrategy 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 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.
● If the NsaDcMgmtConfig.VolteUeScgMgmtStrategy parameter is set to
ADAPTIVE and a VoLTE service is initiated, then:

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 33

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– Assume that the SINR of the VoLTE UE is less than the value of
NsaDcMgmtConfig.UlQualityThldForScgRelease or the uplink or
downlink packet loss rate of QCI 1 is greater than the value of
NsaDcMgmtConfig.VoltePlrThldForScgRelease. Then, if an SgNB exists,
the eNodeB immediately releases it; if no SgNB exists, no SgNB addition
is triggered 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.
– Assume that the SINR of the VoLTE UE is greater than or equal to the
value of NsaDcMgmtConfig.UlQualityThldForScgRelease and the
uplink or downlink packet loss rate of QCI 1 is less than or equal to the
value of NsaDcMgmtConfig.VoltePlrThldForScgRelease. Then, if an
SgNB exists, the eNodeB does not release it; if no SgNB exists, an SgNB
addition can be triggered. The VOLTE_NSA_DC_IF_NR_MEAS_SW option
of the NsaDcMgmtConfig.NsaDcAlgoSwitch parameter can be used to
control whether to deliver NR B1 measurement configurations to the UE
when SgNB addition is triggered. If this option is deselected, no NR B1
measurement configurations are delivered to the UE and no SgNB is
added, preventing the impact on VoLTE services. If this option is selected,
NR B1 measurement configurations are delivered for SgNB addition.
NOTE

After the UE is handed over to a cell, the base station determines whether to add
an SgNB or delete the SgNB if it has been added, based on the SINR
measurement result or the uplink or downlink packet loss rate of QCI 1 in this
cell.
● If the NsaDcMgmtConfig.VolteUeScgMgmtStrategy parameter is set to
VOLTE_SCG_COEXISTENCE, the eNodeB does not process VoLTE services as it
does in the preceding two modes.
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 can be used
to control whether to deliver NR B1 measurement configurations to the UE. If
this option is deselected, no NR B1 measurement configurations are delivered
to the UE, and an SgNB is directly added in the case that blind SCG addition is
in effect, preventing the impact on VoLTE services. If this option is selected,
NR B1 measurement configurations are delivered for SgNB addition.

4.1.1.2.3 PSCell SMTC on the LTE Side

SMTC stands for SSB-based measurement timing configuration. The NrNFreq MO
on the eNodeB side is used to configure SSB information for an NR frequency. The
information is contained in B1 measurement configurations to instruct UEs to
correctly scan SSBs. It is also used to calculate B1 measurement gap positions. SSB
information includes SMTC Period and SSB Offset.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 34

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

If only two or fewer SSB positions are contained in one gap period, SSB positions may
conflict with the positions of other resources such as PUCCH, SRS, and DRX resources, and
even may be unavailable in the gap period. As a result, it is possible that a UE fails to start
gap-assisted measurements on NR frequencies and the MeNB sends an SgNB Modification
Refuse message to the SgNB. To address this issue, the GAP_OFS_ASSIGNMENT_OPT_SW
option of the NsaDcAlgoParam.NsaDcAlgoSwitch parameter can be selected to reduce the
conflicts between SSB positions and other resources' positions.

SMTC Period
The NrNFreq.SsbPeriod parameter must be set to the same value as the
NRDUCell.SsbPeriod parameter. If multiple neighboring NR cells work on the
same NR frequency and have different SSB periods, it is recommended that the
LTE side use the maximum SSB period as the SMTC period for NR frequency
measurement.

If the NrNFreq.SsbPeriod parameter is set to a value greater than 20 ms, some

NSA UEs may have compatibility issues and fail to find NR networks. In this case,
if the SMTC_CONFIG_SW option of the
EnodebAlgoExtSwitch.NsaProtocolCompatSw parameter is selected, the eNodeB
sends an RRC Connection Reconfiguration message to the UEs to assist them in
searching for NR networks.

SSB Offset
An SSB offset is specified by the LTE parameter NrNFreq.SsbOffset. This
parameter can be set in two scenarios: LTE time synchronization and LTE
frequency synchronization. The LST CLKSYNCMODE command can be executed to
query the clock synchronization mode of a base station.

● LTE time synchronization

On the NG-RAN side, the frame offset is specified by the
gNodeBParam.FrameOffset or gNBFreqBandConfig.FrameOffset parameter.
The value ranges of the two parameters are the same. The former applies to a
gNodeB, and the latter applies to a frequency band. If both parameters are
configured, the latter takes effect. The following uses the
gNBFreqBandConfig.FrameOffset parameter as an example.
a. The time difference between the start time of the subframe for the NR
SSB and the global navigation satellite system (GNSS) standard time,
also known as the offset of SSB to the clock source, is calculated based
on the NG-RAN frame offset.

▪ If the value of the gNBFreqBandConfig.FrameOffset parameter is

less than or equal to 261120, the offset of SSB to the clock source is
calculated as follows: (gNBFreqBandConfig.FrameOffset/30720)
MOD NrNFreq.SsbPeriod.

▪ If the value of the gNBFreqBandConfig.FrameOffset parameter is

greater than or equal to 275943, the offset of SSB to the clock source
is calculated as follows: (gNBFreqBandConfig.FrameOffset/30720 –
10 + NrNFreq.SsbPeriod) MOD NrNFreq.SsbPeriod.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 35

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

If the NR cells operate on different frequencies, the

gNBFreqBandConfig.FrameOffset parameter must be set to an identical
value across the frequencies.
b. The SSB offset is corrected based on the eNodeB frame offset.
The offset of SSB to the clock source calculated in the previous step is
used as the SSB offset before correction. Perform the following steps to
correct the SSB offset:
i. The NG-RAN frame offset remainder and E-UTRAN frame offset
remainder are calculated as follows:
○ NG-RAN frame offset remainder =
(gNBFreqBandConfig.FrameOffset MOD 30720)/30720
○ E-UTRAN frame offset remainder =
(CellFrameOffset.FrameOffset MOD 30720)/30720
ii. If the E-UTRAN frame offset remainder is greater than the NG-RAN
frame offset remainder and is less than 0.5 ms, the corrected SSB
offset is calculated as follows: (SSB offset before correction – 0.5 +
NrNFreq.SsbPeriod) MOD NrNFreq.SsbPeriod.
iii. If the preceding condition is not met, the corrected SSB offset is
equal to the SSB offset before correction.
c. The corrected SSB offset is rounded down to its nearest integer, and the
integer is used as the value of the NrNFreq.SsbOffset parameter.
● LTE frequency synchronization
No configuration is required.

4.1.1.2.4 PSCell Addition Based on Virtual Grid Models

For an NSA UE capable of EN-DC but with no SCG added, the eNodeB delivers A3
measurement configurations about the serving frequency with a measurement
period of 2048 ms to the UE. After receiving measurement reports, the eNodeB
obtains the coverage information of candidate SCG frequencies based on LNR
virtual grid models. The time to trigger for event A3 is specified by the
LnrCarrierSelection.IntraFreqMeasA3TimeToTrig parameter. PSCell addition
based on virtual grid models is controlled by the
NSA_CARRIER_SEL_WITH_VG_SW option of the
LnrCarrierSelection.LnrCarrierSelectionSw parameter.

The accuracy requirement on virtual grid models can be configured using the
LnrCarrierSelection.VgMdlPredNrScgMeasRsrpThld parameter. If LNR virtual
grid models for predicting the RSRP of a neighboring NR frequency are available
and the accuracy of the models meets requirements, the eNodeB performs the
following operations:

● Blind PSCell configuration: If the

LnrCarrierSelection.VgMdlPredNrScgMeasRsrpThld parameter is set to a
value other than ACCURACY100_ENH, virtual grid models are used to predict
the RSRP of a neighboring NR frequency so that measurements are not
required. The eNodeB instructs the UE to add an SCG when the virtual-grid-
model-based prediction result about the neighboring NR frequency meets the
entering condition of event B1. The threshold of event B1 for SCG addition is
specified by the NrScgFreqConfig.NsaDcB1ThldRsrp parameter. When the

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 36

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

prediction result meets the leaving condition of event B1, the eNodeB does
not deliver measurement configurations for the neighboring NR frequency.
The VG_SCG_ADD_MEAS_AND_PUNISH_SW option of the
LnrCarrierSelection.LnrCarrierSelectionSw parameter specifies whether to
enable measurement and penalty for SCG addition based on virtual grids. If
this option is selected, after the eNodeB instructs a UE to add an SCG, it
performs the following operations upon reception of a UE-reported
SCGFailureInformationNR message based on which the eNodeB determines
that the SCG addition using the virtual-grid-model-based prediction result
fails:
– The eNodeB immediately triggers an SCG addition procedure based on
event B1 measurement.
– The eNodeB imposes a penalty on the UE. With this penalty, when the
virtual-grid-model-based prediction result meets the entering condition
of event B1 in subsequent procedure of PSCell addition based on virtual
grid models, SCG addition based on event B1 measurement is triggered
for this UE.
If this option is deselected, the eNodeB does not trigger an SCG addition
procedure based on B1 measurement or impose a penalty on the UE.
● Measurement-based PSCell configuration: Assume that the
LnrCarrierSelection.VgMdlPredNrScgMeasRsrpThld parameter is set to
ACCURACY100_ENH. When the virtual-grid-model-based prediction result
about the neighboring NR frequency meets the leaving condition of event B1,
the eNodeB does not deliver B1 measurement configurations for the
neighboring NR frequency. When the prediction result meets the entering
condition of event B1, the eNodeB delivers the B1 measurement
configurations. After the UE reports B1 measurement results, the eNodeB
instructs the UE to add an SCG. For details about MeNB-initiated SgNB
addition, see NSA Mobility Management.
PSCell addition based on virtual grid models is not recommended in certain
scenarios.
● In high-speed mobility scenarios such as high-speed railway dedicated
networks, it is recommended that this function be disabled. This is to prevent
network performance deterioration because of inaccurate NR coverage
evaluation due to fast UE movement.
● During key event assurance, it is recommended that this function be disabled.
This is to prevent network performance deterioration as the function increases
the CPU usage and the number of SRBs.
● During long-term network reconstruction, it is recommended that this
function be disabled or the accuracy required for SCG addition based on
virtual grid models be set to 100% (that is, the
LnrCarrierSelection.VgMdlPredNrScgMeasRsrpThld parameter be set to
ACCURACY100_OFFSET0). This is to prevent network performance
deterioration caused by low accuracy.

4.1.1.2.5 SPID-based SCG Frequency Priority Configuration

The eNodeB can configure different SCG frequency priorities for different types of
UEs. As such, different types of UEs preferentially select different SCG carriers,
improving user experience.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 37

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

On the LTE side, SPIDCFG.NrScgFreqPriorityGroupId and

NrScgFreqPriGrp.NrScgFreqPriorityGroupId are associated to configure SCG
frequency priorities for UEs with different SPIDs.
● If SPIDCFG.NrScgFreqPriorityGroupId is set to a value in the range of 0 to
255 for a specified SPID, the priorities of SCG frequencies corresponding to
NrScgFreqPriGrp.PccDlEarfcn and NrScgFreqPriGrp.NrScgDlArfcn are
determined by NrScgFreqPriGrp.NrScgDlArfcnPriority. If a UE is not
assigned an SPID on the core network or its SPID is not configured on the
eNodeB, the priorities of SCG frequencies in the UE's PCC and SCG frequency
combination are determined by NrScgFreqConfig.ScgDlArfcnPriority.
● If SPIDCFG.NrScgFreqPriorityGroupId is set to 65535, the SPID-based SCG
frequency priority configuration function does not take effect and the
priorities of all SCG frequencies are determined by
NrScgFreqConfig.ScgDlArfcnPriority.
If both SPID-based SCG frequency priority configuration and user-experience-
based NSA carrier combination selection are enabled, the latter does not take
effect for UEs with a specified SPID. In addition, no handover for user-experience-
based NSA carrier combination selection will be initiated towards a base station
with the SPID-based SCG frequency priority configuration function enabled. If
user-experience-based NSA carrier combination selection is required, SPID-based
SCG frequency priority configuration needs to be disabled.

4.1.1.2.6 Operator-specific SCG Frequency Priority Configuration

The eNodeB supports operator-specific SCG frequency priority configuration so
that UEs of different operators can preferentially select different SCG carriers,
improving user experience.
On the LTE side, CnOperator.NrScgFreqPriorityGroupId and
NrScgFreqPriGrp.NrScgFreqPriorityGroupId are associated to configure SCG
frequency priorities for different operators.
● If CnOperator.NrScgFreqPriorityGroupId is set to a value in the range of 0
to 255 for an operator, the priority of the SCG frequency indicated by
NrScgFreqPriGrp.PccDlEarfcn and NrScgFreqPriGrp.NrScgDlArfcn is
determined by NrScgFreqPriGrp.NrScgDlArfcnPriority.
● If CnOperator.NrScgFreqPriorityGroupId is set to 65535, the operator-
specific SCG frequency priority configuration function does not take effect and
the priorities of all SCG frequencies are determined by
NrScgFreqConfig.ScgDlArfcnPriority.

4.1.1.2.7 Differentiated SCG Addition and Deletion Threshold Configuration for NR

CA-capable UEs
For NR FDD+TDD CA-capable UEs, the eNodeB supports differentiated NR FDD
SCG addition threshold configuration, and the gNodeB supports differentiated NR
FDD SCG deletion threshold configuration, improving downlink user-perceived rate
of these UEs.

Differentiated SCG Addition Threshold Configuration for NR CA-capable UEs

Differentiated SCG addition threshold configuration for NR CA-capable UEs takes
effect when the SCG_ADD_B1_THLD_DIFF_SW option of the

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 38

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NsaDcAlgoParam.NsaDcAlgoExtSwitch parameter is selected on the eNodeB

side. With this function, the MeNB uses the sum of the original effective RSRP
threshold for event B1 and the offset specified by the
NrScgFreqConfig.CaUeScgAddRsrpThldOffset parameter as the threshold in
event B1 measurement configurations delivered to NSA UEs that support NR FDD
+TDD CA during measurement-based PSCell configuration. This achieves
differentiated SCG addition threshold configuration in NR FDD.
For details about measurement-based PSCell configuration, see 4.1.1.2.1
Measurement-based PSCell Configuration.

Differentiated SCG Deletion Threshold Configuration for NR CA-capable UEs

Differentiated SCG deletion threshold configuration for NR CA-capable UEs takes
effect when the NRCellNsaDcConfig.CaCapUePscellA2RsrpThldOfs parameter is
set to a non-zero value on the gNodeB side. With this function, the SgNB uses the
sum of the original effective RSRP threshold for event A2 and the offset specified
by the NRCellNsaDcConfig.CaCapUePscellA2RsrpThldOfs parameter as the
threshold in event A2 measurement configurations delivered to NSA UEs that
support NR FDD+TDD CA during RSRP-based SgNB release. This achieves
differentiated SCG deletion threshold configuration in NR FDD.
For details about SgNB-initiated RSRP-based SgNB release, see NSA Mobility
Management.

4.1.1.3 SPID/QCI-specific Carrier Management

4.1.1.3.1 SPID-specific NSA PCC Anchoring and PSCell Management Policies

4.1.1.3.1.1 Multi-Carrier Configuration Group

The eNodeB MO CellMultiCarrCfgGrp can be used to configure a multi-carrier
configuration group and set the measurement configurations related to a
downlink frequency in the group. Table 4-1 lists the parameters that jointly define
a downlink frequency in the multi-carrier configuration group.

Table 4-1 Parameters that define a frequency in the multi-carrier configuration

group
Parameter ID Description

CellMultiCarrCfgGrp.DlArfcn Downlink frequency number

CellMultiCarrCfgGrp.RatType RAT type of the downlink frequency

CellMultiCarrCfgGrp.CnOperatorId ID of an operator for the downlink

frequency

CellMultiCarrCfgGrp.LocalCellId ID of a local cell for the downlink

frequency

A multi-carrier configuration group is identified by the

CellMultiCarrCfgGrp.MultiCarrCfgGroupId parameter. After an

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 39

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

SpidCfg.MultiCarrCfgGroupId parameter is set to the ID of a specific multi-carrier

configuration group, the involved SPID is associated with this group to implement
different SPID-specific NSA PCC anchoring and PSCell management policies.

SPID-specific NSA PCC Anchoring Policy

For a downlink frequency in the multi-carrier configuration group associated with
a specific SPID, when the RAT type of this frequency is EUTRAN and this
frequency is already configured using the PccFreqCfg.PccDlEarfcn parameter, then
the NSA PCC anchoring policy for the SPID-specific UEs on this frequency can be
configured using the following parameters and options:
● CellMultiCarrCfgGrp.NsaPccAnchoringPriority: It specifies the NSA PCC
anchoring priority of the frequency. If it is set to a value ranging from 0 to 31,
the PccFreqCfg.NsaPccAnchoringPriority parameter takes this value. If it is
set to 255, the actual value of PccFreqCfg.NsaPccAnchoringPriority is not
affected.
● FORBID_MEAS_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter: It specifies whether
PCC anchoring measurement on the frequency is prohibited. If this option is
selected, PCC anchoring measurement on the frequency is prohibited. If this
option is deselected, PCC anchoring measurement on the frequency is
allowed.
● HIGH_LOAD_CELL_NSA_PCC_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter: It specifies whether
the eNodeB performs special processing on the frequency during PCC
anchoring for RRC_CONNECTED UEs or RRC_IDLE UEs in NSA networking.
– During PCC anchoring for RRC_CONNECTED UEs in NSA networking, if
this option is selected, the eNodeB selects this frequency as a candidate
NSA PCC anchor for the SPID-specific UEs only when the average
downlink PRB usage of the cell where the UEs camp exceeds
NsaDcMgmtConfig.DlPrbThldForNsaPccAnchor and the UEs are
running large-packet services. If this option is deselected, the eNodeB
always selects this frequency as a candidate NSA PCC anchor for the
SPID-specific UEs.
– During NSA PCC anchoring for RRC_IDLE UEs in NSA networking, if this
option is selected, the eNodeB does not adjust the priority of the
frequency as a candidate NSA PCC anchor for the SPID-specific UEs. If
this option is deselected, the eNodeB adjusts the priority of the frequency
as a candidate NSA PCC anchor for the SPID-specific UEs.
NOTE

If both SPID-specific and QCI-specific NSA PCC anchoring policies are configured for a
downlink frequency, the SPID-specific NSA PCC anchoring policy preferentially takes effect.

SPID-specific PSCell Management Policy

For a downlink frequency in the multi-carrier configuration group associated with
a specific SPID, when the RAT type of this frequency is NR and this frequency is
already configured using the PccFreqCfg.PccDlEarfcn or
NrScgFreqConfig.ScgDlArfcn parameter, then the PSCell management policy for
the SPID-specific UEs camping on the current serving cell on this frequency can be
configured using the following parameters and options:

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 40

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● FORBID_MEAS_FLAG option of the

CellMultiCarrCfgGrp.AggregationAttribute parameter: It specifies whether
the frequency can be treated as an SCG frequency for measurement. If this
option is selected, the frequency cannot be treated as an SCG frequency for
measurement. If this option is deselected, the frequency can be treated as an
SCG frequency for measurement.
● FORBID_BLIND_CFG_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter: It specifies whether
the frequency can be blindly configured as an SCG frequency. If this option is
selected, the frequency cannot be blindly configured as an SCG frequency. If
this option is deselected, the frequency can be blindly configured as an SCG
frequency.
During measurement-based PSCell configuration, the eNodeB can configure
multiple frequencies and corresponding priorities for the SCG after filtering
frequencies based on UE capabilities. If the downlink frequency in the multi-carrier
configuration group for SPID-specific UEs is already configured using the
NrScgFreqConfig.ScgDlArfcn parameter, the priority of this frequency is equal to
NrScgFreqConfig.ScgDlArfcnPriority plus
CellMultiCarrCfgGrp.NrScgPriorityOffset.
After the SCG frequencies are configured, the eNodeB delivers measurement
configurations of these frequencies to the NSA UE. For each of these frequencies,
if the RSRP value measured by the NSA UE is greater than the B1 RSRP threshold,
the UE will report the B1 measurement result. The B1 RSRP threshold is calculated
as follows:
B1 RSRP threshold = A + B + C + D + E
● A: NrScgFreqConfig.NsaDcB1ThldRsrp
● B: CellOp.NsaDcB1RsrpThldOffset
● C: NsaDcQciParamGroup.NsaDcB1RsrpThldOffset
● D: SpidCfg.NsaDcSpidB1RsrpThldOffset
● E: NrNFreq.FreqSpecificOffset
If the downlink frequency in the multi-carrier configuration group for SPID-specific
UEs is already configured using the NrScgFreqConfig.ScgDlArfcn parameter, the
RSRP threshold for event B1 is equal to the preceding sum plus
CellMultiCarrCfgGrp.NsaDcB1RsrpThldOffset.

NOTE

If both SPID-specific and QCI-specific PSCell management policies are configured for a
downlink frequency, the SPID-specific PSCell management policy preferentially takes effect.

Configuration Requirements
For different cells (specified by CellMultiCarrCfgGrp.LocalCellId) in a multi-
carrier configuration group (specified by
CellMultiCarrCfgGrp.MultiCarrCfgGroupId), if their downlink frequency numbers
(specified by CellMultiCarrCfgGrp.DlArfcn), operator IDs (specified by
CellMultiCarrCfgGrp.CnOperatorId), and RAT types (specified by
CellMultiCarrCfgGrp.RatType) are identical, then the following parameters must
also have the same settings for these cells. Otherwise, ping-pong handovers occur.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 41

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● CellMultiCarrCfgGrp.NsaPccAnchoringPriority
● CellMultiCarrCfgGrp.NrScgPriorityOffset
● CellMultiCarrCfgGrp.NsaDcB1RsrpThldOffset

4.1.1.3.1.2 SPID-specific SCG Addition at Short Intervals Without Considering

Traffic Volume
With the function of SPID-specific SCG addition at short intervals without
considering traffic volume, the eNodeB can add a PSCell for an NSA UE working in
the LTE-only state. This implements more flexible and differentiated SCG addition
policies. It is recommended that this function be enabled when the value of
L.Traffic.User.NsaDc.PCell.Avg is greater than or equal to 10 and the value of
L.NsaDc.Capable.5gUser.RRC.Avg is greater than or equal to 20. Otherwise,
network data fluctuation may affect function observation.

The SPID_SHT_PRD_NO_TFC_SCG_ADD_SW option of the

SpidCfg.SpidAlgoSwitch parameter controls whether to enable this function for
UEs with a specified SPID. If this option is selected, the eNodeB triggers SCG
addition at short intervals without evaluating the traffic volume. In this scenario,
the short interval is specified by the
NsaDcMgmtConfig.ShortPrdNoTfcScgAddIntvl parameter. If this option is
deselected, this function is disabled. In this case, see 4.1.1.2 SCG Carrier
Management to learn configurations related to periodic triggering of SCG
addition.

NOTE

When the PERIODIC_SCG_ADD_OPT_SW option of the

NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter is selected, periodic SCG addition and
periodic NSA PCC anchoring for NSA DC UEs are decoupled. As such, the
SPID_SHT_PRD_NO_TFC_SCG_ADD_SW option of the SpidCfg.SpidAlgoSwitch parameter
controls only SCG addition at short intervals without considering traffic volume.
When the PERIODIC_SCG_ADD_OPT_SW option is deselected, the
SPID_SHT_PRD_NO_TFC_SCG_ADD_SW option controls both SCG addition at short
intervals without considering traffic volume and periodic NSA PCC anchoring.

4.1.1.3.2 QCI-specific NSA PCC Anchoring and PSCell Management Policies

4.1.1.3.2.1 Multi-Carrier Configuration Group

The eNodeB MO CellMultiCarrCfgGrp can be used to configure a multi-carrier
configuration group and set the measurement configurations related to a
downlink frequency in the group. Table 4-2 lists the parameters that jointly define
a downlink frequency in the multi-carrier configuration group.

Table 4-2 Parameters that define a frequency in the multi-carrier configuration

group

Parameter ID Description

CellMultiCarrCfgGrp.DlArfcn Downlink frequency number

CellMultiCarrCfgGrp.RatType RAT type of the downlink frequency

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 42

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter ID Description

CellMultiCarrCfgGrp.CnOperatorId ID of an operator for the downlink

frequency

CellMultiCarrCfgGrp.LocalCellId ID of a local cell for the downlink

frequency

A multi-carrier configuration group is identified by the

CellMultiCarrCfgGrp.MultiCarrCfgGroupId parameter. After a
QciPara.MultiCarrCfgGroupId parameter is set to the ID of a specific multi-
carrier configuration group, the involved QCI is associated with this group to
implement different QCI-specific NSA PCC anchoring and PSCell management
policies.

QCI-specific NSA PCC Anchoring Policy

For a downlink frequency in the multi-carrier configuration group associated with
a specific QCI, when the RAT type of this frequency is EUTRAN and this frequency
is already configured using the PccFreqCfg.PccDlEarfcn parameter, then the NSA
PCC anchoring policy for the QCI-specific UEs on this frequency can be configured
using the following parameters and options:
● CellMultiCarrCfgGrp.NsaPccAnchoringPriority: It specifies the NSA PCC
anchoring priority of the frequency. If it is set to a value ranging from 0 to 31,
the PccFreqCfg.NsaPccAnchoringPriority parameter takes this value. If it is
set to 255, the actual value of PccFreqCfg.NsaPccAnchoringPriority is not
affected.
● FORBID_MEAS_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter: It specifies whether
PCC anchoring measurement on the frequency is prohibited. If this option is
selected, PCC anchoring measurement on the frequency is prohibited. If this
option is deselected, PCC anchoring measurement on the frequency is
allowed.
● HIGH_LOAD_CELL_NSA_PCC_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter: It specifies whether
the eNodeB performs special processing on the frequency during PCC
anchoring for RRC_CONNECTED UEs or RRC_IDLE UEs in NSA networking.
– During PCC anchoring for RRC_CONNECTED UEs in NSA networking, if
this option is selected, the eNodeB selects this frequency as a candidate
NSA PCC anchor for the QCI-specific UEs only when the average
downlink PRB usage of the cell where the UEs camp exceeds
NsaDcMgmtConfig.DlPrbThldForNsaPccAnchor and the UEs are
running large-packet services. If this option is deselected, the eNodeB
always selects this frequency as a candidate NSA PCC anchor for the QCI-
specific UEs.
– During NSA PCC anchoring for RRC_IDLE UEs in NSA networking, if this
option is selected, the eNodeB does not adjust the priority of the
frequency as a candidate NSA PCC anchor for the QCI-specific UEs. If this
option is deselected, the eNodeB adjusts the priority of the frequency as
a candidate NSA PCC anchor for the QCI-specific UEs.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 43

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

If both SPID-specific and QCI-specific NSA PCC anchoring policies are configured for a
downlink frequency, the SPID-specific NSA PCC anchoring policy preferentially takes effect.

QCI-specific PSCell Management Policy

For a downlink frequency in the multi-carrier configuration group associated with
a specific QCI, when the RAT type of this frequency is NR and this frequency is
already configured using the PccFreqCfg.PccDlEarfcn or
NrScgFreqConfig.ScgDlArfcn parameter, then the PSCell management policy for
the QCI-specific UEs camping on the current serving cell on this frequency can be
configured using the following parameters and options:

● FORBID_MEAS_FLAG option of the

CellMultiCarrCfgGrp.AggregationAttribute parameter: It specifies whether
the frequency can be treated as an SCG frequency for measurement. If this
option is selected, the frequency cannot be treated as an SCG frequency for
measurement. If this option is deselected, the frequency can be treated as an
SCG frequency for measurement.
● FORBID_BLIND_CFG_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter: It specifies whether
the frequency can be blindly configured as an SCG frequency. If this option is
selected, the frequency cannot be blindly configured as an SCG frequency. If
this option is deselected, the frequency can be blindly configured as an SCG
frequency.

During measurement-based PSCell configuration, the eNodeB can configure

multiple frequencies and corresponding priorities for the SCG after filtering
frequencies based on UE capabilities. If the downlink frequency in the multi-carrier
configuration group for QCI-specific UEs is already configured using the
NrScgFreqConfig.ScgDlArfcn parameter, the priority of this frequency is equal to
NrScgFreqConfig.ScgDlArfcnPriority plus
CellMultiCarrCfgGrp.NrScgPriorityOffset.

After the SCG frequencies are configured, the eNodeB delivers measurement
configurations of these frequencies to the NSA UE. For each of these frequencies,
if the RSRP value measured by the NSA UE is greater than the B1 RSRP threshold,
the UE will report the B1 measurement result. The B1 RSRP threshold is calculated
as follows:

B1 RSRP threshold = A + B + C + D + E

● A: NrScgFreqConfig.NsaDcB1ThldRsrp
● B: CellOp.NsaDcB1RsrpThldOffset
● C: NsaDcQciParamGroup.NsaDcB1RsrpThldOffset
● D: SpidCfg.NsaDcSpidB1RsrpThldOffset
● E: NrNFreq.FreqSpecificOffset

If the downlink frequency in the multi-carrier configuration group for QCI-specific

UEs is already configured using the NrScgFreqConfig.ScgDlArfcn parameter, the
RSRP threshold for event B1 is equal to the preceding sum plus
CellMultiCarrCfgGrp.NsaDcB1RsrpThldOffset.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 44

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

If both SPID-specific and QCI-specific PSCell management policies are configured for a
downlink frequency, the SPID-specific PSCell management policy preferentially takes effect.

Configuration Requirements
For different cells (specified by CellMultiCarrCfgGrp.LocalCellId) in a multi-
carrier configuration group (specified by
CellMultiCarrCfgGrp.MultiCarrCfgGroupId), if their downlink frequency numbers
(specified by CellMultiCarrCfgGrp.DlArfcn), operator IDs (specified by
CellMultiCarrCfgGrp.CnOperatorId), and RAT types (specified by
CellMultiCarrCfgGrp.RatType) are identical, then the following parameters must
also have the same settings for these cells. Otherwise, ping-pong handovers occur.
● CellMultiCarrCfgGrp.NsaPccAnchoringPriority
● CellMultiCarrCfgGrp.NrScgPriorityOffset
● CellMultiCarrCfgGrp.NsaDcB1RsrpThldOffset

4.1.1.3.2.2 QCI-specific SCG Addition at Short Intervals Without Considering Traffic

Volume
With the function of QCI-specific SCG addition at short intervals without
considering traffic volume, the eNodeB can add a PSCell for an NSA UE working in
the LTE-only state. This implements more flexible and differentiated SCG addition
policies. It is recommended that this function be enabled when the value of
L.Traffic.User.NsaDc.PCell.Avg is greater than or equal to 10 and the value of
L.NsaDc.Capable.5gUser.RRC.Avg is greater than or equal to 20. Otherwise,
network data fluctuation may affect function observation.
The QCI_SHT_PRD_NO_TFC_SCG_ADD_SW option of the
CellQciPara.QciAlgoSwitch parameter controls whether to enable this function
for UEs with a specified QCI. If this option is selected, the eNodeB triggers SCG
addition at short intervals without evaluating the traffic volume. In this scenario,
the short interval is specified by the
NsaDcMgmtConfig.ShortPrdNoTfcScgAddIntvl parameter. If this option is
deselected, this function is disabled. In this case, see 4.1.1.2 SCG Carrier
Management to learn configurations related to periodic triggering of SCG
addition.

NOTE

When the PERIODIC_SCG_ADD_OPT_SW option of the

NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter is selected, periodic SCG addition and
periodic NSA PCC anchoring for NSA DC UEs are decoupled. As such, the
QCI_SHT_PRD_NO_TFC_SCG_ADD_SW option of the CellQciPara.QciAlgoSwitch
parameter controls only SCG addition at short intervals without considering traffic volume.
When the PERIODIC_SCG_ADD_OPT_SW option is deselected, the
QCI_SHT_PRD_NO_TFC_SCG_ADD_SW option controls both SCG addition at short intervals
without considering traffic volume and periodic NSA PCC anchoring.

4.1.2 Data Split in NSA DC

Data split can be started after the MeNB receives an SgNB Addition Request
Acknowledge message from the SgNB, indicating that an X2 tunnel has been

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 45

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

set up. The data split architecture can be configured based on the service type
by specifying a bearer type, and then the uplink and downlink data split
modes can be configured.

In this version, all types of services, except the following, are supported by the
MCG bearer, MCG_Bearer_EUTRA_PDCP, MCG split bearer, and SCG split bearer:

● Voice services that use the ROHC function: supported only by the
MCG_Bearer_EUTRA_PDCP.
● E-RABs with QCIs of 1 or 5: supported only by the MCG bearer and
MCG_Bearer_EUTRA_PDCP.
● E-RABs with QCIs of 2–4, 65–67, 75, or 82–85: supported only by the 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.
● For details about the processing of extended QCIs, see QoS Management in
5G RAN feature documentation.
NOTE

● In the Option 3x architecture, if data distribution only to MCG is configured in the

downlink or uplink, it is recommended that the NRDUCellQciBearer.UeInactivityTimer
parameter 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.
● The PDCP layer will discard timeout data packets and the data split performance will be
affected in the following situations:
● In Option 3, the RlcPdcpParaGroup.DiscardTimer parameter is set to a value
other than DiscardTimer_Infinity.
● In Option 3x, the gNBPdcpParamGroup.DlPdcpDiscardTimer parameter is set to a
value other than DiscardTimer_Infinity.
● In NSA DC, data transmission delay is not guaranteed.
● In NSA DC, the transport network cannot ensure fairness among UEs. If multiple UEs are
performing data split at the same time, the data split rates for the UEs may be different.
● In NSA DC, assume that uplink transmission is switched towards the MCG due to uplink
fallback to LTE or uplink data transmission path selection. Then, uplink transmission is
also switched towards the MCG for NSA UEs whose E-RABs with QCIs in the range of 2–
4, 65–67, 75, and 82–85 are set up on SCG split bearers. In this case, one-way X2 delay
is introduced.

4.1.2.1 Data Split Policy Selection

The CellQciPara.NsaDcDefaultBearerMode parameter specifies the bearer mode:
● When this parameter is set to MCG_SPLIT_BEARER, the data split architecture
is Option 3.
● When this parameter is set to SCG_SPLIT_BEARER, the data split architecture
is Option 3x.
● When this parameter is set to MCG_BEARER or MCG_BEARER_EUTRA_PDCP,
data is transmitted only on the LTE side.
For QCI 1 or QCI 5, it is recommended that the
CellQciPara.NsaDcDefaultBearerMode parameter be set to
MCG_BEARER_EUTRA_PDCP.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 46

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

● To ensure the consistency of user experience with services that have the same QCI
between eNodeBs, it is recommended that the same bearer mode be set on these
eNodeBs for the same QCI.
● When the value of the CellQciPara.NsaDcDefaultBearerMode parameter changes, the
data volume allocated to the LTE or NR side may change significantly due to the change
of the bearer mode.

4.1.2.1.1 Downlink Data Split

Downlink Data Split Mode Selection in Option 3

In Option 3, the downlink data split mode is specified by the QCI-level parameter
NsaDcQciParamGroup.DlDataPdcpSplitMode on the LTE side.
● Downlink data is transmitted only on the MCG side.
When the NsaDcQciParamGroup.DlDataPdcpSplitMode parameter is set to
MCG_ONLY, downlink PDCP PDUs are all distributed to the MCG side.
● Downlink data is transmitted only on the SCG side.
When the NsaDcQciParamGroup.DlDataPdcpSplitMode parameter is set to
SCG_ONLY, downlink PDCP PDUs are all distributed to the SCG side.
● Downlink data is distributed dynamically.
– If the NsaDcQciParamGroup.DlDataPdcpSplitMode parameter is set to
SCG_AND_MCG, the primary path is on the PDCP data split anchor side.
Data is preferentially distributed to the primary path and then distributed
between the MeNB and the SgNB.
– If the NsaDcQciParamGroup.DlDataPdcpSplitMode parameter is set to
SCG_PREFERRED, the primary path is on the SgNB side. Data is
preferentially distributed to the primary path and then distributed
between the MeNB and the SgNB.
– If the NsaDcQciParamGroup.DlDataPdcpSplitMode parameter is set to
ADAPT_PRIMARY_PATH, the primary path is adaptively determined
based on air interface capabilities during PDCP data split. Data is
preferentially distributed to the primary path and then distributed
between the MeNB and the SgNB.
Dynamic PDCP data split is based on the LTE and NR air interface status (such
as the RLC transmission rate, air interface transmission delay, and RLC buffer
size) and X2 interface status (such as the transmission delay and congestion
status). The UE PDCP layer re-orders downlink PDCP PDUs and then transmits
them to the upper layer.
On the LTE side, the CellOpQciPara.NsaDcQciParamGroupId parameter can be
associated with the NsaDcQciParamGroup.NsaDcQciParamGroupId parameter to
configure operator-specific downlink data split policies.
● If the CellOpQciPara.NsaDcQciParamGroupId parameter is set to a value in
the range of 0 to 9, the downlink data split policy for the operator is
determined by the associated NsaDcQciParamGroup.DlDataPdcpSplitMode
parameter.
● If the CellOpQciPara MO is not configured, the downlink data split policies
for all operators are determined by the CellQciPara.NsaDcQciParamGroupId
parameter.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 47

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

The NSA_TNLLOAD_BASED_TCSPLIT_SW option of the

NsaDcAlgoParam.NsaDcAlgoSwitch parameter specifies whether to enable the function of
stopping data distribution to the LTE side based on transport load. When the transport load
of the main control board on the LTE side is high, the MeNB does not trigger SCG addition.
This prevents the transport load from increasing due to RLC status reporting for data split.

Downlink Data Split Mode Selection in Option 3x

In Option 3x, the downlink data split mode is specified by the
gNBPdcpParamGroup.DlDataPdcpSplitMode parameter on the NR side.
● Downlink data is transmitted only on the MCG side.
When the gNBPdcpParamGroup.DlDataPdcpSplitMode parameter is set to
MCG_ONLY, downlink PDCP PDUs are all distributed to the MCG.
● Downlink data is transmitted only on the SCG side.
When the gNBPdcpParamGroup.DlDataPdcpSplitMode parameter is set to
SCG_ONLY, downlink PDCP PDUs are all distributed to the SCG.
● Downlink data is distributed dynamically.
– If the gNBPdcpParamGroup.DlDataPdcpSplitMode parameter is set to
SCG_AND_MCG, the primary path is on the PDCP data split anchor side.
Data is preferentially distributed to the primary path and then distributed
between the MeNB and the SgNB.
– If the gNBPdcpParamGroup.DlDataPdcpSplitMode parameter is set to
MCG_PREFERRED, the primary path is on the MeNB side. Data is
preferentially distributed to the primary path and then distributed
between the MeNB and the SgNB.
– If the gNBPdcpParamGroup.DlDataPdcpSplitMode parameter is set to
ADAPT_PRIMARY_PATH, the primary path is adaptively determined
based on air interface capabilities during PDCP data split. Data is
preferentially distributed to the primary path and then distributed
between the MeNB and the SgNB.
NOTE

● A QCI-specific service type is associated with a PDCP parameter group by adding

an NRCELLQCIBEARER MO.
● The NSA_TNLLOAD_BASED_TCSPLIT_SW option of the
NsaDcAlgoParam.NsaDcAlgoSwitch parameter specifies whether to enable the
function of stopping data distribution to the LTE side based on transport load.
Assume that the transport load of the main control board on the LTE side is high. If
the data split mode is not set to MCG_ONLY, data split on the LTE side will be
stopped, preventing load increasing due to RLC status reporting for data split. If
the data split mode is set to MCG_ONLY, data split will not be stopped, preventing
data transmission interruption.
When NSA DC carries TCP services, the downlink PDCP PDU reordering time
on the UE side increases if all the following conditions are met: the
throughput on the LTE and NR sides differs by more than three times, the
throughput on the side with high throughput is stable, but the throughput on
the side with low throughput fluctuates (due to factors such as interference or
load). This affects the TCP traffic and may cause negative gains.
In NR low-frequency scenarios, the PDCP_SN_OFFSET_SW option of the
NRCellNsaDcConfig.NsaDcAlgoSwitch parameter can be used to specify

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 48

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

whether to add an offset to the SNs of packets sent to the low-speed side. If
this option is selected, the PDCP SN offset is used. In this case, data is
preferentially distributed to high-speed side between LTE and NR. In this case,
downlink traffic volume of the high-speed side increases and that of the other
side decreases. If this option is deselected, the PDCP SN offset is not used.
On the NR side, the NRCellOpQciBearer.AmPdcpParamGroupId or
NRCellOpQciBearer.UmPdcpParamGroupId parameter can be associated with
the gNBPdcpParamGroup.PdcpParamGroupId parameter to configure operator-
specific downlink data split policies.
● If the NRCellOpQciBearer.AmPdcpParamGroupId or
NRCellOpQciBearer.UmPdcpParamGroupId parameter is set to a value in
the range of 0 to 9, the downlink data split policy for the operator is
determined by the gNBPdcpParamGroup.DlDataPdcpSplitMode parameter
corresponding to the associated gNBPdcpParamGroup.PdcpParamGroupId
parameter.
● If the NRCellOpQciBearer MO is not configured, the downlink data split
policies for all operators are determined by the
gNBPdcpParamGroup.PdcpParamGroupId parameter.

Basic Mechanism of Downlink Dynamic Data Split

If downlink dynamic data split is used (that is, the
gNBPdcpParamGroup.DlDataPdcpSplitMode parameter is set to
SCG_AND_MCG), the LTE and NR RLC layers send transmission capability
information such as the RLC transmission rate and buffered data volume to the
PDCP layer. Then, the PDCP layer performs dynamic data split based on the LTE
and NR air interface status and X2 interface status (such as the transmission delay
and congestion status). For details about X2 interface status, see Transmission
Resource Management in 5G RAN feature documentation.
The basic principle of data split is that data is preferentially distributed to the
primary path and then distributed between the MeNB and the SgNB. The main
steps are as follows:
1. Data is preferentially distributed to the RLC layer of the primary path based
on the RLC transmission rate and other factors.
2. Data is then distributed to the RLC layer of the other side based on the
desired buffer size reported by the RLC layer to align the delays on the two
sides. This way, the distributed data can reach the UE side at the same time.
For details about the desired buffer size, see section 5.5.3.5 "Desired buffer
size for the data radio bearer" in 3GPP TS 38.425 V15.6.0.
3. After the delays are aligned, data is distributed by the PDCP layer to the
eNodeB and gNodeB sides in turn based on their RLC transmission rates and
other factors.

Enhanced Mechanism of Downlink Dynamic Data Split

The enhanced mechanism of downlink dynamic data split includes the following
functions:
● Downlink real-time data split
● Downlink dynamic data split stop and resumption

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 49

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● Downlink data split optimization in DRX scenarios

In Option 3x (not in Option 3) networking, downlink real-time data split can take
effect to fully utilize the data transmission capabilities of LTE and NR air interfaces
and improve user experience when all the following options are selected:

● On the LTE side: NSA_SPLIT_RATE_OPT_SW option of the

NsaDcMgmtConfig.NsaDcAlgoExtSwitch parameter
● On the NR side: NSA_SPLIT_RATE_OPT_SW option of the
NRCellNsaDcConfig.NsaDcAlgoSwitch parameter, and
NSA_PDCP_SPLIT_OPT_SW option of the gNodeBParam.NsaDcOptSwitch
parameter

The real-time data split function shortens the reporting period of RLC transmission
capability information by exchanging messages between the RLC and PDCP layers
in real time. In this way, the PDCP layer can deliver data in a timely manner,
reducing air interface resource waste. This function estimates the transmission rate
based on the MAC scheduling capability in service interruption scenarios,
improving the data split accuracy.

Dynamic data split is stopped at the PDCP layer in certain scenarios and this
penalty lasts for a period of time, as listed in Table 4-3.

Table 4-3 Data split stop scenarios and penalty period parameters

Data Split Stop Penalty Period Parameter Architecture

Scenario

Data rates differ NRCellNsaDcConfig.DlDataSplitPen Option 3x

considerably between altyPeriod
LTE and NR sides.
NsaDcAlgoParam.DlDataSplitPenal- Option 3
tyPeriod
Packet loss occurs over gNodeBParam.AbnDlDataSplitPe- Option 3x
the X2 interface, or RLC naltyPrd
status reports are not
updated on the NR side NsaDcAlgoParam.AbnDlDataSplitPe Option 3
in a timely manner. naltyPrd

Data congestion occurs NRCellNsaDcConfig.HighDelaySplit Option 3x

because the air PenaltyPrd
interface on the LTE or
NR side is abnormal.

If downlink data split is stopped when data rates differ considerably between LTE
and NR sides or data congestion occurs because the air interface on one side is
abnormal, downlink data split can be resumed when the PDCP detects that the air
interface condition becomes better. This function takes effect only if it is enabled
as follows:

● In Option 3x, select the NSA_SPLIT_ADAPT_RECOVERY_SW option of the

gNodeBParam.NsaDcOptSwitch parameter.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 50

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● In Option 3, select the NSA_SPLIT_ADAPT_RECOVERY_SW option of the

NsaDcAlgoParam.NsaDcAlgoSwitch parameter.
NOTE

● In NSA DC, an IP performance monitoring (IP PM) session is automatically created over
the X2 interface. The X2 interface status information required by PDCP data split is
obtained through the IP PM session.
● If the downlink data split mode needs to be set to SCG_AND_MCG, it is recommended
that IP PM be configured in advance for X2 delay observation.
● If the number of IP PM sessions to be set up exceeds the limit, IP PM sessions fail to be
set up and the PDCP layer cannot obtain X2 delay information. In this case, data split
performance deteriorates.

When data split is stopped due to data congestion caused by an air interface
exception on one side, the PDCP migrates data from the congested side to the
other side for delay-based retransmission if the
NSA_RETRANS_BASED_ON_DELAY_SW option of the
gNodeBParam.NsaDcOptSwitch parameter is selected.

In DRX scenarios, NSA downlink data split optimization is controlled by the

DRX_NSA_SPLIT_OPT_SW option of the NsaDcAlgoParam.NsaDcAlgoSwitch
parameter on the LTE side and the DRX_NSA_SPLIT_OPT_SW option of the
gNodeBParam.NsaDcOptSwitch parameter on the NR side.

● If the primary path for uplink data split is on the SCG side, the PDCP migrates
data packets that fall into the LTE sleep time to the NR side for
retransmission, stops data split on the LTE side, and resumes data split in the
active time. For details about the sleep time and active time, see DRX and
Signaling Control in eRAN feature documentation and DRX in 5G RAN feature
documentation.
● If the primary path for uplink data split is on the MCG side, the PDCP
migrates data packets that fall into the NR sleep time to the LTE side for
retransmission, stops data split on the NR side, and resumes data split in the
active time. For details about the sleep time and active time, see DRX and
Signaling Control in eRAN feature documentation and DRX in 5G RAN feature
documentation.
NOTE

In DRX scenarios, it is recommended that NSA downlink data split optimization be enabled
together with NSA uplink preallocation so that LTE and NR are in active time if possible
when there are services.

4.1.2.1.2 Uplink Data Split

Uplink Data Split Mode Selection in Option 3

In Option 3, the uplink data split mode is specified by the QCI-level parameters
NsaDcQciParamGroup.UlDataSplitPrimaryPath and
NsaDcQciParamGroup.UlDataSplitThreshold on the LTE side:
● Uplink data is transmitted only on the MCG side.
The NsaDcQciParamGroup.UlDataSplitThreshold parameter is set to
INFINITY, and the NsaDcQciParamGroup.UlDataSplitPrimaryPath
parameter is set to MCG.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 51

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● Uplink data is transmitted only on the SCG side.

The NsaDcQciParamGroup.UlDataSplitThreshold parameter is set to
INFINITY, and the NsaDcQciParamGroup.UlDataSplitPrimaryPath
parameter is set to SCG.
● Uplink data is distributed dynamically.
The NsaDcQciParamGroup.UlDataSplitThreshold parameter is set to a value
other than INFINITY, and the UE PDCP buffer data size is greater than or
equal to this threshold.

On the LTE side, the CellOpQciPara.NsaDcQciParamGroupId parameter can be

associated with the NsaDcQciParamGroup.NsaDcQciParamGroupId parameter to
configure operator-specific uplink data split policies.
● If the CellOpQciPara.NsaDcQciParamGroupId parameter is set to a value in
the range of 0 to 9, the uplink data split policy for the operator is determined
by the NsaDcQciParamGroup.UlDataSplitPrimaryPath and
NsaDcQciParamGroup.UlDataSplitThreshold parameters corresponding to
the associated NsaDcQciParamGroup.NsaDcQciParamGroupId parameter.
● If the CellOpQciPara MO is not configured, the uplink data split policies for
all operators are determined by the CellQciPara.NsaDcQciParamGroupId
parameter.

NOTE

● If the NsaDcQciParamGroup.UlDataSplitThreshold parameter is set to a value other

than INFINITY and the data volume buffered at the UE PDCP layer is less than this
threshold, the data transmission mode is determined by the
NsaDcQciParamGroup.UlDataSplitPrimaryPath parameter.
● If the NSA UE does not support dynamic uplink data split, the data transmission mode
that takes effect for the UE is determined by the
NsaDcQciParamGroup.UlDataSplitPrimaryPath parameter as in scenarios where the
NsaDcQciParamGroup.UlDataSplitThreshold parameter is set to INFINITY.
● If the NsaDcQciParamGroup.UlDataSplitThreshold parameter is set to INFINITY and
the NsaDcQciParamGroup.UlDataSplitPrimaryPath parameter is set to SCG, there is
still uplink data transmission on the LTE side even when the uplink data split primary
path is switched to the MCG or when the SCG is released.

Uplink Data Split Mode Selection in Option 3x

In Option 3x, the uplink data split mode is specified by the parameters
gNBPdcpParamGroup.UlDataSplitPrimaryPath and
gNBPdcpParamGroup.UlDataSplitThreshold on the NR side:
● Uplink data is transmitted only on the MCG side.
The gNBPdcpParamGroup.UlDataSplitThreshold parameter is set to
INFINITY, and the gNBPdcpParamGroup.UlDataSplitPrimaryPath parameter
is set to MCG.
● Uplink data is transmitted only on the SCG side.
The gNBPdcpParamGroup.UlDataSplitThreshold parameter is set to
INFINITY, and the gNBPdcpParamGroup.UlDataSplitPrimaryPath parameter
is set to SCG.
● Uplink data is distributed dynamically.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 52

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

The gNBPdcpParamGroup.UlDataSplitThreshold parameter is set to a value

other than INFINITY, and the UE PDCP buffer data size is greater than or
equal to this threshold.
On the NR side, the NRCellOpQciBearer.AmPdcpParamGroupId or
NRCellOpQciBearer.UmPdcpParamGroupId parameter can be associated with
the gNBPdcpParamGroup.PdcpParamGroupId parameter to configure operator-
specific uplink data split policies.
● If the NRCellOpQciBearer.AmPdcpParamGroupId or
NRCellOpQciBearer.UmPdcpParamGroupId parameter is set to a value in
the range of 0 to 9, the uplink data split policy for the operator is determined
by the gNBPdcpParamGroup.UlDataSplitPrimaryPath and
gNBPdcpParamGroup.UlDataSplitThreshold parameters corresponding to
the associated gNBPdcpParamGroup.PdcpParamGroupId parameter.
● If the NRCellOpQciBearer MO is not configured, the uplink data split policies
for all operators are determined by the
gNBPdcpParamGroup.PdcpParamGroupId parameter.

NOTE

● If the gNBPdcpParamGroup.UlDataSplitThreshold parameter is set to a value other

than INFINITY and the data volume buffered at the UE PDCP layer is less than this
threshold, the data transmission mode is determined by the
gNBPdcpParamGroup.UlDataSplitPrimaryPath parameter.
● If the NSA UE does not support dynamic uplink data split, the data transmission mode
that takes effect for the UE is determined by the
gNBPdcpParamGroup.UlDataSplitPrimaryPath parameter as in scenarios where the
gNBPdcpParamGroup.UlDataSplitThreshold parameter is set to INFINITY.
● If the gNBPdcpParamGroup.UlDataSplitThreshold parameter is set to INFINITY and
the gNBPdcpParamGroup.UlDataSplitPrimaryPath parameter is set to SCG, there is
still uplink data transmission on the LTE side even when the uplink data split primary
path is switched to the MCG or when the SCG is released.
● If NSA is selected for an NSA UE during NSA/SA selection based on uplink coverage, the
uplink primary path of the UE is switched to the MCG side (that is, uplink data is
transmitted only on the MCG side). For details about NSA/SA selection based on uplink
coverage, see NSA-SA Selection Based on User Experience.

Uplink AMBR Control for Data Split

● During initial SCG configuration, the aggregate maximum bit rate (AMBR) of
the MeNB and SgNB is configured based on the UE capability.
– If the UE supports uplink data split, the AMBR is configured for the MeNB
and SgNB based on the proportion specified by the
NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio parameter.
– If the UE does not support uplink data split, the AMBR is configured for
the MeNB and SgNB based on the instruction of the core network.
● The MAC layers of the MeNB and SgNB schedule data based on the
configured AMBRs.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 53

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

● If uplink data is distributed dynamically or transmitted only to the SCG, the

NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio parameter cannot be set to 100.
● If uplink data is distributed dynamically or transmitted only to the MCG, the
NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio parameter cannot be set to 0.
● If uplink data is distributed only to the SCG or MCG, the
NsaDcMgmtConfig.NsaDcUeMcgUlAmbrRatio parameter can be set to 255. In this
case, the AMBRs of both the MeNB and the SgNB are configured based on the AMBRs
delivered by the core network.
● When the uplink data split mode is switched to MCG only, the AMBR of the MeNB is
configured based on the AMBR delivered by the core network.

4.1.2.2 Uplink Fallback to LTE

In NSA DC scenarios, when the CellQciPara.NsaDcDefaultBearerMode parameter
is set to MCG_SPLIT_BEARER or SCG_SPLIT_BEARER, the network side controls
the UE to dynamically send uplink data to the gNodeB or eNodeB based on the
uplink SINR of NR. In this way, the uplink coverage of LTE can be used to
compensate for the insufficient uplink coverage of NR. It is recommended that this
function be enabled when LTE and NR cells are co-sited and uplink data is
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.
If this option is selected in Option 3:
● When the uplink NR SINR is less than
NRDUCellSrsMeas.NsaUlFackToLteSinrThld minus
NRDUCellSrsMeas.NsaUlFackToLteSinrHyst for five consecutive times at an
interval specified by NRDUCellSrsMeas.NsaUlToLteSinrTimeToTrig, the
eNodeB instructs the UE to perform data transmission on the LTE side by
sending an RRC connection reconfiguration message to the UE.
● When the uplink NR SINR is greater than
NRDUCellSrsMeas.NsaUlFackToLteSinrThld plus
NRDUCellSrsMeas.NsaUlFackToLteSinrHyst for five consecutive times at an
interval specified by NRDUCellSrsMeas.NsaUlToLteSinrTimeToTrig, the
eNodeB instructs the UE to perform data transmission in the original mode by
sending an RRC connection reconfiguration message to the UE.
If this option is selected in Option 3x:
● When the uplink NR SINR is less than
NRDUCellSrsMeas.NsaUlFackToLteSinrThld minus
NRDUCellSrsMeas.NsaUlFackToLteSinrHyst for five consecutive times at an
interval specified by NRDUCellSrsMeas.NsaUlToLteSinrTimeToTrig, the
gNodeB triggers a change in the uplink data split mode by sending an SgNB
Modification Required message to the eNodeB. The eNodeB instructs the UE
to transmit data on the LTE side by sending an RRC connection
reconfiguration message to the UE.
● When the uplink NR SINR is greater than
NRDUCellSrsMeas.NsaUlFackToLteSinrThld plus

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 54

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NRDUCellSrsMeas.NsaUlFackToLteSinrHyst for five consecutive times at an

interval specified by NRDUCellSrsMeas.NsaUlToLteSinrTimeToTrig, the
gNodeB triggers a change in the uplink data split mode by sending an SgNB
Modification Required message to the eNodeB. The eNodeB instructs the UE
to use the original uplink data split mode by sending an RRC connection
reconfiguration message to the UE.

NOTE

If the NRDUCellSrsMeas.NsaUlFackToLteSinrThld parameter is set to a too large value,

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

4.1.2.3 Fast Retransmission for Downlink Data Split

In NSA DC downlink data split scenarios, data may be overstocked on the LTE or
NR side if the air interface on this side is interfered. In this case, fast
retransmission for downlink data split can be used to quickly migrate the
overstocked data to the other side for fast retransmission. This reduces the impact
of data overstock on the TCP sliding window and increases UE throughput.
This function is controlled by the NSA_DC_FAST_RETRANS_SWITCH option of the
gNodeBParam.NsaDcOptSwitch parameter on the NR side. When this option is
selected and the PDCP layer detects that the difference between the duration for
the RLC buffer to be empty on the LTE side and that on the NR side is greater
than a certain threshold, data is migrated from the rate drop side to the other side
for fast retransmission.
NOTE

● Data migration is not triggered in the following situations: the RLC transmission mode is
UM or TM, the X2 one-way delay is greater than or equal to 10 ms, the CPU usage is
greater than 70%, the PDCP SN length is not 18 bits, the downlink data split mode is
MCG only or SCG only, and the downlink data split bearer type is SRB.
● Fast retransmission for downlink data split is mutually exclusive with the PDCP SN offset
function. The SN offset function takes effect preferentially.
● When packet loss occurs on the X2 link, if data split is performed on the LTE side, data is
not migrated from the LTE side to the NR side; if data split is performed on the NR side,
data is not migrated from the NR side to the LTE side.

4.1.2.4 CP/UP Separation

In the initial phase of NR deployment, 3.5 GHz or 28 GHz frequency bands are
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,
as shown in Figure 4-4, rendering higher throughput and larger capacity.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 55

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-4 CP/UP separation

● Parameter configurations for downlink CP/UP separation

Data Split CP UP Parameter Setting
Architecture

Option 3 LTE NR On the LTE side:

● Set the CellQciPara.NsaDcDefaultBearer-
Mode parameter to MCG_SPLIT_BEARER.
● Set the
NsaDcQciParamGroup.DlDataPdcpSplit-
Mode parameter to SCG_ONLY.
Option 3x LTE NR On the LTE side:
● Set the CellQciPara.NsaDcDefaultBearer-
Mode parameter to SCG_SPLIT_BEARER.
On the NR side:
● Set the
gNBPdcpParamGroup.DlDataPdcpSplit-
Mode parameter to SCG_ONLY.

● Parameter configurations for uplink CP/UP separation

Data Split CP UP Parameter Setting
Architecture

Option 3 LTE NR On the LTE side:

● Set the
NsaDcQciParamGroup.UlDataSplitThres-
hold parameter to INFINITY.
● Set the
NsaDcQciParamGroup.UlDataSplitPrimar-
yPath parameter to SCG.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 56

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Data Split CP UP Parameter Setting

Architecture

Option 3x LTE NR On the NR side:

● Set the
gNBPdcpParamGroup.UlDataSplitThres-
hold parameter to INFINITY.
● Set the
gNBPdcpParamGroup.UlDataSplitPrimar-
yPath parameter to SCG.

4.1.2.5 UL/DL Separation

In NSA DC, when NR uplink coverage is limited but LTE uplink coverage is not
limited, uplink and downlink user-plane services are carried respectively on the LTE
side and NR side. LTE uplink coverage is used to compensate for the insufficient
NR uplink coverage.
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:

● Set the ● Set the
NsaDcQciParamGroup.UlDa CellQciPara.NsaDcDefault
taSplitThreshold parameter BearerMode parameter to
to INFINITY. MCG_SPLIT_BEARER.
● Set the ● Set the
NsaDcQciParamGroup.UlDa NsaDcQciParamGroup.Dl
taSplitPrimaryPath DataPdcpSplitMode
parameter to MCG. parameter to SCG_ONLY.

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

● Set the ● Set the
gNBPdcpParamGroup.UlDat CellQciPara.NsaDcDefault
aSplitThreshold parameter BearerMode parameter to
to INFINITY. SCG_SPLIT_BEARER.
● Set the On the NR side:
gNBPdcpParamGroup.UlDat ● Set the
aSplitPrimaryPath gNBPdcpParamGroup.DlD
parameter to MCG. ataPdcpSplitMode
parameter to SCG_ONLY.

4.1.2.6 NSA UE Data Split Based on CCE Usage

A low-frequency LTE cell has a large coverage area and can easily admit a large
number of UEs at the cell edge. If NSA UEs can only camp on this cell for NSA DC,

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 57

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

the cell is likely to be congested. In this case, the user experience of non-NSA non-
CA UEs in the cell deteriorates.
This function controls downlink data split of NSA DC and CA based on the CCE
usage of the PCell. It alleviates cell congestion by degrading the user experience of
NSA DC and CA UEs and improves the user experience of non-NSA non-CA UEs in
the cell. It is recommended that this function be enabled when the downlink data
split mode is set to SCG_ONLY or SCG_AND_MCG.
This function takes effect only in LTE FDD cells with a bandwidth less than or
equal to 5 MHz. It is controlled by the
CellDlschAlgo.DataSplitCceUsageHighThld parameter. Table 4-4 lists the
configured values and effective values of CCE usage threshold parameters for data
split.

Table 4-4 Configured values and effective values of CCE usage threshold
parameters for data split
Parameter Configured Effective Value
Value

CellDlschAlgo.DataSplitCce 0–100 Equal to the configured value

UsageHighThld (an upper
threshold of CCE usage for
data split)

CellDlschAlgo.DataSplitCce 0–100 ● The effective value of this

UsageLowThld (a lower parameter is 0 if the
threshold of CCE usage for configured value of this
data split) parameter is greater than
or equal to the effective
value of
CellDlschAlgo.DataSplitCc
eUsageHighThld.
● The effective value of this
parameter is equal to the
configured value of this
parameter if the configured
value of this parameter is
less than the effective value
of
CellDlschAlgo.DataSplitCc
eUsageHighThld.

The eNodeB determines whether the PCell of NSA DC is congested based on the
measured and filtered CCE usage of the PCell.
The CCE usage of the PCell of an NSA UE is calculated as follows:
CCE usage = max((L.ChMeas.CCE.ULUsed.Equivalent +
L.ChMeas.CCE.DLUsed.Equivalent) / L.ChMeas.CCE.AvailPower.Equivalent x
100%, (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed +
L.ChMeas.CCE.DLUsed) / L.ChMeas.CCE.Avail x 100%)

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 58

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

The calculated CCE usage is then filtered and compared with the values of
CellDlschAlgo.DataSplitCceUsageHighThld and
CellDlschAlgo.DataSplitCceUsageLowThld to determine whether the PCell is
congested.
● If the CCE usage of the PCell of NSA DC is greater than the effective value of
CellDlschAlgo.DataSplitCceUsageHighThld, the PCell is congested.
● If the CCE usage of the PCell of NSA DC is less than or equal to the effective
value of CellDlschAlgo.DataSplitCceUsageLowThld, the PCell is not
congested.
● If the CCE usage of the PCell of NSA DC is less than or equal to the effective
value of CellDlschAlgo.DataSplitCceUsageHighThld and greater than the
effective value of CellDlschAlgo.DataSplitCceUsageLowThld, the congestion
status of the PCell is the same as that in the last second.
Table 4-5 describes the handling mechanisms based on the congestion status of
the PCell.

Table 4-5 Handling mechanisms based on the congestion status of the PCell
Scenario PCell Congested PCell Not Congested

A UE has ● When the Downlink data of the UE is

only one CCE_USAGE_BASED_SPLIT_OPT_S distributed as usual.
carrier on W option of the In Option 3x, however, if
the LTE CellAlgoExtSwitch.DlSchEnhSwit the data split mode is not
side. ch parameter is selected: set to MCG_ONLY and
– In Option 3, downlink data of backpressure of NSA data
the UE is distributed only to split based on transport
the NR side through the PDCP load is triggered, downlink
layer of the eNodeB. data of the UE is
– In Option 3x, downlink data of transmitted only on the NR
the UE is distributed only to side.
the NR side through the PDCP
layer of the gNodeB.
● When the
CCE_USAGE_BASED_SPLIT_OPT_S
W option of the
CellAlgoExtSwitch.DlSchEnhSwit
ch parameter is deselected,
downlink data is dynamically
distributed for the UE.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 59

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Scenario PCell Congested PCell Not Congested

A UE has Downlink data of the UE on the LTE Downlink data of the UE

multiple side is transmitted only on LTE SCCs. on the LTE side is
carriers on transmitted as usual.
the LTE In Option 3x, however, if
side. the data split mode is not
set to MCG_ONLY and
backpressure of NSA data
split based on transport
load is triggered, downlink
data of the UE is
transmitted only on the NR
side.

If the downlink data of an NSA UE cannot be transmitted in the PCell:

● The user experience of this NSA UE deteriorates. If the number of NSA UEs in
the cell is very large, the Cell Downlink Average Throughput decreases.
● If the LTE SCC or NR SCG coverage or the air interface quality deteriorates,
the user experience of this NSA UE deteriorates significantly.
● The downlink retransmission rate and downlink scheduling delay increase for
the NSA UE but decrease for non-NSA UEs. Therefore, the downlink
retransmission rate and downlink packet delay of the cell change.
● More resources in the PCell are available to non-NSA non-CA UEs. If the
proportion of small-packet services is high, the number of scheduling times in
the PCell increases and accordingly the CCE usage in the PCell increases.
NOTE

● After NSA UE data split based on CCE usage takes effect, the L.CA.Traffic.bits.DL.PCell
counter value of the PCell may decrease if some NSA UEs in the PCell have multiple
carriers on the LTE side.
● Assume that the CCE_USAGE_BASED_SPLIT_OPT_SW option of the
CellAlgoExtSwitch.DlSchEnhSwitch parameter is selected, and an NSA UE has only one
carrier on the LTE side and its downlink data is distributed only to the NR side. Then,
data-volume-based LTE SCC addition and NSA PCC anchoring cannot be triggered as the
data volume is insufficient.

4.1.2.7 SPID-based NSA Uplink Primary Path Configuration

This function allows operators to configure uplink primary path selection policies
and uplink data split thresholds for different types of NSA UEs based on SPIDs,
thereby providing differentiated experience for these UEs. This function takes
effect only for non-GBR bearers. It does not affect the configuration of uplink
primary paths and uplink data split thresholds for GBR bearers.

When an NSA UE with a specific SPID accesses or is handed over to the network,
the uplink primary path and uplink data split threshold for the NSA UE are
specified by the parameters listed in Table 4-6.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 60

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Table 4-6 SPID-based NSA uplink primary path configuration

Parameter Name Parameter Setting

Uplink Primary Path Selection ● MCG: Data is preferentially distributed

Mode to the MCG.
(gNBRfspConfig.UlPrimaryPathS ● SCG: Data is preferentially distributed to
elMode) the SCG.
● DEFAULT: The SPID-based NSA uplink
primary path configuration function
does not take effect. The QCI-specific
configuration takes effect by default.

Uplink Split Threshold ● This parameter does not take effect

(gNBRfspConfig.UlDataSplitThre when the
shold) gNBRfspConfig.UlPrimaryPathSel-
Mode parameter is set to DEFAULT.
● When this parameter is set to INFINITY:
– If the
gNBRfspConfig.UlPrimaryPathSel-
Mode parameter is set to MCG,
uplink data of the NSA UE is
transmitted only on the MCG side.
– If the
gNBRfspConfig.UlPrimaryPathSel-
Mode parameter is set to SCG, uplink
data of the NSA UE is transmitted
only on the SCG side.
● When this parameter is set to a value
other than INFINITY and the UE PDCP
buffer data size is greater than or equal
to the threshold specified by this
parameter, uplink data is distributed
dynamically.

4.1.3 Uplink Power Control in NSA DC

The eNodeB and the gNodeB can control the uplink transmit power of NSA
UEs in the NSA DC state through parameter configuration.
Initial power control is performed for NSA UEs that initially access the network,
and time division multiplexing (TDM) power control is performed to improve
uplink coverage when trigger conditions are met, as shown in Figure 4-5. TDM
power control is an enhancement to uplink power control in NSA DC. For details,
see EPC-based NSA Performance Enhancement.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 61

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-5 Uplink power control in NSA DC

The maximum transmit power for initial power control is configured as follows:

● If the maximum uplink transmit power supported by an NSA UE that initially

accesses the network is 23 dBm, the following parameters need to be set on
the LTE side to specify the maximum transmit power for the LTE and NR sides
of the UE in NSA DC:
– NsaDcMgmtConfig.NsaDcUeMcgUlMaximumPower, indicating the
maximum uplink transmit power on the MCG side
– NsaDcMgmtConfig.NsaDcUeScgUlMaximumPower, indicating the
maximum uplink transmit power on the SCG side
It is recommended that the sum of the maximum uplink transmit power on
the MCG side and that on the SCG side do not exceed 23 dBm.
● If the maximum uplink transmit power supported by an NSA UE that initially
accesses the network is 26 dBm, the maximum transmit power values
configured for the LTE and NR sides of the UE are both 23 dBm.
NOTE

After an NSA UE accesses the network, a maximum transmit power is configured for the UE
on the NR side. The total power of uplink channels at the same time cannot exceed the
maximum transmit power. For details about power control on each channel, see Power
Control in 5G RAN feature documentation.

4.1.4 Interference Avoidance in NSA DC

In NSA DC scenarios, if secondary intermodulation signals generated during uplink
concurrence of LTE and NR on the UE side fall in the downlink frequency band of
LTE, the UE will experience interference when receiving downlink signals of LTE
and the UE receiver sensitivity will decrease by a maximum of 28.6 dB. If
secondary harmonic signals generated during uplink transmission of LTE on the UE
side fall in the downlink frequency band of NR, the UE will experience interference
when receiving downlink signals of NR and the UE receiver sensitivity will decrease
by a maximum of 23.9 dB. Interference avoidance in NSA DC is implemented
based on interference type identification. It uses certain interference
avoidance policies for secondary intermodulation interference and secondary
harmonic interference to reduce the impact of interference.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 62

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

4.1.4.1 Interference Type Identification

Table 4-7 describes the parameters required for determining the interference type.

Table 4-7 Parameters required for determining the interference type

Parameter Description Calculation Method

LTE_UL_low Minimum value of the LTE uplink center

LTE uplink frequency frequency – LTE
range bandwidth/2

LTE_UL_high Maximum value of the LTE uplink center

LTE uplink frequency frequency + LTE
range bandwidth/2

LTE_DL_low Minimum value of the LTE downlink center

LTE downlink frequency frequency – LTE
range bandwidth/2

LTE_DL_high Maximum value of the LTE downlink center

LTE downlink frequency frequency + LTE
range bandwidth/2

NR_UL_low Minimum value of the NR uplink center

NR uplink frequency frequency – NR
range bandwidth/2

NR_UL_high Maximum value of the NR uplink center

NR uplink frequency frequency + NR
range bandwidth/2

NR_DL_low Minimum value of the NR downlink center

NR downlink frequency frequency – NR
range bandwidth/2

NR_DL_high Maximum value of the NR downlink center

NR downlink frequency frequency + NR
range bandwidth/2

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.

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.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 63

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

4.1.4.2 Interference Avoidance Policies

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

Secondary Intermodulation Interference Avoidance

● Time-domain avoidance
In secondary intermodulation interference avoidance, the LTE side avoids NR
uplink control channels and data channels based on TDM.
As shown in Figure 4-6, the LTE FDD+NR TDD scenario is used as an example.
Assume that the slot configuration of NR TDD is DDDSU and the scheduling
unit is 0.5 ms. When LTE uplink subframes conflict with NR uplink subframes,
the LTE side does not perform uplink transmission. The time-domain
avoidance solution applies to scenarios with both LTE FDD and NR TDD.

Figure 4-6 TDM for intermodulation interference avoidance

NOTE

Intermodulation interference avoidance requires time synchronization between the LTE

and NR cells in NSA networking. The TDM function triggered by secondary
intermodulation interference uses the same TDM pattern selection policy as TDM
power control.
● Frequency-domain avoidance
If only some RBs in the LTE downlink frequency band experience secondary
intermodulation interference, the eNodeB preferentially allocates the RBs that
are not interfered by secondary intermodulation signals to UEs in the cell,
reducing the interference impact.

Secondary Harmonic Interference Avoidance

The eNodeB preferentially schedules the uplink RBs that do not cause interference
to NR downlink data channels and does not schedule the uplink RBs that cause
interference to NR downlink common channels (PBCH/common PDCCH).

4.1.4.3 Implementation of Interference Avoidance

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.

Secondary Intermodulation Interference Avoidance

● Time-domain avoidance
– On the NR side, if the CROSS_MDLT_INTRF_AVOID_SW option of the
NRDUCellAlgoSwitch.NsaDcAlgoSwitch parameter is selected, the

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 64

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

gNodeB determines the interference type as described in 4.1.4.1

Interference Type Identification. If the interference type is secondary
intermodulation interference, the NR side sends an LTE-NR joint
scheduling time sequence to the eNodeB through a pattern. This mode
requires that LTE FDD and NR TDD meet the time synchronization
requirements and relative frame offset constraints. When the
LNR_RELATIVE_FRM_OFS_ADAPT_SW option of the
gNodeBParam.NsaDcOptSwitch parameter is selected, the LTE side can
send its frame offset to the NR side, and the NR side calculates the
relative frame offset.
– On the LTE side, if the TDM_SWITCH option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is selected, the eNodeB
performs uplink and downlink scheduling based on the pattern received
from the gNodeB. When the LNR_RELATIVE_FRM_OFS_ADAPT_SW
option of the NsaDcAlgoParam.NsaDcAlgoSwitch parameter is selected,
the relative frame offset between LTE and NR can be automatically
obtained.
When secondary intermodulation interference avoidance in the time domain
is enabled, it is recommended that the
TDM_CHG_WITH_INTRA_CELL_HO_SW option of the
NsaDcAlgoParam.NsaDcAlgoSwitch parameter be selected. Under this
setting, an intra-MeNB-cell handover is triggered when there is a TDM status
change, ensuring that the TDM status of the MeNB is consistent with that of
the NSA UE. TDM status changes include TDM activation, TDM deactivation,
and TDM pattern change.
● Frequency-domain avoidance
If the INTERFERENCE_AVOID_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is selected and the
NsaDcMgmtConfig.ImdIntrfFreqAvoidanceType parameter is set to
PRIOR_ALLOC_NO_INTRF_RB, the eNodeB preferentially schedules the
downlink RBs that are not interfered by secondary intermodulation signals.
NOTE

● In scenarios with small-packet services or a small number of UEs, the eNodeB

preferentially schedules the downlink RBs that are not interfered by secondary
intermodulation signals. Therefore, interference with the downlink of LTE can be
avoided.
● In scenarios with large-packet services or a large number of UEs, UEs may occupy
all RBs. Therefore, the interference avoidance effect is not obvious.
● The gain of interference avoidance depends on the anti-interference capability of
the terminal. The better the anti-interference capability of the terminal, the lower
the gain.
● When nonstandard-bandwidth-related features (such as compact bandwidth,
flexible bandwidth, manual RB blocking, Horizontal SuperBAND, and spectrum
sharing) are enabled on the LTE side, the interference avoidance effect is not
obvious in multi-user scenarios.

Secondary Harmonic Interference Avoidance

● Avoiding NR common channels
– On the NR side, if the HARMONIC_INTRF_AVOID_SW option of the
NRDUCellAlgoSwitch.NsaDcAlgoSwitch parameter is selected and the
NRDUCellNsaDcConfig.HarmonicIntrfAvoidRange parameter is set to

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 65

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NR_DL_COMMON_CHANNEL, the interference type is determined as

described in 4.1.4.1 Interference Type Identification. If the interference
type is secondary harmonic interference, the gNodeB sends the time-
frequency positions of NR downlink common channels to the eNodeB
through a pattern.
– On the LTE side, if the INTERFERENCE_AVOID_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is selected and the
NsaDcMgmtConfig.HarmonicIntrfAvoidRange parameter is set to
NR_DL_COMMON_CHANNEL, the eNodeB does not schedule the RBs
indicated by the pattern received from the gNodeB.
● Avoiding both NR common channels and data channels
– On the NR side, if the HARMONIC_INTRF_AVOID_SW option of the
NRDUCellAlgoSwitch.NsaDcAlgoSwitch parameter is selected and the
NRDUCellNsaDcConfig.HarmonicIntrfAvoidRange parameter is set to
NR_DL_COMMON_AND_DATA_CHANNEL, the gNodeB sends the time-
frequency positions of NR downlink common channels to the eNodeB
through a pattern and preferentially schedules the downlink RBs that are
not interfered by LTE secondary harmonic signals.
– On the LTE side, if the INTERFERENCE_AVOID_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter is selected and the
NsaDcMgmtConfig.HarmonicIntrfAvoidRange parameter is set to
NR_DL_COMMON_AND_DATA_CHANNEL, the eNodeB does not
schedule the RBs indicated by the pattern received from the gNodeB and
preferentially schedules the uplink RBs that do not cause secondary
harmonic interference to the downlink of NR.
NOTE

● In scenarios with small-packet services or a small number of UEs, the gNodeB

preferentially schedules the downlink RBs that are not interfered by secondary harmonic
signals, and the eNodeB preferentially schedules the uplink RBs that do not cause
secondary harmonic interference to the downlink of NR. Therefore, interference with the
downlink of NR can be avoided.
● In scenarios with large-packet services or a large number of UEs, UEs may occupy all
RBs. Therefore, the interference avoidance effect is not obvious.

4.1.5 NSA DC Virtual Grid Models

Basic Principles
UEs with the same radio signal characteristics can be classified into a category
based on multi-dimensional measurements. The eNodeB considers the UEs with
the same RSRP measurement result on a frequency to be in the same virtual grid.
For example, if UE 1's measurement result on a frequency is [(Cell 1, RSRP 1),
(Cell 2, RSRP 2), ...] and UE 2's measurement result is the same, the eNodeB
considers the two UEs to be in the same virtual grid. The eNodeB uses machine
learning technology with virtual grids as features to construct a signal
characteristics mapping from all virtual grids in a cell to a frequency. This mapping
is contained in an entity called virtual grid model.

The eNodeB supports the building of LNR virtual grid models (only RSRP
prediction models) in NSA DC. After obtaining the virtual grid information of
a UE in an LTE cell, the eNodeB can query the RSRP prediction model for a

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 66

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

specific neighboring NR frequency to quickly predict the RSRP of the UE on

this frequency.
Functions related to virtual grid model building and application are controlled by
the following options of the LnrCarrierSelection.LnrCarrierSelectionSw
parameter:
● LNR_VIRTUAL_GRID_SW: If this option is selected, LNR virtual grid model
building is enabled.
● NSA_ANCHOR_VIRTUAL_GRID_SW: If this option is selected, NSA LTE anchor
virtual grid model building is enabled.
For details about LTE virtual grid models, see Multi-carrier Unified Scheduling in
eRAN feature documentation.
Functions related to virtual grid model building require a large number of main
control board resources. Different switches need to be turned on for different main
control boards:
● For the UMPTga, it is recommended that the
AI_ENHANCEMENT_OPT_SWITCH option of the
eNodeBResModeAlgo.ServiceMode parameter be selected.
● For the UMPTe, it is recommended that the
AI_ENHANCEMENT_OPT_SWITCH option of the
eNodeBResModeAlgo.ServiceMode parameter be selected.
● For the UMPTg, it is recommended that the
UMPTG_ENHANCEMENT_SWITCH option of the
eNodeBResModeAlgo.ServiceMode parameter be selected.

Virtual Grid Model Building and Update

Figure 4-7 illustrates how to build and update virtual grid models in NSA
scenarios.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 67

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-7 Process for building and updating virtual grid models

The building process is as follows:

1. The eNodeB determines the scope of LNR RSRP prediction models and uses
the format of [LTE cell, Neighboring NR frequency] to indicate the scope.
Virtual grid models are not built for the following cells:
– Cells with the Cell.MultiRruCellFlag parameter set to BOOLEAN_TRUE
– Cells with high speed mobility enabled
– Cells with ultra high speed mobility enabled
– eMTC-only cells
– FDD cells with a cell radius greater than 100 km
– FDD NB-IoT cells
– Cells with the Cell.WorkMode parameter set to DL_ONLY or LAA

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 68

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– Cells in a group with the PATTERN_ADJ_SWITCH option of the

SectorSplitGroup.SectorSplitSwitch parameter selected
– Cells having the same frequency as cells in a group with the
BEAM_NUM_ADJ_SWITCH option of the
SectorSplitGroup.SectorSplitSwitch parameter selected
Virtual grid models are not built for neighboring NR frequencies with the
VG_MODEL_FORBID_BUILD_FLAG option of the
NrNFreq.AggregationAttribute parameter selected.
If the VG_MDL_PRED_NCELL_ENH_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is selected and
virtual grid model building is triggered, the following neighboring NR cells
reported by UEs during data collection are identified as unknown neighboring
cells and included in model training:
– Neighboring NR cells with physical cell identifier (PCI) conflicts
– Neighboring NR cells not in the table of neighbor relationships with NR
If the number of virtual grid models to be built exceeds the specifications,
these models are prioritized based on the following rules, and then higher-
priority models are selected for building as long as the specifications allow.
– A larger cell bandwidth indicates a higher model building priority.
– A higher NSA anchoring priority indicates a higher model building
priority.
– A higher SCG frequency priority indicates a higher model building priority.
NSA LTE anchor virtual grid model building can also be enabled for cells with
LNR virtual grid model building enabled if the
NSA_ANCHOR_VIRTUAL_GRID_SW option of the
LnrCarrierSelection.LnrCarrierSelectionSw parameter is selected. The
building process is the same as that for LTE virtual grid models. For details,
see Multi-carrier Unified Scheduling in eRAN feature documentation.
NOTE

LTE and LNR virtual grid models share the same model specifications and are built
based on the feature activation sequence.
The virtual grid model specifications are as follows:
If an eNodeB serves S cells and each cell has N neighboring NR frequencies, a
total of S x N LNR RSRP prediction models are required.
– The eNodeB equipped with a UMPTga supports 90 LNR RSRP prediction
models if the AI_ENHANCEMENT_SWITCH or
AI_ENHANCEMENT_OPT_SWITCH option of the
eNodeBResModeAlgo.ServiceMode parameter is selected; otherwise, the
eNodeB supports 36 models.
– When equipped with a UMPTe:

▪ The eNodeB supports 90 LNR RSRP prediction models if the

AI_ENHANCEMENT_SWITCH option of the
eNodeBResModeAlgo.ServiceMode parameter is selected.

▪ The eNodeB supports 18 LNR RSRP prediction models if the

AI_ENHANCEMENT_OPT_SWITCH option of the
eNodeBResModeAlgo.ServiceMode parameter is selected in the
case of LN or GULN multimode scenarios.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 69

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

▪ If both of the preceding options are deselected, the eNodeB supports

36 LNR RSRP prediction models.
– The eNodeB equipped with a UMPTg supports 168 LNR RSRP prediction
models if the UMPTG_ENHANCEMENT_SWITCH option of the
eNodeBResModeAlgo.ServiceMode parameter is selected; otherwise, the
eNodeB supports 90 models.
2. The base station randomly selects 15 UEs (supporting EN-DC or SA) every 40s
in each cell for which models are to be built, and periodically collects their 24-
hour measurement reports about each frequency as the sample data of RSRP
prediction models.
3. After completing data collection, the base station starts model training and
calculates the accuracy of each model.
4. The base station evaluates whether each model can be used based on their
model accuracy. If the accuracy of an RSRP prediction model is greater than
or equal to 80%, the model has been built successfully and can be put into
service. Otherwise, the model has failed to be built and the building process
goes back to 2. If the building fails seven consecutive times, it can be tried
again 28 days later.
5. After completing the model building based on 24-hour data, the base station
randomly selects three UEs every 40s in each cell for which models are to be
built, collects 7x24-hour data, and builds new models. If a new model is more
accurate than the old one, the new one is put into use.
When the LNR_VIRTUAL_GRID_SW option of the
LnrCarrierSelection.LnrCarrierSelectionSw parameter is deselected, the eNodeB
stops the building and use of virtual grid models, and stores the models that have
been successfully built. These models can be stored for a maximum of seven days
if the eNodeB is not reset. They can be used again if this option is selected within
the seven days. They are no longer stored if the eNodeB is reset within the seven
days.
The process for monitoring the performance of virtual grid models and updating
models is as follows:
1. After a model is put into service, the eNodeB starts the model monitoring and
updating process. It performs 2 and 4 in parallel.
2. The base station monitors the success rate of PSCell additions based on
virtual grid models in real time and goes to 3.
3. If the success rate of PSCell additions based on a virtual grid model is less
than the value of LnrCarrierSelection.VgMdlKpiMonitorThld for two
consecutive hours, the base station suspends the use of this model, goes to 6
to rebuild a model, and uses the new one after the rebuilding succeeds.
4. The base station calculates the model accuracy every two days and goes to 5.
5. If the accuracy of a model is lower than expected, the base station considers
that this model is aged. It suspends the use of this model, goes to 6 to rebuild
a model, and uses the new one after the rebuilding succeeds.
6. The base station randomly selects three UEs every 40s in each cell for which
models are to be built and collects 7x24-hour data to rebuild models.
Running the RST APP command will delete the successfully built models if one of
the following options of the eNodeBResModeAlgo.ServiceMode parameter is

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 70

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

deselected: (1) AI_ENHANCEMENT_SWITCH for the UMPTe or UMPTga; (2)

AI_ENHANCEMENT_OPT_SWITCH for the UMPTe or UMPTga; (3)
UMPTG_ENHANCEMENT_SWITCH for the UMPTg.

4.1.6 Other Functions in NSA DC

4.1.6.1 NR Data Volume Reporting

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

Figure 4-8 NR data volume reporting from the RAN side

Uplink and downlink NR data volumes are reported on a per bearer basis. The
base station measures the number of bytes in SDU packets to calculate the air-
interface data volumes distributed to the NR side. It then reports the volumes
through the Secondary RAT Usage Report List IE in a Secondary RAT Data Usage
Report message or another message, as shown in Figure 4-8.

● In Option 3, the data split anchor is on the MeNB. Therefore, the MeNB
directly measures the data volumes distributed to the NR side and does not
require data volume reporting by the SgNB over the X2 interface. Then, the
MeNB directly reports the volumes to the MME on the core network.
● In Option 3x, the SgNB measures the air interface data volume distributed to
the NR side and notifies the MeNB through an X2 interface message. If the
LTE parameter NsaDcMgmtConfig.NrDataVolumeRptCfg is not set to 0, the
LTE side will report the NR data volumes notified by the NR side 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 NR data volume possibly has a deviation.
● In Option 3, the NsaDcMgmtConfig.NrDataVolumeRptCfg parameter on the
LTE side specifies whether NR data volumes are reported to the core network
based on events or at intervals.
– Event-triggered NR data volume reporting

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 71

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

If this parameter is set to 65535, the eNodeB reports NR data volumes

only based on events. After MCG split bearer setup, the eNodeB starts
timing and measures NR data volumes. Upon a bearer change or release,
the eNodeB records the end time, calculates the total data volumes
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 Request,
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 volumes not only based on events but also
based on the period specified by this parameter. That is, the eNodeB
periodically reports NR data volumes to the core network through the
Secondary RAT Data Usage Report message after the timing starts.
● In Option 3x, the NRCellNsaDcConfig.NrDataVolumeRptCfg parameter on
the NR side specifies whether NR data volumes are reported to the eNodeB
based on events or at intervals.
– Event-triggered NR data volume reporting
If this parameter is set to 65535, the gNodeB reports NR data volumes
based on events. After SCG split bearer setup, the gNodeB starts timing
and measures NR data volumes. 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 volumes distributed to the NR side, and reports the data
volumes to the eNodeB through the Secondary RAT Data Usage Report
message over the X2 interface. The eNodeB 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 Request, 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 volumes not only based on events but also
based on the period specified by this parameter. That is, the gNodeB
periodically reports NR data volumes 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 the eNodeB is required to report NR data volumes to the
MME, the NsaDcMgmtConfig.NrDataVolumeRptCfg parameter also needs
to be set to a value other than 0 on the LTE side. This parameter specifies
whether NR data volumes are reported to the MME, but does not specify
whether NR data volumes are reported based on events or at intervals.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 72

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

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:
● 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.
● 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 0.5s waiting period, the bearer path is not switched to the target
SgNB, and therefore the UE has no data volume on the target SgNB side. After the
timer expires, a bearer path change is triggered. NSA PCC anchoring cannot be
triggered when an RRC connection is reestablished on the LTE side.
If the UE has multiple E-RABs that use different data split bearers (MCG split bearer or
SCG split bearer), NR data volumes are reported on a per bearer basis according to the
methods specified in Option 3 and Option 3x, respectively.

4.1.6.2 S-KgNB Update

To improve security in data transmission in NSA DC, the security key S-KgNB at the
PDCP layer cannot remain unchanged. 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 over the X2 interface. Considering that there
may be UE compatibility issues, the SCG needs to be deleted first and an SCG is
added after a period of time. The time does not exceed the value of
NsaDcMgmtConfig.ScgAdditionInterval.

4.1.6.3 gNodeB and UE Signaling Exchange on SRB3

According to section 7.5 "SRB3" in 3GPP TS 37.340 V15.7.0, the gNodeB can
directly exchange eNodeB-unrelated signaling (such as intra-NR measurement
configuration or intra-NR resource configuration) with a UE on SRB3.
When the NSA_DC_SRB3_SWITCH option of the gNodeBParam.NsaDcOptSwitch
parameter is selected, SRB3 is supported. During an SgNB addition, the gNodeB
determines whether the UE supports SRB3 (that is, whether the UE-MRDC-
Capability IE reported by the UE contains SRB3 information). If the UE supports
SRB3, the gNodeB sends SRB3 configurations to the UE. After the configurations
are applied, the UE can send measurement reports directly to the gNodeB on
SRB3, as shown in Figure 4-9. The gNodeB can also directly send intra-NR
resource configurations to the UE through an RRC Reconfiguration message. If the
UE does not support SRB3, signaling cannot be directly exchanged between the
gNodeB and the UE; instead, signaling needs to be forwarded by the eNodeB.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 73

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-9 Signaling exchange on SRB3

During inter-SgNB PSCell change or SgNB release, the gNodeB directly deletes the
SRB3 configurations.

4.1.6.4 Uplink Single-Side Transmission (Trial)

This is a trial feature and applies only to LTE FDD and NR FDD frequency band
combinations.
NSA UEs can send data only on the LTE or NR side in some NSA DC frequency
band combinations, which requires adaptation on the network side. This feature
allocates uplink channel resources at the TTI level on the LTE and NR sides in TDM
mode, and implements uplink single-side transmission on the LTE or NR side
through TDM. This feature is similar to TDM power control described in EPC-based
NSA Performance Enhancement. The difference is the scenarios where TDM
patterns take effect. The eNodeB delivers a TDM pattern to the UE in the
following scenarios:
● SgNB addition: The frequency band of the PSCell of the SgNB and the
frequency band of the PCell of the MeNB must be an uplink single-side
transmission frequency band combination.
● SgNB or MeNB change: The frequency band combination of the PCell and
PSCell after the change must be an uplink single-side transmission frequency
band combination.
This feature is controlled by the TDM_SWITCH option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter on the LTE side and the
SINGLE_UL_NSA_SW option of the NRCellNsaDcConfig.NsaDcAlgoSwitch

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 74

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

parameter on the NR side. In addition, uplink single-side transmission frequency

band combinations need to be configured on the two sides.
● On the LTE side, use the NrScgFreqConfig.PccDlEarfcn and
NrScgFreqConfig.ScgDlArfcn parameters to specify EN-DC frequency
combinations that support only uplink single-side transmission (by converting
bands to frequencies), and select the SINGLE_UL_NSA_FLAG option of the
NrScgFreqConfig.AggregationAttribute parameter.
● On the NR side, use the gNBDedNsaDcBandComb.LteBandId and
gNBDedNsaDcBandComb.NrBandId parameters to specify EN-DC band
combinations that support only uplink single-side transmission, and select the
SINGLE_UL_NSA_FLAG option of the
gNBDedNsaDcBandComb.AggregationAttribute parameter.
When uplink single-side transmission is enabled, it is recommended that the
TDM_CHG_WITH_INTRA_CELL_HO_SW option of the
NsaDcAlgoParam.NsaDcAlgoSwitch parameter be selected. Under this setting,
an intra-MeNB-cell handover is triggered when there is a TDM status change,
ensuring that the TDM status of the MeNB is consistent with that of the NSA UE.
TDM status changes include TDM activation, TDM deactivation, and TDM pattern
change.
This feature requires that the radio frames and subframes of LTE and NR be
completely aligned. The alignment can be achieved by setting frame offsets in the
case of time synchronization.
● On the LTE side, use the CellFrameOffset.FrameOffset parameter to set a
frame offset.
● On the NR side, use the gNBFreqBandConfig.FrameOffset parameter to set
a frame offset.

NOTE

This feature requires time synchronization between the eNodeB and the gNodeB, with a
relative frame offset of 0 ms.
This feature requires that the NR cell parameter NRDUCellPrach.PrachConfigurationIndex
be set only to 1, 2, 5, 6, 9, 10, 13, 14, 17, 18, or 21.

With this feature, the network side selects a TDM pattern from Figure 4-10 and
Figure 4-11, and sends it to the UE. Based on the pattern, the UE performs uplink
single-side transmission in the time domain where LTE and NR subframes are
staggered in each TTI.

Figure 4-10 TDM pattern 1

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 75

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-11 TDM pattern 2

4.1.6.5 Uplink Preallocation

In a single mode (LTE or NR), uplink preallocation is triggered by downlink
packets. In NSA DC scenarios, if uplink and downlink data split modes are
inconsistent, preallocation on the LTE or NR side cannot be triggered, increasing
the end-to-end delay.
In NSA DC scenarios, this function increases the number of times that the base
station proactively schedules UEs to reduce the duration of uplink data packet
buffering on UEs, speed up the response to UE services, and improve user
experience. The following uses Option 3x as an example to describe the NSA
uplink preallocation procedure.

Figure 4-12 Uplink preallocation procedure in Option 3x

The NSA uplink preallocation shown in Figure 4-12 is described as follows:

(1) The NR PDCP determines whether to send uplink preallocation indications to
the LTE and NR sides based on the uplink and downlink packets transmitted on
the LTE and NR sides.
(2) The NR PDCP instructs the LTE and NR sides to enable uplink preallocation.
(3) The LTE MAC and NR MAC start uplink preallocation after receiving the uplink
preallocation instruction from the NR PDCP.
The related configuration is as follows:
● In Option 3, this function requires the selection of the
NSA_DC_PREALLOCATION_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter. This function also requires
the enabling of uplink smart preallocation on the LTE side and uplink
preallocation on the NR side.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 76

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● In Option 3x, this function requires the selection of both the

NSA_DC_PREALLOCATION_SW option of the
NRCellNsaDcConfig.NsaDcAlgoSwitch parameter and the
NSA_DC_PREALLOCATION_SW option of the
NsaDcMgmtConfig.NsaDcAlgoSwitch parameter. This function also requires
the enabling of uplink smart preallocation on the LTE side and uplink
preallocation on the NR side.
NOTE

● For sparse packets, the NSA uplink preallocation switch does not need to be turned on if
the following conditions are met: (1) uplink and downlink data is transmitted only on
the MCG side in Option 3 or only on the SCG side in Option 3x; (2) fallback to LTE and
uplink data transmission path selection are not enabled.
● For common packets, the NSA uplink preallocation switch does not need to be turned
on if the following conditions are met: (1) uplink and downlink data is transmitted only
on the MCG or SCG side, or downlink data is dynamically distributed and uplink data is
transmitted on the data split anchor side; (2) fallback to LTE and uplink data
transmission path selection are not enabled.

For details about uplink smart preallocation on the LTE side, see Uplink Scheduling
in eRAN feature documentation. For details about uplink preallocation on the NR
side, see Uplink Scheduling in 5G RAN feature documentation.
Table 4-8 lists the settings of the UE count threshold for NSA preallocation on the
LTE side and the NSA uplink preallocation switch and their results.

Table 4-8 Settings of the UE count threshold for NSA preallocation and the NSA
uplink preallocation switch and their results
UE Count Threshold for NSA Uplink Result
NSA Preallocation Preallocation
(NsaDcMgmtConfig.Nsa Switch
DcUePreUserCntThld) (NSA_DC_PREALL
OCATION_SW
option of
NsaDcMgmtConfi
g.NsaDcAlgoSwit
ch)
Not 0 On NSA uplink preallocation takes
effect. The number of UEs for
which the function takes effect
is limited by the
NsaDcMgmtConfig.NsaDcUeP
reUserCntThld parameter
setting.

0 On NSA uplink preallocation takes

effect.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 77

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

UE Count Threshold for NSA Uplink Result

NSA Preallocation Preallocation
(NsaDcMgmtConfig.Nsa Switch
DcUePreUserCntThld) (NSA_DC_PREALL
OCATION_SW
option of
NsaDcMgmtConfi
g.NsaDcAlgoSwit
ch)
Not 0 Off NSA uplink preallocation does
not take effect, but
preallocation for NSA UEs on
the LTE side takes effect. The
number of NSA UEs for which
preallocation takes effect is
limited by the
NsaDcMgmtConfig.NsaDcUeP
reUserCntThld parameter. For
details, see Uplink Scheduling
in eRAN feature
documentation.

0 Off Neither NSA uplink

preallocation nor preallocation
for NSA UEs on the LTE side
takes effect.

4.1.6.6 SCG Release and Addition Based on UE Overheating Status Reporting

This function supports SCG release and addition based on overheating messages
and overheating clearance messages reported by UEs to improve user experience
in NSA scenarios.
This function is controlled by the OVERHEATING_RPOTECTION_SW option of the
NsaDcAlgoParam.NsaDcAlgoSwitch parameter on the LTE side.
● After a UE detects an overheating state, it notifies the eNodeB by sending a
UEAssistanceInformation message with the OverheatingAssistance IE
containing the reducedMaxCCs field, which indicates the maximum number of
SCCs supported by the UE. Then, the eNodeB triggers an SCG release
procedure.
● After the UE is no longer in the overheating state, it notifies the eNodeB by
sending a UEAssistanceInformation message with the OverheatingAssistance
IE not containing the reducedMaxCCs field. After receiving the overheating
clearance indication, the eNodeB checks the interval between the overheating
clearance reporting time and the overheating reporting time.
– If the interval is greater than or equal to the
NsaDcMgmtConfig.ScgAdditionInterval parameter value, an SCG
addition procedure is triggered.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 78

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– If the interval is less than the NsaDcMgmtConfig.ScgAdditionInterval

parameter value, an SCG addition procedure is triggered only after the
interval reaches the parameter value.
After reporting an overheating message, the UE can report another overheating
message only after the penalty timer specified by the
RrcConnStateTimer.OverheatingIndProhibitTmr parameter expires.

4.1.6.7 Intra-Band EN-DC

Whether an EN-DC band combination supports intra-band EN-DC can be
configured, according to section 4.2.7.9 "MRDC-Parameters" in 3GPP TS 38.306
V16.1.0, as listed in Table 4-9.

Table 4-9 Intra-band EN-DC capabilities

UE Capability Reportinga Description

The UE reports an intraBandENDC- Supports intra-band EN-DC with only

Support IE with a value of "non- non-contiguous spectrum.
contiguous".

The UE does not report the Supports intra-band EN-DC with only
intraBandENDC-Support IE. contiguous spectrum.

The UE reports the intraBandENDC- Supports intra-band EN-DC with both

Support IE with a value of "both". contiguous and non-contiguous
spectrum.
NOTE
a: The preceding UE capabilities are reported at EN-DC band combination level.

When intra-band EN-DC is required, the eNodeB and the gNodeB determine
whether intra-band LTE and NR frequencies conflict with each other based on NSA
UE capabilities and base station configurations. The LnrFreqRelationship MO is
used to specify whether an LTE frequency and an NR frequency are intra-band
contiguous or intra-band non-contiguous. In addition, the
NSA_FREQ_CONFLICT_AVOID_SW option of the
gNodeBParam.NsaDcOptSwitch parameter on the NR side needs to be selected.
If intra-band LTE and NR frequencies conflict with each other, the eNodeB and the
gNodeB perform the following processing:
● eNodeB
– The eNodeB does not deliver measurement configurations for an NR
frequency that cannot coexist with the NSA anchor and does not add any
NR cell on this frequency as a PSCell.
– If the eNodeB detects that an LTE SCell cannot coexist with the added NR
SCG, it will remove the LTE SCell and will not deliver measurement
configurations for the frequency of this LTE SCell.
– If the target LTE cell for an inter-frequency handover conflicts with the
PSCell in the NR SCG, the eNodeB performs a handover with an SgNB
change.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 79

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● gNodeB
– The gNodeB does not add an NR cell that cannot coexist with the NSA
anchor as an SCell.
– The gNodeB does not select an NR cell that cannot coexist with the NSA
anchor as the target cell for an inter-frequency handover.
– If an NR SCell cannot coexist with the target cell for an LTE inter-
frequency handover, the gNodeB removes this SCell.
NOTE

Whether a UE supports inter-band EN-DC with contiguous spectrum is specified in an

interBandContiguousMRDC IE, according to section 4.2.7.9 "MRDC-Parameters" in 3GPP TS
38.306 V16.1.0. The LnrFreqRelationship MO can be used to configure whether an LTE
frequency and an NR frequency are inter-band contiguous. Based on the parameter settings
and UE capabilities, the eNodeB and the gNodeB determine whether the LTE and NR
frequencies can coexist. If not, the base stations perform the processing above.

If an LTE frequency and an NR frequency of a specified NR bandwidth overlap in

terms of frequency band, the LTE frequency, NR frequency and NR bandwidth can
be configured using the LnrFreqRelationship.DlEarfcn,
LnrFreqRelationship.NrDlArfcn and LnrFreqRelationship.NrDlBandwidth
parameters, respectively, and the OVERLAPPED option of the
LnrFreqRelationship.FreqRelationship parameter must be selected. Under these
settings, the base stations will determine that the two frequencies conflict with
each other for NSA DC and perform the previous processing.

NOTE

● If the frequency configured for an LTE cell is a multi-band frequency, this LTE frequency
is considered to conflict with an NR frequency if the OVERLAPPED option is selected for
the relationship between the primary or secondary frequency and the NR frequency. In
this case, the previous processing method is performed.
● It is recommended that the NR_SCG_BW_CHECK_OPT_SW option of the
NsaDcAlgoParam.NsaDcAlgoSwitch parameter be selected. If the UE capability
information does not include the channelBWs-UL or channelBWs-DL IE that specifies
the NR bandwidths supported by a UE, the eNodeB considers that the UE supports
bandwidths supported by each NR frequency band defined in section 5.3.5 in 3GPP TS
38.101-1 V15.7.0 and 3GPP TS 38.101-2 V15.7.0 by default when evaluating the NR cell
bandwidth during an NR SCG addition. In addition, if the NR cell bandwidth is 30 MHz
or 70 MHz, an NR SCG addition can be performed only when the UE supports the 30
MHz or 70 MHz bandwidth, respectively.

If an LTE frequency and an NR frequency with specified bandwidth 1 are intra-

band contiguous, the LTE frequency, NR frequency and NR bandwidth 1 can be
configured using the LnrFreqRelationship.DlEarfcn,
LnrFreqRelationship.NrDlArfcn and LnrFreqRelationship.NrDlBandwidth
parameters, respectively, and the LnrFreqRelationship.FreqRelationship
parameter must be set to INTRA_BAND_CONTIGUOUS. If at the same time this
LTE frequency and the same NR frequency with specified bandwidth 2 are intra-
band non-contiguous, the LTE frequency, NR frequency and NR bandwidth 2 can
be configured using the LnrFreqRelationship.DlEarfcn,
LnrFreqRelationship.NrDlArfcn and LnrFreqRelationship.NrDlBandwidth
parameters, respectively, and the LnrFreqRelationship.FreqRelationship
parameter must be set to INTRA_BAND_NON_CONTIGUOUS. If a UE does not
support intra-band contiguous EN-DC using the configured LTE frequency and the
NR frequency with specified NR bandwidth 1 or the UE does not support intra-

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 80

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

band non-contiguous EN-DC using the configured LTE frequency and the NR
frequency with specified NR bandwidth 2, set the
UeCompat.LnrFreqRelpWhitelist parameter to configure a function whitelist for
the UE and then associate this whitelist with the LnrFreqRelationship MO. That
is, set FREQ_RELATIONSHIP_ID_N of the UeCompat.LnrFreqRelpWhitelist
parameter to ON, where N is equal to the value of
LnrFreqRelationship.RelationshipId. In this way, the relationship between LTE
and NR frequencies is configured to take effect only for a certain type of NSA UE.
The gNodeB determines whether the UE supports each LTE-NR frequency
relationship configured on the eNodeB. The processing method is the same as
above.
Intra-band EN-DC requires that LTE and NR cells be deployed on the same site,
according to 3GPP TS38.201 V16.1.0.
On the LTE side, co-site intra-band combinations such as the NSA DC combination
of B3 and N3 can be configured when the CO_DEPLOYMENT_NSA_FLAG option
of the NrScgFreqConfig.AggregationAttribute parameter is selected. Co-site cell
pairs can be configured when the CO_DEPLOYMENT_NSA_FLAG option of the
NrNRelationship.AggregationAttribute parameter is selected.
If the LTE anchor cell frequency belongs to a band (for example, B3) in a co-site
intra-band combination, then:
● During an SCG addition by the MeNB, co-site cell filtering is performed based
on the measurement result and blind SCG addition procedure.
● During an intra-MeNB handover, an SgNB Modification Request message is
sent. Co-site cells are selected from the neighboring NR cells reported along
with LTE cell measurement results or from the blind-configurable neighboring
NR cells. (When the NsaDcLteMeasCtrlwithNbrMeasSw option of the
GlobalProcSwitch.ProtocolSupportSwitch parameter is selected, the MeNB
includes a reportAddNeighMeas IE in delivered LTE measurement
configurations and the NSA UE reports neighboring NR cell measurement
results along with LTE cell measurement results.) If there are qualified
neighboring NR cells, the SgNB side is notified and determines whether to
trigger an intra-SgNB cell change. If there are no qualified neighboring NR
cells and the source SgNB cell and the target MeNB cell are in the same co-
site intra-band combination but not in the same cell pair, the SCG is released.
● During an inter-MeNB handover, a Handover Request message is sent. If the
target MeNB cell and the source SgNB cell are not in the same cell pair, a
handover with an SgNB change is performed and the target MeNB
determines whether to add an SCG.
On the NR side, co-site cells need to be selected when the following conditions are
met: (1) an intra-frequency or inter-frequency cell change is required on the NR
side; (2) the frequency band (for example, band 3) of the LTE anchor cell belongs
to a co-site intra-band combination; (3) the SgNB receives a measurement report
from the UE. Co-site cells are selected from measurement cells based on the co-
site intra-band combinations and co-site cell pairs configured on the NR side.
On the NR side, co-site intra-band combinations can be configured when the
CO_DEPLOYMENT_NSA_FLAG option of the
gNBDedNsaDcBandComb.AggregationAttribute parameter is selected. Co-site
cell pairs can be configured when the CO_DEPLOYMENT_NSA_FLAG option of the
gNBNrLteCellComb.AggregationAttribute parameter is selected.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 81

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

A reported cell is filtered out if its frequency is in the NR band (for example, N3)
of a co-site intra-band combination but it is not in a co-site cell pair.

NOTE

If LTE+NR co-site intra-band combinations are configured on the NR side, it is

recommended that the band information of co-site external NR cells be specified by the
NRExternalNCell.FrequencyBand parameter so that the gNodeB can select target cells
based on the band information.

4.1.6.8 EN-DC Band Combination Blacklist Function

When some NSA UEs access certain EN-DC band combinations, UE performance
may deteriorate due to compatibility issues. In this case, the EN-DC band
combination blacklist function can be used to prohibit the use of specific LTE or
NR bands in certain EN-DC band combinations, improving user experience of NSA
UEs.

A blacklist can be configured by setting NSA_BAND_COMB_ID_N of the

UeCompat.NsaBandCombBlacklist1 or UeCompat.NsaBandCombBlacklist2
parameter. Specifically, set NSA_BAND_COMB_ID_N to On, where N is equal to
the value of PrivateCaBandComb.PrivateCaCombId. If this PrivateCaBandComb
MO is associated with the PrivateBand MO and if Bandwidth_0M of the
PrivateBand.CombBandBw parameter is set to On, the specified band cannot be
added to the EN-DC band combination associated with the PrivateCaBandComb
MO.

For example, an NSA UE reports an EN-DC band combination B3+B20+N41. If the

base station is not expected to configure this combination for the UE, perform the
following configurations. Set the UeCompat MO to blacklist this UE, set
NSA_BAND_COMB_ID_0 of the UeCompat.NsaBandCombBlacklist1 parameter
to On, and set the parameters in the PrivateBand MO associated with the band
combination whose PrivateCaBandComb.PrivateCaCombId parameter is set to 0,
by referring to the configurations below.

● Configure band 3 in the EN-DC band combination.

Parameter ID Parameter Value

PrivateBand.PrivateCaCombId 0

PrivateBand.CombBandIndex 1

PrivateBand.CombBandId 3

PrivateBand.BandType LTE

PrivateBand.CombBandBw Bandwidth_0M is not set to On.

● Configure band 20 in the EN-DC band combination.

Parameter ID Parameter Value

PrivateBand.PrivateCaCombId 0

PrivateBand.CombBandIndex 2

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 82

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter ID Parameter Value

PrivateBand.CombBandId 20

PrivateBand.BandType LTE

PrivateBand.CombBandBw Bandwidth_0M is not set to On.

● Configure N41 in the EN-DC band combination.

Parameter ID Parameter Value

PrivateBand.PrivateCaCombId 0

PrivateBand.CombBandIndex 3

PrivateBand.CombBandId 41

PrivateBand.BandType NR

PrivateBand.CombBandBw Bandwidth_0M is set to On and

other options are set to Off,
indicating that the band is not
allowed in this combination.

If an LTE frequency in EN-DC band combinations with a specified NR bandwidth

that include a certain NR frequency is not expected to be configured as an LTE
SCC, the LnrFreqRelationship MO can be set to prohibit this LTE frequency from
serving as an LTE SCC. To be specific, the LTE frequency, NR frequency and NR
bandwidth can be configured using the LnrFreqRelationship.DlEarfcn,
LnrFreqRelationship.NrDlArfcn and LnrFreqRelationship.NrDlBandwidth
parameters, respectively, and LnrFreqRelationship.FreqRelationship must be set
to SCC_AVOIDANCE. Under these settings, if this NR frequency exists in all
possible EN-DC band combinations, the configured LTE frequency will not be
added as an LTE SCC. The relationship between LTE and NR frequencies can be
configured to take effect only for a certain type of NSA UE. First, set the
UeCompat.LnrFreqRelpWhitelist parameter to configure a function whitelist for
the UE. Then, associate this whitelist with the LnrFreqRelationship MO, that is,
set FREQ_RELATIONSHIP_ID_N of the UeCompat.LnrFreqRelpWhitelist
parameter to On, where N is equal to the value of
LnrFreqRelationship.RelationshipId.
The NSA_FREQ_CONFLICT_AVOID_SW option of the
gNodeBParam.NsaDcOptSwitch parameter needs to be selected on the gNodeB
side. Under this setting, after the eNodeB receives information about the NR
PSCell and SCell frequencies in EN-DC band combinations from the gNodeB, the
eNodeB will determine whether to prohibit the addition of an NR cell as the
PSCell or an SCell if the NR cell conflicts with the LTE PCell.

4.1.6.9 RRC Connection Reestablishment Optimization for Defective NSA UEs

When the BWP actually used on an SCG frequency is modified (intra-base-station
scenarios), changed (inter-base-station scenarios), or added for a defective UE on
the network, the BWP bandwidth is strictly checked. If the BWP bandwidth is not a

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 83

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

3GPP-defined standard bandwidth, the defective UE will repeatedly trigger RRC

connection reestablishment. To address this issue, Huawei eNodeB supports RRC
connection reestablishment optimization for defective NSA UEs. When the
NSA_NR_CARRIER_FORBID_SW option of the
UeCompat.BlacklistControlExtSwitch2 parameter is selected and the defective
UEs are blacklisted, the eNodeB checks the causes of RRC connection
reestablishments for the blacklisted UEs. If an RRC connection reestablishment for
a blacklisted UE is caused by a modification, change, or addition of the BWP
actually used on an SCG frequency and the reestablishment cause is
reconfigurationFailure, a frequency that actually uses a non-protocol-defined BWP
cannot be added as an SCG frequency for the blacklisted UE.
When there are multiple configurable SCG frequencies on the network, the
NON_STANDARD_BWP_FLAG option of the
NrScgFreqConfig.AggregationAttribute parameter can be used to specify
whether the BWP actually used on an SCG frequency is a non-protocol-defined
BWP. When an RRC connection reestablishment is triggered for a blacklisted UE
because the BWP actually used on the SCG frequency is modified, changed, or
added, the eNodeB:
● Prohibits addition of a frequency with a non-protocol-defined BWP (the
frequency for which the NON_STANDARD_BWP_FLAG option is selected) as
an SCG frequency for the blacklisted UE.
● Allows addition of a frequency with a protocol-defined BWP (the frequency
for which the NON_STANDARD_BWP_FLAG option is deselected) as an SCG
frequency for the blacklisted UE.
The preceding differentiated processing makes it possible to configure SCG
frequencies for blacklisted UEs.
For more details about blacklist control, see Terminal Awareness Differentiation in
eRAN feature documentation.

4.1.6.10 Scheduling Protection Against the Impact of NR SRS Antenna

Switching on LTE Bands
If a UE is configured with an EN-DC combination (for example, a combination of
LTE 1800 MHz and NR 2600 MHz) and SRS antenna switching on the NR side
affects uplink transmission and downlink reception on the LTE side, then the
txSwitchImpactToRx and txSwitchWithAnotherBand IEs need to be included in the
UE capability information according to 3GPP TS 38.306.
Assume that the SRS_RES_CONFIG_TO_LTE_SW option of the
NRDUCellSrs.SrsAlgoExtSwitch parameter is selected on the NR side, the
NR_UL_ANT_SEL_OPT_SW option of the NsaDcAlgoParam.NsaDcAlgoExtSwitch
parameter is selected on the LTE side, and the gNodeB detects that SRS antenna
switching in the NR cell imposes an impact on the LTE band in the case of EN-DC.
Then, the gNodeB notifies the eNodeB of time-domain positions of SRS antenna
switching. After receiving the message, the eNodeB stops uplink and downlink
scheduling in the affected subframes. This reduces the bit error rate and increases
the uplink and downlink throughput on the LTE side.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 84

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

● The preceding function can be enabled only when time synchronization is achieved on
both LTE and NR sides.
● Uplink scheduling avoidance is not performed in the LTE cell if the SRS antenna
switching period in the NR cell exceeds 10 ms. Downlink scheduling avoidance is not
performed in the LTE cell if the SRS antenna switching period in the NR cell exceeds 40
ms.

4.1.6.11 NCGI Measurement Optimization in EN-DC

A UE uses the DRX mechanism by default when measuring the CGI of a
neighboring cell. Specifically, the base station configures a set of DRX parameters
for the UE, and the UE reads the CGI of the neighboring cell after entering the
DRX state. When an NSA UE measures CGIs on the NR side, the UE expects a long
sleep time on both the NR and LTE sides. Currently, DRX parameters are
configured separately on the NR and LTE sides for the NSA UE and take effect
independently. In this case, the NSA UE may not have enough common sleep time
for measuring CGIs on the NR side, and therefore cannot measure CGIs on the NR
side.
This function enables the NR and LTE sides to cooperate with each other when an
NSA UE performs CGI measurement on the NR side, maximizing the duration in
which the UE is in the common sleep time and increasing the probability of CGI
measurement by the UE. This function applies to synchronous networking
scenarios.
This function requires the following options to be selected:
● On the LTE side: NSA_NR_NCGI_DRX_OPT_SW option of the
EnodebAlgoExtSwitch.MultiNetworkingOptionOptSw parameter
● On the NR side: NSA_NCGI_MEAS_DRX_SW option of the
gNodeBParam.NsaDcOptSwitch parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 85

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-13 NCGI measurement procedure for NSA UEs

When the function is enabled on both sides and an NSA UE triggers a CGI
measurement on the NR side, the related procedure is as follows:
1. The gNodeB sends an SgNB Modification Required message to the eNodeB
over the X2 interface. This message contains the measurement configuration
with the measurement report type of "reportCGI", and the DRX parameters of
the UE for CGI measurement on the NR side.
2. If the UE is not performing VoIP services (QCI = 1/65/66) on the LTE side, the
eNodeB uses the DRX parameters sent from the gNodeB to trigger LTE DRX in
ANR scenarios.
3. The UE reads SIB1 of the corresponding cells based on the measurement
configuration and sends a measurement report containing the CGI-Info to the
gNodeB.
4. After receiving the measurement report containing the CGI information, the
gNodeB deletes the CGI measurement configuration and instructs the eNodeB
to cancel the CGI measurement.
5. After receiving the CGI measurement cancellation notification, the eNodeB
stops LTE DRX in ANR scenarios.

4.2 Network Analysis

4.2.1 Benefits
● Overall throughput of the entire network

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 86

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NSA DC does not directly affect network capacity. However, if the resources of
the network have not been used up, NSA DC can increase the resource
efficiency and throughput of the network.
● NSA UE throughput
If the resources of the network have not been used up, NSA DC can increase
the throughput of UEs.
● Overall PRB usage for the network
Most UE services on commercial networks are burst services, and there is a
very low probability that 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.
● Downlink real-time data split
In NR FDD scenarios, this function can fully utilize the air interface
transmission capabilities of LTE and NR to improve user experience of NSA
UEs.
● Uplink preallocation
This function increases the number of times the base station proactively
schedules UEs in NSA scenarios, shortens the duration of uplink data packet
buffering on the NSA UE, accelerates the response to UE services, and
improves user experience.
● Uplink fallback to LTE
After this function takes effect, the uplink data transmission of cell edge users
(CEUs) in the NR cell is switched to the LTE network, increasing the uplink
user-perceived rate of these UEs.
● Fast retransmission for downlink data split
This function reduces the impact of data overstock due to single-side rate
drop on the TCP sliding window and increases UE throughput.
● PSCell addition based on virtual grid models
For UEs in an area without NR coverage, this function reduces invalid gap-
assisted measurements for periodic SCG addition based on measurement. For
UEs moving from an area without NR coverage to an area with NR coverage,
this function can quickly detect NR coverage and add SCGs, increasing the 5G
online duration of these UEs.
● Uplink CA in EN-DC
This function allows an NSA UE to be configured with both an NR SCG and
LTE uplink CA, improving uplink experience of the UE at the cell center or at a
medium distance from the cell center.
● Preferential selection of a band combination with only one NR carrier for NSA
UEs
This function increases the throughput of NSA UEs when NR CA cannot be
performed.
● Differentiated SCG addition and deletion threshold configuration for NR CA-
capable UEs
This function allows differentiated configuration of NR FDD SCG addition and
deletion thresholds for NSA UEs that support NR FDD+TDD CA, increasing the
downlink user-perceived rate of these UEs.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 87

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

4.2.2 Impacts
Network Impacts
● If a UE is configured with NSA DC, the UE has one 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 performance
of data split in NSA DC. 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.
● In scenarios with a smaller LTE bandwidth and a higher load or with a larger
NR bandwidth and a lower load, it is more likely that the NSA DC rate is less
than the NR_ONLY rate.
● 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.
● Assume that the UE power saving function is triggered after an NSA UE
reports an SCGFailureInformationNR message in which the failureType-r15 IE
is set to t310-Expiry and the first ARFCN-ValueNR-r15 IE and first pci-r15 IE in
the measResultFreqListNR IE are both set to 0. Then, if the
SCG_REL_MEAS_OPT_SW option of the
EnodebCounterParaGrp.EnodebCounterAlgoSwitch parameter is selected
and the eNodeB releases the SCG after receiving that message, the release is
counted as a normal release. The L.NsaDc.MenbTrig.SgNB.NormRel counter
value will increase and the KPIs calculated based on this counter will also
change.
● After the function of SCG release and addition based on UE overheating
status reporting takes effect, the values of SgNB-release-related counters on
the LTE side will increase. Such counters include
L.NsaDc.MenbTrig.SgNB.Rel.UeException, L.NsaDc.SgNB.Rmv.Att, and
L.NsaDc.MenbTrig.SgNB.NormRel. The KPIs calculated based on the
preceding counters may also change.
● After downlink real-time data split takes effect in Option 3x, the data volume
on the LTE and NR sides changes, and the values of user-plane performance
indicators, such as the average MCS index, BLER, load, and average user-
perceived rate, may also change.
After downlink real-time data split takes effect in NR FDD scenarios where
UEs are evenly distributed, the data volume distributed from the NR PDCP to
the LTE side increases, that is, the value of the N.PDCP.Vol.DL.X2U.TrfPDU.Tx
counter increases.
– On the LTE side, there are increases in the downlink cell data volume, cell
throughput, PRB usage, and average MCS index.
– On the NR side, there are decreases in the downlink cell data volume, cell
throughput, PRB usage, and average MCS index.
● After downlink real-time data split, downlink dynamic data split stop, or fast
retransmission for downlink data split takes effect, there may be no new

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 88

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

packets or the number of new packets decreases on the NR side. As a result, a

timer cannot be updated based on the new packets and expires. A
retransmission is performed upon timer expiry. If the number of
retransmissions reaches 32, service drops occur. Therefore, after the preceding
functions take effect, the service drop rate may increase.
● Enabling uplink fallback to LTE has the following impacts on the network:
– The proportion of downlink traffic at the cell edge may increase as the
uplink data transmission performance at the cell edge improves. The
downlink data rates of NR UEs may decrease and the proportion of user
data distributed to the LTE side may increase as the proportion of
downlink traffic at the cell edge increases.
– The uplink data volume on the LTE side may increase as NR UEs running
uplink services at the cell edge fall back to LTE. In addition, the increase
in the number of LTE CEUs may decrease the LTE uplink rate and increase
the packet loss rate.
– The number of SgNB Modification Required messages sent by the NR
side increases, and the probability of procedure conflicts increases. As a
result, the SgNB modification success rate may decrease.
– The service drop rate on the LTE side may increase as the number of RRC
connection reconfiguration messages sent on the LTE side increases.
– The rate of abnormal SgNB releases triggered by the SgNB increases, but
the total rate of abnormal SgNB releases triggered by the MeNB and
SgNB decreases.
● Virtual grid model building and update require the selection of a certain
number of UEs for gap-assisted inter-frequency measurement. Therefore, the
uplink and downlink throughputs of these UEs decrease. In addition, the
number of SgNB Modification Request messages sent by the eNodeB to the
gNodeB increases, and the values of counters related to network interference
slightly change. As the number of selected UEs is small, the impact on the
average uplink and downlink throughputs of UEs is negligible when there are
more than 15 online UEs in a cell.
● Measurement reports need to be collected during virtual grid model building.
This may have the following network impacts:
– The number of signaling messages over the air interface may increase.
– The number of SRBs may increase.
– The average MCS index may decrease because small-index MCSs are used
for SRBs.
– The service drop rate may increase because RRC connection
reconfiguration messages may fail to be sent.
– The traffic volume may fluctuate because gap-assisted measurement may
cause fluctuations in channel quality measurement results.
● The CPU usage of the main control board increases when the eNodeB builds
virtual grid models and frequently queries virtual grid models.
● The building and query of virtual grid models consume more main control
board resources. When the number of UEs served by a base station is too
large, congestion may occur earlier. As a result, the RRC connection setup
success rate decreases and the service drop rate increases.
● If the required accuracy of LNR virtual grid models for SCG addition is set to a
value other than 100%, the model-based predictions can be used for blind

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 89

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

SCG addition. Indicators related to SCG addition may deteriorate in the

following scenarios:
– The blind SCG addition performance of certain UEs is poor.
– The eNodeB monitors and updates virtual grid models when the network
structure changes due to RF optimization or other reasons.
– The predicted RSRP values in some grids are inaccurate.
– Some UEs in power saving mode report the SCGFailureInformationNR
message to the MeNB.
● In DRX scenarios, the downlink packet transmission delay decreases when
NSA downlink data split optimization takes effect. If the uplink non-primary
path side enters the DRX sleep state, the data volume decreases on this side,
whereas the data volume (for example, L.Thrp.bits.DL.NsaDc,
N.PDCP.Vol.DL.X2U.TrfPDU.Tx, or N.ThpVol.DL) increases and the number of
active UEs (L.Traffic.ActiveUser.DL.Avg) decreases on the uplink primary
path side. After the data volume changes, the values of user-plane indicators
(such as the PRB usage, MCS index, or CQI) also change. For example, the
PRB usage and average MCS index decrease on the uplink non-primary path
side but increase on the uplink primary path side.
● In DRX scenarios, UEs are more likely to enter the DRX state as PSCell
addition based on virtual grid models will reduce inter-frequency
measurement configurations delivered by the base station to UEs. As a result,
the values of the L.Traffic.User.Cdrx.Avg and L.Cdrx.Active.TtiNum counters
will increase.
● If PSCell addition based on virtual grid models has been enabled on the
network, enabling measurement and penalty for SCG addition based on
virtual grids will increase the number of B1 measurement configurations
delivered by the eNodeB. If there are UEs that are incompatible with blind
SCG addition on the network, the NR data volume will increase.
● After NCGI measurement optimization in EN-DC takes effect, the throughput
of NSA UEs on the LTE side may decrease.
● Enabling SPID- or QCI-specific NSA PCC anchoring and PSCell management
policies has the following impacts on the network:
– The number of NSA DC PCC-anchoring-based handover preparation
attempts (indicated by L.NsaDC.PCCAnchor.HHO.PrepAttOut) decreases.
– If the FORBID_MEAS_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter is selected, the
number and total duration of inter-frequency measurements for NSA UEs
decrease. As a result, PCC anchoring to the frequency specified by
CellMultiCarrCfgGrp.DlArfcn cannot be triggered or the frequency
specified by CellMultiCarrCfgGrp.DlArfcn cannot be added as an SCG
frequency, and the UE throughput on the LTE and NR sides may decrease.
If this option is deselected, network performance is not affected.
– If the FORBID_BLIND_CFG_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter is selected, the
number and total duration of inter-frequency measurements for NSA UEs
increase. If this option is deselected, network performance is not affected.
– If the HIGH_LOAD_CELL_NSA_PCC_FLAG option of the
CellMultiCarrCfgGrp.AggregationAttribute parameter is selected, NSA
PCC anchoring to the frequency specified by

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 90

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

CellMultiCarrCfgGrp.DlArfcn is allowed only for UEs in high-load cells.

As a result, the load of the cell operating on this frequency decreases,
and the number of NSA UEs also decreases. If this option is deselected,
network performance is not affected.
● After SPID- or QCI-specific SCG addition at short intervals without considering
traffic volume is enabled, the duration in which UEs with the specified SPID or
QCI stay in the NSA DC state and the number of inter-RAT measurements
increase. Inter-RAT measurements decrease the user-perceived rate and
increase UE power consumption.

Function Impacts
RAT Function Function Reference Description
Name Switch

LTE Traffic model- DlPacketLen Downlink The throughput of LTE

based AwareSchSw Scheduling in UEs decreases, and
performance option of the eRAN feature the throughput of
optimization CellAlgoSwit documentatio NSA UEs increases.
ch.DlSchSwit n
ch parameter
LTE Downlink NonGbrBund Downlink The throughput of LTE
non-GBR lingSwitch Scheduling in UEs increases, and the
packet option of the eRAN feature throughput of NSA
bundling CellAlgoSwit documentatio UEs decreases.
ch.DlSchSwit n
ch parameter
LTE Delay-based QciPara.DlPd QoS The throughput of LTE
differentiated bForExtende Management UEs increases, and the
scheduling for dQci in eRAN throughput of NSA
extended feature UEs decreases.
QCIs documentatio
n

LTE Emergency None Emergency When a UE is

call Call in eRAN identified as an
feature emergency call UE, it
documentatio cannot perform NSA
n DC.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 91

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

LTE Breathing BreathingPilo Breathing After this feature is

Pilot tSwitch Pilot in eRAN enabled, the data
option of the feature volume of an NSA UE
CellDlschAlg documentatio may be lower than
o.BreathingPi n the downlink data
lotAlgoSwitc volume threshold for
h parameter large-packet services
and consequently the
NSA UE is identified
as a non-large-packet
UE. As a result, the
gains brought by this
feature are affected.

LTE Uplink FDD InterFddTddC Carrier ● When NSA DC

+TDD CA aSwitch Aggregation services are in
option of the in eRAN progress, uplink
CaMgtCfg.Ce feature FDD+TDD CA does
llCaAlgoSwit documentatio not take effect.
ch parameter n ● When uplink FDD
+TDD CA is in
progress, the uplink
secondary carrier
needs to be
removed if NSA DC
is required.

LTE ROHC CellAlgoSwit ROHC in This function is not

ch.RohcSwitc eRAN feature compatible with the
h documentatio MCG bearer, MCG
n split bearer, or SCG
split bearer. If such a
bearer is set up for an
NSA UE, the PDCP of
the bearer will be set
to NR PDCP
(according to 3GPP TS
38.323). However, if
ROHC-based services
(voice services or
TCP/IP data services)
are used, only the
bearer named
MCG_Bearer_EUTRA_P
DCP can be set up
and the PDCP of the
bearer must be set to
E-UTRA PDCP
(according to 3GPP TS
36.323).

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 92

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

LTE Turbo start PdcpRohcPar Video This function is not

video a.Profiles set Experience compatible with the
to Optimization MCG bearer, MCG
Profile0x000 in eRAN split bearer, or SCG
6 feature split bearer. If such a
documentatio bearer is set up for an
n NSA UE, the PDCP of
the bearer will be set
to NR PDCP
(according to 3GPP TS
38.323). However, if
ROHC-based services
(voice services or
TCP/IP data services)
are used, only the
bearer named
MCG_Bearer_EUTRA_P
DCP can be set up
and the PDCP of the
bearer must be set to
E-UTRA PDCP
(according to 3GPP TS
36.323).

LTE Super SuperCombC Super If an LTE cell has a

combined cell ellSwitch Combined larger coverage than
option of the Cell (FDD) in an NR cell, a UE that
CellAlgoSwit eRAN feature is in the LTE cell but
ch.SfnAlgoSw documentatio not in the NR cell
itch n cannot measure the
parameter NR cell.

LTE eMTC EMTC_SWITC eMTC in eMTC UEs do not

introduction H option of eRAN feature support NR.
the documentatio
CellEmtcAlgo n
.EmtcAlgoSw
itch
parameter

LTE In-band relay InBandRelay Relay in eRAN In-band relay requires

DeNbSwitch feature the support of Huawei
and documentatio customized UEs.
InBandRelay n Huawei customized
ReNbSwitch UEs supporting in-
options of the band relay do not
CellAlgoSwit support NSA DC.
ch.RelaySwit
ch parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 93

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

LTE VoLTE ENodeBAlgoS VoLTE in If an SCG is added for

witch.Eutran eRAN feature a UE running VoLTE
VoipSupportS documentatio services, the UE
witch n occupies power on the
NR side, which
decreases the
available power on
the LTE side and
affects the VoLTE
uplink coverage.

LTE System Sib24Switch Idle Mode If system information

information option of the Management broadcast is enabled
broadcast CellSiMap.SiS in eRAN together with EPC-
witch feature based NSA DC or NSA
parameter documentatio PCC anchoring, then
n the
CellSiMap.SibxPeriod
parameter (x = 2,
3, ...) must be greater
than or equal to 16
radio frames, the
CellSiMap.SibTransCt
rlSwitch parameter
must be set to OFF,
and the
CellSiMap.SiSchResR
atio parameter must
be set to 0. Under
other configurations,
NSA DC or NSA PCC
anchoring may fail.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 94

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

LTE Energy None Energy The accuracy of inter-

conservation Conservation frequency signal
and emission and Emission quality prediction
reduction Reduction in based on virtual grid
eRAN feature models decreases in
documentatio cells with energy
n conservation and
emission reduction
enabled. If a cell of a
base station is
blocked, data
collection about this
cell will be stopped in
all virtual grids of its
intra-base-station
intra-frequency cells
and data collection
about the frequency
of this cell will also be
stopped in the virtual
grids of the other
cells.

LTE Multi-carrier CellShutdow Energy Enabling multi-carrier

coordinated n.CellShutdo Conservation coordinated energy
energy saving wnSwitch set and Emission saving affects the
to Reduction in progress of virtual
ON_MULTI_C eRAN feature grid model building.
ARRIER_HIER documentatio
_SHUTDOWN n

LTE Smart carrier SMART_CARR Multi-carrier If LTE and LNR virtual

selection IER_SELECTI Unified grid models are built
based on ON_SW Scheduling in at the same time in a
virtual grids option of the eRAN feature cell, a UE chosen by
MultiCarrUnif documentatio both models for
iedSch.Multi n sampling randomly
CarrierUnifie selects one of the
dSchSw target frequencies for
parameter measurement. This
affects the building
duration.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 95

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

LTE AQM CellAlgoSwit AQM in eRAN This function does not

ch.AqmAlgoS feature take effect within 1s
witch documentatio after an SCG is
n released if real-time
data split is enabled in
downlink dynamic
data split mode in
Option 3x. This
reduces the
probability of
inappropriate packet
discard.

LTE Management NR_NFREQ_ ANR If measurement of a

of MEAS_MGMT Management neighboring frequency
neighboring _SW option in eRAN is disabled by setting
NG-RAN of the feature the corresponding
frequency CellAlgoExtS documentatio frequency
measurement witch.AnrOpt n measurement flag,
flags Switch the MeNB does not
parameter select this frequency
as a target frequency
for SCG addition.

LTE Uplink full- UL_COVERAG Massive After uplink full-

antenna E_BOOST_SW MIMO antenna reception
reception option of the Enhancement takes effect, the
SectorSplitGr s (FDD) in number of SgNB
oup.SectorSp eRAN feature releases triggered by
litSwitch documentatio LTE uplink coverage
parameter n may change because
uplink coverage on
the LTE side improves.
This affects PSCell
management for
VoLTE UEs.

LTE Prohibition of UE_REL_FOR None After prohibition of

IMMCI BID_IMMCI_F IMMCI delivery for
delivery for OR_MLB_SW MLB upon UE release
MLB upon UE option of the is enabled, the RRC
release CellQciPara. Connection Release
QciAlgoSwitc message does not
h parameter carry the IMMCI IE
when the UE enters
idle mode. As a result,
the PCC anchoring
procedure for NSA
UEs in idle mode does
not take effect.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 96

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

LTE NSA PCC NSA_PCC_AN EPC-based Differentiated SCG

anchoring CHORING_S NSA addition threshold
based on NR WITCH Performance configuration for NR
coverage option of the Enhancement CA-capable UEs has
NsaDcMgmt the following impacts
Config.NsaDc on NSA PCC
AlgoSwitch anchoring based on
parameter NR coverage for NSA
and UEs that support NR
NsaDcMgmt FDD+TDD CA:
Config.NsaDc The sum of the
PccAnchoring original effective RSRP
Policy set to threshold and the
BASED_ON_N offset specified by the
R_COVERAGE NrScgFreqConfig.CaU
eScgAddRsrpThldOff
set parameter is used
as the actual RSRP
threshold for event B1
to determine whether
an SCG can be added
with the candidate
target LTE cell during
PCC anchoring.

NR RAN sharing gNBSharing Multi- When both NSA

with common Mode.gNBM Operator networking based on
carrier ultiOpSharin Sharing in 5G EPC and RAN sharing
gMode RAN feature with common carrier
documentatio are enabled, data split
n is supported between
an E-UTRAN cell and
an NR cell only if they
belong to the same
operator.

NR RAN sharing gNBSharing Multi- When both NSA

with Mode.gNBM Operator networking based on
dedicated ultiOpSharin Sharing in 5G EPC and RAN sharing
carrier gMode RAN feature with dedicated carrier
documentatio are enabled, data split
n is supported between
an E-UTRAN cell and
an NR cell only if they
belong to the same
operator.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 97

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

NR Configuration HIGH_RELIAB URLLC in 5G Secondary harmonic

of low latency ILITY_BASIC_ RAN feature interference avoidance
and high SW option of documentatio does not take effect if
reliability the n it is enabled together
NRDUCellAlg with configuration of
oSwitch.High low latency and high
ReliabilitySw reliability.
itch
parameter

NR Downlink DL_INTRF_RA Downlink If both the NR

interference NDOM_SW Scheduling in frequency-domain
randomizatio option of the 5G RAN avoidance function for
n-based NRDUCellAlg feature secondary harmonic
scheduling oSwitch.Ada documentatio interference avoidance
ptiveEdgeExp n and the downlink
EnhSwitch interference
parameter randomization-based
scheduling function
are enabled, the
former does not take
effect.

NR Cell NRDUCell.Nr Cell In NSA networking, if

Combination DuCellNetwo Combination uplink fallback to LTE
rkingMode in 5G RAN is enabled in a
set to feature combined cell, the
HYPER_CELL_ documentatio number of fallbacks
COMBINE_M n to the LTE network
ODE and may decrease, and the
NRDUCellMu NR cell may serve
ltiTrp.DataTr more UEs in weak
ansMode set coverage areas. The
to increase in the
BASIC_MODE number of UEs in
or weak coverage areas
DPS_MODE may cause the uplink
and downlink cell
throughput to
decrease and the
service drop rate to
increase. To mitigate
this issue, it is
recommended that
the
NRDUCellSrsMeas.Ns
aUlFackToLteSinrThl
d parameter be set to
a larger value.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 98

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

NR Hyper Cell NRDUCell.Nr Hyper Cell in In NSA networking, if

DuCellNetwo 5G RAN uplink fallback to LTE
rkingMode feature is enabled in a hyper
set to documentatio cell, the number of
HYPER_CELL n fallbacks to the LTE
network may
decrease, and the NR
cell may serve more
UEs in weak coverage
areas. The increase in
the number of UEs in
weak coverage areas
may cause the uplink
and downlink cell
throughput to
decrease and the
service drop rate to
increase. To mitigate
this issue, it is
recommended that
the
NRDUCellSrsMeas.Ns
aUlFackToLteSinrThl
d parameter be set to
a larger value.

NR CCE-based CCE_BASED_S Multi- ● LTE side: CCE-

data split stop PLIT_STOP_S Frequency based data split
for NSA DC W option of Smart stop for NSA DC
UEs the Aggregation UEs takes effect
NRDUCellAlg in 5G RAN only when the
oSwitch.Nsa feature CellQciPara.NsaDc
DcAlgoSwitc documentatio DefaultBearerMod
h parameter n e parameter is set
to
SCG_SPLIT_BEARE
R.
● NR side: CCE-based
data split stop for
NSA DC UEs does
not take effect for
UEs for which the
gNBPdcpParamGr
oup.DlDataPdcpSp
litMode parameter
is set to
MCG_ONLY or
SCG_ONLY.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 99

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

NR CCE-based CCE_BASED_S Multi- It is recommended

data split stop PLIT_STOP_S Frequency that NSA uplink
for NSA DC W option of Smart preallocation also be
UEs the Aggregation enabled when CCE-
NRDUCellAlg in 5G RAN based data split stop
oSwitch.Nsa feature for NSA DC UEs and
DcAlgoSwitc documentatio uplink smart
h parameter n preallocation are both
enabled. When
NR Uplink smart UL_SMART_P Uplink downlink scheduling
preallocation REALLOCATI Scheduling in stops in the NR cell,
ON_SWITCH 5G RAN NSA uplink
option of the feature preallocation
NRDUCellPus documentatio increases the number
ch.UlPrealloc n of times UE data
ationSwitch packets are
parameter preallocated and
accelerates the
gNodeB's response to
UE services.

SRAN UL and DL NRDUCellAlg UL and DL If UL and DL

Decoupling oSwitch.UlDl Decoupling Decoupling is enabled
DecouplingS in an NR cell, uplink
witch fallback to LTE does
not take effect.

SRAN IP None IP If the IP PM function

performance Performance is abnormal, the base
monitoring 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.

SRAN LTE key event LTE_BIG_EVE LTE FDD and If LTE key event
assurance NT_ASSURA NR Dynamic assurance is enabled,
NCE_SW Spectrum uplink fallback to LTE
option of the Sharing does not take effect.
LteNrSpctShr
CellGrp.LteNr
SpctShrSwitc
h parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 100

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

SRAN UL CellRfShutdo Multi-RAT If UL coordinated

coordinated wn.MultiRatJ Coordinated channel shutdown is
channel ointChnShut Energy Saving enabled, sample
shutdown downSw collection for virtual
grid model building is
affected.

SRAN Uplink ● LTE: ● Uplink ● If the

preallocation PreAllocat Scheduling NsaDcMgmtConfi
ionSwitch in eRAN g.NsaDcUeMcgUlA
option of feature mbrRatio
the documenta parameter is set to
CellAlgoS tion 0, preallocation
witch.UlSc ● Uplink does not take
hSwitch Scheduling effect on the LTE
parameter in 5G RAN side.
● NR: feature ● If the
UL_BASIC_ documenta NsaDcMgmtConfi
PREALLOC tion g.NsaDcUeMcgUlA
ATION_S mbrRatio
WITCH parameter is set to
and 100, preallocation
UL_SMART does not take
_PREALLO effect on the NR
CATION_S side.
WITCH
options of
the
NRDUCell
Pusch.UlPr
eallocatio
nSwitch
parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 101

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

SRAN NSA carrier ● LTE: EPC-based After SPID-based SCG

combination NSA_LTE_F NSA frequency priority
selection DD_SEL_O Experience configuration is
based on user PT_SW or Improvement enabled, user-
experience NSA_LTE_T experience-based NSA
DD_SEL_O carrier combination
PT_SW selection does not
option of take effect for UEs
the with the specified
EnodebAlg SPIDs.
oExtSwitc
h.MultiNe
tworking
OptionOp
tSw
parameter
● NR:
NSA_LTE_S
EL_OPT_S
W option
of the
gNodeBPa
ram.Netw
orkingOpt
ionOptSw
parameter

SRAN DSS and NR ● LTE: LTE FDD and After refarming from
Flexible DSS_FLEX_ NR Dynamic spectrum sharing to
Refarming REFARM_S Spectrum NR, the number of
W option Sharing LTE frequencies
of the decreases by one and
Spectrum therefore the number
Cloud.Spe of NSA UEs may
ctrumClou decrease.
dEnhSwitc
h
parameter
● NR:
DSS_FLEX_
REFARM_S
W option
of the
NRDUCell
AlgoSwitc
h.Spectru
mCloudEn
hSwitch
parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 102

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

SRAN PC2 UE uplink ● LTE: EPC-based When PC2 UE uplink

NR power PC2_UE_N NSA NR power
configuration R_UL_PWR Performance configuration
maximization _CFG_MAX Enhancement maximization takes
_SW effect for PC2 UEs,
option of initial power control
the in NSA DC does not
NsaDcMg take effect.
mtConfig.
NsaDcAlg
oSwitch
parameter
● NR:
PC2_UE_N
R_UL_PWR
_CFG_MAX
_SW
option of
the
NRCellNsa
DcConfig.
NsaDcAlg
oSwitch
parameter

4.3 Requirements
4.3.1 Licenses
There are no license requirements for basic functions.
If a UE is configured with NSA DC, the UE has one RRC connection with the MeNB
and another RRC connection with the SgNB. Therefore, both LTE and NR sides
require an RRC Connected User license unit. The licensing principle for the number
of RRC_CONNECTED UEs on the LTE side in NSA networking is the same 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
UEs on the NR side, see License Management in 5G RAN feature documentation.
In Option 3, the eNodeB receives more data because of EN-DC data split.
Therefore, you need to apply for a license for eNodeB traffic on the LTE side. For
details, see License Management in eRAN feature documentation.

4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated, if there are any.
For detailed operations, see the relevant feature documents.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 103

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Prerequisite Functions
RAT Function Function Reference Description
Name Switch

LTE SRS resource SRSCfg.SrsCf Physical Uplink data

management gInd Channel transmission path
Resource selection in NSA
Management scenarios requires the
in eRAN following
feature configurations:
documentatio ● The
n SRSCfg.SrsCfgInd
parameter is set to
LTE High speed Cell.HighSpe High Speed
BOOLEAN_TRUE.
mobility edFlag Mobility in
eRAN feature ● The
documentatio Cell.HighSpeedFla
n g parameter is set
to LOW_SPEED.
LTE Mobility NsaDcAlgoPa NSA Mobility ● The
management ram.HoNsaB Management NsaDcAlgoParam.
in NSA DC andCombSel HoNsaBandCombS
ectPolicy electPolicy
parameter is set to
LTE_SCC_NR_SCG_
FIRST.

SRAN Uplink ● LTE: ● Uplink In Option 3 or Option

preallocation SmartPreA Scheduling 3x, NSA uplink
llocationS in eRAN preallocation requires
witch feature that both LTE uplink
option of documenta smart preallocation
the tion and NR uplink
CellAlgoS ● Uplink preallocation be
witch.UlSc Scheduling enabled.
hSwitch in 5G RAN
parameter feature
● NR: documenta
UL_SMAR tion
T_PREALL
OCATION_
SWITCH
option of
the
NRDUCell
Pusch.UlPr
eallocatio
nSwitch
parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 104

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

SRAN Delay-based NSA_RETRAN EPC-based If delay-based

retransmissio S_BASED_ON NSA Basics retransmission is
n _DELAY_SW enabled, fast
option of the retransmission for
gNodeBPara downlink data split
m.NsaDcOpt also needs to be
Switch enabled.
parameter

SRAN NSA downlink DRX_NSA_SP EPC-based In DRX scenarios, if

data split LIT_OPT_SW NSA Basics NSA downlink data
optimization option of the split optimization is
gNodeBPara enabled, fast
m.NsaDcOpt retransmission for
Switch downlink data split
parameter, or also needs to be
DRX_NSA_SP enabled.
LIT_OPT_SW
option of the
NsaDcAlgoPa
ram.NsaDcAl
goSwitch
parameter

SRAN NSA data split ● LTE: EPC-based If preferred path

rate NSA_SPLIT NSA Basics adaption in downlink
optimization _RATE_OP data split is enabled,
T_SW NSA data split rate
option of optimization also
the needs to be enabled.
NsaDcMg The RLC performs rate
mtConfig. estimation based on
NsaDcAlg the MAC scheduling
oExtSwitc capability and reports
h the RLC status to the
parameter PDCP more frequently.
● NR:
NSA_SPLIT
_RATE_OP
T_SW
option of
the
NRCellNsa
DcConfig.
NsaDcAlg
oSwitch
parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 105

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Mutually Exclusive Functions

RAT Function Function Reference Description
Name Switch

LTE Blind PSCell EPS_FALLBAC EPC-based The

addition for K_BLIND_SCG NSA NsaDcMgmtConfig.V
EPS fallback _ADD_SW Performance olteUeScgMgmtStrat
UEs option of the Enhancement egy parameter cannot
NsaDcMgmt be set to
Config.NsaDc VOLTE_PREFERRED if
AlgoExtSwitc blind PSCell addition
h parameter for EPS fallback UEs is
enabled.

LTE High speed Cell.HighSpe High Speed Virtual grids are not
mobility edFlag Mobility in built for high-speed
eRAN feature cells.
documentatio
n

LTE Ultra-low- INTER_ENB_ Multi-carrier Ultra-low-latency

latency ULTRA_LOW_ Unified scheduling for inter-
scheduling for LATENCY_SW Scheduling in eNodeB CA based on
inter-eNodeB option of the eRAN feature relaxed backhaul is
CA based on MultiCarrUnif documentatio not compatible with
relaxed iedSch.Multi n TDM.
backhaul CarrierUnifie
dSchEnSw
parameter

LTE NSA carrier NSA_LTE_FD EPC-based The preferential

combination D_SEL_OPT_S NSA selection of a band
selection W or Experience combination with only
based on user NSA_LTE_TD Improvement one NR carrier for
experience D_SEL_OPT_S NSA UEs function is
W option of not compatible with
the NSA carrier
EnodebAlgoE combination selection
xtSwitch.Mul based on user
tiNetworking experience.
OptionOptS
w parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 106

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

LTE NSA/SA LTE_FDD_NS NSA-SA The preferential

selection A_SA_DL_SEL Selection selection of a band
based on user _OPT_SW, Based on User combination with only
experience LTE_TDD_NS Experience one NR carrier for
A_SA_DL_SEL NSA UEs function is
_OPT_SW, or not compatible with
LTE_FDD_NS NSA/SA selection
A_SA_UL_SEL based on user
_OPT_SW experience.
option of the
EnodebAlgoE
xtSwitch.Mul
tiNetworking
OptionOptS
w parameter
LTE NSA carrier NSA_LTE_FD EPC-based The differentiated
combination D_SEL_OPT_S NSA SCG addition
selection W or Experience threshold
based on user NSA_LTE_TD Improvement configuration for NR
experience D_SEL_OPT_S CA-capable UEs
W option of function is not
the compatible with NSA
EnodebAlgoE carrier combination
xtSwitch.Mul selection based on
tiNetworking user experience.
OptionOptS
w parameter
LTE NSA/SA LTE_FDD_NS NSA-SA The differentiated
selection A_SA_DL_SEL Selection SCG addition
based on user _OPT_SW, Based on User threshold
experience LTE_TDD_NS Experience configuration for NR
A_SA_DL_SEL CA-capable UEs
_OPT_SW, or function is not
LTE_FDD_NS compatible with
A_SA_UL_SEL NSA/SA selection
_OPT_SW based on user
option of the experience.
EnodebAlgoE
xtSwitch.Mul
tiNetworking
OptionOptS
w parameter

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 107

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

RAT Function Function Reference Description

Name Switch

LTE PSCell NSA_CARRIE EPC-based The differentiated

addition R_SEL_WITH_ NSA Basics SCG addition
based on VG_SW threshold
virtual grid option of the configuration for NR
models LnrCarrierSel CA-capable UEs
ection.LnrCar function is not
rierSelection compatible with
Sw parameter PSCell addition based
on virtual grid models.

LTE Collaboration ROHC_NR_P None If the

between DCP_COLLAB ROHC_NR_PDCP_COL
ROHC and NR _SW option LAB_SW option of the
PDCP of the NsaDcMgmtConfig.N
NsaDcMgmt saDcAlgoExtSwitch
Config.NsaDc parameter is selected,
AlgoExtSwitc the
h parameter NSA_DC_CAPABILITY
_SWITCH option of
the
NsaDcMgmtConfig.N
saDcAlgoSwitch
parameter must be
deselected.

NR Extended Cell NRDUCell.Cel Extended Cell The Extended Cell

Range lRadius Range in 5G Range function is not
RAN feature compatible with
documentatio secondary
n intermodulation
interference avoidance
in the time domain.

NR Extended Cell NRDUCell.Cel Extended Cell The Extended Cell

Range lRadius Range in 5G Range function is not
RAN feature compatible with
documentatio uplink single-side
n transmission.

4.3.3 Hardware
Base Station Models
On the LTE side, the compatible base stations are as follows:
● 3900 and 5900 series base stations (macro base stations). 5900 series base
stations must be configured with the BBU5900, BBU5910, or BBU5900A.
● DBS3900 LampSite and DBS5900 LampSite
On the NR side, the compatible base stations are as follows:

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 108

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● 3900 and 5900 series base stations (macro base stations). 3900 series base
stations must be configured with the BBU3910, and 5900 series base stations
must be configured with the BBU5900, BBU5910, or BBU5900A.
● DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.

Boards
The compatible boards are listed below.
RAT Board Type Board Name Option 3 Option 3x

LTE Main control UMPTb Supported Supported

board

LTE Main control UMPTe Supported Supported

board

LTE Main control UMPTg Supported Supported

board

LTE Baseband All UBBP Supported Supported

processing boards
unit

LTE Integrated UMDU Supported Supported

board

NR Main control UMPTe Supported Supported

board

NR Main control UMPTg Supported Supported

board

NR Baseband UBBPg Supported Supported

processing
unit

NR Baseband UBBPfw1 Supported Supported

processing
unit

NOTE

LNR virtual grid model building requires that the main control board of the eNodeB be
UMPTe, UMPTga, or UMPTg series.

RF Modules
This function does not depend on RF modules.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 109

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

4.3.4 Networking
The following describes the networking scenarios and interconnection modes
supported by NSA DC.
● 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.
NOTE

IP transmission is recommended in co-site inter-subrack scenarios. If CI interconnection

is used, it is recommended that the same type of main control board (for example,
UMPTg) be configured for two subracks to ensure optimal performance.
The transmission path of LTE-NR user-plane data is specified by the
gNodeBParam.X2uTransmissionType parameter:
– If this parameter is set to ROUTING_TRANS, LTE-NR user-plane data is
transmitted through IP.
– 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.
– In co-site co-BBU scenarios, if this parameter is set to INTRA_TRANS,
LTE-NR user-plane data is transmitted through the backplane.
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.
● 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.
● LTE-NR separate-BBU separate-MPT
Figure 4-14 shows an NR base station using a BBU5900 or BBU5910 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 & 5900 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.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 110

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Figure 4-14 LTE-NR separate-BBU networking

● LTE-NR co-BBU separate-MPT and LTE-NR co-BBU co-MPT

As shown in Figure 4-15 and Figure 4-16, the LTE and NR base stations share
the same BBU5900 or BBU5910. They can use different main control boards
or share the same main control board.
– As shown in Figure 4-15, 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.

Figure 4-15 LTE-NR co-BBU separate-MPT networking

– As shown in Figure 4-16, X2 control-plane and user-plane data between

LTE and NR is exchanged within the UMPT.

Figure 4-16 LTE-NR co-BBU co-MPT networking

● IP transmission interconnection between LTE- and NR-only base stations

As shown in Figure 4-17, the NR base station uses a BBU5900 or BBU5910,
LTE and NR use different BBUs, and both NR and LTE base stations are single-
mode ones.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 111

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

X2 control-plane and user-plane data between LTE and NR is transmitted

through IP transmission interconnection.

Figure 4-17 Interconnection between LTE and NR

LTE Cloud BB and NR BBU

Figure 4-18 shows a newly deployed NR network using a BBU5900 (not a
BBU5910) and the existing LTE network using Cloud BB. In this scenario, only
transmission interconnection is supported.

Figure 4-18 LTE Cloud BB and NR BBU networking

4.3.5 Others
● 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.
– TDM-based intermodulation interference avoidance, uplink power
control, and uplink single-side transmission require the UE to support
TDM.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 112

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– Uplink dynamic data split requires the support from the UE.
● EPC requirements
– The EPC must be CloudEPC to 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 need to
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.
● Clock requirements
TDM requires time synchronization between LTE FDD and NR.

4.4 Operation and Maintenance

4.4.1 When to Use

It is recommended that this feature be enabled when operators require dual
connectivity with the eNodeB and gNodeB or service provisioning by the gNodeB.
For details about RAN sharing in NSA networking, see RAN Sharing in eRAN
feature documentation and Multi-Operator Sharing in 5G RAN feature
documentation.
PSCell addition based on virtual grid models is not recommended in the following
scenarios:
● High-speed mobility scenarios such as high-speed railway dedicated networks:
requiring the prevention of network performance deterioration because of
inaccurate NR coverage evaluation due to fast UE movement
● Big event assurance scenarios: requiring the prevention of network
performance deterioration caused by the increase in CPU usage when this
function is used
● Long-term network reconstruction scenarios: requiring the prevention of
network performance deterioration caused by the decrease in the accuracy of
virtual grid models

4.4.2 Data Configuration

4.4.2.1 Data Preparation

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side and the NRCellAlgoSwitch MO on the
NR side to configure NSA DC.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 113

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NSA DC LTE: Select the

Algorithm NsaDcMgmtConfig.NsaDcAlg NSA_DC_CAPABILITY_SWITC
Switch oSwitch H option.

NSA DC NR: The default value is ON.

Switch NRCellAlgoSwitch.NsaDcSwit
ch

The following table describes the parameters that must be set in the PccFreqCfg
MO on the LTE side to configure PCC frequencies (or anchor frequencies).

NOTE

This MO and the anchoring priority do not need to be configured for non-anchor
frequencies.

Parameter Parameter ID Setting Notes

Name

PCC DL PccFreqCfg.PccDlEarfcn Set this parameter based on

EARFCN the operator's network plan.

NSA PCC PccFreqCfg.NsaPccAnchoring Set this parameter based on

Anchoring Priority the network plan if an
Priority independent camping policy
needs to be configured for
NSA UEs.

NSA DC PCC PccFreqCfg.NsaDcPccA4RsrpT It is recommended that this

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

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

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 114

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

PCC DL NrScgFreqConfig.PccDlEarfcn Set this parameter based on

EARFCN the operator's network plan.

SCG DL NrScgFreqConfig.ScgDlArfcn Set this parameter based on

ARFCN the operator's network plan.

SCG DL NrScgFreqConfig.ScgDlArfcn Set this parameter based on

ARFCN Priority the operator's network plan.
Priority

NSA DC B1 NrScgFreqConfig.NsaDcB1Thl It is recommended that this

Event RSRP dRsrp parameter be set to a value
Threshold not less than the coverage-
based PSCell release threshold
or handover threshold on the
NR side. This prevents a PSCell
release or handover from
being triggered immediately
after an SgNB is added.

NR B1 Time NrScgFreqConfig.NrB1TimeT A smaller value of this

To Trigger oTrigger parameter results in earlier
event B1 reporting. A larger
value of this parameter results
in the opposite effect.

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

NOTE

The frequency bands and additional frequency bands configured for external NR cells on
the LTE side must be the same as those configured for the corresponding NR cells on the
NR side.

Parameter Parameter ID Setting Notes

Name

Downlink NrExternalCell.DlArfcn Set this parameter based on

ARFCN the 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

ID the operator's network plan.

Tracking Area NrExternalCell.Tac Set this parameter based on

Code the operator's network plan.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 115

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Frequency NrExternalCell.FrequencyBan Set this parameter based on

Band d the operator's network plan.

Additional NrExternalCell.AdditionalFre Set this parameter based on

Frequency quencyBand the operator's network plan.
Band

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

Parameter Parameter ID Setting Notes

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 operator's network plan.

SSB Period NrNFreq.SsbPeriod See 4.1.1.2.3 PSCell SMTC on

the LTE Side.

SSB Offset NrNFreq.SsbOffset See 4.1.1.2.3 PSCell SMTC on

the LTE Side.

SSB NrNFreq.SubcarrierSpacing Set this parameter to the

Subcarrier same value as the
Spacing NRDUCell.SubcarrierSpacing
parameter.

According to section 5.4.2.3 "Channel raster entries for each operating band" in
3GPP TS 38.104 V17.9.0, a frequency may belong to multiple NR frequency bands.
For such a frequency, a band needs to be configured on the eNodeB side. For
example, a neighboring NR frequency whose NR-ARFCN is in the range of
422000–434000 belongs to bands n1 and n66. The NrMfbiFreq MO on the
eNodeB side must be set based on the NR network plan, with this NR frequency
configured in band n1 or n66.
If a frequency does not belong to multiple NR frequency bands, the NR MFBI
parameters do not need to be set.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 116

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Downlink NrMfbiFreq.DlArfcn Set this parameter to the NR

ARFCN SSB frequency based on the
operator's network plan.

Frequency NrMfbiFreq.FrequencyBand Set this parameter based on

Band the operator's network plan.

Additional NrMfbiFreq.AdditionalFreque Set this parameter based on

Frequency ncyBand the operator's network plan.
Band

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

Parameter Parameter ID Setting Notes

Name

gNodeB ID NrNRelationship.GnodebId Set this parameter based on

the operator's network plan.

Local cell ID NrNRelationship.LocalCellId Set this parameter based on

the operator's network plan.

Blind NrNRelationship.BlindConfig It is recommended that this

Configuration Indicator parameter be set to TRUE if
Indicator the 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, there is
only one neighboring NR cell
with the same coverage as an
LTE cell. It is recommended
that only one neighboring NR
cell be configured on an NR
frequency. If multiple
neighboring NR cells are
configured on one NR
frequency, SgNB addition may
fail.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 117

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

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
NsaDcAlgoParam MO on the LTE side to configure the gap offset allocation
optimization switch.

Parameter Parameter ID Setting Notes

Name

NSA DC NsaDcAlgoParam.NsaDcAlgo Select the

Algorithm Switch GAP_OFS_ASSIGNMENT_OPT
Switch _SW option.

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side to configure periodic SCG addition based
on data volume.

Parameter Parameter ID Setting Notes

Name

SCG Addition NsaDcMgmtConfig.ScgAdditi The default value is 60. If NSA

Interval onInterval carrier combination selection
based on user experience is
not enabled and SCG addition
needs to be quickly triggered,
set this parameter to a smaller
value.

SCG Addition NsaDcMgmtConfig.ScgAdditi The default value is 0. It is

Buffer Length onBufferLenThld recommended that this
Threshold parameter be set to a value
greater than 0 to avoid
frequent SCG additions
triggered by small-packet
services.

SCG Addition NsaDcMgmtConfig.ScgAdditi The recommended value is 5.

Buffer Delay onBufferDelayThld
Threshold

The following table describes the parameters that must be set in the
EnodebAlgoExtSwitch and UeCompat MOs on the LTE side to configure the
preferential selection of a band combination with only one NR carrier for NSA UEs
function.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 118

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Multi EnodebAlgoExtSwitch.Multi Select the

Networking NetworkingOptionOptSw NSA_NR_SINGLE_BC_PREFER
Option Opt _SW option of this parameter
Switch if the preferential selection of
a band combination with only
one NR carrier for NSA UEs
function is required.

Whitelist UeCompat.WhitelistCtrlExtS- Select the

Control witch1 NSA_NR_SINGLE_BC_PREFER
Extension _SW option of this parameter
Switch 1 if the preferential selection of
a band combination with only
one NR carrier for NSA UEs
function needs to take effect
only for whitelisted UEs.

The following table describes the parameters that must be set in the
NsaDcAlgoParam and NrScgFreqConfig MOs on the LTE side to configure
differentiated SCG addition threshold configuration for NR CA-capable UEs.

Parameter Parameter ID Setting Notes

Name

NSA DC NsaDcAlgoParam.NsaDcAlgo Select the

Algorithm ExtSwitch SCG_ADD_B1_THLD_DIFF_SW
Extension option of this parameter if
Switch differentiated SCG addition
threshold configuration for NR
CA-capable UEs is required.

SCG Addition NrScgFreqConfig.CaUeScgAd Set this parameter based on

RSRP Thld dRsrpThldOffset the operator's network plan.
Offset for CA
UEs

The following table describes the parameters that must be set in the
NRCellNsaDcConfig MO on the NR side to configure differentiated SCG deletion
threshold configuration for NR CA-capable UEs.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 119

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

CA-capable NRCellNsaDcConfig.CaCapUe Set this parameter to a non-

UE PSCell A2 PscellA2RsrpThldOfs zero value based on the
RSRP Thld operator's network plan if
Offset differentiated SCG deletion
threshold configuration for NR
CA-capable UEs is required.

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

Parameter Parameter ID Setting Notes

Name

NSA DC LTE: Set this parameter based on

Default CellQciPara.NsaDcDefaultBe the operator's network plan.
Bearer Mode arerMode
Board LTE: The default parameter value is
Resource BRDRESASSIGNMENT.BRDAS MODE1. Set this parameter to
Assignment SIGNMENT MODE3 if the
Mode CellQciPara.NsaDcDefaultBe
arerMode parameter is set to
MCG_SPLIT_BEARER.
The change in the value of
this parameter may change
the transmission specifications
and signaling specifications of
the main control board.

Downlink NR: The value SCG_ONLY is

Data PDCP gNBPdcpParamGroup.DlData recommended.
Split Mode PdcpSplitMode

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side and the NRCellNsaDcConfig and
gNBPdcpParamGroup MOs on the NR side to support downlink real-time data
split in Option 3x.

Parameter Parameter ID Setting Notes

Name

NSA DC LTE: Select the

Algorithm NsaDcMgmtConfig.NsaDcAlg NSA_SPLIT_RATE_OPT_SW
Extension oExtSwitch option.
Switch

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 120

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NSA DC NR: Select the

Algorithm NRCellNsaDcConfig.NsaDcAl NSA_SPLIT_RATE_OPT_SW
Switch goSwitch option.

NSA DC NR: Select the

Optimization gNodeBParam.NsaDcOptSwit NSA_PDCP_SPLIT_OPT_SW
Switch ch option.

Downlink NR: The value SCG_AND_MCG is

Data PDCP gNBPdcpParamGroup.DlData recommended.
Split Mode PdcpSplitMode

The following table describes the parameters that must be set in the
NsaDcAlgoParam and NsaDcMgmtConfig MOs on the LTE side and the
NRCellNsaDcConfig MO on the NR side to enable downlink data split to be
resumed adaptively in Option 3.

Parameter Parameter ID Setting Notes

Name

NSA DC LTE: Select the

Algorithm NsaDcAlgoParam.NsaDcAlgo NSA_SPLIT_ADAPT_RECOVER
Switch Switch Y_SW option.

NSA DC LTE: Select the

Algorithm NsaDcMgmtConfig.NsaDcAlg NSA_SPLIT_RATE_OPT_SW
Extension oExtSwitch option.
Switch

NSA DC NR: Select the

Algorithm NRCellNsaDcConfig.NsaDcAl NSA_SPLIT_RATE_OPT_SW
Switch goSwitch option.

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side and the NRCellNsaDcConfig and
gNodeBParam MOs on the NR side to enable downlink data split to be resumed
adaptively in Option 3x.

Parameter Parameter ID Setting Notes

Name

NSA DC LTE: Select the

Algorithm NsaDcMgmtConfig.NsaDcAlg NSA_SPLIT_RATE_OPT_SW
Extension oExtSwitch option.
Switch

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 121

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NSA DC NR: Select the

Optimization gNodeBParam.NsaDcOptSwit NSA_SPLIT_ADAPT_RECOVER
Switch ch Y_SW option.

NSA DC NR: Select the

Algorithm NRCellNsaDcConfig.NsaDcAl NSA_SPLIT_RATE_OPT_SW
Switch goSwitch option.

The following table describes the parameters that must be set in the
NsaDcQciParamGroup MO on the LTE side and the gNBPdcpParamGroup MO on
the NR side to configure uplink data split modes.

Parameter Parameter ID Setting Notes

Name

Uplink Data LTE: The value INFINITY is

Split NsaDcQciParamGroup.UlDat recommended.
Threshold aSplitThreshold
Uplink Data LTE: The value SCG is
Split Primary NsaDcQciParamGroup.UlDat recommended.
Path aSplitPrimaryPath
Uplink Data NR: The value INFINITY is
Split gNBPdcpParamGroup.UlData recommended.
Threshold SplitThreshold
Uplink Data NR: The value SCG is
Split Primary gNBPdcpParamGroup.UlData recommended.
Path SplitPrimaryPath

NOTE

When uplink data is transmitted over the X2 link and 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
mode be set to MCG_ONLY in the Option 3 architecture and be set to SCG_ONLY in the
Option 3x architecture.

If the UE supports shortSN and the PDCP sequence numbers configured on the
LTE and NR sides are different, dedicated bearers with the same QCI fail to be set
up on the LTE and NR sides, and the default bearer will be released. It is
recommended that the PDCP sequence numbers be set to the same value on the
LTE and NR sides. For details about the shortSN, see section 4.2.4 "PDCP
Parameters" in 3GPP TS 38.306 V15.5.0.
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

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 122

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

transmission interruption caused by PDCP SN size insufficiency. The configuration

method is as follows:
● On the LTE side, the QciPara.NsaDcRlcPdcpParamGroupId parameter
specifies the ID of an RLC PDCP parameter group used in NSA DC scenarios.
Set the RlcPdcpParaGroup.AmPdcpSnSize parameter in the parameter group
to AmPdcpSnSize_18bits.
● On the NR side, set the gNBPdcpParamGroup.DlPdcpSnSize parameter to
BITS18(18).
The LTE and NR sides must be configured with the same RLC mode for bearers
with the same QCI. Otherwise, no SgNB can be added.
The following table describes the parameters that must be set in the
NRCellNsaDcConfig and NRDUCellSrsMeas MOs on the NR side to configure
uplink fallback to LTE.

Parameter Parameter ID Setting Notes

Name

NSA DC NRCellNsaDcConfig.NsaDcAl Select the

Algorithm goSwitch UL_FALLBACK_TO_LTE_SWITC
Switch H option.

NSA Uplink NRDUCellSrsMeas.NsaUlFack The value -30 is

Fallback to ToLteSinrThld recommended.
LTE SINR Thld

NSA Uplink NRDUCellSrsMeas.NsaUlFack The value 30 is recommended.

Fallback to ToLteSinrHyst
LTE SINR Hyst

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side to configure initial power control in NSA
DC.

Parameter Parameter ID Setting Notes

Name

NSA DC UE NsaDcMgmtConfig.NsaDcUe The value 20 is recommended.

MCG Uplink McgUlMaximumPower
Maximum
Power

NSA DC UE NsaDcMgmtConfig.NsaDcUe The value 20 is recommended.

SCG Uplink ScgUlMaximumPower
Maximum
Power

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side and the NRDUCellAlgoSwitch MO on
the NR side to configure interference avoidance.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 123

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NSA DC LTE: Select the

Algorithm NsaDcMgmtConfig.NsaDcAlg INTERFERENCE_AVOID_SW
Switch oSwitch and TDM_SWITCH options.

NSA DC NR: ● If the interference type is

Algorithm NRDUCellAlgoSwitch.NsaDc secondary intermodulation
Switch AlgoSwitch interference, select the
CROSS_MDLT_INTRF_AVOI
D_SW option.
● If the interference type is
secondary harmonic
interference, select the
HARMONIC_INTRF_AVOID
_SW option.

The following table describes the parameters that must be set in the
NRCellNsaDcConfig MO on the NR side to specify the NR data volume reporting
policy in Option 3x.

Parameter Parameter ID Setting Notes

Name

NR Data NRCellNsaDcConfig.NrDataV ● The recommended value is

Volume olumeRptCfg 65535 if NR data volume
Reporting reporting needs to be
Config triggered only by events.
● The recommended value is
600 if both event-based
triggering and periodic
triggering of NR data
volume reporting are
required.

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

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 124

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Upper Layer NsaDcMgmtConfig.UpperLay The value

Indication erIndicationSwitch NR_NCELL_BASED_BROADCA
Switch ST is recommended. If there
are UEs not supporting the
R15 upperLayerIndication IE in
the network, the value OFF is
recommended.

The following table describes the parameters that must be set in the CnOperator
MO on the LTE side to specify whether to broadcast the serving PLMN
upperLayerIndication IE in SIB2.

Parameter Parameter ID Setting Notes

Name

Operator CnOperator.OperatorFunSwi Set this parameter based on

Function tch the operator's network plan.
Switch

The following table describes the parameters that must be set in the
NRCellQciBearer MO on the NR side to add the AM or UM PDCP parameter
group ID for the corresponding QCI.

Parameter Parameter ID Setting Notes

Name

AM PDCP NRCellQciBearer.AmPdcpPar Set this parameter based on

Parameter amGroupId the operator's network plan.
Group ID

UM PDCP NRCellQciBearer.UmPdcpPar Set this parameter based on

Parameter amGroupId the operator's network plan.
Group ID

The following table describes the parameters that must set in the
gNBPdcpParamGroup MO on the NR side to specify the PDCP parameter group
ID.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 125

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

PDCP gNBPdcpParamGroup.PdcpPa Set this parameter based on

Parameter ramGroupId the value of
Group ID NRCellQciBearer.AmPdcpPar
amGroupId or
NRCellQciBearer.UmPdcpPar
amGroupId configured for the
corresponding QCI.

The following table describes the parameters that must be set in the
RlcPdcpParaGroup MO on the LTE side to allow SCG split bearer setup for GBR
services.

Parameter Parameter ID Setting Notes

Name

RLC-UM or RlcPdcpParaGroup.RlcMode Set this parameter based on

RLC-AM the QCI.
mode

AM Mode RlcPdcpParaGroup.AmPdcpS It is recommended that this

PDCP SN nSize parameter be set to
Length AmPdcpSnsize_18bits when
RlcPdcpParaGroup.RlcMode
is set to RlcMode_AM.

UM PDCP-SN RlcPdcpParaGroup.PdcpSnSiz It is recommended that this

size e parameter be set to
PdcpSnsize_18bits when
RlcPdcpParaGroup.RlcMode
is set to RlcMode_UM.

NOTE

In Option 3x, uplink or downlink data of GBR services can be transmitted only on the SCG
side.

The following table describes the parameters that must be set in the
NrExternalCell MO on the LTE side to configure the external NR cell networking
mode in NSA and SA hybrid networking.

Parameter Parameter ID Setting Notes

Name

NR NrExternalCell.NrNetworkin Set this parameter based on

Networking gOption the operator's network plan.
Option

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 126

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side to configure an adaptive PSCell
management policy for VoLTE UEs.

Parameter Parameter ID Setting Notes

Name

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

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

The following table describes the parameters that must be set in the
NsaDcAlgoParam MO on the LTE side to specify the maximum X2 transmission
rate for PDCP packets in Option 3.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 127

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

X2 NsaDcAlgoParam.X2TransMa ● The default value 1 is

Transmission xRate recommended to prevent
Max Rate the NR network from being
affected by excessively high
data rates allocated to the
NR side.
● When dynamic data split
requires the NR network to
support a larger air
interface capability, it is
recommended that this
parameter be set to a value
greater than the NR air
interface capability and the
final data transmission rate
is subject to the air
interface capability. If the
configured value of this
parameter is less than the
NR air interface capability,
the actual data
transmission rate is the
configured value of this
parameter.
● The value of this parameter
must be smaller than the
physical transmission
bandwidth.
● If this parameter is set to a
value far less than the NR
air interface capability, data
forwarding may take a long
time. If a handover occurs
during data forwarding,
packet loss occurs.

The following table describes the parameters that must be set in the
gNodeBParam MO on the NR side to configure the maximum X2 transmission
rate for PDCP packets when LTE-NR user-plane data is transmitted in Option 3x.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 128

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Max X2 gNodeBParam.MaxX2TransR ● The default value 1 is

Transmission ate recommended to prevent
Rate the LTE network from being
affected by excessively high
data rates allocated to the
LTE side.
● When dynamic data split
requires the LTE network to
support a larger air
interface capability, it is
recommended that this
parameter be set to a value
greater than the LTE air
interface capability and the
final data transmission rate
is subject to the air
interface capability. If the
configured value of this
parameter is less than the
LTE air interface capability,
the actual data
transmission rate is the
configured value of this
parameter.
● The value of this parameter
must be smaller than the
physical transmission
bandwidth.
● The default value of the
gNodeBParam.MaxX2Tran
sRate parameter is
100Mbits. Adjust the
parameter based on
transmission conditions
when enabling SN-
terminated MCG bearer
transmission.
● If this parameter is set to a
value far less than the NR
air interface capability, data
forwarding may take a long
time. If a handover occurs
during data forwarding,
packet loss occurs.

The following table describes the parameters that must be set in the
gNodeBParam MO on the NR side to configure the maximum X2 transmission

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 129

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

rate for PDCP packets when user-plane data is transmitted through the backplane
or cascading interface (CI) in Option 3x scenarios where LTE and NR are co-sited.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 130

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Intra-Site Max gNodeBParam.IntraSiteMaxX ● The default value of this

X2 2TransRate parameter is 0, indicating
Transmission that the maximum X2
Rate transmission rate for PDCP
packets is not configured
based on the transmission
path but determined by the
configured value of the
gNodeBParam.MaxX2Tran
sRate parameter.
● If this parameter is set to a
non-zero value, the
maximum X2 transmission
rate for PDCP packets is
configured based on the
transmission path.
– If LTE-NR user-plane
data is transmitted
through the backplane
or CI, the maximum X2
transmission rate for
PDCP packets is
determined by the
configured value of the
gNodeBParam.IntraSite
MaxX2TransRate
parameter.
– If LTE-NR user-plane
data is transmitted
through IP, the
maximum X2
transmission rate for
PDCP packets is
determined by the
configured value of the
gNodeBParam.MaxX2Tr
ansRate parameter.
● When dynamic data split
requires the LTE network to
support a larger air
interface capability, it is
recommended that this
parameter be set to a value
greater than the LTE air
interface capability. If the
configured value of this
parameter is less than the
LTE air interface capability,

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 131

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

the actual data

transmission rate is the
configured value of this
parameter.
● The value of this parameter
must be smaller than the
physical transmission
bandwidth.

The following table describes the parameters that must be set in the
gNodeBParam MO on the NR side to configure fast retransmission for downlink
data split.

Parameter Parameter ID Setting Notes

Name

NSA DC gNodeBParam.NsaDcOptSwit Select the

Optimization ch NSA_DC_FAST_RETRANS_SWI
Switch TCH option.

The following table describes the parameters that must be set in the
NrScgFreqConfig MO on the LTE side and the gNBDedNsaDcBandComb and
NRCellNsaDcConfig MOs on the NR side to configure uplink single-side
transmission frequency band combinations.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 132

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Frame Offset LTE: ● If the

or FDD Frame CellFrameOffset.FrameOffset CellFrameOffset.FrameOff
Offset or set parameter is set, the
ENodeBFrameOffset.FddFra frame offset is determined
meOffset by this parameter.
● If the
CellFrameOffset.FrameOff
set parameter is not set,
the frame offset is
determined by the
ENodeBFrameOffset.FddFr
ameOffset parameter.
● The frame offset is 0 ms in
time synchronization
scenarios if neither of the
preceding parameters is
set.
● The parameter value must
be the same as that
configured on the NR side.

PCC DL LTE: Set this parameter based on

EARFCN NrScgFreqConfig.PccDlEarfcn the operator's network plan.

SCG DL LTE: Set this parameter based on

ARFCN NrScgFreqConfig.ScgDlArfcn the operator's network plan.

Aggregation LTE: Set this parameter to

Attribute NrScgFreqConfig.Aggregatio SINGLE_UL_NSA_FLAG.
nAttribute
NSA DC LTE: Select the TDM_SWITCH
Algorithm NsaDcMgmtConfig.NsaDcAlg option.
Switch oSwitch
Frame Offset NR: The frame offset is 0 ms in
gNBFreqBandConfig.FrameOf time synchronization scenarios
fset if this parameter is not set.
The frame offset on the NR
side must be the same as that
on the LTE side.

LTE Band ID NR: gNBDedNsaDcBand- Set this parameter based on

Comb.LteBandId the operator's network plan.

NR Band ID NR: gNBDedNsaDcBand- Set this parameter based on

Comb.NrBandId the operator's network plan.

Aggregation NR: gNBDedNsaDcBand- Set this parameter to

Attribute Comb.AggregationAttribute SINGLE_UL_NSA_FLAG.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 133

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NSA DC NR: Select the

Algorithm NRCellNsaDcConfig.NsaDcAl SINGLE_UL_NSA_SW option.
Switch goSwitch

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side to configure NSA uplink preallocation in
Option 3.

Parameter Parameter ID Setting Notes

Name

NSA DC NsaDcMgmtConfig.NsaDcAlg Select the

Algorithm oSwitch NSA_DC_PREALLOCATION_S
Switch W option.

The following table describes the parameters that must be set in the
NsaDcMgmtConfig MO on the LTE side and the NRCellNsaDcConfig MO on the
NR side to configure NSA uplink preallocation in Option 3x.

Parameter Parameter ID Setting Notes

Name

NSA DC LTE: Select the

Algorithm NsaDcMgmtConfig.NsaDcAlg NSA_DC_PREALLOCATION_S
Switch oSwitch W option.

NSA DC NR: Select the

Algorithm NRCellNsaDcConfig.NsaDcAl NSA_DC_PREALLOCATION_S
Switch goSwitch W option.

(Optional) The following table describes the parameters that must be set in the
NrScgFreqConfig MO on the LTE side to configure an LTE+NR intra-band
combination.

Parameter Parameter ID Setting Notes

Name

PCC DL NrScgFreqConfig.PccDlEarfcn Set this parameter based on

EARFCN the operator's network plan.

SCG DL NrScgFreqConfig.ScgDlArfcn Set this parameter based on

ARFCN the operator's network plan.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 134

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Aggregation NrScgFreqConfig.Aggregatio If the eNodeB PCC band (or a

Attribute nAttribute neighboring eNodeB PCC
band) and the downlink SCG
band have the same band
number (for example, B3 and
N3), it is recommended that
the
CO_DEPLOYMENT_NSA_FLAG
option of this parameter be
selected.

(Optional) The following table describes the parameters that must be set in the
NrNRelationship MO on the LTE side to configure a co-site intra-band pair of LTE
and NR cells.

Parameter Parameter ID Setting Notes

Name

gNodeB ID NrNRelationship.GnodebId Set this parameter based on

the operator's network plan.

Local cell ID NrNRelationship.LocalCellId Set this parameter based on

the operator's network plan.

Aggregation NrNRelationship.Aggregatio If the LTE cell and the

Attribute nAttribute neighboring NR cell are
deployed in the same band
(for example, B3 and N3) and
on the same site, it is
recommended that the
CO_DEPLOYMENT_NSA_FLAG
option of this parameter be
selected.

(Optional) The following table describes the parameters that must be set in the
gNBDedNsaDcBandComb MO on the NR side to configure an LTE+NR intra-band
combination.

Parameter Parameter ID Setting Notes

Name

LTE Band ID gNBDedNsaDcBand- Set this parameter based on

Comb.LteBandId the operator's network plan.

NR Band ID gNBDedNsaDcBand- Set this parameter based on

Comb.NrBandId the operator's network plan.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 135

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Aggregation gNBDedNsaDcBand- If the gNodeB band (or a

Attribute Comb.AggregationAttribute neighboring gNodeB band)
and the LTE anchor band are
the same (for example, B3 and
N3), it is recommended that
the
CO_DEPLOYMENT_NSA_FLAG
option of this parameter be
selected.

(Optional) The following table describes the parameters that must be set in the
gNBNrLteCellComb MO on the NR side to configure the CGIs of a co-site intra-
band pair of LTE and NR cells.

Parameter Parameter ID Setting Notes

Name

NR MCC gNBNrLteCellComb.Mcc Set this parameter based on

the operator's network plan.

NR MNC gNBNrLteCellComb.Mnc Set this parameter based on

the operator's network plan.

gNodeB ID gNBNrLteCellComb.gNodeBI Set this parameter based on

d the operator's network plan.

Cell ID gNBNrLteCellComb.CellId Set this parameter based on

the operator's network plan.

LTE MCC gNBNrLteCellComb.LteMcc Set this parameter based on

the operator's network plan.

LTE MNC gNBNrLteCellComb.LteMnc Set this parameter based on

the operator's network plan.

eNodeB ID gNBNrLteCellComb.eNodeBI Set this parameter based on

d the operator's network plan.

LTE Cell ID gNBNrLteCellComb.LteCellId Set this parameter based on

the operator's network plan.

Aggregation gNBNrLteCellComb.Aggregat If the LTE cell and the

Attribute ionAttribute neighboring NR cell are
deployed in the same band
(for example, B3 and N3) and
on the same site, it is
recommended that the
CO_DEPLOYMENT_NSA_FLAG
option of this parameter be
selected.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 136

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

The following table describes the parameters that must be set in the
NRCellNsaDcConfig and NRCellNsaDcConfigGrp MOs on the NR side to
configure SgNB release based on RSRP or SSB SINR.

Parameter Parameter ID Setting Notes

Name

PSCell A2 NRCellNsaDcConfig.PscellA2 It is recommended that this

RSRP RsrpThld parameter be set to a value
Threshold less than the NSA DC event B1
RSRP threshold on the LTE side
to prevent PSCell addition
from being triggered
immediately after SgNB
release.

PSCell A2 NRCellNsaDcConfigGrp.Pscel It is recommended that the

RSRP Thld lA2RsrpThldOffset sum of
Offset NRCellNsaDcConfig.PscellA2
RsrpThld and
NRCellNsaDcConfigGrp.Pscel
lA2RsrpThldOffset be less
than the NSA DC event B1
RSRP threshold on the LTE side
to prevent PSCell addition
from being triggered
immediately after SgNB
release.

PSCell A2 NRCellNsaDcConfigGrp.Pscel A smaller value of this

Time To lA2TimeToTrig parameter results in earlier
Trigger event A2 reporting. A larger
value of this parameter results
in the opposite effect.

NSA DC NRCellNsaDcConfig.NsaDcAl Select the

Algorithm goSwitch SINR_BASED_SCG_RELEASE_S
Switch W option.

PSCell A2 NRCellNsaDcConfigGrp.Pscel A smaller value of this

SINR lA2SinrThld parameter results in a lower
Threshold probability of removing the
SCG of an NSA UE. A larger
value of this parameter results
in the opposite effect.

NOTE

The PSCell A2 hysteresis has a fixed value of 1 dB and it is unconfigurable.

(Optional) The following table describes the parameters that must be set in the
EnodebAlgoExtSwitch and gNodeBParam MOs for the MeNB to filter out
neighboring NR cells under any SgNB whose S1-U interface is unavailable in
Option 3x.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 137

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NSA DC EnodebAlgoExtSwitch.NsaDc Select the

Algorithm AlgoSwitch S1U_STATUS_BASED_SCG_AD
Switch D_SW option.

NSA DC gNodeBParam.NsaDcOptSwit Select the

Optimization ch S1U_STATUS_SEND_SW
Switch option.

(Optional) The following table describes the parameters that must be set in the
EnodebAlgoExtSwitch and NrExternalCell MOs on the LTE side and the
gNodeBParam MO on the NR side to configure SCG addition when LTE and NR
belong to different PLMNs.

Parameter Parameter ID Setting Notes

Name

NSA DC EnodebAlgoExtSwitch.NsaDc If the

Algorithm AlgoSwitch EQUIVALENT_PLMN_ADD_SC
Switch G_SW option is selected, the
MeNB can select NR
frequencies or NR cells based
on the equivalent PLMN
information delivered by the
core network.

NSA DC EnodebAlgoExtSwitch.NsaDc If the core network does not

Algorithm AlgoSwitch deliver equivalent PLMN
Switch information, it is
recommended that the
INTER_PLMN_ADD_SCG_SW
option be selected. Under this
setting, the MeNB can select
NR frequencies or NR cells
based on the inter-PLMN
handover list specified by the
InterPlmnHoList MO.

NSA DC gNodeBParam.NsaDcOptSwit If the

Optimization ch SCG_ADD_PLMN_SELECT_PO
Switch LICY_SW option is selected,
the SgNB performs admission
decision based on the Select
PLMN IE in the SgNB Addition
Request message.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 138

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Master PLMN NrExternalCell.MasterPlmnR Set this parameter to TRUE if

Reserved Flag eservedFlag the gNodeB serving an
external NR cell works in RAN
sharing with dedicated carrier
and the external cell belongs
to a secondary operator.

The following table describes the parameters that must be set in the
NsaDcAlgoParam and RrcConnStateTimer MOs on the LTE side to configure SCG
release and addition based on UE overheating status reporting.

Parameter Parameter ID Setting Notes

Name

NSA DC NsaDcAlgoParam.NsaDcAlgo Select the

Algorithm Switch OVERHEATING_RPOTECTION
Switch _SW option.

Overheating RrcConnStateTim- The value S120 is

Indication er.OverheatingIndProhi- recommended.
Prohibit Timer bitTmr

The following table describes the parameters that must be set in the
eNodeBResModeAlgo MO on the LTE side to set the service mode for the eNodeB
resource allocation algorithms.

Parameter Parameter ID Setting Notes

Name

Service Mode eNodeBResModeAl- ● If the main control board is

go.ServiceMode a UMPTg, select the
UMPTG_ENHANCEMENT_
SWITCH option.
● If the main control board is
a UMPTe or UMPTga, select
the
AI_ENHANCEMENT_OPT_S
WITCH option.

The following table describes the parameters that must be set in the
LnrCarrierSelection MO on the LTE side to configure functions related to NSA DC
virtual grid model building.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 139

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

LNR Carrier LnrCarrierSelec- Select the

Selection tion.LnrCarrierSelectionSw LNR_VIRTUAL_GRID_SW
Switch option to enable LNR virtual
grid model building.
Select the
NSA_ANCHOR_VIRTUAL_GRI
D_SW option to enable NSA
LTE anchor virtual grid model
building.

The following table describes the parameters that must be set in the
LnrCarrierSelection MO on the LTE side to configure PSCell addition based on
virtual grid models.

Parameter Parameter ID Setting Notes

Name

LNR Carrier LnrCarrierSelec- To enable PSCell addition

Selection tion.LnrCarrierSelectionSw based on virtual grid models,
Switch Select the
LNR_VIRTUAL_GRID_SW and
NSA_CARRIER_SEL_WITH_VG
_SW options to enable PSCell
addition based on virtual grid
models.
It is recommended that the
VG_SCG_ADD_MEAS_AND_P
UNISH_SW option be selected
if there are UEs that are
incompatible with blind SCG
addition on the network.

Intra-Freq LnrCarrierSelec- The value 320MS is

Measurement tion.IntraFreqMeasA3TimeTo recommended.
A3 Time-to- Trig
Trigger

Virtual Grid LnrCarrierSelec- The value

Mdl Pred NR tion.VgMdlPredNrScgMeasRs ACCURACY100_ENH is
SCG Meas rpThld recommended.
RSRP Thld

Virtual Grid LnrCarrierSelec- The value 95 is recommended.

Mdl KPI tion.VgMdlKpiMonitorThld
Monitor Thld

The following tables describe the parameters that must be set in the
LnrFreqRelationship, UeCompat, PrivateCaBandComb, and PrivateBand MOs

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 140

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

on the LTE side and the gNodeBParam MO on the NR side to configure the EN-
DC band combination blacklist function, prohibiting an EN-DC band combination
from being used or prohibiting a certain LTE frequency in any EN-DC band
combination that includes a certain NR frequency from serving as an LTE SCC.
● Prohibiting the use of an EN-DC band combination
Parameter Parameter ID Setting Notes
Name

NSA Band UeCompat.NsaBandCombBl Set

Combination acklist1 NSA_BAND_COMB_ID_N to
Blacklist 1 On, where N is equal to the
value of the
PrivateCaBandComb.Privat
eCaCombId parameter
associated with the EN-DC
band combination blacklist.

NSA Band UeCompat.NsaBandCombBl Set

Combination acklist2 NSA_BAND_COMB_ID_N to
Blacklist 2 On, where N is equal to the
value of the
PrivateCaBandComb.Privat
eCaCombId parameter
associated with the EN-DC
band combination blacklist.

Private CA PrivateCaBandComb.Privat Set this parameter based on

Band eCaCombId the operator's network plan.
Combination
ID

NSA Flag PrivateCaBandComb.NsaFla Set this parameter based on

g the operator's network plan.

Band Type PrivateBand.BandType Set this parameter based on

the operator's network plan.

Combination PrivateBand.CombBandBw For an NR band, select the

Band Bandwidth_0M option and
Bandwidth deselect the other options.

● Prohibiting a certain LTE frequency in any EN-DC band combination that

includes a certain NR frequency from serving as an LTE SCC

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 141

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

LTE-NR UeCompat.LnrFreqRelpWhi Set

Frequency telist FREQ_RELATIONSHIP_ID_N
Relationship to On, where N is equal to
Whitelist the value of the associated
LnrFreqRelation-
ship.RelationshipId
parameter.

Relationship LnrFreqRelation- The value of this parameter

ID ship.RelationshipId corresponds to N in the
UeCompat.LnrFreqRelpWhi
telist parameter's
FREQ_RELATIONSHIP_ID_N
that is set to On.

Downlink LnrFreqRelation- Set this parameter based on

EARFCN ship.DlEarfcn the operator's network plan.
The LTE frequency specified
by this parameter cannot
serve as an LTE SCC if it is in
an EN-DC combination that
includes a specified NR
frequency.

Downlink LnrFreqRelation- Set this parameter based on

NR-ARFCN ship.NrDlArfcn the operator's network plan.
The specified LTE frequency
cannot serve as an LTE SCC
if it is in an EN-DC
combination that includes
the NR frequency specified
by this parameter.

Frequency LnrFreqRelation- Set this parameter to

Relationship ship.FreqRelationship SCC_AVOIDANCE.

NSA DC gNodeBParam.NsaDcOptS Select the

Optimization witch NSA_FREQ_CONFLICT_AVO
Switch ID_SW option.

The following table describes the parameters that must be set in the UeCompat
and NrScgFreqConfig MOs on the LTE side to configure RRC connection
reestablishment optimization for defective NSA UEs.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 142

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Blacklist UeCompat.BlacklistContro- Configure the

Control lExtSwitch2 NSA_NR_CARRIER_FORBID_S
Extension W option based on the
Switch 2 network plan.

Aggregation NrScgFreqConfig.Aggregatio Configure the

Attribute nAttribute NON_STANDARD_BWP_FLAG
option based on the network
plan.

The following table describes the parameters that must be set to configure
preferred path adaption in downlink data split in Option 3.
Parameter Parameter ID Setting Notes
Name

Downlink LTE: The value

Data PDCP NsaDcQciParamGroup.DlDat ADAPT_PRIMARY_PATH is
Split Mode aPdcpSplitMode recommended.

NSA DC LTE: Select the

Algorithm NsaDcMgmtConfig.NsaDcAlg NSA_SPLIT_RATE_OPT_SW
Extension oExtSwitch option.
Switch

NSA DC NR: Select the

Algorithm NRCellNsaDcConfig.NsaDcAl NSA_SPLIT_RATE_OPT_SW
Switch goSwitch option.

The following table describes the parameters that must be set to configure
preferred path adaption in downlink data split in Option 3x.
Parameter Parameter ID Setting Notes
Name

Downlink NR: The value

Data PDCP gNBPdcpParamGroup.DlData ADAPT_PRIMARY_PATH is
Split Mode PdcpSplitMode recommended.

NSA DC LTE: Select the

Algorithm NsaDcMgmtConfig.NsaDcAlg NSA_SPLIT_RATE_OPT_SW
Extension oExtSwitch option.
Switch

NSA DC NR: Select the

Algorithm NRCellNsaDcConfig.NsaDcAl NSA_SPLIT_RATE_OPT_SW
Switch goSwitch option.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 143

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

The following table describes the parameters that must be set to configure NSA
downlink data split optimization in DRX scenarios.
Parameter Parameter ID Setting Notes
Name

NSA DC LTE: Select the

Algorithm NsaDcAlgoParam.NsaDcAlgo DRX_NSA_SPLIT_OPT_SW
Switch Switch option.

NSA DC NR: Select the

Optimization gNodeBParam.NsaDcOptSwit NSA_DC_FAST_RETRANS_SWI
Switch ch TCH option.

NSA DC NR: Select the

Optimization gNodeBParam.NsaDcOptSwit DRX_NSA_SPLIT_OPT_SW
Switch ch option.

The following table describes the parameters that must be set on the NR side for
SPID-based NSA uplink primary path configuration.

Parameter Parameter ID Setting Notes

Name

Uplink gNBRfspConfig.UlPrimaryPat ● It is recommended that the

Primary Path hSelMode uplink primary path
Selection selection mode be set to
Mode DEFAULT.
● The uplink primary path
can be set to MCG or SCG
as required.

Uplink Data gNBRfspConfig.UlDataSplitT ● If uplink data split is not

Split hreshold enabled, it is recommended
Threshold that the uplink data split
threshold be set to
INFINITY.
● If uplink data split is
enabled, it is recommended
that the uplink data split
threshold be set to
BYTE1600 or set as
required.

The following table describes the parameters that must be set for SPID-based SCG
frequency priority configuration on the LTE side.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 144

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NR SCG SPIDCFG.NrScgFreqPriority- Set this parameter to the

Frequency GroupId same value as the
Priority Group NrScgFreqPriGrp.NrScgFreqP
ID riorityGroupId parameter.
NR SCG NrScgFreqPriGrp.NrScgFreqP Set this parameter based on
Frequency riorityGroupId the operator's network plan.
Priority Group
ID

PCC DL NrScgFreqPriGrp.PccDlEarfcn Set this parameter based on

EARFCN the operator's network plan.

NR SCG DL NrScgFreqPriGrp.NrScgDlArf Set this parameter based on

ARFCN cn the operator's network plan.

NR SCG DL NrScgFreqPriGrp.NrScgDlArf Set this parameter based on

ARFCN cnPriority the operator's network plan.
Priority

The following table describes the parameters that must be set on the LTE side to
control operator-specific SCG frequency priority configuration.
Parameter Parameter ID Setting Notes
Name

NR SCG CnOperator.NrScgFreqPriori- Set this parameter to the

Frequency tyGroupId same value as the
Priority Group NrScgFreqPriGrp.NrScgFreqP
ID riorityGroupId parameter.
NR SCG NrScgFreqPriGrp.NrScgFreqP Set this parameter based on
Frequency riorityGroupId the operator's network plan.
Priority Group
ID

PCC DL NrScgFreqPriGrp.PccDlEarfcn Set this parameter based on

EARFCN the operator's network plan.

NR SCG DL NrScgFreqPriGrp.NrScgDlArf Set this parameter based on

ARFCN cn the operator's network plan.

NR SCG DL NrScgFreqPriGrp.NrScgDlArf Set this parameter based on

ARFCN cnPriority the operator's network plan.
Priority

The following table describes the parameters that must be set on the LTE side to
configure uplink CA in EN-DC.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 145

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NSA DC NsaDcMgmtConfig.NsaDcAlg To enable uplink CA in EN-DC,

Algorithm oExtSwitch select the
Extension NSA_LTE_UL_2CC_SW option.
Switch

(Optional) The following table describes the parameters that must be set on the
LTE side to configure SPID-specific NSA PCC anchoring and PSCell management
policies.

Parameter Parameter ID Setting Notes

Name

Multi-Carrier CellMultiCarrCfgGrp.MultiCa Set this parameter to a value

Config Group rrCfgGroupId ranging from 0 to 15 based on
ID the network plan.

Multi-Carrier SpidCfg.MultiCarrCfgGroupId Set this parameter to a value

Config Group ranging from 0 to 15 based on
ID the network plan. The value of
this parameter must be the
same as that of
CellMultiCarrCfgGrp.MultiCa
rrCfgGroupId.
CN Operator CellMultiCarrCfgGrp.CnOper Set this parameter to a value
ID atorId ranging from 0 to 5 based on
the network plan.

RAT Type CellMultiCarrCfgGrp.RatType Set this parameter to EUTRAN

or NR as required.

Downlink CellMultiCarrCfgGrp.DlArfcn Set this parameter based on

ARFCN the network plan.

NSA PCC CellMultiCarrCfgGrp.NsaPcc Set this parameter to a value

Anchoring AnchoringPriority ranging from 0 to 31 based on
Priority the network plan.

Aggregation CellMultiCarrCfgGrp.Aggreg Set this parameter based on

Attribute ationAttribute the network plan.

NR SCG CellMultiCarrCfgGrp.NrScgPr Set this parameter based on

Priority Offset iorityOffset the network plan.

NSA DC B1 CellMultiCarrCfgGrp.NsaDcB Set this parameter based on

RSRP 1RsrpThldOffset the network plan.
Threshold
Offset

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 146

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

DL PRB Usage NsaDcMgmtConfig.DlPrbThl Set this parameter based on

Thld for NSA dForNsaPccAnchor the network plan.
PCC Anchor

SPID SpidCfg.SpidAlgoSwitch Set the

Algorithm SPID_SHT_PRD_NO_TFC_SCG
Switch _ADD_SW option based on
the network plan.

Short-Period NsaDcMgmtConfig.ShortPrd Set this parameter based on

No-Traffic NoTfcScgAddIntvl the network plan.
SCG Add
Interval

(Optional) The following table describes the parameters that must be set on the
LTE side to configure QCI-specific NSA PCC anchoring and PSCell management
policies.

Parameter Parameter ID Setting Notes

Name

Multi-Carrier CellMultiCarrCfgGrp.MultiCa Set this parameter to a value

Config Group rrCfgGroupId ranging from 0 to 15 based on
ID the network plan.

Multi-Carrier QciPara.MultiCarrCfgGroupId Set this parameter to a value

Config Group ranging from 0 to 15 based on
ID the network plan. The value of
this parameter must be the
same as that of
CellMultiCarrCfgGrp.MultiCa
rrCfgGroupId.
CN Operator CellMultiCarrCfgGrp.CnOper Set this parameter to a value
ID atorId ranging from 0 to 5 based on
the network plan.

RAT Type CellMultiCarrCfgGrp.RatType Set this parameter to EUTRAN

or NR as required.

Downlink CellMultiCarrCfgGrp.DlArfcn Set this parameter based on

ARFCN the network plan.

NSA PCC CellMultiCarrCfgGrp.NsaPcc Set this parameter to a value

Anchoring AnchoringPriority ranging from 0 to 31 based on
Priority the network plan.

Aggregation CellMultiCarrCfgGrp.Aggreg Set this parameter based on

Attribute ationAttribute the network plan.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 147

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

NR SCG CellMultiCarrCfgGrp.NrScgPr Set this parameter based on

Priority Offset iorityOffset the network plan.

NSA DC B1 CellMultiCarrCfgGrp.NsaDcB Set this parameter based on

RSRP 1RsrpThldOffset the network plan.
Threshold
Offset

DL PRB Usage NsaDcMgmtConfig.DlPrbThl Set this parameter based on

Thld for NSA dForNsaPccAnchor the network plan.
PCC Anchor

QCI CellQciPara.QciAlgoSwitch Set the

Algorithm QCI_SHT_PRD_NO_TFC_SCG_
Switch ADD_SW option based on the
network plan.

Short-Period NsaDcMgmtConfig.ShortPrd Set this parameter based on

No-Traffic NoTfcScgAddIntvl the network plan.
SCG Add
Interval

(Optional) The following table describes the parameters that must be set on the
LTE side to configure NR FR2 frequency measurement in polling mode in NSA
mmWave networking.

Parameter Parameter ID Setting Notes

Name

Aggregation NrScgFreqConfig.Aggregatio Set the

Attribute nAttribute NR_FR2_MEAS_POLLING_FLA
G option based on the
network plan.
It is recommended that the
option settings be the same
for FR2 frequencies with
different
NrScgFreqConfig.PccDlEarfcn
values but with the same
NrScgFreqConfig.ScgDlArfcn
value.

(Optional) The following table describes the parameters that must be set to
configure blacklist control for SCC management in NSA networking on the LTE
side if there are abnormal UEs for which SCCs cannot be added together with
SCGs.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 148

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Parameter Parameter ID Setting Notes

Name

Blacklist UeCompat.BlacklistContro- Select the

Control lExtSwitch2 NSA_CA_FORBID_SW option if
Extension there are abnormal UEs for
Switch 2 which SCCs cannot be added
together with SCGs.

4.4.2.2 Using MML Commands

Before using MML commands, refer to 4.2.2 Impacts and 4.3 Requirements and
complete the parameter configurations for related functions based on the impact,
dependency, and mutually exclusive relationships between the functions, as well
as the actual network scenario. In addition, ensure that the license, hardware,
networking, and cell requirements are met.
Before using MML commands, confirm the related parameter modification
precautions by referring to the fields including "Service Interrupted After
Modification" and "Caution" for the corresponding parameters in the parameter
reference.

Activation Command Examples

NOTE

To enable or disable the main control board enhancement mode:

● If the main control board model has been determined, you are advised to select or
deselect the corresponding option.
● If the main control board model is unknown, you are advised to select or deselect both
the AI_ENHANCEMENT_SWITCH and UMPTG_ENHANCEMENT_SWITCH options. The
base station automatically identifies the main control board model and activates or
deactivates the enhancement mode of only the identified model.

On the eNodeB side

//Adding a neighboring NR frequency
ADD NRNFREQ: LocalCellId=21, DlArfcn=636666, UlArfcnConfigInd=NOT_CFG, SsbOffset=0,
SsbPeriod=20MS, SubcarrierSpacing=30KHZ;
//Specifying a frequency band and an additional frequency band for the neighboring NR frequency whose
NR-ARFCN falls within the range of 158200-160600, 285400-303400, 386000-398000, 402000-404000,
422000-434000, 514000-537999, 620000-653333, or 2054166-2084999.
//Setting the frequency band to which the neighboring NR frequency belongs
ADD NRMFBIFREQ: DlArfcn=636666, FrequencyBand=N77, AdditionalFrequencyBand=N78;
//Adding an external NR cell in multi-operator radio access network (MORAN) scenarios where cells are not
shared by operators
ADD NREXTERNALCELL: Mcc="262", Mnc="01", GnodebId=255, CellId=1, DlArfcn=636666,
UlArfcnConfigInd=NOT_CFG, PhyCellId=1, Tac=1, NrNetworkingOption=NSA, FrequencyBand=N77,
AdditionalFrequencyBand=N78, MasterPlmnReservedFlag=TRUE;
//Adding an external NR cell in non-MORAN scenarios
ADD NREXTERNALCELL: Mcc="262", Mnc="01", GnodebId=255, CellId=1, DlArfcn=636666,
UlArfcnConfigInd=NOT_CFG, PhyCellId=1, Tac=1, NrNetworkingOption=NSA, FrequencyBand=N77,
AdditionalFrequencyBand=N78;
//(Optional) Adding an additional PLMN ID for an external NR cell in sharing scenarios
ADD NREXTERNALCELLPLMN: Mcc="262", Mnc="01", GnodebId=255, CellId=1, SharedMcc="460",
SharedMnc="01", NrNetworkingOption=NSA;
//Adding a neighbor relationship with the NR cell
ADD NRNRELATIONSHIP: LocalCellId=21, Mcc="262", Mnc="01", GnodebId=255, CellId=1;

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 149

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

//Adding a PCC frequency

ADD PCCFREQCFG: PccDlEarfcn=1500;
//Adding an NR SCG frequency
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) Turning on the gap offset allocation optimization switch
MOD NSADCALGOPARAM: NsaDcAlgoSwitch=GAP_OFS_ASSIGNMENT_OPT_SW-1;
//(Optional) Modifying the period or data volume thresholds for periodic SCG addition
MOD NSADCMGMTCONFIG: LocalCellId=21, ScgAdditionInterval=60, ScgAdditionBufferLenThld=0,
ScgAdditionBufferDelayThld=5;
//(Optional) Enabling the preferential selection of a band combination with only one NR carrier for NSA
UEs function
MOD ENODEBALGOEXTSWITCH: MultiNetworkingOptionOptSw=NSA_NR_SINGLE_BC_PREFER_SW-1;
//(Optional) Turning on the whitelist control switch for the preferential selection of a band combination
with only one NR carrier for NSA UEs function
ADD UECOMPAT: Index=0, UeInfoType=UE_CAPABILITY, UeCapIndex=0,
WhitelistCtrlExtSwitch1=NSA_NR_SINGLE_BC_PREFER_SW-1;
//(Optional) Enabling differentiated SCG addition threshold configuration for NR CA-capable UEs and
configuring the RSRP threshold offset for SCG addition for such CA-capable UEs
MOD NSADCALGOPARAM: NsaDcAlgoExtSwitch=SCG_ADD_B1_THLD_DIFF_SW-1;
MOD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=636666, CaUeScgAddRsrpThldOffset=-5;
//(Optional) Enabling time-domain intermodulation interference avoidance
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoSwitch=TDM_SWITCH-1;
MOD NSADCALGOPARAM: NsaDcAlgoSwitch=LNR_RELATIVE_FRM_OFS_ADAPT_SW-1;
//(Optional) Enabling frequency-domain intermodulation interference avoidance
MOD NSADCMGMTCONFIG: LocalCellId=21,
NsaDcAlgoSwitch=INTERFERENCE_AVOID_SW-1&TDM_SWITCH-1;
//(Optional) Enabling harmonic interference avoidance
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoSwitch=INTERFERENCE_AVOID_SW-1,
ImdIntrfFreqAvoidanceType=PRIOR_ALLOC_NO_INTRF_RB;
//(Optional) Enabling upperLayerIndication broadcast in SIB2
MOD NSADCMGMTCONFIG: LocalCellId=21, UpperLayerIndicationSwitch=ON;
//(Optional) Enabling the serving cell PLMN upperLayerIndication to be broadcast in SIB2
MOD CNOPERATOR: CnOperatorId=0, OperatorFunSwitch=UPPER_LYR_IND_NO_BROADCAST_SW-0;
//(Optional) Enabling uplink single-side transmission in NSA DC scenarios. If the frame offsets in the
CellFrameOffset and EnodeBFrameOffset MOs are not set, the value 0 takes effect in time synchronization
scenarios.
MOD CELLFRAMEOFFSET: LocalCellId=21, FrameOffsetMode=CustomFrameOffset, FrameOffset=0;
MOD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=361000,
AggregationAttribute=SINGLE_UL_NSA_FLAG-1;
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoSwitch=TDM_SWITCH-1;
//Modifying the QCI-level downlink data split mode in Option 3
MOD NSADCQCIPARAMGROUP: LocalCellId=21, NsaDcQciParamGroupId=0,
DlDataPdcpSplitMode=SCG_ONLY;
//Modifying the QCI-level uplink data split primary path and uplink data split threshold in Option 3
MOD NSADCQCIPARAMGROUP: LocalCellId=21, NsaDcQciParamGroupId=0, UlDataSplitPrimaryPath=SCG,
UlDataSplitThreshold=INFINITY;
//(Optional) Modifying the downlink and uplink data split modes in Option 3 for a specific operator
MOD CELLOPQCIPARA: CnOperatorId=1, LocalCellId=21, Qci=9, NsaDcQciParamGroupId=0;
//(Optional) Enabling downlink real-time data split
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoExtSwitch=NSA_SPLIT_RATE_OPT_SW-1;
//(Optional) Enabling adaptive resumption of downlink data split in Option 3
MOD NSADCALGOPARAM: NsaDcAlgoSwitch=NSA_SPLIT_ADAPT_RECOVERY_SW-1;
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoExtSwitch=NSA_SPLIT_RATE_OPT_SW-1;
//(Optional) Enabling adaptive resumption of downlink data split in Option 3x
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoExtSwitch=NSA_SPLIT_RATE_OPT_SW-1;
//(Optional) Configuring the maximum uplink MCG transmit power and maximum uplink SCG transmit
power for NSA DC UEs for initial power control
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcUeMcgUlMaximumPower=20,
NsaDcUeScgUlMaximumPower=20;
//(Optional) Enabling NSA uplink preallocation
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoSwitch= NSA_DC_PREALLOCATION_SW-1;
//(Optional) Configuring intra-band EN-DC

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 150

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

MOD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=361000,

AggregationAttribute=CO_DEPLOYMENT_NSA_FLAG-1;
ADD NRNRELATIONSHIP: LocalCellId=21, Mcc="262", Mnc="01", GnodebId=1, CellId=7,
AggregationAttribute=CO_DEPLOYMENT_NSA_FLAG-1;
//(Optional) Configuring SCG release and addition based on UE overheating status reporting
MOD NSADCALGOPARAM: NsaDcAlgoSwitch=OVERHEATING_RPOTECTION_SW-1;
MOD RRCCONNSTATETIMER: OverheatingIndProhibitTmr=S120;
//(Optional) Enabling SCG addition based on S1-U status in Option 3x
MOD ENODEBALGOEXTSWITCH: NsaDcAlgoSwitch= S1U_STATUS_BASED_SCG_ADD_SW-1;
//(Optional) Turning on the EQUIVALENT_PLMN_ADD_SCG_SW or INTER_PLMN_ADD_SCG_SW switch
when LTE and NR belong to different PLMNs
MOD ENODEBALGOEXTSWITCH:
NsaDcAlgoSwitch=EQUIVALENT_PLMN_ADD_SCG_SW-1&INTER_PLMN_ADD_SCG_SW-1;
//(Optional) Turning on the UMPTg enhancement switch when the main control board is UMPTg
MOD ENODEBRESMODEALGO: ServiceMode=UMPTG_ENHANCEMENT_SWITCH-1;
RST APP: AID=1;
//(Optional) Turning on the AI enhancement optimization switch if the main control board is a UMPTe or
UMPTga
MOD ENODEBRESMODEALGO:
ServiceMode=AI_ENHANCEMENT_SWITCH-0&AI_ENHANCEMENT_OPT_SWITCH-1;
RST APP: AID=1;
//(Optional) Enabling LNR virtual grid model building
MOD LNRCARRIERSELECTION: LnrCarrierSelectionSw=LNR_VIRTUAL_GRID_SW-1;
//(Optional) Enabling NSA LTE anchor virtual grid model building
MOD LNRCARRIERSELECTION: LnrCarrierSelectionSw=NSA_ANCHOR_VIRTUAL_GRID_SW-1;
//(Optional) Enabling PSCell addition based on virtual grid models (measurement-based PSCell addition)
MOD LNRCARRIERSELECTION: VgMdlPredNrScgMeasRsrpThld=ACCURACY100_ENH,
LnrCarrierSelectionSw=NSA_CARRIER_SEL_WITH_VG_SW-1, IntraFreqMeasA3TimeToTrig=320MS,
VgMdlKpiMonitorThld=95;
//(Optional) Enabling PSCell addition based on virtual grid models (blind PSCell configuration)
MOD LNRCARRIERSELECTION: VgMdlPredNrScgMeasRsrpThld=ACCURACY90_OFFSET0,
LnrCarrierSelectionSw=NSA_CARRIER_SEL_WITH_VG_SW-1, IntraFreqMeasA3TimeToTrig=320MS,
VgMdlKpiMonitorThld=95;
//(Optional) Enabling measurement and penalty for SCG addition based on virtual grids
MOD LNRCARRIERSELECTION: LnrCarrierSelectionSw=VG_SCG_ADD_MEAS_AND_PUNISH_SW-1;
//(Optional) Prohibiting the use of a specific EN-DC band combination (for example, B3+B20+N41)
ADD UECOMPAT: Index=0, UeInfoType=UE_CAPABILITY, UeCapIndex=0, NsaBandCombBlacklist1=
NSA_BAND_COMB_ID_0-1;
ADD PRIVATECABANDCOMB: PrivateCaCombId=0, MaxAggregatedBw=200, BwCombSetId=0, NsaFlag=TRUE;
ADD PRIVATEBAND: PrivateCaCombId=0, CombBandIndex=1, CombBandId=3,
CombBandBw=Bandwidth_1_4M-1&Bandwidth_3M-1&Bandwidth_5M-1&Bandwidth_10M-1&Bandwidth_15
M-1&Bandwidth_20M-1&Bandwidth_0M-0;
ADD PRIVATEBAND: PrivateCaCombId=0, CombBandIndex=2, CombBandId=20,
CombBandBw=Bandwidth_1_4M-1&Bandwidth_3M-1&Bandwidth_5M-1&Bandwidth_10M-1&Bandwidth_15
M-1&Bandwidth_20M-1&Bandwidth_0M-0;
ADD PRIVATEBAND: PrivateCaCombId=0, CombBandIndex=3, CombBandId=41,
CombBandBw=Bandwidth_1_4M-0&Bandwidth_3M-0&Bandwidth_5M-0&Bandwidth_10M-0&Bandwidth_15
M-0&Bandwidth_20M-0&Bandwidth_0M-1, BandType=NR;
//(Optional) Forbidding a specified LTE frequency from serving as an LTE SCC when it is in an EN-DC band
combination that includes a specified NR frequency
ADD UECOMPAT: Index=0, UeInfoType=UE_CAPABILITY, UeCapIndex=0, LnrFreqRelpWhitelist=
FREQ_RELATIONSHIP_ID_32-1;
ADD LNRFREQRELATIONSHIP: RelationshipId=0, DlEarfcn=1500, NrDlArfcn=636666,
NrDlBandwidth=CELL_BW_20M-0, FreqRelationship=SCC_AVOIDANCE;
//(Optional) Configuring RRC connection reestablishment optimization for defective NSA UEs to prohibit
blacklisted UEs from adding NR carriers as SCG carriers
MOD UECOMPAT: Index=0, UeInfoType=UE_CAPABILITY, UeCapIndex=0,
BlacklistControlExtSwitch2=NSA_NR_CARRIER_FORBID_SW-1;
//(Optional) Configuring RRC connection reestablishment optimization for defective NSA UEs to specify the
SCG frequency with a non-protocol-defined BWP
MOD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=151600,
AggregationAttribute=NON_STANDARD_BWP_FLAG-1;
//(Optional) Enabling preferred path adaption in downlink data split
MOD NSADCQCIPARAMGROUP: LocalCellId=21, NsaDcQciParamGroupId=0,
DlDataPdcpSplitMode=ADAPT_PRIMARY_PATH;
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoExtSwitch=NSA_SPLIT_RATE_OPT_SW-1;
//(Optional) Enabling NSA downlink data split optimization in DRX scenarios
MOD NSADCALGOPARAM: NsaDcAlgoSwitch=DRX_NSA_SPLIT_OPT_SW-1;
//(Optional) Enabling SPID-based SCG frequency priority configuration

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 151

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

ADD NRSCGFREQPRIGRP: NrScgFreqPriorityGroupId=0, PccDlEarfcn=1500, NrScgDlArfcn=636666,

NrScgDlArfcnPriority=7;
ADD NRSCGFREQPRIGRP: NrScgFreqPriorityGroupId=0, PccDlEarfcn=1500, NrScgDlArfcn=361000,
NrScgDlArfcnPriority=6;
ADD SPIDCFG: Spid=1, NrScgFreqPriorityGroupId=0;
//(Optional) Setting the operator-specific SCG frequency priority configuration function
ADD NRSCGFREQPRIGRP: NrScgFreqPriorityGroupId=0, PccDlEarfcn=1500, NrScgDlArfcn=636666,
NrScgDlArfcnPriority=7;
ADD NRSCGFREQPRIGRP: NrScgFreqPriorityGroupId=1, PccDlEarfcn=1500, NrScgDlArfcn=636666,
NrScgDlArfcnPriority=6;
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="mobile1",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="01", NrScgFreqPriorityGroupId=1;
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="mobile2",
CnOperatorType=CNOPERATOR_SECONDARY, Mcc="460", Mnc="02", NrScgFreqPriorityGroupId=0;
//(Optional) Enabling uplink CA in EN-DC
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoExtSwitch=NSA_LTE_UL_2CC_SW-1;
//(Optional) Enabling non-NR-coverage-triggered EN-DC combination reselection to support EN-DC band
combination changes triggered due to weak NR coverage in the uplink or downlink
MOD ENODEBALGOEXTSWITCH: NsaDcAlgoSwitch= NO_NR_COV_EN_DC_RESEL_SW-1;
//(Optional) Adding an SPID configuration with a multi-carrier configuration group ID specified
ADD SPIDCFG: Spid=1, MultiCarrCfgGroupId=1;
//(Optional) Modifying a QCI configuration with a multi-carrier configuration group ID specified
MOD QCIPARA: Qci=1, MultiCarrCfgGroupId=1;
//(Optional) Configuring the NSA PCC anchoring policy
ADD CELLMULTICARRCFGGRP: DlArfcn=1500, RatType=EUTRAN, CnOperatorId=1, MultiCarrCfgGroupId=1,
LocalCellId=21, AggregationAttribute=FORBID_MEAS_FLAG-1&HIGH_LOAD_CELL_NSA_PCC_FLAG-1,
NsaPccAnchoringPriority=8;
MOD NSADCMGMTCONFIG: LocalCellId=21, DlPrbThldForNsaPccAnchor=95;
//(Optional) Configuring the PSCell management policy
ADD CELLMULTICARRCFGGRP: DlArfcn=636666, RatType=NR, CnOperatorId=1, MultiCarrCfgGroupId=1,
LocalCellId=21, NrScgPriorityOffset=1, NsaDcB1RsrpThldOffset=1,
AggregationAttribute=FORBID_MEAS_FLAG-1;
//(Optional) Enabling SPID-specific SCG addition at short intervals without considering traffic volume
ADD SPIDCFG: Spid=1, SpidAlgoSwitch=SPID_SHT_PRD_NO_TFC_SCG_ADD_SW-1;
//(Optional) Enabling QCI-specific SCG addition at short intervals without considering traffic volume
ADD CELLQCIPARA: LocalCellId=21, Qci=11, QciAlgoSwitch=QCI_SHT_PRD_NO_TFC_SCG_ADD_SW-1;
//(Optional) Setting Short-Period No-Traffic SCG Add Interval
MOD NSADCMGMTCONFIG: LocalCellId=21, ShortPrdNoTfcScgAddIntvl=4;
//(Optional) Enabling NR FR2 frequency measurement in polling mode in NSA mmWave networking
MOD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=151600, ScgDlArfcnPriority=7,
AggregationAttribute=NR_FR2_MEAS_POLLING_FLAG-1;
//(Optional) Configuring blacklist control for SCC management in NSA networking on the LTE side if there
are abnormal UEs for which SCCs cannot be added together with SCGs
ADD UECOMPAT: Index=0, UeInfoType=IMEISV_TAC_SVN, ImeisvTac=12345678, ImeisvSvn=12,
BlacklistControlExtSwitch2=NSA_CA_FORBID_SW-1;

On the gNodeB side

//Setting the downlink PDCP-layer data split mode in the gNodeB PDCP parameter group (The following
uses data split only to the SCG as an example. Set the data split mode based on the network plan.)
MOD GNBPDCPPARAMGROUP: PdcpParamGroupId=1, DlDataPdcpSplitMode=SCG_ONLY;
//Setting the primary path and threshold for uplink data split in the gNodeB PDCP parameter group (The
following uses data split only to the SCG as an example. Set the data split mode based on the network
plan.)
MOD GNBPDCPPARAMGROUP: PdcpParamGroupId=1, UlDataSplitPrimaryPath=SCG,
UlDataSplitThreshold=INFINITY, DlPdcpSnSize=BITS18;
//(Optional) Configuring downlink and uplink data split modes in Option 3x for a specific operator
MOD NRCELLOPQCIBEARER: OperatorId=1, NrCellId=7, Qci=9, RlcMode=AM, AmPdcpParamGroupId=1;
//(Optional) Enabling downlink real-time data split
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=NSA_SPLIT_RATE_OPT_SW-1;
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_PDCP_SPLIT_OPT_SW-1;
//(Optional) Enabling adaptive resumption of downlink data split in Option 3
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=NSA_SPLIT_RATE_OPT_SW-1;
//(Optional) Enabling adaptive resumption of downlink data split in Option 3x
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_SPLIT_ADAPT_RECOVERY_SW-1;
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=NSA_SPLIT_RATE_OPT_SW-1;
//Setting NR cell algorithm switches
MOD NRCELLALGOSWITCH: NrCellId=7, NsaDcSwitch=ON;
//Modifying the bearer configuration of an NR cell with the RLC Mode parameter set to AM and the
AmPdcpParamGroupId parameter set to the same value as PdcpParamGroupId

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 152

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

MOD NRCELLQCIBEARER: NrCellId=7, Qci=9, AmPdcpParamGroupId=1, RlcMode=AM;

//(Optional) Configuring event-based triggering of NR data volume reporting in Option 3x
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) Enabling time-domain intermodulation interference avoidance
MOD NRDUCELLALGOSWITCH: NrDuCellId=120, NsaDcAlgoSwitch=CROSS_MDLT_INTRF_AVOID_SW-1;
MOD NRDUCELLNSADCCONFIG: NrDuCellId=120,
HarmonicIntrfAvoidRange=NR_DL_COMMON_AND_DATA_CHANNEL;
//(Optional) Enabling harmonic interference avoidance
MOD NRDUCELLALGOSWITCH: NrDuCellId=120, NsaDcAlgoSwitch=HARMONIC_INTRF_AVOID_SW-1;
//(Optional) Enabling SRB3
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_DC_SRB3_SWITCH-1;
//(Optional) Enabling uplink single-side transmission in NSA DC scenarios. If the frame offset is not set, the
value 0 takes effect in time synchronization scenarios.
MOD GNBFREQBANDCONFIG: FrequencyBand=N3, FrameOffset=0;
ADD GNBDEDNSADCBANDCOMB: NrBandId=N3, LteBandId=3,
AggregationAttribute=SINGLE_UL_NSA_FLAG-1;
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=SINGLE_UL_NSA_SW-1;
//(Optional) Enabling fast retransmission for downlink data split
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_DC_FAST_RETRANS_SWITCH-1;
//(Optional) Enabling NSA uplink preallocation
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=NSA_DC_PREALLOCATION_SW-1;
//(Optional) Configuring intra-band EN-DC
ADD GNBDEDNSADCBANDCOMB: NrBandId=N3, LteBandId=3,
AggregationAttribute=CO_DEPLOYMENT_NSA_FLAG-1;
ADD GNBNRLTECELLCOMB: Mcc="454", Mnc="06", gNodeBId=329, CellId=247, LteMcc="454",
LteMnc="06", eNodeBId=324, LteCellId=240, AggregationAttribute=CO_DEPLOYMENT_NSA_FLAG-1;
//(Optional) Configuring SgNB release based on RSRP
MOD NRCELLNSADCCONFIG: NrCellId=7, PscellA2RsrpThld=-121;
MOD NRCELLNSADCCONFIGGRP: NrCellId=7, NsaDcConfigGroupId=2, PscellA2RsrpThldOffset=0,
PscellA2TimeToTrig=640MS;
//(Optional) Configuring SgNB release based on SSB SINR
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=SINR_BASED_SCG_RELEASE_SW-1;
MOD NRCELLNSADCCONFIGGRP: NrCellId=7, NsaDcConfigGroupId=2, PscellA2SinrThld=-10;
//(Optional) Enabling differentiated SCG deletion threshold configuration for NR CA-capable UEs by
configuring the offset used to calculate the RSRP threshold for PSCell event A2 for CA-capable UEs
MOD NRCELLNSADCCONFIG: NrCellId=7, CaCapUePscellA2RsrpThldOfs=-5;
//(Optional) Enabling S1-U status sending in Option 3x
MOD GNODEBPARAM: NsaDcOptSwitch=S1U_STATUS_SEND_SW-1;
//(Optional) Setting the PLMN selection policy switch for SCG addition when LTE and NR belong to
different PLMNs
MOD GNODEBPARAM: NsaDcOptSwitch= SCG_ADD_PLMN_SELECT_POLICY_SW-1;
//(Optional) Enabling the gNodeB to send information about the NR PSCell and SCell frequencies in EN-DC
band combinations to the eNodeB so that the eNodeB can determine whether to forbid the addition of an
LTE frequency as the frequency of an LTE SCC
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_FREQ_CONFLICT_AVOID_SW-1;
//(Optional) Enabling preferred path adaption in downlink data split
MOD GNBPDCPPARAMGROUP: PdcpParamGroupId=1, DlDataPdcpSplitMode=ADAPT_PRIMARY_PATH;
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=NSA_SPLIT_RATE_OPT_SW-1;
//(Optional) Enabling NSA downlink data split optimization in DRX scenarios
MOD GNODEBPARAM: NsaDcOptSwitch=DRX_NSA_SPLIT_OPT_SW-1;
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_DC_FAST_RETRANS_SWITCH-1;
//(Optional) Configuring an SPID-specific NSA uplink primary path with the SPID specified by
gNBRfspConfig.RfspIndex
MOD GNBRFSPCONFIG: OperatorId=0, RfspIndex=0, UlPrimaryPathSelMode=SCG,
UlDataSplitThreshold=BYTE1600;

Deactivation Command Examples

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

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 153

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

//Turning off the NSA DC switch on the LTE side

MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoSwitch=NSA_DC_CAPABILITY_SWITCH-0;
//Disabling downlink real-time data split
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoExtSwitch=NSA_SPLIT_RATE_OPT_SW-0;
// Disabling NSA downlink data split optimization in DRX scenarios
MOD NSADCALGOPARAM: NsaDcAlgoSwitch=DRX_NSA_SPLIT_OPT_SW-0;
//Disabling adaptive resumption of downlink data split in Option 3
MOD NSADCALGOPARAM: NsaDcAlgoSwitch=NSA_SPLIT_ADAPT_RECOVERY_SW-0;
//Disabling event-triggered NR data volume reporting in Option 3 on the LTE side
MOD NSADCMGMTCONFIG: LocalCellId=21, NrDataVolumeRptCfg=0;
//Turning off the interference avoidance switch
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoSwitch=INTERFERENCE_AVOID_SW-0;
//Disabling upperLayerIndication broadcast in SIB2
MOD NSADCMGMTCONFIG: LocalCellId=21, UpperLayerIndicationSwitch=OFF;
//Disabling uplink single-side transmission in NSA DC
MOD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=361000,
AggregationAttribute=SINGLE_UL_NSA_FLAG-0;
//Disabling the co-site intra-band pair of LTE and NR cells
MOD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=361000,
AggregationAttribute=CO_DEPLOYMENT_NSA_FLAG-0;
MOD NRNRELATIONSHIP: LocalCellId=21, Mcc="262", Mnc="01", GnodebId=1, CellId=7,
AggregationAttribute=CO_DEPLOYMENT_NSA_FLAG-0;
//Disabling SCG addition based on equivalent PLMN or inter-PLMN information
MOD ENODEBALGOEXTSWITCH:
NsaDcAlgoSwitch=EQUIVALENT_PLMN_ADD_SCG_SW-0&INTER_PLMN_ADD_SCG_SW-0;
//Turning off the LTE-NR carrier selection switches
MOD LNRCARRIERSELECTION:
LnrCarrierSelectionSw=LNR_VIRTUAL_GRID_SW-0&NSA_CARRIER_SEL_WITH_VG_SW-0&NSA_ANCHOR_VIRT
UAL_GRID_SW-0;
//Disabling LNR virtual grid model building
MOD LNRCARRIERSELECTION: LnrCarrierSelectionSw=LNR_VIRTUAL_GRID_SW-0;
//Disabling NSA LTE anchor virtual grid model building
MOD LNRCARRIERSELECTION: LnrCarrierSelectionSw=NSA_ANCHOR_VIRTUAL_GRID_SW-0;
//Disabling PSCell addition based on virtual grid models
MOD LNRCARRIERSELECTION: LnrCarrierSelectionSw=NSA_CARRIER_SEL_WITH_VG_SW-0;
//Disabling measurement and penalty for SCG addition based on virtual grids
MOD LNRCARRIERSELECTION: LnrCarrierSelectionSw=VG_SCG_ADD_MEAS_AND_PUNISH_SW-0;
//Turning off the UMPTg enhancement switch when the main control board is a UMPTg (The switch setting
must be the same as that before PSCell addition based on virtual grid models is enabled.)
MOD ENODEBRESMODEALGO: ServiceMode=UMPTG_ENHANCEMENT_SWITCH-0;
RST APP: AID=1;
//Turning off the AI enhancement optimization switch if the main control board is a UMPTe or UMPTga
(The switch setting must be the same as that before PSCell addition based on virtual grid models is
enabled.)
MOD ENODEBRESMODEALGO: ServiceMode=AI_ENHANCEMENT_OPT_SWITCH-0;
RST APP: AID=1;
//Disabling the preferred path adaption function
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoExtSwitch=NSA_SPLIT_RATE_OPT_SW-0;
//Disabling SPID-based SCG frequency priority configuration
ADD SPIDCFG: Spid=1, NrScgFreqPriorityGroupId=65535;
//(Optional) Disabling the preferential selection of a band combination with only one NR carrier for NSA
UEs function
MOD ENODEBALGOEXTSWITCH: MultiNetworkingOptionOptSw=NSA_NR_SINGLE_BC_PREFER_SW-0;
//(Optional) Turning off the whitelist control switch for the preferential selection of a band combination
with only one NR carrier for NSA UEs function
MOD UECOMPAT: Index=0, UeInfoType=UE_CAPABILITY, UeCapIndex=0,
WhitelistCtrlExtSwitch1=NSA_NR_SINGLE_BC_PREFER_SW-0;
//(Optional) Disabling differentiated SCG addition threshold configuration for NR CA-capable UEs
MOD NSADCALGOPARAM: NsaDcAlgoExtSwitch=SCG_ADD_B1_THLD_DIFF_SW-0;
//(Optional) Disabling uplink CA in EN-DC
MOD NSADCMGMTCONFIG: LocalCellId=21, NsaDcAlgoExtSwitch=NSA_LTE_UL_2CC_SW-0;
//(Optional) Disabling non-NR-coverage-triggered EN-DC combination reselection
MOD ENODEBALGOEXTSWITCH: NsaDcAlgoSwitch= NO_NR_COV_EN_DC_RESEL_SW-0;
//(Optional) Disabling SPID-specific SCG addition at short intervals without considering traffic volume
ADD SPIDCFG: Spid=1, SpidAlgoSwitch=SPID_SHT_PRD_NO_TFC_SCG_ADD_SW-0;
//(Optional) Disabling QCI-specific SCG addition at short intervals without considering traffic volume
ADD CELLQCIPARA: LocalCellId=21, Qci=11, QciAlgoSwitch=QCI_SHT_PRD_NO_TFC_SCG_ADD_SW-0;
//(Optional) Disabling NR FR2 frequency measurement in polling mode in NSA mmWave networking

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 154

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

MOD NRSCGFREQCONFIG: PccDlEarfcn=1500, ScgDlArfcn=151600, ScgDlArfcnPriority=7,

AggregationAttribute=NR_FR2_MEAS_POLLING_FLAG-0;

On the gNodeB side

//Turning off the NSA DC switch on the NR side
MOD NRCELLALGOSWITCH: NrCellId=7, NsaDcSwitch=OFF;
//(Optional) Disabling downlink real-time data split
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=NSA_SPLIT_RATE_OPT_SW-0;
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_PDCP_SPLIT_OPT_SW-0;
//(Optional) Disabling adaptive resumption of downlink data split in Option 3x
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_SPLIT_ADAPT_RECOVERY_SW-0;
//(Optional) Disabling fallback to LTE
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=UL_FALLBACK_TO_LTE_SWITCH-0;
//(Optional) Disabling event-based triggering of NR data volume reporting in Option 3x
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 uplink single-side transmission in NSA DC
MOD GNBDEDNSADCBANDCOMB: NrBandId=N3, LteBandId=3,
AggregationAttribute=SINGLE_UL_NSA_FLAG-0;
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=SINGLE_UL_NSA_SW-0;
//(Optional) Disabling fast retransmission for downlink data split
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_DC_FAST_RETRANS_SWITCH-0;
//(Optional) Disabling NSA uplink preallocation
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=NSA_DC_PREALLOCATION_SW-0;
//(Optional) Disabling the co-site intra-band pair of LTE and NR cells
MOD GNBDEDNSADCBANDCOMB: NrBandId=N3, LteBandId=3, AggregationAttribute=
CO_DEPLOYMENT_NSA_FLAG-0;
//(Optional) Disabling the preferred path adaption function
MOD NRCELLNSADCCONFIG: NrCellId=7, NsaDcAlgoSwitch=NSA_SPLIT_RATE_OPT_SW-0;
//(Optional) Disabling NSA downlink data split optimization in DRX scenarios
MOD GNODEBPARAM: NsaDcOptSwitch=DRX_NSA_SPLIT_OPT_SW-0;
MOD GNODEBPARAM: NsaDcOptSwitch=NSA_DC_FAST_RETRANS_SWITCH-0;
//(Optional) Disabling differentiated SCG deletion threshold configuration for NR CA-capable UEs
MOD NRCELLNSADCCONFIG: NrCellId=7, CaCapUePscellA2RsrpThldOfs=0;

4.4.2.3 Using the MAE-Deployment

● Fast batch activation
This function can be batch activated using the Feature Operation and
Maintenance function of the MAE-Deployment. For detailed operations, see
the following section in the MAE-Deployment product documentation or
online help: MAE-Deployment Operation and Maintenance > MAE-
Deployment Guidelines > Enhanced Feature Management > Feature
Operation and Maintenance.
● Single/Batch configuration
This function can be activated for a single base station or a batch of base
stations on the MAE-Deployment. For detailed operations, see Feature
Configuration Using the MAE-Deployment.

4.4.3 Activation Verification

Monitoring Counters
Counters related to NSA DC can be subscribed on the MAE-Access in one-click
mode.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 155

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

● After activating NSA DC, observe the counters listed in the following tables.
On a network with NSA UEs, NSA DC has taken effect only if the following
counters produce non-zero values.

Counter ID Counter Name NE

1526747850 L.Traffic.User.NsaDc.PCell.A eNodeB

vg

1911816745 N.User.NsaDc.PSCell.Avg gNodeB

● Observe the number of times NR measurement configurations are delivered in

NSA DC scenarios.
– The counter L.NsaDc.MeasCtrl.NR indicates the number of times NR
measurement configurations are delivered in NSA DC scenarios.
– The counter L.NsaDc.MeasCtrl.NR.NoGap indicates the number of times
NR gap-free measurement configurations are delivered in NSA DC
scenarios.
● Check whether data split has taken effect in NSA DC.
– The counter N.PDCP.Vol.DL.X2U.TrfPDU.Tx indicates the total downlink
data volume split for NSA 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 UEs over the X2 interface. If the counter value
is greater than 0, uplink data split has taken effect.
● Check whether uplink preallocation has taken effect.
– This function has taken effect if there is uplink data transmission but no
downlink data transmission on the LTE side and the smart preallocation
function takes effect on the LTE side in NSA networking. For details about
the activation verification method, see Uplink Scheduling in eRAN feature
documentation.
– This function has taken effect if there is uplink data transmission but no
downlink data transmission on the NR side and the uplink preallocation
function takes effect on the NR side in NSA networking. For details about
the activation verification method, see Scheduling in 5G RAN feature
documentation.
● Check whether virtual grid model building has taken effect.
Perform monitoring from the second week after the function is enabled as it
takes one week to build virtual grid models.
– If the value of L.AiGrid.LnrRsrpPred.Model.AverNum is not 0, virtual
grid model building has taken effect.
– If the value of L.VirtualGrid.Model.NrFreq.ScgAddAtt.Times is not 0,
PSCell addition based on virtual grid models has taken effect. The
number of failed SCG additions based on LNR virtual grid models is
indicated by the L.VirtualGrid.Model.NrFreq.ScgAddFail.Times counter.
The number of successful SCG additions based on LNR virtual grid
models is equal to L.VirtualGrid.Model.NrFreq.ScgAddAtt.Times minus
L.VirtualGrid.Model.NrFreq.ScgAddFail.Times.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 156

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– If the value of L.VirtualGrid.Model.NrFreq.InvalidMeasFree.Times is

not 0, invalid NR measurement configurations are not delivered because
it is predicted that there is no NR coverage based on virtual grids.
– If the SMART_CARRIER_SELECTION_SW option of the
MultiCarrUnifiedSch.MultiCarrierUnifiedSchSw parameter is deselected
and the values of L.HHO.VirtualGrid.Model.PrepAttOut and
L.NsaDC.PCCAnchor.HHO.PrepAttOut are not 0, NSA anchoring using
LTE RSRP values predicted based on virtual grids has taken effect.
– Run the DSP AIGRIDMOD command to query the status of all models of
the eNodeB, including Good RSRP Forecast Status, Poor RSRP Forecast
Status, RSRP Model Latest Offline Time, and RSRP Model Latest Offline
Reason.
● Check whether downlink real-time data split has taken effect.
Check the value of N.PDCP.Vol.DL.X2U.TrfPDU.Tx / N.PDCP.Vol.DL.TrfPDU.Tx
x 100%. That is, check the ratio of the data volume of downlink PDCP PDUs
transmitted over the X2 interface to that distributed from the PDCP to the
RLC. If the value increases, downlink real-time data split has taken effect.

Message Tracing
1. Log in to the MAE-Access. Choose Monitor > Signaling Trace > Signaling
Trace Management. The Signaling Trace Management window is displayed.
2. Trace UE random access.
Choose Trace Type > LTE > Application Layer > Uu Interface Trace. You can
observe that the UE sends an RRC_CONN_SETUP_CMP message to the
eNodeB to initiate an LTE access procedure.
3. (Optional) The eNodeB delivers an NR measurement configuration message
to the UE.
Choose Trace Type > LTE > Application Layer > Uu Interface Trace. You can
observe that the eNodeB sends an RRC_CONN_RECFG message to the UE,
which contains the EventB1 IE.

4. (Optional) The UE reports measurement results.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 157

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

Choose Trace Type > LTE > Application Layer > Uu Interface Trace. You can
observe that the UE sends an RRC_MEAS_RPRT message, which contains IEs
related to the measured PCIs and signal strength of NR cells.

5. The SgNB is added on the LTE side.

Choose Trace Type > LTE > Application Layer > X2 Interface Trace. You can
observe 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 completed.
6. The eNodeB configures the SCG for the UE. The UE returns a message
indicating that the configuration is complete.
Choose Trace Type > LTE > Application Layer > Uu Interface Trace. You can
observe that the eNodeB sends an RRC_CONN_RECFG message to the UE,
which contains the nr-config-r15 IE.
7. The eNodeB sends an ERAB MOD message to the core network over an S1
interface.
Choose Trace Type > LTE > Application Layer > S1 Interface Trace. You can
observe that the eNodeB sends an S1AP_E_RAB_MOD_IND message to the
core network, notifying the core network that all downlink data of the UE is
sent to the gNodeB.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 158

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

NOTE

For LTE-NR joint tracing, joint tracing must be started before the UE accesses the
network.
8. (Optional) Check whether RLC rate optimization in downlink real-time data
split has taken effect.
Choose Trace Type > LTE > Application Layer > X2 Interface Trace. Check
whether the eNodeB sends an EN-DC Private Vendor Configuration Transfer
message with an eNB Cell Configuration Indication 1 IE whose bit 11 is set to
1, and whether the gNodeB sends the eNodeB an EN-DC Private Vendor
Configuration Transfer message with a gNB Cell Configuration Indication 1 IE
whose bit 9 is set to 1. If so, the function has taken effect.
9. (Optional) Check whether uplink fallback to LTE has taken effect.
Choose Trace Type > LTE > Application Layer > X2 Interface Trace. Check
whether the gNodeB sends the eNodeB an SgNB Modification Required
message with IEs SgNB to MeNB Container > CG-Config > scg-RB-Config >
drb-ToAddModList > pdcp-Config in which primaryPath is set to 0 (indicating
the MCG) and ul-DataSplitThreshold is set to infinity. If so, the function has
taken effect.
10. (Optional) Check whether the interference avoidance function has taken
effect.
Choose Trace Type > LTE > Application Layer > X2 Interface Trace. Check
whether the gNodeB sends the eNodeB an SgNB Addition Request
Acknowledge, SgNB Modification Request Acknowledge, or SgNB Modification
Required message with IEs SgNB Resource Coordination Information > UL
Coordination Information whose bits are not all zeros. If the bits are not all
zeros, the function has taken effect. If the bits are all zeros, the function has
not taken effect.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 159

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

11. (Optional) Check whether SIB2 includes an upperLayerIndication IE.

Choose Trace Type > LTE > Application Layer > Uu Interface Trace. If SIB2
sent by the base station includes an upperLayerIndication IE, the function has
taken effect.
12. (Optional) Check whether uplink single-side transmission in NSA DC has
taken effect.
– Choose Trace Type > LTE > Application Layer > Uu Interface Trace.
Check whether the eNodeB sends a UE an RRC_CONN_RECFG message
with a tdm-PatternConfig-r15 IE. If so, the function has taken effect.
– Choose Trace Type > LTE > Application Layer > X2 Interface Trace.
Check that the gNodeB sends the eNodeB an SgNB Addition Request
Acknowledge, SgNB Modification Request Acknowledge, or SgNB
Modification Required message with IEs SgNB Resource Coordination
Information > UL Coordination Information that includes a bitmap
indicating a TDM pattern.
13. (Optional) Check whether the NR data volume reporting function has taken
effect.
Choose Trace Type > LTE > Application Layer > X2 Interface Trace. Check
whether the gNodeB sends the eNodeB a Secondary RAT Data Usage Report
message. If so, the function has taken effect. In the message, the Usage Count
UL IE indicates the uplink data volume, and the Usage Count DL IE indicates
the downlink data volume.
14. (Optional) Check whether fast retransmission for downlink data split has
taken effect.
Choose Trace Type > LTE > Application Layer > X2 Interface Trace. Check
whether the gNodeB sends the eNodeB an EN-DC Private Vendor
Configuration Transfer message with a gNB Feature Configuration Indication 1
IE whose bit 0 is set to 1. If so, the function has taken effect.

4.4.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 observed on the gNodeB
side. The counters related to the user plane at the LTE PDCP layer do not measure
the throughput of NSA UEs.
● 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 UEs are
different from those of LTE-only UEs:

▪ Outgoing handover success rate of NSA UEs =

L.NsaDc.HHO.ExecSuccOut / L.NsaDc.HHO.ExecAttOut x 100%

▪ Incoming handover success rate of NSA UEs =

L.NsaDc.PCell.Change.Succ / L.NsaDc.PCell.Change.Exec x 100%

▪ Abnormal service drop rate of NSA UEs = L.NsaDc.E-

RAB.AbnormRel / L.NsaDc.E-RAB.NormRel x 100%

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 160

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– Calculate the total downlink data split volume of NSA UEs by adding
L.Thpt.bits.DL.McgSplit.MeNB and L.Thpt.bits.DL.McgSplit.SgNB. If the
volume increases continuously, this feature is running properly.
– Calculate the total uplink data split volume of NSA UEs by adding
L.Thpt.bits.UL.McgSplit.MeNB and L.Thpt.bits.UL.McgSplit.SgNB. If the
volume increases continuously, this feature is running properly.
– 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 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 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 UEs on the LTE side.
– Observe the L.NsaDc.DRB.Add.Att and L.NsaDc.DRB.Add.Succ counters
to obtain the number of data split bearer setup attempts and the number
of successful data split bearer setups for NSA UEs, respectively.
NOTE

In NSA networking, counter reporting by PLMN is supported on the LTE side. For
details, see RAN Sharing in eRAN feature documentation.
● On the gNodeB side
– Observe the N.PDCP.Vol.DL.X2U.TrfPDU.Tx counter to obtain the total
downlink data volume split for NSA UEs over the X2 interface. If the
value of this counter increases continuously, this feature is working
properly.
– Observe the N.PDCP.Vol.UL.X2U.TrfPDU.Rx counter to obtain the total
uplink data volume split for NSA UEs over the X2 interface. If the value of
this counter increases continuously, this feature is working properly.
– Observe the N.NsaDc.InterSite.SgNB.Add.Att counter to obtain the
number of inter-site SgNB addition attempts in the LTE-NR NSA DC
scenario.
– Observe the N.NsaDc.InterSite.SgNB.Add.Succ counter to obtain the
number of successful inter-site SgNB additions in the LTE-NR NSA DC
scenario.
– Observe the N.NsaDc.SgNB.Add.Att.QCI counter to obtain the number
of SgNB addition attempts for a specific QCI in LTE-NR NSA DC scenarios.
– Observe the N.NsaDc.SgNB.Add.Succ.QCI counter to obtain the number
of successful SgNB additions for a specific QCI in LTE-NR NSA DC
scenarios.
– Observe the N.NsaDc.SgNB.Rel.QCI counter to obtain the total number
of SgNB releases for a specific QCI in LTE-NR NSA DC scenarios.
– Observe the N.NsaDc.SgNB.Rel.SgNBTrigger.QCI counter to obtain the
total number of SgNB releases triggered by SgNB for a specific QCI in
LTE-NR NSA DC scenarios.
– Observe the N.NsaDc.SgNB.Rel.MeNBTrigger.NormalRel.QCI counter to
obtain the total number of normal SgNB releases triggered by MeNB for
a specific QCI in LTE-NR NSA DC scenarios.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 161

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 4 NSA Networking Based on EPC

– Observe the N.NsaDc.SgNB.AbnormRel.QCI counter to obtain the total

number of abnormal SgNB releases triggered by SgNB for a specific QCI
in LTE-NR NSA DC scenarios.
– Observe the N.NsaDc.SgNB.Rel.InitialAdd.RachFail.QCI counter to
obtain the number of SCG releases due to random access failures during
initial SCG addition for a specific QCI in LTE-NR NSA DC scenarios.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 162

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 5 Parameters

5 Parameters

The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
● gNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● gNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.

NOTE

You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.

FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?

Step 1 Open the EXCEL file of parameter reference.

Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID.

Step 3 Click OK. All parameters related to the feature are displayed.

----End

FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?

Step 1 Open the EXCEL file of the used reserved parameter list.

Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 163

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 5 Parameters

View its information, including the meaning, values, impacts, and product version
in which it is activated for use.

----End

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 164

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 6 Counters

6 Counters

The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● 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.
Step 3 Click OK. All counters related to the feature are displayed.

----End

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 165

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 7 Glossary

7 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 166

SingleRAN
EPC-based NSA Basics Feature Parameter
Description 8 Reference Documents

8 Reference Documents

● 3GPP TS 38.101: "NR; User Equipment (UE) radio transmission and reception"
● 3GPP TS 37.340: "E-UTRA and NR; Multi-connectivity; Stage-2"
● 3GPP TS 36.331: "E-UTRA; Radio Resource Control (RRC) Protocol
specification"
● Transmission Resource Management in 5G RAN feature documentation
● Power Control in 5G RAN feature documentation
● Multi-Frequency Smart Aggregation in 5G RAN feature documentation
● Uplink Scheduling in 5G RAN feature documentation
● Downlink Scheduling in 5G RAN feature documentation
● Cell Combination in 5G RAN feature documentation
● Hyper Cell in 5G RAN feature documentation
● Carrier Aggregation in eRAN feature documentation
● Idle Mode Management in eRAN feature documentation
● Uplink Scheduling in eRAN feature documentation
● Downlink Scheduling in eRAN feature documentation
● QoS Management in eRAN feature documentation
● Breathing Pilot in eRAN feature documentation
● Air Interface Latency Optimization in eRAN feature documentation
● Low-Band Booster in eRAN feature documentation
● UL and DL Decoupling
● X2 and S1 Self-Management in NSA Networking
● NSA Mobility Management
● BBU Interconnection in 3900 & 5900 Series Base Station Product
Documentation

Issue 01 (2024-03-09) Copyright © Huawei Technologies Co., Ltd. 167