Feature Performance Assessment (FPA)

5GC002199 Inter-Frequency mobility (NSA option 3x) with

MeNB coordination
LTE5227 SgNB initiated coordination of NR measurements

GS/CS/NWA-C
• Version : 1.0
• Date : 26/11/2020
• Authors : Hervé-Julien MAJCHER/ Sundar Venugopalan (AT&T CS support)
• Status : Release
1 © Nokia 2020
FPA – 5GC002199 Inter-Frequency mobility (NSA option 3x) with MeNB coordination
LTE5227 SgNB initiated coordination of NR measurements
Table of contents

Overview & Validation Performance Main KPI non- Restrictions &

Expected Strategy Results regression Issues
Benefits Analysis

Conclusion Feedback to References

R&D

2 © Nokia 2020
FPA – 5GC002199 Inter-Frequency mobility (NSA option 3x) with MeNB coordination
LTE5227 SgNB initiated coordination of NR measurements

Overview &
Expected Benefits
Table of contents

3 © Nokia 2020
Introduction
Mobility in Non standalone (option 3x)

5GC000572 Intra-Frequency 5GC000573 Intra-Frequency Inter-gNB

Intra gNB mobility (NSA option mobility (NSA option 3x)
3x)
LTE4530 Inter-SgNB Mobility for LTE-
NR DC Option 3X
Intra-NR
5GC001094 Intra-Frequency Intra-DU
Intra - Frequency gNB mobility (NSA option 3x)

5GC001095 Inter-Frequency 5GC002199 Inter-Frequency

mobility (NSA option 3x) mobility (NSA option 3x) with
without MeNB coordination MeNB coordination
Intra-NR
Inter - Frequency LTE5227 SgNB initiated co-
ordination of NR measurements

5GC000575 Intra-MeNB LTE 5GC000574 Inter-MeNB LTE

handover without gNB change handover without gNB change

Intra-LTE LTE4281 LTE connected mobility LTE5348 Inter-eNB handover for

(Intra/Inter - Frequency) for LTE-NR DC option 3x LTE-NR DC option 3X

4 © Nokia 2020
Introduction
Inter frequency PSCell change for NSA (Option 3x)
S1 (CP and UP)
X2 (CP and UP) • Inter frequency Handover support for gNB in NSA mode has
F1 (CP and UP)
S1-UP been introduced with 5GC001095 feature, but with some
EPC MeNB
limitations due to SgNB coordination of Measurement Gaps
(MG) configuration:
− Independent measurement gap capable UE only,

Source en-gNB Target en-gNB − HO possible from FR1 to FR2 (MG configuration not needed) or from
CU#1 CU#2 FR2 to FR2 (FR2 MG configuration needed)*.
• The feature 5GC002199 (with counterpart LTE5227) removes
above limitations by introducing support of MeNB
coordination of MG configuration.
SgNB
SgNB eNB#1
DU#1.1
DU#1.1
SgNB • When coordinated by MeNB, common MG pattern for FR1
DU#2.1
f1 f2 and FR2 can be used, thus inter frequency HO is no longer
f3 f4
2.2.1
limited by frequency of source / target cell.

intra en-gNB • Similarly to 5GC001095, inter frequency HO procedure is

intra DU inter en-gNB based on A1, A2 and A3/A5 events triggered by SS-
RSRP/SS-RSRQ measurements.
intra en-gNB
inter DU
*Frequency Ranges (TS 38.101):
FR1: 410 MHz – 7125 MHz
FR2: 24250 MHz – 52600 MHz
5 © Nokia 2020
Technical Details 5GC
00
refre 1095
Inter frequency measurements lifecycle s h er
Start point
• All events are based on SS-RSRP/SS-RSRQ (or combined) measurements
• Trigger point to start inter frequency measurement is A2 event. SgNB Addition
procedure
• When A2 event is reported, the UE is being configured with inter freq.
A3/A5/A3&A5 and A1 measurements according to the configuration. A2 measurement
configuration
• A1 measurement, configured together with the A3 and/or A5, is used for
terminating inter freq. A3/A5 measurements. A2 measurement
• When radio conditions become better and UE reports A1 event, it is A2 event reported
reconfigured with A2 measurement again. A1 event Reconfiguration to
reported A1, A3, A5 measurements
• If event A3 or A5 or A3&A5 (depending on a configuration) is reported,
HO procedure is triggered.
A1, A3, A5
• After HO execution, UE is attached to a new (target) cell and reconfigured measurements
with A2 measurement again.
A3 / A5 event reported
HO decision

Event A1: Serving becomes better than threshold HO execution

Event A2: Serving becomes worse than threshold
Event A3: Neighbor becomes offset better than serving
Event A5: Serving becomes worse than threshold1 and neighbor becomes better
than threshold2
6 © Nokia 2020
 Technical Details
Measurement Gaps

• Idea of Measurement Gaps (MG) is to retune UE for a small period of time (gap) to different Frequency Ranges:
frequency in order to measure neighbor cells for inter-frequency mobility purposes. During MG FR1: 410 MHz – 7125 MHz
intervals gNB does not schedule data for the UE. FR2: 24250 MHz – 52600 MHz

• For 5G cells there are two frequency ranges defined: sub 6GHz (FR1) and millimeter wave (FR2). 5G Reference – TS 38.101
UE can support independent MG pattern for different FR or not:
− Per-FR MG – UE is able to monitor each FR independently. FR1 measurements are coordinated by MeNB,
while FR2 measurements by SgNB. (FR2 measurements → 5GC001095)
− Per-UE MG – UE is capable of one MG pattern for both FRs, thus MeNB coordination is required for any
inter frequency measurements (FR1 or FR2). (Covered by 5GC002199 & LTE5227)

• UE MG capability is indicated in UE-MRDC-Capability Information Element IE/Group Name

UE-MRDC-Capability
• 5GC002199 requires MG to be coordinated by MeNB. It can be either independent FR1
>measAndMobParametersMRDC
measurement (per-FR1) or measurement with common pattern (per-UE), however LTE5227
supports per-UE case only. >>measAndMobParametersMRDC-Common
>>>independentGapConfig = SUPPORTED

7 © Nokia 2020
Technical Details
Measurement Gap parameters

There are four parameters that determine a measurement gap configuration. For 5GC02199, these parameters are configured on
LTE site (LTE5227):
• Measurement Gap Length:
- Allowed values [ms]: 1.5, 3, 3.5, 4, 5.5, 6
• Measurement Gap Repetition Period:
- Allowed values [ms]: 20, 40, 80, 160
• Measurement Gap Timing Advance:
- Allow the UE to retune to/from the measured frequency before/after the SMTC (SSB Measurement Timing Configuration) window
- Allowed values [ms]: 0, 0.25, 0.50
• Gap Offset:
- Value of gapOffset is the offset with which gaps have to be started in terms of SFN (System Frame Number).
- The value range is from 0 to mgrp -1
MGTA MGRP

First subframe of the gap MGL

8 © Nokia 2020
Deployment Aspects
Feature activation

The feature is activated in the same way as 5GC001095 with two activation flags:
MRBTS.NRBTS.actInterFreqInterGnbMobilityNsa
MRBTS.NRBTS.actInterFreqIntraGnbMobilityNsa
The first flag is for Inter gNB inter-freq. mobility, while the second one is for Intra gNB inter-freq. mobility.
Depending on needs, the flags can be activated together or separately.
• Neighbor relations between inter frequency 5G cells are using same object class as used for intra frequency mobility
(MRBTS.NRBTS.NRCELL.NRREL). Up to 256 NRREL instances per NR cell configured.
• Additionally, per-frequency layer measurement parameters (thresholds etc.) needs to be configured with NRHOIF object
(MRBTS.NRBTS.NRCELL.NRHOIF). Up to 7 NRHOIF instances per cell can be created.
• As a trigger for start / stop A3 or A5 measurements are events A2 and A1, these events have to be configured as well with all
relevant parameters:
 MRBTS.NRBTS.NRCELL.a1MeashoEnabled
 MRBTS.NRBTS.NRCELL.a2MeashoEnabled

• Additionally, LTE5227 needs to be activated on MeNB.

9 © Nokia 2020
 Deployment Aspects
NRHOIF objects for 5G Inter frequency HO configuration
NR inter frequency measurement parameters are defined per layer with NRHOIF object class (MRBTS/NRBTS/NRCELL)
• Each NRHOIF instance defines one target frequency layer with SSB related parameters and measurement (A3 and A5) configuration
used for this layer.
• Up to 7 NRHOIF objects can be created per 5G NRCELL object (1 radio cell – can be multiple NRCELLs per DU)

MRBTS/NRBTS/NRCELL/NRHOIF/nrhoifId ID of the NRHOIF

MRBTS/NRBTS/NRCELL/NRHOIF/nrhoifId instance NRHOIF objects are
MRBTS/NRBTS/NRCELL/NRHOIF/freqBandIndicatorNR
MRBTS/NRBTS/NRCELL/NRHOIF/nrhoifId
MRBTS/NRBTS/NRCELL/NRHOIF/freqBandIndicatorNR used for all kinds of
MRBTS/NRBTS/NRCELL/NRHOIF/cellDepType
MRBTS/NRBTS/NRCELL/NRHOIF/nrhoifId
MRBTS/NRBTS/NRCELL/NRHOIF/freqBandIndicatorNR
MRBTS/NRBTS/NRCELL/NRHOIF/cellDepType 5G-5G NSA neighbor
NRCELL: MRBTS/NRBTS/NRCELL/NRHOIF/freqBandIndicatorNR
MRBTS/NRBTS/NRCELL/NRHOIF/cellDepType relationships for inter
source cell for MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasEnabled Frequency Band
MRBTS/NRBTS/NRCELL/NRHOIF/cellDepType
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasEnabled frequency mobility
PSCell change MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasSsbRsrp associated with
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasEnabled
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasSsbRsrp purposes:
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasSsbRsrq ssbFrequency
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasEnabled
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasSsbRsrp
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasSsbRsrq 5GC001095
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasSsbRsrp
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasSsbRsrq 5GC002199
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasEnabled SA / NSA / both
MRBTS/NRBTS/NRCELL/NRHOIF/a3MeasSsbRsrq
Up to 7 MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasSsbRsrp
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasEnabled
NRHOIF MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasSsbRsrq
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasEnabled
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasSsbRsrp
per MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasEnabled
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasSsbRsrp Configuration of
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasSsbRsrq
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasSsbRsrp
NRCELL MRBTS/NRBTS/NRCELL/NRHOIF/ssbFrequency
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasSsbRsrq A3 / A5 events -
MRBTS/NRBTS/NRCELL/NRHOIF/a5MeasSsbRsrq thresholds, offsets,
MRBTS/NRBTS/NRCELL/NRHOIF/ssbFrequency
MRBTS/NRBTS/NRCELL/NRHOIF/ssBurstSetPeriod
MRBTS/NRBTS/NRCELL/NRHOIF/ssbFrequency etc.
MRBTS/NRBTS/NRCELL/NRHOIF/ssBurstSetPeriod
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbScs
MRBTS/NRBTS/NRCELL/NRHOIF/ssbFrequency
MRBTS/NRBTS/NRCELL/NRHOIF/ssBurstSetPeriod
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbScs
MRBTS/NRBTS/NRCELL/NRHOIF/numberOfTransmittedSsBlocks
MRBTS/NRBTS/NRCELL/NRHOIF/ssBurstSetPeriod
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbScs
MRBTS/NRBTS/NRCELL/NRHOIF/numberOfTransmittedSsBlocks
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbSmtcDuration
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbScs
MRBTS/NRBTS/NRCELL/NRHOIF/numberOfTransmittedSsBlocks
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbSmtcDuration Parameters specify
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbSmtcPeriodicity
MRBTS/NRBTS/NRCELL/NRHOIF/numberOfTransmittedSsBlocks
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbSmtcDuration
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbSmtcPeriodicity inter frequency
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbSmtcDuration
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbSmtcPeriodicity neighbor SSB
MRBTS/NRBTS/NRCELL/NRHOIF/ifhoSsbSmtcPeriodicity configuration.
10 © Nokia 2020
Introduction
Before & after

Before After

• MeNB does not support coordination of • Thanks to 5GC002199 and LTE5227,

Measurement Gaps for NR mobility.
• Inter frequency PSCell Handover for NSA (Option
3x) is possible, but MG has to be coordinated by
SgNB (5GC001095), thus the procedure is limited
to certain UE type (independent measurement gap
capable) and certain HO direction (FR1>FR2 or
FR2>FR2)
Measurement Gap configuration can be
coordinated by MeNB.
• Inter frequency PSCell Handover is not limited by
UE capability of independent FR measurement or
frequencies of source and target cells.

11 © Nokia 2020
FPA – 5GC002199 Inter-Frequency mobility (NSA option 3x) with MeNB
coordination
Results Overview
Activities & Results :
• Feature activated on AT&T Philly CL4 42eNB/4gNBs
• Validation strategy to analyse Enb trace to confirm that
feature is working as design
• Checking that associated PM/ KPI are working
• Checking no impact on standard NKPI

Main Benefits & Potential Costs :

• Feature 5GC002199 (with counterpart LTE5227) removes

above limitations of 5GC001095 feature by introducing
support of MeNB coordination of MG configuration
• When coordinated by MeNB, common MG pattern for FR1
Green-light recommandation : Green
and FR2 can be used, thus inter frequency HO is no longer
limited by frequency of source / target cell.
• Similarly to 5GC001095, inter frequency HO procedure is
based on A1, A2 and A3/A5 events Restrictions:

12 © Nokia 2020
FPA – 5GC002199 Inter-Frequency mobility (NSA option 3x) with MeNB coordination
LTE5227 SgNB initiated coordination of NR measurements

Validation Strategy
& Plan
Table of contents

13 © Nokia 2020
 Field
FFA cluster andEvaluation
gNBs & Key events

Features were activated in Philly on 4gNB

Key Events Related To Feature Activation

 9/23, these two features were activated on Philly CL4 42eNB/4gNBs
 9/25, some parameter setting were adjusted
 10/8, LTE5515 was disabled on two eNodeBs (re-enabled after field test).
 10/12, knife for CAS-352008-G7T1 was loaded to PAL01457 and PAL01602.
 10/16, these two features were activated on PAL01433/PAPN001433,
PAL01546/PAPN001546.

14 © Nokia 2020
 Feature Activation
Parameter Settings

15 © Nokia 2020
Feature Activation
Parameter Settings

16 © Nokia 2020
 Feature Activation

17 © Nokia 2020
FPA – 5GC002199 Inter-Frequency mobility (NSA option 3x) with MeNB coordination
LTE5227 SgNB initiated coordination of NR measurements

Performance
Results
Table of contents

18 © Nokia 2020
 •PAPN001602 10/9

Field Drive Test

Intra gNB inter frequency HO: A5 triggered from N2 to N5
•// SCG setup on N2
•20:26:23.176540 8023052752 R RRC Measurement Report [mId=18 PCell:rsrp=60(-80dBm) rsrq=24(-8dB) NeighCellNR
•rsrp=78]
pci=13
•20:26:23.180885 8023052752 S X2 SgNB Addition Request tgtCid=(mEnbId=21602,rCid=23 •) candicateCell (ssbFreq-387850)
•20:26:23.191042 8023052752 R X2 SgNB Addition Request Acknowledge [pci=13 •measObjToAddMod (moId-1,nr,ssbFreq-
•387850) rptCfgIdToAddMod(...repCfgId-2,nr,A2,a2thr_66(-90dBm) ,hyst_2,ttt_ms40,ssb,intval_ms120,...)
•measIdToAddMod(...mId-2,moId-1,repCfgId-2,...)
•...
•// A2 is received
•20:26:23.376549 8023052752 R RRC UL Information Transfer MRDC [measReport mId=2 servCellId=8
•ServCell:pci=13:rsrp=64(-92dBm) :rsrq=65(-11dB):sinr=84(19dB)]
•20:26:23.376943 8023052752 S X2 RRC Transfer [measReport mId=2 servCellId=8 ServCell:pci=13:rsrp=64(-
•92dBm) :rsrq=65(-11dB): sinr=84(19dB)]

•// Setup measGAP, A1/A5

•20:26:23.619778 8023052752 R X2 SgNB Modification Required [cause=radioNetwork:rRM-purpose]
•20:26:23.621147 8023052752 S X2 SgNB Modification Request
•20:26:23.624853 8023052752 R X2 SgNB Modification Request Acknowledge ...

•20:26:23.626238 8023052752 S RRC Connection Reconfiguration [gap-setup gapOffset=gp0_19...]

20:26:23.648463 8023052752 R RRC Connection Reconfiguration Complete [transId=1 scgConfigResp]
20:26:23.649637 8023052752 S X2 SgNB Modification Confirm [x2apId=3733 sgNbX2apId=897]

•// A5 is received
•20:26:24.076509 8023052752 R RRC UL Information Transfer MRDC [measReport mId=5 servCellId=8
•ServCell:pci=13:rsrp=65(-91dBm):rsrq=65(-11dB):sinr=92(23dB) NeighCellNR pci=13:rsrp=81(-75dBm •):rsrq=65(-
•11dB):sinr=86(20dB)]
•20:26:24.076879 8023052752 S X2 RRC Transfer

•// HO to N5, set up A2 again

•20:26:24.087813 8023052752 R X2 SgNB Modification Required [cause=radioNetwork:ho-desirable-radio-reason
•servCellIdx=8 pci=13 dl-earfch=173910-scs=kHz15-25prbs ...rptCfgIdToAddMod(repCfgId-6,nr, •A2,a2thr_86(-
•70dBm) ,hyst_2,ttt_ms40,ssb,intval_ms120...

•20:26:24.091863 8023052752 S RRC Connection Reconfiguration

20:26:24.138525 8023052752 R RRC Connection Reconfiguration Complete  A3 triggered IFHO also work from N2 to N5
20:26:24.139612 8023052752 S X2 SgNB Modification Confirm  UE hardly report A3 when it is on N5. So the IFHO is triggered by A5
19 © Nokia 2020  from N5 to N2, because of RSRP of N5 is in general higher than N2
 Field Drive Test PAPN001602 10/9

(... continue) Intra gNB inter frequency HO: N5 to N2

// A2 is received on N5
20:26:24.296475 8023052752 R RRC UL Information Transfer MRDC [measReport mId=7 servCellId=8  A3 triggered IFHO also tested. It is easy trigger from N2 to N5.
ServCell:pci=13:rsrp=81(-75dBm):rsrq=65(-11dB):sinr=92(23dB)]
20:26:24.296863 8023052752 S X2 RRC Transfer

// Setup measGAP and A1/A5

20:26:24.298506 8023052752 R X2 SgNB Modification Required
20:26:24.299508 8023052752 S X2 SgNB Modification Request
20:26:24.302788 8023052752 R X2 SgNB Modification Request Acknowledge [measObjToAddMod(moId-3,nr,
•387850,smtc1:sf20_0,smtc1Dur=sf3,thrRsrp_0,thrRsrq_0,n2) rptCfgIdToAddMod(repCfgId-
7,nr,A1,hyst_2,ttt_ms40,ssb,intval_ms120,repCfgId-8,nr,A5,hyst_1,ttt_ms320,ssb,intval_ms120)... ssbFreq-

•20:26:24.303896 8023052752 S RRC Connection Reconfiguration

•20:26:24.325459 8023052752 R RRC Connection Reconfiguration Complete
•20:26:24.326967 8023052752 S X2 SgNB Modification Confirm

•// A5 is received
•20:26:24.756541 8023052752 R RRC UL Information Transfer MRDC [measReport mId=10 servCellId=8
•ServCell:pci=13:rsrp=82(-74dBm):rsrq=65(-11dB):sinr=92(23dB) NeighCellNR pci=13:rsrp=78(-78dBm):rsrq=65(-
11dB):sinr=87(20.5dB)]

•// HO to N2, set up A2

•20:26:24.768122 8023052752 R X2 SgNB Modification Required [cause=radioNetwork:ho-desirable-radio-reason
•nrTransId=1) servCellIdx=8 pci=13 dl-earfch=386092-scs=kHz15-106prbs measObjToAddMod(moId-3,nr,ssbFreq-
•387850,smtc1:sf20_0,smtc1Dur=sf5,thrRsrp_0,thrRsrq_0,n2) rptCfgIdToAddMod(repCfgId-9,nr,A2,a2thr_66(-
•90dBm) ,hyst_2,ttt_ms40,ssb,intval_ms120) ...]
•20:26:24.772402 8023052752 S RRC Connection Reconfiguration
•20:26:24.843522 8023052752 R RRC Connection Reconfiguration Complete
•20:26:24.844667 8023052752 S X2 SgNB Modification Confirm

•// GAP-release
•20:26:24.871409 8023052752 R X2 SgNB Modification Required
20:26:24.872870 8023052752 S X2 SgNB Modification Request
•20:26:24.876053 8023052752 R X2 SgNB Modification Request Acknowledge
•20:26:24.876489 8023052752 S X2 SgNB Modification Confirm
•// Setup DRX•1 7after
© No mGAP
a 2 0 2 is released

20 © Nokia 2020
•20:26:24.879340 8023052752 R X2 SgNB Modification Required
 PAPN001602 10/12

Field Drive Test

Intra gNB inter frequency HO: N5 to N2 to N5
 Inter frequency HO between PAPN001602_N005B (PCI=13) and PAPN001602_N002B(PCI=13)

•18 © Nokia
21 2020 2020
© Nokia
 •PAPN001602 and PAPN001457 10/12

Field Drive Test

Inter-gNB inter frequency HO : N5 to N2 (1/2)
Inter frequency HO from PAPN001457_N005C (PCI=47) to PAPN001602_N002A(PCI=12)
Challenging RF: N2 RF is worse than N5.
• Settings on PAPN001457_N005C: A2 thr=-90, A5 thr1=-95, thr2=-110 Take advantage of N2 bandwidth.
• HO happened at (A5: serving N5 -107, neighbor N2 -110)

•19 © Nokia
22 20202020
© Nokia
 PAPN001602 and PAPN001457 10/12
Field Drive Test
(... continued) Inter-gNB inter frequency HO: N2 to N5 to N2

Inter frequency HO from PAPN001602_N002A (PCI=12) to PAPN001457_N005C (PCI=47)

· Settings on PAPN001602_N002A: A2 thr=-114, A5 thr1=-90, thr2=-120 Challenging RF: N2 RF is worse than N5
· HO happened at (A5: serving N2 -117, neighbor N5 -109)
Inter frequency HO from PAPN001457_N005C (PCI=47) to PAPN001602_N002A (PCI=12)
· HO happened at (A5: serving N5 -108, neighbor N2 -109)

23 © Nokia 2020
 5G20A_NRBTS_Philly_CL4_gNBs
Performance Aspects
(New Counter) Measurement GAP

· Number of Gap Pattern ID 0: The counter is updated when the LTE4981

activation LTE5227
measurement Gap Pattern Id 0 is configured.
activation
· Started pegging when LTE4981 was activated (eNB initiated).
· After LTE5227 was activated, gNB initiated MG increase, but both
threshold A2 setting and the drive tests can impact its pegging.

LTE5227
activation
LTE4981 LTE5227
activation activation

24 © Nokia 2020
 5G20A_NRBTS_Philly_CL4_gNBs

Performance
Measurement Aspects
GAP configured by NR band

25 © Nokia 2020
 5G20A_NRBTS_Philly_CL4_gNBs
Performance Aspects
Inter-frequency intra-DU HO attempt and success rates

Test on knife load

First success after

LTE5515 was disabled

26 © Nokia 2020
 Performance
(New Counter) Duration ofAspects
inter frequency HO
5G20A_NRBTS_Philly_CL4_gNBs

· The minimum/maximum duration of executed intra gNB intra DU inter frequency PS-Cell changes via MeNB. Duration is
indicated on a 0.1 millisecond level.
· Duration is counted between the CpIf: SendToMeNB message containing the X2AP: SgNB Modification Required and the CpIf:
ReceiveFromMeNB message containing the X2AP: SgNB Modification Confirm

27 © Nokia 2020
 Performance
(New Counter) Duration ofAspects
inter frequency HO
5G20A_NRBTS_Philly_CL4_gNBs

· These counters indicate the minimum/maximum/total duration of executed inter frequency SN change. Duration is
indicated on a 0.1 millisecond level.
· Duration is counted between the CpIf: SendToMeNB message containing the X2AP: SgNB
· Change Required and the CpIf: ReceiveFromMeNB message containing the X2AP: SgNB Change Confirm

28 © Nokia 2020
 5G20A_NRBTS_Philly_CL4_gNBs

Performance Aspects
(New Counter) Inter frequency HO attempt and failures

M55151C00001: Number of intra gNB inter frequency intra DU PS-Cell change attempts for NSA 3x via MeNB
M55151C00002: Number of intra gNB inter frequency intra DU PS-Cell change attempts for NSA 3x via SRB3
M55151C00003: Number of intra gNB intra-DU inter frequency PS-Cell change failures due to TDCoverall timer expiry

29 © Nokia 2020
 5G20A_NRBTS_Philly_CL4_gNBs
Performance
(New Counter)Aspects
Inter frequency HO failures

· M55151C00004: Number of intra gNB intra DU inter frequency PS-Cell change handover preparation failures due to MeNB refusal
· M55151C00005: Number of intra gNB intra-DU inter frequency PS-Cell change handover preparation failures due to target cell resource allocation failure
· M55151C00006: Number of intra gNB intra-DU inter frequency PS-Cell change failures due to T304 timer expiry
· M55151C00007: Number of intra gNB intra-DU inter frequency PS-Cell change handover preparation failures due to E1 procedure failure during HO preparation
· M55151C00007: Number of intra gNB intra-DU inter frequency PS-Cell change handover preparation failures due to F1 procedure failure.

30 © Nokia 2020
 Performance Aspects 5G20A_NRBTS_Philly_CL4_gNBs
(Existing Counter) Inter frequency HO execution attempt and failures

These counters are introduced with 5GC001630 (RAN sharing in SA and additional configuration for NSA 3x)
· M55145C00121: The number of intra-gNB inter-frequency intra-DU PS-Cell change execution attempts for NSA 3x via MeNB or via SRB3 per PLMN-ID
· M55145C00122: The number of intra-gNB inter-frequency intra-DU PS-Cell change execution failures for NSA 3x via MeNB or via SRB3 per PLMN-ID. Failures due to
TDCoverall timer expiry, MeNB refusal or T304 timer expiry.
· M55145C00123: The number of intra-gNB inter-frequency intra-DU PS-Cell change preparation failures for NSA 3x due to target cell resource allocation failure

31 © Nokia 2020
 5G20A_NRBTS_Philly_CL4_gNBs

· The drive test was done in the beta sector of

PAPN001602 on 10/9 and 10/12.
· A2 timeToTrigger was set to 40ms, there are many
inter frequency HO ping-pong between N2 and N5
NR cell.

32 © Nokia 2020
FPA – 5GC002199 Inter-Frequency mobility (NSA option 3x) with MeNB coordination
LTE5227 SgNB initiated coordination of NR measurements

Main KPI
non-regression
Analysis Table of contents

33 © Nokia 2020
 5G20A_NRBTS_Philly_CL4_gNBs

Performance Aspects
GNB Dashboard KPI: retainability, accessibility, DL and UL throughput (9/23 activation)

34 © Nokia 2020
 5G20A_NRBTS_Philly_CL4_gNBs

Performance Aspects
GNB Dashboard KPI: HO (9/23 activation)

Due to single gNB

increase. Not related
to this feature.

35 © Nokia 2020
FPA – 5GC002199 Inter-Frequency mobility (NSA option 3x) with MeNB coordination
LTE5227 SgNB initiated coordination of NR measurements

Restrictions & Issues

Table of contents

36 © Nokia 2020
Restrictions & issues
Issues Identified (NCT Tickets)
Not Applicable

37 © Nokia 2020
FPA – 5GC002199 Inter-Frequency mobility (NSA option 3x) with MeNB coordination
LTE5227 SgNB initiated coordination of NR measurements

Conclusion

Table of contents

38 © Nokia 2020
Conclusion

 Base on the large number of log analysis from drive test and PM counter analysis, these two
features’ mainly function are working as expected.
 When gN reveives A2 from UE, it initiates measurement GAP setup. The GAP parameters
are coordinated and provided by eNodeB.
 gNB sets up correct measurement types for IFHO purpose (A1, A3, A5)
 When gNB receives A3 or A5, it initiates the IFHO to N5 or N2 from the current band.
 It appear it is easy to trigger A3 when UE is on band2 and lead to N2 to N5 IFHO
 A5 can trigger UE IFH from N2 to N5 or N5 to N2
 The IFHO volume is very low on the test sites, mainly come from our test devices.
 The counters introduced by these features work as designed.

39 © Nokia 2020
NOKIA
 Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia. This document is
provided subject to confidentiality obligations of the
applicable agreement(s).
This document is intended for use of Nokia’s customers
and collaborators only for the purpose for which this
document is submitted by Nokia. No part of this
document may be reproduced or made available to the
public or to any third party in any form or means
without the prior written permission of Nokia. This
document is to be used by properly trained
professional personnel. Any use of the contents in this
document is limited strictly to the use(s) specifically
created in the applicable agreement(s) under which the
document is submitted. The user of this document may
voluntarily provide suggestions, comments or other
feedback to Nokia in respect of the contents of this
document ("Feedback"). Such Feedback may be used in
Nokia products and related specifications or other
documentation. Accordingly, if the user of this
document gives Nokia Feedback on the contents of this
document, Nokia may freely use, disclose, reproduce,
license, distribute and otherwise commercialize the
feedback in any Nokia product, technology, service,
specification or other documentation.
Nokia operates a policy of ongoing development. Nokia
reserves the right to make changes and improvements
to any of the products and/or services described in this
document or withdraw this document at any time
without prior notice.
The contents of this document are provided "as is".
Except as required by applicable law, no warranties of
any kind, either express or implied, including, but not
limited to, the implied warranties of merchantability
and fitness for a particular purpose, are made in
relation to the accuracy, reliability or contents of this
document. NOKIA SHALL NOT BE RESPONSIBLE IN ANY
EVENT FOR ERRORS IN THIS DOCUMENT or for
any loss of data or income or any special, incidental,
consequential, indirect or direct damages howsoever
caused, that might arise from the use of this document
or any contents of this document.
This document and the product(s) it describes
are protected by copyright according to the
applicable laws.
Nokia is a registered trademark of Nokia Corporation.
Other product and company names mentioned herein
may be trademarks or trade names of their respective
owners.