Lzu1431171 M6

5G RAN NR Accessibility
5G RAN NR KPIs (1/5)
© Ericsson AB
2020-01-01 2020
| 5G | 5G
RAN NR RAN NR Accessibility
Accessibility | Internal
| Ericsson R1A | Figure 1-00
| Page
Objectives of Chapter 1
On completion of this chapter the participants will be able to:

1 Measure NR Accessibility performance
1.1 Use Flex Counters to get KPIs for EN-DC capable UEs
1.2 Explain the EN-DC and Standalone (SA) Setup procedure
1.3 Use eNodeB counters to measure the Initial E-RAB Establishment Success Rate in EN-DC
1.4 Use counters to measure the EN-DC Setup Success Rate in the gNodeB and eNodeB
1.5 Use gNodeB counters to measure the DRB Accessibility - Success Rate for mapped 5QI
1.6 Use counters to measure the Random Access in the gNodeB and eNodeB
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page
Reference Material
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page
Where to Measure? (NSA)
LTE only RB Split DRB
— NR capable UEs have its Control Plane
(Option 3x)
provided by the eNB
eNodeB gNodeB => Control Plane Observability for NR NSA UE
is in eNB
LTE PDCP NR PDCP
— The EN-DC bearers for NR capable UEs have
LTE RLC LTE RLC NR RLC their user plane to Core Network from gNB
=> PDCP (upper L2) observability is in
gNodeB for EN-DC bearers
LTE RLCLTE MAC NR MAC
— NR capable UEs can have their user plane
connected to both the gNB and eNB
=> Lower L2 (RLC, MAC) and L1 observability
in both eNB and gNB
LTE User plane EN-DC

UE Control plane UE
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page
Flexible Counters Concept
— Flexible counters are used to ensure that each operator can get KPIs differentiated for a configurable
set of UEs or bearers. Available in eNB since L17.A.
— The Flexible counters all have prefix “pmFlex” and are visible in MOM and PM jobs
— PmFlexCounterFilter MO is used to configure filter parameters for the Flexible counters.
— In the ROP file you will see several instances of each Flexible counter; one for each filter combination
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page
Flexible Counters for NR NSA; used in eNodeB
— A new filter parameter ENDC is defined for NR NSA, with
three (minimum) levels:
— 0 = Counter stepped if the UE is capable of EN-DC
— 1 = Counter stepped if the UE’s EN-DC capability matches the
eNodeB configuration (some LTE + NR frequency band
combination supported by both cell and UE)
— 2 = Counter stepped if the UE has user plane through gNodeB,
ie NR leg setup
— If selecting filter level 0, all UEs covered by level 1 and 2 are

covered as well
— If selecting filter level 1, all UEs covered by level 2 are
covered as well
— Filtering with level 0 can be of interest in the whole LTE
network, but level 1 and 2 are only applicable in EN-DC
configured eNodeBs
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page
Flexible Counters for EN-DC
— Three levels of filtering are available for the EN-DC
EPC
— The included levels are set by the parameter endcFilterMin
— For example, if this parameter is set to 1, then the counter is stepped if the EN-DC
state is either ENDC_NR_MATCHED or ENDC_NR_ACTIVE
ManagedElement B B
+- ENodeBFunction eNB gNB
+- PmFlexCounterFilter=1
counterNameSuffix=Endc1To99 (readOnly) LTE Cell 5G NR Cell
endcFilterEnabled=true
endcFilterMax=99 (ENDC_UE_RELEASED) (readOnly) Filter EN-DC Stage
endcFilterMin=1 (ENDC_NR_MATCHED) 0
(ENDC_NR_CAPABLE)
The UE is confirmed to be capable of EN-DC
+- PmFlexCounterFilter=2
(ENDC_NR_MATCHED)
counterNameSuffix=Endc2To99 (readOnly) 1
B1 measurements for EN-DC are configured in the UE
endcFilterEnabled=true (ENDC_NR_ACTIVE)
2
endcFilterMax=99 (ENDC_UE_RELEASED) (readOnly) ENDC is active for the UE
(ENDC_UE_RELEASED)
endcFilterMin=2 (ENDC_NR_ACTIVE) 99
UE is released
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page
Non-Standalone Accessibility Overview
EPC
In NR NSA scenario (with 5G coverage): S1-C
— RRC establishment and signalling are performed in 4G network through the S1-U
1
anchor cell in eNB
— RAB is established in both, first in 4G (Initial E-RAB Establishment) and then in
DRB
NR cells (EN-DC Setup) LTE NR
SRB
Accessibility KPI (session setup success rate) can be described as a

combination of different network access procedures: UE
— Control plane (RRC & S1 Signaling)
— User plane (RAB) establishment processes
2
EPC
So the Accessibility KPIs: S1-C S1-U
— Initial E-RAB Establishment Success Rate in LTE can be seen as main X2-C
Accessibility KPI also for NR NSA
X2-U
— EN-DC Setup Success Rate can be seen as a secondary Accessibility KPI for
NR NSA. DRB
LTE NR
SRB DRB
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page
UE
Differentiated Initial E-RAB Establishment Success
Rate Captured in eNodeB (EN-DC)
To monitor EN-DC stage 0 and 1 is recommended
pmFlexErabEstabSuccInit_Endcxxx
Differentiated Initial E-RAB Establishment SR = 100 x RRCESTABR x S1SIGCONNESTABR x
pmFlexErabEstabAttInit_Endcxxx
(Captured in eNodeB)
Where:
pmRrcConnEstabSucc
RRCESTABR = EPC
pmRrcConnEstabAtt – pmRrcConnEstabAttReatt - RRCMMEOVL
RRCMMEOVL =
pmRrcConnEstabFailMmeOvlMos +
pmRrcConnEstabFailMmeOvlMod
B B
eNB gNB
LTE Cell 5G NR Cell
pmS1SigConnEstabSucc
S1SIGCONNESTABR = KPI is on
pmS1SigConnEstabAtt – pmS1SigConnEstabFailMmeOvlMos EUtranCellFDD /
EUtranCellTDD
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page level
Bearer Type Transitions for EN-DC (EN-DC Setup)
MN Terminated SN Terminated
1 MCG DRB Split DRB
Initial Context Setup / LTE (MN) NR (SN) LTE (MN) NR (SN)
2
Incoming Handover /
RRC Re-establishment PDCP SN Addition PDCP
2 At reception of a B1 measurement report RLC RLC RLC
or after the Initial Context Setup procedure
is completed (configuration based) MAC MAC MAC
5
L1 L1 L1
3 When a bearer is set up that prevents other bearers being SN Release
configured as SN Terminated Split Bearers, for example at
VoLTE call setup
3 4
4 At reception of a B1 measurement. The B1 measurement is started
when the bearer – that prevents other bearers to be configured as SN SCG Release SCG Addition
terminated Split DRBs – is released, for example at VoLTE call release. (SN Modification) (SN Modification)
5 Triggered by NR radio link failure or by LTE or NR mobility

SN Terminated
events. The transition from the SN Terminated MCG Bearer state is triggered 5 MCG DRB
only by LTE mobility events (as there are no SCG resources in this case). SN Release LTE (MN) NR (SN)
PDCP
RLC
CPI (NR RAN 19.Q4) MN: Master Node
– Planning SN: Secondary Node MAC
–RAN Information MCG: Master Cell Group
–5G Mobility and Traffic Management Guideline (4.3) SCG: Secondary Cell Group L1
DRB: Data Radio Bearer
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page
SRB: Signaling Radio Bearer
SN Addition Criteria
Split bearer is allowed if all of the following conditions are met:
— ARP Value of Bearer > meNodeBS1TermReqArpLev for at least one bearer
and
— ARP Value of Bearer > splitNotAllowedUeArpLev for all bearers
and
— TTI bundling is not activated for any of the established bearers
Also, if the NR frequency is low or mid band (FR1), at least one of the
following conditions must be met:
— The UE is capable of dynamic power sharing
or MN Terminated SN Terminated
MCG DRB Split DRB
— The parameter endcSplitAllowedNonDynPwrShUe is true
LTE (MN) NR (SN) LTE (MN) NR (SN)
or PDCP SN Addition PDCP
RLC RLC RLC
— The UE has no bearers with serviceType = VoIP or PTT
MAC MAC MAC
L1 L1 L1
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 10
EN-DC Establishment – Overview
1 MN Terminated SN Terminated
MCG DRB Split DRB
Initial Context Setup /
Two step procedure for EN-DC establishment: Incoming Handover /
LTE (MN) NR (SN) 2 LTE (MN) NR (SN)
RRC Re-establishment PDCP SN Addition PDCP

RLC RLC RLC
1. At Initial Context Setup bearers are setup as a MN terminated MAC MAC MAC
MCG DRB. L1 L1 L1
— EN-DC specific UE capabilities are fetched if not received
from core network
— Optionally a B1 measurement is started.
UE MeNB SgNB EPC
2. The bearer is reconfigured to a Split bearer and the SN is added
— at reception of a B1 measurement report (measurement
based setup), or Initial Context Setup
— after the Initial Context Setup procedure is completed • Fetch EN-DC specific UE capabilities
(configuration based setup) • Start B1 measurements (optional)
Initial User-plane configuration for the Split DRB:

B1 Measurement Report
— Downlink: NR (after successful NR RA)
— Uplink: LTE or NR (configurable) SN Addition (eNB to gNB relocation)
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 11
EN-DC Setup Success Rate
EN-DC Setup SR [%] = 100 X

pmEndcSetupUeSucc EN-DC Setup SR [%] = 100 X pmEndcSetupUeSucc
(Captured in eNodeB) pmEndcSetupUeAtt (Captured in gNodeB) pmEndcSetupUeAtt
EPC
B B
eNB gNB
LTE Cell 5G NR Cell
KPI is on EUtranCellFDD KPI is on NRCellCU level.
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 12
SN Addition (eNB to gNB relocation, UL in LTE ) (1/2)
SgNodeB SN Addition
UE MeNB CU-CP CU-UP SGW MME
UL/DL User data in LTE
MN terminated SN terminated
MCG DRB Split DRB
RRC: B1 Measurement Report
Prepare for DRB

reconfiguration User-plane
X2: SgNB Addition
Request (RRC: CG-ConfigInfo) SGW
pmEndcSetupUeAtt + pmEndcSetupUeAtt + S1-U
pmEndcSetupScgUeAtt + pmEndcSetupScgUeAtt +
E1AP: Bearer Context Setup Request LTE PDCP NR PDCP
X2-U
pmEndcNrDrbSetupAtt +
Allocate PDCP and LTE RLC LTE RLC NR RLC

SCG resources
E1AP: Bearer Context Setup Response
LTE MAC LTE MAC NR MAC
pmEndcNrDrbSetupSucc +
X2: SgNB Addition
Request Acknowledge (RRC: CG-Config)
Suspend DRB
X2: SN Status Transfer MeNB SgNB
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 13
SN Addition (eNB to gNB relocation, UL in LTE ) (2/2)
SgNodeB SN Addition
UE MeNB CU-CP CU-UP SGW MME
RRC Reconfiguration MN terminated SN terminated
(“Add SCG” stop B1) Prepared for UL data
MCG DRB Split DRB
LTE Random Access
User-plane
UL User data in LTE (new ciphering key)
SGW
RRC Reconfiguration Complete
X2: SgNB Reconfiguration Complete S1-U S1-U
pmEndcSetupUeSucc + pmEndcSetupUeSucc +
LTE PDCP NR PDCP
pmEndcSetupScgUeSucc + pmEndcSetupScgUeSucc + X2-U
NR Random Access
LTE RLC LTE RLC NR RLC
S1-AP: E-RAB Modification Indication
Bearer
End marker packet Modification LTE MAC NR MAC
LTE MAC
Resume DRB RA RA
DL User data in NR (new ciphering)
New path
S1-AP: E-RAB Modification Confirm
MeNB SgNB
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 14
EN-DC Bearer Type Transition (Accessibility Counters)
EUtranCellFDD.pmEndcSetupUeAtt NRCellCU.pmEndcSetupUeAtt
MN Terminated NRCellCU.pmEndcSetupUeSucc SN Terminated
1 EUtranCellFDD. pmEndcSetupUeSucc
MCG DRB NRCellCU.pmEndcSetupScgUeAtt Split DRB
EUtranCellFDD.pmEndcSetupScgUeAtt
Initial Context Setup / LTE (MN) NR (SN) EUtranCellFDD.pmEndcSetupScgUeSucc NRCellCU.pmEndcSetupScgUeSucc LTE (MN) NR (SN)
Incoming Handover / EUtranCellFDD.pmEndcSetupFailNrRa
RRC Re-establishment PDCP PDCP
RLC RLC RLC
2
MAC SN Addition MAC MAC
L1 L1 L1
5
SN Release
3
SCG Release 4
MN: Master Node (SN Modification)
SN: Secondary Node 5 SCG Addition
SN Terminated (SN Modification)
MCG: Master Cell Group SN Release
SCG: Secondary Cell Group MCG DRB
DRB: Data Radio Bearer LTE (MN) NR (SN)
SRB: Signaling Radio Bearer NRCellCU.pmEndcSetupScgUeAtt
PDCP NRCellCU.pmEndcSetupScgUeSucc
CPI (NR RAN 19.Q4)
RLC PpControlLink.pmEndcNrDrbSetupAtt
– Product Overview
– Features and Capacities PpControlLink.pmEndcNrDrbSetupSucc
– LTE-NR Dual Connectivity MAC
– Performance of LTE-NR Dual Connectivity EUtranCellFDD.pmEndcSetupScgUeAtt
L1 EUtranCellFDD.pmEndcSetupScgUeSucc
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 15
EUtranCellFDD.pmEndcSetupFailNrRa
Random Access Success Rate
pmRaSuccCbra pmRadioRaCbSuccMsg3
Random Access SR = 100 X Random Access SR = 100 X
(Captured in eNodeB) pmRaMsg2AttCbra (Captured in gNodeB) pmRadioRaCbAttMsg2
EPC
B B
eNB gNB
LTE Cell 5G NR Cell
(SA and NSA)
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 16
Cell Range and Random Access (SA and NSA) (1)
ManagedElement
+GNBDUFunction
+NRCellDU
cellRange{1..100000} Maximum signal path distance from base station where
cellRange connection to UE can be set up and maintained.
If empty, system configures 5000 m for High-Band cells and 1600 m for Low-Band or Mid-
Band cells. For High-Band, 5000 m is the maximum value. If a higher value is configured,
value 5000 m is used.
X Value greater than 15000 m when rachPreambleFormat is

RACH_PREAMBLE_FORMAT_00 (F0) can cause random access performance degradation
and interference to other channels.
gNB
Unit: 1 m
pmRadioRaCbFailMsg1Ooc
The number of CBRA preambles discarded due to the timing offset corresponding to a
greater distance than the configured cell range. Unit: messages
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 17
Cell Range and Random Access (SA and NSA) (2)
pmRadioRaAttTaDistr (NRCellDU)
Distribution of measured TA values from all detected possible random access attempts.
TA values are expressed as a percentage of TA that correspond to configured cell range.
Unit: messages PDF Ranges:
Example: cellRange = 1600 m Bin[0]: [0..10[ %

Bin[1]: [10..20[ %
Bin[2]: [20..30[ %
Bin[3]: [30..40[ %
Bin[4]: [40..50[ %
Bin[5]: [50..60[ %
800 m Bin[6]: [60..70[ %
Bin[7]: [70..80[ %
Bin[8]: [80..90[ %
1900 m
X
Bin[9]: [90..100[ %
gNB Bin[10]: [100..110[ %
Bin[11]: [110..]: %
Condition: Stepped when RA Msg1 received. Counter includes both true and false random
access attempts.
0 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 110%
pmRadioRaAttTaDistr = 0 0 0 0 0 1
0 0 0 0 0 0 0
1
0m Bin[0]
160mBin[1]
320mBin[2]
480mBin[3]
640mBin[4]
800mBin[5]
960mBin[6] Bin[7]
1120m Bin[8]
1280m Bin[9]
1440m Bin[10]
1600m Bin[11]
1760m
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 18
Contention Based Random Access Counters (SA and NSA)
(1/2) Msg1 Random Access Preamble Received
pmRadioRaCbPreambles +
Are the preambles discarded Yes

because of reaching maximum pmRadioRaCbFailMsg1MaxMsg3Sched +
scheduled RA Msg3?
No
Are the preambles Yes

discarded because of a greater pmRadioRaCbFailMsg1Ooc +
timing offset than the configured
distance?
No
Attempt to schedule Msg2
pmRadioRaCbAttMsg2 +
Was no RA response (Msg2) Yes

sent due to expiry of the random pmRadioRaCbFailMsg2Disc +
B access response window?
No
gNB A B
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 19
Contention Based Random Access Counters (SA and NSA)
(2/2) A B
Msg2 Random Access response sent toward UE
Msg3 (NSA and SA), RRC Setup Request Received (SA only)
Yes
Is Msg3 received with wrong pmRadioRaCbFailMsg3Crc +
CRC?
No
Yes
Is Msg3 received with wrong pmRadioRaCbFailMsg3Crnti +
CRNTI?
No
Yes
Is a DTX detected for Msg3? pmRadioRaCbFailMsg3Dtx +
B
No
pmRadioRaCbSuccMsg3 +
gNB End of Flow

© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 20
DRB Accessibility - Success Rate for mapped 5QI (SA)
DRB Accessibility - Success Rate = 100 x RrcConnEstab x NgSigConnEstab x DrbEstab
for mapped 5QI [%]
B
gNB
Where:
RrcConnEstab = pmRrcConnEstabSucc – pmRrcConnEstabSuccMos
5G NR Cell
RrcConnEstabAtt
Counters on
RrcConnEstabAtt = pmRrcConnEstabAtt – (pmRrcConnEstabAttReatt + NRCellCU
pmRrcConnEstabAttMos – pmRrcConnEstabAttReattMos) level
NgSigConnEstab = pmNgSigConnEstabSucc – pmNgSigConnEstabSuccMos Repetitive attempts from

pmNgSigConnEstabAtt – pmNgSigConnEstabAttMos the same UE are removed.
DrbEstab = pmDrbEstabSucc5qi Accesses for mobile

originated signaling are
pmDrbEstabAtt5qi removed.
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 21
Initial Access (SA)
Overview
gNB
Like LTE, an UE is able to receive 5G data SIB1 broadcasted AMF SMF
services if it is registered and has at least one
PDU session established 1 2 Random Access & RRC Connection Establishment
AMF Selection
NGAP: Initial UE Message (NAS: Registration Request)
Unlike LTE, it is possible in NR for an UE to be
Authentication and NAS Security Activation
registered without a PDU session and Data
Radio Bearer (DRB) established (steps 1-3) RRC: DL Information Transfer NGAP: Initial Context Setup Request
(Registration Accept) (NAS: Registration Accept)
UE indicates ”Slice ID” in RRC Setup Complete AS Security
allowing slice specific treatment (e.g. CN node 3
RAN Initiated UE Capability Retrieval (if not provided by CN)
selection)
NGAP: Initial Context Setup Response
NAS: Registration Complete
Steps performed:
NAS: PDU Session Establishment Request
PDU Session
(1) Random Access NGAP: PDU Session Resource Setup Request Established in 5GCN
(2) RRC Connection Establishment 4 RRC: DL Information Transfer (optional (optional NAS PDU, PDU Session Establishment
NAS PDU) Accept)
(3) Registration f Reconfiguration
NGAP: PDU Session Resource Setup
(4) PDU Session establishment Response
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 22
NR SA - Accessibility Counters (1)
ManagedElement
GNBDUFunction
NRCellCU
pmRrcConnEstabAtt
pmRrcConnEstabAtt Number of attempted RRC Connection Establishment procedures. See 3GPP TS 38.331, RRC Setup Request. Condition: Stepped when
an RRC Setup Request message is received in gNodeB CU.
pmRrcConnEstabSucc
Number of successfully completed RRC Connection Establishment procedures. See 3GPP TS 38.331, RRC Setup Complete. Condition: Stepped when an
RRC Setup Complete message is received in gNodeB CU.
pmRrcConnEstabAttReatt
Number of RRC Setup Requests that are considered as re-attempts. See 3GPP TS 38.331, RRC Setup Request. Condition: Stepped when an RRC Setup
Request message is received in gNodeB CU while an RRC Connection Establishment is already ongoing with same UE identity.
pmRrcConnEstabAttMos
Number of attempted RRC Connection Establishment procedures with establishment cause Mobile Originating Signaling (MOS). See 3GPP TS 38.331, RRC
Setup Request. Condition: Stepped when an RRC Setup Request message is received in gNodeB CU with establishment cause Mobile Originating Signaling
(MOS).
gNB
pmRrcConnEstabSuccMos
Successful RRC Connection Establishments where establishment cause is Mobile Originating Signaling (MOS). See 3GPP TS 38.331, RRC Setup Complete.
Condition: Stepped when an RRC Setup Complete message is received in gNodeB CU and establishment cause is Mobile Originating Signaling (MOS).
pmRrcConnEstabAttReattMos
Number of RRC Setup Requests that are considered as re-attempts for establishment cause Mobile Originating Signaling (MOS). See 3GPP TS 38.331, RRC
Setup Request. Condition: Stepped when an RRC Setup Request message is received in gNodeB CU with establishment cause Mobile Originating Signaling
(MOS) and while an RRC Connection Establishment is already ongoing with same UE identity.
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 23
ManagedElement
GNBDUFunction
NRCellCU
pmNgSigConnEstabAtt
The number of NG signaling connection establishment attempts. Unit: messages
Condition: Stepped at initiation of the AMF selection, selecting to which AMF the NGAP message Initial UE Message shall be
sent.
pmNgSigConnEstabAttMos
Number of NG signaling connection establishment attempts for connections with RRC establishment cause Mobile Originating
Signaling (MOS) by receiving a first message from AMF. See 3GPP TS 38.331, RRC Setup Request. Unit: messages
Condition: Stepped at initiation of AMF selection, selecting to which AMF the NGAP message Initial UE Message can be sent.
pmNgSigConnEstabSucc
gNB The number of successful NG signaling connection establishments. Unit: messages
Condition: Stepped at first message received on this UE associated logical NG connection.
pmNgSigConnEstabSuccMos
Number of successful NG signaling connection establishments for connections with RRC establishment cause Mobile Originating
Signaling (MOS). See 3GPP TS 38.331, RRC Setup Request. Unit: messages
Condition: Stepped when first message is received on this UE associated to logical NG connection.
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 24
ManagedElement
GNBDUFunction
NRCellCU
pmDrbEstabAtt5qi
Number of DRB establishment attempts for each 5QI for each cell.
Compressed: True
Condition: Stepped when attempting to establish DRB using one of following NGAP procedures:
- Initial Context Setup.
- PDU Session Resource Setup.
- PDU Session Resource Modify.
pmDrbEstabSucc5qi
Number of successful DRB establishments for each 5QI for each cell.
gNB
Compressed: True
Condition: Stepped when a DRB is successfully established using one of following NGAP procedures:
- Initial Context Setup.
- PDU Session Resource Setup.
- PDU Session Resource Modify.
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 25
Summary of Chapter 1
The participants should now be able to:

1 Measure NR Accessibility performance
1.1 Use Flex Counters to get KPIs for EN-DC capable UEs
1.2 Explain the EN-DC and Standalone (SA) Setup procedure
1.3 Use eNodeB counters to measure the Initial E-RAB Establishment Success Rate in EN-DC
1.4 Use counters to measure the EN-DC Setup Success Rate in the gNodeB and eNodeB
1.5 Use gNodeB counters to measure the DRB Accessibility - Success Rate for mapped 5QI
1.6 Use counters to measure the Random Access in the gNodeB and eNodeB
© Ericsson AB
2020-01-01 2020
| 5G | 5G
| Page 26
ericsson.com/training

Lzu1431171 M6

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lzu1431171 M6

Uploaded by

Copyright:

Available Formats

5G RAN NR Accessibility

5G RAN NR KPIs (1/5)

On completion of this chapter the participants will be able to:

LTE User plane EN-DC

— If selecting filter level 0, all UEs covered by level 1 and 2 are

Accessibility KPI (session setup success rate) can be described as a

5 Triggered by NR radio link failure or by LTE or NR mobility

RRC Re-establishment PDCP SN Addition PDCP

Initial User-plane configuration for the Split DRB:

EN-DC Setup SR [%] = 100 X

LTE Cell 5G NR Cell

KPI is on EUtranCellFDD KPI is on NRCellCU level.

Prepare for DRB

pmEndcSetupUeAtt + pmEndcSetupUeAtt + S1-U

Allocate PDCP and LTE RLC LTE RLC NR RLC

X2: SgNB Reconfiguration Complete S1-U S1-U

LTE Cell 5G NR Cell

(SA and NSA)

X Value greater than 15000 m when rachPreambleFormat is

Example: cellRange = 1600 m Bin[0]: [0..10[ %

Are the preambles discarded Yes

Are the preambles Yes

Was no RA response (Msg2) Yes

B access response window?

Msg2 Random Access response sent toward UE

gNB End of Flow

NgSigConnEstab = pmNgSigConnEstabSucc – pmNgSigConnEstabSuccMos Repetitive attempts from

DrbEstab = pmDrbEstabSucc5qi Accesses for mobile

NAS: Registration Complete

The participants should now be able to:

You might also like