LTE4193 Dynamic Trigger for LTE-NR

DC Option 3X
Feature Assessment
May 20th 2019

1 © Nokia 2019 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
What’s new in LTE4193

• Support for multiple NR-PDCP bearers setup during Initial Context Setup procedure.
• Support for E-RAB Setup of EN-DC eligible bearer(s) configured as NR-PDCP bearer(s).
• If UE has no SCG split bearer, then trigger of EN-DC setup
• Support for incoming inter-eNB handover (including inter-RAT HO) with one or more EN-DC
eligible bearer(s) that are configured as NR-PDCP bearer(s).
• Upon HO completion target eNB, triggers EN-DC setup.
• Support for incoming intra-eNB handover with one or more NR PDCP bearer(s) that are
configured as NR-PDCP bearer(s).
• Upon HO completion target eNB, triggers EN-DC setup.
• Support for B1 measurements to allow for dynamic triggering of EN-DC bearer setup
• B1 measurements configured for all cases of UE entering cell (ICS/HO) and E-RAB bearer setup
• B1 measurements deconfigured after successful SgNB addition
• B1 measurements re-established after SgNB release

2 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
Dynamic trigger of EN-DC procedure

LTE4193 introduces the capability for eNB to trigger E-UTRA NR Dual connectivity (EN-DC) based on NR coverage. Until
now, in LTE4088, EN-DC is triggered blindly immediately after Initial Context Setup.
• For NR coverage detection, eNB uses B1 measurements on NR frequencies. UE triggers measurement report for B1
event when candidate cell strength is above specified threshold (entry criteria defined as per TS 36.331 section
5.5.4.7).
• When NR coverage conditions are met, EN-DC procedure to perform SCG split bearer is triggered. The NR cell used for
SgNB addition is chosen as the strongest cell from B1-NR measurement report from the UE. The NR-PDCP bearer
chosen for SCG split bearer creation is based on ARP level of the bearer as implemented in LTE4088. The actual
procedure for SCG split bearer creation is not modified as part of this feature (remains the same same as in LTE4088)
• If SgNB addition procedure fails for the selected SgNB, MeNB will retry SgNB addtition procedure for the next SgNB
based on next strongest B1-NR measurement result until there is no more NR cells in B1-NR measurement report.
MeNB will send all reported NR cells corresponding to the selected SgNB, in the SgNB Addition procedure.

• NOTE: in case of blind SgNB addition procedure i.e. LTE4088 enabled, but LTE4193 disabled, only the default or
prioritized NR cell will be attempted; there would be no retry of other other NR cells in case of failure.

3 © Nokia 2018 Customer Confidential

Technical Details
Dual Connectivity NSA mode 3x operation – call flow (1/2)
UE MeNB SgNB MME S-GW P-GW

X2 connection existing

LTE Cell detection (PSS and SSS) and

LTE System Information decoding HSS
Random Access over LTE

RRC Connection Establishment S1AP:Initial UE Message

Update Location
GTP:Create Session Request
GTP:Create Session Request (DL S5 TEID)

GTP:Create Session Response (UL S5 TEID)

S1AP:Initial Context Setup Request (UL S1 TEID) GTP:Create Session Response (UL S1 TEID)

AS Security Setup

UE Capability Transfer

RRC Connection Reconfiguration S1AP:Initial Context Setup Response (DL S1 TEID)

GTP:Modify Bearer Request (DL S1 TEID)
GTP:Modify Bearer Request

GTP:Modify Bearer Response

GTP:Modify Bearer Response
UL S1 TEID / DL S1 TEID UL S5 TEID / DL S5 TEID

4 © Nokia 2018 Customer confidential

Technical Details
X2AP: SGNB ADDITION REQUEST
UE MeNB SgNB MME S-GW P-GW

Measurement Report

X2AP:SgNB Addition Request With LTE4193 the SgNB Addition Request is launched
X2AP:SgNB Addition Request Acknowledge
only upon receiving UE Measurement Report with the NR
RRC Connection Reconfiguration
measurement quantity (RSRP, RSRQ) that fulfills the NR
RRC Connection Reconfiguration Complete activation conditions
X2AP:SgNB Reconfiguration Complete

X2AP:SN Status Transfer

UL data only

DL data Forwarding (opt.)

5G Cell detection (PSS and SSS) and 5G System Information decoding

Random Access over 5G

S1AP:E-RAB Modification Indication GTP:Modify Bearer Request

GTP:Modify Bearer Response

Two channels over air interface S1AP:E-RAB Modification Confirm
U-Plane
U-Plane, C-Plane

5 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
Feature details

• LTE4193 applies to any eligible bearer independently how it was setup: E-RAB setup, incoming handover, except that
EN-DC is not triggered after call re-establishment.
• Eligible bearers of EN-DC capable UE are created in the cell with NR PDCP, whatever the cause of bearer creation.
- ARP Priority Level is used to to select which bearer will be EN-DC split

• LTE4193 relies on report of B1 measurement for NR to trigger dual connectivity for the eligible bearer.
• The measurement is configured on all the EN-DC capable UE supporting it, when the bearer exists and dual
connectivity is not active. The eNB triggers DC establishment once the B1 measurement condition has been reported.
• At EN-DC establishment, B1 measurement is de-configured.

• LTE4193 sets measurement gaps as necessary for B1 measurements of NR. To enable measurement gaps, all target
neighboring NR cells shall have the same overlapping SSB timing configuration, and for capacity reason, SSB
periodicity shall be 20ms or less. SSB duration of 5 subframes is not be supported.

6 © Nokia 2018 Customer Confidential

Technical Details
EN-DC eligible bearer
Verification if the bearer is suitable for EN-DC setup (EN-DC eligible)
• check for nonGBR QCIs (QCI 6 to QCI 9) and operator specific nonGBR QCIs (QCI98 to QCI100 or QCI128 to QCI254):
- If in the corresponding QCI Profile (qciTab-x parameter) operator configured EN-DC support for this QCI (parameter
lteNrDualConnectSupport).
- ARP value of this bearer is within ARP range configured by operator as EN-DC allowed ARP range by setting startArpEnDc
and stopArpEnDc parameters in the corresponding QCI Profile (following condition must be met startArpEnDc<=
ARP<=stopArpEnDc)
• UE supports EN-DC in its capabilities
• If a Handover Restriction List was provided by MME (or during a previous incoming HO), and if this HRL does not contain IE “NR
Restrict in EPS as Secondary RAT” set to value “NRrestrictedinEPSasSecondaryRAT”.
• the eNB need to check UL SCell exist or not. If exist, then EN-DC connectivity shall be not started for the UE.
• - if LTE4575 is disabled, the eNB need to check SCell exist or not. If exist, then EN-DC connectivity shall be not started for the
UE.
If any of these conditions is not satisfied, such bearer will be treated as MCG bearer and will be handled according legacy LTE
behavior.
Note that within INITIAL CONTEXT SETUP all of bearers will be treated as suitable for EN-DC, if they are configured with QCI values,
for which EN-DC support is configured.

7 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
B1 measurements

• LTE4193 introduces the capability for eNB to trigger E-UTRA NR Dual connectivity (EN-DC) based on NR coverage.
Without LTE4193 (LTE4088), EN-DC is triggered blindly immediately after Initial Context Setup.
• For NR coverage detection, eNB will use B1 measurements on NR frequencies. UE triggers measurement report for
B1 event when candidate cell strength is above specified threshold (entry criteria defined as per TS 36.331 section
5.5.4.7).
• When NR coverage conditions are met, EN-DC procedure to perform SCG split bearer is triggered.
- The NR cell used for SgNB addition is chosen as the strongest cell from B1-NR measurement report from the UE (up to 8 cells reported
per NR frequency band).
- The NR-PDCP bearer chosen for SCG split bearer creation is based on ARP level of the bearer. The actual procedure for SCG split bearer
creation is not modified as part of this feature, it remains same as in LTE4088.

• If SgNB addition procedure fails for the selected SgNB, MeNB will re-try SgNB addtition procedure for the next SgNB
based on next strongest B1-NR measurement result until there is no more NR cells in B1-NR measurement report.
• MeNB will send all reported NR cells corresponding to the selected SgNB, in the SgNB Addition procedure.

8 © Nokia 2018 Customer Confidential

Technical details
Measurement gap for B1-NR measurements

The measurement gaps for B1-NR measurements need to be supported.

• It’s assumed that SSB periodicity is 20ms. A higher periodicity (e.g. 40 ms or more) would result in:
- Lower number of UEs eligible for EN-DC due to lack of compatible PUCCH resources for EN-DC MG
- When CA is configured, a higher usage of aCSI, resulting in lack of PDCCH capacity and in uplink aggregated throughput
reduction
• UEs that are candidate for EN-DC are immediately configured with PUCCH resources that are compatible with EN-DC
measurement gap location at Initial Context Setup, or at new cell access with UE capability info (e.g. incoming HO).
• When measurement gaps are required later, the same gap pattern (i.e. periodicity and offset) would be provided.
There’s no further gap pattern reconfiguration during the call. The exception is when a measurement gap is required
for RSTD (Reference Signal Time Difference), then the gap pattern would be reconfigured as per LTE1638 existing
procedure; once done, there’s no further reconfiguration back to EN-DC compatible area.
• For those candidate EN-DC UEs, if there’s no compatible PUCCH resources that can be found at ICS or initial cell
access time, then the UE is configured with B1-NR measurement without measurement gaps.

9 © Nokia 2018 Customer Confidential

Technical Details
Support of multiple neighbor NR cell relationships

LTE4193 supports multiple neighbor 5G cell configurations by extending the multiplicity of LNRELGNBCELL object.
If LTE4193 is disabled, then default cell is used to pick gNB cell for SCG split bearer.

X2 SgNB addition Request -> MeNB to SgNB Container-> CG-ConfigInfo -> NewRadioCell information,
- In case of blind/data-volume-only based EN-DC setup, only the default LNRELGNBCELL will be included without
RSRP/RSRQ measurement information
- In case of NR-B1 measurement/all-condition based EN-DC setup, all the LNRELGNBCELLs in B1-NR report and
mapped to that SgNB will be included w/ RSRP/RSRQ measurement information.

10 © Nokia 2018 Customer Confidential

Technical details
Event B1 measurement for EN-DC with gNB (5G)

eNB supports event B1 measurement for EN-DC with gNB(5G) on NR carriers

3GPP TS 36.133 (chapter 8.1.2.1.1.1) says that a UE shall be capable of measuring using gaps up to the following number
of carriers per RAT group within up to the total of 7 carrier frequency layers:
• 3 FDD E-UTRA inter-frequency carriers
• 3 TDD E-UTRA inter-frequency carriers
• 3 UTRA carriers (either 3 UTRA-FDD or 3 UTRA-TDD carries)
• 32 GSM carriers (one GSM layer corresponds to maximum 32 carriers)
• 5 CDMA2000-1XRTT carriers
• 5 CDMA2000-eHRPD carriers

On top of this, 3GPP TS36.133 v15.1.0 requires an EN-DC capable UE to support monitoring of up to 9 frequency
carriers.
As part of LTE4193 feature, measurement of up to two NR carriers are supported. These 2 NR carriers shall not be
counted as part of the above limit of total 7 carrier frequency layers (updated limit: 9 carriers).

Note: within the scope of LTE4193 a single NR measurement object (measObjectNR-r15) will
configure only cells from a single frequency

11 © Nokia 2018 Customer Confidential

Test Setup

12 © Nokia 2018 Customer Confidential

Test Setup
Parameter Settings
(PLMN-PLMN/MRBTS-116171/LNBTS-116171),actDynTrigLteNrDualConnectivity=1

(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),dynTriggerLteNrDcConfList:Structure1:lcrId=-1
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),dynTriggerLteNrDcConfList:Structure1:method=10

(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcQuantityConfig:Structure1:filterCoefficientRsrp=4
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcQuantityConfig:Structure1:filterCoefficientRsrq=4
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcQuantityConfig:Structure1:quantityConfigId=0

(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:b1ThresholdNrRsrp=36
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:b1TimeToTriggerRsrp=40
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:b1TimeToTriggerRsrq=40
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:b1TriggerQuantity=0
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:carrierFreqNrCell=2249947
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:freqBandIndicatorNR=260
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:hysB1ThresholdRsrp=4
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:hysB1ThresholdRsrq=4
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:quantityConfigId=0
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:ssbDuration=0
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:ssbOffset=0
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:ssbPeriodicity=0
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),nrDcMeasConfig:Structure1:ssbSubcarrierSpacing=240

(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),tPeriodicPhr=10
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),tProhibitPhr=0
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),dataVolThreshold=1024
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),dlPathlossChg=1
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),enDCpMaxEUTRApowerOffset=0
(PLMN-PLMN/MRBTS-116171/LNBTS-116171/NRDCDPR-0),enDCpMaxNRpowerOffset=0

13 © Nokia 2018 Customer Confidential

Trace Analysis

14 © Nokia 2018 Customer Confidential

 EMIL Trace
Split bearer established after B1 measurement report (1/2)
01:13:59.668121 8003015874 R S1 Initial Context Setup Request [mmeUeId=39845154 enbUeId=92 ueAmbrDL=1288.64mbps ueAmbrUL=150mbps eRabId=5 qci=9 prioLevel=12 gtpTeId=2187255882 EPS-MM encAlgo=0xe000 ipAlgo=0xe000]
01:13:59.669158 8003015874 S RRC Security Mode Command [transId=2 cipherAlgo=eea2 integAlgo=eia2]
01:13:59.669305 8003015874 S RRC UE Capability Enquiry [transId=2 ueCapab(eutra,utra) bands(2,4,66,46,5,17,12,29)]
01:13:59.684483 8003015874 R RRC Security Mode Complete [transId=2]
01:13:59.707661 8003015874 R RRC UE Capability Information [transId=2 ratType=eutra]
01:13:59.711714 8003015874 S RRC Connection Reconfiguration [transId=1 measObjToAddMod(moId-1,eutra,freq-900(Band2 (1900 PCS)) moId-2,eutra,freq-710(Band2 (1900 PCS)) moId-3) rptCfgIdToAddMod(rId-
1,eutra,A3,a3offset_6,hyst_2,ttt_ms320,rsrqTrig,rId-2,eutra,A5,a5_thr1_rsrp_0,a5_thr2_rsrp_43,hyst_0,ttt_ms320,rsrpTrig,rId-3,eutra,A2,a2_thr_rsrp_18,hyst_4,ttt_ms1280,rsrpTrig,rId-4,eutra,A2,a2_thr_rsrp_24,hyst_4,ttt_ms40,rsrpTrig,rId-
5,interrat,B1,hyst_0,ttt_ms256) measIdToAddMod(mId-1,moId-1,rId-1,mId-2,moId-1,rId-2,mId-4,moId-1,rId-3,mId-7,moId-1,rId-4,mId-17,moId-3,rId-5) gap-setup gapOffset=gp0_19 NAS srbToAddMod:srb-2 drbToAddMod:epsBId=5:drbId=4:lci=3:lcg=3
drxSetup srsConf(bw0,hbw0,freqDPos=0,cfgIdx=12,txComb=0,cs2) nrRbConfig1] // MCG bearer setup, B1 measurement setup
01:13:59.836487 8003015874 R RRC Connection Reconfiguration Complete [transId=1]
01:13:59.836503 8003015874 R RRC UL Information Transfer [ EPS-MM]
01:13:59.837070 8003015874 S S1 Uplink NAS Transport [mmeUeId=39845154 enbUeId=92 EPS-MM mEnbId=1010067 rCid=3 tac=65313]
01:13:59.837312 8003015874 S S1 Initial Context Setup Response [mmeUeId=39845154 enbUeId=92 eRabId=5 gtpTeId=3641]
01:13:59.837570 8003015874 S S1 UE Capability Info Indication [mmeUeId=39845154 enbUeId=92 ueRadioCapab]
01:13:59.840600 8003015874 S RRC Connection Reconfiguration [transId=1 sCellToAddMod(cIdx=1 pci=353 dlFreq=710)] // Split bearer is not setup right after ICS. Here is another RRC reconfiguration.
01:13:59.845726 8003015874 R S1 Downlink NAS Transport [mmeUeId=39845154 enbUeId=92 EPS-MM]
01:13:59.845939 8003015874 S RRC DL Information Transfer [transId=2 EPS-MM]
01:13:59.870480 8003015874 R RRC Connection Reconfiguration Complete [transId=1]
01:13:59.870751 8003015874 PMI peg counter M8007C10_SRB2_SETUP_ATT (3)
01:13:59.870751 8003015874 PMI peg counter M8007C11_SRB2_SETUP_SUCC (3)
01:13:59.870751 8003015874 PMI peg counter M8013C47_UE_CTX_SETUP_SUCC (3)
01:13:59.870751 8003015874 PMI peg counter M8013C62_UE_CTX_SETUP_SUCC_REL11H_UE (3)
…
01:14:00.616496 8003015874 R RRC Measurement Report [mId=17 PCell:rsrp=57 rsrq=26 NeighCell] // B1 measurement report
01:14:00.617125 8003015874 S RRC UE Capability Enquiry [transId=2 ueCapab(nr,eutra-nr)]
01:14:00.673567 8003015874 R RRC UE Capability Information [transId=2 ratType=nr ratType=eutra-nr]
01:14:00.675525 8003015874 S X2 SgNB Addition Request [x2apId=283 nrEncAlgo=0xe000 nrIpAlgo=0xe000 ueAmbrDL=1288.64mbps ueAmbrUL=150mbps erabToAdd(eRabId=5,qci=9,prioLevel=12, meNBDLGtp( s1ULGtp) MeNBtoSgNBContainer
tgtCid=(mEnbId=1010067,rCid=3)]
01:14:00.722384 8003015874 R X2 SgNB Addition Request Acknowledge [x2apId=283 sgNbX2apId=15 s1DLGtp) sgNBULGtp) SgNBtoMeNBContainer]
01:14:00.727137 8003015874 S RRC Connection Reconfiguration [transId=1 measIdToRemove(17) gap-release drbToAddMod:epsBId=5:drbId=5:lci=4:lcg=3 drbToRelease(4) drxSetup sCellToAddMod(cIdx=1) nrConf-setup nrRbConfig1 nrRbConfig2]
01:14:00.862508 8003015874 R RRC Connection Reconfiguration Complete [transId=1 scgConfigResp]
01:14:00.862860 8003015874 PMI peg counter M8011C68_CA_SCELL_CONFIG_SUCC (3)
01:14:00.862860 8003015874 PMI peg counter M8080C0_SCG_ADD_PREP_ATT (3)
01:14:00.862860 8003015874 PMI peg counter M8080C3_SCG_ADD_PREP_SUCC (3)
01:14:00.862860 8003015874 PMI peg counter M8013C500_XXX (3)
01:14:00.862860 8003015874 PMI peg counter M8008C32_DRB_SCG_ADD_ATT (3)
01:14:00.862860 8003015874 PMI peg counter M8008C33_DRB_SCG_ADD_SUCC (3)
01:14:00.863125 8003015874 S X2 SgNB Reconfiguration Complete [x2apId=283 sgNbX2apId=15 meNBtoSgNBContainer]
01:14:00.863555 8003015874 S X2 SN Status Transfer [x2apId=283 x2apId=0 sgNbX2apId=15]
01:14:00.863655 8003015874 S S1 ERAB Modification Indication [mmeUeId=39845154 enbUeId=92 eRabId=5 dlGtpTeId=1966099]
01:14:00.871067 8003015874 R S1 ERAB Modification Confirm [mmeUeId=39845154 enbUeId=92 eRabId=5]
01:14:05.706650 8003015874 R X2 Secondary R A T Data Usage Report [x2apId=283 sgNbX2apId=15]
01:14:10.706803 8003015874 R X2 Secondary R A T Data Usage Report [x2apId=283 sgNbX2apId=15]
01:14:15.706985 8003015874 R X2 Secondary R A T Data Usage Report [x2apId=283 sgNbX2apId=15]
15 © Nokia 2018 Customer Confidential
 UE Trace
Split bearer established after B1 measurement report (2/2)
22:45:57.723 [4G:pci-37:700] S NAS Service Request
22:45:57.723 [4G:pci-37:700] S RRC Connection Request [mmec=177 mTmsi=0xC5D9E95B highPriorityAccess]
22:45:57.759 [4G:pci-37:700] S RAC Random Access Request (MSG1)
22:45:57.769 [4G:pci-37:700] R RAC Random Access Response (MSG2)
22:45:57.769 [4G:pci-37:700] S RAC UE Identification Message (MSG3)
22:45:57.782 [4G:pci-37:700] R RAC Contention Resolution Message (MSG4)
22:45:57.886 [4G:pci-37:700] R RRC Connection Setup [srbToAddMod srb1]
22:45:57.890 [4G:pci-37:700] S RRC Connection Setup Complete [transId=2 plmnId=1 EPS-MM:ServiceRequest]
22:45:57.928 [4G:pci-37:700] R RRC Security Mode Command [transId=2 cipherAlgo=eea2 integAlgo=eia2]
22:45:57.929 [4G:pci-37:700] S RRC Security Mode Complete [transId=2]
22:45:57.929 [4G:pci-37:700] R RRC UE Capability Enquiry [transId=2 capabReq(eutra) reqFreqNR=0x00C0040800B0061040041030]
22:45:57.929 [4G:pci-37:700] S RRC UE Capability Information [transId=2ratType=eutra ratContainer]
22:45:57.948 [4G:pci-37:700] R RRC Connection Reconfiguration [transId=1 measObjToAddMod(moId-1,eutra,carrierFreq-700,moId-2,) rptCfgIdToAddMod(rId-1,A3,a3offset_6,hyst_2,ttt_ms320,rId-2,A5,thrRsrp_0,thrRsrp_43,hyst_0,ttt_ms320,rId-
3,A2,thrRsrp_0,hyst_4,ttt_ms1280,rId-4,A2,thrRsrp_25,hyst_4,ttt_ms40,rId-5,B1,b1-ThresholdNR-r15 nr-RSRP-r15 : 61,hyst_4,ttt_ms40,ss-sinr FALSE) measIdToAddMod(mId-1,moId-1,rId-1,mId-2,moId-1,rId-2,mId-4,moId-1,rId-3,mId-7,moId-1,rId-
4,mId-17,moId-2,rId-5,) srbToAddMod:srb-2:epsBId=6:drbId=4:epsBId=5:drbId=5 drx_setup taTimer=sf10240 srsConf(bw2,hbw0,freqDPos=0,cfgIdx=12,txComb=0,cs0) nrRbConfig1] // Setup MCG bearer, B1 measurement
22:45:58.304 [4G:pci-37:700] S RRC Connection Reconfiguration Complete [transId=1]

22:45:58.843 [4G:pci-37:700] S RRC Measurement Report [mId=17:rsrp=79 rsrq=13 NeighCellNR pci=62 rsrp=80] // UE send B1 measurement report
22:45:58.888 [4G:pci-37:700] R RRC UE Capability Enquiry [transId=2 capabReq(nr,eutra-nr) reqFreqNR=0x00C0040800B0061040041030]
22:45:58.893 [4G:pci-37:700] S RRC UE Capability Information [transId=2ratType=nr ratContainerratType=eutra ratContainer]
22:45:59.008 [4G:pci-37:700] R RRC Connection Reconfiguration [transId=1 measIdToRemove(17,):epsBId=5:drbId=6 drbToRelease(5,) drx_setup taTimer=sf10240 nrConf-setup nrRbConfig1 nrRbConfig2]
22:45:59.088 [4G:pci-37:700] S RRC Connection Reconfiguration Complete [transId=1]
22:46:00.609 [4G:pci-37:700] R RRC Connection Reconfiguration [transId=1 measIdToAddMod(mId-17,moId-2,rId-5,):epsBId=5:drbId=7 drbToRelease(6,) drx_setup taTimer=sf10240 nrConf-release nrRbConfig1]
22:46:00.648 [4G:pci-37:700] S RRC Connection Reconfiguration Complete [transId=1]

22:46:01.204 [4G:pci-37:700] S RRC Measurement Report [mId=17:rsrp=79 rsrq=11 NeighCellNR pci=62 rsrp=76]
22:46:01.250 [4G:pci-37:700] R RRC UE Capability Enquiry [transId=2 capabReq(nr,eutra-nr) reqFreqNR=0x00C0040800B0061040041030]
22:46:01.251 [4G:pci-37:700] S RRC UE Capability Information [transId=2ratType=nr ratContainerratType=eutra ratContainer]
22:46:01.368 [4G:pci-37:700] R RRC Connection Reconfiguration [transId=1 measIdToRemove(17,):epsBId=5:drbId=8 drbToRelease(7,) drx_setup taTimer=sf10240 nrConf-setup nrRbConfig1 nrRbConfig2]
22:46:01.446 [4G:pci-37:700] S RRC Connection Reconfiguration Complete [transId=1]

22:46:02.412 [4G:pci-37:700] S RRC SCG Failure Information NR [synchReconfigFailureSCG]

22:46:03.008 [4G:pci-37:700] R RRC Connection Reconfiguration [transId=1 measIdToAddMod(mId-17,moId-2,rId-5,):epsBId=5:drbId=9 drbToRelease(8,) drx_setup taTimer=sf10240 nrConf-release nrRbConfig1]
22:46:03.044 [4G:pci-37:700] S RRC Connection Reconfiguration Complete [transId=1]
…
22:46:24.008 [4G:pci-37:700] R RRC Connection Release [transId=3 cause=other]

The eNB sends UE capability inquiry every time before set up split
bearer (next chart). This will be fixed CRL-29598 Improve EN-DC UE
capability handling of non-standard-compliant Ues.

16 © Nokia 2018 Customer Confidential

 UE Trace
Split bearer established after B1 measurement report (2/2)
We have analyzed the cases and outcome is that this is a UE deficiency. UE is clearly deviating from what is defined in 3GPP.
There is a workaround possible from eNB side. Please be informed that our plan is to fix this with

CRL-29598 Improve EN-DC UE capability handling of non-standard-compliant UEs

As to the case that the UE does not include the applied filter in the UE-MRDC-CAP, this is clearly a UE bug and it is expected
behavour that eNB does not start EN-DC if does not get from the UE. From TS 38.331 section 5.6.1.4:

<<
The UE shall:

1> include the received frequencyBandListFilter in the field appliedFreqBandListFilter of the requested UE capability;
>>

missing appliedFreqBandListFilter leads to retrieval of EUTRAN-NR and NR

containers with same filter used during EUTRAN container

17 © Nokia 2018 Customer Confidential

 UE Trace
Intra-eNB HO: Split bearer established after B1 measurement report on target cell

21:59:24.129 [4G:pci-307:9820] S RRC Measurement Report [mId=1:rsrp=48 rsrq=0 NeighCell pci=308:rsrp=52 rsrq=12 pci=387 rsrp=81]
21:59:24.396 [4G:pci-307:9820] S RRC Measurement Report [mId=1:rsrp=47 rsrq=0 NeighCell pci=308:rsrp=53 rsrq=13 pci=387 rsrp=81]
21:59:24.459 [4G:pci-307:9820] R RRC Connection Reconfiguration [transId=1 mobilityCtrl targetPhyCellId=308 newUeId=62697 drx_setup taTimer=sf10240 srsConf(bw3,hbw0,freqDPos=4,cfgIdx=12,txComb=1,cs7)
srConf(pucchResIdx=40,confIdx=5,dsrTransMax=n64) cqiIndxTab(pCell:) intraLTE cipherAlgo=eea2 integAlgo=eia2 nrConf-release nrRbConfig1] // HO command with split bearer release
21:59:24.482 [4G:pci-308:9820] S RRC Connection Reconfiguration Complete [transId=1]
21:59:24.492 [4G:pci-308:9820] S RAC Random Access Request (MSG1)
21:59:24.502 [4G:pci-308:9820] R RAC Random Access Response (MSG2)
21:59:24.502 [4G:pci-308:9820] S RAC UE Identification Message (MSG3)
21:59:24.514 [4G:pci-308:9820] R RRC Connection Reconfiguration [transId=1 measIdToRemove(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,) measIdToAddMod(mId-1,moId-1,rId-1,mId-2,moId-1,rId-2,mId-
4,moId-1,rId-3,mId-7,moId-1,rId-4,mId-17,moId-2,rId-5,) drx_setup taTimer=sf10240]
21:59:24.520 [4G:pci-308:9820] S RRC Connection Reconfiguration Complete [transId=1]
21:59:24.521 [4G:pci-308:9820] R RRC System Information Block Type1 [tac=33806,cid=360024_150,qRxLevMin=-116]
21:59:24.537 [4G:pci-308:9820] R RRC System Information [sib2:t300=ms1000,t301=ms1500,t310=ms2000,t311=ms10000,upperLayerIndR15]
21:59:24.555 [4G:pci-308:9820] R RRC System Information [sib3:,cellReselPrio=4,qRxLevMin=-116]
21:59:24.560 [4G:pci-308:9820] R RRC System Information Block Type1 [tac=33806,cid=360024_150,qRxLevMin=-116]
21:59:24.562 [4G:pci-308:9820] R RRC Connection Reconfiguration [transId=1 srsConf(bw2,hbw0,freqDPos=6,cfgIdx=7,txComb=0,cs6)]
21:59:24.566 [4G:pci-308:9820] S RRC Connection Reconfiguration Complete [transId=1]
21:59:24.575 [4G:pci-308:9820] R RRC System Information [sib5:,qRxLevMin=-122,cellReselPrio=4,qRxLevMin=-122,cellReselPrio=3,qRxLevMin=-122,cellReselPrio=2,qRxLevMin=-122,cellReselPrio=2]
21:59:24.590 [4G:pci-308:9820] R RRC UE Capability Enquiry [transId=2 capabReq(eutra) reqFreqNR=0x0020760818]
21:59:24.590 [4G:pci-308:9820] S RRC UE Capability Information [transId=2ratType=eutra ratContainer]
21:59:24.595 [4G:pci-308:9820] R RRC System Information [sib6:carrierFreq=4385,,cellReselPrio=0,qRxLevMin=-120carrierFreq=9662,,cellReselPrio=6,qRxLevMin=-120]
21:59:25.844 [4G:pci-308:9820] R RRC Paging [mmec=193,mTmsi=0xD81B5235]
21:59:27.846 [4G:pci-308:9820] S RRC Measurement Report [mId=17:rsrp=48 rsrq=4 NeighCellNR pci=385 rsrp=84 pci=387 rsrp=73] // B1 measurement report
21:59:27.878 [4G:pci-308:9820] R RRC UE Capability Enquiry [transId=2 capabReq(nr,eutra-nr) reqFreqNR=0x0020760818]
21:59:27.879 [4G:pci-308:9820] S RRC UE Capability Information [transId=2ratType=nr ratContainerratType=eutra ratContainer]
21:59:27.930 [4G:pci-308:9820] S RRC Measurement Report [mId=1:rsrp=47 rsrq=3 NeighCell pci=307:rsrp=50 rsrq=13]
21:59:27.949 [4G:pci-308:9820] R RRC Connection Reconfiguration [transId=1 measIdToRemove(17,):epsBId=5:drbId=4 drbToRelease(5,) drx_setup taTimer=sf10240 nrConf-setup nrRbConfig1 nrRbConfig2] // split bearer set up after HO to
target.
21:59:28.035 [4G:pci-308:9820] S RRC Connection Reconfiguration Complete [transId=1]
21:59:28.167 [4G:pci-308:9820] S RRC Measurement Report [mId=1:rsrp=47 rsrq=3 NeighCell pci=307:rsrp=49 rsrq=12 pci=387 rsrp=81]
21:59:28.429 [4G:pci-308:9820] S RRC Measurement Report [mId=1:rsrp=48 rsrq=4 NeighCell pci=307:rsrp=48 rsrq=12 pci=387 rsrp=81]
21:59:28.671 [4G:pci-308:9820] S RRC Measurement Report [mId=1:rsrp=47 rsrq=4 NeighCell pci=307:rsrp=47 rsrq=12 pci=387 rsrp=81]

18 © Nokia 2018 Customer Confidential

UE Log
Inter-eNB HO: Split bearer established after B1 measurement report on target cell

//on NVL00024
20:11:41.356 [4G:pci-37:700] S RRC Measurement Report [mId=17:rsrp=67 rsrq=21 NeighCellNR pci=62 rsrp=64]
20:11:41.392 [4G:pci-37:700] R RRC UE Capability Enquiry [transId=2 capabReq(nr,eutra-nr) reqFreqNR=0x00C0040800B0061040041030]
20:11:41.392 [4G:pci-37:700] S RRC UE Capability Information [transId=2ratType=nr ratContainerratType=eutra ratContainer]
20:11:41.513 [4G:pci-37:700] R RRC Connection Reconfiguration [transId=1 measIdToRemove(17,):epsBId=5:drbId=25 drbToRelease(24,) drx_setup taTimer=sf10240 nrConf-setup nrRbConfig1 nrRbConfig2]
20:11:41.575 [4G:pci-37:700] S RRC Connection Reconfiguration Complete [transId=1]
20:11:42.041 [4G:pci-37:700] R RRC Paging [mmec=193,mTmsi=0xD9CA4B40]
20:11:43.361 [4G:pci-37:700] R RRC Paging [mmec=193,mTmsi=0xCA755F08]
20:11:43.596 [4G:pci-37:700] R RRC Connection Reconfiguration [transId=1 measIdToAddMod(mId-17,moId-2,rId-5,):epsBId=5:drbId=26 drbToRelease(25,) drx_setup taTimer=sf10240 nrConf-release nrRbConfig1] // split bearer released.
20:11:43.639 [4G:pci-37:700] S RRC Connection Reconfiguration Complete [transId=1]

20:11:56.044 [4G:pci-37:700] S RRC Measurement Report [mId=1:rsrp=50 rsrq=0 NeighCell pci=194:rsrp=55 rsrq=12]
20:11:56.145 [4G:pci-37:700] R RRC Connection Reconfiguration [transId=1 mobilityCtrl targetPhyCellId=194 newUeId=46822 srbToAddMod:srb-1:srb-2:epsBId=5:drbId=26 drx_setup taTimer=sf10240
srsConf(bw3,hbw0,freqDPos=11,cfgIdx=12,txComb=1,cs3) srConf(pucchResIdx=2,confIdx=5,dsrTransMax=n64) intraLTE cipherAlgo=eea2 integAlgo=eia2 fullConfig nrRbConfig1] // In HO command

// on NVL00404
20:11:56.183 [4G:pci-194:700] S RRC Connection Reconfiguration Complete [transId=1]
20:11:56.189 [4G:pci-194:700] S RAC Random Access Request (MSG1)
20:11:56.199 [4G:pci-194:700] R RAC Random Access Response (MSG2)
20:11:56.199 [4G:pci-194:700] S RAC UE Identification Message (MSG3)
20:11:56.211 [4G:pci-194:700] R RRC Connection Reconfiguration [transId=1 measObjToAddMod(moId-1,eutra,carrierFreq-700,moId-2,) rptCfgIdToAddMod(rId-1,A3,a3offset_6,hyst_2,ttt_ms320,rId-2,A5,thrRsrp_0,thrRsrp_43,hyst_0,ttt_ms320,rId-
3,A2,thrRsrp_0,hyst_4,ttt_ms1280,rId-4,A2,thrRsrp_25,hyst_4,ttt_ms40,rId-5,B1,b1-ThresholdNR-r15 nr-RSRP-r15 : 61,hyst_4,ttt_ms40,ss-sinr FALSE)
measIdToRemove(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,) measIdToAddMod(mId-1,moId-1,rId-1,mId-2,moId-1,rId-2,mId-4,moId-1,rId-3,mId-7,moId-1,rId-4,mId-17,moId-2,rId-5,)] // setup B1
measurement
20:11:56.213 [4G:pci-194:700] S RRC Connection Reconfiguration Complete [transId=1]
20:11:56.217 [4G:pci-194:700] R RRC System Information Block Type1 [tac=33806,cid=360024_10,qRxLevMin=-122]
20:11:56.220 [4G:pci-194:700] S NAS Tracking Area Update Request [no-bearer-req,TA-updt,oldGuti=(mmeGid=65369,mmec=177,mTmsi=0XCEC5E94E),tai=33803]
20:11:56.220 [4G:pci-194:700] S RRC UL Information Transfer [EPS-MM:TAURequest(TA-updt,no-bearer-req,oldGuti=(mmeGid=65369,mmec=177,mTmsi=0xCEC5E94E))]
20:11:56.233 [4G:pci-194:700] R RRC System Information [sib2:t300=ms1000,t301=ms1500,t310=ms2000,t311=ms10000,upperLayerIndR15]
20:11:56.252 [4G:pci-194:700] R RRC System Information [sib3:,cellReselPrio=3,qRxLevMin=-122]
20:11:56.694 [4G:pci-194:700] R RRC Connection Reconfiguration [transId=1 srsConf(bw2,hbw0,freqDPos=0,cfgIdx=12,txComb=0,cs2)]
20:11:56.699 [4G:pci-194:700] S RRC Connection Reconfiguration Complete [transId=1]
20:11:56.701 [4G:pci-194:700] R RRC DL Information Transfer [transId=2 EPS-MM]

20:12:24.770 [4G:pci-194:700] S RRC Measurement Report [mId=17:rsrp=61 rsrq=6 NeighCellNR pci=380 rsrp=69] // B1 measurement
20:12:24.795 [4G:pci-194:700] R RRC UE Capability Enquiry [transId=2 capabReq(nr,eutra-nr) reqFreqNR=0x00F040C0E80400204005803082]
20:12:24.801 [4G:pci-194:700] S RRC UE Capability Information [transId=2ratType=nr ratContainerratType=eutra ratContainer]
20:12:24.937 [4G:pci-194:700] R RRC Connection Reconfiguration [transId=1 measIdToRemove(17,):epsBId=5:drbId=6 drbToRelease(26,) taTimer=sf10240 nrConf-setup nrRbConfig1 nrRbConfig2] // split bearer setup on target cell.

19 © Nokia 2018 Customer Confidential

 UE Trace
LTE4193_5: Handover into EN-DC capable cell (actDynTrigLteNrDualConnectivity FALSE)
split bearer is blindly activated after HO
17:37:43.470 [4G:pci-307:9820] R RRC Security Mode Command [transId=2 cipherAlgo=eea2 integAlgo=eia2]
17:37:43.470 [4G:pci-307:9820] S RRC Security Mode Complete [transId=2]
17:37:43.471 [4G:pci-307:9820] R RRC UE Capability Enquiry [transId=2 capabReq(eutra,utra)]
17:37:43.472 [4G:pci-307:9820] S RRC UE Capability Information [transId=2ratType=eutra ratContainerratType=utra ratContainer]
17:37:43.488 [4G:pci-307:9820] R RRC Connection Reconfiguration [transId=1 measObjToAddMod(moId-1,eutra,carrierFreq-9820,) rptCfgIdToAddMod(rId-1,A3,a3offset_6,hyst_2,ttt_ms320,rId-2,A5,thrRsrp_0,thrRsrp_43,hyst_0,ttt_ms320,rId-
3,A2,thrRsrp_0,hyst_4,ttt_ms1280,rId-4,A2,thrRsrp_25,hyst_4,ttt_ms40,) measIdToAddMod(mId-1,moId-1,rId-1,mId-2,moId-1,rId-2,mId-4,moId-1,rId-3,mId-7,moId-1,rId-4,) srbToAddMod:srb-2:epsBId=5:drbId=4 drx_setup taTimer=sf10240
srsConf(bw2,hbw0,freqDPos=6,cfgIdx=7,txComb=0,cs6) nrRbConfig1] // MCG bearer setup
17:37:43.594 [4G:pci-307:9820] S RRC Connection Reconfiguration Complete [transId=1]
17:37:43.594 [4G:pci-307:9820] S RRC Connection Reconfiguration Complete [transId=1]
17:37:43.595 [4G:pci-307:9820] R NAS Attach Accept [guti=(mmeGid=65369,mmec=193,mTmsi=0XD838E978)]
17:37:43.595 [4G:pci-307:9820] R NAS Activate Default Eps Bearer Context Request
17:37:43.597 [4G:pci-307:9820] S NAS Attach Complete
17:37:43.598 [4G:pci-307:9820] S RRC UL Information Transfer [EPS-MM]
17:37:43.643 [4G:pci-307:9820] R RRC DL Information Transfer [transId=2 EPS-MM]
17:37:43.643 [4G:pci-307:9820] R NAS Emm Information
. . . . . . . UE sent many rounds of measurement reports for HO target PCI-308. eNB didn’t respond until now.
17:39:32.946 [4G:pci-307:9820] S RRC Measurement Report [mId=1:rsrp=49 rsrq=0 NeighCell pci=308:rsrp=55 rsrq=7]
17:39:33.005 [4G:pci-307:9820] R RRC Connection Reconfiguration [transId=1 mobilityCtrl targetPhyCellId=308 newUeId=42870 drx_setup taTimer=sf10240 srsConf(bw3,hbw0,freqDPos=9,cfgIdx=7,txComb=1,cs5)
srConf(pucchResIdx=2,confIdx=11,dsrTransMax=n64) intraLTE cipherAlgo=eea2 integAlgo=eia2 nrRbConfig1] // HO Command for target PCI-308

17:39:33.026 [4G:pci-308:9820] S RRC Connection Reconfiguration Complete [transId=1] // HO complete on PCI-308

17:39:33.027 [4G:pci-308:9820] S RAC Random Access Request (MSG1)
17:39:33.035 [4G:pci-308:9820] R RAC Random Access Response (MSG2)
17:39:33.035 [4G:pci-308:9820] S RAC UE Identification Message (MSG3)
17:39:33.044 [4G:pci-308:9820] R RRC System Information Block Type1 [tac=33806,cid=360024_150,qRxLevMin=-116]
17:39:33.060 [4G:pci-308:9820] R RRC Connection Reconfiguration [transId=1 measIdToRemove(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,) measIdToAddMod(mId-1,moId-1,rId-1,mId-2,moId-1,rId-2,mId-
4,moId-1,rId-3,mId-7,moId-1,rId-4,)] // No B1 setup
17:39:33.062 [4G:pci-308:9820] S RRC Connection Reconfiguration Complete [transId=1]
17:39:33.075 [4G:pci-308:9820] R RRC Connection Reconfiguration [transId=1 srsConf(bw2,hbw0,freqDPos=0,cfgIdx=12,txComb=0,cs2)]
17:39:33.081 [4G:pci-308:9820] S RRC Connection Reconfiguration Complete [transId=1]
17:39:33.081 [4G:pci-308:9820] R RRC System Information [sib2:t300=ms1000,t301=ms1500,t310=ms2000,t311=ms10000,upperLayerIndR15]
17:39:33.091 [4G:pci-308:9820] R RRC UE Capability Enquiry [transId=2 capabReq(eutra) reqFreqNR=0x00A0400580308207608180]
17:39:33.093 [4G:pci-308:9820] S RRC UE Capability Information [transId=2ratType=eutra ratContainer]
17:39:33.100 [4G:pci-308:9820] R RRC System Information [sib3:,cellReselPrio=4,qRxLevMin=-116]
17:39:33.110 [4G:pci-308:9820] R RRC UE Capability Enquiry [transId=2 capabReq(nr,eutra-nr) reqFreqNR=0x00A0400580308207608180]
17:39:33.110 [4G:pci-308:9820] S RRC UE Capability Information [transId=2ratType=nr ratContainerratType=eutra ratContainer]
17:39:33.165 [4G:pci-308:9820] R RRC Connection Reconfiguration [transId=1:epsBId=5:drbId=5 drbToRelease(4,) taTimer=sf10240 nrConf-setup nrRbConfig1 nrRbConfig2] // split bearer setup right after HO on target cell
17:39:33.240 [4G:pci-308:9820] S RRC Connection Reconfiguration Complete [transId=1]
17:39:33.600 [4G:pci-308:9820] R RRC System Information [sib5:,qRxLevMin=-122,cellReselPrio=4,qRxLevMin=-122,cellReselPrio=3,qRxLevMin=-122,cellReselPrio=2,qRxLevMin=-122,cellReselPrio=2]
17:39:33.619 [4G:pci-308:9820] R RRC System Information [sib6:carrierFreq=4385,,cellReselPrio=0,qRxLevMin=-120carrierFreq=9662,,cellReselPrio=6,qRxLevMin=-120]

20 © Nokia 2018 Customer Confidential

Performance Aspect

21 © Nokia 2018 Customer Confidential

NVL00024 – Initial MCG E-RAB Setup with NR PDCP (M8006C332/333)

22 © Nokia 2018
 NVL00024 - Establishment of additional MCG bearers with NR PDCP

Small number of additional

MCG bearer setup compare to
the initial one.

23 © Nokia 2018
NVL00024 – DRB establishment of initial MCG bearers with NR PDCP(M8007C16/17)

24 © Nokia 2018
NVL00024 - DRB establishment attempts of additional MCG bearers with NR
PDCP (M8007C18/19)

25 © Nokia 2018
NVL00024 – MCG ERAB Setup Due to Incoming HO (M8006C21/22)

CAS-230696-C0B5: FL19_IW: MCG ERAB setup SR due to incoming HO Accessibility >100 %

26 © Nokia 2018
NVL00024 The number of Downlink Carrier Aggregation SCell full releases due to
SCG split bearer activation (M8011C292 / 293)
DL_CA_SCELL_DECONFIG_SUCC_SCG (M8011C293)|DL_CA_SCELL_DECONFIG_ATT_SCG (M8011C292)

Counters are updated upon SCell full release attempt/success performed by the eNB for a UE with Carrier Aggregation due to an SCG split
bearer activation.
CA activity for 5G device is enabled after LTE4575 is activated after May14th).
27 © Nokia 2018
NVL00024: SgNB Addition Preparation Success Rate
LTE6631a_SgNB_Addition_Preparation_Success_Rate_5G18A|SCG_ADD_PREP_ATT (M8080C0)

These counters are introduced by LTE4088.

28 © Nokia 2018
Summary

29 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
Summary

This feature works as designed to support the following new functions.

• Support for B1 measurements to allow for dynamic triggering of EN-DC bearer setup
• B1 measurements configured for cases of UE entering cell (ICS/HO) and E-RAB bearer setup
• B1 measurements deconfigured after successful SgNB addition
• B1 measurements re-established after SgNB release N

• Support for multiple NR-PDCP bearers setup during Initial Context Setup procedure based on PM counters.

• Support for incoming inter-eNB handover (including inter-RAT HO) with one or more EN-DC eligible bearer(s) that
are configured as NR-PDCP bearer(s). Upon HO completion target eNB, triggers EN-DC setup.

• Support for incoming intra-eNB handover with one or more NR PDCP bearer(s) that are configured as NR-PDCP
bearer(s). Upon HO completion target eNB, triggers EN-DC setup.

• MCG bearer set up PM counters for initial and additional ERAB or DRB work as expected.
• FIG_SUCC_SCG (M8011C293)|DL_CA_SCELL_DECONFIG_ATT_SCG (M8011C292)

30 © Nokia 2018
 BACKUP SLIDES

31 © Nokia 2018
LTE4193 Dynamic trigger for LTE-NR Dual Connectivity
(DC) Option 3X
Feature Details

32 © Nokia 2018 Customer Confidential

Technical details
B1-NR Measurements

To be able to perform successfully the B1 measurements, gNB and eNB must be phase synched (i.e. only synchronous
dual-connectivity mode is supported) (btsSyncMode must be set to 'PhaseSync')
• All target neighboring gNB cells must have compatible SSB timing configuration (i.e. fit a superset SSB timing
configuration provisioned via O&M)
• SSB duration must be 4 SF or less
• Only gap pattern 0 will be supported

An additional requirement is that·LTE1130 Dynamic PUCCH allocation must be activated

• LTE4193 introduces B1-NR measurement which require LTE measurement gaps that are aligned with SSB timing and
duration on 5G NR side. This requires dynamic PUCCH (re)allocation that would favor such measurement gaps.
• LTE1130 allows dynamic PUCCH re-allocation e.g. after RRC Connection Setup, during
RRCConnectionReconfiguration for ICS. Without LTE1130, dynamic PUCCH allocation will not be possible and thus
measurement gap allocation for B1-NR measurement would fail.

33 © Nokia 2018 Customer Confidential

EN-DC MG + PUCCH resources allocation to an UE

1. Upon detection that the UE is EN-DC eligible (e.g. EN-DC feature flag is activated, UE is EN-DC capable…), the MG allocation
algorithm is called.
2. The algorithm runs once during the lifetime of the call to determine if EN-DC MG would later be possible or not (no late run-
time EN-DC MG reconfiguration shall be supported with LTE4193):
3. it returns the gapOffset for EN-DC measurement gap and optionally, an alternative set of PUCCH resources that would be
compatible with EN-DC MG
4. UE state Control shall store this “EN-DC MG eligibility” result along with the gapOffset for future use.
5. The BM would reconfigure the UE with whatever resulting PUCCH resources
6. In case that the UE is “EN-DC MG eligible”, then whenever a gap is required, be it for EN-DC, or for legacy purpose such as
inter-freq, UEC shall return the gap information that was previously stored.
7. An exception to this rule is LTE1638 (RSTD MG). If triggered with emergency QCI1, the PUCCH resources and measurement gap
can be run-time reconfigured) but once completed, there’s no reconfiguration back to EN-DC.
8. In case that the UE is not “EN-DC MG eligible”, then when the gap for legacy purpose such as inter-freq kicks in, the legacy gap
determination shall be run

Note: if no resources satisfying EN-DC MG constraint is found, then legacy algorithm would apply. The higher layer would also be
informed that the UE is not eligible for EN-DC MG (i.e. perform B1 NR measurements without MG)

34 © Nokia 2018 Customer Confidential

Technical Details
Multiple NR PDCP MCG bearer(s) establishment within INITIAL CONTEXT SETUP
1. Upon reception of S1AP: INTIAL CONTEXT SETUP REQUEST from the MME with EN-DC QCI MeNB performs admission control for the
requested bearers.
2. If Handover Restriction List IE was contained in S1AP: INTIAL CONTEXT SETUP REQUEST, MME does not resticted NR usage
3. If NR UE Security Capabilities IE was contained in S1AP: INTIAL CONTEXT SETUP REQUEST, the MeNB shall store this IE in UE Context for
further usage in EN-DC connectivity establishment
4. Optionally if UE Capabilities for EUTRA or EUTRAN_NR MRDC Capabilities and/or NR Capabilities are missing in S1AP: INTIAL CONTEXT SETUP
REQUEST, MeNB shall try to retrieve those capabilities from UE using RRC:UECapabilityEnquiry message. Retrieved capabilities are forwarded
to MME with S1AP: UE CAPABILITY INFO INDICATION message.
5. The MeNB performs radio configuration as per the RLC and PDCP profiles (for EN-DC QCI DRBs eNB shall configure NR PDCP within
radioBearerConfig and omit LTE PDCP Config from radioResourceConfigDedicated) and sends a RRC: RRCConnectionReconfiguration to the
UE.
6. When UE acknowledges the radio configuration with RRC: RRCConnectionReconfigurationComplete, the MeNB sends a S1AP: INITIAL CONTEXT
SETUP RESPONSE to the MME.
Outcome:
• S1AP: INITIAL CONTEXT SETUP RESPONSE message is sent to the MME with requested QCIs bearer setup.
• One or more MCG Bearers with EN-DC QCI is served by LTE with NR PDCP, other bearers are configured with LTE PDCP.
• Optionally SgNB addition is triggered subsequently

35 © Nokia 2018 Customer Confidential

Technical details
Multiple NR PDCP MCG bearer(s) establishment during inter-eNB incoming HO
1. Upon receipt of S1AP: HANDOVER REQUEST from the MME or Upon receipt of X2AP:HANDOVER REQUEST from source eNB with EN-DC QCI,
target MeNB performs admission control for the requested bearers.
2. If Handover Restriction List IE was contained in HANDOVER REQUEST, MME does not restricted NR usage
3. If NR UE Security Capabilities IE was contained in HANDOVER REQUEST, the target MeNB shall store this IE in UE Context for further usage in
EN-DC connectivity establishment
4. The target MeNB build HANDOVER COMMAND message and send it to source eNB
- radio configuration as per the RLC and PDCP profiles (for EN-DC QCI DRBs eNB shall configure NR PDCP within radioBearerConfig and omit
LTE PDCP Config from radioResourceConfigDedicated),
- ‘fullconfig’ IE shall be set to ‘true’
- SCG configuration is released if any (i.e. the SCG split bearer if exist is changed back to MCG bearer )
5. Source eNB send RRC: RRCConnectionReconfiguration (HANDOVER COMMAND information encapsulated in it) to the UE.
6. UE connected to the target eNB and send out RRCConnectionReconfigurationComplete message. Handover is completed as for legacy
functionality.
7. Optionally if UE Capabilities for EUTRAN_NR MRDC Capabilities and/or NR Capabilities are missing in HANDOVER REQUEST, target eNB shall try
to retrieve those capabilities from UE using RRC:UECapabilityEnquiry message.
Outcome:
• One or more MCG Bearers with EN-DC QCI are served by target eNB with NR PDCP, other bearers are configured with LTE PDCP.
• Optionally SgNB addition is triggered subsequently
36 © Nokia 2018 Customer Confidential
Technical details
Multiple NR PDCP MCG bearer(s) establishment during intra-eNB reestablishment
1. UE observes Radio link failure, performs cell selection and chooses a Cell of the serving/source eNodeB.
2. UE requests RRC Re-Establishment towards the Cell
3. as per legacy functionality, the RRC Connection Re-establishment procedure is finished and PDCP type of each bearer is kept as before.
4. eNB receives RRC CONNECTION RE-ESTABLISHMENT REQUEST from UE, and UE context identification and authentication check are passed as
per LTE4088.
5. When building RrcConnectionReconfiguration message and send it to UE, Enb shall apply following
1. If Handover Restriction List IE was contained in UE context, MME does not resticted NR usage
2. If NR UE Security Capabilities IE was contained in HANDOVER REQUEST, the MeNB shall store this IE in UE Context for further usage in EN-
DC connectivity establishment
6. UE send out RRCConnectionReconfigurationComplete message.
Outcome:
• Intra-eNB reestablishment procedure is completed successfully
• One or more MCG Bearers with EN-DC QCI are still served by eNB with NR PDCP, other bearers are configured with LTE PDCP.

37 © Nokia 2018 Customer Confidential

Technical details
Multiple NR PDCP MCG bearer(s) establishment during E-RAB SETUP procedure
1. Upon receipt of S1AP: E-RAB SETUP REQUEST from the MME with EN-DC QCI, MeNB performs admission control for the requested bearers
2. If Handover Restriction List IE stored in UE context indicate that MME does not resticted NR usage
3. The MeNB performs radio configuration as per the RLC and PDCP profiles (for EN-DC QCI DRBs eNB shall configure NR PDCP within
radioBearerConfig and omit LTE PDCP Config from radioResourceConfigDedicated) and sends a RRC: RRCConnectionReconfiguration to the
UE.
4. When UE acknowledges the radio configuration with RRC: RRCConnectionReconfigurationComplete, the MeNB sends a S1AP: E-RAB SETUP
RESPONSE to the MME.

Outcome:
• S1AP: E-RAB SETUP RESPONSE message is sent to the MME with requested QCIs bearer setup.
• One or more MCG Bearers with EN-DC QCI is served by LTE with NR PDCP, other bearers are configured with LTE PDCP.
• CA configuration is not impacted by NR-PDCP bearer establishment.
• Optionally SgNB addition is triggered subsequently

38 © Nokia 2018 Customer Confidential

Technical details
UE enters cell with EN-DC eligible bearer – coverage Based trigger (1/2)
1. UE enters cell via Initial Context Setup, Incoming HO or Reestablishment with one or more EN-DC QCI bearers eligible for NR-PDCP
configuration.
2. eNB successfully allocates measurement gap for B1-NR measurements, given the SSB timing configuration and PUCCH resource allocation
3. eNB prepares measurement configuration for B1 measurement for NR frequencies configured in eNB and for which eNB has received
information from neighbor NR cells
- b1-ThresholdNR shall be set to RSRP or RSRQ value based on parameter setting
- reportAmount shall be set to 1
- Measurement gap shall be configured to gp0
4. eNB includes the measurement configuration for B1-NR event in same RRCConnectionReconfiguration that is sent for Initial Context Setup. In
case of Incoming HO and Reestablishment, it will be included in RRCConnectionReconfiguration sent for measurement configuration
- B1-NR measurement for NR frequencies is activated at the UE
5. eNB receives B1-NR measurement report from UE
6. eNB creates a list of NR candidate cells based on strength (measurement quantity used for B1-NR measurement) for which X2(gNB) link is
active with each unique gNB among the list of cells. eNB selects the strongest candidate NR cell from the list and sends the list of candidate
NR cells belonging to the same gNB of the strongest candidate NR cell chosen, in the X2AP: SgNB Addition Request.

39 © Nokia 2018 Customer Confidential

Technical details
UE enters cell with EN-DC eligible bearer - coverageBased trigger (2/2)
7. SgNB Addition Procedure same as in LTE4088
8. eNB shall store any further B1-NR Measurement Report messages received from the UE during SgNB addition procedure.
9. after receiving X2AP: SGNB ADDITION REQUEST ACKNOWLEDGE, eNB shall deactivate B1-NR measurement, if activated at the UE, in the same
RRCConnectionReconfiguration message for EN-DC configuration. Measurement gap will be released
Outcome:
• SgNB addition procedure is successfully completed to the strongest NR cell selected by eNB based on B1-NR measurement report
• B1-NR measurement is deactivated at the UE and measurement gap has been released, unless some other inter-frequency/inter-RAT
measurement that requires measurement gap is still active at the UE
• SCG Split Bearer is established with the chosen NR cell. In case of multiple NR-PDCP bearers, the NR-PDCP bearer for SCG Split bearer is
chosen per LTE4088 implementation
Exceptions:
• if measurement gap allocation fails, eNB shall still configure B1-NR measurement and proceed with E-RAB setup in
RRCConnectionReconfiguration message to UE ( eNB may or may not recieve any B1-NR measurement reports from the UE)
• For "coverageBased" method, if X2(GNB) link of all candidate NR cells included in measurement report are not available, then EN-DC addition
will not be attempted until next B1-NR measurement report is received.

40 © Nokia 2018 Customer Confidential

Technical Details
UE enters cell with EN-DC eligible bearer – SgNB addition failure
1. eNB receives B1-NR measurement report from UE with more than one candidate NR cells
2. eNB selects the strongest NR candidate from B1-NR measurement report, for which X2(gNB) link is active. If X2(gNB) link is not active for the
strongest NR candidate, then the next strongest NR candidate in the list is chosen. This selection is repeated until an NR cell is chosen for
which X2(gNB) link is active.
3. MeNB starst preparation of EN-DC connectivity operation for UE, by sending X2AP: SGNB ADDITION REQUEST message to SgNB with all the NR
candidate cells selected based on B1-NR measurement report that belong to same SgNB, and MeNB shall start timer T_DC_Prep.
- eNB shall store any further B1-NR Measurement Report messages received from the UE
- SgNB does not respond with X2AP: SGNB ADDITION REQUEST ACKNOWLEDGE message and T_DC_Prep expires; or SgNB reject the X2AP:
SGNB ADDITION REQUEST.
4. eNB releases SgNB resources (as in LTE4088)
5. eNB selects the next set of eligible candidates that belong to another gNB, from B1-NR measurement report and attempt another SgNB
addition. In case of SgNB addition failure again, eNB shall do this until all eligible candidates are exhausted in the list.
Outcome:
• SgNB addition procedure is successfully completed to one of the NR cells reported by the UE in B1-NR measurement report
• SCG Split Bearer is established with the chosen NR cell. In case of multiple NR-PDCP bearers, the NR-PDCP bearer for SCG Split bearer is
chosen per implementation

41 © Nokia 2018 Customer Confidential

Technical Details
Initial Context Setup with EN-DC and coverage based trigger - without MG

Initial Context Setup - bearer with NR-PDCP configured - default NR cell exists - SgNB Addition
• LTE4193 is NOT activated at cell level (either actDynTrigLteNrDualConnectivity is set to FALSE or lcrId of LNCEL is
NOT provided in any of NRDCDPR/NRDCPR while actDynTrigLteNrDualConnectivity is set to TRUE)
• the parameter LNCEL/defaultLnRelGnbCellId is initialized and points to existing LNCEL/LNRELGNBCELL object which
refers to NR cell
Description
• UE enters cell of eNB (RRC Connection Setup procedure) and eNB starts X2AP SgNB Addition procedure (interactions
with gNB, UE and MME happen)
Outcome:
• SgNB addition procedure is successfully completed to default NR cell.
• SCG Split Bearer is established with the chosen NR cell. In case of multiple NR-PDCP bearers, the NR-PDCP bearer for
SCG Split bearer is chosen per implementation

42 © Nokia 2018 Customer Confidential

Technical Details
Initial Context Setup with EN-DC and coverage based trigger - without MG

Initial Context Setup - bearer with NR-PDCP configured - no default NR cell exists – no SgNB Addition
• LTE4193 is NOT activated at cell level (either actDynTrigLteNrDualConnectivity is set to FALSE or lcrId of LNCEL is
NOT provided in any of NRDCDPR/NRDCPR while actDynTrigLteNrDualConnectivity is set to TRUE)
• the parameter LNCEL/defaultLnRelGnbCellId is NOT initialized
Description
• UE enters cell of eNB (RRC Connection Setup procedure)
• eNB does not start X2AP SgNB Addition procedure
Outcome:
• NB configures the NR-PDCP configuration
• SCG Split Bearer is not established. UE stays in LTE.

43 © Nokia 2018 Customer Confidential

LTE4193 Dynamic trigger for LTE-NR Dual Connectivity
(DC) Option 3X
Configuration Parameters

44 © Nokia 2018 Customer Confidential

Configuration management
Definition of 'EN-
'EN-DC functionality is enabled'

If all the following conditions are met for a cell, then dynamic EN-DC functionality is thought as ‘enabled’ for this specific
cell:
• parameter actDynTrigLteNrDualConnectivity is set to 'true' (dynamic trigger for EN-DC is activated (LTE4193-B)).
• Either of the following conditions is satisfied:
- The lcrId of this cell is configured in dynTriggerLteNrDcConfList of either NRDCPR or NRDCDPR
- lcrId of dynTriggerLteNrDcConfList in NRDCDPR is set to special value of -1 (all cells)

• parameter method of corresponding dynTriggerLteNrDcConfList from above step is set to 'coverageBased'

If one of following conditions is met for a cell, then EN-DC functionality is thought as ‘enabled’ for this specific cell:
• If dynamic EN-DC functionality is enabled, OR
• If dynamic EN-DC functionality is NOT enabled, parameter actLteNrDualConnectivity is set to ‘true’, parameter
defaultLnRelGnbCellId is configured

Otherwise, EN-DC functionality is thought as 'disabled' for this specific cell.

45 © Nokia 2018 Customer Confidential

Configuration management
MOCs and parameters (1/3)

LTE4193 configuration management involves the following parameters:

Activation flag • MRBTS/LNBTS/NRDCPR/nrDcPrId

• MRBTS/LNBTS/actDynTrigLteNrDualConnectivity • MRBTS/LNBTS/LNCEL/defaultLnRelGnbCellId
• MRBTS/LNBTS/LNCEL/LNRELGNBCELL/lnRelGnbCellId
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig
New attributes to NR EN-DC profile
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/ssbSubcarrierSpacing
MRBTS/LNBTS/NRDCDPR
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/ssbPeriodicity
Attributes:
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/ssbOffset
• MRBTS/LNBTS/NRDCPR/nrDcQuantityConfig
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/ssbDuration
• MRBTS/LNBTS/NRDCPR/nrDcQuantityConfig/quantityConfigId
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/quantityConfigId
• MRBTS/LNBTS/NRDCPR/nrDcQuantityConfig/filterCoefficientRsrq
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/hysB1ThresholdRsrq
• MRBTS/LNBTS/NRDCPR/nrDcQuantityConfig/filterCoefficientRsrp
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/hysB1ThresholdRsrp
• MRBTS/LNBTS/NRDCPR/dynTriggerLteNrDcConfList
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/carrierFreqNrCell
• MRBTS/LNBTS/NRDCPR/dynTriggerLteNrDcConfList/method
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/freqBandIndicatorNR
• MRBTS/LNBTS/NRDCPR/dynTriggerLteNrDcConfList/lcrId

46 © Nokia 2018 Customer Confidential

• +
Configuration management
MOCs and parameters (2/3)

LTE4193 configuration management involves the following parameters:

New parameters
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/b1TriggerQuantity
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/b1TimeToTriggerRsrq
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/b1TimeToTriggerRsrp
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/b1ThresholdNrRsrq
• MRBTS/LNBTS/NRDCPR/nrDcMeasConfig/b1ThresholdNrRsrp

47 © Nokia 2018 Customer Confidential

Configuration management
MOCs and parameters (1/3)

LTE4193 configuration management involves the following parameters:

New attributes to default NR profile • MRBTS/LNBTS/NRDCDPR/dlPathlossChg

MRBTS/LNBTS/NRDCDPR • MRBTS/LNBTS/NRDCDPR nrDcMeasConfig

Attributes: • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/ssbSubcarrierSpacing

• MRBTS/LNBTS/NRDCDPR/cAggrLteNrDcCellList • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/ssbPeriodicity

• MRBTS/LNBTS/NRDCDPR/nrDcQuantityConfig • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/ssbOffset

• MRBTS/LNBTS/NRDCDPR/nrDcQuantityConfig/quantityConfigId • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/ssbDuration

• MRBTS/LNBTS/NRDCDPR/nrDcQuantityConfig/filterCoefficientRsrq • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/quantityConfigId

• MRBTS/LNBTS/NRDCDPR/nrDcQuantityConfig/filterCoefficientRsrp • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/hysB1ThresholdRsrq

• MRBTS/LNBTS/NRDCDPR/dynTriggerLteNrDcConfList • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/hysB1ThresholdRsrp

• MRBTS/LNBTS/NRDCDPR/dynTriggerLteNrDcConfList/method • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/carrierFreqNrCell

• MRBTS/LNBTS/NRDCDPR/dynTriggerLteNrDcConfList/lcrId • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/b1TriggerQuantity

• MRBTS/LNBTS/NRDCDPR nrDcDPrId • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/b1TimeToTriggerRsrq

• MRBTS/LNBTS/NRDCDPR tProhibitPhr • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/b1TimeToTriggerRsrp

• MRBTS/LNBTS/NRDCDPR/tPeriodicPhr • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/b1ThresholdNrRsrq

48 © Nokia 2018 Customer Confidential • MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig/b1ThresholdNrRsrp

LTE4193 Dynamic trigger for LTE-NR Dual Connectivity
(DC) Option 3X
Performance counters & Alarms

49 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
New/related counters

• M8006C332 Number of Initial MCG E-RAB Setup attempts with NR PDCP

- This counter provides the number of establishment attempts of initial MCG bearer with NR PDCP. Each bearer, which is eligible to be an
MCG bearer with NR PDCP, of the "E-RAB to be Setup List" IE is counted.
- This counter is updated by the number of MCG bearers with NR PDCP in the "E-RAB to be Setup List" IE, within the following message:
S1AP: INITIAL CONTEXT SETUP REQUEST.
- Aggregation Dimension: LNBTS, LNCEL
• M8006C333 Number of Initial MCG E-RAB Setup successes with NR PDCP
- This counter provides the number of successful establishments of initial MCG bearer with NR PDCP. Each MCG bearer of the "E-RAB Setup
List" IE established with NR PDCP is counted.
- This counter is updated by the number of MCG bearers with NR PDCP in the "E-RAB Setup List" IE, within the following message: S1AP:
INITIAL CONTEXT SETUP RESPONSE.
- Aggregation Dimension: LNBTS, LNCEL
- Aggregation Dimension: LNBTS, LNCEL

50 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
New/related counters

• M8007C16 Number of DRB establishment attempts of initial MCG bearers with NR PDCP
- This counter provides the number of DRB establishment attempts for an MCG bearer with NR PDCP after Initial Context Setup Request
was received from the MME.
- This counter is updated by the number of initial DRBs each time the eNB tries to establish with the UE a DRB for an MCG bearer with NR
PDCP, within the following message: RRC Connection Reconfiguration. Note: This is only related to a situation when previously S1AP:
Initial Context Setup Request was received from the MME.

• M8007C17 Number of successful DRB establishments of initial MCG bearers with NR PDCP
- This counter provides the number of successful DRB establishments for an MCG bearer with NR PDCP after Initial Context Setup Request
was received from the MME.
- This counter is updated by the number of established initial DRBs with NR PDCP, within the following message: RRC Connection
Reconfiguration Complete. Note: This is only related to a situation when previously S1AP: Initial Context Setup Request was received from
the MME.
- Aggregation Dimension: LNBTS, LNCEL

51 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
New/related counters

• M8007C18 Number of DRB establishment attempts of additional MCG bearers with NR PDCP
- This counter provides the number of DRB establishment attempts for an MCG bearer with NR PDCP after E-RAB Setup Request was
received from the MME.
- This counter is updated by the number of additional DRBs each time the eNB tries to establish with the UE a DRB with NR PDCP, within
the following message: RRC Connection Reconfiguration. Note: This is only related to a situation when previously S1AP: E-RAB Setup
Request was received from the MME.
- Aggregation Dimension: LNBTS, LNCEL
• M8007C19 Number of successful DRB establishments of additional MCG bearers with NR PDCP
- This counter provides the number of successful DRB establishments for an MCG bearer with NR PDCP after E-RAB Setup Request was
received from the MME.
- This counter is updated by the number of established additional DRBs with NR PDCP, within the following message: RRC Connection
Reconfiguration Complete. Note: This is only related to a situation when previously S1AP: E-RAB Setup Request was received from the
MME.
- Aggregation Dimension: LNBTS, LNCEL

52 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
New counters

• M8006C19 Number of establishment attempts of additional MCG bearers with NR PDCP

- The number of establishment attempts of additonal MCG bearers with NR PDCP. Each bearer, which is eligible to be an MCG bearer with
NR PDCP, of the "E-RAB to be Setup List" IE is counted.
- This counter is updated by the number of MCG bearers with NR PDCP in the "E-RAB to be Setup List" IE, within the following message:
S1AP: E-RAB SETUP REQUEST.
- Aggregation Dimension: LNBTS, LNCEL
• M8006C20 Number of successful establishments of additional MCG bearers with NR PDCP
- The number of successful establishments of additional MCG bearers with NR PDCP. Each MCG bearer of the "E-RAB Setup List" IE
established with NR PDCP is counted.
- This counter is updated by the number of MCG bearers with NR PDCP in the "E-RAB Setup List" IE, within the following message: S1AP: E-
RAB SETUP RESPONSE.
- Aggregation Dimension: LNBTS, LNCEL

53 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
New counters

• M8006C21 The number of establishment attempts of MCG bearers with NR PDCP due to an incoming handover
- The number of establishment attempts of MCG bearers with NR PDCP due to an incoming handover. Each bearer, which is eligible to be an
MCG bearer with NR PDCP, is counted.
- Updated: This counter is updated by the number of MCG bearers each time the eNB tries to establish with the UE an MCG bearer with NR
PDCP due to an incoming handover, after the following messages: Handover Request or internal message in case of Intra-eNB HO. Note:
Intra-cell HO cases are not counted.
- Aggregation Dimension: LNBTS, LNCEL
• M8006C22 The number of successful establishments of MCG bearers with NR PDCP due to an incoming handover
- The number of successful establishments of MCG bearers with NR PDCP due to an incoming handover. Each MCG bearer established with
NR PDCP is counted. Note: This counter is also incremented due to a re-establishment in an unprepared cell or a re-establishment in the
target cell during ongoing handover procedure.
- This counter is updated by the number of established MCG bearers with NR PDCP due to an incoming handover, after the following
messages: RRC Connection Reconfiguration Complete. Note: Intra-cell HO cases are not counted.
- Aggregation Dimension: LNBTS, LNCEL

54 © Nokia 2018 Customer Confidential

LTE4193 Dynamic Trigger for LTE-
LTE-NR DC Option 3X
New counters

• M8011C292 The number of attempts for Downlink Carrier Aggregation SCell full releases due to SCG split bearer
activation
- This counter shows the number of attempts for Downlink Carrier Aggregation SCell full releases due to SCG split bearer activation.
- Counter update: upon SCell full release attempt performed by the eNB for a UE with Carrier Aggregation due to an SCG split bearer
activation.
- Aggregation Dimension: LNBTS, LNCEL

• M8011C293 The number of successful Downlink Carrier Aggregation SCell full releases due to SCG split bearer
activation
- This counter shows the number of successful Downlink Carrier Aggregation SCell full releases due to SCG split bearer activation.
- Counter update: upon SCell full release success received by the eNB for a UE with Carrier Aggregation due to an SCG split bearer
activation.
- Aggregation Dimension: LNBTS, LNCEL

55 © Nokia 2018 Customer Confidential