LTE-NR Dual Connectivity: Feature Description

LTE-NR Dual Connectivity
Feature Description
5/221 04-LZA 701 6017/1 Uen CZ12C

Copyright
© Ericsson AB 2018, 2019. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Contents
Contents
1 LTE-NR Dual Connectivity Overview 1
2 Dependencies of LTE-NR Dual Connectivity 2
3 Feature Operation of LTE-NR Dual Connectivity 4

3.1 EN-DC Deployment 4
3.2 Scenarios Triggering EN-DC Procedures in the Secondary Node 9
3.2.1 Secondary Node User Activity Supervision 9
3.2.2 Detection of Radio Link Failure by the Secondary Node 10
3.2.3 Timer for NR Random Access Expires 10
3.2.4 NR Cell is Locked 10
3.2.5 PDCP COUNT Threshold Is Reached 10
3.2.6 E1 Link Break 11
3.2.7 NR Mobility 11
3.3 EN-DC Bearer Type Transitions 11
3.4 EN-DC Configuration 13
3.4.1 Dynamic Power Sharing 13
3.4.2 Switching of Downlink MCG and SCG Resources 14
3.4.3 Switching of Uplink MCG and SCG Resources 15
3.4.4 EN-DC Band Combination Coordination 16
3.5 EN-DC Procedures 17
3.5.1 Secondary Node Addition 17
3.5.2 Master Node Initiated Secondary Node Modification 21
3.5.3 Uplink Resource Switching 23
3.5.4 Master Node Initiated Secondary Node Release 25
3.5.5 Secondary Node Initiated Secondary Node Release 28
3.5.6 Secondary Node Indicating User Activity 29
4 Network Impact of LTE-NR Dual Connectivity 31
5 Parameters for LTE-NR Dual Connectivity 33
6 Performance of LTE-NR Dual Connectivity 34
7 Activate Basic Feature 36
8 Engineering Guidelines for LTE-NR Dual Connectivity 37

8.1 Configure IP Connectivity for the X2-U Interface on the
Secondary Node in EN-DC 37
8.2 X2 Link Break 37
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

8.3 TCP Optimization for the Secondary Node Terminated DRBs in

EN-DC 38
8.4 Secondary RAT Data Usage Reporting 39
8.5 Configure Ciphering Algorithm Priority for Secondary Node
Terminated DRBs 40
8.6 Configure Radio Link Failure Parameters for the Secondary
Cell Group 40
8.7 Configure Threshold Value for Uplink Resource Switching 41
Appendix A: Feature Change History 43

Appendix A.a: 19.Q2: X2 IP Addressing for the gNodeB In EN-DC 43
Appendix A.b: 19.Q3: Downlink Packet Forwarding at Secondary Node
Addition Procedure for NR in EN-DC 44
Appendix A.c: 19.Q4: Switching of Uplink MCG and SCG Resources 46
Appendix A.d: 20.Q3: Increased EN-DC X2 Cardinality to 256 47
Appendix A.e: PDCP Flow Control 48
Appendix A.f: EN-DC-Triggered Handover at Incoming Handover 49
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

LTE-NR Dual Connectivity Overview
1 LTE-NR Dual Connectivity Overview
Access Type NR
Feature Identity: FAJ 121 4908
Value Package Name: NR High-Band Base Package
NR Low/Mid-Band Base Package
Value Package Identity: FAJ 801 4002/5H
FAJ 801 4002/5LM
Node Type: Baseband Radio Node
Licensing: Basic feature. No license is required.
Summary
The LTE-NR Dual Connectivity (FAJ 121 4908) feature introduces support for E-
UTRA – NR Dual Connectivity (EN-DC) in the gNodeB being the Secondary Node
in the EN-DC deployment.
EN-DC is realized as the combination of the following features and system

functions:
— Basic Intelligent Connectivity (FAJ 121 4843)
— LTE-NR Dual Connectivity (FAJ 121 4908)
— LTE carrier aggregation
— NR carrier aggregation
With the LTE-NR Dual Connectivity feature activated, SCG radio resources
provided by the Secondary Node (gNodeB) in the EN-DC deployment can be set
up for the EN-DC-capable UE in NR coverage.
The benefits of the EN-DC deployment are the following:

— Higher peak rate of network data traffic by aggregating LTE and NR carriers.
— Sustainable capacity and performance growth.
Additional Information
For more information on EN-DC deployment, see the following documentation:
— 3GPP TS 37.716 specifications "E-UTRA - NR Dual Connectivity of x bands"
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 1

2 Dependencies of LTE-NR Dual Connectivity
Table 1 Feature Dependencies
Feature Relationship Description

Basic Intelligent Connectivity (FAJ Prerequisite To achieve EN-DC functionality
121 4843) between the Master Node (eNodeB)
and the Secondary Node (gNodeB),
the Basic Intelligent Connectivity
feature must be activated on the
Master Node.
IEEE 1558 Time and Phase Prerequisite Both the Master Node and the
Synchronization (FAJ 121 2022) Secondary Node must be time and
phase synchronized either using
GNSS (GPS) or the IEEE 1588 Time
and Phase Synchronization feature.
In addition, both of the nodes have to
have the same frame start offset.
If EN-DC is deployed without the

time synchronization feature, EN-DC
setup is only guaranteed between
LTE cells and NR cells if either of the
following conditions is met:
— Both the LTE cells and the NR
cells are on the same Baseband
Radio Node.
— The LTE cells and the NR cells are

synchronized by the means of
Node Group Synchronization.
GTP-U Supervision (FAJ 121 2024) Conflicting There are not enough GTP-U
Supervision resources to run GTP-U
Supervision on a gNodeB in LTE-NR
Dual Connectivity while LTE
functionality is loaded.
LTE-NR Uplink Aggregation (FAJ 121 Related — When the SCG radio resource is
5091) released for a UE, the LTE-NR
Uplink Aggregation feature is
deactivated until the next
successful EN-DC Setup for the
same UE.
— The LTE-NR Uplink Aggregation

feature only changes the primary
path of the uplink switching.
2 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Dependencies of LTE-NR Dual Connectivity
Feature Relationship Description

High Speed UE High-Band (FAJ 121 Related To ensure that the UE is configured
5017) with the number of DMRS symbols
required for High Speed UE High-
Band to operate, a UE capability
check is performed.
Hardware Requirements
The LTE-NR Dual Connectivity feature is supported on all Baseband units
supporting NR.
Limitations
— Both the Master Node and the Secondary Node must be time and phase
synchronized either using GNSS (GPS) or the IEEE 1588 Time and Phase
Synchronization feature. In addition, both of the nodes have to have the
same frame start offset.
If EN-DC is deployed without the time synchronization feature, EN-DC setup

is only guaranteed between LTE cells and NR cells if either of the following
conditions is met:
— Both the LTE cells and the NR cells are on the same Baseband Radio
Node.
— The LTE cells and the NR cells are synchronized by the means of Node
Group Synchronization.
— Packet forwarding is not supported for Secondary Node terminated DRBs

during RRC connection re-establishment.
Network Requirements
— The LTE-NR Dual Connectivity feature requires the S1AP E-RAB Modification
Indication procedure to be supported in the EPC.
— The RLC mode for a specific QCI defined in the Master Node has to reflect the
corresponding setting in the Secondary Node. For the Secondary Node, the
RLC mode for a QCI is set using the CUCP5qi.rlcMode attribute for the
corresponding 5QI in the CUCP5qiTable MO instance. This MO instance must
have the CUCP5qiTable.default5qiTable attribute set to true if the
CUCP5qi.profile5qi attribute has a value configured that is equal to either
of the following attribute values set on the Master Node:
— QciProfileOperatorDefined.qci
— QciProfilePredefined.qci
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 3

3 Feature Operation of LTE-NR Dual

Connectivity
3.1 EN-DC Deployment

EN-DC, covering the fundamental interaction between a Master Node (eNodeB)
and a Secondary Node (gNodeB), is realized as the combination of the following
features and system functions:
— Basic Intelligent Connectivity (FAJ 121 4843)
— LTE-NR Dual Connectivity (FAJ 121 4908)
— LTE carrier aggregation
— NR carrier aggregation
The EN-DC-capable UE is always connected to the eNodeB, being the Master

Node in EN-DC. The UE can connect to the gNodeB, being the Secondary Node in
EN-DC, if the UE is within NR coverage. The UE is connected both to the eNodeB
and the gNodeB through the Uu interface.
The eNodeB connects to the EPC through the S1 interface. The S1-C interface is
used for control plane, while the S1-U interface is used for user plane.
The gNodeB connects to the EPC through the S1-U interface for user plane.
The eNodeB and the gNodeB are connected to each other through the X2
interface. The X2-C interface is used for control plane, while the X2-U interface is
used for user plane. One eNodeB can be connected to several gNodeBs and one
gNodeB can be connected to several eNodeBs.
4 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Feature Operation of LTE-NR Dual Connectivity
User Plane
Control Plane
EPC
S1
-U
-U
S1
C
S 1-
gNodeB
eNodeB
X2-C
X2-U
Uu ra g e
LTE Uu NR NR cove
LTE cove
rage
L0002002E
Figure 1 Connection for the EN-DC-Capable UE
The following cell groups can serve the EN-DC-capable UE:
Master Cell Group (MCG)

The MCG, provided by the eNodeB, can consist of a
Primary Cell (PCell) and zero or more Secondary Cells
(SCells).
Secondary Cell Group (SCG)

The SCG, provided by the gNodeB, can consist of a
Primary Secondary Cell (PSCell) and zero or more
Secondary Cells (SCells).
When the EN-DC-capable UE is connected to both the Master Node (eNodeB)

and the Secondary Node (gNodeB), it has the following MCG and SCG radio
resources for user plane traffic:
Master Node terminated MCG DRBs

Master Node terminated MCG DRBs are provided in the
MCG and use LTE PDCP resources. These DRBs transmit
user plane traffic between the UE and the eNodeB. Such
DRBs terminate the user plane through the S1-U interface
between the eNodeB and the EPC. Master Node
terminated MCG DRBs are ciphered and deciphered in the
Master Node.
Secondary Node terminated split DRBs

Secondary Node terminated split DRBs are provided in
the SCG and use NR PDCP resources. The split DRB can
use both MCG and SCG resources after Secondary Node
Addition. The use of the split DRB is determined based on
whether the UE is in NR coverage or not. These bearers
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 5

can transmit user plane traffic between the UE and the

eNodeB or between the UE and the gNodeB, depending
on the QCI configuration and NR link quality. Such DRBs
terminate the user plane through the S1-U interface
between the gNodeB and the EPC. Secondary Node
terminated split DRBs are ciphered and deciphered in the
Secondary Node.
Secondary Node terminated MCG DRBs

Secondary Node terminated MCG DRBs are provided in
the MCG after SCG Release that triggers DRB
reconfiguration. In this case, these DRBs use NR PDCP
resources and transmit user plane traffic between the UE
and the eNodeB through the gNodeB. These bearers are
also used when the SCG is available, but they are not
allowed to be split by configuration. Such DRBs terminate
the user plane through the S1-U interface between the
gNodeB and the EPC. Secondary Node terminated MCG
DRBs are ciphered and deciphered in the Secondary
Node.
6 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

EPC
EPC
Master Node Secondary Node Secondary Node

Terminated Terminated Terminated
MCG Bearer MCG Bearer Split Bearer
S1-C S1-U S1-U
LTE NR NR
PDCP PDCP PDCP
X2-C
eNodeB X2-U gNodeB

(Master (Secondary
Node) Node)
M
CG s
ra rce
di ou
o
re r es
so d io
ur ra
LT ce G Uu
EU s SC NR
u
UE
Control Plane
User Plane
L0002382C
Figure 2 MCG and SCG Radio Resources in EN-DC
The UE uses either of the following combinations of radio resources when

connected to both nodes in EN-DC:
— Master Node terminated MCG DRBs and Secondary Node terminated split
DRBs
Such a case applies when the UE is in NR coverage and can use both MCG
and SCG resources depending on the QCI configuration of the DRBs. Split is
allowed for DRBs by configuration.
— Master Node terminated MCG DRBs and Secondary Node terminated MCG
DRBs
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 7

Such a case applies when the UE is only served by the MCG because of an
SCG Release procedure. However, Secondary Node terminated MCG DRBs
are also used when DRBs are not allowed to be split by configuration.
In EN-DC, the UE is in RRC_CONNECTED mode in the eNodeB. The control of the

UE is managed through the LTE RRC signaling between the eNodeB and the UE.
Information specific to gNodeB resources is carried by containers conveying NR
RRC signaling over the X2-C and the LTE Uu interfaces.
The gNodeB resources, including a candidate NR cell, for the EN-DC-capable UE

are configured using the following procedures:
— Secondary Node Addition
— Secondary Cell Group Addition
The eNodeB selects a candidate NR cell using one of the following methods:
Configuration-based setup
One candidate NR cell is referenced by the primary LTE
cell serving the UE.
Measurement-based setup
The eNodeB orders the UE to perform an LTE inter-RAT
B1 measurement to find a suitable NR cell.
With the gNodeB resources available to the EN-DC-capable UE, DRBs can be
reconfigured to become Secondary Node terminated split DRBs. With the DRBs
reconfigured to be split, the user plane provided to the UE is configured in the
following ways:
— Downlink traffic is transmitted through the gNodeB using SCG resources

after a successful NR random access procedure. If the NR link quality falls
below a configured threshold, downlink traffic is redirected to use MCG
resources for the split DRB. Initial downlink transmission is done through
SCG. However, the further use of SCG, MCG, or the combination of the two is
determined by NR link quality and buffer age.
— Uplink traffic is transmitted either through the eNodeB using MCG resources
or the gNodeB using SCG resources. The initial uplink transmission is
configurable. However, the NR link quality determines the further use of MCG
or SCG resources for uplink traffic.
In both directions, the Secondary Node terminated split DRB uses NR PDCP
resources.
RELATED INFORMATION
3.3 EN-DC Bearer Type Transitions on page 11
3.4.2 Switching of Downlink MCG and SCG Resources on page 14
8 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

3.4.3 Switching of Uplink MCG and SCG Resources on page 15
3.5.1 Secondary Node Addition on page 17
3.5.2 Master Node Initiated Secondary Node Modification on page 21
3.5.4 Master Node Initiated Secondary Node Release on page 25
3.5.5 Secondary Node Initiated Secondary Node Release on page 28
8. Engineering Guidelines for LTE-NR Dual Connectivity on page 37
8.5 Configure Ciphering Algorithm Priority for Secondary Node Terminated

DRBs on page 40
3.2 Scenarios Triggering EN-DC Procedures in the

Secondary Node
3.2.1 Secondary Node User Activity Supervision

The Secondary Node is responsible for monitoring user plane activity on the
Secondary Node terminated DRBs serving each UE.
When no user plane data is sent to or received from the UE on any of the
Secondary Node terminated DRBs for a period of 5 s, the Secondary Node sends
an X2AP SGNB ACTIVITY NOTIFICATION to the Master Node. This message
indicates to the Master Node that the UE is inactive on Secondary Node
terminated DRBs.
If user plane data is sent to or received from the UE on any of the Secondary
Node terminated DRBs after the inactivity notification, the Secondary Node
sends a new X2AP SGNB ACTIVITY NOTIFICATION message to the Master Node.
This message indicates to the Master Node that the UE is reactivated.
RELATED INFORMATION
3.5.6 Secondary Node Indicating User Activity on page 29
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 9

3.2.2 Detection of Radio Link Failure by the Secondary Node

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.
RELATED INFORMATION
8.6 Configure Radio Link Failure Parameters for the Secondary Cell Group on
page 40
3.2.3 Timer for NR Random Access Expires

detects that the timer for a successful NR Random Access procedure is expired.
RELATED INFORMATION
3.2.4 NR Cell is Locked

The Secondary Node initiates the Secondary Node Release procedure when the
state of the serving NR cell changes in either of the following ways:
— The NRCellDU.administrativeState attribute is set to LOCKED by the
operator.
— The NRCellDU.operationalState attribute is set to DISABLED by an

underlying fault in the referenced sector carrier or by sector carrier lock.
RELATED INFORMATION
3.2.5 PDCP COUNT Threshold Is Reached

The Secondary Node initiates the Secondary Node Release procedure when the
uplink or downlink PDCP COUNT threshold is reached for at least one Secondary
Node terminated DRB (both split and MCG).
The purpose of the release is to avoid COUNT wrap-around.
10 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

RELATED INFORMATION
3.2.6 E1 Link Break

detects an E1 link break.
At E1 link break, the GNBCUUP Service Unavailable alarm is raised on the

Secondary Node.
RELATED INFORMATION
3.2.7 NR Mobility
NR Mobility can trigger EN-DC procedures. For information on what types of
mobility in NR result in triggering EN-DC procedures, see the following
documentation:
— Manage Mobility NR
— NR Mobility
— 5G Mobility and Traffic Management Guideline
3.3 EN-DC Bearer Type Transitions

Bearer type transitions in EN-DC are possible among the following DRB types:
— Master Node terminated MCG DRBs
— Secondary Node terminated split DRBs
— Secondary Node terminated MCG DRBs
The EN-DC-configured UE can be in one of the following states, depending on the

combination of the DRB types, as shown in Figure 3:
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 11

Table 2 EN-DC-Configured UE States with DRB Type Combination Used

EN-DC-Configured UE Combination of DRB Types
State
A This combination only contains Master Node
terminated MCG DRBs.
B This combination contains one or more Secondary
Node terminated split DRBs and zero or more
Master Node terminated MCG DRBs.
C This combination contains one or more Secondary
Node terminated MCG DRBs and zero or more
Master Node terminated MCG DRBs.
2
Secondary Node Addition
UE Connection Setup
A B
4
Secondary Cell Group
Addition
C
5
3
Master Node / Secondary Node
Initiated Secondary Node
Release
Release
L0002165F
Figure 3 Bearer Type Transition in EN-DC
1. UE Connection Setup
The EN-DC-capable UE is connected only by using Master Node terminated

MCG DRBs. Therefore, in the UE Connection Setup, user plane data is
transmitted through the Master Node only.
2. Secondary Node Addition
During the Secondary Node Addition procedure, one or more of the existing
Master Node terminated MCG DRBs are reconfigured to Secondary Node
terminated split DRBs.
3. SCG Release (Secondary Node Modification)
During SCG Release, all Secondary Node terminated split DRBs are
reconfigured to the Secondary Node terminated MCG DRBs. The SCG
12 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

resources for the UE are released, but the PDCP context is kept in the
Secondary Node.
4. SCG Addition (Secondary Node Modification)
During SCG Addition, all Secondary Node terminated MCG DRBs are
reconfigured to Secondary Node terminated Split DRBs.
5. Secondary Node Release
During the Secondary Node Release Procedure, all Secondary Node

terminated DRBs (split or MCG) are reconfigured to Master Node terminated
MCG DRBs. All SCG resources for the UE are released. PDCP resources for the
UE are relocated from the Secondary Node to the Master Node.
The UE can be released to RRC_IDLE mode from any of the EN-DC-configured UE

states.
RELATED INFORMATION
3.4 EN-DC Configuration
3.4.1 Dynamic Power Sharing

The uplink transmission power capability of the EN-DC-capable UE must be split
between the SCG radio resources and the MCG radio resources when the UE is
configured with at least one Secondary Node terminated split DRB. This is
required if the UE is using an EN-DC band combination with an NR band in Low-
Band or Mid-Band.
If the UE is capable of dynamic power sharing on the used EN-DC band

combination, the UE manages its transmission power capability by itself. In Low-
Band and Mid-Band, dynamic power sharing allows the UE to configure the
maximum uplink transmission power for both MCG and SCG radio resources in
steps of 1 dB.
If user data transmission for both MCG and SCG radio resources is scheduled at
the same time, transmission power is allocated in the following order:
1. Power is allocated first to the MCG radio resources.

2. The remaining power is allocated to the SCG radio resources.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 13

The allocation of uplink transmission power ensures that the total uplink power
configured separately for the MCG and SCG radio resources is not exceeded.
If the UE is not capable of dynamic power sharing, the network needs to

configure the UE with a maximum uplink transmission power semi-statically for
both the SCG and the MCG radio resources.
The Secondary Node receives the maximum uplink transmission power for the
SCG resources over the X2 interface.
For more information on dynamic power sharing and UE power classes, see the
following documentation:
— 3GPP TS 38.101, NR; User Equipment (UE) Radio Transmission and
Reception; Release 15
— 3GPP TS 38.331, NR; Radio Resource Control (RRC); Release 15
3.4.2 Switching of Downlink MCG and SCG Resources

The switching of downlink MCG and SCG resources allows downlink data
transmission to conform to the estimated radio quality of the NR link. The
switching depends on the following conditions:
— When the estimated radio quality of the NR link is good, the downlink data
transmission uses the SCG radio resources.
— When the estimated radio quality of the NR link is poor, the downlink data
transmission uses the MCG radio resources.
Note: The UE does not require reconfiguring for downlink switching.
The switching of downlink MCG and SCG resources can be adopted to rapidly
changing radio conditions because it does not involve the reconfiguration of the
UE. The radio quality of the NR link is defined by the configured threshold value
of NRCellDU.endcDlNrLowQualThresh. The gNodeB switches to the MCG radio
resources of the split bearer if there are two consecutive CQI measurements
below the threshold, or four consecutive CQI measurements are missing. Unsent
packets and upcoming packets are then transmitted over the MCG radio
resources.
The NRCellDU.endcDlNrQualHyst parameter defines the hysteresis for

switching back to the SCG resources. If the radio quality of the NR link exceeds
the threshold, and the hysteresis value, the traffic is directed back to the SCG
resources again.
The frequency of switching occasions between the MCG and SCG radio resources
can be limited by a prohibit timer. The timer is configured with the
GNBCUUPFunction.endcDlNrRetProhibTimer attribute.
14 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

3.4.3 Switching of Uplink MCG and SCG Resources

The switching of uplink Master Cell Group (MCG) and Secondary Cell Group
(SCG) resources allows uplink data transmission to conform to the estimated
radio quality of the NR link in the following way:
— When the estimated radio quality of the NR link is good, the uplink data
transmission uses the SCG radio resources.
— When the estimated radio quality of the NR link is poor, the uplink data
transmission uses the MCG radio resources.
The switching of MCG and SCG resources in UL is slower than it is in DL because

it involves the reconfiguration of the UE. The radio quality of the NR link is
defined by the configured threshold value of
NRCellDU.endcUlNrLowQualThresh.
If the NR radio quality drops below the configured threshold value, the gNodeB
switches to the MCG radio resources of the split bearer.
In Low-Band and Mid-Band, if the UE quickly moves out of the NR cell coverage,
the detection of CRC failures and discontinuous transmissions in uplink causes
the gNodeB to switch to the MCG radio resources regardless of the estimated
radio quality of the NR link.
The NRCellDU.endcUlNrQualHyst parameter defines the hysteresis for

switching back to the SCG radio resources. If the radio quality of the NR link
reaches the threshold, as well as the hysteresis value, the traffic is directed back
to the SCG radio resources again.
The maximum value of the uplink SINR is estimated at every PUSCH reception. A
filter smooths the uplink SINR samples. The smoothing is needed to normalize
the reaction time to temporary changes of the SINR. The maximum uplink-
normalized SINR value is checked against the value of the
NRCellDU.endcUlNrLowQualThresh attribute.
The shortest possible period of successfully switching between MCG and SCG
radio resources can be configured in the
GNBCUUPFunction.endcUlNrRetProhibTimer parameter, that serves as a
prohibit timer.
In High-Band, it is possible to switch to the DFTS-OFDM waveform and to a

single uplink TX port while transmitting SCG radio resources. In this way, uplink
TX port switching provides a suitable buffer before switching to the transmission
of MCG radio resources.
The quality of MCG radio resources is not evaluated before the uplink switching
of radio resources. The good quality of MCG radio resources must be ensured by
the mobility procedures the Master Node terminated MCG DRBs determine.
Different uplink channel quality conditions employ different uplink switching
mechanisms if both layer switching and radio resource switching are enabled.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 15

RELATED INFORMATION
3.5.3 Uplink Resource Switching on page 23
8.7 Configure Threshold Value for Uplink Resource Switching on page 41
3.4.4 EN-DC Band Combination Coordination

The EN-DC band combination coordination function is used to set up carrier
aggregation within the MCG and the SCG. The band combination coordination is
triggered to add the SCG during the following EN-DC procedures:
— Secondary Node Addition
— Secondary Node Modification
EN-DC Band Combination Selection in the Master Node
1. The Master Node (eNodeB) performs LTE SCell evaluation to maximize LTE
throughput based on the following criteria:
• LTE carrier aggregation-related features
• The eNodeB configuration
• Optimized EN-DC band combination coordination with best selected

SCell
Note: In the phase of the SCell evaluation (after the UE capability check),
the eNodeB checks if the NR PSCell frequency (considered in the
EN-DC band combination coordination) is not a frequency of an LTE
SCell candidate for the UE. If it turns out that there is a frequency
match, the eNodeB does not consider the given LTE SCell as part of
the EN-DC band combination.
2. The Master Node prepares a list of EN-DC band combinations matching the
selected LTE carrier aggregation part and the target NR PSCell band.
3. The Master Node signals the list of allowed EN-DC band combinations to the
Secondary Node.
If SCG is removed or Secondary Node is released, existing EUTRA Capability E-

UTRA Carrier Aggregation band combination algorithm is used.
EN-DC Band Combination Selection in the Secondary Node
1. The Secondary Node (gNodeB) selects the band combination that is

appropriate to the network configuration based on the following information
it receives:
16 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

— The UE capability information of the EN-DC-capable UE.
— The list of allowed band combinations signaled by the Master Node.
2. After selecting a band combination providing the maximum NR throughput,

the Secondary Node signals it back to the Master Node to complete the UE
configuration.
RELATED INFORMATION
3.5 EN-DC Procedures
3.5.1 Secondary Node Addition

The Secondary Node Addition procedure is used to establish a UE context at the
Secondary Node which, this way, provides SCG radio resources to the EN-DC-
capable UE.
Downlink packet forwarding is supported in EN-DC during the Secondary Node

Addition procedure. It is always enabled and not controlled by MO configuration.
Downlink packets are forwarded from the Master Node to the Secondary Node
using the X2-U interface.
During the Secondary Node Addition procedure, the EN-DC band combination is
chosen in the Secondary Node in coordination with the allowed EN-DC band
combinations signaled by the Master Node. The EN-DC-capable UE is configured
with the MCG and SCG information (LTE and NR carriers) according to the chosen
EN-DC band combination.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 17

Master Secondary
UE Node Node MME
1. Secondary Node Addition Preparation

X2AP:
SGNB ADDITION REQUEST
EN-DC band combination coordination
X2AP:
SGNB ADDITION REQUEST ACKNOWLEDGE
X2AP:
SN STATUS TRANSFER
2. RRC Connection Reconfiguration

RRC:
RRCConnectionReconfiguration
LTE Random Access
RRC:
RRCConnectionReconfigurationComplete
3. X2AP:
SGNB RECONFIGURATION COMPLETE
4. Path Update
S1AP:
E-RAB MODIFICATION INDICATION
S1AP:
E-RAB MODIFICATION CONFIRM
5. NR Random Access
L0002150D
Figure 4 Secondary Node Addition Procedure
1. Secondary Node Addition Preparation
a. Following the configuration-based or the B1 measurement-based

triggering of the Secondary Node Addition procedure, the Master Node
sends an SGNB ADDITION REQUEST message to the Secondary Node
through the X2-C interface.
The message contains the EN-DC band combinations and an NR target

cell the Master Node selected.
b. If the Secondary Node sends the SGNB ADDITION REQUEST
ACKNOWLEDGE message to the Master Node, new allocated SCG radio
resources exist on the Secondary Node, as well as MCG radio resources
on the Master Node, for the UE.
The Secondary Node chooses one of the band combinations provided by

the Master Node, and selects one PSCell, and possibly also NR SCells.
The Secondary Node then sends the selected band combination back in
18 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

the SGNB ADDITION REQUEST ACKNOWLEDGE message. The EN-DC

configuration is finalized in the Master Node based on the selected band
combination.
c. The Master Node sends the SN STATUS TRANSFER message to the
Secondary Node.
The SN STATUS TRANSFER message contains the PDCP status

information (uplink and downlink COUNT values) for RLC AM bearers to
be reconfigured from Master Node terminated to Secondary Node
terminated DRBs.
d. Separate LTE carrier aggregation thresholds are used for the split DRBs
to control the activation and deactivation of LTE SCells. The following
attributes are used to set the carrier aggregation thresholds on the
Master Node:
— CarrierAggregationFunction.dcSCellActDeactDataThres
— CarrierAggregationFunction.dcSCellActDeactDataThresHyst
— CarrierAggregationFunction.dcSCellDeactDelayTimer
a. The Master Node initiates the RRCConnectionReconfiguration

message to the UE. The message includes the NR RRC configuration
message the Master Node received from the Secondary Node.
b. The UE applies the new configuration. LTE Random Access procedure
between the UE and the Master Node is performed.
c. The UE sends the RRCConnectionReconfigurationComplete message
to the Master Node. All the LTE SCells are activated once the RRC
reconfiguration of the UE is completed to receive the data.
3. The Master Node sends the SGNB RECONFIGURATION COMPLETE message to
indicate to the Secondary Node that the UE is reconfigured successfully. The
time to wait for the SGNB RECONFIGURATION COMPLETE message is
configured in the GNBCUCPFunction.tDcOverall attribute on the Secondary
Node.
Note: It is recommended that the value of the

GNBCUCPFunction.tDcOverall timer in the Secondary Node be
greater than the value of the
Rrc.tRrcConnectionReconfiguration timer in the Master Node.
4. Path Update
a. The Master Node starts updating the user plane path for the Secondary
Node terminated split DRBs by sending the E-RAB MODIFICATION
INDICATION message to the MME.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 19

b. The MME confirms the user plane path update by sending the E-RAB
MODIFICATION INDICATION message to the Master Node.
5. NR Random Access procedure between the UE and the Secondary Node is

performed.
RELATED INFORMATION
3.4.4 EN-DC Band Combination Coordination on page 16
3.5.1.1 Packet Forwarding at Secondary Node Addition

During the Secondary Node Addition procedure, bearer resources allowed to be

Secondary Node terminated Split DRBs are moved from the Master Node to the
Secondary Node.
Downlink packets are sent from the SGW to old bearer resources in the Master
Node. During the Secondary Node Addition procedure, a packet forwarding
tunnel between the two nodes is established over the X2-U interface.
Packet forwarding behavior between the old and the new bearer resources varies
based on the following conditions:
— In both RLC AM and UM, downlink packets that are not yet sent to the UE by
the old bearer resources in the Master Node are forwarded to the newly set
up Split DRBs. The Split DRBs in the Secondary Node send these packets to
the UE.
— In RLC AM, downlink packets from the Master Node that are sent to, but not
acknowledged by the UE, are forwarded to the Secondary Node terminated
Split DRB where they are dropped.
Packet forwarding between old and newly set up bearer resources ensures that
packet loss is minimized during the Secondary Node Addition procedure.
Packet forwarding ends when the path switch is completed and the SGW starts
sending packets to the new bearer resources in the Secondary Node.
20 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

SGW
S1-U S1-U
Master Node Packet Forwarding Tunnel Secondary Node
X2-U
EN-DC
UE
Packet flow before Secondary Node Addition
Packet forwarding during Secondary Node Addition
Packet flow following Secondary Node Addition
Secondary Node terminated Split bearer after Secondary Node Addition
Master Node terminated MCG bearer before Secondary Node Addition
L0002327B
Figure 5 Downlink Session Packet Flow in EN-DC during Secondary Node

Addition Procedure
3.5.2 Master Node Initiated Secondary Node Modification

The Master Node Initiated Secondary Node Modification procedure is initiated by
the Master Node and has one of the following purposes:
SCG Removal To remove the SCG resources and reconfigure the

Secondary Node terminated split DRB(s) to Secondary
Node terminated MCG DRB(s), while keeping NR PDCP
resources in the Secondary Node.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 21

SCG Addition To set the SCG resources up and reconfigure the

Secondary Node terminated MCG DRB(s) to Secondary
Node terminated split DRB(s).
E-RAB Release To release SCG resources (if established Secondary Node

terminated split DRBs exist) and PDCP resources for
Secondary Node terminated DRBs (both split and MCG).
One or more E-RABs can be released in the same
procedure.
E-RAB Setup To set up SCG resources (if established Secondary Node

terminated split DRBs exist) and PDCP resources for
Secondary Node terminated DRBs (both split and MCG).
One or more E-RABs can be set up in the same procedure.
The EN-DC band combination coordination function is triggered during the SCG
Addition procedure to select the EN-DC band combination.
Master Secondary
UE Node Node MME
1. Secondary Node Modification Preparation

X2AP:
SGNB MODIFICATION REQUEST
X2AP:
SGNB MODIFICATION REQUEST ACKNOWLEDGE

RRC:
LTE Random Access
RRC:
3. X2AP:
SGNB RECONFIGURATION COMPLETE
4. NR Random Access
L0002308C
Figure 6 Master Node Initiated Secondary Node Modification
1. Secondary Node Modification Preparation
a. The Master Node triggers the modification procedure by sending the

SGNB MODIFICATION REQUEST message to the Secondary Node.
22 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

b. The Secondary Node confirms the procedure by sending the SGNB

MODIFICATION REQUEST ACKNOWLEDGE message back.
a. The Master Node initiates RRC connection reconfiguration towards the

UE by sending the RRCConnectionReconfiguration message,
including the NR RRC reconfiguration message received from the
Secondary Node, to it.
b. The LTE Random Access procedure between the UE and the Master
Node is only performed at either an SCG Addition or an SCG Removal
procedure.
c. The UE applies the new configuration and replies to Master Node in the
RRCConnectionReconfigurationComplete message, including the NR
RRC response message.
3. The Master Node sends the SGNB RECONFIGURATION COMPLETE message to

the Secondary Node indicating that the reconfiguration procedure by the UE
is completed.
4. The NR Random Access procedure between the UE and the Secondary Node
is only performed at SCG Addition.
RELATED INFORMATION
3.4.4 EN-DC Band Combination Coordination on page 16
3.5.3 Uplink Resource Switching

The switching of the uplink MCG and SCG resources in the EN-DC-capable UE is
performed through X2AP signaling between the Master Node and the Secondary
Node, and RRC signaling between the UE and the Master Node. The procedure is
the same to switch from MCG to SCG as the one to switch from SCG to MCG in
uplink.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 23

UE Master Secondary
Node Node
1. Secondary Node Modification Request
X2AP:
SGNB MODIFICATION REQUIRED
RRC:
RRC:
3.
X2AP:
SGNB MODIFICATION CONFIRM
L0002502A
Figure 7 Uplink MCG and SCG Resource Switching
1. Secondary Node Modification Required
The Secondary Node sends the SGNB MODIFICATION REQUIRED message to

the Master Node requesting the reconfiguration of the UE. The request
contains the NR RRC information indicating if the uplink resource switch is
from MCG to SCG, or from SCG to MCG.
a. The Master Node initiates the RRC connection reconfiguration to the UE

by sending the RRCConnectionReconfiguration message containing
the NR RRC information received from the Secondary Node.
b. The UE applies the new configuration and replies to the Master Node in
the RRCConnectionReconfigurationComplete message containing the
NR RRC response to be relayed to the Secondary Node.
3. The Master Node sends the SGNB MODIFICATION CONFIRM message to the
Secondary Node to indicate that the reconfiguration of the UE is completed.
This message contains the NR RRC response from the UE.
24 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

3.5.4 Master Node Initiated Secondary Node Release

The Master Node Initiated Secondary Node Release procedure is initiated by the
Master Node. It is used to trigger the release of the UE context at the Secondary
Node.

Release procedure. It is always enabled and not controlled by MO configuration.
Downlink packets are forwarded from the Secondary Node to the Master Node
During the Secondary Node Release procedure, all the LTE SCells are configured
simultaneously and activated based on LTE carrier aggregation buffer thresholds.
Master Secondary
UE Node Node MME

X2AP:
SGNB RELEASE REQUEST
X2AP:
SGNB RELEASE REQUEST ACKNOWLEDGE
X2AP:
SN STATUS TRANSFER
RRC:
LTE Random Access
RRC:
3. Path Update
S1AP:
S1AP:
4. X2AP:
UE CONTEXT RELEASE
L0002156D
Figure 8 Master Node Initiated Secondary Node Release
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 25

a. The Master Node triggers the release of the SCG resources for a specific
UE by sending the SGNB RELEASE REQUEST message to the Secondary
Node.
b. The Secondary Node confirms the procedure by sending the SGNB
RELEASE REQUEST ACKNOWLEDGE message back.
c. The Secondary Node sends a SN STATUS TRANSFER message containing

PDCP status information (uplink and downlink COUNT values) for
Secondary Node terminated DRBs in RLC AM to the Master Node.
a. The Master Node initiates reconfiguration of the RRC connection to the

UE in RRC_CONNECTED mode. The reconfiguration is triggered by the
RRCConnectionReconfiguration message.
Node is performed.
c. The UE, applying the new configuration, sends the
RRCConnectionReconfigurationComplete message back to the
Master Node.
3. Path Update (if the UE is in RRC_CONNECTED mode)
a. The Master Node starts updating the user plane path for the Master
Node terminated MCG DRBs by sending the E-RAB MODIFICATION
MODIFICATION CONFIRMATION message to the Master Node.
4. The Master Node triggers the procedure to release the UE context at the
Secondary Node by sending the UE CONTEXT RELEASE message.
3.5.4.1 Packet Forwarding at Secondary Node Release
During the Secondary Node Release procedure, bearer resources allowed to be

Secondary Node terminated Split DRBs are moved from the Secondary Node to
the Master Node.
Downlink packets are sent from the SGW to the Secondary Node. If the bearer
resources in the Secondary Node are released, packet forwarding is performed
from the Secondary Node to the Master Node. A packet forwarding tunnel
between the two nodes is established over the X2-U interface.
Packet forwarding behavior between the bearer resources varies based on the
following conditions:
— In RLC UM, downlink packets that are not yet sent to the UE by the bearer
resources in the Secondary Node are forwarded to the Master Node.
26 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

— In RLC AM, downlink packets from the Secondary Node that are sent to, but
not acknowledged by the UE, are forwarded to the Master Node terminated
Split DRB where they are dropped.
Packet forwarding between the bearer resources ensures that packet loss is
minimized during the Secondary Node Release procedure.
Packet forwarding ends when the SGW sends an end marker to the Secondary
Node. The Secondary Node Release procedure is completed.
SGW
S1-U S1-U
Master Node Packet Forwarding Tunnel Secondary Node
X2-U
EN-DC
UE
Packet flow before Secondary Node Release
Packet flow after Secondary Node Release
Packet forwarding during Secondary Node Release
Secondary Node terminated Split bearer before Secondary Node Release
Master Node terminated MCG bearer after Secondary Node Release
L0002433A
Figure 9 Downlink Session Packet Flow in EN-DC during Secondary Node

Release Procedure
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 27

3.5.5 Secondary Node Initiated Secondary Node Release

The Secondary Node Initiated Secondary Node Release procedure is initiated by
the Secondary Node. It is used to trigger the release of the UE context at the
Secondary Node.
During the Secondary Node Release procedure, all the LTE SCells are configured
simultaneously and activated based on LTE carrier aggregation buffer thresholds.
Master Secondary
UE Node Node MME

X2AP:
SGNB RELEASE REQUIRED
X2AP:
SGNB RELEASE CONFIRM
X2AP:
SN STATUS TRANSFER
RRC:
LTE Random Access
RRC:
3. Path Update
S1AP:
S1AP:
4. X2AP:
UE CONTEXT RELEASE
L0002207C
Figure 10 Secondary Node Initiated Secondary Node Release
a. The Secondary Node triggers the release of the SCG resources for a
specific UE by sending the SGNB RELEASE REQUIRED message to the
Master Node.
b. The Master Node confirms the procedure by sending the SGNB RELEASE
CONFIRM message back.
28 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

c. The Secondary Node sends a SN STATUS TRANSFER message containing

PDCP status information (uplink and downlink COUNT values) for
Secondary Node terminated DRBs in RLC AM to the Master Node.
a. The Master Node initiates reconfiguration of the RRC connection to the

UE in RRC_CONNECTED mode. The reconfiguration is triggered by the
RRCConnectionReconfiguration message.
Node is performed.
c. The UE, applying the new configuration, sends the
RRCConnectionReconfigurationComplete message back to the
Master Node.
3. Path Update (if the UE is in RRC_CONNECTED mode)
a. The Master Node starts updating the user plane path for the Master
Node terminated MCG DRBs by sending the E-RAB MODIFICATION
MODIFICATION CONFIRMATION message to the Master Node.
4. The Master Node triggers the procedure to release the UE context at the
Secondary Node by sending the UE CONTEXT RELEASE message.
3.5.6 Secondary Node Indicating User Activity

The Secondary Node reports to the Master Node if the UE becomes inactive or
reactivated. Reporting is done on a UE level for all Secondary Node terminated
DRBs combined.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 29

Master Secondary
Node Node
User Activity Supervision
UE user plane inactivity

on Secondary Node
terminated DRBs for 5s
X2AP SGNB ACTIVITY NOTIFICATION
L0002778A
Figure 11 Reporting User Activity
1. The Secondary Node sends an X2AP SGNB ACTIVITY NOTIFICATION to the

Master Node in the following cases:
— When no user plane data is sent to or received from the UE on any of the
Secondary Node terminated DRBs for a period of 5 s.
— When user plane data is sent to or received from the UE on any of the
Secondary Node terminated DRBs after the inactivity notification.
The X2AP SGNB ACTIVITY NOTIFICATION message indicates to the Master

Node that the UE is inactive or reactivated considering Secondary Node
terminated DRBs.
RELATED INFORMATION
3.2.1 Secondary Node User Activity Supervision on page 9
30 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Network Impact of LTE-NR Dual Connectivity
4 Network Impact of LTE-NR Dual

Connectivity
Capacity and Performance

Throughput is expected to increase by using Secondary Node terminated DRBs.
Interfaces
X2-C For the X2-C interface, the following messages are used:
— SGNB ADDITION REQUEST
— SGNB ADDITION REQUEST ACKNOWLEDGE
— SGNB ADDITION REQUEST REJECT
— SGNB MODIFICATION REQUIRED
— SGNB MODIFICATION CONFIRM
— SGNB MODIFICATION REFUSE
— SGNB MODIFICATION REQUEST
— SGNB MODIFICATION REQUEST ACKNOWLEDGE
— SGNB MODIFICATION REQUEST REJECT
— SGNB RECONFIGURATION COMPLETE
— SGNB RELEASE REQUEST
— SGNB RELEASE REQUEST ACKNOWLEDGE
— SGNB RELEASE REQUIRED
— SGNB RELEASE CONFIRM
S1-C For the S1-C interface, the following messages are used:
— E-RAB MODIFICATION INDICATION
— E-RAB MODIFICATION CONFIRM
F1 The following F1AP messages are used:

— UE CONTEXT MODIFICATINO REQUEST
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 31

— UE CONTEXT MODIFICATINO RESPONSE
E1 The following E1AP messages are used:

— BEARER CONTEXT MODIFICATION REQUEST
— BEARER CONTEXT MODIFICATION RESPONSE
32 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Parameters for LTE-NR Dual Connectivity
5 Parameters for LTE-NR Dual Connectivity
Table 3 Parameters for the Secondary Node

Parameter Type Description
QciProfileEndcConfigExt.tReorderingU Introduced See MOM description.
lPdcp
QciProfileEndcConfigExt.tReorderingU Introduced See MOM description.

lDiscardPdcp
QciProfileEndcConfigExt.tReorderingD Introduced See MOM description.

lPdcp
QciProfileEndcConfigExt.initialUplin Introduced See MOM description.

kConf
QciProfileEndcConfigExt.rlcModeQciUM Introduced See MOM description.
SecurityHandling.cipheringAlgoPrio Introduced See MOM description.
GNBCUCPFunction.tDcOverall Introduced See MOM description.
LocalIpEndpoint.addressRef Introduced See MOM description.
GNBCUUPFunction.endcDlNrRetProhibTim Introduced See MOM description.

er
NRCellDU.endcDlNrLowQualThresh Introduced See MOM description.
NRCellDU.endcDlNrQualHyst Introduced See MOM description.
NRCellDU.endcUlNrLowQualThresh Introduced See MOM description.
NRCellDU.endcUlNrQualHyst Introduced See MOM description.
GNBCUUPFunction.endcUlNrRetProhibTim Introduced See MOM description.

er
NRCellDU.endcUlLegSwitchEnabled Introduced See MOM description.
NRCellCU.mcpcEnabled Introduced See MOM description.
NRCellCU.mcpcPSCellProfileRef Introduced See MOM description.
McpcPSCellProfile.rsrpCriticalEnable Introduced See MOM description.

d
McpcPSCellProfile.rsrpCritical Introduced See MOM description.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 33

6 Performance of LTE-NR Dual Connectivity
KPIs
This feature has no associated KPIs.
Counters
— PpControlLink.pmEndcNrDrbSetupAtt
— PpControlLink.pmEndcNrDrbSetupSucc
— X2UTermination.pmPdcpPktFwdRecDlDiscQos
— X2UTermination.pmPdcpPktFwdRecDlQos
— X2ULink.pmPdcpPktFwdTransDlDiscQos
— X2ULink.pmPdcpPktFwdTransDlQos
— NRCellCU.pmEndcSetupScgUeAtt
— NRCellCU.pmEndcSetupScgUeSucc
— NRCellCU.pmEndcSetupUeAtt
— NRCellCU.pmEndcSetupUeSucc
— NRCellCU.pmEndcRelUeNormal
— NRCellCU.pmEndcRelUeAbnormalMenb
— NRCellCU.pmEndcRelUeAbnormalSgnb
— NRCellCU.pmEndcRelUeAbnormalMenbAct
— NRCellCU.pmEndcRelUeAbnormalSgnbAct
— GNBCUUPFunction.pmProhibitTimerRefuseUlLegSwitch
Events
— CuCpProcEndcSetup
— CuCpProcX2MnInitiatedSgnbModification
— CuCpX2RrcTransfer
34 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Performance of LTE-NR Dual Connectivity
— CuCpX2SecondaryRatDataUsageReport
— CuCpX2SgnbActivityNotification
— CuCpX2SgnbModificationRequest
— CuCpX2SgnbModificationRequestAcknowledge
— CuCpX2SgnbModificationRequestReject
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 35

7 Activate Basic Feature
This is a basic feature. It does not require manual activation and cannot be
deactivated.
While optional features need to be activated, basic features are activated

automatically during node integration. They also do not have a software license
key associated, which means that they have no entries in the LKF that is installed
on the node.
It is possible that some functions of basic features need to be enabled or

configured manually.
36 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Engineering Guidelines for LTE-NR Dual Connectivity
8 Engineering Guidelines for LTE-NR Dual

Connectivity
8.1 Configure IP Connectivity for the X2-U Interface on the

Secondary Node in EN-DC
In EN-DC, the user plane connection between the Master Node (eNodeB) and the
Secondary Node (gNodeB) is established over the X2-U interface.
It is recommended to use optical 10G connection for all routers between the
nodes in EN-DC, if the LTE air interface capacity is above 600Mbps across all cells
in the eNodeB.
Prerequisites
A LocalIpEndpoint MO that is suitable to refer to X2 must exist on the gNodeB.
If it doesn't exist, create an instance of it.
Steps
1. Add X2 to the LocalIpEndpoint.interfaceList list.
Results
The IP address for EN-DC connectivity over the X2-U interface is configured on
the gNodeB.
For more information on direct X2 IPsec configuration for the gNodeB in EN-DC,
see Manage IPsec.
After This Task

The gNodeB needs to be restarted, so that the configured IP address for the X2-U
interface can be applied. After node restart, the
TermPointToENodeB.administrativeState attribute, as well as the
termination point on the eNodeB, must be UNLOCKED to initiate the X2 Setup
procedure.
For more information about X2 Setup procedure, see X2 Configuration.
8.2 X2 Link Break

X2 link break in EN-DC occurs when the connection over the X2 interface is lost
between the Master Node (eNodeB) and the Secondary Node (gNodeB).
An X2 link break is typically caused by the following:
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 37

— The TermPointToENodeB MO on the Secondary Node to the Master Node is

locked
— The termination point on the Master Node to the Secondary Node is locked
— Transport failure
— The Master Node restarts or is not operational
An X2 link break in EN-DC is detected both in the Master Node and the
Secondary Node independently. The Secondary Node can lose connection to all
Master Nodes over the X2 interface in EN-DC. In such cases, the LTE Anchor
Service Unavailable alarm is raised on the Secondary Node.
The Secondary Node releases all the resources associated with the affected X2
link.
It is recommended to use optical 10G connection for all routers between the
gNodeB and eNodeB in EN-DC, if the LTE air interface capacity is above 600
Mbps across all cells in the eNodeB.
8.3 TCP Optimization for the Secondary Node Terminated

DRBs in EN-DC
TCP optimization is available for the Secondary Node terminated DRBs (split and
MCG) in EN-DC. With it, reduced queuing delay is provided in the user plane
traffic with the purpose of improved end user performance.
For TCP optimization of the Secondary Node terminated DRBs, the Active Queue
Management (AQM) is used in the PDCP buffer in the gNodeB.
The AQM mode 1 configuration is set to activate AQM in the gNodeB buffer, and
it applies to non-GBR DRBs. The following parameters apply to the age of data
packets in AQM mode 1 in the gNodeB:
— The buffer age for a single data packet, discarded with the purpose of
reducing buffer queuing, is set to 100 ms.
— The buffer age for discarding all older data packets is set to 500 ms.
AQM mode 1 is only applied to downlink user data traffic in EN-DC.
Note: The TCP Optimization (FAJ 121 1713) LTE feature is licensed for the
eNodeB. However, it is provided to the Secondary Node terminated
DRBs without a license check in EN-DC. At the Secondary Node Release
procedure, when the all the Secondary Node terminated DRBs are
reconfigured to be Master Node terminated MCG DRBs, TCP
optimization is dependent on if the feature is activated on the eNodeB.
For buffer dimensioning, the Stanford model is recommended. The buffer

recommendation is applicable to a transport node external to the baseband unit
if that node can become a congestion point.
38 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Equation 1 Stanford Model
C Interface speed of congested interface
R Round-Trip Time
N number of TCP/IP flows
Example 1 Buffering in C=1 Gbps Use Case

C= 1 Gbps, R= 50 ms, N = 2 flows
Buffer = 1 Gbps * 50 ms / SQRT(2) = 35 Mbits = 4.5 MB
8.4 Secondary RAT Data Usage Reporting

The secondary RAT data usage reporting functionality provides UE-level
observability information in EN-DC. This information is available in the EPC
about the data volume transmitted by the SCG radio resources of a Secondary
Node terminated split DRB.
UE-level data volume information is gained from the Secondary Node through
dedicated signaling over the following interfaces:
— The X2 interface between the Master Node (eNodeB) and the Secondary
Node (gNodeB).
— The S1 interface between both the Master and Secondary Nodes and the
MME.
Data usage reports are generated at the following EN-DC procedures:

— SCG Release (Master Node Initiated Secondary Node Modification)
— Secondary Node Release (both Master Node and Secondary Node initiated)
The signaling and report formats are standardized by 3GPP. The reports contain
the following information:
— The time period covered by the report.
— The uplink data volume information for a set of Secondary Node terminated
split DRBs.
— The downlink data volume information for a set of Secondary Node

terminated split DRBs.
The secondary RAT data usage reporting functionality is activated on the

Secondary Node by setting the
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 39

GNBCUUPFunction.endcDataUsageReportEnabled attribute to true. If the

secondary RAT data usage reporting is activated on the Master Node, the
Secondary Node signals the data usage report to the EPC.
Table 4 Node Behavior at Secondary RAT Data Usage Reporting Activation

Attribute Value on Node Behavior Description
GNBCUUPFunction.endc The Secondary Node counts transferred data
DataUsageReportEnabl volume on the SCG radio resources of Secondary
ed is set to true. Node terminated split DRBs for the UE. Collected
data is sent to the Master Node through the X2
interface as a secondary RAT data usage report.
GNBCUUPFunction.endc The Secondary Node does not count transferred
DataUsageReportEnabl data volume and does not send any secondary RAT
ed is set to false. data usage reports to the Master Node through the
X2 interface.
RELATED INFORMATION
8.5 Configure Ciphering Algorithm Priority for Secondary

Node Terminated DRBs
Secondary Node terminated DRBs are ciphered and deciphered in the Secondary
Node. The ciphering algorithm is selected independently.
Steps
1. Configure the SecurityHandling.cipheringAlgoPrio attribute to set the

priority order in which the ciphering algorithm is selected.
8.6 Configure Radio Link Failure Parameters for the

In EN-DC, Radio Link Control (RLC) and Radio Resource Control (RRC)
parameters exist for SCG radio configuration. By using these parameters, the
Radio Link Failure (RLF) conditions can be set for the SCG resources available for
the UE. The RLF conditions configured using these parameters are signaled to
the UE in the RRCConnectionReconfiguration NR RRC message. If the UE
detects RLF, which means RLC or RRC parameter values are exceeded, it sends
40 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

the SCGFailureInformationNR LTE RRC message to the Master Node. The

purpose of the message is to indicate a failure of the SCG resources to the Master
Node.
At the reception of the SCGFailureInformationNR message, the Master Node

initiates the Secondary Node Release procedure.
Steps
1. Set the Rrc.t310 attribute to configure a waiting time for RLF.
By configuring a waiting time for RLF, the trigger to the UE sending the
SCGFailureInformationNR message can be modified.
2. Set the Rrc.t304 attribute to configure a waiting time for the completion of
a successful NR Random Access procedure.
When the timer for a successful NR Random Access procedure expires, the
UE detects RLF and sends the SCGFailureInformationNR message to the
Master Node.
3. Configure the DataRadioBearer.dlMaxRetxThreshold attribute to define

the number of the maximum allowed RLC retransmission in downlink. When
this number is reached, the Secondary Node detects RLF and initiates the
Secondary Node Release procedure.
4. Configure the DataRadioBearer.ulMaxRetxThreshold attribute to define

the number of the maximum allowed RLC retransmission in uplink. When
this number is reached, the UE sends the SCGFailureInformationNR
message to the Master Node which initiates the Secondary Node Release
procedure.
5. Configure the DataRadioBearer.tPollRetransmitDl attribute to set the

time when a new poll request is sent by the UE. This occurs if no RLC status
report is received from the Secondary Node.
6. Configure the DataRadioBearer.tPollRetransmitUl attribute to set the

time when a new poll request is sent by the Secondary Node. This occurs if
no RLC status report is received from the UE.
8.7 Configure Threshold Value for Uplink Resource

Switching
A lower value of the NRCellDU.endcUlNrLowQualThresh attribute allows
greater NR usage, while a higher value allows the maximization of NR
throughput.
The values of the NRCellDU.endcUlNrLowQualThresh and the

NRCellDU.endcUlNrQualHyst attributes are recommended configurations. For
more information on the possible value ranges, see the MOM description.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 41

Steps
1. Set the NRCellDU.administrativeState attribute to LOCKED.
2. Set the NRCellDU.endcUlNrLowQualThresh attribute to the following

values:
Band Recommended Value Range

Low-band and mid-band -2–40(1)
High-band 17
(1) The 35–40 value range is only recommended for high throughput scenarios.
3. Set the NRCellDU.endcUlNrQualHyst attribute to the following values:
Band Recommended Value Range

Low-band and mid-band 6–12
High-band 6
It is recommended to set the NRCellDU.endcUlNrQualHyst attribute to at least
6 to minimize the switching of uplink radio resources.
4. Set the NRCellDU.administrativeState attribute to UNLOCKED.
RELATED INFORMATION
3.4.3 Switching of Uplink MCG and SCG Resources on page 15
3.5.3 Uplink Resource Switching on page 23
42 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Feature Change History
Appendix A: Feature Change History
This section lists changes that affected this feature and the impact it had on
network.
Appendix A.a: 19.Q2: X2 IP Addressing for the gNodeB In EN-DC

X2-U connectivity attributes on the gNodeB can be configured for EN-DC
between the Master eNodeB and the Secondary gNodeB.
Feature Name: LTE-NR Dual Connectivity

Feature Identity: FAJ 121 4908 R2
Value Package Name: NR Common Features Base Package
Value Package Identity: FAJ 801 4002 R3
Access Type: NR
The IP address for connections over the X2-U interface in EN-DC can be
configured between the Master eNodeB and the Secondary gNodeB using the
GNBCUUPFunction.x2UpIpAddressRef attribute.
If the GNBCUUPFunction.x2UpIpAddressRef attribute is not configured, the

GNBCUUPFunction.upIpAddressRef mandatory attribute can be used to set up
connections over the X2-U interface in EN-DC. These attributes are used for all
connections over the X2-U interface for the gNodeB.
Note: The GNBCUUPFunction.rpUpIpAddressRef attribute is no longer used

for configuring the IP address for connections over the X2-U interface in
EN-DC.

No impact.
Operation
No impact.
Interfaces
X2-U Downlink packets are forwarded from the Master

(eNodeB to the Secondary (gNodeB using a packet
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 43

forwarding tunnel over the X2-U interface configured for

EN-DC.
Hardware
No special hardware requirements.
Other Network Elements

No impact.
Appendix A.b: 19.Q3: Downlink Packet Forwarding at Secondary Node Addition Procedure
for NR in EN-DC
Downlink packet forwarding is supported between the Master Node and the
Secondary Node during the Secondary Node Addition procedure.

Value Package Identity: FAJ 801 4002
Access Type: NR

During the Secondary Node Addition procedure, bearer resources allowed to be

Secondary Node terminated Split DRBs are moved from the Master Node to the
Secondary Node. Packet forwarding is performed between old MCG bearers in
the Master Node and newly set up Split DRBs in the Secondary Node.
Packet forwarding ensures that downlink packet loss is minimized during the
Secondary Node Addition procedure.
If the new bearer resources are set up in the Secondary Node, user plane data in
downlink is sent to the new Secondary Node terminated Split DRBs.

By ensuring that downlink packet loss is minimized during the Secondary Node
Addition procedure, data retransmission and TCP slow start can be avoided.
44 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Operation
The following PM counters on the Secondary (gNodeB include forwarded packet
count in downlink for each QCI during the Secondary Node Addition procedure:
— X2UTermination.pmPdcpPktFwdRecDlQos for received DRB packets
— X2UTermination.pmPdcpPktFwdRecDlDiscQos for discarded DRB packets
The following flexible counters on the Master (eNodeB include forwarded packet
count in EN-DC during the Secondary Node Addition procedure:
— EUtranCellFDD.pmFlexPdcpPktFwdDl
— EUtranCellFDD.pmFlexPdcpPktDiscDlHo
— EUtranCellTDD.pmFlexPdcpPktFwdDl
— EUtranCellTDD.pmFlexPdcpPktDiscDlHo
The following PM counters on the Master (eNodeB include forwarded packet

count in EN-DC during the Secondary Node Addition procedure:
— EUtranCellFDD.pmPdcpPktFwdDl
— EUtranCellFDD.pmPdcpPktDiscDlHo
— EUtranCellFDD.pmPdcpPktDiscDlHoQci
— EUtranCellTDD.pmPdcpPktFwdDl
— EUtranCellTDD.pmPdcpPktDiscDlHo
— EUtranCellTDD.pmPdcpPktDiscDlHoQci
Interfaces
X2-U Downlink packets are forwarded from the Master

(eNodeB to the Secondary (gNodeB using a packet
forwarding tunnel over the X2-U interface configured for
EN-DC.
Hardware

No impact.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 45

Appendix A.c: 19.Q4: Switching of Uplink MCG and SCG Resources

This enhancement enables the LTE-NR Dual Connectivity feature to use
uplink switching of MCG and SCG radio resources depending on the radio
quality.

NR High-Band Base Package
FAJ 801 4002/5H R3
FAJ 801 4002/5LM R3
Access Type: NR
The switching of MCG and SCG radio resources allows uplink data transmission
to use the SCG radio resources when the estimated radio quality is good, and the
MCG radio resources when radio quality is poor. The switching of uplink MCG and
SCG resources can be used even with fast changing radio conditions.
If the NR radio quality drops below the threshold value, the UE switches to the
MCG resources of the split bearer.

If there is poor radio quality on the SCG resources, uplink transmission
performance is preserved by switching to the MCG resources.
For the X2AP interface, the following messages are implemented:

— SGNB MODIFICATION REQUIRED
— SGNB MODIFICATION CONFIRM
— SGNB MODIFICATION REFUSE
Operation
The switching of uplink MCG and SCG resources is enabled on cell level by
configuring the NRCellDU.endcUlLegSwitchEnabled attribute. The
NRCellDU.endcUlNrLowQualThresh threshold value is configured to define the
threshold of low NR radio quality. The NRCellDU.endcUlNrQualHyst parameter
defines the hysteresis for switching back to the SCG resources.
46 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Interfaces
No impact.
Hardware
No specific hardware requirements.

No impact.
Appendix A.d: 20.Q3: Increased EN-DC X2 Cardinality to 256

The feature enhancement allows to set up an increased number of X2
connections for the nodes in EN-DC deployment.
Feature Name: Basic Intelligent LTE-NR Dual Connectivity

Connectivity
Feature Identity: FAJ 121 4843 FAJ 121 4908
Value Package Name: Intelligent Connectivity NR Base Package
Value Package Identity: FAJ 801 1013 FAJ 801 4002
Node Type: Baseband Radio Node Baseband Radio Node
Access Type: LTE NR
Benefits
The main benefit of the feature enhancement is the increased number of node
connections in EN-DC.

The number of EN-DC X2 connections is increased from 64 to 256.
The enhancement allows a maximum of 256 EN-DC X2 connections for each

gNodeB or eNodeB.
Operation
The following MOs are used to configure EN-DC X2 connections:
— ExternalGNodeBFunction (LTE)
— ExternalENodeBFunction (NR)
— TermPointToGNB (LTE)
— TermPointToENodeB (NR)
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 47

The total number of direct X2 IPsec tunnels is 512. The direct X2 IPsec tunnels
include both EN-DC X2 and LTE X2 connections.
If more than 512 X2 connections are anticipated, direct X2 IPsec can be enabled
for EN-DC X2 only by setting the ENodeBFunction.ipsecEndcEpAddressRef
attribute. In this case, the ENodeBFunction.ipsecEpAddressRef attribute must
not be set.
When exceeding the limit of direct X2 IPsec VPN connections, the remaining X2
traffic is sent through the Security Gateway. This traffic is still protected by IPsec,
but delays can be anticipated.
The feature enhancement has no effect on the total number of GTP-U paths with
a unique combination of local IP address and remote IP address. Hence, the total
number of GTP-U paths can be a maximum of 576.
It is required to plan the deployment manually to keep the total number of the
specified GTP-U paths in LTE and NR within a limit of 576.
— LTE: X2-U, EN-DC X2-U, and S1-U
— NR: Xn-U, NG-U, EN-DC X2-U, and S1-U
Exceeding the limit causes the failure of additional GTP-U session setup since
GTP-U paths cannot be created.
Interfaces
No impact.
Hardware

ENM version 20.2 or later is required for this feature enhancement.
Appendix A.e: PDCP Flow Control

This enhancement introduces the option to limit the number of not yet
transmitted PDCP packets that can be in flight towards the UE.

Value Package Name: Peak Rate Evolution
48 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25


Access Type: NR
UEs may experience packet loss during LTE-NR Downlink Aggregation when the
difference of the transmission between the MCG and SCG radio resources is too
large. The enhancement aims to minimize the packet loss in the UE caused by the
following:
— The difference in the queue times for the packets in the different radio
resources.
— The Layer 2 buffer of the UE is exhausted.

No impact.
Operation
The GNBCUUPFunction.estimatedUeL2Buffer attribute is introduced. The
attribute is used to adapt to the size of the reordering buffer by limiting the
number of not yet transmitted PDCP packets that are in flight towards the UE.
Interfaces
No impact.
Hardware

This enhancement requires ENM version 20.1 or later to be used.
Appendix A.f: EN-DC-Triggered Handover at Incoming Handover

The feature supports the handover of an EN-DC-capable UE in connected
mode from an LTE cell where setting up SCG resources is not possible or
from an LTE cell supporting EN-DC, triggered at an incoming handover.

Value Package Name: NR High-Band Base Package
Value Package Identity: FAJ 801 4002/5H
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 49

FAJ 801 4002/5LM

Access Type: NR
Benefits
The feature is used to move an EN-DC-capable UE in connected mode, triggered
at an incoming handover, to a neighboring LTE cell that supports EN-DC in the
following cases:
— Handover is triggered in an LTE cell where setting up SCG resources is not
possible. The purpose of the handover is to move the UE that is unable to set
up SCG resources in a cell, to a neighboring LTE cell where setting up SCG
resources is possible.
— Handover is triggered at incoming handover in an LTE cell where setting up

SCG resources is possible. The purpose of the handover is to move the UE to
a neighboring LTE cell where it can set up a better EN-DC connection than
the EN-DC connection the UE uses originally.
The feature supports inter-frequency handover at the completion of incoming

IRAT and incoming intra-LTE handovers.
With the feature activated, the eNodeB considers the following when selecting
the target LTE cell:
— NR coverage
— Prioritized NR frequencies
— Band combinations supported by the UE
With the feature activated, the UE has a better chance to be connected through
EN-DC with better throughput.

The subscriber capacity is slightly lowered because of increased CPU load. The
feature relies on UE inter-frequency measurements to identify the UE that is
suitable for EN-DC-triggered handover.
An increase in the RRC signaling associated with inter-frequency measurements

and the handover-related signaling can be expected. When using this feature, the
number of inter-frequency handovers increases even in good radio conditions.
Operation
The benefits of the enhancement can be observed with the Handover Success
Rate KPI.
This feature introduces the following counters:
50 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

— EUtranCellFDD.pmCellHoPrepAttLteInterFEndcHo
— EUtranCellTDD.pmCellHoPrepAttLteInterFEndcHo
— EUtranCellFDD.pmCellHoPrepSuccLteInterFEndcHo
— EUtranCellTDD.pmCellHoPrepSuccLteInterFEndcHo
— EUtranCellFDD.pmCellHoExeAttLteInterFEndcHo
— EUtranCellTDD.pmCellHoExeAttLteInterFEndcHo
— EUtranCellFDD.pmCellHoExeSuccLteInterFEndcHo
— EUtranCellTDD.pmCellHoExeSuccLteInterFEndcHo
Interfaces
No impact.
Hardware
No impact.

To fully benefit from the change, the node requires support from ENM version
20.3 or later.
5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 51

LTE-NR Dual Connectivity: Feature Description

Uploaded by

Copyright:

Available Formats

You might also like

LTE-NR Dual Connectivity: Feature Description

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE-NR Dual Connectivity: Feature Description

Uploaded by

Copyright:

Available Formats

LTE-NR Dual Connectivity

5/221 04-LZA 701 6017/1 Uen CZ12C

5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

1 LTE-NR Dual Connectivity Overview 1

2 Dependencies of LTE-NR Dual Connectivity 2

3 Feature Operation of LTE-NR Dual Connectivity 4

4 Network Impact of LTE-NR Dual Connectivity 31

5 Parameters for LTE-NR Dual Connectivity 33

6 Performance of LTE-NR Dual Connectivity 34

7 Activate Basic Feature 36

8 Engineering Guidelines for LTE-NR Dual Connectivity 37

5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

8.3 TCP Optimization for the Secondary Node Terminated DRBs in

Appendix A: Feature Change History 43

5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

1 LTE-NR Dual Connectivity Overview

EN-DC is realized as the combination of the following features and system

— LTE-NR Dual Connectivity (FAJ 121 4908)

— LTE carrier aggregation

The benefits of the EN-DC deployment are the following:

— Sustainable capacity and performance growth.

5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 1

2 Dependencies of LTE-NR Dual Connectivity

Table 1 Feature Dependencies

Feature Relationship Description

If EN-DC is deployed without the

— The LTE cells and the NR cells are

— The LTE-NR Uplink Aggregation

2 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Feature Relationship Description

If EN-DC is deployed without the time synchronization feature, EN-DC setup

— Packet forwarding is not supported for Secondary Node terminated DRBs

5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 3

3 Feature Operation of LTE-NR Dual

3.1 EN-DC Deployment

— Basic Intelligent Connectivity (FAJ 121 4843)

— LTE-NR Dual Connectivity (FAJ 121 4908)

— LTE carrier aggregation

The EN-DC-capable UE is always connected to the eNodeB, being the Master

4 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Figure 1 Connection for the EN-DC-Capable UE

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

Master Cell Group (MCG)

Secondary Cell Group (SCG)

When the EN-DC-capable UE is connected to both the Master Node (eNodeB)

Master Node terminated MCG DRBs

Secondary Node terminated split DRBs

5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 5

can transmit user plane traffic between the UE and the

Secondary Node terminated MCG DRBs

6 5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25

Master Node Secondary Node Secondary Node

eNodeB X2-U gNodeB

Figure 2 MCG and SCG Radio Resources in EN-DC

The UE uses either of the following combinations of radio resources when

5/221 04-LZA 701 6017/1 Uen CZ12C | 2020-08-25 7

In EN-DC, the UE is in RRC_CONNECTED mode in the eNodeB. The control of the

The gNodeB resources, including a candidate NR cell, for the EN-DC-capable UE