NRDC Dual Connectivity

NR-NR Dual Connectivity https://opomenmidf2.idf2.vend2.ran.mob.orange.net/elex?
id=9283
Feature Description 113/221 04-LZA 701 6017/1 Uen EA25T
NR-NR Dual Connectivity

Contents
1 NR-NR Dual Connectivity Overview

The NR-NR Dual Connectivity feature introduces support for Multi-Radio Dual Connectivity with the 5GC. This
allows the UE to be connected to one gNodeB acting as the Master Node and another gNodeB acting as the
Secondary Node.
Fe a t u r e N a m e NR-NR Dual Connectivity

Fe a t u r e I d e n t i t y FAJ 121 5380
Va l u e P a c k a g e N a m e Peak Rate Evolution
Va l u e P a c k a g e I d e n t i t y FAJ 801 4005
Node Type Baseband Radio Node
Access Type NR
License-controlled feature. One license is required for each node.
Licensing The feature license must be installed on both the Master Node and the
Secondary Node.
Summary
The NR-NR Dual Connectivity feature enables the UE to connect to the 5GC using a Master Node with Low-Band (FR1)
or Mid-Band (FR1) and a Secondary Node with High-Band (FR2) NR frequencies.
The feature allows the UE to take advantage of the downlink and uplink bit rates of High-Band frequencies while the
UE is connected to the 5GC using Low-Band or Mid-Band anchor frequencies.
The feature provides the following benefits:
– The UEs utilize the higher bit rates of High-Band frequencies both in downlink and uplink.
– The packet processing resources are offloaded in gNodeBs with Low-Band or Mid-Band frequencies by using
PDCP resources in gNodeBs with High-Band frequencies.
Additional Info rmation

For more information and related topics, see the following documentation:
– RAN Parameter Recommendations Lists
– 3GPP TS 37.340; NR; Multi-connectivity; Overall description; Stage-2
– 3GPP TS 38.331; NR; Radio Resource Control (RRC); Protocol specification
– 3GPP TS 38.413; NG-RAN; NG Application Protocol (NGAP)
– 3GPP TS 38.423; NG-RAN; Xn Application Protocol (XnAP)
1.1 NR-DC Deployment

The NR-DC-capable UE operating in NR SA mode is always connected to a gNodeB with Low-Band (FR1) or Mid-Band
(FR1) frequencies. This type of gNodeB acts as the Master Node in NR-DC. The UE can connect to another gNodeB with
High-Band (FR2) frequencies if the UE is in High-Band coverage. This type of gNodeB acts as the Secondary Node in
NR-DC. The UE connects to the Master Node over the Uu interface. The Uu interface between the UE and the
Secondary Node is only established when the UE is configured with NR-DC.
1 sur 74 23/04/2024, 07:35

NR-NR Dual Connectivity https://opomenmidf2.idf2.vend2.ran.mob.orange.net/elex?id=9283
The Master Node is connected to the 5GC over the NG interface. The NG-C interface is used for control plane, while the
NG-U interface is used for user plane.
The Secondary Node connects to the 5GC over the NG-U interface for user plane.
The Master Node and the Secondary Node are connected to each other over the Xn interface. The Xn-C interface is
used for control plane, while the Xn-U interface is used for user plane. One Master Node can be connected to several
Secondary Nodes, and one Secondary Node can be connected to several Master Nodes.
5GC
NG
-U
-U
-C
G
N
G
N
Secondary
Master
Node
Node
Xn-C
Xn-U
G) PSCell PCell
(SC
Uu (MCG) Uu
Legend
User Plane Master Node = the master gNodeB providing the MCG
Control Plane Secondary Node = the secondary gNodeB providing the SCG
High-Band coverage
Low-Band or Mid-Band coverage
L0003062A
Figure 1 Interface Connections in NR-DC
In NR-DC, the UE is in RRC_CONNECTED mode in the Master Node. The control of the UE is managed through the RRC
signaling between the UE and the Master Node. Information specific to the Secondary Node resources is carried by
containers conveying RRC messages between the Secondary Node and the Master Node over the Xn-C interface and
between the Master Node and the UE over the Uu interface.
The following cell groups can serve the NR-DC-capable UE:

M a ster C e ll G rou p The MCG, configured for Low-Band or Mid-Band frequencies, is provided by the Master Node.
( M CG ) The MCG consists of one PCell and optionally one or several SCells.
Secondary Cell The SCG, configured for High-Band frequencies, is provided by the Secondary Node. The SCG
G r o u p ( S CG ) consists of one PSCell and optionally one or several SCells.
When the UE is configured with NR-DC, the following types of PDU sessions are provided for user data transport
between the UE and a data network using the 5GC:
M a ster Nod e This type of PDU session carries QoS flows configured with specific 5QI profiles and ARP levels
terminated PDU that prevent the QoS flows from being Secondary Node terminated. This is why all QoS flows
sessions within this type of PDU session are terminated by the Master Node. For such a PDU session, one
user plane tunnel is configured over the NG-U interface for all its QoS flows between the Master
Node and the 5GC.
Secondary Node This type of PDU session carries QoS flows configured with specific 5QI profiles and ARP levels
te r m i n a te d P D U that allow the QoS flow to be Secondary Node terminated. This is why all QoS flows within this
sessions type of PDU session are terminated by the Secondary Node. For such a PDU session, one user
plane tunnel is set up over the NG-U interface for all its QoS flows between the Secondary Node
and the 5GC.
It is possible that a UE connected with NR-DC can use a combination of the two types of PDU sessions. This way a UE
can have some QoS flows that are Secondary Node terminated, while some other QoS flows for the UE remain to be
Master Node terminated.
EPC
5GC
Master Node Secondary Node

terminated terminated
QoS flows QoS flows

PDU session PDU session
Master Node terminated user plane traffic
Secondary Node terminated user plane traffic
L0003099A
2 sur 74 23/04/2024, 07:35

Figure 2 Termination of QoS Flows within PDU Sessions

QoS flows are carried by DRBs between the UE, the Master Node, and the Secondary Node. When the UE is connected
with NR-DC, the UE can be configured with the following bearer types:
M a ster Nod e The Master Node terminated MCG DRBs use only MCG radio resources and the packet processing
t e r m i n a t e d M CG resources of the Master Node. These DRBs transmit user plane traffic between the UE and the
DRBs Master Node. The Master Node terminated MCG DRBs are ciphered and deciphered in the Master
Node.
Secondary Node The Secondary Node terminated split DRBs use MCG and SCG radio resources, and the packet
te r m i n a te d s p l i t processing resources of the Secondary Node. Split DRBs are configured with both the MCG and
DRBs SCG radio resources after Secondary Node Addition. These DRBs are ciphered and deciphered in
the Secondary Node.
EPC
5GC

terminated QoS flows terminated QoS flows
NG-U NG-U
SDAP SDAP

MCG DRB Split DRB
PDCP Xn-U PDCP

(Master key) (Secondary key)
RLC RLC RLC
MAC and Layer 1 MAC and Layer 1
MCG radio resources SCG radio resources
User Plane (Master Node terminated)
User Plane (Secondary Node terminated)
L0003098A
Figure 3 MCG and SCG Radio Resources for User Plane in NR-DC
Rela ted I nform at ion

Termination Point Control of QoS Flows in the Master Node
Bearer Type Change in NR-DC
User Plane Management
Configure 5QI and ARP Levels for QoS Flows Allowed to Be Secondary Node Terminated
2 Dependencies of NR-NR Dual Connectivity

The feature has prerequisites. The UE connected with NR-DC is handled differently when used with a number of
other features. Related features impact NR-DC performance. The feature comes with requirements on the 5GC, the
UE, the number of Baseband units and on the 5QI settings.
Table 1 Feature Dependencies
Fe a t u r e Rela tio n sh ip Description

The NR Standalone feature must be operable on the Master Node, so that
the UE is provided with a PCell on Low-Band or Mid-Band frequencies.
NR Standalone (FAJ 121 If the values of the age threshold for downlink RLC buffer monitoring is set
Prerequisite
5060) higher than the AQM minimum and maximum age thresholds of the TCP
optimization function, the high buffer report might be delayed or prevented
due to discarded user plane packets.
The Master Node and the Secondary Node must be time and phase
IEEE 1588 Time and
synchronized with the same frame start offset by either using GNSS or the
Phase Synchronization Related
IEEE 1588 Time and Phase Synchronization feature. The IEEE 1588 Time
(FAJ 121 2022)
and Phase Synchronization feature is a prerequisite if GNSS is not used.
For A4 measurements aiming for NR-DC setup on High-Band frequencies, a
gapless measurement configuration is applied in the following use cases:
Measurement Gap- – The UE supports independent measurement gap configuration.
Aware NR Scheduling Prerequisite
(FAJ 121 5295) – The measurement gap for High-Band inter-frequency measurements
is disabled for UEs based on the configuration of the
CapabilityHandlingUeCfg.gaplessFr2InterFreqMeasSupp
3 sur 74 23/04/2024, 07:35


attribute.
Otherwise, the measurement gap is configured in the Master Node when an
A4 measurement is started for NR-DC setup.
If the A4 measurement configuration is removed, the measurement gap is
only needed in NR-DC if the Master Node configures other measurements
that require a measurement gap. The measurement gap configuration is
forwarded to the Secondary Node in the following cases:
– At the Secondary Node Addition procedure
– At the Secondary Node initiated Secondary Node Change procedure
– If the measurement gap is changed in NR-DC by using the Master

Node initiated Secondary Node Modification procedure
The Secondary Node does not schedule user data transmission during the
measurement gap that is received from the Master Node.
As specified by 3GPP, measurement gap requirement information reporting
is not supported in NR-DC. This is why measurement gap requirement
information provided by the UE is not used when the UE is configured with
NR-DC.
Independent measurement gap configuration is supported based on UE
capabilities.
The NR Air Interface Protection feature is conflicting with NR-NR Dual
Connectivity on node level.
NR Air Interface If the NR Air Interface Protection feature is enabled on the Master Node,
Protection (FAJ 121 Conflicting NR-DC setup is allowed for the UE but user plane integrity protection
5340) cannot continue in the Secondary Node. This potentially results in user
plane data transmission failure if integrity protection is activated in the UE
before the NR-DC setup.
With the NR Flexible Cell Shaping High-Band feature activated, the UE
NR Flexible Cell Shaping configured with NR-DC can use a different set of SSB beams depending on
High-Band (FAJ 121 Related the movement of the UE and the radio conditions in the SCG. To reconfigure
5441) the UE, the Secondary Node initiates the Secondary Node Modification
procedure.
With the Fronthaul Sharing feature activated, the UE configured with NR-
Fronthaul Sharing (FAJ DC can use a different set of SSB beams depending on the movement of
Related
121 5213) the UE and the radio conditions in the SCG. To reconfigure the UE, the
Secondary Node initiates the Secondary Node Modification procedure.
Carrier aggregation is supported on the Master Node for the UE configured
NR DL Carrier with NR-DC.
Aggregation (FAJ 121 Related When SCells are activated in the MCG before NR-DC is configured, the
5201) offloading can decrease the probability to receive a high buffer report and
therefore decrease the probability to set up NR-DC.
With the Coverage-Optimized Uplink Transmission High-Band feature
Coverage-Optimized
activated, the UE configured with NR-DC can perform uplink dynamic port
Uplink Transmission
Related and waveform switch between CP-OFDM and DFT-s-OFDM when the UE is
High-Band (FAJ 121
at the border of the SCG coverage. To reconfigure the UE, the Secondary
5145)
Node initiates the Secondary Node Modification procedure.
With the Coverage-Optimized Uplink Scheduling High-Band feature
activated, the UE configured with NR-DC can perform uplink dynamic port
and waveform switch between CP-OFDM and DFT-s-OFDM when the UE is
Coverage-Optimized at the border of the SCG coverage.
Uplink Scheduling High- Related The full benefits of the Coverage-Optimized Uplink Scheduling High-Band
Band (FAJ 121 5387) feature are obtained by performing dynamic waveform switch between CP-
OFDM with SCells configured and DFT-s-OFDM with SCells deconfigured
for the uplink SCG radio resources. To reconfigure the UE, the Secondary
Node initiates the Secondary Node Modification procedure.
4 sur 74 23/04/2024, 07:35


In NR-DC, the Secondary Node sends the selected PSCell ID to the Master
Location Support (FAJ
Related Node during the Secondary Node Addition procedure. The Master Node
121 5311)
stores the received PSCell ID.
Even if multiple PSCells are configured in the Secondary Node, only one of
Multiple PSCells High- them can be used for UEs configured with NR-DC. The PSCell-capable
Related
Band (FAJ 121 5341) High-Band frequency used is the one that has a frequency relation
configured to the PCell on the Master Node.
PUCCH resources for the UE configured with NR-DC can be reconfigured to
retain SCG resources when the Secondary Node detects that the UE
Scheduler High-Band
Related attempts to access through RACH under poor radio conditions in the SCG.
(FAJ 121 4904)
To reconfigure the UE, the Secondary Node initiates the Secondary Node
Modification procedure.
UEs connected with NR-DC are released to RRC_IDLE mode instead of
RRC_INACTIVE state at user inactivity.
RRC Inactive State (FAJ
Related The criteria for starting A4 measurements to set up NR-DC are not
121 5328)
reevaluated when the UE resumes RRC_CONNECTED mode after being in
RRC_INACTIVE state.
With the NR RRC Connection Re-establishment feature, the UE configured
with NR-DC falls back to the RRC Connection Establishment procedure
NR RRC Connection Re-
after sending the RRCReestablishmentRequest message.
establishment (FAJ 121 Related
The criteria for starting an A4 measurement to set up NR-DC are not
5346)
reevaluated when the UE performs an RRC Connection Re-establishment
procedure.
The Master Node prevents the UE with NR-DC connection from performing
NR Automated Neighbor
NCGI measurements without checking the relevant UE capabilities.
Relations (FAJ 121 Related
A3 measurement reports are considered during the automatic promotion of
5218)
lightweight neighbor cell relation objects.
For Secondary Node terminated PDU sessions, the Master Node sends the
NR Dynamic QoS
modification request for the QoS properties of already established QoS
Modification (FAJ 121 Related
flows terminated in the Secondary Node using the Secondary Node
5622)
Modification procedure.
The Shared NR RAN feature is not supported to be used with NR-DC.
Shared NR RAN (FAJ
Related Neither the MRL, nor the UE-selected PLMN is considered in PSCell
121 5211)
selection.
RAN Slicing Framework The supported S-NSSAI list of the Secondary Node is not considered at
Related
(FAJ 121 5095) PSCell selection.
NR Mobility (FAJ 121 All inter-gNodeB handovers for UEs that are connected with NR-DC are
Related
5041) performed using NG-based handover.
The LTE-NR Dual Connectivity feature provides the means of configuring
the following functions also used in NR-DC:
– The primary path of uplink user data
LTE-NR Dual – The switching of downlink MCG and SCG radio resources of the
Connectivity (FAJ 121 Related Secondary Node terminated split DRB
4908)
– The switching of uplink MCG and SCG radio resources of the
Secondary Node terminated split DRB
The configurable attributes to control the functions in EN-DC are also used
in NR-DC.
The LTE-NR Downlink Aggregation feature provides the means of
LTE-NR Downlink configuring the following functions also used in NR-DC:
Aggregation (FAJ 121 Related – The downlink PDCP aggregation of the MCG and SCG radio
4912) resources
5 sur 74 23/04/2024, 07:35


– The flow control mechanism
The configurable attributes to control the functions in EN-DC are also used
in NR-DC.
The LTE-NR Uplink Aggregation feature provides the means of configuring
whether uplink user data is aggregated over both the MCG and SCG radio
resources in NR-DC. The configurable attribute to control the function in
LTE-NR Uplink
EN-DC is also used in NR-DC.
Aggregation (FAJ 121 Related
Uplink PDCP aggregation is disabled for NR-DC UEs when the primary data
5091)
path is MCG. The MCG aggregation threshold that is introduced by the
coverage-controlled uplink PDCP aggregation function is not used for NR-
DC UEs.
NR 4CC DL Carrier
The NR 4CC DL Carrier Aggregation High-Band feature enables up to four
Aggregation High-Band Related
downlink component carriers for the SCG on the Secondary Node.
(FAJ 121 4902)
NR 8CC DL Carrier
The NR 8CC DL Carrier Aggregation High-Band feature enables up to eight
downlink component carriers for the SCG on the Secondary Node.
(FAJ 121 4964)
NR Uplink Carrier
The NR Uplink Carrier Aggregation High-Band feature enables uplink
carrier aggregation for the SCG on the Secondary Node.
(FAJ 121 5092)
EPS Fallback for IMS At voice calls, the UE connected with NR-DC is possible to be redirected or
Related
Voice (FAJ 121 5059) handed over to LTE.
NR Emergency Fallback At emergency calls, the UE connected with NR-DC is possible to be
Related
to LTE (FAJ 121 5166) redirected to LTE.
The Secondary Node Addition and the Secondary Node Release procedures
can be performed with minimum user data interruption of Master Node
Basic Voice over NR
Related terminated PDU sessions. Therefore, the split DRBs for QoS flows in the
(FAJ 121 5219)
Secondary Node terminated PDU sessions are kept during a VoNR call for
UEs in High-Band coverage.
DRBs that are set up for IMS signaling, voice and latency-sensitive services
are automatically configured not to be set up as Secondary Node
terminated split DRBs.
The NrdcSnTermination = SnTerminationProhibited MO instance
is still possible to be manually overridden to allow Secondary Node
termination of such services. In case of manual override, the NR Robust
NR Robust Header Header Compression for Voice feature, activated on the Master Node, still
Compression for Voice Related prohibits the Secondary Node termination of DRBs for IMS signaling, voice
(FAJ 121 5400) and latency-sensitive services in either of the following ways:
– The received A4 measurement report to establish Secondary Node
terminated split DRBs for such services is ignored.
– The Master Node does not start downlink RLC buffer monitoring of
Secondary Node terminated split DRBs for such services.
Advanced Downlink For UEs configured with NR-DC, most of the traffic is transmitted through
Single-User MIMO Mid- Related the SCG, therefore, the benefit of the enhanced SRS resource allocation
Band (FAJ 121 5262) function is less visible.
The Multi-Layer Coordination and the Bandwidth-Triggered Inter-System
Handover functions of the NR Traffic Steering feature are not triggered if
NR-DC can be established for the NR-DC-capable UE.
NR Traffic Steering (FAJ If NR-DC can be established but no High-Band cells are in coverage, the
Related Multi-Layer Coordination and the Bandwidth-Triggered Inter-System
121 5458)
Handover functions can be triggered.
The Dynamic Cell Set Change during Mobility function does not trigger any
immediate traffic steering at UE Setup or RRC Resume if NR-DC can be
6 sur 74 23/04/2024, 07:35


established.
If the Secondary Node in NR-DC is configured when the periodic interval for
Dynamic Cell Set Change during Mobility function elapses, no traffic
steering procedure is initiated.
If the Secondary Node in NR-DC is established, the Multi-Layer
Coordination procedure stops.
The following function are adapted to the UE Grouping Framework:
– NR-DC enabler
– A4 measurement configuration
UE Grouping Framework
Related
(FAJ 121 5314) – Downlink RLC buffer monitoring
– Secondary Node termination of QoS flows
– Intra-Frequency Mobility Control in the Secondary Node

NR 3CC DL Carrier with NR-DC.
NR 4CC DL Carrier with NR-DC.
NR DL Carrier
with NR-DC.
Aggregation for
Related When SCells are activated in the MCG before NR-DC is configured, the
Coverage Extension
offloading can decrease the probability to receive a high buffer report and
(FAJ 121 5202)
TDD PCell Support for
with NR-DC.
DL Carrier Aggregation
Related When SCells are activated in the MCG before NR-DC is configured, the
Low/Mid-Band (FAJ 121
offloading can decrease the probability to receive a high buffer report and
5363)
During UE overheating, all active SCells are deactivated. SCell reactivation
NR UE-Assisted is not allowed until the overheating condition is mitigated. If the UE
Overheating Mitigation Related preference is to release the Secondary Node to mitigate the overheating, a
(FAJ 121 5449) check is performed to prevent Secondary Node addition before the
overheating condition is mitigated.
NR 256-QAM Downlink The NR 256-QAM Downlink High-Band feature enables 256-QAM
High-Band (FAJ 121 Related modulation order for High-Band carriers configured in the SCG on the
5476) Secondary Node.
The DRX configuration of the MCG is forwarded to the Secondary Node at
the Secondary Node Addition and the Secondary Node initiated Secondary
Connected Mode DRX
Related Node Change procedures. The Secondary Node aligns the DRX
(FAJ 121 4963)
configuration of the SCG with the DRX configuration of the MCG based on
the received information.
In NR-DC, measurement gap configuration can change in the Master Node
because of UE group changes that are triggered by one of the following
User- and Service- procedures:
Specific Mobility (FAJ Related
– PDU Session Resource Setup
121 5399)
– PDU Session Resource Modify
7 sur 74 23/04/2024, 07:35


– PDU Session Resource Release
If the measurement gap configuration is updated this way, it is not
forwarded to the Secondary Node.
NR QoS Profile
QoS profile modification is supported for UEs in the PCell on the Master
Modification (FAJ 121 Related
Node only.
5503)
NR Dynamic Power
When the NR-NR Dual Connectivity feature is active, the power-saving
Optimizer (FAJ 121 Related
mode is suspended.
5443)
User- and Service-
Specific Carrier During initial configuration, the SCell selection in MCG and SCG uses the
Related
Aggregation (FAJ 121 attributes introduced for carrier aggregation configurations.
5555)
H a rd wa re
NR-DC is not supported if the Master Node and the Secondary Node are located in the same Baseband.
Limitations
No known limitations.
N e t wo r k Re q u i re m e nt s
– The UE must be capable of NR-DC and compliant with the 15.6.0 or later version of the RRC protocol.
– The AMF in the 5GC must support the PDU Session Resource Modify Indication procedure compliant with the
15.8.0 or later version of the NGAP protocol.
– The RLC mode for a specific 5QI must be set to the same value in both the Master Node and in the Secondary
Node. In both of the nodes, the RLC mode for a 5QI is set using the CUCP5qi.rlcMode attribute under the
CUCP5qiTable MO for the corresponding 5QI.
3 Feature Operation of NR-NR Dual Connectivity

3.1 Master Node Criteria for NR-DC Setup
The criteria for NR-DC setup are evaluated in the Master Node for the following cases:
– At Initial Context Setup
– At the PDU Session Resource Setup procedure
– At the PDU Session Resource Modify procedure
– At the PDU Session Resource Release procedure
– At an incoming handover to the Master Node
– At both the Master Node Initiated and the Secondary Node Initiated Secondary Node Release procedures
An A4 measurement is used to detect that the UE is in High-Band coverage. The purpose of this inter-frequency
measurement is that the UE finds a candidate PSCell cell on a High-Band frequency to establish NR-DC.
Downlink RLC buffer monitoring makes it possible to trigger the NR-DC setup based on UE traffic level in the downlink
RLC buffer. Through buffer-based NR-DC setup, unnecessary NR-DC setups can be avoided for UEs with short data
sessions.
Figure 4 shows the operational flow of evaluating the NR-DC setup criteria.
8 sur 74 23/04/2024, 07:35

Start
Are A4 measurement criteria No A4 measurement

fulfilled? is not started
Yes
No Are criteria to start downlink

RLC buffer monitoring fulfilled?
Yes
Downlink RLC buffer

monitoring starts
No
Downlink RLC buffer
Is high buffer report received?
monitoring continues
Yes
Are A4 measurement criteria No A4 measurement

fulfilled? is not started
Yes
A4 measurement starts
A4 measurement report
is received
evaluation
NR-DC setup
is allowed
L0003485A
Figure 4 Operational Flow of Evaluating the NR-DC Setup Criteria

NR-DC Band Combination Selection
PDU Session Resource Setup Procedure
PDU Session Resource Modify Procedure
PDU Session Resource Release Procedure
Master Node Initiated Secondary Node Release
Secondary Node Initiated Secondary Node Release
Incoming IRAT Handover from LTE into an NR-DC-Capable PCell
3.1.1 A4 Measurement Criteria
The following conditions must be fulfilled for the Master Node to configure the UE to start A4 measurements for the
NR-DC setup:
– The NR-NR Dual Connectivity feature is activated and operable on the Master Node.
– The NrdcMnCellProfileUeCfg.nrdcEnabled attribute is set to true in the instance of the cell MO that
represents the PCell on the Master Node.
– At least one established PDU session is allowed by configuration to be Secondary Node terminated.
– A measurement object, the SSB on one High-Band frequency, can be selected with all the following conditions
being fulfilled:
• The frequency of the measurement object is represented by an NRFrequency MO instance.
• At least one NRFreqRelation MO instance must exist from the NRCellCU MO instance representing the
PCell to the NRFrequency MO instance representing the High-Band frequency of the measurement object.
Note: The NRFreqRelation MO instance between the PCell and the High-Band frequency must be created
manually.
• The UE is capable of at least one combination that supports NR-DC of the following bands:
– At least one band of the PCell frequency.
– At least one band of the NRFrequency MO representing the High-Band frequency of the measurement
object.
Such band combinations are checked against the list of the allowed band combinations. If the list exists, it
contains the band combinations filtered by the operating band of the PCell frequency. If not, all bands of the
PCell frequency are considered.
If multiple instances of the NRFrequency MO exist with different High-Band frequencies, the one with the
lowest NR-ARFCN is selected.
Figure 5 shows the Master Node MO structure with relations considered for A4 measurements.
9 sur 74 23/04/2024, 07:35

Master Node MO Structure Secondary Node MO Structure

on the Master Node
GNBCUCPFunction
NRCellCU NRNetwork ExternalGNBCUCPFunction
A
NRFrequency ExternalNRCellCU
C B
NRFreqRelation NRFrequency
D
E
F
NRCellRelation
TermPointToGNodeB
A NRCellCU.nRFrequencyRef D NRFreqRelation.nRFrequencyRef
B ExternalNRCellCU.nRFrequencyRef E NRCellRelation.nRFreqRelationRef
C NRCellRelation.nRCellRef F NRCellRelation.nRCellRef
Parent-Child Connection Reference Connection
L0003100A
Figure 5 Master Node MO Structure with Relations Considered for A4 Measurements

3.1.2 Downlink RLC Buffer Monitoring
Downlink RLC buffer monitoring is used for monitoring the downlink RLC buffer based on the following conditions:
– The age of the oldest SDU packet in the RLC queue, which is configured through the
NrdcMnCellProfileUeCfg.nrdcSetupDlPktAgeThr attribute.
– The volume of the packets in the RLC queue, which is configured through the
NrdcMnCellProfileUeCfg.nrdcSetupDlPktVolThr attribute.
If all the preconditions for starting an A4 measurement are met, the Master Node can start the downlink RLC buffer
monitoring. This depends on the following conditions:
– The NrdcMnCellProfileUeCfg.nrdcSetupDlPktAgeThr attribute or the

NrdcMnCellProfileUeCfg.nrdcSetupDlPktVolThr, or both are configured with a value greater than 0.
– High buffer status is not set.
Note: High buffer status indicates whether the threshold attributes are exceeded during downlink RLC buffer
monitoring. If both threshold attributes are configured, high buffer status is set only when both
thresholds are exceeded. If only one of the threshold attributes is configured, high buffer status is set
when that threshold is exceeded.
Buffer monitoring is only applied to DRBs that are allowed to be set up as Secondary Node terminated DRBs by
configuration. If both of the threshold attributes are configured, high buffer status is reported only when both
thresholds are exceeded for one of the DRBs. If only one of the threshold attributes is configured, high buffer status is
reported when this threshold is exceeded for one of the DRBs. When high buffer status has been reported for one DRB,
buffer measurement stops for all other DRBs for a specific UE.
3.1.3 A4 Measurement Configuration

The A4 measurement is configured for the UE during the RRC Reconfiguration procedure to have the SSB on one High-
Band frequency as the measurement object.
The trigger quantity for the A4 measurement is RSRP, and the measurement is started and stopped periodically. The
measurement time is the sum of the NrdcMnCellProfileUeCfg.nrdcMeasTime attribute value and the value set in
the timeToTrigger member of the NrdcMnCellProfileUeCfg.rsrpPSCellCandidate attribute. The
measurement interval, while the measurement is halted, is configured by using the
NrdcMnCellProfileUeCfg.nrdcMeasRestartTime attribute. This configurable periodicity of the measurement
provides a means of limiting UE battery consumption. The A4 measurement is stopped and removed from the UE
configuration at the Secondary Node Addition procedure. No A4 measurement is started while the UE is connected with
NR-DC. When the Secondary Node Release procedure is triggered, either by the Master Node or the Secondary Node,
the A4 measurement restarts.
Note: Downlink RLC buffer monitoring is not requested at A4 measurement interval expiration.
10 sur 74 23/04/2024, 07:35

Measurement Measurement
time time
Measurement NR-DC configured Measurement

interval interval
Time [sec]
Start Remove 1. Master Node receives

Master Node or Secondary Node
A4 Measurement A4 Measurement 2. Secondary Node Addition
initiated Secondary Node Release
Remove Start
A4 Measurement A4 Measurement
L0003103D
Figure 6 A4 Measurement Handling and Periodicity

A4 measurements are performed as gapless measurements for the following UEs:
– UEs that support independent measurement gap configuration
– UEs for which the value of the CapabilityHandlingUeCfg.gaplessFr2InterFreqMeasSupp attribute is

set to true
Otherwise, the measurement gap is configured on all frequencies.

The NrdcMnCellProfileUeCfg.rsrpPSCellCandidate attribute contains the following configurable members
for the A4 measurement:
threshold If the RSRP of any cells on the measured High-Band frequency is above this configured threshold,
the UE sends an A4 measurement report to the Master Node.
hysteresis The hysteresis is used to prevent the retriggering of an A4 measurement report if the measured
value fluctuates close to the configured threshold.
timeToTrigger The value defines how long the threshold criteria must be fulfilled before triggering an A4
measurement report.
3.1.4 Evaluation of A4 Measurement Repor t
The UE sends the A4 measurement report to the Master Node in the RRC MeasurementReport message. The
measurement report contains only one PCI that belongs to the neighbor cell with the best RSRP value on the measured
High-Band frequency. If the following criteria are met, the Master Node initiates the Secondary Node Addition
procedure to the gNodeB hosting the PSCell candidate the UE reported:
– The reported PCI can be mapped to an existing ExternalNRCellCU MO instance representing the PSCell
candidate on the measured High-Band frequency. The MO is a child to the ExternalGNBCUCPFunction MO
representing the Secondary Node in the MO structure of the Master Node.
– One NRCellRelation MO instance exists between the ExternalNRCellCU MO and the NRCellCU MO
instance that represents the serving PCell on the Master Node.
Note: The NRCellRelation MO instance between the NRCellCU and ExternalNRCellCU MOs must be
created manually.
– At least one band combination exists in the list of allowed band combinations that contains the band of the
found PSCell candidate.
– A PDU session exists for this UE that is allowed to be Secondary Node terminated by configuration.
– A connection over the Xn interface exists between the Master Node hosting the PCell and the Secondary Node
hosting the PSCell candidate. The connection is represented by a TermPointToGNodeB MO instance. The MO is
a child to the ExternalGNBCUCPFunction MO representing the Secondary Node in the MO structure of the
Master Node. For the connection to be functional, the TermPointToGNodeB.administrativeState
attribute must be set to UNLOCKED and the TermPointToGNodeB.operationalState attribute must display
ENABLED.
11 sur 74 23/04/2024, 07:35


Secondary Node Addition
3.2 Termination Point Control of QoS Flows in the Master Node
For each QoS flow, the 5GC provides a 5QI value and an ARP value. These values are compared to a framework of 5QI
profiles and the configuration of Secondary Node termination to determine whether a QoS flow is allowed to be
Secondary Node terminated or not.
GNBCUCPFunction
NrdcSnTermination CUCP5qiTable
defaultNrdcSnTerm
NrdcSnTerminationUeCfg
CUCP5qi
nrdcSnTermAllowed
nrdcSnTerminationRef
Legend
Reference Connection
Affected MOs and parameters
L0003142A
Figure 7 MO Structure for Controlling Secondary Node Termination of QoS Flows
The CUCP5qi MO instance under the CUCP5qiTable MO contains the configuration of a specific 5QI profile. The
CUCP5qi.nrdcSnTerminationRef attribute can contain a reference to an NrdcSnTermination MO instance.
The NrdcSnTermination MO has the NrdcSnTerminationUeCfg MO as its child. The NrdcSnTermination and
the NrdcSnTerminationUeCfg MOs are both defined by the operator or created automatically. The
NrdcSnTerminationUeCfg.nrdcSnTermAllowed attribute is used to apply different settings for each ARP
applicable to the 5QI profile referencing the parent NrdcSnTermination MO instance. The attribute is configured to
control whether a QoS flow with the 5QI profile is allowed to be Secondary Node terminated or not.
Note: The NrdcSnTermination = SnTerminationProhibited MO instance is automatically created with a child
NrdcSnTerminationUeCfg = Base MO instance. The NrdcSnTermination =
SnTerminationProhibited MO instance with a child NrdcSnTerminationUeCfg = Base MO instance
prohibits QoS flows for IMS signaling, voice, and latency-sensitive services to be terminated by the Secondary
Node. It is recommended that this MO instance is used for such services, so that no manual configuration is
needed.
If the CUCP5qi.nrdcSnTerminationRef attribute is empty, any of the following cases is applicable:
– If it exists, the automatically created NrdcSnTermination = SnTerminationProhibited MO instance with

a child NrdcSnTerminationUeCfg = Base MO instance is used for the following services:
• IMS signaling
• Voice services
• Latency-sensitive services
– If it exists, the NrdcSnTermination MO instance with the NrdcSnTermination.defaultNrdcSnTerm

attribute set to true is used for services other than IMS signaling, voice services, or latency-sensitive services.
If no instance set as default of the NrdcSnTermination MO exists, the QoS flow with the specific 5QI is not
allowed to be Secondary Node terminated.
A PDU session is allowed to be Secondary Node terminated if all of its QoS flows are allowed to be Secondary Node
terminated. By controlling QoS flow termination, a UE can use a combination of different types of PDU sessions. One
type of PDU session has only Master Node terminated QoS flows, while the other has only Secondary Node terminated
QoS flows. The same configuration, whether Secondary Node termination is allowed or not, is recommended for all QoS
flows in the same PDU session.
12 sur 74 23/04/2024, 07:35


3.3 Bearer Type Change in NR-DC
A bearer type change is when one type of DRB is reconfigured into the other. This occurs at different NR-DC procedures
that trigger DRB reconfiguration. Bearer type changes exist between the following types of DRBs supported in NR-DC:
– Master Node terminated MCG DRB
– Secondary Node terminated split DRB
The NR-DC-capable UE can be in one of the following states depending on the DRB type it uses:
Idle Mode The UE is in RRC_IDLE mode.
C o nn e cted M od e The UE is connected to the Master Node using one or more Master Node terminated MCG DRBs
w i t h N R- D C N o t only. Therefore, user plane traffic is transmitted through the Master Node only.
C o nfi g u red At this stage, if all the criteria for starting an A4 measurement are met, the UE is configured by the
Master Node to start A4 measurements to find a candidate PSCell on a High-Band frequency.
At the reception of the A4 measurement report, the Master Node initiates the Secondary Node
Addition procedure, if all the criteria for the procedure are met. During the Secondary Node
Addition procedure, one or more Master Node terminated MCG DRBs that are allowed to be split
by configuration are reconfigured to become Secondary Node terminated split DRBs.
C o nn e cted M od e The UE is connected in NR-DC both to the Master Node and the Secondary Node. The UE can use
w i t h N R- D C the following bearer types depending on the 5QI and ARP configuration of the QoS flows the
C o nfi g u red DRBs carry:
– One or more Secondary Node terminated split DRBs.
– A combination of one or more Master Node terminated MCG DRBs and one or more
Secondary Node terminated split DRBs.
Different scenarios can trigger the Master Node initiated or the Secondary Node initiated
Secondary Node Release procedure. The result is that the Secondary Node resources for the UE
are released. Secondary Node terminated split DRBs are reconfigured into Master Node
terminated MCG DRBs. The UE remains connected to the Master Node.
The UE can be released to RRC_IDLE mode when connected in NR-DC.
The different UE state changes and the NR-DC procedures that trigger bearer type changes are shown in Figure 8.
A4 Measurement-based
Initial Context Setup Secondary Node Addition
Connected Mode with Connected Mode with

Idle Mode
NR-DC Not Configured NR-DC Configured
RRC Connection Release Master Node or Secondary Node

initiated Secondary Node Release
RRC Connection Release
L0003102B
Figure 8 UE State Changes at NR-DC Procedures

NR-DC Deployment
Incoming Handover into a New PCell
13 sur 74 23/04/2024, 07:35


3.4 User Plane Management
With the Secondary Node resources available to the UE, the bearer type can be changed from Master Node terminated
DRBs to Secondary Node terminated split DRBs. For Secondary Node terminated split DRBs, the user plane provided to
the UE is set up in the following ways:
– Downlink traffic is transmitted through the MCG or SCG radio resources of the Secondary Node terminated split
DRB depending on the High-Band downlink radio link quality. Downlink data can be aggregated over both the
MCG and SCG radio resources depending on the amount of data.
– Uplink traffic is transmitted either through the MCG or SCG radio resources of the Secondary Node terminated
split DRB. The uplink data path through which the uplink traffic is transmitted is based initially on configuration
and then the High-Band uplink radio link quality. Uplink user data can be aggregated over both the MCG and
SCG radio resources depending on the following variables:
• The amount of user data.
• The UE capability to support splitting of uplink PDCP data on both the MCG and SCG for the Secondary Node
terminated split DRB.
• The configuration of the uplink data split threshold.
The uplink PDCP aggregation function is enabled for NR-DC UEs only if the primary uplink data path is SCG.
The different user plane management functions used in NR-DC are provided by the following features operable on the
Secondary Node:
– The LTE-NR Dual Connectivity provides the means of configuring the following functions also used in NR-DC:
• The initial primary path of uplink user data
• The switching of downlink MCG and SCG radio resources of the Secondary Node terminated split DRB
• The switching of uplink MCG and SCG radio resources of the Secondary Node terminated split DRB
– The LTE-NR Uplink Aggregation provides the means of configuring whether uplink user data is aggregated over
both the MCG and SCG radio resources in NR-DC. The uplink data split threshold attribute
QciProfileEndcConfigExt.ulDataSplitThresholdMcg that is intended for cases in which the primary
path is MCG is not used for NR-DC UEs.
– The LTE-NR Downlink Aggregation provides the means of configuring the following functions also used in NR-
DC:
• The downlink aggregation of the MCG and SCG radio resources
• The flow control mechanism

Parameters for NR-NR Dual Connectivity
Secondary Node Initiated Secondary Node Modification
LTE-NR Dual Connectivity
LTE-NR Uplink Aggregation
LTE-NR Downlink Aggregation
3.5 NR-DC Band Combination Selection
The band combination and feature set are selected among the allowed ones to maximize SCG carrier aggregation and
optimize Layer 1 and Layer 2 configuration. Band combinations contain the operating bands of the PCell frequency and
14 sur 74 23/04/2024, 07:35

the SCG frequencies that support NR-DC. The UE support of the different band combinations and feature sets is
signaled in the NR-DC-specific UE capabilities.
The Master Node requests the NR-DC-specific UE capabilities (if not received from the AMF) from the UE at Initial
Context Setup. A candidate PSCell is considered if the UE is capable of a band combination supporting NR-DC that
contains the following:
– The band of the PCell frequency
– The band of the High-Band frequency of the candidate PSCell
Band combination and feature set selection is a distributed function between the Master Node and the Secondary Node
according to the following steps:
1. The Master Node assembles a list of allowed band combinations based on the reported NR-DC-specific UE
capabilities. This list contains the band combinations that fulfill the following criteria:
– The band combination contains the PCell frequency band and it supports NR-DC.
– The band combination and the feature set support any of the possible PCell configurations.
Note: A PCell configuration is possible if it is supported by the cell capabilities of the PCell, such as the number
of MIMO layers, bandwidth, and modulation that the PCell can handle.
The generation of the allowed band combination list in the Master Node can result in one of the following outcomes:
– If the list is not empty and it contains the High-Band frequency of the latest A4 measurement report in at least
one band combination supporting NR-DC for the UE, the Secondary Node Addition procedure can be triggered.
– The list is not empty, but it does not contain the High-Band frequency of the latest A4 measurement report in any
band combinations supporting NR-DC for the UE. In this case, the Master Node does not trigger the Secondary
Node Addition procedure at the reception of an A4 measurement report. However, subsequent A4 measurements
can start.
– If the list is empty, the Master Node does not trigger the Secondary Node Addition procedure at the reception of
an A4 measurement report. In addition, no subsequent A4 measurement is started while the UE remains in
connected mode in the same PCell.
2. The Master Node signals the list of allowed band combinations to the Secondary Node at the Secondary Node
Addition and Secondary Node initiated Secondary Node Change procedures using the XnAP S-NODE ADDITION
REQUEST message.
3. At the reception of the XnAP S-NODE ADDITION REQUEST message, the Secondary Node uses the list of allowed
band combinations and NR-DC-specific UE capabilities to select the best possible cell set for the SCG. It selects, for
example, the number of carrier components, the MIMO layers and the type of modulation in a way that maximizes
the Secondary Node throughput.
4. The Secondary Node signals the SCG configuration to the Master Node using the XnAP S-NODE ADDITION
REQUEST ACKNOWLEDGE message.
5. At the reception of the XnAP S-NODE ADDITION REQUEST ACKNOWLEDGE message, the Master Node selects the
best possible cell set for the MCG given the SCG configuration provided by the Secondary Node. This can involve the
following actions:
– The Master Node reconfigures the PCell.
– The Master Node adds or removes SCells from the MCG if carrier aggregation is applied on the Master Node.

A4 Measurement Criteria
Evaluation of A4 Measurement Report
15 sur 74 23/04/2024, 07:35


3GPP TS 38.101-3; NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2
Interworking operation with other radios
3.6 User Activity Supervision
For the UE configured with NR-DC, both the Master Node and the Secondary Node monitor user activity. The Master
Node does it on UE level, considering the overall UE state of being active or inactive.
The PDCP layer in the Master Node monitors the activity of all the Master Node terminated MCG DRBs for the UE. The
DRB is inactive if it is not used for user data transmission during the time period defined by the inactivity timer set on
the Master Node in the InactivityProfileUeCfg.tInactivityTimer attribute.
The Master Node also monitors if NAS RRC messages are sent or received during the time period defined by the NAS
inactivity timer. The timer is set in the Master Node using the GNBCUCPFunction.nasInactivityTime attribute
expires.
The PDCP layer in the Secondary Node monitors the activity of all Secondary Node terminated split DRBs. These DRBs
are inactive if they are not used for user data transmission for the time value of the
InactivityProfileUeCfg.tInactivityTimerNrdcSn attribute. When the Secondary Node detects that the
activity state of the Secondary Node terminated split DRBs change (from active to inactive or from inactive to active), it
sends the XnAP ACTIVITY NOTIFICATION message to the Master Node. This message is used to notify the Master
Node about the activity state of the Secondary Node terminated split DRBs for the UE.
High buffer status indicated by downlink RLC buffer monitoring in the Master Node is cleared if the Secondary Node
indicates the inactivity of Secondary Node terminated DRBs.
GNBCUCPFunction.nasInactivityTime
NAS RRC message

sent or received
Master Node
terminated MCG DRBs Inactivity timer
active/inactive
A Secondary Node
InactivityProfileUeCfg.tInactivityTimer terminated Split DRBs
active/inactive
Xn-C interface
User activity supervision in NR-DC A XnAP ACTIVITY NOTIFICATION
L0003117B
Figure 9 User Activity Supervision in NR-DC

The Master Node releases the UE to RRC_IDLE mode when all the following criteria are fulfilled:
– The Master Node terminated MCG DRBs are inactive as indicated by the expired inactivity timer.
– The Secondary Node terminated split DRBs are inactive as indicated by the notification from the Secondary
Node.
– No NAS RRC messages are sent or received during the configured time period.

UE Released to Idle Mode
3.7 Xn Link Break Handling
An Xn link break occurs when the connection between the Master Node and the Secondary Node is lost over the Xn-C
interface. The Xn link break can typically be caused by any of the following cases:
– Transport failure occurs over the Xn interface.
16 sur 74 23/04/2024, 07:35

– Either the Master Node or the Secondary Node restarts or is not operational.
– The local termination point of the Xn interface on the Master Node or on the Secondary Node is locked. This
occurs when the TermPointToGNodeB.administrativeState attribute is set to LOCKED.
UE Master Node Secondary Node AMF
Xn link
break
1. Xn link break detected 1. Xn link break detected
UEs with Secondary Node terminated split DRBs using the Xn link
2. NG Reset procedure
NGAP NG RESET
3. RRC RRCConnectionRelease
NGAP NG RESET ACKNOWLEDGE
4. Local resource cleanup 4. Local resource cleanup
5. Xn link recovery
L0003114A
Figure 10 Sequence of Xn Link Break Handling at Lost Xn Connection

The Xn link break handling in NR-DC is done according to the following sequence:
1. The Xn link break is detected both in the Master Node and the Secondary Node independently.
When the Xn link break is caused by setting the TermPointToGNodeB.administrativeState attribute to

LOCKED, the SCTP association shuts down for transport over the Xn interface before the detection of the Xn link
break. The TermPointToGNodeB.operationalState attribute displays DISABLED. If the termination point is
locked on the Master Node, it is the Master Node that shuts down the SCTP association. If the termination point is
locked on the Secondary Node, it is the Secondary Node that shuts down the SCTP association.
2. The NG Reset procedure is used between the Master Node and the AMF.
a. The Master Node sends the NGAP NG RESET message to the AMF. This message contains the list of UEs using
Secondary Node terminated split DRBs served by the broken Xn link. The message indicates the release of all the
affected UEs.
b. The AMF responds to the Master Node with the NGAP NG RESET ACKNOWLEDGE message.
3. The Master Node initiates the release of all UEs served by the broken Xn link to RRC_IDLE mode. This is triggered
when the Master Node sends the RRC RRCConnectionRelease message to the affected UEs.
4. All the MCG and the SCG radio resources of the Secondary Node terminated split DRBs, as well as all other UE-
specific resources, allocated to the affected UEs are locally released. This occurs in both the Master Node and the
Secondary Node simultaneously.
5. The Master Node and the Secondary Node initiate new Xn link setup attempts independently to restore connection
over the Xn interface. However, when the Xn link break is caused by locking the termination point, no Xn link re-
establishment is initiated either by the Master Node or the Secondary Node.
The XnC Link to GNodeB Failure alarm is raised on both the Master Node and the Secondary Node at Xn link
break. However, when the Xn link break is caused by locking the termination point, no alarm is raised either on the
Master Node or on the Secondary Node.

Detection of an Xn Link Break in the Master Node
XnC Link to GNodeB Failure
3.8 Master Node Mobility Support in NR-DC
3.8.1 Intra-gNodeB Handover When NR-DC Is Configured
The following intra-gNodeB mobility cases are supported in NR-DC for the Master Node:
17 sur 74 23/04/2024, 07:35

– Intra-frequency intra-gNodeB handover
– Inter-frequency intra-gNodeB handover
The intra-gNodeB handover follows the procedure of the NR Mobility feature. However, when used in NR-DC, the
Master Node initiated Secondary Node Release procedure is performed during handover.
After sending the RRC RRCReconfiguration to the UE, the Master Node initiates the Secondary Node Release
procedure. With it, all PDU sessions for the UE that are Secondary Node terminated in the source cell are reconfigured
to be Master Node terminated in the target cell. PDU sessions that are already Master Node terminated are kept. If
Xn-U downlink TEIDs are provided, packet forwarding is performed for the Secondary Node terminated PDU sessions.
After the UE responds to the Master Node with the RRC RRCReconfigurationComplete message, the Master Node
uses the PDU Session Resource Modify Indication procedure to notify the AMF of the new NG-U downlink TEIDs
provided during the Secondary Node Release procedure.
The Master Node either configures the UE in the target cell to perform A4 measurements or it configures downlink RLC
buffer monitoring. The aim is to find a candidate PSCell for the Secondary Node Addition procedure.

Outgoing Intra-System Handover from the Source Cell
Reception of an A4 Measurement Report
Master Node Criteria for NR-DC Setup
NR Mobility
3.8.2 Inter-gNodeB Handover When NR-DC Is Configured
The following inter-gNodeB mobility cases are supported in NR-DC for the Master Node over the NG interface:
– Intra-frequency inter-gNodeB, NG-based handover
– Inter-frequency inter-gNodeB, NG-based handover
The inter-gNodeB, NG-based handover follows the procedure of the NR Mobility feature. However, when used in NR-
DC, the Master Node initiated Secondary Node Release procedure is performed during the handover.
After sending the RRC RRCReconfiguration to the UE, the source Master Node initiates the Secondary Node
Release procedure. With it, all PDU sessions for the UE, regardless if Secondary Node or Master Node terminated, are
moved from the source Master Node to the target gNodeB. On the target gNodeB, all the moved PDU sessions are
reconfigured to be Master Node terminated. If Xn-U downlink TEIDs are provided, packet forwarding is performed for
the Secondary Node terminated PDU sessions from the Secondary Node to the target gNodeB. Packet forwarding is
also performed for Master Node terminated PDU session from the source Master Node to the target gNodeB.
After the Secondary Node Release procedure, the source Master Node sends the NGAP UPLINK RAN STATUS
TRANSFER message to the AMF. The message contains the combined PDCP COUNT values from the source Master Node
and the Secondary Node for AM DRBs.
The Master Node either configures the UE in the target cell to perform A4 measurements or it configures downlink RLC
buffer monitoring. The aim is to find a candidate PSCell for the Secondary Node Addition procedure.

NR Mobility
3.8.3 IRAT Handover to LTE When NR-DC Is Configured
18 sur 74 23/04/2024, 07:35

The IRAT handover to LTE follows the procedure of the NR Mobility feature. However, when used in NR-DC, the Master
Node initiates the UE context release to the Secondary Node.

Outgoing IRAT Handover from the Master Node
Master Node Initiated UE Context Release
NR Mobility
3.8.4 Incoming IRAT Handover from LTE into an NR-DC-Capable P Cell
The handling of the incoming IRAT handover from LTE follows the procedure of the NR Mobility feature. The target
gNodeB, acting as the Master Node, either configures the UE to perform A4 measurements or it configures downlink
RLC buffer monitoring. The aim is to find a candidate PSCell for the Secondary Node Addition procedure.

NR Mobility
3.9 Secondary Node Mobility Support in NR-DC
3.9.1 Intra-Frequenc y, Inter-gNodeB PSCell Change When NR-DC Is Configured
For the UE connected with NR-DC, intra-frequency, inter-gNodeB PSCell change is supported while intra-frequency,
intra-gNB PSCell change is not. The A3 measurement for the event that triggers intra-frequency, inter-gNodeB PSCell
change is configured on the Secondary Node by using the following attributes:
– IntraFreqMCCellProfileUeCfg.betterSpCellTriggerQuantity
– IntraFreqMCCellProfileUeCfg.rsrpBetterSpCell
The attribute contains the following configurable members:
• hysteresis
• offset
• timeToTrigger
– IntraFreqMCCellProfileUeCfg.rsrqBetterSpCell
• hysteresis
• offset
• timeToTrigger
The UE performs A3 measurements on the frequency of the PSCell to find a High-Band cell with better radio link quality
to be the candidate for PSCell change. The A3 measurement configuration is transmitted to the UE at the Secondary
Node Addition procedure that is triggered either by initial NR-DC setup, or inter-gNodeB PSCell change. If the UE finds
a High-Band cell that has better radio link quality than the serving PSCell based on the configuration, the A3 Event is
triggered.
The UE sends the A3 measurement report to the Master Node and the Master Node forwards the A3 measurement
report to the source Secondary Node where the report is evaluated. If the reported PCI is a known external neighbor in
the Secondary Node, intra-frequency, inter-gNodeB PSCell change is triggered by using the Secondary Node Initiated
Secondary Node Change procedure. The A3 measurement report is ignored if the PCI is unknown or it is a known
internal neighbor in the source Secondary Node.
During intra-frequency, inter-gNodeB PSCell change, the source Secondary Node initiates the Secondary Node Change
procedure. Downlink packet forwarding is initiated from the source Secondary Node to the target Secondary Node.
19 sur 74 23/04/2024, 07:35

After the UE performs a successful Random Access procedure in the target PSCell, the target Secondary Node can send
and receive user data in the SCG.

Reception and Transmission of a Measurement Report to the Secondary Node
Radio Link Quality of Neighbor High-Band Cell Becomes Better than the Serving PSCell
Secondary Node Initiated Secondary Node Change
3.10 Scenarios for Master Node Triggered NR-DC Procedures
3.10.1 Detection of High Buffer Status
If downlink RLC buffer monitoring is active, the Master Node configures the UE with A4 measurement if either or both
of the NrdcMnCellProfileUeCfg.nrdcSetupDlPktAgeThr and
NrdcMnCellProfileUeCfg.nrdcSetupDlPktVolThr thresholds are exceeded and high buffer status is set in the
Master Node.

Downlink RLC Buffer Monitoring
3.10.2 Reception of an A4 Measurement Repor t
The UE, as configured to perform inter-frequency A4 measurements, reports the PCI of a candidate PSCell on a High-
Band frequency to the Master Node.
When an A4 measurement report is received by the Master Node, the Secondary Node Addition procedure starts if all
the criteria for triggering the procedure are met.

Evaluation of A4 Measurement Report
3.10.3 Reception and Transmission of a Measurement Repor t to the Secondary Node
If the UE that is configured with NR-DC finds a High-Band cell that has better radio link quality than the serving PSCell
by performing A3 measurements, the UE sends the A3 measurement report to the Master Node by using the RRC
ULInformationTransferMRDC message. The Master Node forwards the A3 measurement report by sending the
XnAP RRC TRANSFER message to the source Secondary Node, where the measurement report is evaluated.

Radio Link Quality of Neighbor High-Band Cell Becomes Better than the Serving PSCell
Uplink Information Transfer and RRC Transfer
3.10.4 UE Indicating SCG Radio Link Failure
The UE can indicate RLF by sending the SCGFailureInformation RRC message to the Master Node in the following
cases:
– It is not possible to perform random access to the PSCell during the Secondary Node Addition procedure.
– The configured maximum number of allowed RLC retransmissions is reached in uplink.
– The timer set in the Rrc.t310 attribute expires.
At the reception of the SCGFailureInformation RRC message, the Master Node initiates the Secondary Node
Release procedure.
20 sur 74 23/04/2024, 07:35


3.10.4.1 UE Requesting the SCG to Be Released
The UE can send the RRC SCGFailureInformation message to the Master Node to trigger a Master Node initiated
Secondary Node Release procedure. This way, the UE can request a release of the SCG when it is not needed.
The UE indicates the request to release the SCG with the following attributes in the measResultFreqList IE set to
the appropriate values:
– ssbFrequency = 0
– MeasResultNR:
• phyCellId = 0
• cellResults = empty
Note: The refFreqCSI-RS attribute is ignored if it is received.
When this type of the Master Node initiated Secondary Node Release procedure is used, the UE is not expected to send
any A4 measurement reports. This is expected to last until the UE needs the SCG.
This type of Secondary Node Release procedure is observed on the Secondary Node as a normal release.

3.10.5 UE Released to Idle Mode
When the UE is released to RRC_IDLE mode by the Master Node, resources in the Secondary Node are released. This is
triggered in the Secondary Node at the reception of the XnAP UE CONTEXT RELEASE message sent by the Master
Node.

3.10.6 PDU Session Resource Setup P rocedure
During the PDU Session Resource Setup procedure, resources over the Uu and NG-C interfaces are assigned for one or
more PDU sessions and their corresponding QoS flows. The procedure aims to set up DRBs corresponding to the QoS
flows for a given UE.
C o n n e c te d M o d e w i t h N R- D C N o t C o n fi g u re d
Based on the configured 5QI and ARP values of each QoS flow in a PDU session, the following cases occur:
– If the new PDU session is allowed to be Secondary Node terminated, the Master Node either starts downlink RLC
buffer monitoring or configures the UE to start A4 measurements.
– If the new PDU session is not allowed to be Secondary Node terminated by configuration, the Master Node takes
no action related to NR-DC at reception of the NGAP PDU SESSION RESOURCE SETUP REQUEST message.
C o n n e c te d M o d e w i t h N R- D C C o n fi g u re d
When the UE is configured with NR-DC, setting up additional Secondary Node terminated PDU sessions is not
supported. Such PDU sessions are set up as being Master Node terminated, regardless if the 5QI and ARP configuration
allows Secondary Node termination. The PDU sessions remain to be Master Node terminated until the next time NR-DC
is configured.

21 sur 74 23/04/2024, 07:35


3.10.7 PDU Session Resource Modif y P rocedure
During the PDU Session Resource Modify procedure, the AMF requests the Master Node to modify the already existing
PDU sessions for a given UE. The procedure is used to set up, modify or release a QoS flow within an established PDU
session.
A PDU session is modified to be allowed to be Secondary Node terminated by releasing QoS flows that prevent
Secondary Node termination by configuration. A PDU session is modified not to be allowed to be Secondary Node
terminated by adding QoS flows that prevent Secondary Node termination by configuration.
Based on the configured QoS flow in a PDU session, the following cases can occur:
– The Master Node either starts downlink RLC buffer monitoring or configures the UE to start A4 measurements if
the following conditions are met:
• Downlink RLC buffer monitoring or A4 measurements are not already ongoing.
• A PDU session becomes allowed to be Secondary Node terminated by releasing or modifying QoS flows.
– When no PDU session is allowed to be Secondary Node terminated any longer by adding or successfully
modifying QoS flows, the ongoing A4 measurement continues until the measurement time is up. However, A4
measurements are not restarted after that.
Based on the configured QoS flow in a PDU session, the following cases can occur:
– When QoS flows are added to already established PDU sessions, the following restrictions apply:
• If the established PDU session is Master Node terminated, newly added QoS flows are always Master Node
terminated, regardless of the configuration of 5QI and ARP.
• If the established PDU session is Secondary Node terminated, newly added QoS flows are always Secondary
Node terminated, regardless of the configuration of the 5QI and ARP. When a QoS flow is added to prevent
Secondary Node termination in a Secondary Node terminated PDU session, the PDU session remains
Secondary Node terminated. The Secondary Node applies the modified QoS properties based on the received
information from the Master Node.
– When the last QoS flow that prevents the PDU session from being Secondary Node terminated is released, the
PDU session remains Master Node terminated and no action is taken. Such PDU sessions remain to be Master
Node terminated until the next time NR-DC is configured.
– When the QoS properties of a QoS flow are modified in established PDU sessions, the following restrictions
apply:
• If the established PDU session is Master Node terminated, newly added QoS flows are always Master Node
terminated, regardless of the modification of QoS properties of the PDU session.
• If the established PDU session is Secondary Node terminated, newly added QoS flows are always Secondary
Node terminated, regardless of the modification of QoS properties of the PDU session. When a QoS flow is
added to prevent Secondary Node termination in a Secondary Node terminated PDU session, the PDU session
remains Secondary Node terminated. The Secondary Node applies the modified QoS properties based on the
received information from the Master Node.
• When the QoS properties of the last QoS flow that prevents the PDU session from being Secondary Node
terminated are modified, the PDU session remains Master Node terminated and no action is taken. Such PDU
sessions remain to be Master Node terminated until the next time NR-DC is configured.
22 sur 74 23/04/2024, 07:35

QoS Flow A1 QoS Flow B1
PDU Session A PDU Session B
SDAP SDAP
PDCP PDCP
RLC RLC RLC
Set up QoS Flow Release QoS Flow
QoS Flow A1 QoS Flow B1 QoS Flow B2
SDAP SDAP
PDCP PDCP
PDCP
RLC RLC RLC

RLC RLC
L0003104B
Figure 11 Setting Up and Releasing QoS Flow for Secondary Node Terminated PDU Session

Master Node Initiated Secondary Node Modification
3.10.8 PDU Session Resource Release P rocedure
During the PDU Session Resource Release procedure, resources of established PDU sessions are released for a given
UE.
If the released PDU session was the last that was allowed to be Secondary Node terminated, any ongoing A4
measurement continues until the measurement time is up. However, A4 measurements are not restarted after that.
If a subset of PDU sessions is released and the evaluation of the A4 measurement criteria is successful, for example, as
a result of a UE group change, the Master Node configures the UE to start A4 measurements or downlink RLC buffer
monitoring.
When the UE is configured with NR-DC, releasing a subset of Secondary Node terminated PDU sessions is not
supported.
When a subset of Secondary Node terminated PDU sessions is released, the following sequence applies:
1. Resources in the Secondary Node are released at the reception of the XnAP UE CONTEXT RELEASE message sent
by the Master Node.
2. The Master Node requests the UE context release by sending the NGAP UE CONTEXT RELEASE REQUEST
message to the AMF.
3. The UE is released to RRC_IDLE mode by the Master Node.
When all Secondary Node terminated PDU sessions are released, resources in the Secondary Node are released at the
reception of the XnAP UE CONTEXT RELEASE message sent by the Master Node. The A4 measurement criteria and
the conditions for downlink RLC buffer monitoring are evaluated again in the Master Node. If the evaluation is
successful, the Master Node configures the UE to start A4 measurements or downlink RLC buffer monitoring.
QoS Flow A1 QoS Flow B1
SDAP SDAP
PDCP PDCP
RLC RLC RLC
PDU Session Resource Release
QoS Flow A1
PDU Session A
Master Node
SDAP
PDCP
RLC
MAC and Layer 1
L0003116B
Figure 12 Release of the Last Secondary Node Terminated PDU Session
23 sur 74 23/04/2024, 07:35


3.10.9 Detection of an Xn Link Break in the Master Node
When an Xn link break is detected by the Master Node, all the UEs using Secondary Node terminated split DRBs served
by the broken Xn link are released to RRC_IDLE mode by the Master Node. The outcome is the same if the Xn link break
is caused by locking the termination point of the Xn interface on the Master Node.

Xn Link Break Handling
3.10.10 Outgoing Intra-System Handover from the Source Cell
At all types of outgoing intra-system handover from the source cell on the Master Node, the Master Node initiates the
Secondary Node Release procedure as part of the handover execution.

Intra-gNodeB Handover When NR-DC Is Configured
Inter-gNodeB Handover When NR-DC Is Configured
3.10.11 Incoming Handover into a New P Cell
At incoming handover into a new PCell, the Master Node can build the configuration for the UE to start A4
measurements to find a candidate PSCell on a High-Band frequency or start downlink RLC buffer monitoring if the NR-
DC-specific UE capabilities are known in the new PCell.
The UE capabilities are not known in the new NR-DC-capable PCell in the following cases when the UE moves to this
PCell from a non-NR-DC-capable cell the first time:
– After UE registration to the 5GC
– After incoming IRAT handover from LTE
Therefore, the NR-DC setup criteria are not met. The NR-DC setup criteria are checked again when the UE connects to
the network the next time, or when a subsequent handover is performed to another NR-DC-capable PCell.
If the UE capabilities are known in the new PCell, the target Master Node either configures the UE to perform A4
measurements or it configures downlink RLC buffer monitoring.
Downlink RLC buffer monitoring is requested if the following conditions are fulfilled:
– All criteria for starting an A4 measurement are met.
– The value of the NrdcMnCellProfileUeCfg.nrdcSetupDlPktAgeThr or

NrdcMnCellProfileUeCfg.nrdcSetupDlPktVolThr attribute is greater than 0.
– In the case of NG- or Xn-based inter-gNodeB handover, the UE was not configured with NR-DC before the
handover.
– In the case of intra-gNodeB handover, high buffer status is not set.
If downlink RLC buffer monitoring is not requested, the Master Node configures the UE in the target cell to perform A4
measurements. The aim is to find a candidate PSCell for the Secondary Node Addition procedure.
24 sur 74 23/04/2024, 07:35


Intra-gNodeB Handover When NR-DC Is Configured
Inter-gNodeB Handover When NR-DC Is Configured
Incoming IRAT Handover from LTE into an NR-DC-Capable PCell
3.10.12 Outgoing IRAT Handover from the Master Node
At an outgoing IRAT handover, the Master Node initiates the UE context release to the Secondary Node.

IRAT Handover to LTE When NR-DC Is Configured
3.10.13 Measurement Gap Addition in the Master Node
The measurement gap is added in the Master Node for measurements that require it. If NR-DC is configured, the Master
Node uses the Master Node initiated Secondary Node Modification procedure to indicate the configured measurement
gap to the Secondary Node. Because of this, the Secondary Node does not schedule user data during the measurement
gap that is added in the Master Node.
Rela ted c o nc ep t s
3.10.14 Measurement Gap Removal in the Master Node
The measurement gap is removed in the Master Node if the last measurement that requires a measurement gap is
removed. If NR-DC is configured, the Master Node uses the Master Node initiated Secondary Node Modification
procedure to inform the Secondary Node that the measurement gap is removed.
3.11 Scenarios for Secondary Node Triggered NR-DC Procedures
3.11.1 Secondary Node Detects Radio Link Failure
The Secondary Node initiates the Secondary Node Release procedure when it detects that the configured maximum
number of allowed RLC retransmissions is reached in downlink.

3.11.2 NR Cell or Sector Carrier Is Locked on the Secondary Node
The Secondary Node initiates the Secondary Node Release procedure when either of the following attributes of the
PSCell and the associated sector carrier is set to LOCKED:
– NRCellDU.administrativeState
– NRSectorCarrier.administrativeState

3.11.3 Random Access Timer Expiry in Secondary Node
The Secondary Node initiates the Secondary Node Release procedure when it detects that the time for performing a
successful random access to the PSCell is expired during the Secondary Node Addition procedure.
25 sur 74 23/04/2024, 07:35


3.11.4 PDCP COUNT Threshold Is Reached
The Secondary Node initiates the Secondary Node Release procedure when the uplink or the downlink PDCP COUNT
threshold is reached for at least one Secondary Node terminated split DRB. During the procedure, the PDCP COUNT
values are forwarded to the Master Node.
In this case, the purpose of the Secondary Node initiated Secondary Node Release procedure is to prevent COUNT wrap-
around.

3.11.5 High-Band Uplink Radio Link Quality Falls Below Configured Threshold in the
PSCell
If the High-Band uplink radio link quality falls below a configured threshold in the PSCell, the Secondary Node initiates
the Secondary Node Modification procedure to change the uplink primary path from SCG to MCG.
Note: The good quality of the MCG radio resources must be ensured by the UE that performs mobility procedures on
the Master Node.
The uplink PDCP aggregation is disabled when the primary uplink path is set to MCG after switching from the SCG to
the MCG radio resources of the Secondary Node terminated split DRB.

Configuration Considerations for Switching of Uplink MCG and SCG Radio Resources of the Secondary Node
Terminated Split DRB
3.11.6 High-Band Uplink Radio Link Quality Rises Above Configured Threshold in the
PSCell
If the High-Band uplink radio link quality rises above a configured threshold in the PSCell, the Secondary Node initiates
the Secondary Node Modification procedure to change the uplink primary path from MCG to SCG if all of the following
conditions apply:
– The primary uplink path for the transmission of PDCP PDUs is MCG.
– The transmission of PDCP PDUs in uplink is active.
– The GNBCUUPFunction.endcUlNrRetProhibTimer timer is not running.
If the primary uplink path is switched back to SCG, the uplink PDCP aggregation is enabled.

Configuration Considerations for Switching of Uplink MCG and SCG Radio Resources of the Secondary Node
Terminated Split DRB
3.11.7 Radio Link Quality of Neighbor High-Band Cell Becomes Better than the Serving
PSCell
When a UE that is configured with an A3 measurement and connected with NR-DC reports that the radio link quality of
a High-Band cell in a neighboring gNodeB becomes better than the serving PSCell, the UE sends the A3 measurement
report that contains the PCI of a High-Band cell that has better coverage.
26 sur 74 23/04/2024, 07:35

The source Secondary Node evaluates the PCI of the reported High-Band cells, as follows:
– If the reported PCI is a known external neighbor and PSCell change to the reported cell is allowed, intra-
frequency, inter-gNodeB PSCell change is triggered.
– The A3 measurement report is ignored if the PCI is unknown or it is a known internal neighbor.

Uplink Information Transfer and RRC Transfer
Secondary Node Initiated Secondary Node Change
3.11.8 Uplink Transmission Por t and Waveform Switch
The Secondary Node initiates the Secondary Node Modification procedure to reconfigure the UE to perform dynamic
port and waveform switch between CP-OFDM and DFT-s-OFDM when the UE is at the coverage border in the SCG.

3.11.9 CSI-RS Configuration for Wide Beam Suppor t
The Secondary Node initiates the Secondary Node Modification procedure to reconfigure the UE to use a different set of
SSB beams depending on the movement of the UE and the radio conditions in the SCG.

3.11.10 Maximum Number of Scheduling Requests Is Reached in the SCG
The Secondary Node initiates the Secondary Node Modification procedure to reconfigure PUCCH resources for the UE
to retain SCG resources. This is done when the Secondary Node detects that a UE connected with NR-DC attempts to
access on RACH under poor radio conditions in the SCG.

3.11.11 High Rate
When high rate is detected, the Secondary Node initiates the Secondary Node Modification procedure.
The Secondary Node initiates the Secondary Node Modification procedure when high rate is detected, and the
DrbRlcUeCfg.dlHighRateTimerEnabled attribute is set to true. When the split DRB reaches the predefined high
rate at the first time, the DRB downlink RLC timers are set to the values defined by
the DrbRlcUeCfg.tStatusProhibitDlHighRate and the DrbRlcUeCfg.tReassemblyDlHighRate attributes.
The timer configuration change is done for both MCG and SCG. The UE keeps the timer values for high rate until the
next mobility event, even if the PDCP exits the high rate conditions.
3.12 NR-DC Procedures

3.12.1 Secondary Node Addition
The Secondary Node Addition procedure establishes a UE context in the Secondary Node. This way, the Secondary
Node can provide SCG and PDCP resources to the NR-DC-capable UE.
At the Secondary Node Addition procedure, PDU sessions that are allowed to be Secondary Node terminated by
configuration are moved to the Secondary Node. The following changes are applied:
– All DRBs in the PDU session are reconfigured from Master Node terminated MCG DRBs to Secondary Node
terminated split DRBs keeping the same DRB ID.
27 sur 74 23/04/2024, 07:35

– New RLC and MAC entities are established for the Secondary Node terminated split DRBs in the Secondary Node.
In the Master Node, the following options are available:
• The RRC Reconfiguration procedure is performed without an intra-cell handover
The RLC entity in the Master Node is reestablished by releasing the old RLC bearer and setting up a new RLC
bearer for the reconfigured DRB. The PDCP is always reestablished when this option is used.
This option is used when the number of the Master Node terminated MCG DRBs plus twice the number of the
DRBs that are reconfigured from Master Node terminated to Secondary Node terminated is less than or equal
to eight.
• The RRC Reconfiguration procedure is performed with an intra-cell handover
In this case, an intra-cell handover is performed in the Master Node to reestablish the RLC entities of the
reconfigured DRBs. The DRBs are released and added again for the UE without PDCP re-establishment.
This option is only used when the number of the Master Node terminated MCG DRBs plus twice the number of
the DRBs that are reconfigured from Master Node terminated to Secondary Node terminated is greater than
eight.
– The security key is changed from the master key to the secondary key.
– Downlink packet forwarding is performed over the Xn-U interface.
– Any ongoing A4 measurements stop.
1. RRC MeasurementReport
2. XnAP S-NODE ADDITION REQUEST
3. XnAP S-NODE ADDITION REQUEST ACKNOWLEDGE
4. XnAP XN-U ADDRESS INDICATION
5. XnAP SN STATUS TRANSFER
6. RRC RRCReconfiguration
7. PCell Random Access
8. RRC RRCReconfigurationComplete
9. XnAP S-NODE RECONFIGURATION COMPLETE
10. PSCell Random Access
11. NGAP PDU SESSION RESOURCE MODIFY INDICATION
12. NGAP PDU SESSION RESOURCE MODIFY CONFIRM
L0003144A
Figure 13 Sequence of Secondary Node Addition
1. The NR-DC-capable UE sends an A4 measurement report to the Master Node in the RRC MeasurementReport
message.
When the A4 measurement report is received, the Master Node evaluates if all the criteria for the Secondary Node
Addition procedure are met. If all the criteria are met, the Master Node initiates the Secondary Node Addition
procedure to the Secondary Node that is the gNodeB that hosts the reported candidate PSCell on a High-Band
frequency.
28 sur 74 23/04/2024, 07:35

2. The Master Node sends the XnAP S-NODE ADDITION REQUEST message to the Secondary Node over the Xn-C
interface. This message contains the following information:
– The request to set up one or several PDU sessions terminated by the Secondary Node. For existing PDU sessions,
the Master Node forwards information on the contained QoS flows and the NG-U uplink TEID.
– The secondary key to be used in the Secondary Node.
– The UE capabilities including the complete list of band combinations the UE reported.
– The list of allowed NR-DC band combinations.
– The PSCell candidate, or possibly more than one candidate, selected by the Master Node.
At the reception of the message, the Secondary Node uses only the first PSCell candidate received from the Master
Node for PSCell selection in case more than one PSCell candidate is provided.
3. The Secondary Node responds to the Master Node with the XnAP S-NODE ADDITION REQUEST ACKNOWLEDGE
message. This message contains the following information:
– The NG-U downlink TEID for each PDU session with QoS flows to be Secondary Node terminated.
– The request to prepare MCG radio resources for the DRBs to be reconfigured as split. This is done by the
Secondary Node providing Xn-U uplink TEIDs.
– TEIDs provided by the Secondary Node for downlink packet forwarding for each DRB.
– The CG-Config message containing the selected band combination and feature set. This list includes the PSCell
and possibly SCells of the SCG.
4. The Master Node sends the XnAP XN-U ADDRESS INDICATION message to the Secondary Node. The message
contains the Xn-U downlink TEIDs for the DRBs to be reconfigured as split. The DRBs to be reconfigured as split are
suspended in the Master Node.
5. The Master Node can send the XnAP SN STATUS TRANSFER message to the Secondary Node for AM DRBs. The
message is used to forward the PDCP COUNT values.
At this stage, the DRBs to be reconfigured as split are suspended and downlink packet forwarding starts.
6. The Master Node sends the RRC RRCReconfiguration message to the UE over the Uu interface. The message
includes information about the MCG and the SCG.
7. Optionally, random access is performed in the PCell. This depends on whether an intra-cell handover is used or not.
8. The UE responds to the Master Node with the RRC RRCReconfigurationComplete message. The UE can start
sending uplink user data in the MCG using the secondary key in the relocated PDCP.
9. The Master Node sends the XnAP S-NODE RECONFIGURATION COMPLETE message to the Secondary Node over
the Xn-C interface. The message contains information on the successful reconfiguration of the UE. The DRBs
reconfigured as split resume in the Secondary Node. The Secondary Node can start sending downlink user data in
the MCG using the secondary key in the relocated PDCP.
10. The UE performs the random access procedure in the PSCell. After a successful random access procedure, the
Secondary Node can send and receive user data in the SCG using the secondary key.
11. The Master Node sends the NGAP PDU SESSION RESOURCE MODIFY INDICATION message to the AMF over the
NG-C interface to provide the new NG-U downlink TEID that is used by the UPF. After the path update, the UPF
starts sending downlink user data to the Secondary Node.
12. The AMF confirms the path update by responding to the Master Node with the NGAP PDU SESSION RESOURCE
MODIFY CONFIRM message.
29 sur 74 23/04/2024, 07:35

Note: If the measurement gap is reconfigured, the Master Node might send an additional RRC
RRCReconfiguration message to the UE and an additional Secondary Node initiated Secondary Node
Modification procedure is performed.
The following messages in the sequence are initiated in parallel:
– XnAP SN STATUS TRANSFER
– RRC RRCReconfiguration
– NGAP PDU SESSION RESOURCE MODIFY INDICATION

3.12.2 Master Node Initiated Secondary Node Modification
The Master Node initiated Secondary Node Modification procedure is triggered by the following scenarios:
– New QoS flows are set up in an established Secondary Node terminated PDU session.
– The QoS properties of a QoS flow are modified in an established Secondary Node terminated PDU session.
– QoS flows are released in an established Secondary Node terminated PDU session.
– Measurements that require measurement gap configuration are started in the Master Node.
– Measurements that require measurement gap configuration are stopped in the Master Node.
UE Master Node Secondary Node
1. XnAP S-NODE MODIFICATION REQUEST
2. XnAP S-NODE MODIFICATION RESPONSE
6. XnAP S-NODE RECONFIGURATION

COMPLETE
L0003147B
Figure 14 Sequence of Master Node Initiated Secondary Node Modification
1. The Master Node sends the XnAP S-NODE MODIFICATION REQUEST message to the Secondary Node.
2. The Secondary Node replies to the Master Node with the XnAP S-NODE MODIFICATION REQUEST
ACKNOWLEDGE message.
3. Optionally, the Master Node sends the XnAP XN-U ADDRESS INDICATION message to the Secondary Node if the
PDU session resource modification includes the addition of new QoS flows to already established Secondary Node
terminated PDU sessions.
4. The Master Node updates the UE with the RRC RRCReconfiguration message.
5. The UE responds with the RRC RRCReconfigurationComplete message to the Master Node.
6. Optionally, the Master Node sends the XnAP S-NODE RECONFIGURATION COMPLETE message to the Secondary
Node if measurements that require a measurement gap on the Master Node are started and stopped.
30 sur 74 23/04/2024, 07:35

Measurement Gap Addition in the Master Node
Measurement Gap Removal in the Master Node
3.12.3 Secondary Node Initiated Secondary Node Modification
The Secondary Node initiated Secondary Node Modification procedure is triggered by the following scenarios:
– The High-Band uplink radio quality drops below or rises above a configurable threshold value, after which the UE
is reconfigured to change the uplink primary path of PDCP PDU transmission.
– The UE must be reconfigured to use a different set of SSB beams depending on the movement of the UE and the
radio conditions in the SCG.
– PUCCH resources must be reconfigured for the UE to retain SCG resources when the Secondary Node detects that
a UE connected with NR-DC attempts to access on RACH under poor radio conditions in the SCG.
– The UE must be reconfigured to perform dynamic port and waveform switch between CP-OFDM and DFT-
s-OFDM when the UE is at the coverage border in the SCG.
– The UE is reconfigured with different RLC timers when the UE DRB reaches the predefined high rate for the first
time. The RLC timers in both the MCG and the SCG are reconfigured.
1. XnAP S-NODE MODIFICATION REQUIRED
4. XnAP S-NODE MODIFICATION CONFIRM
L0003309A
Figure 15 Sequence of Secondary Node Initiated Secondary Node Modification
1. The Secondary Node initiates the Secondary Node Modification procedure by sending the XnAP S-NODE
MODIFICATION REQUIRED message to the Master Node over the Xn-C interface.
2. The Master Node sends the RRC RRCReconfiguration message to the UE over the Uu interface.
3. The UE responds to the Master Node by sending the RRC RRCReconfigurationComplete message.
4. The Master Node responds with the XnAP S-NODE MODIFICATION CONFIRM message to the Secondary Node.

High-Band Uplink Radio Link Quality Falls Below Configured Threshold in the PSCell
High-Band Uplink Radio Link Quality Rises Above Configured Threshold in the PSCell
Uplink Transmission Port and Waveform Switch
CSI-RS Configuration for Wide Beam Support
Maximum Number of Scheduling Requests Is Reached in the SCG
Parameters for NR-NR Dual Connectivity
High Rate
3.12.4 Uplink Information Transfer and RRC Transfer
The Uplink Information Transfer and the RRC Transfer procedures have the following purposes:
31 sur 74 23/04/2024, 07:35

– The Uplink Information Transfer procedure is used to transfer MR-DC-dedicated information from the UE to the
Master Node. The RRC MeasurementReport messages are transferred this way from the UE to the Master
Node.
– The RRC Transfer procedure is used to forward encapsulated RRC messages by the Master Node from the UE to
the Secondary Node.
1. RRC ULInformationTransferMRDC
(with measurement report)
2. XnAP RRC TRANSFER

(with measurement report)
L0003464A
Figure 16 Sequence of Uplink Information Transfer and RRC Transfer
1. The UE sends the RRC ULInformationTransferMRDC message to the Master Node. The message contains a
measurement report.
2. The Master Node encapsulates the RRC ULInformationTransferMRDC message that is received from the UE
and transfers it to the Secondary Node by using the XnAP RRC TRANSFER message.

Reception and Transmission of a Measurement Report to the Secondary Node
3.12.5 Secondary Node Initiated Secondary Node Change
The Secondary Node initiated Secondary Node Change procedure is used for the following:
– To transfer a UE context from the source Secondary Node to a target Secondary Node.
– To change the SCG configuration in UE from one Secondary Node to another Secondary Node.
AMF UE Master Node Target Source

Secondary Node Secondary Node
Measurement report
evaluated
1. XnAP S-NODE CHANGE REQUIRED

ACKNOWLEDGE
4. Xn-U ADDRESS INDICATION
5. XnAP S-NODE CHANGE CONFIRM
9. XnAP S-NODE RECONFIGURATON COMPLETE
12. PSCell Random Access
15. XnAP UE CONTEXT RELEASE
L0003415A
Figure 17 Sequence of Secondary Node Initiated Secondary Node Change
1. When intra-frequency, inter-gNodeB PSCell change is triggered, the source Secondary Node sends the XnAP
S-NODE CHANGE REQUIRED message to the Master Node.
2. The PSCell Change procedure to the target PSCell on the neighbor gNodeB is accepted in the Master Node if the
following requirements are fulfilled:
– The reported PCI can be mapped to an existing ExternalNRCellCU MO instance that represents the PSCell
candidate on the measured High-Band frequency. The MO is a child of the ExternalGNBCUCPFunction MO
that represents the target Secondary Node in the MO structure of the Master Node.
– An NRCellRelation MO instance exists between the ExternalNRCellCU MO instance that represents the
32 sur 74 23/04/2024, 07:35

target PSCell and the NRCellCU MO instance that represents the serving PCell on the Master Node.
Note: The NRCellRelation MO instance between the NRCellCU and ExternalNRCellCU MOs must be
created manually.
– A connection over the Xn interface exists between the Master Node that hosts the PCell and the Secondary Node
that hosts the target PSCell candidate.
The connection is represented by a TermPointToGNodeB MO instance. The MO is a child of the

ExternalGNBCUCPFunction MO that represents the Secondary Node in the MO structure of the Master Node.
For the connection to be functional, the TermPointToGNodeB.administrativeState attribute must be set
to UNLOCKED and the TermPointToGNodeB.operationalState attribute must display ENABLED.
If the requirements are fulfilled, the Master Node triggers Secondary Node Addition by sending the XnAP S-NODE
ADDITION REQUEST message to the target Secondary Node that hosts the target PSCell.
3. The Secondary Node responds by sending the XnAP S-NODE ADDITION REQUEST ACKNOWLEDGE message to
the Master Node.
4. The Master Node sends the XnAP XN-U ADDRESS INDICATION message to the target Secondary Node.
5. The Master Node sends the XnAP S-NODE CHANGE CONFIRM message to the source Secondary Node.
6. The Master Node reconfigures the UE by sending the RRC RRCReconfiguration message. The message includes
information about the MCG and the SCG.
8. The UE responds to the Master Node by sending the RRC RRCReconfigurationComplete message.
9. The Master Node sends the XnAP S-NODE RECONFIGURATON COMPLETE message to the target Secondary Node.
10. The source Secondary Node sends the Secondary Node status by using the XnAP SN STATUS TRANSFER message
to the Master Node.
The downlink packet forwarding is started from the source Secondary Node to the target Secondary Node.
11. The Master Node sends the XnAP SN STATUS TRANSFER message to the target Secondary Node.
12. The UE performs the random access procedure in the target PSCell.
After a successful random access procedure is performed, the Secondary Node can send and receive user data in the
SCG.
13. The Master Node signals to the AMF by sending the NGAP PDU SESSION RESOURCE MODIFY INDICATION
message to change the NG-U termination of the Secondary Node terminated split DRBs to the target Secondary
Node.
14. The AMF responds to the Master Node by sending the NGAP PDU SESSION RESOURCE MODIFY CONFIRM
message.
15. The Master Node sends the XnAP UE CONTEXT RELEASE message to the source Secondary Node.
RRCReconfiguration message to the UE and an additional Secondary Node initiated Secondary Node
Modification procedure is performed.
3.12.6 Master Node Initiated UE Context Release
33 sur 74 23/04/2024, 07:35

XnAP UE CONTEXT RELEASE
L0003163A
Figure 18 Sequence of Master Node Initiated UE Context Release
The Master Node requests the Secondary Node to release all the SCG resources for the UE by sending the XnAP UE
CONTEXT RELEASE message over the Xn-C interface to the Secondary Node.

Outgoing IRAT Handover from the Master Node
3.12.7 Master Node Initiated Secondary Node Release
The Master Node initiated Secondary Node Release procedure triggers the release of the UE context at the Secondary
Node.
The Master Node initiated Secondary Node Release procedure is triggered by one of the following scenarios:
– The UE detects RLF in the SCG.
– Any type of intra-system handover is performed from the source cell on the Master Node.
At the Master Node initiated Secondary Node Release procedure, Secondary Node terminated PDU sessions are moved
to the Master Node. The following changes are applied:
– All DRBs in the PDU session are reconfigured from Secondary Node terminated split DRBs to Master Node
terminated MCG DRBs keeping the same DRB ID.
– RLC and MAC entities established at the Secondary Node Addition procedure are released for the DRBs to be
reconfigured from Secondary Node terminated into Master Node terminated.
DRBs that are reconfigured from Secondary Node terminated to Master Node terminated is less than or equal
to eight.
reconfigured DRBs. The DRBs are released and added again for the UE without PDCP reestablishment.
This option is only used in either of the following cases:
34 sur 74 23/04/2024, 07:35

– When the number of the Master Node terminated MCG DRBs plus twice the number of the DRBs that are
reconfigured from Secondary Node terminated to Master Node terminated is greater than eight.
– At least one UM DRB is reconfigured from Secondary Node terminated into Master Node terminated.
– The security key is changed from the secondary key to the master key.
– If all the criteria for starting an A4 measurement are met, the Master Node either starts downlink RLC buffer
monitoring or configures the UE to start A4 measurements.
1. XnAP S-NODE RELEASE REQUEST
2. XnAP S-NODE RELEASE REQUEST ACKNOWLEDGE
L0003145A
Figure 19 Sequence of Master Node Initiated Secondary Node Release
1. If one of the trigger conditions is detected, the Master Node initiates the release of the Secondary Node. To initiate
the procedure, the Master Node sends the XnAP S-NODE RELEASE REQUEST message over the Xn-C interface.
With this message, the Master Node triggers the release of the SCG resources for a specific UE.
2. The Secondary Node replies with the XnAP S-NODE RELEASE REQUEST ACKNOWLEDGE message. The message
contains the following information:
– The list of PDU sessions with Secondary Node terminated QoS flows to be released.
– Information on the QoS flows that the Secondary Node terminated PDU sessions contain.
– The request for downlink packet forwarding.
3. The Master Node sends the XnAP XN-U ADDRESS INDICATION message to the Secondary Node with information
on TEIDs for packet forwarding. When the message is received, the downlink packet forwarding starts.
4. The Secondary Node can send the XnAP SN STATUS TRANSFER message to the Master Node for AM DRBs. The
indicates to the UE that the SCG resources are released, and it also contains information about the MCG. The
message might also contain A4 measurement configuration.
7. The UE responds to the Master Node by sending the RRC RRCReconfigurationComplete message. The Master
Node can start sending and receiving user data using the master key in the relocated PDCP. After the UE
reconfiguration is confirmed, the DRBs reconfigured as Master Node terminated resume in the Master Node.
starts sending downlink user data to the Master Node.
35 sur 74 23/04/2024, 07:35

10. The Master Node requests the Secondary Node to release all the SCG resources for the UE by sending the XnAP UE
RRCReconfiguration message to the UE.
– XnAP UE CONTEXT RELEASE

UE Indicating SCG Radio Link Failure
UE Requesting the SCG to Be Released
3.12.8 Secondary Node Initiated Secondary Node Release
The Secondary Node initiated Secondary Node Release procedure triggers the release of the UE context at the
Secondary Node.
The Secondary Node initiated Secondary Node Release procedure is triggered by one of the following scenarios:
– The Secondary Node detects RLF.
– The PSCell or the underlying sector carrier is locked.
– The random access timer expires in the Secondary Node.
– The PDCP COUNT threshold is reached for a Secondary Node terminated split DRB.
At the Secondary Node initiated Secondary Node Release procedure, Secondary Node terminated PDU sessions are
moved to the Master Node. The following changes are applied:
– All DRBs in the PDU session are reconfigured from Secondary Node terminated split DRBs to Master Node
terminated MCG DRBs keeping the same DRB ID.
– RLC and MAC entities established at the Secondary Node Addition procedure are released for the DRBs to be
reconfigured from Secondary Node terminated into Master Node terminated.
DRBs that are reconfigured from Secondary Node terminated to Master Node terminated is less than or equal
to eight.
reconfigured DRBs. The DRBs are released and added again for the UE without PDCP reestablishment.
36 sur 74 23/04/2024, 07:35

This option is only used in either of the following cases:
– When the number of the Master Node terminated MCG DRBs plus twice the number of the DRBs to be
reconfigured from Secondary Node terminated to Master Node terminated is greater than eight.
– At least one UM DRB is reconfigured from Secondary Node terminated into Master Node terminated.
– The security key is changed from the secondary key to the master key.
– If all the criteria for starting an A4 measurement are met, the Master Node either starts downlink RLC buffer
monitoring or configures the UE to start A4 measurements.
1. XnAP S-NODE RELEASE REQUIRED
2. XnAP S-NODE RELEASE CONFIRM
L0003146A
Figure 20 Sequence of Secondary Node Initiated Secondary Node Release
1. If one of the trigger conditions is detected, the Secondary Node initiates the release of the Secondary Node. To
initiate the procedure, the Secondary Node sends the XnAP S-NODE RELEASE REQUIRED message to the Master
Node over the Xn-C interface. The message contains the following information:
– The list of PDU sessions with Secondary Node terminated QoS flows to be released.
– Information on the QoS flows that the Secondary Node terminated PDU sessions contain.
– The request for downlink packet forwarding.
2. The Master Node replies with the XnAP S-NODE RELEASE CONFIRM message to the Secondary Node with
information on TEIDs for packet forwarding. When the message is received, the downlink packet forwarding starts.
3. The Secondary Node can send the XnAP SN STATUS TRANSFER message to the Master Node for AM DRBs. The
indicates to the UE that the SCG resources are released, and it also contains information about the MCG. The
message might also contain A4 measurement configuration.
6. The UE responds to the Master Node by sending the RRC RRCReconfigurationComplete message. The Master
Node can start sending and receiving user data using the master key in the relocated PDCP. After the UE
reconfiguration is confirmed, the DRBs reconfigured as Master Node terminated resume in the Master Node.
starts sending downlink user data to the Master Node.
9. The Master Node requests the Secondary Node to release all the SCG resources for the UE by sending the XnAP UE
37 sur 74 23/04/2024, 07:35

RRCReconfiguration message to the UE.
– XnAP UE CONTEXT RELEASE

Secondary Node Detects Radio Link Failure
NR Cell or Sector Carrier Is Locked on the Secondary Node
Random Access Timer Expiry in Secondary Node
PDCP COUNT Threshold Is Reached
4 Network Impact of NR-NR Dual Connectivity

The feature affects data throughput, retainability, and UE battery life. It introduces and adds information to
signaling messages over external interfaces.
Capacity and Perfo rmance

Data throughput for the UE is expected to increase when Secondary Node terminated split DRBs are used. This is
because the SCG provides increased bandwidth with High-Band frequencies. When using the Secondary Node
terminated split DRB, the following impact can be expected on Master Node and Secondary Node traffic:
– Data traffic volume over the Secondary Node to the UE increases. The level of increase is lower if downlink RLC
buffer monitoring is active.
– Data traffic volume over the Master Node to the UE might decrease as most of the traffic flows through the SCG.
– Total user throughput might increase.
– Signaling is expected to increase over the following interfaces:
• The NG-C interface between the Master Node and the 5GC
• The Uu interface between the Master Node and the UE
• The Xn-C interface between the Master Node and the Secondary Node
With the activation of the feature, impact on Retainability can be expected. This is because at feature activation, both
the Master Node with the feature activated and also the neighbor gNodeBs without the feature start requesting NR-
DC-specific UE capabilities. The increased number of RRC UECapabilityEnquiry messages sent to UEs occurs for
one of the following reasons:
– The AMF does not support storing or updating UE capabilities.
– The UE uses an RRC protocol version older than 15.6.0. Such UEs are not able to indicate if NR-DC-specific
capabilities were already requested by the network or not.
This Retainability impact can affect the network in the following ways:
– An increase in the network load can be expected because of the frequent requests for NR-DC-specific UE
capabilities.
38 sur 74 23/04/2024, 07:35

– The risk of dropping the connection increases for UEs that are at the cell edge or in bad radio conditions.
With intra-frequency, inter-gNodeB PSCell change, the following benefits are expected:
– The number of abnormal Secondary Node releases for UEs that are caused by RLF can be reduced. This improves
retainability.
– Improved end user performance and data throughput is expected because of the following factors:
• The UE spends less time in the SCG with poor radio link quality.
• The UE can continue to use the higher bit rates of High-Band frequencies in an SCG with good radio link
quality.
• The PSCell change for the UE results in no packet loss.
With the configuration of downlink RLC buffer monitoring, NR-DC setup is triggered based on the level of UE traffic and
this way the number of unnecessary NR-DC setups decrease. When the UE traffic is higher than the configured
threshold, A4 measurement configuration is delayed. When the UE traffic is lower than the configured threshold, NR-
DC is not configured for the UE.
When downlink carrier aggregation is used on the Master Node before NR-DC is configured, and SCells are activated to
carry traffic, the probability of a high buffer report decreases. As a result, the probability to set up NR-DC decreases.
I n te r fa c e s
The feature affects the following external interfaces:
Xn-C The feature introduces the following messages over the Xn-C interface:
– ACTIVITY NOTIFICATION
– ERROR INDICATION (different message instances for UE-associated and non-UE associated signaling)
– RRC TRANSFER
– S-NODE ADDITION REQUEST
– S-NODE ADDITION REQUEST ACKNOWLEDGE
– S-NODE ADDITION REQUEST REJECT
– S-NODE CHANGE REQUIRED
– S-NODE CHANGE CONFIRM
– S-NODE CHANGE REFUSE
– S-NODE MODIFICATION CONFIRM
– S-NODE MODIFICATION REFUSE
– S-NODE MODIFICATION REQUIRED
– S-NODE MODIFICATION REQUEST
– S-NODE MODIFICATION REQUEST ACKNOWLEDGE
– S-NODE MODIFICATION REQUEST REJECT
– S-NODE RECONFIGURATION COMPLETE
– S-NODE RELEASE REQUEST
– S-NODE RELEASE REQUEST ACKNOWLEDGE
– S-NODE RELEASE REJECT
– S-NODE RELEASE REQUIRED
39 sur 74 23/04/2024, 07:35

– S-NODE RELEASE CONFIRM
– SN STATUS TRANSFER
– UE CONTEXT RELEASE
– XN-U ADDRESS INDICATION
NG-C The feature introduces the following messages:
– PDU SESSION RESOURCE MODIFY INDICATION
– PDU SESSION RESOURCE MODIFY CONFIRM
The feature uses the following messages at Xn link break:
– NG RESET
– NG RESET ACKNOWLEDGE
Uu The feature introduces the following messages:
– RRC SCGFailureInformation
– RRC ULInformationTransferMRDC
The following RRC messages are modified containing NR-DC information:
– RRCReconfiguration
– CG-Config
– CG-ConfigInfo
Othe r Net work El e ments

Higher UE battery consumption is expected when NR-DC-capable UEs perform A4 measurements or use the Secondary
Node resources.
UE battery life is extended when the UE indicates the release of the Secondary Node when not using SCG resources
while connected in NR-DC.
UE battery consumption can be reduced by using downlink RLC buffer monitoring.
5 Parameters for NR-NR Dual Connectivity

The feature introduces new configurable parameters. It uses parameters of the LTE-NR Dual Connectivity, the LTE-
NR Downlink Aggregation, and the LTE-NR Uplink Aggregation features for user plane management.
Table 2 MOs Introduced by NR-NR Dual Connectivity
P arame ter Type Description

NrdcControl Introduced See MOM description.
NrdcMnCellProfile Introduced See MOM description.
NrdcMnCellProfileUeCfg Introduced See MOM description.
NrdcSnTermination Introduced See MOM description.
NrdcSnTerminationUeCfg Introduced See MOM description.
Table 3 Attributes for PCell Configuration on the Master Node
40 sur 74 23/04/2024, 07:35


NRCellCU.nrdcMnCellProfileRef Introduced See MOM description.
NrdcControl.nrdcControlId Introduced See MOM description.
NrdcMnCellProfile.nrdcMnCellProfileId Introduced See MOM description.
NrdcMnCellProfile.reservedBy Introduced See MOM description.
NrdcMnCellProfileUeCfg.nrdcMnCellProfileUeCfgId Introduced See MOM description.
NrdcMnCellProfileUeCfg.nrdcEnabled Introduced See MOM description.
Table 4 Attributes to Configure A4 Measurements

NrdcMnCellProfileUeCfg.nrdcMeasRestartTime Introduced See MOM description.
NrdcMnCellProfileUeCfg.nrdcMeasTime Introduced See MOM description.
See MOM description.
The attribute contains the
following configurable
members:
NrdcMnCellProfileUeCfg.rsrpPSCellCandidate Introduced
– threshold
– hysteresis
– timeToTrigger
Table 5 Attributes to Configure Downlink RLC Buffer Monitoring

NrdcMnCellProfileUeCfg.nrdcSetupDlPktAgeThr Introduced See MOM description.
NrdcMnCellProfileUeCfg.nrdcSetupDlPktVolThr Introduced See MOM description.
Table 6 Attributes to Configure A3 Measurements for Intra-Frequency, Inter-gNodeB PSCell Change.

The table contains the attributes used to configure intra-frequency, inter-gNodeB PSCell Change used in NR-DC. For
more information on the functions and configuration, see the relevant sections of the NR Mobility feature description.
IntraFreqMCCellProfileUeCfg.betterSpCellTriggerQuantity Affecting See MOM description.
members:
IntraFreqMCCellProfileUeCfg.rsrpBetterSpCell Affecting
– hysteresis
– offset
– timeToTrigger
members:
IntraFreqMCCellProfileUeCfg.rsrqBetterSpCell Affecting
– hysteresis
– offset
41 sur 74 23/04/2024, 07:35


– timeToTrigger
Table 7 Attributes on the Master Node to Configure PDU Session Termination

CUCP5qi.nrdcSnTerminationRef Introduced See MOM description.
NrdcSnTermination.defaultNrdcSnTerm Introduced See MOM description.
NrdcSnTermination.nrdcSnTerminationId Introduced See MOM description.
NrdcSnTermination.reservedBy Introduced See MOM description.
NrdcSnTerminationUeCfg.nrdcSnTermAllowed Introduced See MOM description.
NrdcSnTerminationUeCfg.nrdcSnTerminationUeCfgId Introduced See MOM description.
Table 8 Attributes to Configure Inactivity Timers

InactivityProfileUeCfg.tInactivityTimerNrdcSn Introduced See MOM description.
GNBCUCPFunction.nasInactivityTime Affecting See MOM description.
InactivityProfileUeCfg.tInactivityTimer Affecting See MOM description.
Table 9 Attributes to Configure Xn Interface Timers for NR-DC Procedures

GNBCUCPFunction.tXnDcOverall Introduced See MOM description.
GNBCUCPFunction.tXnDcPrep Introduced See MOM description.
Table 10 Attributes on the Secondary Node to Configure Radio Link Failure Conditions.
The table contains the attributes used to configure Radio Link Failure (RLF) conditions for the SCG resources available
for the UE. For more information on the configuration, see the relevant section of the LTE-NR Dual Connectivity feature
description.
Rrc.t310 Affecting See MOM description.
Rrc.t304 Affecting See MOM description.
DataRadioBearer.dlMaxRetxThreshold Affecting See MOM description.
DataRadioBearer.ulMaxRetxThreshold Affecting See MOM description.
DataRadioBearer.tPollRetransmitDl Affecting See MOM description.
DataRadioBearer.tPollRetransmitUl Affecting See MOM description.
Table 11 Attributes Used for AQM Configuration on the Secondary Node

CUUP5qi.aqmMode Affecting See MOM description.
CUUP5qi.estimatedE2ERTT Affecting See MOM description.
CUUP5qi.packetDelayBudget Affecting See MOM description.
CUUP5qi.packetDelayBudgetOffset Affecting See MOM description.
The AQM maximum age for packets
DU5qi.estimatedE2ERTT Affecting in AQM MODE1 in RLC can be
calculated by using the
42 sur 74 23/04/2024, 07:35


DU5qi.estimatedE2ERTT
attribute.
Table 12 Attributes of LTE-NR Dual Connectivity Used in NR-DC.

The table contains the attributes used to configure the initial primary path of uplink user data, and the uplink and
downlink thresholds for MCG and SCG radio resource switching of the LTE-NR Dual Connectivity feature used in NR-
DC. For more information on the functions and configurations, see the relevant sections of the LTE-NR Dual
Connectivity feature description.
GNBCUUPFunction.endcUlNrRetProhibTimer Affecting See MOM description.
NRCellDU.endcUlLegSwitchEnabled Affecting See MOM description.
NRCellDU.endcUlNrLowQualThresh Affecting See MOM description.
NRCellDU.endcUlNrQualHyst Affecting See MOM description.
NRCellDU.endcDlNrLowQualThresh Affecting See MOM description.
NRCellDU.endcDlNrQualHyst Affecting See MOM description.
QciProfileEndcConfigExt.initialUplinkConf Affecting See MOM description.
NRCellDU.endcDlLegSwitchEnabled Affecting See MOM description.
Table 13 Attributes of LTE-NR Downlink Aggregation Used in NR-DC.

The table contains the attributes used to configure the flow control mechanism and the downlink aggregation of the
MCG and SCG radio resources of the LTE-NR Downlink Aggregation feature used in NR-DC. For more information on
the functions and configurations, see the relevant sections of the LTE-NR Downlink Aggregation feature description.
GNBCUUPFunction.endcDlNrRetProhibTimer Affecting See MOM description.
GNBCUUPFunction.dcDlAggExpiryTimer Affecting See MOM description.
GNBCUUPFunction.dlPdcpSpsTargetTimeLTE Affecting See MOM description.
GNBCUUPFunction.dlPdcpSpsTargetTimeNR Affecting See MOM description.
GNBCUUPFunction.dcDlAggActTime Affecting See MOM description.
GNBCUUPFunction.dcDlPdcpInitialMcgRate Affecting See MOM description.
GNBCUUPFunction.dcDlPdcpInitialScgRate Affecting See MOM description.
CUUP5qi.dcDlPdcpAggrPrioCg Affecting See MOM description.
CUUP5qi.dcDlPdcpAggrTimeDiffCg Affecting See MOM description.
CUUP5qi.dcDlPdcpAggrTimeDiffProhibit Affecting See MOM description.
CUUP5qi.dcDlPdcpAggrTimeDiffThresh Affecting See MOM description.
Table 14 Attributes of LTE-NR Uplink Aggregation Used in NR-DC.

The table contains the attribute used to configure whether uplink user data is aggregated over the MCG and SCG radio
resources of the LTE-NR Uplink Aggregation feature used in NR-DC. In addition, the uplink PDCP aggregation function
is applicable for NR-DC if the primary uplink data path is SCG. For more information on the function and the
configuration, see the relevant sections of the LTE-NR Uplink Aggregation feature description.
QciProfileEndcConfigExt.ulDataSplitThreshold Affecting See MOM description.
Table 15 Attributes for High Rate
43 sur 74 23/04/2024, 07:35


DrbRlcUeCfg.tStatusProhibitDlHighRate Introduced See MOM description.
DrbRlcUeCfg.dlHighRateTimerSwitchEnabled Introduced See MOM description.
DrbRlcUeCfg.tReassemblyDlHighRate Introduced See MOM description.
Table 16 Attributes to Configure Independent Measurement Gap.

The table contains the attribute used to configure the independent measurement gap used in NR-DC. For more
information on the configuration, see the relevant sections of Measurement Gap-Aware NR Scheduling.
CapabilityHandlingUeCfg.gaplessFr2InterFreqMeasSupp Affecting See MOM description.
TCP Optimization for the Secondary Node Terminated Split DRB in NR-DC
A4 Measurement Criteria
User Activity Supervision
TCP Optimization for the Secondary Node Terminated Split DRB in NR-DC
LTE-NR Downlink Aggregation
LTE-NR Uplink Aggregation
Measurement Gap-Aware NR Scheduling
6 Performance of NR-NR Dual Connectivity

The feature introduces Performance Indicators to monitor Secondary Node Addition and Release. New PM counters
and PM events are introduced by the feature, and existing ones can also be used to monitor the different feature
functions.
KPIs
This feature has no associated Key Performance Indicators.
P e rfo rm ance Indi cators

The Performance Indicators for monitoring the Secondary Node Addition procedure are shown in Table 17.
Table 17 Performance Indicators for Monitoring Secondary Node Addition
P e rfo rma nc e I n d ic ator Fo r m u l a

NR-DC Setup Success Rate Captured on Master gNodeB 100 × NRCellCU.pmNrdcSetupUeMnSucc /
(expressed in percentage) NRCellCU.pmNrdcSetupUeMnAtt
NR-DC Setup Success Rate Captured on Secondary 100 × NRCellCU.pmNrdcSetupUeSnSucc /
gNodeB (expressed in percentage) NRCellCU.pmNrdcSetupUeSnAtt
The Performance Indicators for monitoring the Secondary Node Release procedures are shown in Table 18.
Table 18 Performance Indicators for Monitoring Secondary Node Release

NR-DC Relocation Success
Rate Captured on Master 100 × NRCellCU.pmNrdcRelRelocUeMnSucc /
gNodeB (expressed in NRCellCU.pmNrdcRelRelocUeMnAtt
percentage)
44 sur 74 23/04/2024, 07:35


100 × NrdcRellUeSnAbnormalAct / NrdcRellUeTotal
NrdcRellUeSnAbnormalAct NRCellCU.pmNrdcRelUeSnAbnormalMnInitAct
+
NR-DC Release Abnormal NRCellCU.pmNrdcRelUeSnAbnormalSnInitAct
Active Rate Captured on
NrdcRellUeTotal NRCellCU.pmNrdcRelUeSnNormal +
Secondary gNodeB
NRCellCU.pmNrdcRelUeSnAbnormalMnInit +
(expressed in percentage)
NRCellCU.pmNrdcRelUeSnAbnormalSnInit
Note: This PI can also be used for monitoring intra-frequency, inter-gNodeB PSCell
change.
The Performance Indicators for monitoring intra-frequency, inter-gNodeB PSCell change are shown in Table 19.
Table 19 Performance Indicators for Monitoring Intra-Frequency, Inter-gNodeB PSCell Change

100 ×
NR-DC Inter-gNodeB PSCell Change Success Rate
NRCellCU.pmNrdcPSCellChangeSnSuccInterSgnb /
Captured on Secondary Node
NRCellCU.pmNrdcPSCellChangeSnAttInterSgnb
The Performance Indicator shown in Table 20 provides observability for downlink RLC buffer monitoring.
Table 20 Performance Indicators for Downlink RLC Buffer Monitoring

(1 -
pmEbsNrdcSetupMnBufMonReport/pmEbsNrdcSetupMnBufMonConfig)
× 100
Buffer-based NR-DC Setup avoidance The EBS counters used with the formula might indicate that the reason for
rate NR-DC setup not being triggered is the downlink RLC buffer monitoring.
However, it is possible that this is the result of a different procedure, for
example, an incoming handover.
This PI can only be observed on the Master Node.
C o u nter s
The following PM counters are used to monitor Accessibility for the Secondary Node Addition procedure:
– NRCellCU.pmNrdcSetupUeMnAtt
– NRCellCU.pmNrdcSetupUeMnSucc
– NRCellCU.pmNrdcSetupUeSnAtt
– NRCellCU.pmNrdcSetupUeSnSucc
The following PM counters are used to monitor packet forwarding in NR-DC:
– GNBCUUPFunction.pmPdcpPktFwdRecDlQos
– GNBCUUPFunction.pmPdcpPktFwdRecDlDiscQos
– EP_XnU.pmPdcpPktFwdTransDlQos
– EP_XnU.pmPdcpPktFwdTransDlDiscQos
The following PM counters are used to monitor Retainability for the Secondary Node Release procedures:
– NRCellCU.pmNrdcRelRelocUeMnAtt
45 sur 74 23/04/2024, 07:35

– NRCellCU.pmNrdcRelRelocUeMnSucc
– NRCellCU.pmNrdcRelUeSnNormal
– NRCellCU.pmNrdcRelUeSnAbnormalMnInit
– NRCellCU.pmNrdcRelUeSnAbnormalMnInitAct
– NRCellCU.pmNrdcRelUeSnAbnormalSnInit
– NRCellCU.pmNrdcRelUeSnAbnormalSnInitAct
The following PM counters are used to monitor intra-frequency, inter-gNodeB PSCell change:
– NRCellCU.pmNrdcPSCellChangeMnAttInterSgnb
– NRCellCU.pmNrdcPSCellChangeMnSuccInterSgnb
– NRCellCU.pmNrdcPSCellChangeSnAttInterSgnb
– NRCellCU.pmNrdcPSCellChangeSnSuccInterSgnb
– NRCellCU.pmNrdcPSCellChangeResAllocSnAttInterSgnb
– NRCellCU.pmNrdcPSCellChangeResAllocSnSuccInterSgnb
The following PM counters are used to monitor UEs connected with NR-DC:
– NRCellCU.pmRrcConnLevelMaxNrDc
– NRCellCU.pmRrcConnLevelSumNrDc
– NRCellCU.pmRrcConnLevelMaxSa
– NRCellCU.pmRrcConnLevelSumSa
– NRCellCU.pmRrcConnLevelSamp
The following EBS counters are used to monitor UEs connected with NR-DC:
– pmEbsRrcConnLevelMaxSa, which can be used as a flexible counter.
– pmEbsRrcConnLevelSumSa, which can be used as a flexible counter.
– pmEbsRrcConnLevelSamp
The EBS counters are associated with the NRCellCU MO. For information on the EBS counters, see Lists and Delta
Lists.
The following EBS counters are used to monitor the intra-cell handover at Secondary Node Addition and Release
procedures in NR-DC:
– pmEbsNrdcRelRelocUeMnAttIcho
– pmEbsNrdcRelRelocUeMnSuccIcho
– pmEbsNrdcSetupUeMnAttIcho
– pmEbsNrdcSetupUeMnSuccIcho
Lists.
The following EBS counters associated with the EUtranCellRelation and the NRCellCU MOs can be used to
monitor Master Node mobility with the NrDcConfigured filter applied:
– pmEbsHoPrepAttOutEutran
– pmEbsHoPrepAttOutEutranPoorCov
46 sur 74 23/04/2024, 07:35

– pmEbsHoPrepSuccOutEutran
– pmEbsHoPrepSuccOutEutranPoorCov
– pmEbsHoExeAttOutEutran
– pmEbsHoExeAttOutEutranPoorCov
– pmEbsHoExeSuccOutEutran
– pmEbsHoExeSuccOutEutranPoorCov
For information on the EBS counters, see Lists and Delta Lists.
The following EBS counters associated with the NRCellCU and the NRCellRelation MOs can be used to monitor
Master Node mobility with the NrDcConfigured filter applied:
– pmEbsHoPrepAttOutInterGnb
– pmEbsHoPrepAttOutInterGnbIntraF
– pmEbsHoPrepAttOutIntraGnb
– pmEbsHoPrepAttOutIntraGnbIntraF
– pmEbsHoPrepSuccOutInterGnb
– pmEbsHoPrepSuccOutInterGnbIntraF
– pmEbsHoPrepSuccOutIntraGnb
– pmEbsHoPrepSuccOutIntraGnbIntraF
– pmEbsHoExeAttOutInterGnb
– pmEbsHoExeAttOutInterGnbIntraF
– pmEbsHoExeAttOutIntraGnb
– pmEbsHoExeAttOutIntraGnbIntraF
– pmEbsHoExeSuccOutInterGnb
– pmEbsHoExeSuccOutInterGnbIntraF
– pmEbsHoExeSuccOutIntraGnb
– pmEbsHoExeSuccOutIntraGnbIntraF
The following PM counters can be used to monitor the switching of downlink MCG and SCG radio resources of the
Secondary Node terminated split DRB:
– GNBCUUPFunction.pmPdcpRadioResSwitchDlMcg
– GNBCUUPFunction.pmPdcpRadioResSwitchDlScg
The following EBS counters associated with the GNBCUUPFunction MO can be used to monitor the switching of uplink
MCG and SCG radio resources of the Secondary Node terminated split DRB:
– GNBCUUPFunction.pmEbsNrdcPrimaryCgSwitchUlMcgTrigger$
– GNBCUUPFunction.pmEbsNrdcPrimaryCgSwitchUlScgTrigger$
For more information on the EBS counters, see Lists and Delta Lists - Referral Document.
The GNBCUUPFunction.pmProhibitTimerRefuseUlLegSwitch PM counter can be used to monitor how many
times the uplink radio resource switching to SCG radio resources is rejected because of the
GNBCUUPFunction.endcUlNrRetProhibTimer attribute setting.
47 sur 74 23/04/2024, 07:35

The following EBS counters associated with the NRCellCU MO provide observability for downlink RLC buffer
monitoring:
– pmEbsNrdcSetupMnBufMonConfig
– pmEbsNrdcSetupMnBufMonReport
The following PM counters can be used to monitor measurement gap handling in NR-DC:
– NRCellDU.pmMeasGapDurationDistr
– NRCellDU.pmMeasGapUeMaxDistr
– NRCellDU.pmMeasGapUeMnMaxDistr
– NRCellDU.pmMeasGapUeSumDistr
– NRCellDU.pmMeasGapUeMnSumDistr
– NRCellDU.pmMeasGapUeSamp
The following PM counters are used to monitor the number of UEs using the cell as a PSCell or a PCell with configured
downlink SCells:
– NRCellCU.pmCaConfigDlSumNrdcDistr
– NRCellCU.pmCaConfigDlSumSaDistr
The following EBS counters associated with the NRCellDU MO are used to monitor user throughput on the Master
Node:
– pmEbsnMacDrbThpDlMbbHighVolDistr
– pmEbsnMacDrbThpDlMbbLowVolDistr
– pmEbsnMacUeThpUlMbbHighVolDistr
– pmEbsnMacUeThpUlMbbLowVolDistr
– pmEbsnMacPduVolDlUeSCell
– pmEbsnMacPduVolDlUePCell
The following EBS counters are used to monitor the dynamic modification of QoS properties:
– pmEbsDrbModAtt
– pmEbsDrbModSucc
– pmEbsDrbModFailCauseGrpNgCause
Lists.
Eve nt s
The following PM events are used for monitoring the Secondary Node Addition procedure and the messages used in the
procedure:
– CuCpProcMnNrdcSetup
– CuCpProcSnNrdcSetup
– CuCpXnSNodeAdditionRequest
48 sur 74 23/04/2024, 07:35

– CuCpXnSNodeAdditionRequestAcknowledge
– CuCpXnSNodeAdditionRequestReject
– CuCpXnXnUAddressIndication
– CuCpXnSNodeReconfigurationComplete
– CuCpXnSnStatusTransfer
The CuCpProcSnNrdcSetup PM event can be used to monitor the following NR-DC procedures:
– Initial Secondary Node Addition
– PSCell Change
The reception of A4 measurement reports can be monitored using the CuCpMeasurementReportSaEval PM event.
The following PM events are used to monitor the Master Node Initiated Secondary Node Modification procedure:
– CuCpXnSNodeModificationRequest
– CuCpXnSNodeModificationRequestAcknowledge
– CuCpXnSNodeModificationRequestReject
The following PM events are used to monitor the Secondary Node Initiated Secondary Node Modification procedure:
– CuCpXnSNodeModificationConfirm
– CuCpXnSNodeModificationRefuse
– CuCpXnSNodeModificationRequired
– DuProcUeContextModification
The following PM events are used to monitor both the Master Node initiated Secondary Node Modification and the
Secondary Node initiated Secondary Node Modification procedures:
– CuCpProcMnNrdcModification, which is monitored in the Master Node.
– CuCpProcSnNrdcModification, which is monitored in the Secondary Node.
The Secondary Node Modification procedure can be used to transfer the new QoS properties of already established
QoS flows in Secondary Node terminated PDU sessions. The events can be also used to monitor the modification of
QoS properties of Secondary Node terminated PDU sessions.
The CuUpProcSnNrdcUlPrimaryCgSwitch PM event is used to monitor the NR-DC switching of uplink MCG and
SCG radio resources of the Secondary Node terminated split DRB procedure.
When the Master Node uses the PDU Session Resource Modify Indication procedure, the following PM events can be
monitored:
– CuCpNgPduSessionResourceModifyIndication
– CuCpNgPduSessionResourceModifyConfirm
The RLF detection can be monitored by using the CuCpRrcScgFailureInformation PM event.

The CuCpPerCellRrcConnectedUe PM event is used for monitoring the connected UEs in the following ways:
– The connected NR SA UEs, including those configured with NR-DC, in the PCell
– The connected UEs configured with NR-DC in the PSCell
The following PM events are used for monitoring the Secondary Node Release procedures and the messages used in
the procedures:
49 sur 74 23/04/2024, 07:35

– CuCpProcMnNrdcRelease
– CuCpProcSnNrdcRelease
– CuCpXnSNodeReleaseRequest
– CuCpXnSNodeReleaseRequestAcknowledge
– CuCpXnSNodeReleaseReject
– CuCpXnSNodeReleaseRequired
– CuCpXnSNodeReleaseConfirm
– CuCpXnXnUAddressIndication
– CuCpXnUeContextRelease
– CuCpXnSnStatusTransfer
The following PM events are updated with the NrDcConfigured filter to monitor Master Node mobility and to include
the nrdc_configured event parameter:
– CuCpProcNrHoPrepOut
– CuCpProcNrHoExeOut
The following PM events are used to monitor the Error Indication procedure between the Master Node and the
Secondary Node:
– CuCpXnErrorIndicationCommon
– CuCpXnErrorIndicationDedicated
The following PM events are used to monitor intra-frequency, inter-gNodeB PSCell change:
– CuCpMeasurementReportNrdcEval
– CuCpProcMnNrdcSNodeChange
– CuCpProcSnNrdcSNodeChange
– CuCpRrcULInformationTransferMRDC
– CuCpXnRrcTransfer
– CuCpXnSNodeChangeConfirm
– CuCpXnSNodeChangeRefuse
– CuCpXnSNodeChangeRequired
The DuProcUeContextModification PM event is used to monitor the UE context modification in the Secondary
Node.
The following PM events provide observability for downlink RLC buffer monitoring:
– CuCpMnNrdcSetupBufMonConfig
– CuCpMnNrdcSetupBufMonReport
The DuPerUeTrafficRep PM event with the PER_UE_MAC_MEAS_GAP_DRX_INACT event parameter can be used to
monitor the expiration of the DRX inactivity timer during a measurement gap in the Secondary Node.
7 Activate NR-NR Dual Connectivity

To use the feature, it must be activated following the usual feature activation procedure.
50 sur 74 23/04/2024, 07:35

P re re q u i s i te s
– The license key is installed both in the Master Node and the Secondary Node.
– The conflicting features are deactivated on the Master Node and the Secondary Node.
– CCTR is active for at least one week before this procedure to collect enough troubleshooting data.
S te p s
1. Set the attribute FeatureState.featureState to ACTIVATED in the FeatureState=CXC4012582 MO

instance on both the Master Node and the Secondary Node.
When the feature is activated, to enable the use of NR-DC for UEs in the PCell on the Master Node:
2. Set the NrdcMnCellProfileUeCfg.nrdcEnabled attribute to true.
After This Task

Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.
8 Deactivate NR-NR Dual Connectivity

If the feature is no longer needed, it can be deactivated following the usual feature deactivation procedure. It must
also be deactivated before the activation of any conflicting feature.
– CCTR is active for at least one week before this procedure to collect enough troubleshooting data.
S te p s
1. Set the NrdcMnCellProfileUeCfg.nrdcEnabled attribute to false in the PCell on the Master Node.
2. Set the attribute FeatureState.featureState to DEACTIVATED in the FeatureState=CXC4012582 MO

instance on both the Master Node and the Secondary Node.
After This Task

Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.
9 Engineering Guidelines for NR-NR Dual Connectivity

9.1 Configure IP Connectivity in NR-DC for the Xn-U Interface
In NR-DC, the user plane connection between the Master Node and the Secondary Node is established over the Xn-U
interface.
Separate LocalIpEndpoint MO instances exist on both the Master Node and on the Secondary Node. On the Master
Node, the MO is under the EndpointResource MO, which is a child to the GNBDUFunction MO. On the Secondary
Node, the MO is under the EndpointResource MO, which is a child to the GNBCUUPFunction MO.
S te p s
1. Configure the LocalIpEndpoint.addressRef attribute on the Master Node to reference an instance of either the
AddressIPv4 or AddressIPv6 MO.
The Master Node uses the configured IP address for local transport network endpoints for the user plane
51 sur 74 23/04/2024, 07:35

connection.
2. Add the F1 value to the list in the LocalIpEndpoint.interfaceList attribute on the Master Node.
The Xn-U interface uses the IP address referenced in the LocalIpEndpoint.addressRef attribute on the Master
Node to connect to the Secondary Node.
3. Configure the LocalIpEndpoint.addressRef attribute on the Secondary Node to reference an instance of either
the AddressIPv4 or AddressIPv6 MO.
The Secondary Node uses the configured IP address for local transport network endpoints for the user plane
connection.
4. Add the XN value to the list in the LocalIpEndpoint.interfaceList attribute on the Secondary Node.
The Xn-U interface uses the IP address referenced in the LocalIpEndpoint.addressRef attribute on the
Secondary Node to connect to the Master Node.
Results
The IP addresses to connect the nodes in NR-DC over the Xn-U interface are defined.
After This Task

Both the Master Node and the Secondary Node need to be restarted, so that the IP address configuration can take
effect.
9.2 TCP Optimization for the Secondary Node Terminated Split DRB in NR-DC
TCP optimization provides reduced queuing delay in downlink user plane traffic to improve end user performance. AQM
is used for TCP optimization of the Secondary Node terminated split DRBs in NR-DC. AQM is performed in the downlink
PDCP buffer of the Secondary Node when configured using the CUUP5qi.aqmMode attribute. The attribute can be
configured to one of the following values, depending on the traffic characteristics:
OFF AQM is not used.
Packets are discarded if they become older than 1 second.
MODE1 AQM is active. Recommended AQM mode for DRBs with non-GBR traffic.
A single packet is discarded when it becomes older than the minimum age threshold. The minimum age of
packets is calculated as 2 × CUUP5qi.estimatedE2ERTT.
A prohibit timer, set as 4 × CUUP5qi.estimatedE2ERTT, is present between discarding single packets.
All packets that are older than the maximum age threshold are discarded. The maximum age of packets is
calculated as 10 × CUUP5qi.estimatedE2ERTT.
When the DRB exceeds the predefined high rate, the minimum age AQM is performed at lower packet age
than the normal rate condition value defined by 2 × CUUP5qi.estimatedE2ERTT.
NR-DC DRBs do not use AQM minimum age in RLC under PDCP aggregation. If the LTE-NR Downlink
Aggregation feature is disabled, or the CUUP5qi.dcDlPdcpAggrPrioCg parameter is set to
NO_AGGREGATION, the AQM minimum age is handled in RLC.
A reduced value of the CUUP5qi.estimatedE2ERTT attribute leads to AQM packet discard performed at a
lower packet age, which results in the following changes:
– Reduced packet queuing delay
– Increased number of AQM packet discards in PDCP stepping EP_NgU.pmPdcpPktRecDlDiscAqm5qi

and EP_NgU.pmPdcpPktRecDlDisc5qi
Performance can be affected negatively if the configured value of the CUUP5qi.estimatedE2ERTT

attribute is too low and there are not enough user data packets available for transmission temporarily.
It is recommended to align the setting of the CUUP5qi.estimatedE2ERTT attribute with the value of AQM
maximum age for DRBs in RLC in the gNodeB-DU by configuring the CUUP5qi.estimatedE2ERTT attribute
52 sur 74 23/04/2024, 07:35

with an equal or lower value than the DU5qi.estimatedE2ERTT attribute.

The reason for this is if packets reach a lower AQM maximum age in RLC at a lower age than the higher AQM
maximum age in PDCP, the packets are discarded, resulting in higher values for the
RpUserPlaneLink.pmPdcpPktTransDlDiscAqmQos and
RpUserPlaneLink.pmPdcpPktTransDlDiscQos counters.
MODE2 AQM is active. Recommended AQM mode for DRBs with GBR traffic.
Packets older than the sum of CUUP5qi.packetDelayBudget and
CUUP5qi.packetDelayBudgetOffset are discarded.
9.3 Configure 5QI and ARP Levels for QoS Flows Allowed to Be Secondary
Node Terminated
By using different settings for each ARP and 5QI, operators can determine which QoS flows are allowed to be
Secondary Node terminated.
– An instance of the NrdcSnTermination MO exists under the GNBCUCPFunction MO.
– The NrdcSnTermination.defaultNrdcSnTerm is set to false.
– An instance of NrdcSnTerminationUeCfg MO exists as the child of the NrdcSnTermination MO.
– An instance of the CUCP5qi MO is configured as a 5QI profile representing the configuration of a QoS flow.
S te p s
1. Configure the CUCP5qi.nrdcSnTerminationRef attribute to contain a reference to the instance of the

NrdcSnTermination MO.
2. Configure a value to the NrdcSnTerminationUeCfg.nrdcSnTermAllowed attribute that allows Secondary

Node termination for an ARP or an ARP combination.
Results
This specific QoS flow is allowed to be terminated by the Secondary Node. The DRB carrying this QoS flow is configured
as a Secondary Node terminated split DRB.

9.4 Configuration Considerations for Switching of Uplink MCG and SCG Radio
Resources of the Secondary Node Terminated Split DRB
In deployments with a mix of EN-DC and NR-DC UEs, the value of the NRCellDU.endcUlNrLowQualThresh
attribute might have to be increased to avoid RLF for NR-DC UEs. By adjusting the
NRCellDU.endcUlNrLowQualThresh attribute to be the most optimal for NR-DC, the uplink PDCP PDU
transmission throughput can be improved and maintained in variable High-Band radio conditions.
9.5 Observability of NR-DC Setup Based on Downlink Buffer Threshold

Configuration
The benefits of configuring a downlink buffer threshold based on the age or volume of the packets during NR-DC setup
as shown in Table 21.
Table 21 PM Counter Changes with Downlink Buffer Threshold Configured
PM C ou nter Change
53 sur 74 23/04/2024, 07:35

PM C ou nter Change
NRCellDU.pmMacVolDl
NRCellDU.pmMacVolDlDrb
Increased in the Master Node and decreased in the
NRCellDU.pmMacVolDlDrbQos
Secondary Node
NRCellDU.pmMacVolUl
NRCellDU.pmMacVolUlResUe
NRCellCU.pmNrdcSetupUeMnAtt
NRCellCU.pmNrdcSetupUeMnSucc
Decreased
NRCellCU.pmNrdcSetupUeSnAtt
NRCellCU.pmNrdcSetupUeSnSucc
NRCellCU.pmNrdcRelUeSnNormal
NRCellCU.pmNrdcRelUeSnAbnormalMnInit
NRCellCU.pmNrdcRelUeSnAbnormalMnInitAct Decreased
NRCellCU.pmNrdcRelUeSnAbnormalSnInit
NRCellCU.pmNrdcRelUeSnAbnormalSnInitAct
NRCellCU.pmRrcConnLevelMaxNrDc
Decreased
NRCellCU.pmRrcConnLevelSumNrDc
9.6 Configuration of UE Group-Adapted NR-DC Functions

The UE Grouping Framework makes it possible to differentiate system behavior between UE groups.
Table 22 shows the MOM attributes used for service-aware differentiation of functions in NR-DC.
Table 22 MOM Attributes Used for Service-Aware Differentiation of Functions in NR-DC
Fu n c t i o n At t r i b u t e
Enabling NR-DC in the PCell NrdcMnCellProfileUeCfg.nrdcEnabled
NrdcMnCellProfileUeCfg.nrdcSetupDlPktAgeThr
Downlink RLC buffer monitoring
NrdcMnCellProfileUeCfg.nrdcSetupDlPktVolThr
A4 measurement timer NrdcMnCellProfileUeCfg.nrdcMeasTime
A4 measurement restart timer NrdcMnCellProfileUeCfg.nrdcMeasRestartTime
RSRP A4 measurement report
criteria when searching for PSCell NrdcMnCellProfileUeCfg.rsrpPSCellCandidate
candidate
Intra-Frequency Mobility Control in
the Secondary Node – IntraFreqMCCellProfileUeCfg.rsrpBetterSpCell
Secondary Node termination of QoS
flows – NrdcSnTerminationUeCfg.nrdcSnTermAllowed
Once NR-DC is set up for a UE and the UE group-adapted NR-DC functions are in use, a change of the UE group
resulting in a new configuration of the UE group has no impact. For example, if downlink RLC buffer monitoring is
ongoing for a UE when the UE group changes in such a way that the NrdcMnCellProfileUeCfg.nrdcEnabled
attribute is set to false, the ongoing downlink RLC buffer monitoring is not impacted.
Note: For the Intra-Frequency Mobility Control in the Secondary Node, the change of the UE group can result in the
change of the A3 measurement during an active connection.
Appendix A: Feature Change History

This section lists changes that affected this feature and the impact it had on the network.
54 sur 74 23/04/2024, 07:35

Appendix A.a: 22.Q1: Switching of Uplink MCG and SCG Radio Resources of
the Secondary Node Terminated Split DRB in NR-DC
The enhancement enables the switching of the uplink primary path for PDCP PDU transmission of the Secondary
Node terminated split DRBs based on the uplink radio quality in the SCG.
Feature Name: NR-NR Dual Connectivity

Feature Identity: FAJ 121 5380
Value Package Name: Peak Rate Evolution
Value Package Identity: FAJ 801 4005
Node Type: Baseband Radio Node
Access Type: NR
Summary and Benefits

By allowing the switching of the uplink primary path of Secondary Node terminated split DRBs based on dynamic
evaluation of the SCG uplink quality, the enhancement provides the following benefits:
– It reduces the number of Secondary Node releases that are caused by SCG RLF for UEs that are configured with
NR-DC.
– It maintains uplink PDCP PDU transmission throughput in variable High-Band radio conditions.

The switching of the uplink MCG and SCG radio resources of the Secondary Node terminated split DRB improves
Retainability for the Secondary Node in NR-DC.
Operation
The enhancement introduces the following attributes that are used to configure Xn interface timers for NR-DC
procedures:
– GNBCUCPFunction.tXnDcOverall
– GNBCUCPFunction.tXnDcPrep
The enhancement makes the following attributes applicable to configuring the uplink MCG and SCG radio resource
switching function of the LTE-NR Dual Connectivity feature used in NR-DC:
– GNBCUUPFunction.endcUlNrRetProhibTimer
– NRCellDU.endcUlLegSwitchEnabled
– NRCellDU.endcUlNrLowQualThresh
– NRCellDU.endcUlNrQualHyst
The GNBCUUPFunction.pmProhibitTimerRefuseUlLegSwitch PM counter can be used to monitor how many

times the uplink radio resource switching to SCG radio resources is rejected because of the
GNBCUUPFunction.endcUlNrRetProhibTimer attribute setting.
If the initial uplink primary path is SCG, the following PM counters in the Secondary Node can decrease if switching of
the uplink MCG and SCG radio resources of the Secondary Node terminated split DRB for NR-DC is used:
55 sur 74 23/04/2024, 07:35

– NRCellDU.pmMacTimeUlResUe
– NRCellDU.pmMacVolUl
– NRCellDU.pmMacVolUlResUe
– NRCellDU.pmMacVolUlResUeLate
– NRCellDU.pmMacVolUlResUeLastSlot
– NRCellDU.pmPuschSchedActivity
– NRCellDU.pmMacHarqUlAckQpsk
– NRCellDU.pmMacHarqUlDtxQpsk
– NRCellDU.pmMacHarqUlNackQpsk
– RpUserPlaneLink.pmPdcpPktLossUlQos
– RpUserPlaneLink.pmPdcpPktLossUlToDiscQos
– RpUserPlaneLink.pmPdcpPktLossUlToQos
– RpUserPlaneLink.pmPdcpVolRecUlQos on the internal RpUserPlaneLink
– RpUserPlaneLink.pmPdcpPktRecUlQos on the internal RpUserPlaneLink
– RpUserPlaneLink.pmPdcpPktRecUlOooQos
If the initial uplink primary path is SCG, the following PM counters in the Master Node can increase if switching of the
uplink MCG and SCG radio resources of the Secondary Node terminated split DRB for NR-DC is used:
– NRCellDU.pmMacTimeUlResUe
– NRCellDU.pmMacVolUlResUeLate
– NRCellDU.pmMacVolUlResUeLastSlot
– NRCellDU.pmPuschSchedActivity
– NRCellDU.pmMacHarqUlAckQpsk
– NRCellDU.pmMacHarqUlNackQpsk
If the initial uplink primary path is SCG, the following PM counters in the Secondary Node can increase if switching of
the uplink MCG and SCG radio resources of the Secondary Node terminated split DRB for NR-DC is used:
– RpUserPlaneLink.pmPdcpVolRecUlQos on the external RpUserPlaneLink
– RpUserPlaneLink.pmPdcpPktRecUlQos on the external RpUserPlaneLink
The enhancement introduces the following PM events:
– CuCpXnSNodeModificationConfirm
– CuCpXnSNodeModificationRefuse
56 sur 74 23/04/2024, 07:35

– CuCpXnSNodeModificationRequired
The following PM events are used to monitor both the Master Node initiated Secondary Node Modification and the
Secondary Node initiated Secondary Node Modification procedures:
– CuCpProcMnNrdcModification, which is monitored in the Master Node.
– CuCpProcSnNrdcModification, which is monitored in the Secondary Node.
The enhancement deprecates the CuCpProcNrdcModification PM event.

The CuUpProcSnNrdcUlPrimaryCgSwitch PM event is used to monitor the NR-DC switching of uplink MCG and
SCG radio resources of the Secondary Node terminated split DRB procedure.
H a rd wa re
No special hardware requirements.
I n te r fa c e s
This change affects the following interfaces:
Xn-C The enhancement introduces the following messages over the Xn-C interface:
– S-NODE MODIFICATION CONFIRM
– S-NODE MODIFICATION REFUSE
– S-NODE MODIFICATION REQUIRED

It is recommended to use ENM version 22.1 or later to support the MOM changes introduced by this feature
enhancement. If the Release Independence Manager application is used, the MOM changes are supported on earlier
ENM versions also.

Appendix A.b: 22.Q3: PSCell Change, Intra-Frequency Inter-gNodeB
This enhancement enables intra-frequency, inter-gNodeB PSCell change for UEs that are configured with NR-DC.

Value Package Identity FAJ 801 4005
Access Type NR
I mp a c t a t Up g rad e Mandatory

Intra-frequency, inter-gNodeB PSCell change moves the UE that is configured with NR-DC from the serving PSCell that
has poor radio link quality to a target PSCell that has better radio link quality. This way, the number of Secondary Node
releases that are caused by RLF can be reduced for UEs that are configured with NR-DC.

With this feature enhancement, the following benefits are expected:
– The number of abnormal Secondary Node releases for UEs that are caused by RLF can be reduced. This improves
retainability.
57 sur 74 23/04/2024, 07:35

– Improved end-user performance and data throughput is expected because of the following factors:
• The UE spends less time in the SCG with poor radio link quality.
• The UE can continue to use the higher bit rates of High-Band frequencies in an SCG with good radio link
quality.
• The PSCell change for the UE results in no packet loss.
This feature enhancement has an impact on the following PIs:
– The NR-DC Inter-gNodeB PSCell Change Success Rate Captured on Secondary Node PI is expected to increase,
because the user plane interruption time during which the UE moves from one High-Band cell to another is
reduced.
– The NR-DC Release Abnormal Active Rate Captured on Secondary gNodeB PI is expected to decrease because of
the decrease in the number of abnormal Secondary Node releases for NR-DC-capable UEs.
Operation
This feature enhancement makes the following attributes applicable to configuring A3 measurements on the
Secondary Node in NR-DC:
– IntraFreqMCCellProfileUeCfg.rsrpBetterSpCell
• hysteresis
• offset
• timeToTrigger
• hysteresis
• offset
• timeToTrigger
This feature enhancement introduces the following PM counters to monitor intra-frequency, inter-gNodeB PSCell
change:
– NRCellCU.pmNrdcPSCellChangeMnAttInterSgnb
– NRCellCU.pmNrdcPSCellChangeMnSuccInterSgnb
– NRCellCU.pmNrdcPSCellChangeSnAttInterSgnb
– NRCellCU.pmNrdcPSCellChangeSnSuccInterSgnb
– NRCellCU.pmNrdcPSCellChangeResAllocSnAttInterSgnb
– NRCellCU.pmNrdcPSCellChangeResAllocSnSuccInterSgnb
The following PM counters are stepped for packet forwarding during intra-frequency, inter-gNodeB PSCell change:
– EP_XnU.pmPdcpPktFwdTransDlQos
– EP_XnU.pmPdcpPktFwdTransDlDiscQos
– GNBCUUPFunction.pmPdcpPktFwdRecDlQos
58 sur 74 23/04/2024, 07:35

– GNBCUUPFunction.pmPdcpPktFwdRecDlDiscQos
This feature enhancement introduces the following PM events to monitor intra-frequency, inter-gNodeB PSCell change:
– CuCpMeasurementReportNrdcEval
– CuCpProcMnNrdcSNodeChange
– CuCpProcSnNrdcSNodeChange
– CuCpRrcULInformationTransferMRDC
– CuCpXnRrcTransfer
– CuCpXnSNodeChangeConfirm
– CuCpXnSNodeChangeRefuse
– CuCpXnSNodeChangeRequired
This feature enhancement makes the CuCpProcSnNrdcSetup PM event applicable to track intra-frequency, inter-
gNodeB PSCell change during a Secondary Node Addition procedure.
This feature enhancement introduces the NR-DC Inter-gNodeB PSCell Change Success Rate Captured on Secondary
Node PI.
I n te r fa c e s
This feature enhancement affects the following interfaces:
Xn-C New information is added to the XnAP S-NODE ADDITION REQUEST message, which indicates the trigger of
the Secondary Node Addition procedure.
This feature enhancement introduces the following messages over the Xn-C interface:
– S-NODE CHANGE CONFIRM
– S-NODE CHANGE REFUSE
– S-NODE CHANGE REQUIRED
– RRC TRANSFER
Uu A3 measurement configuration is added to the RRC CG-Config message.

This feature enhancement introduces the RRC ULInformationTransferMRDC message.
H a rd wa re
No specific hardware requirements.

ENM versions also.

Appendix A.c: 22.Q3: Secondary Node-Triggered SCG Reconfiguration and
Improved Observability for Secondary Node Release in NR-DC
This feature enhancement introduces Secondary Node-triggered SCG reconfiguration for the UE while it is
connected in NR-DC. It also provides improved observability for the Secondary Node Release procedure.
Additionally, through this feature enhancement, the UE can request the release of the Secondary Node when it does
not use the SCG resources.
59 sur 74 23/04/2024, 07:35


Access Type NR

SCG reconfiguration of the UE connected with NR-DC is required in the following cases:
– At uplink transmission port and waveform switch
– At CSI-RS configuration for wide beam support
– When the maximum number of scheduling requests is reached in the SCG.
Any of these cases triggers the Secondary Node Initiated Secondary Node Modification procedure with the purpose to
reconfigure the SCG. This way, the number of Secondary Node Releases caused by RLF is reduced.
UE battery life is extended when the UE requests the release of the Secondary Node as SCG resources are released.

NR-DC performance degradation can be avoided if the SCG used by the UE can be reconfigured.
The value of the NR-DC Release Abnormal Active Rate Captured on Secondary gNodeB PI, which is used for
monitoring Secondary Node releases, decreases. This happens because the value of the
NRCellCU.pmNrdcRelUeSnAbnormalSnInit and NRCellCU.pmNrdcRelUeSnAbnormalSnInitAct PM
counters decreases.
Table 23 shows the PM counters that can be used to monitor when the UE sends the RRC SCGFailureInformation
message with special values to the Master Node to trigger a Master Node initiated Secondary Node Release procedure.
Table 23 PM Counter Changes during the Secondary Node Release Procedure
PM C ou nter Change
NRCellCU.pmNrdcRelUeSnNormal Increase
NRCellCU.pmNrdcRelUeSnAbnormalSnInit Decrease
NRCellCU.pmNrdcRelUeSnAbnormalSnInitAct Decrease
Operation
An additional field that specifies the modification type is added to the CuCpProcSnNrdcModification and
DuProcUeContextModification PM events.
H a rd wa re
I n te r fa c e s
This change affects the following interfaces:
– Uu
• The RRC RRCReconfiguration message is updated with information on SCG reconfiguration.
• The RRC SCGFailureInformation message is updated with attributes of the measResultFreqList IE

set to nil or empty. This triggers the Master Node initiated Secondary Node Release.
– Xn-C
• The XnAP S-NODE MODIFICATION REQUIRED and XnAP S-NODE MODIFICATION CONFIRM messages
60 sur 74 23/04/2024, 07:35

are updated.

ENM versions also.

Appendix A.d: 22.Q3: Downlink Buffer-Based NR-DC Setup
Downlink RLC buffer monitoring allows operators to trigger the NR-DC setup based on UE traffic level in the
downlink RLC buffer.

Access Type NR
I mp a c t a t Up g rad e Optional

For UEs with short data sessions, unnecessary NR-DC setups can be avoided using downlink RLC buffer threshold
configuration specific to operator needs. This way, UE battery life can be extended and control signaling can be
reduced.
This feature enhancement makes it possible to configure different downlink RLC thresholds for different UE groups.

With active downlink RLC buffer monitoring, the number of NR-DC setups is expected to decrease for NR-DC-capable
UEs.
Lower traffic level is expected in the SCG because NR-DC setup is triggered less frequently.
With active downlink RLC buffer monitoring, signaling over the NG-C, Xn-C, and Uu interfaces can be reduced. This is
because for UEs with low traffic volume, NR-DC setup is not triggered when downlink RLC buffer thresholds are
configured with values above the DRB traffic level.
At higher UE traffic, A4 measurement configuration is delayed for UEs with active downlink RLC buffer monitoring
indicating high buffer status.
UE battery consumption can be reduced by using downlink RLC buffer monitoring.
Operation
The following attributes can be used to configure the downlink RLC buffer thresholds:
– NrdcMnCellProfileUeCfg.nrdcSetupDlPktAgeThr
– NrdcMnCellProfileUeCfg.nrdcSetupDlPktVolThr
The following attributes are adapted to the UE Grouping Framework:
– NrdcMnCellProfileUeCfg.nrdcEnabled
– NrdcMnCellProfileUeCfg.nrdcMeasTime
– NrdcMnCellProfileUeCfg.nrdcMeasRestartTime
– NrdcMnCellProfileUeCfg.rsrpPSCellCandidate
61 sur 74 23/04/2024, 07:35

– NrdcMnCellProfileUeCfg.nrdcSetupDlPktAgeThr
– NrdcMnCellProfileUeCfg.nrdcSetupDlPktVolThr
The Buffer-based NR-DC Setup avoidance rate Performance Indicator can be used to observe the percentage of
potential NR-DC setups that are avoided because of not meeting the buffer-based NR-DC setup criteria.
The following EBS counters associated with the NRCellCU MO are used in the formula for the Buffer-based NR-DC
Setup avoidance rate Performance Indicator:
– pmEbsNrdcSetupMnBufMonConfig
– pmEbsNrdcSetupMnBufMonReport
The following PM counters related to throughput are increased in the Master Node and decreased in the Secondary
Node when downlink RLC buffer monitoring is active:
– NRCellDU.pmMacVolDl
– NRCellDU.pmMacVolDlDrb
– NRCellDU.pmMacVolDlDrbQos
The following PM counters related to NR-DC setup are decreased when downlink RLC buffer monitoring is active:
The following PM counters related to NR-DC UE release are decreased when downlink RLC buffer monitoring is active:
The following counters related to the peak number of NR-DC UEs are decreased when downlink RLC buffer monitoring
is active:
The following PM events can be used to observe downlink RLC buffer monitoring:
– CuCpMnNrdcSetupBufMonConfig
– CuCpMnNrdcSetupBufMonReport
I n te r fa c e s
No impact.
H a rd wa re
62 sur 74 23/04/2024, 07:35


ENM versions also.

Appendix A.e: 22.Q3: Disabling the Switching of Downlink MCG and SCG
Radio Resources of the Secondary Node Terminated Split DRB for NR-NR
Dual Connectivity
This feature enhancement allows the disabling of MCG and SCG radio resource switching in downlink.

Access Type NR
I mp a c t a t Up g rad e Optional

The feature enhancement introduces the option to disable the switching of downlink MCG and SCG radio resources of
the Secondary Node-terminated split DRB. This can increase the coverage for UEs using High-Band SCG radio
resources.

Allowing too large SCG radio resource coverage can decrease performance and an increase of abnormal radio bearer
releases in poor High-Band coverage areas.
Operation
To disable MCG and SCG radio resource switching in downlink, the NRCellDU.endcDlLegSwitchEnabled attribute
must be set to false in the PSCell.
I n te r fa c e s
No impact.
H a rd wa re

No impact.

Appendix A.f: 22.Q4: Adding SCells on the Master Node at Secondary Node
Release in NR-DC
The feature enhancement enables the addition of SCells for the UE on the Master Node during the Secondary Node
Release procedure.
63 sur 74 23/04/2024, 07:35


Access Type NR

The feature enhancement ensures higher data throughput for the UE on the Master Node when the UE is not
configured with NR-DC. This is achieved by adding the SCells for the UE on the Master Node during the Secondary
Node Release procedure.

With increased use of carrier aggregation in use cases with configured NR-DC, the Low-Band and Mid-Band downlink
UE throughput might increase if Low-Band and Mid-Band SCells are configured and used during the Secondary Node
Release procedure.
The following EBS counters might change when SCells are added for the UE on the Master Node during the Secondary
Node Release procedure:
– pmEbsMacDrbThpDlMbbHighVolDistr
– pmEbsMacDrbThpDlMbbLowVolDistr
The EBS counters are associated with the NRCellDU MO. For information on the EBS counters, see Lists and Delta
Lists.
The following PM counters might change when SCells are added for the UE on the Master Node during the Secondary
Node Release procedure:
– NRCellDU.pmMacVolDlSCell
– NRCellDU.pmMacVolDlSCellExt
Operation
No impact.
I n te r fa c e s
The RRC RRCReconfiguration message is updated with information on SCells that are to be added and on SCell
measurement configuration.
H a rd wa re

The pmEbsMacDrbThpDlMbbHighVolDistr and the pmEbsMacDrbThpDlMbbLowVolDistr EBS counters are
deprecated. It is recommended that ENM versions between 21.4 and 22.3 are used for these counters to monitor the
feature enhancement. The pmEbsnMacDrbThpDlMbbHighVolDistr and the
pmEbsnMacDrbThpDlMbbLowVolDistr EBS counters replace the deprecated EBS counters and ENM version 22.3 or
later is recommended for feature enhancement observability.
The UE must support downlink carrier aggregation as specified in 3GPP TS 38.101.

64 sur 74 23/04/2024, 07:35

NR DL Carrier Aggregation
Appendix A.g: 22.Q3: Configuration of AQM MODE1 in the gNodeB-DU for
NR-DC
This feature enhancement enables the configuration of AQM maximum age in RLC for NR-DC DRBs.

Access Type NR

This feature enhancement enables the configuration of AQM maximum age in RLC for NR-DC DRBs which enables the
configuration of a higher value of the CUUP5qi.estimatedE2ERTT attribute for NR-DC DRBs.

Increasing the value of the CUUP5qi.estimatedE2ERTT attribute allows increased buffering of user data packets for
NR-DC DRBs which can improve throughput for large file downloads. Increased buffering can cause buffering delays
which can have a negative performance impact on interactive applications.
Operation
The AQM maximum age is configured using the DU5qi.estimatedE2ERTT attribute for NR-DC DRBs with the
DU5qi.aqmMode attribute configured to 1.
I n te r fa c e s
No impact.
H a rd wa re

It is required to use ENM version 22.3 or later to support the MOM changes introduced by this feature enhancement.

NR Standalone
Appendix A.h: 22.Q4: UE Group Adaptation for Secondary Node Mobility
Support and Secondary Node Termination of QoS Flows in NR-DC
This feature enhancement introduces support for UE group differentiated configuration for the intra-frequency
mobility control in the secondary node and user differentiation for secondary node termination of QoS flows
functions in the NR-NR Dual Connectivity feature.

Access Type NR
65 sur 74 23/04/2024, 07:35


U E G ro u p Ad a p ta t i o n fo r The feature enhancement allows the differentiated configuration of A3 measurement for
N R - D C I n t r a - Fr e q u e n c y intra-frequency inter-gNodeB PSCell change for UE groups. Reconfiguration of the A3
Mobility measurement is supported, if the configuration of the A3 measurement changes after the
UE is moved to another UE group during an active connection.
The UE group differentiated configuration of the NR-DC intra-frequency inter-gNodeB
PSCell change is license controlled through the User- and Service-Specific Mobility
feature.
U s e r D i f fe re nt i a t i o n fo r The feature enhancement allows the differentiated configuration of termination point

Secondary Node control of QoS flows in the Master Node. If the termination control configuration changes
Termination of QoS Flows after the UE is moved to another UE group with a different termination control
configuration, already applied configurations are not reconfigured.

By using the flexible counter framework for EBS counters, operators can define differentiated counters for different UE
groups. Events can be defined by using UE group identifiers as separate flexible counter filtering attributes. For more
information, see UE Grouping Framework.
Operation
The feature enhancement enables the following UE group-specific MO classes to be configured and used for NR-DC
UEs:
– IntraFreqMCCellProfileUeCfg
– NrdcSnTerminationUeCfg
The following UE grouping attributes are added under the NrdcSnTerminationUeCfg MO class:
– prefUeGroupList
– UeGroupList
– UeConfGroupList
The attributes for Intra.Frequency SCell Mobility are added to the IntraFreqMCCellProfileUeCfg MO instance.
I n te r fa c e s
No impact.
H a rd wa re

It is required to use ENM version 22.4 or later to support the MOM changes introduced by this feature enhancement.

Appendix A.i: 22.Q4: PCell Reconfiguration in NR-DC
The feature enhancement enables PCell reconfiguration for the UE during the Secondary Node Addition, the
Secondary Node Release, and the Inter-gNodeB, Intra-Frequency PSCell Change procedures.

66 sur 74 23/04/2024, 07:35


Access Type NR

The enhancement introduces the following functional changes:
– When generated in the Master Node, the list of allowed band combinations considers all the possible PCell
configurations.
– The PCell is reconfigured during the Secondary Node Addition and the Inter-gNodeB, Intra-Frequency PSCell
Change procedures based on the following factors:
• The UE capabilities
• The band combination that is selected by the Secondary Node
• The feature set entry that is selected by the Secondary Node
– The PCell is reconfigured based on the UE capabilities during the Secondary Node Release procedure.
With the support for PCell reconfiguration, the feature enhancement provides the following benefits:
– The number of successful NR-DC setups can increase depending on the UE capabilities.
– A maximized SCG configuration is provided based on the given UE capabilities.

With a maximized SCG configuration, the following changes can be expected:
– Data traffic volume over the Secondary Node can increase.
– The gNodeBs that act as Master Node can be further offloaded.
– A less optimized MCG configuration might be expected based on the given UE capabilities. Because of this, a
decreased uplink or downlink MCG throughput might also be expected.
The number of NR-DC users can increase.

The following PM counters in the Master Node might increase with the increased number of NR-DC users:
– NRCellCU.pmNrdcRelRelocUeMnAtt
– NRCellCU.pmNrdcRelRelocUeMnSucc
The following PM counters in the Secondary Node might increase with the increased number of NR-DC users:
67 sur 74 23/04/2024, 07:35

The following EBS counters in the Master Node might increase with the increased number of NR-DC users:
– pmEbsNrdcRelRelocUeMnAttIcho
– pmEbsNrdcRelRelocUeMnSuccIcho
– pmEbsNrdcSetupUeMnAttIcho
– pmEbsNrdcSetupUeMnSuccIcho
Lists.
Because of the maximized SCG configuration, the following PM counters, which are related to cell throughput, might be
impacted in the Secondary Node:
– NRCellDU.pmMacVolUlSCell
Because of the maximized SCG configuration, the following EBS counters, which are related to user throughput, might
be impacted in the Master Node and in the Secondary Node:
– pmEbsMacUeThpUlMbbHighVolDistr
– pmEbsMacUeThpUlMbbLowVolDistr
The EBS counters are associated with the NRCellDU MO. For information on the EBS counters, see Lists and Delta
Lists.
Operation
No impact.
I n te r fa c e s
The MCG CellGroupConfig IE, which is included in the RRC RRCReconfiguration message, might contain the
new PCell configuration during the following NR-DC procedures:
– Secondary Node Addition
– Inter-gNodeB, Intra-Frequency PSCell Change
– Secondary Node Release
H a rd wa re
68 sur 74 23/04/2024, 07:35


The following EBS counters are deprecated:
– pmEbsMacUeThpUlMbbHighVolDistr
– pmEbsMacUeThpUlMbbLowVolDistr
It is recommended that ENM versions between 21.4 and 22.3 are used for these counters to monitor the feature
enhancement.
The following EBS counters replace the deprecated EBS counters:
ENM version 22.3 or later is recommended for feature enhancement observability.

Appendix A.j: 23.Q2: Measurement Gap-Aware Secondary Node Scheduling
for NR-DC
With the feature enhancement, the measurement gap configuration on the Master Node is forwarded to the
Secondary Node in NR-DC deployments.

Access Type NR

If the measurement gap configuration on the Master Node is forwarded to the Secondary Node, the Secondary Node
does not schedule the UE connected with NR-DC during the measurement gap. This way, DTX can be avoided in the
SCG.
During the Secondary Node Addition Procedure, the Master Node forwards the DRX configuration, which is used in the
MCG, to the Secondary Node. Based on the forwarded information, the Secondary Node aligns the DRX configuration
of the SCG with the DRX configuration of the MCG. This also applies when the Secondary Node initiated Secondary
Node Change procedure is performed.
The measurement gap information and the DRX configuration are sent from the Master Node to the Secondary Node at
the Secondary Node Addition and Secondary Node initiated Secondary Node Change procedures.
If a measurement gap is configured or removed on the Master Node, the Master Node initiated Secondary Node
Modification procedure is used to forward measurement gap information to the Secondary Node in the following cases:
– If a measurement gap is added, the measurement gap configuration is sent to the Secondary Node.
– If a measurement gap is removed, an instruction is sent to the Secondary Node to stop configuring measurement
69 sur 74 23/04/2024, 07:35

gaps.
The DRX configurations of the MCG and the SCG are only aligned at Secondary Node Addition. If the DRX
configuration changes during NR-DC operation, the DRX configurations of the MCG and the SCG might not remain
aligned. This can affect UE power consumption.
The measurement gap can change in the Master Node because of UE group changes that are triggered by certain
procedures. If this happens, the Secondary Node is not informed about the updated measurement gap configuration.
The following procedures in NR-DC can cause changes in UE groups:
– PDU Session Resource Setup
– PDU Session Resource Modify
– PDU Session Resource Release
The feature enhancement provides the following benefits:
– The Secondary Node does not schedule the UE that is connected with NR-DC during the measurement gap. This
way, the DTX rate in the Secondary Node is expected to decrease. This might improve link adaptation and it also
improves UE throughput in downlink and uplink.
– HARQ transmission failures are expected to decrease in the Secondary Node.
– Aligning the MCG DRX configuration with that of the SCG can reduce UE power consumption.
– Cell throughput might increase in the Secondary Node, as the Secondary Node can schedule more UEs during the
measurement gap in addition to those that use the measurement gap.

With the feature enhancement, the following performance impact can be expected:
– UE throughput is increased in downlink and uplink.
– UE power consumption might be reduced.
– Cell throughput might be increased in the Secondary Node.
The following PM counters can be used to observe the reduction in the DTX rate:
– NRCellDU.pmMacHarqDlDtxQpsk
– NRCellDU.pmMacHarqDlDtx16Qam
– NRCellDU.pmMacHarqUlDtx16Qam
– NRCellDU.pmMacHarqDlDtx64Qam
– NRCellDU.pmMacHarqUlDtx64Qam
The following PM counters can be used to observe the improvement in cell throughput:
– NRCellDU.pmMacVolDl
The following PM counters can be used to monitor measurement gap handling in NR-DC:
– NRCellDU.pmMeasGapDurationDistr
– NRCellDU.pmMeasGapUeMaxDistr
– NRCellDU.pmMeasGapUeMnMaxDistr
70 sur 74 23/04/2024, 07:35

– NRCellDU.pmMeasGapUeSumDistr
– NRCellDU.pmMeasGapUeMnSumDistr
– NRCellDU.pmMeasGapUeSamp
The DuPerUeTrafficRep PM event with the PER_UE_MAC_MEAS_GAP_DRX_INACT event parameter can be used to
monitor the interval of the DRX inactivity timer during a configured measurement gap.
Operation
No impact.
I n te r fa c e s
The feature enhancement affects the following interfaces:
Uu Information on the applied measurement gap in the Master Node and the Secondary Node is transmitted to the
UE during the RRC Reconfiguration procedure.
Xn-C Information on measurement gap configuration, DRX configuration for MCG, and measurement configuration is
sent in the XnAP S-NODE ADDITION REQUEST message.
Information on measurement gap configuration is sent in the XnAP S-NODE MODIFICATION REQUEST
message.
H a rd wa re

ENM versions also.

Measurement Gap-Aware NR Scheduling
Appendix A.k: NR-DC with Low-Band and Mid-Band Carrier Aggregation
Low-Band and Mid-Band carrier aggregation can be used at the same time as High-Band carrier aggregation for
UEs connected with NR-DC.

Access Type NR

This feature enhancement makes it possible to use Low-Band and Mid-Band carrier aggregation for UEs connected
with NR-DC simultaneously with High-Band carrier aggregation.
The feature enhancement provides maximized MCG configuration based on the SCG configuration selected by the
Secondary Node. The maximized MCG configuration leads to higher aggregated peak rate and higher MCG peak rate
when only the MCG or both the MCG and SCG are used.

The following EBS counter values can increase in the Master Node:
71 sur 74 23/04/2024, 07:35

– pmEbsnMacPduVolDlUeSCell
– pmEbsnMacPduVolDlUePCell
The following PM counter values can increase in the Master Node:
The following PM counters are updated:
– NRCellCU.pmCaConfigDlSumSaDistr
– NRCellCU.pmCaConfigDlSamp
The following PM events might be triggered more frequently because of the increased number of Secondary Node
modifications and RRC Reconfigurations:
– CuCpProcMnNrdcModification
– CuCpProcSnNrdcModification
– CuCpXnSNodeReconfigurationComplete
– CuCpRrcReconfiguration
– CuCpRrcReconfigurationComplete
Operation
The NRCellCU.pmCaConfigDlSumNrdcDistr PM counter is introduced to monitor the number of UEs using the cell
as a PSCell with configured downlink SCells.
The following PM events are updated:
– DuPerUeRbTrafficRep
– DuPerUeRbTrafficRepAggr10
– DuPerUeRbTrafficRepAggr60
– DuPerUeTrafficRep
– DuPerUeTrafficRepAggr10
– DuPerUeTrafficRepAggr60
– CuCpPerNrCellCuCaConfiguredDl
I n te r fa c e s
This feature enhancement affects the following interfaces:
Xn-C The XnAP S-NODE ADDITION REQUEST ACKNOWLEDGE message is updated to contain the list of band
combinations and feature sets supporting the selected SCG configuration.
72 sur 74 23/04/2024, 07:35

When measurement gap configuration changes in the Master Node during the Secondary Node Addition or
Secondary Node initiated Secondary Node Change procedure, the Master Node might initiate a Secondary Node
Modification procedure to forward the changed measurement gap configuration to the Secondary Node.
When Low-Band or Mid-Band SCells are added or removed, the Master Node might initiate the Secondary Node
Modification procedure when the measurement gap configuration changes.
Uu RRC signaling might increase because of the following factors:
– The modification of the measurement gap configuration at SCell Addition and SCell Removal.
– When the measurement gap configuration changes in the Master Node during the Secondary Node
Addition or Secondary Node initiated Secondary Node Change procedure, the Master Node might initiate
an additional RRC Reconfiguration procedure to change the measurement gap in the UE.
H a rd wa re

ENM versions also.

Appendix A.l: 23.Q3: Dynamic QoS Modification in NR-DC
The feature enhancement allows the dynamic modification of the QoS properties of already established QoS flows
in Secondary Node terminated PDU sessions.

Access Type NR

The feature enhancement introduces the option to dynamically modify the 5QI and the ARP parameters of the QoS
profile of an already established QoS flow in a Secondary Node terminated PDU session. The modification is initiated
by the 5GC. The modification is validated in the Master Node and the Secondary Node, and it is signaled to the UE by
the Master Node.
The dynamic modification of already established QoS properties provides increased flexibility when changing the
characteristics of the service.

If the Master Node initiated Secondary Node Modification procedure fails, the UE is released. The UE release has the
following results on performance:
– The UE throughput degrades until the Secondary Node Addition procedure is triggered for the UE.
– The number of attempted and successful NR-DC setup might increase.

The PIs used for monitoring the Secondary Node Addition procedure as shown in Table 24 do not increase.
Table 24 Performance Indicators for Monitoring Secondary Node Addition
73 sur 74 23/04/2024, 07:35

P e rfo rman c e I n d ic ator Fo r m u l a

NR-DC Setup Success Rate Captured on Master 100 × NRCellCU.pmNrdcSetupUeMnSucc /
gNodeB (expressed in percentage) NRCellCU.pmNrdcSetupUeMnAtt
NR-DC Setup Success Rate Captured on Secondary 100 × NRCellCU.pmNrdcSetupUeSnSucc /
gNodeB (expressed in percentage) NRCellCU.pmNrdcSetupUeSnAtt
The NRCellCU.pmPduSessionModifySucc counter increases because the feature enhancement increases the
number of successful PDU Session Modification procedures.
Operation
Changing in the 5QI value can result in the change of the attributes defined in the following 5QI tables:
– CUCP5qi
– CUUP5qi
– DU5qi
The following attributes are not allowed to be modified in an established QoS flow:
– CUCP5qi.pdcpSnSize
– CUCP5qi.rlcMode
– DrbRlcUeCfg.rlcSNLength
If the 5QI or the ARP values are changed, the UE group that is assigned to the UE can also change. This can affect the
configuration of the UE group-adapted features.
I n te r fa c e s
The feature enhancement affects the following messages on the Xn-C interface:
– The XnAP S-NODE MODIFICATION REQUEST message on the Xn-C interface is updated with the PDU
Session Resource Modification Info – SN terminated IE.
– The XnAP S-NODE MODIFICATION REQUEST ACKNOWLEDGE message on the Xn-C interface is updated with
thePDU Session Resource Modification Response Info – SN terminated IE.
H a rd wa re

The 5GC must support the modification of QoS properties.
ENM version 23.3 or later is required for this feature enhancement.

Legal | © Ericsson AB 2021–2023
74 sur 74 23/04/2024, 07:35

NRDC Dual Connectivity

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NRDC Dual Connectivity

Uploaded by

Copyright:

Available Formats

NR-NR Dual Connectivity https://opomenmidf2.idf2.vend2.ran.mob.orange.net/elex?

Feature Description 113/221 04-LZA 701 6017/1 Uen EA25T

NR-NR Dual Connectivity

1 NR-NR Dual Connectivity Overview

Fe a t u r e N a m e NR-NR Dual Connectivity

Additional Info rmation

– RAN Parameter Recommendations Lists

– 3GPP TS 37.340; NR; Multi-connectivity; Overall description; Stage-2

– 3GPP TS 38.331; NR; Radio Resource Control (RRC); Protocol speciﬁcation

– 3GPP TS 38.413; NG-RAN; NG Application Protocol (NGAP)

– 3GPP TS 38.423; NG-RAN; Xn Application Protocol (XnAP)

1.1 NR-DC Deployment

1 sur 74 23/04/2024, 07:35

Figure 1 Interface Connections in NR-DC

The following cell groups can serve the NR-DC-capable UE:

Master Node Secondary Node

Master Node Secondary Node

Master Node Secondary Node

Master Node terminated user plane traffic

Secondary Node terminated user plane traffic

2 sur 74 23/04/2024, 07:35

Figure 2 Termination of QoS Flows within PDU Sessions

Master Node Secondary Node

Master Node Secondary Node

PDCP Xn-U PDCP

RLC RLC RLC

MAC and Layer 1 MAC and Layer 1

MCG radio resources SCG radio resources

User Plane (Master Node terminated)

User Plane (Secondary Node terminated)

Rela ted I nform at ion

2 Dependencies of NR-NR Dual Connectivity

Table 1 Feature Dependencies

Fe a t u r e Rela tio n sh ip Description

3 sur 74 23/04/2024, 07:35

Fe a t u r e Rela tio n sh ip Description

– At the Secondary Node initiated Secondary Node Change procedure

– If the measurement gap is changed in NR-DC by using the Master

4 sur 74 23/04/2024, 07:35

Fe a t u r e Rela tio n sh ip Description

5 sur 74 23/04/2024, 07:35

Fe a t u r e Rela tio n sh ip Description

6 sur 74 23/04/2024, 07:35

Fe a t u r e Rela tio n sh ip Description

– Secondary Node termination of QoS ﬂows

– Intra-Frequency Mobility Control in the Secondary Node

7 sur 74 23/04/2024, 07:35

Fe a t u r e Rela tio n sh ip Description

3 Feature Operation of NR-NR Dual Connectivity

– At Initial Context Setup

– At the PDU Session Resource Setup procedure

– At the PDU Session Resource Modify procedure

– At the PDU Session Resource Release procedure

– At an incoming handover to the Master Node

8 sur 74 23/04/2024, 07:35

Are A4 measurement criteria No A4 measurement

No Are criteria to start downlink

Downlink RLC buffer

Are A4 measurement criteria No A4 measurement

Figure 4 Operational Flow of Evaluating the NR-DC Setup Criteria

Rela ted I nform at ion

• The frequency of the measurement object is represented by an NRFrequency MO instance.

– At least one band of the PCell frequency.

9 sur 74 23/04/2024, 07:35