RA57331-V-22R2 - LE05 - Network Usage Analysis - Internal - Version

Network Usage Analysis
NokiaEDU
5G Radio Optimization Part 2, Nokia internal version

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

Please delete this slide if document is uncontrolled
Module Objective
Document ID: DXXXXXXXXX
By the end of the course, participants will be able to:
Document Location:
Organization:
Version Description of charges Date Author Owner Status Reviewed by Reviewed Approver Approval
date date
• define optimization in the context of mobile telecoms
DD-MM-YYYY DD-MM-YYYY DD-MM-YYYY
• sketch optimization-related processes on overview level
• distinguish measurements, counters and KPIs
• recall the Nokia 5G Performance Management Architecture
• list measurement types and KPI use cases
3 RA57331-V-22R2 © Nokia 2022
3 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 3
Module Objective
After completing this learning element, the participant should be able to:
Index
Locate Introduction
Record 5G Radio Interface Capacity
• Optimization Overview
Recognize Number of Users
• Optimization Activities
Repeat Data Volume • Compatibility matrix between 5G and SRAN releases
Discuss Number of Access
• Attempts
Quiz I
• 5G Performance Management Architecture
• Counters
• Key Performance Indicators
• References
• Quiz II/Exercise
4 RA57331-V-22R2 © Nokia 2022
4 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 4
Index
Index Introduction
5G Radio Interface Capacity
Number of Users
Data Volume
Number of Access Attempts
• Compatibility matrix between 5G and SRAN releases
• Quiz I
• Counters
• References
5 RA57331-V-22R2 © Nokia 2022
5 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 5
Index
Optimization Overview
Introduction Introduction
• Radio NetworkNumber of Users
Optimization ensures the quality of the network in terms of performance
Data Volume
• Performance isNumber
quantified
of Access Key
using Performance Indicators ( KPIs) agreed with
Attempts
customers
• KPIs can be based on network statistics (OSS KPIs) or drive testing (field KPIs)
• The usage of one or the other (or both) will depend on the metrics to be improved and
project characteristics:
Field tests KPIs OSS KPIs
The end-user experience is directly measured Difficult to combine counters to show end-user
experience
Tests are only done at certain locations during Covers all the users all the time
certain times
Performance in very specific locations can be Performance is typically averaged over a cell
measured
The performance of a specific UE is measured Average performance of all UEs
Can be done even before network is launched Certain traffic level required to have statistical
validity
6 RA57331-V-22R2 © Nokia 2022
6 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 6
Introduction
Capacity Areas
Optimization Overview
• Usage analysis consists of measuring the current capacity utilization and handle the
KPIs sets
areas where there are capacity bottlenecks. The capacity areas which need to be
monitored:
• Key Performance Indicators are grouped in sets according to different areas that may
• 5Grequire
radio optimization
interface capacity
• • 5GFollowing
admissionareascontrol
are covered within this training portfolio:
Accessibility:
• 5G gNB processing
• Ability of the network to provide a connection when requested by the
capacity
user.
• LTE radio interface capacity (due to increased load from EN-DC connections)
• Retainability: Ability of the network to maintain a connection during the expected
• LTE service
eNB processing
time. capacity (due to increased load from EN-DC connections)
• Interface
• Usage:capacity (X2, and
Throughput S1, NGC, F1)usage (traffic volumes, users, attempts)
network
• Integrity:
• Capacity Latencies
licenses
• Mobility: Related to handover and cell change procedures.
7 RA57331-V-22R2 © Nokia 2022
7 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 7
Index
Optimization cases
Pre-launch optimization
Introduction
Number of Users
• Done before the Data Volume
‘launch’ of
the network Number of Access Attempts
• Low network traffic due to
lack/little users
• Optimization relies mainly in
field KPIs
• Optimization focuses in verifying the RF design and identify coverage and quality
problems
• Optimization usually done in groups (clusters) and overall network acceptance is passed
after the cluster acceptance tests are passed
8 RA57331-V-22R2 © Nokia 2022
8 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 8

Overview
Optimization cases
Post-launch
• Both optimization
the signaling channels (PRACH, PDCCH, PUCCH) and the data channels (PDSCH
and PUSCH) need to be managed.
• Network carries
user’s traffic
There
• are
OSStwoKPIsmain
are optimization areas:
• RL Quality: relevant
statistically The radio link should be good, so high modulation and coding schemes
and provide
• Radio
information on resources: (Slots and PRBs) should be utilized as much as possible
interface
different levels
(network, site, cell)
• PDSCH and PUSCH capacity can directly affect the throughput
• Optimization is not
• Capacity problems
necessarily limitedon the signaling channels can also negatively impact the throughput
to a certain
• Spectral efficiencyarea is often used as a measure
(e.g. cluster)
9 RA57331-V-22R2 © Nokia 2022
9 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 9

PDCCH – Relevant Features
Optimization cases
Post-launch optimization
Feature ID Feature name
5GC002469 Adaptive PDCCH symbol configuration
CB006555 Dynamic PDCCH pattern modification
After the initialgeneral performance
5GC000791 check
PDCCH to set level
aggregation the control
baseline, the optimization steps are:
CB007090 PDCCH symbol usage control
• Configuration and parameter analysis to verify that the network is implemented as
planned, with the desired features, that there is consistency in the parameter settings.
• Performance
• 5GC000791: assessment
PDCCH aggregation levellooks at OSS statistics to investigate the important aspects
control
• like accessibility,
introduces retainability,
link adaptation usage channel
for the PDCCH and integrity.
• RF Analysis and mobility optimizationconditions
• CCE aggregation level is determined by radio is based on network and drive test data to make
• Compromise between enough CCE capacity and serving users at the cell edge
improvement proposals for the antenna configurations.
• End-user
• 5CB007090: throughput
PDCCH symbol usageandcontrol
latency performance normally investigated as dedicated items
• and specificadjusts
dynamically optimization
the number methodologies
of symbols usedapply.
for PDCCH between 1 and 3
minimizes the risk of PDCCH starvation in busy cells
• •Root Cause Analysis to find solutions for unresolved issues left in previous.
• maximizes the PDSCH resources in cells with low load
• Finally, system changes are proposed and implemented. These changes can
include parameter changes, feature activations, HW expansions or others.
10 RA57331-V-22R2 © Nokia 2022
10 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 10

PDCCH – Performance Monitoring
Index
NR_5149a: Average
• Optimization Overview PDCCH CCE starvation ratio in cell
Compatibility matrix between
• SLT_UL_CCE_STARVATION_CBWP0..9 5G and SRAN releases
+ SLT_DL_CCE_STARVATION_CBWP0..9
• --------------------------------------------------------------------------------------
Quiz I
SLT_UL_GRANT_CAPABILITY_CBWP0..9 + SLT_DL_GRANT_CAPABILITY_CBWP0..9
• Counters
• References
• Relevant counters are available in the 55335: PDCCH usage measurement
11 RA57331-V-22R2 © Nokia 2022
11 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 11

PUCCH
Post-launch optimization steps
1. Configuration
• PUCCH utilization andand parameter
congestion analysis
depends on
• The number of users in the cell
• How
1a. often a connected
Analysis user sends1b.
of network CSIAnalysis
reports -ofthis
cellislevel csiReportPeriodicity
controlled by 1c. Check if planned
• Capacity
level(CSI reports per time) - depends
parameters on the(i.e.
parameters frame
thosestructure and on several features
parameters are
• different
Admission Control in the DU is doing across the
this calculation and cells) implemented
in case rejects on the
new connection requests
network
Network level parameters do
not change across cells • Validate the PCI plan Verification that the
•
• PUCCH capacity optimization procedure consists of: planned /intended
• Compare planned • Validate the RSI plan parameters
• For the given configuration,
parameters against calculate the maximum number of connected users are
• Validate the Neighbor implemented by
recommended
Use OSS values
counters to monitor if there plan
is a capacity
•
from Product Line or for 4G-5Gissue
and 5G- comparing a network raml
5G neighbours xml file or SCF if a few
• If yes,Global
use one
NPOof the several methods to either increase the capacity or reduce the usage
sites with planned ones.
• Understand deviations • Possible tools: EdenNET
• Tools: xml parser
and their impact in
performance should be
understood
12 RA57331-V-22R2 © Nokia 2022
12 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 12

PUCCH – Relevant Features Summary
5GC002511 Load based UCI periodicity
5GC002545 FDM of periodic CSI reports on PUCCH for FR1 cells
5GC000885 Long PUCCH for FDD cells
5GC001348 2. Performance
Uplink Assessment
channel multiplexing
• High level idea of the network performance for
5GC001732 UCI multiplexing on PUCCH by FR2
checking
TDD cellsthe most important KPIs
5GC002200agreed with customer Support 8 port CSI-RS codebook for SU-MIMO
CB006064 Long PUCCH for FR1 TDD cells [only ABIL]
• Check sites are on air and
5GC001817
with no alarms
Aperiodic CSI reporting on PUSCH for non-beamforming FDD cells [only ABIO]
•
CB007220 Use either drive or OSS
AperiodicIfCSI
KPIs. using drive
reporting ontesting
PUSCH for procedure
beamformingisFR1
similar to pre-
TDD cells [only ABIO]
CB007950 launch optimization except for the
Long PUCCH for need
FR1 TDDfor a detailed
cells (ABIO) analysis. Enough to drive a
CB007827 single cluster to get a rough ideacapacity
Long PUCCH of theenhancement
performance.
- FR1 TDD [22R1]
CB007798 Aperiodic CSI reporting on PUSCH for non-beamforming FDD cells – ABIL[22R1]
CB008131 Aperiodic CSI reporting for FR1 CA deployments with FDD as Pcell [22R1]
3. RF and mobility Optimization

• Maximizing coverage and dominance areas making physical antenna changes (e.g.
tilts, azimuths)
13 RA57331-V-22R2 © Nokia 2022
13 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 13

PUCCH – Load based UCI Periodicity
5GC002511: Load based UCI periodicity:
• Adapts the periodicity of the CSI reports based on the number of connected users
• Divides the PUCCH resources into two pools,
• One pool which uses csiReportPeriodicity
4. End-user performance optimization
• Another pool which uses the maximum value (320 slots for TDD networks and 160 slots for FDD networks)
• Size of the pools is defined by the loadBasedCsiPerThreshold
• • Mainly involves optimization through parameterization and feature usage. The aim
Example:
of this step is to:
• TD-LTE frame, beamforming enabled, 5GC002545 enabled, csiReportPeriodicity = 320 slots
•
• Maximize the end-user performance by changing parameter values.
➔ Cell capacity 160 users
• Optimize the
• 5GC002511
Enable with antenna beam patterns=also
loadBasedCsiPerThreshold using
50 and parameterization.to 80 slots
set csiReportPeriodicity
• Pool #2 supports 160 * 50% = 80 users. Pool #1 supports 80 / 4 = 20 users.
• ➔ Cell capacity: 80 + 20 = 100 users
• Attractive in medium loaded cells as better latency can be obtained
• 5GC002511 then prevents admission control rejections during the occasional periods with higher cell load
14 RA57331-V-22R2 © Nokia 2022
14 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 14

Long PUCCH
Index
5GC000885: Long PUCCH for FDD cells,
CB006064: Long PUCCH for FR1 TDD cells and
CB007950: Long PUCCH for FR1 TDD cells (ABIO):
• Increases PUCCH capacity •up to 1152 connected
Optimization users per cell
Activities
• Capacity depends on frame Compatibility
• structure, matrix
bandwidth, between
presence 5G and
of other SRAN releases
features etc.
• • (srPeriodicity
Dedicated parameter for SR Quiz I ) removes dependency of latency and csiReportPeriodicity
• Counters
CB007827: Long PUCCH capacity
• Keyenhancement
Performance - FR1 TDD:
Indicators
• • References
Potential to double the capacity for connected users in the cell
• • Quizreports
Possibility to bundle the periodic II/Exercise
of CSI-RS and beam management into one PUCCH F3
• Capacity gain is realized if beamforming, long PUCCH and 5GC002200 PMI beamforming are enabled
• Supported for eCPRI radio units
15 RA57331-V-22R2 © Nokia 2022
15 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 15

PUCCH – Multiplexing
Compatibility matrix between 5G and SRAN Releases
5GC002545: FDM of periodic CSI reports on PUCCH for FR1 cells and
System RAN SW 3GPP for NR 3GPP for NetAct
5GC001732:
Release UCI multiplexing on PUCCH for FR2 TDD: LTE
• Multiplexing
5G21A of several
SRAN 20C periodic
3GPP Rel-15CSI reports
03/2020 (for LA,
+ 06/2020 NBCbeam
CRs management)
N/A of one
NetAct UE + FP773 NetAct 20 SP2106
20 SP2105
SRAN 21A
• PUCCH capacity increase
SRAN 21B
SRAN 21A 5G20B N/A 3GPP Rel-15 NetAct 20 SP2102 + FP764 NetAct 20 SP2104
5G21A 03/2019
5GC001348: Uplink channel multiplexing:
5G21B
• PUSCH data and
5G21B PUCCH
SRAN 21A symbols
3GPP Rel-15 can be multiplexed into the
09/2020 N/A PRACH slot
NetAct 20 SP2108 + FP799 NetAct 22
SRAN 21B
• PUCCH capacity increase
22R1-SR
SRAN 21B 5G21A NA 3GPP Rel-15 NetAct 20 SP2108 + FP799 NetAct 22
5G21B 03/2020
22R1-5G
22R1-5G SRAN 21B 3GPP Rel-16 12/2020 N/A NetAct 22 FP2201 + FP868 NetAct 22 FP2202
22R1-SR
22R2-SR
22R1-SR 5G 21B N/A 3GPP Rel-15 NetAct 22 FP2201 + FP868 NetAct 22 FP2202
22R1-SR 03/2020
22R2-SR
16 RA57331-V-22R2 © Nokia 2022
16 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 16

PUCCH – Cell specific CSI-RS
• Index
5GC002200: Support 8 port CSI-RS codebook for SU-MIMO:
Improves PDSCH throughput in TDD FR1
Resource set 1:
• 1CSI-RS resource
• Legacy UE-specific → cell specific CSI-RS signal
• Panel split 4,1
• Result: capacity (connected Optimization
• UEs) increase Overview
• Optimization Activities • 16 PMI beams
• CSI-RS resources are grouped in the CSI-RS resource sets
• UEs may support different•number
Quiz ofI CSI-RS resources Resource set 2:
• • 5G Performance
5GC002200 defines 3 CSI-RS resource sets Management Architecture
• 2 CSI-RS resources
• • Counters
Maximum number of the CSI-RS resources: • Panel split 2,2
• NRCELL.periodicCsiAcquisition.maxCsirsNumber • 128 PMI beams
• References
• Please note that multiple resource
• Quiz sets can be transmitted
II/Exercise
8 port CSI-RS resources:
Resource set 3:
1 2 3 4
• 4 CSI-RS resources
• Panel split 2,2
• 256 PMI beams
example special slot with CSI-RS symbols
17 RA57331-V-22R2 © Nokia 2022
17 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 17
Quiz 1-1

Which
PUCCHKPIs measure
– Aperiodic directly
CSI the end-user experience?
Reporting
5GC001817: Aperiodic CSI reporting on PUSCH for non-beamforming FDD cells and
CB007220: Aperiodic CSI reporting on PUSCH for beamforming FR1 TDD cells:
• Aperiodic
Field reporting
test KPIsto receive frequent CSI reports, available for ABIO
• csiReportPeriodicity can be relaxed, e.g. maximum value
OSS KPIs
CB007798: Aperiodic CSI reporting on PUSCH for non-beamforming FDD cells – ABIL:
• 5GC001817 functionality available for ABIL
CB008131: Aperiodic CSI reporting for FR1 CA deployments with FDD as PCell:
• “Spillover” feature [22R1] to 5GC001817 and CB007220
• Aperiodic CSI reporting support for configurations with CA and with FDD as P(S)Cell
18 © 2022 Nokia
18 RA57340-V-22R2 © Nokia 2022
18 RA57331-V-22R2 © Nokia 2022
RA57331-V-22R2 18
Quiz 1-2

Which optimization
Monitoring Usage andscenario aims
Congestion at verifying the RF design and to
- KPIs
identify areas of poor coverage and quality?
KPI id KPI name Formula
NR_5247a 5G Average number of connected AVE_NUMBER_OF_NSA_USERS / AVE_NUMBER_OF_NSA_USERS_DENOM +
Pre-launch optimization
users per cell AVE_NUMBER_OF_SA_RRC / AVE_NUMBER_OF_SA_RRC_DENOM
NR_5125a 5G Maximum number of NSA users PEAK_NUMBER_OF_NSA_USERS
Post-launch
NR_5129a optimization
5G Maximum number of SA RRC PEAK_NUMBER_OF_SA_RRC_USERS
connected users
NR_5126a 5G Average admission holding time AVE_NSA_USER_HOLDING_TIME / AVE_NSA_USER_HOLDING_TIME_DEN
of NSA users
NR_548b 5G Average RRC connection duration AVE_SA_RRC_HOLDING_TIME / 1000 / AVE_SA_RRC_HOLDING_TIME_DEN
for SA users
NR_5248a 5G admission control rejection ratio (SGNB_DU_NSA_ADMISSION_NO_PUCCH +
due to lack of PUCCH capacity SGNB_SA_DU_RAC_REJ_DUE_PUCCH) / (SGNB_DU_NSA_ADMISSION_REQ +
SGNB_SA_DU_ADMISSION_REQ)
19 © 2022 Nokia
19 RA57340-V-22R2 © Nokia 2022
19 RA57331-V-22R2 © Nokia 2022
RA57331-V-22R2 19

Monitoring Usage and Congestion - Example
•
Index
Admission control rejections in a loaded cell:
csiReportPeriodicity is 320 slots
• Beamforming enabled and frame structure is TD-LTE
• Cell capacity is 40 connected users
• Steep increase of admission• control rejections
Compatibility whenbetween
matrix average number
5G and of users
SRAN NR_5124 exceeds 35
releases
• Quiz I
• Counters
• References
20 RA57331-V-22R2 © Nokia 2022
20 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 20

PDSCH – Relevant Features Summary
•
Performance Management Architecture
PDSCH capacity utilization is directly impacted by the amount of user traffic
• Overview
Capacity problems will immediately be translated into decreased end-user throughput
Features related to PDSCH capacity management:
•
KPIs High-level
performance reporting
End-user
Feature ID Feature name Comments
• Main performance metrics providing information of the
• Based on counters
5GC00067 perception Performance
UL/DL FDM scheduling
different performance areas.
Allows to frequency multiplex two UEs in the same slot.and
ThisKPIs
is especially
Reports • KPIs are based on counters
9 effective if many small packets are transmitted in the• network. Information provided
Works for
FR1 TDD cells. UEs must use same beam(s) is closer to the user
5GC00072 PSCell load balancing Counters
Balances the sector load over multiple intra-band carriers perception
FR2 only
• Describe individual values that can be collected into • Bases for wide
1 measurements.
network optimization
CB005892 Frequency domain multiplexing
gNB • Extends 5GC000679
Counters are incremented forfunctionality to FDD
example when certain cells. It also enhances TDD cell
event
measurements occurs.
for FDD cells • multiplexing from 2 to 4 UEs in same
Each counter belongs only to one measurement type. slot. UEs must use same beam(s)
5GC00253 FDM allocation enhancements Removes the same-beam condition for eCPRI RUs
Low-level performance
7
reporting
5GC00052 DL MU-MIMO for Digital Allows to re-use time and frequency domain resources between UEs which
4 Beamforming Procedures
are spatially separated in the cell
• Based on gNB traces
• Provide detailed info
Observations
CB006667 Increased number of FDM Allows up to 16 UEs to be multiplexed in the same slot. Only forsystem
on the ABIL
System
scheduled UEs per slot behavior
CB007859 characteristics
Spillover of CB006667 for ABIO, Extends CB006667 functionality to ABIO • Used for
ABIN, ASOE [22R1] troubleshooting of
specific cases
21 RA57331-V-22R2 © Nokia 2022
21 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 21

PDSCH - KPIs
KPI id
Measurements
KPI name Formula Comment
Overview
NR_5110a 5G Usage ratio of PDSCH data DATA_SLOT_PDSCH / DL_DATA_SLOTS • Not necessarily an indication of
slots over all DL data slots congestion
• PM counters are measurements categorized in groups related to•a Gives similar function.
a good approximation even
• Each group is a measurement type. if PDSCH is also carried on SSB
and TRS slots
• Measurement types are administrative units for activating/deactivating the counters as
NR_5114a 5G PRB utilization for PDSCH PRB_USED_PDSCH / • There can be congestion even with
a set
low PRB utilization
• Different measurement typesPRB_AVAIL_PDSCH
can be activated per gNB
NR_5192c 5G Average number of ACC_SCHED_UE_PDSCH / • Related to FDM feature efficiency
• Measurements canMU-MIMO)
scheduled (FDM and be identified either by: + SSB_SLOT_PDSCH +
(DATA_SLOT_PDSCH
UEs on PDSCH
• Measurement ID (e.g. M55316) or TRS_SLOT_PDSCH)
NR_5100c 5G Average MAC layer user 8 * DL_MAC_SDU_VOL_DTCH / • Impacted by radio link quality,
• Measurement name (e.g. NR Carrier Aggregation Distributed Unitpacket
throughput in downlink (gNB-DU) orand UL slot
size, SSB
((ACC_UE_DL_DRB_DATA -
• Measurement abbreviationACC_UE_DL_SLEEP_DATA)
(e.g. NCADU) *
overhead and multiple
simultaneous users.
• Each Measurement ID has a uniquely associated name
(DATA_SLOT_PDSCH_TIME / and abbreviation
DATA_SLOT_PDSCH)) • Small data bursts will show low
values
22 RA57331-V-22R2 © Nokia 2022
22 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 22

PDSCH - KPIs
Measurements All counters available for Classical and Cloud BTS except
M557xx: Radio Cloud Platform only available in the Cloud
KPI id KPI name Formula Comment
5G NR Measurement Types (1/2)
BTS
NR_973a 5G Average downlink RLC delay DL_RLC_DELAY_L_QOS_GRP_01..20 / plane measurements
(*) User • scheduler arewaiting timegroup of
the largest
measurements followed by the control plane ones.
in gNB-DU DL_RLC_INI_PDU_TX_L_QOS_GRP_01..20
• high values: scheduler is waiting
for empty transmission slots or
M513xx: Common M557xx: Radio Cloud M40xxx Miscellaneous
transport plane Platform load the scheduler is waiting for the UE
countersto wake up from DRX
measurements measurements
NR_1393a
Not 5G Average
specific to allocated
5G PDSCH PRB_USED_PDSCH
Counters related/to:
(DATA_SLOT_PDSCH +
These Tells
•are how well
counters the scheduler is able
which
PRB size SSB_SLOT_PDSCH + TRS_SLOT_PDSCH)are not specific forPRBs
to fill the 5G but
• Usage (CPU, Memory, also
NR_1481a 5G DL PDCP SDU throughput on DL_PDCP_VOL_UE_TPUT_5G_QOS05…20
Disk…) / used for other
• Excludes RATs
small data bursts
NR leg Control
M551xx: per DRB for QoS group 5
plane DL_PDCP_TIME_UE_TPUT_QOS_05...20
measurements
to 20
Counters related to:
M556xx: O&M M553xx: User plane
• Interfaces (S1, F1AP, measurements (*)
X2-C) measurements
Counters related to:
• Admission Control Counters related to:
• Interfaces ( X2-U, F1-U)
(Central and Distributed • Modules (SMOD,
Unit) • Procedures (DL/UL
BBMOD, RMOD) HARQ, RACH Usage…)
• Bearers (EPS, Radio)
• Cell availability • Layers (MAC, PDCP..)
• UE State
23 RA57331-V-22R2 © Nokia 2022
23 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 23

PDSCH – Optimization Procedure
Measurements
Following actions should be considered:
• Fill5G NRslots
up the Measurement
by activating theTypes (2/2)multiplexing features
PDSCH FDM
• Enable multi-user MIMO
• Counters for M513xx: Common transport plane measurements are used also for other RATs
• Reduce the overhead from non-PDSCH slots and symbols (though it may degrade other areas)
• Mapping of M513xx measurements to 5G BTS components:
• Increase the efficiency of the PDSCH by optimizing the RF performance and
• Using throughput enhancement features (4x4 MIMO, 256 QAM)
• Specific QCIs may be improved by using QoS-based scheduling
• Increase 5G site density
24 RA57331-V-22R2 © Nokia 2022
24 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 24

PDSCH – Case Example
Performance Management Architecture Part 1Case example of PDSCH multiplexing
5G NR Counters per release - Example for M551xx5G20A,
Control Plane
80MHz, beamCounters
set #3#1: (1/2)
• Clear dependency number of active DL UEs
Measurement id Measurement vs. slot
Abbreviation Objectutilization,
level 5G21Bcongestion
22R1 22R2starts above
55110 NR X2-C Interface signalling NRBTS level NX2CB50% NRBTS 35 35 35
55112 NR X2-C Interface signalling NRCELL level NX2CC NRCELL 60 60 68
55113 NR F1AP Interface Report per CELL •NF1CCDL PRBNRCELL
max is 217
25 (80 25
MHz) 25
55114 Central unit (CU) Radio admission control measurement RACCU NRCELL 42 42 49
55115 Distributed unit (DU) Radio admission control measurement •
RACDU Below 60% slot utilization, only an average
NRCELL 25 27 31
of 80 PRBs is used
55116 NR UE State NRCELL level NNSAUE NRCELL 12 12 12
55117 NR F1AP Interface Report per DU NF!CD NRDU 73 73 73
55118 NR Carrier Aggregation Central Unit (CU) NCAC NRCELL 70 72 72
55119 NR NGC Interface per BTS •
NNGCB CB005892: Frequency domain multiplexing
NRBTS 31 31 31
55120 NR Intra Frequency PSCell Change NINFC for FDD cells in use (max 4 UEs per slot)
NRCELL 20 20 20
55121 NR E1AP Interface Report per BTS NE1CB NRBTS 10 10 10
55123 NR E1AP Interface Report per CU-UP •NE1CU Average scheduled UEs on PDSCH rather
NRCUUP 8 8 8
low, assumed cause: different UEs

55124 NR RRC Interface Report per CELL NRRCC NRCELL 53 53 66
55125 NR NGAP Interface Report per CELL NNGCC NRCELL 58 62 147
55126 NR XN Interface NXNCB frequently use different beams
NRBTS 34 34 34
55127 NR RRC Interface Report per DU NRRCD NRDU 13 13 19
55128 NR LTE Mobility •LTEMO Optimization options:
NRBTS 13 13 13
55129 NR RLF Report per Cell NRLFC NRCELL 3 3 3
55130 NR NSA Signaling Radio Bearer in the gNB-CU •
SRB3C CB006667: Increased
NRCELL 3 number
3 of FDM
3
55131 Central unit (CU) traffic measurement NTRAF scheduled
NRBTS UEs per1 slot 1where up1 to 16 UEs can
55132 NR E1AP Interface Report per CU-UP for NSA NE1UN be combined
NRCUUP 8 8 8
55133 NR E1AP Interface Report per CU-UP for SA NE1US NRCUUP 12 12 12
55134 NR E1AP Interface Report per CU-CP for NSA •
NE1CN 5GC002537:
NRBTS FDM 8 allocation
8 enhancements,
8
55135 NR E1AP Interface Report per CU-CP for SA NE1CS feature allows to combine UEs 16
NRBTS 16 16 in different
beams
25 RA57331-V-22R2 © Nokia 2022
25 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 25

PUSCH – Relevant Features Summary
•
Performance Management Architecture Part 1
PUSCH capacity utilization is directly impacted by the amount of user traffic in UL but also by DL TCP (approx. 1% TCP
ack)
5G NR Counters per release - Example for M551xx Control Plane Counters (2/2)
• Capacity problems can impact uplink as well as downlink end-user throughput
Measurement id Measurement Abbreviation Object level 5G21B 22R1 22R2
Feature ID
55136 Feature name
Enforced LTE measurement gap reports per Cell Comments LTEMG NRCELL 12 12 12
5GC00067955138 UL/DL FDM
Standalone (SA)scheduling
Central unit (CU) Radio admission control Allows to frequency
RSACUmultiplex two UEs in the same
NRCELL
NRCELL
59 slot.
59 This 59
is
55139 Standalone (SA) Distributed unit (DU) Radio admission control RSADU 39 41 46
55140 Standalone (SA) gNB traffic measurement especially effective
RSANBif many small packets are transmitted
NRBTS 3 3 in the
3
55141 NR NSA Signaling Radio Bearer in gNB-DU SRB3D NRCELL 2 2 2
55143 NR XN-C Interface signalling NRCELL level network NXNCC NRCELL 10 10 10
5GC000721
55144 PSCell load
NR mobility balancing
between gNB cell and E-UTRAN Cell Balances the sector load over multiple intra-band
NREMO Neighbour Relation 14 carriers
14 (FR2)
14
55145 NR RAN Sharing NRANS NRCELL / MCC-MNC 40 52 68
55146 NR Radio Bearer NRBC NRCELL 4 4 4
CB005892
55147 Frequency
NR Mobility CUdomain multiplexing for Extends 5GC000679
NMOCU functionality to FDD cells.21It also21enhances
NRCELL 23
NMODU NRCELL
FDD cells TDD cell multiplexing
NSL from 2 to 4 MNC,
UEs SD
in same 33
slot 35
55148 NR Mobility DU 1 1 1
55149 NR Slice NRBTS, 41
5GC002537
55150 FDM allocation
NR F1AP enhancements
Interface Report for CU per DU Removes the same-beam
NF1UU condition
NRDU for eCPRI 45
RUs 45 45
55151 NR Inter Frequency PSCell Change NIFC NRCELL 24 24 24
CB006667
55152 Increased
NR Measurementnumber
Gaps of FDM scheduled Allows up to 16 NRMG
UEs to be multiplexed
NRCELL in the same
12 slot12 (ABIL)12
55153 UEs per slot
NR Relations report NRREL
NGCFB
Neighbour Relation
NRCELL
5 5 8
55155 NG-C Flex SA mode 8 8 8
5GC001118
55157 256 QAM for PUSCH
NR Mobility Profiles Enables the more efficient 256QAM
NRMOP NRCELLmodulation
64 (ABIO)
64 64
CB007859
55160
55161
Spillover of CB006667 Increased
Admission Control with CU and for NSA NRPMQAP
Admission Control with CU and for SA NRPMQAP
Extends CB006667 functionality
ACCNQ
ACCSQ
also to ABIO
NRCELL / NRPMQAP
NRCELL / NRPMQAP
3
3
55162 number of FDM
X2 Connection Controlscheduled
NRPMQAP UEs per X2CCQ NRCELL / NRPMQAP 9
55163 NCG Interface NRPMQAP NGCCQ NRCELL / NRPMQAP 27
55165 slot for ABIO,
NR Resource ABIN,
Utilization per ASOE
CELL NRUC NRCELL 35
CB007797 55166 256 QAM
NR RRC for PUSCH
Interface Report per (FDD - DU
CELL for ABIL) Enables 256QAM for ABIL FDD
NRCCD NRCELL 4 4
26 RA57331-V-22R2 © Nokia 2022
26 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 26

PUSCH – Performance Analysis
Measurements
Analysis of the PUSCH congestion follows closely the procedure for PDSCH:
• Measurement
PUSCH slot utilization Interval
is a convenient first KPI
• Number of active uplink UEs can, together with the uplink user throughput, be investigated to have an indication
Measurement interval or granularity period (GP) is the length of the interval during
•
which data is collected for the counters in a measurement.
Differences between PUSCH and PDSCH analysis:
• Each measurement type can have a different measurement interval.
• Congestion has no impact on the uplink RLC delay (counters do not include scheduler waiting time)
•
• Measurement intervals are aligned within the hour at 00:00h and repeated periodically.
In TDD higher PUSCH slot utilization is common as UL:DL ratio is low
• • Supported
Typically, the uplinkmeasurement
path carries smallintervals:
ack for DL, 0 (disabled),
uplink 5,small,
PRB usage 15, so30,there
60ismin
muchor 6, 12,
higher 24 hours.
potential of
Default 15 minutes.
multiplexing
• PUSCH allocations for the (ghost) msg3 may consume substantial PUSCH capacity, in case, ghosts should be reduced
• In low loaded cells, a high share can be proactively scheduled slots, difficult to distinguish the case via OSS counters
• For high loaded cells, the PUSCH slots are instead simply used for the higher prioritized real traffic
27 RA57331-V-22R2 © Nokia 2022
27 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 27

PUSCH - KPIs
KPI id
Measurements
Reporting
NR_5111a Interval
5G Usage ratio of PUSCH data DATA_SLOT_PUSCH / UL_DATA_SLOTS Does not give the complete picture
slots over all UL data slots because there may not be
• Reporting interval is the time interval at which the PM data is reported/sent from
congestion even with gNB
high slot
to the NMS (NetAct) utilization. Good approximation
• A gNB can have only one reporting interval and it is configured at even NRBTS when PRACH slots are used
level
for PUSCH scheduling
•
NR_577c Like the measurement
5G PUSCH slot utilization interval, it is aligned with the hour at 00:00h
((DATA_SLOT_PUSCH + PRACH_SLOTS_PUSCH) Probably not relevant in 5G20A
compensated
• Supported for proactive
reporting UL / (UL_DATA_SLOTS
intervals: 5, 15, 30, 60+min.
PRACH_SLOTS_PUSCH))
Default 60 min.* where the “UL Prolong Timer” is
scheduling (UL_MAC_SDU_VOL_DTCH / used for proactive UL scheduling
(PUSCH_CP_INI_VOL_64TBL_MCS00…28 +
PUSCH_DFT_INI_VOL_64TBL_MCS00..27 +
PUSCH_CP_INI_VOL_256TBL_MCS00..27))
NR_5115a 5G PRB utilization for PUSCH PRB_USED_PUSCH / PRB_AVAIL_PUSCH Does not give the complete picture
because there can be congestion
even with low PRB utilization
NR_5121a 5G Average number of active ACC_UE_UL_DRB_DATA / Impacted by congestion but not by
UEs with data in the buffer for SAMPLE_CNT_NR_CELL_UTIL_UL DRX
DRBs in UL
28 RA57331-V-22R2 © Nokia 2022
28 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 28

PUSCH - KPIs
KPI id
Measurements
PM data
NR_5193b collection
5G Average process inACC_SCHED_UE_PUSCH
number of the gNB / Tells how well the FDM feature works
scheduled (FDM and MU-MIMO) (DATA_SLOT_PUSCH +
• Counters are collected in the PRACH_SLOTS_PUSCH)
UEs on PUSCH CU and in the DU of the gNB using PM providers.
NR_1394a 5G Average allocated PUSCH
• After being collected, they arePRB_USED_PUSCH
forwarded to/ the
(DATA_SLOT_PUSCH + Tells how well the scheduler is able to
PM collector in the central unit.
PRB size PRACH_SLOTS_PUSCH) fill the PRBs
• Upon
NR_5101b reporting
5G Average interval
MAC layer user 8 * UL_MAC_SDU_VOL_DTCH / Impacted by radio link quality, traffic
timer expiration,
throughput in uplink gNB (ACC_UE_UL_DRB_DATA * pattern, RACH and DL slot overhead
CU merges all files (DATA_SLOT_PUSCH_TIME / and multiple simultaneous users.
containing counters, DATA_SLOT_PUSCH)) Small data bursts will generate low
compress them and values
NR_1478asends them
5G UL RLC to NMSper
SDU throughput UL_RLC_VOL_UE_TPUT_QOS_05…20 / Excludes small data bursts
(NetAct)
DRB for QoS groups 5 to 20 UL_RLC_TIME_UE_TPUT_QOS_05...20
Timer:
PMCADM/reportingIntervalPm;
default 1h
29 RA57331-V-22R2 © Nokia 2022
29 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 29

5G Admission Control - CU and DU Functions
Index
CU and DU Functions
Radio admission control (RAC) in the CU is performing the following checks:
• Number of active UEs
• operating in SA mode
Optimization or NSA mode 3x per 5G cell group (NRCELLGRP)
Overview
• Number of active UEs • operating in SA mode
Optimization or NSA mode 3x per 5G cell (NRCELL)
Activities
• Number of non-GBR•DRBs Compatibility
of active UEsmatrix between
operating in SA 5G andorSRAN
mode releases
NSA mode 3x per 5G cell group (NRCELLGRP)
• • Quiz I
Number of non-GBR DRBs of active UEs operating in SA mode or NSA mode 3x per 5G cell (NRCELL)
• Number of users per• CP-UE
Counters
• Number of non-GBR•DRBs Keyper CP-UE
Performance Indicators
• • References
UE capabilities with regard to supported bandwidth and band combinations are checked
The admission control in the DU will check if there is enough PUCCH capacity:
• Depending on csiReportPeriodicity, rejections can happen with a relatively small number of users
• In practice, admission control rejections related to capacity issues are related to PUCCH capacity
30 RA57331-V-22R2 © Nokia 2022
30 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 30

5G Admission Control - Feature Summary
Counters
Feature Summary
Overview
•5GC000480
PM Counters areRadio Admission Controlcategorized
measurements for NSA mode 3xinoperation
groups related to a similar area or
5GC001836
function. Spillover from 5GC000480 Radio Admission Control for NSA mode 3x operation
5GC000876 Radio Admission Control - SA mode
• Each of those groups are the measurement types.
31 RA57331-V-22R2 © Nokia 2022
31 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 31

5G Admission Control - KPIs
Counters
Naming convention
KPI id KPI name Formula
NR_272b Finaladmission
5G Radio Counter ID
rejection SGNB_NSA_RAC_REJ_DUE_TO_CPUE
Counters ID / (SGNB_NSA_ADMISSION_REQ
can be divided into two+ parts:
ratio per cause lack of CP-UE SGNB_NSA_RAC_REJ_DUE_TO_CPUE + SGNB_NSA_RAC_REJ_DUE_TO_NGBR)
• Measurement ID
capacity
- First part of counter represent
NR_273b M55312C00001SGNB_NSA_RAC_REJ_DUE_TO_NGBR
5G Radio admission rejection / (SGNB_NSA_ADMISSION_REQ
Measurement
+
ID and starts with
ratio per cause lack of non- SGNB_NSA_RAC_REJ_DUE_TO_CPUE + SGNB_NSA_RAC_REJ_DUE_TO_NGBR)
GBR capacity letter ‘M’ – Every counter can be
NR_5247a Average connected users
Measurement ID Counter Number simply connected to proper +
(AVE_NUMBER_OF_NSA_USERS / AVE_NUMBER_OF_NSA_USERS_DENOM)
(AVE_NUMBER_OF_SA_RRC / AVE_NUMBER_OF_SA_RRC_DENOM)
measurement
NR_5248a Admission controlinrejections
measurement (SGNB_DU_NSA_ADMISSION_NO_PUCCH + SGNB_SA_DU_RAC_REJ_DUE_PUCCH) /
• Counter Number
due to lack of PUCCH (SGNB_DU_NSA_ADMISSION_REQ + SGNB_SA_DU_ADMISSION_REQ)
capacity
- Second part of counter stands for
Counter Number and starts with
How to read counter ID (above): letter ‘C’ – This is Index for every
• It is User Plane counter (M553xx)
• It’s ID within M55312 measurement is C00001 counter
32 RA57331-V-22R2 © Nokia 2022
32 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 32

KPI id
Counters
KPI name Formula
Radio5Gmeasurement
NR_5124b target
Average number of NSA levels (1/2)
AVE_NUMBER_OF_NSA_USERS / AVE_NUMBER_OF_NSA_USERS_DENOM
users
• Counters
NR_5125a 5G Maximumhave different
number of NSAcollection levels.
PEAK_NUMBER_OF_NSA_USERS
users
• All counters in a measurement group have the same managed object class (MOC) or
NR_5014c 5G Radio admission success (100 * SUM([SGNB_NSA_ADMISSION_SUCC]) /SUM([SGNB_NSA_ADMISSION_REQ] +
target level for collection.
ratio for NSA user [in CU] [SGNB_NSA_RAC_REJ_DUE_TO_CPUE] + [SGNB_NSA_RAC_REJ_DUE_TO_NGBR]
• Example object levels: +[SGNB_NSA_RAC_REJ_DUE_TO_NSA]))
NR_274b 5G Radio admission rejection SGNB_NSA_RAC_REJ_DUE_TO_NSA / (SGNB_NSA_ADMISSION_REQ +
• NRBTS: New Radio Base
ratio per cause lack of NSA
Station
SGNB_NSA_RAC_REJ_DUE_TO_CPUE + SGNB_NSA_RAC_REJ_DUE_TO_NGBR)
• NRCELL: New Radio Cell
user capacity
NR_5075a 5G NSA Admission control SGNB_DU_NSA_ADMISSION_NO_PUCCH / SGNB_DU_NSA_ADMISSION_REQ
• NRDU: New Radio Distributed Unit.
rejection ratio due to lack of
Similar to LNBTS level in LTE
PUCCH resources
• NRCUUP: New Radio CU-UP
• MNLENT: Management Layer Entity
• MRBTS/EQM: Equipment
33 RA57331-V-22R2 © Nokia 2022
33 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 33

KPI id
Counters
KPI name Formula
Radio5Gmeasurement
NR_5128b target
Average number of SA levels (2/2)
AVE_NUMBER_OF_SA_RRC / AVE_NUMBER_OF_SA_RRC_DENOM
RRC connected users
• There
NR_5129a is no NRCELLGRP
5G Maximum number of SA (sector)
PEAK_NUMBER_OF_SA_RRC_USERS
level
RRCfor PM counters
connected users collection.
NR_5162a 5G Radio admission success SGNB_SA_ADMISSION_SUCC / SGNB_SA_ADMISSION_REQ
• Forratio
postprocessing
for SA users [in CU]
purposes, it
NR_5079acan5Gbe derivedcontrol
SA Admission by aggregating
SGNB_SA_DU_RAC_REJ_DUE_PUCCH /
therejection
counters onto the
ratio due lack ofNRCELLs
under
PUCCHeach NRCELLGRP. SGNB_SA_DU_ADMISSION_REQ
resources
34 RA57331-V-22R2 © Nokia 2022
34 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 34

5G Admission Control – Case Example
Case Counters
example of Admission Control, 5G20B, NSA and SA mixed cell:
• Counter
Admission Aggregation
control rejections due to lack of PUCCH capacity in the cell is independent on mode, SA connection or
NSA
• • + Counters
SA can
NSA behavior be be
should aggregated
analyzed to to
getobjects that
a clear result are
• ‘above’
Example, them
left: SA loadin thecan
alone MOCnothierarchy.
explain the blocking
MRBTS
• • Example:
Example, NRCELL
right: combined counters
SA and ananalysis
NSA traffic be aggregated
shows a clear result NRBTS
to NRBTS, cluster (multiple NRBSs) or PLMN NRCELL
level.
NRCELLGRP
• Depending on the counter the aggregation can NRPMRNL

be sum, average…etc.
NRSCTP
• Counters have also their own aggregation level. NRDU
• Raw counters have 15 min. aggregation level LTEENB

giving the possibility of further aggregating NRCUUP
them to 30 min, 1h, 6 h…
35 RA57331-V-22R2 © Nokia 2022
35 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 35
Index
Index Introduction
Number of Users
Data Volume
• Quiz I
• Counters
• References
36 RA57331-V-22R2 © Nokia 2022
36 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 36
Number of Users
KPIs to measure number of users
KPIs
KPI idOverview
KPI name Formula SA / NSA
LTE_6435a Average EN-DC capable UEs with 4G AVG_CAP_UE_SCG / 100 NSA
• KPIs reflect the quality of a network by measuring the network performance, including
RRC connection
LTE_1907btrends inofthe
Share performance.
4G RRC connections done with (AVG_CAP_UE_SCG / 100) / RRC_CONNECTED_UE_AVG NSA
EN-DC capable UE
• KPIs are logical formulas based on counters:
NR_5124b 5G Average number of NSA users AVE_NUMBER_OF_NSA_USERS / NUMBER_OF_NSA_USERS_DENOM NSA
NR_5128b 5G Average number of SA RRC AVE_NUMBER_OF_SA_RRC / AVE_NUMBER_OF_SA_RRC_DENOM SA

connected users
NR_5415a 5G Average number of active UEs with (ACC_UE_DL_DRB_DATA - ACC_UE_DL_SLEEP_DATA) / Both

data in the buffer for DRBs in DL SAMPLE_CNT_NR_CELL_UTIL_DL
(excluding DRX)
NR_5121a 5G Average number of active UEs with ACC_UE_UL_DRB_DATA / SAMPLE_CNT_NR_CELL_UTIL_UL Both

• KPIs are
data inuniquely
the buffer for identified
DRBs in UL by:
• KPI ID (e.g. NR_5010a)
• KPI Name (e.g. 5G Contention free RACH setup attempts)
37 RA57331-V-22R2 © Nokia 2022
37 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 37
Number of Users
Examples from live network (NSA)
•
KPIs
5G19A networks where dominant user cases are FWA and MBB with smartphones.
• #Naming
connectedconvention
users much higher than # of active users, especially in smartphone user case.
• Proactive UL scheduling in use explaining why the number of UL active users is higher than the number of DL
active users.
– FWA: Connected users = 19 * active DL Overall KPI ID
Smartphone:
–Official Connected
KPIs ID can be dividedusers= 206 parts:
in to three * active DL
• Prefix
NR_5124b: Connected users:
• Prefix is saying that KPI belongs to 5G (to
average number of NSA users,
differentiate among other technologies)
i.e. number of users with
• DRBKPI Number
lest one 5G
-
at
Number is uniquely identifying certain KPI among

NR_5010a
NR_5120a: Active usersother
DL
(NR_5415a- KPI
fromVersion
22R1 Version
onwards) - Third part of KPI ID allows to maintain versions constant prefix
(e.g. when KPI formula is changed from release KPI number
NR_5121a: Active userstoUL
release)
FWA: Fixed Wireless Access

MBB: Mobile Broadband
38 RA57331-V-22R2 © Nokia 2022
38 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 38
Number of Users
NR_5415a
KPIs
NR_5415a: 5G Average number of active UEs with data in the buffer for DRBs in DL (excluding
Use Cases (1/2)
DRX): • Numbers of users
• 5G network usage • Data Volume
ACC_UE_DRB_DATA - ACC_UE_DL_SLEEP_DATA • Number of access attempts
• Ghost preambles
--------------------------------------------------------------------------------------
• Throughput • Packet delays within gNB
• Latency • PDCP SDU discards
SAMPLE_CNT_NR_CELL_UTIL_DL
• Capacity
• Cell availability • Admission control
• This
• KPI shows
NSA/SA the average number of PSCell or SCell UEs which
accessibility • have
PRACH buffered data in
utilization
PDSCH/PUSCH utilization
any
• DRB in downlink
NSA/SA direction (excluding DRX).
retainability •
• CCE load
• VoNR
• sample_cnt_nr_cell_util_dl
• Radio link quality
indicates the number of samples • Co-scheduled UEs
• CPU load (gNB-CU)
• Sampling period 1 slot
• Beamforming
• Mobility NSA/SA • Histograms of beam usage for preambles, PDSCH, PUSCH
• 5G carrier aggregation • RSRP difference between best and second-best beam
• Specific profile performance
• Interface performance (S1, NG, X2, Xn, F1, E1, front-
haul)
• BTS energy consumption
39 RA57331-V-22R2 © Nokia 2022
39 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 39
Index
KPIs
Introduction
Use Cases (1/2)
• 5G network usage Number of Users
• Ghost preambles Data Volume
• Throughput Number of Access Attempts
• Latency
• Capacity
• Cell availability
• NSA/SA accessibility
• NSA/SA retainability
• VoNR • UL & DL MCS distribution
• Radio link quality • UL & DL HARQ success ratio
• DL CQI histogram
• Beamforming
• PUSCH SINR, RSSI, Received signal power
• Mobility NSA/SA • PUCCH SINR
• 5G carrier aggregation • RLC PDU retransmissions / discards
• Specific profile performance • Radio link failures
• Interface performance (S1, NG, X2, Xn, F1, E1, front- • Beam recovery failures
haul)
• BTS energy consumption
40 RA57331-V-22R2 © Nokia 2022
40 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 40
Data Volume
Overview
•
Index
In the 5G RAN, the transferred data can be taken from many interfaces (S1, X2, F1) and
protocol layers (MAC, RLC, PDCP)
• For quick evaluation of the traffic volume, the easiest is to look either at the PDCP
layer (contains both 5G and 4GActivities
• Optimization EN-DC user plane traffic) or at the RLC layer (contains
5G user plane traffic)
• Check the section• onQuizthroughput
I KPIs for other possibilities
• PDCP layer counters• are also available in the LTE, both for all LTE traffic and specifically
Counters
for the EN-DC traffic
• received / sent
Key Performance via the X2 interface. This means that the EN-DC
Indicators
LTE traffic share of• the whole LTE traffic can be calculated
References
41 RA57331-V-22R2 © Nokia 2022
41 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 41
Data Volume
KPIs to measure data volume
Relevant 3GPP Specifications
KPI id KPI name Formula NSA / SA
NR_745a 5G Average PDCP throughput received over S1-U DL 8 * DL_PDCP_VOL_RCV_S1U_QOS_GRP_01...20 / NSA 4G + 5G
• TS28.550: Performance
GTP-U tunnel (Mbps) assurance. Describes the performance
(PERIOD_DURATION management framework
* 60 * 1000) legs
NR_748a
in general terms. Also, some requirements on
5G Average PDCP throughput sent over S1-U UL GTP-U
file formats etc.
8 * UL_PDCP_VOL_SNT_S1U_QOS_GRP_01...20 / NSA 4G + 5G
tunnel (Mbps) (PERIOD_DURATION * 60 * 1000) legs
NR_62a 5G DL RLC PDU throughput transmitted without 8*DL_RLC_VOL_TX_H_QOS_GRP_01...20 / (1000 * NSA 5G leg + SA
• TS28.552: 5G performance measurements. Describes the required counters in the 5G
repetitions by High RLC (Mbps) MEAS_PERIOD_NR_HIGH_RLC_REPORT)
NR_63a
RAN 5G
asULwell as in the 5G core network elements
RLC SDU throughput received without repetitions
(AMF / SMF / UPF / PCF / UDM) NSA 5G leg + SA
8*UL_RLC_VOL_RX_H_QOS_GRP_01...20 / (1000 *
by High RLC (Mbps) MEAS_PERIOD_NR_HIGH_RLC_REPORT)
E-UTRAN SCG split bearer’s PDCP PDU data volume

TS28.554: 5G end to end Key Performance Indicators. Uses the counters described in
LTE_6638b PDCP_PDU_X2_DL_SCG / 1000000 NSA 4G leg
• received on X2 interface from gNB (MB)
TS28.552
LTE_6643b
to build KPI formulas
E-UTRAN SCG split bearer’s PDCP PDU data volume PDCP_PDU_X2_UL_SCG / 1000000 NSA 4G leg
transmitted via X2 interface from eNB (MB)
TS32.425: E-UTRAN Performance Measurements For NSA option 3, the legacy RRC
LTE_1910b EN-DC share of total eNB PDCP data volume, downlink PDCP_PDU_X2_DL_SCG / (PDCP_PDU_X2_DL_SCG NSA 4G leg
• + PDCP_SDU_VOL_DL)
measurements
LTE_1911b
described on it also apply for
EN-DC share of total eNB PDCP data volume, uplink
EN-DC connections
PDCP_PDU_X2_UL_SCG / (PDCP_PDU_X2_UL_SCG NSA 4G leg
+ PDCP_SDU_VOL_UL)
• TR38.913: Study on scenarios and requirements for next generation access

technologies. Technical Report. It contains requirements for the 5G RAN
42 RA57331-V-22R2 © Nokia 2022
42 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 42
Data Volume
KPIs to measure data volume
Key Performance Indicators KPI
Operating Documentation
•
NR_1249a 5G and SRAN
5G Average PDCP22R2 BTSreceived
throughput Performance
over NG-U DL • 5G and SRAN 22R2 BTS Parameters
8 * DL_PDCP_VOL_RCV_NGU_QOS_GRP_01...20 /
SA
Measurements
GTP-U tunnel (Mbps) (PERIOD_DURATION * 60 * 1000)
NR_1250a 5G Average PDCP throughput sent over NG-U UL GTP-U 8 * UL_PDCP_VOL_SNT_NGU_QOS_GRP_01...20 / SA

tunnel (Mbps) (PERIOD_DURATION * 60 * 1000)
43 RA57331-V-22R2 © Nokia 2022
43 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 43
Index
Key Performance Indicators KPI
Introduction
Delta with Respect to 5G22R1
Number of Users
Excel file available through Discovery Center:
Data Volume
44 RA57331-V-22R2 © Nokia 2022
44 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 44

KPIs to measure the access attempts (NSA)
Tools
• LTE_6942b / LTE_6160b gives indication of how big is the EN-DC share of the total
UE logging
LTE connection setups
• QXDM/QCAT: for analysis of Qualcomm log files.
• Qualcomm MTP: Available for field trials along with other handsets based on Qualcomm
NR_5003b 5G Number of SgNB X2_SGNB_ADD_REQ_ACK_SENT + X2_SGNB_ADD_REQ_REJ_SENT NSA
chipsets.
addition requests
LTE_6942b SgNB Addition Preparation SGNB_ADD_PREP_ATT - SGNB_ADD_PREP_ATT_IE_HO_X2 NSA
Attempts for Initial Access
LTE_6160b Total E-UTRAN RRC SIGN_CONN_ESTAB_ATT_MO_S + SIGN_CONN_ESTAB_ATT_MT + LTE
Connection Setup Attempts SIGN_CONN_ESTAB_ATT_MO_D + SIGN_CONN_ESTAB_ATT_DEL_TOL +
SIGN_CONN_ESTAB_ATT_HIPRIO + SIGN_CONN_ESTAB_ATT_EMG +
SIGN_CONN_ESTAB_ATT_MO_VOICE + SIGN_CONN_ESTAB_ATT_OTHERS
45 RA57331-V-22R2 © Nokia 2022
45 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 45

KPIs to measure the access attempts (SA)
Reporting Suite Nokia Radio 5G
Introduction
Reporting Suite Nokia Radio 5G is designed to provide information for Service & Network Planning,
Service Creation, Service & Network Monitoring and Business Management.
Connecting
people
Performance
NR_5160b KPIs number
5G SA Total are used by different
of RRC operational areas for:
NRRCD_RRC_STPREQ_MO_SIGNALLING + NRRCD_RRC_STPREQ_MO_DATA + SA
connection establishment NRRCD_RRC_STPREQ_MT_ACCESS + NRRCD_RRC_STPREQ_EMERGENCY +
Network Dimensioning and
• attempts Optimization
NRRCD_RRC_STPREQ_HIPRIO_ACCESS +
NRRCD_RRC_STPREQ_MO_VOICECALL +
• Troubleshooting NRRCD_RRC_STPREQ_MO_VIDEOCALL + NRRCD_RRC_STPREQ_MO_SMS +
• Traffic Trend analysis forNRRCD_RRC_STPREQ_MPS
Long term planning + NRRCD_RRC_STPREQ_MCS
NR_5230a • 5G SA Number
Network of initial
Performance NNGCC_UE_CTXT_STP_REQ_RECD Connecting SA
context setup requests things
• ServiceatUsage
received gNB-CU
Pre-defined reports are available off-the-shelf and are grouped in various
5G reporting categories, offering 1000+ KPIs and 41 pre-defined reports.
Reporting Suite Nokia 5G runs on top of NetAct on Regional Cluster and

NPM on Global Cluster.
46 RA57331-V-22R2 © Nokia 2022
46 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 46

Examples from live networks (NSA)
Reporting Suite Nokia Radio 5G
Reports Overview
Changes between
5G21A v21.1.2 and 5G21B v21.2.1
New
Updated
Deleted
• Low-traffic 5G19B smartphone network, summarized • High-traffic 5G19A FWA network, summarized over all
over all the cells in the network the cells in the network
• Throughput and SgNB additions have highly fluctuating • Relatively stable KPI values
values due to low number of users
• Note that SgNB additions have opposite phase
compared to the throughput - this could be due to long
streaming connections in the evening
47 RA57331-V-22R2 © Nokia 2022
47 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 47
Pre-defined Reports – System Program
System Program provides a general view of the network status. With these reports the user has a high level overview
of the network performance and can easily spot if any problem occurs. These reports should be used to benchmark
the network.
These reports include Nokia 5G
most important KPIs, such as:
• Cell availability
• RACH setup
• RRC setup
• SgNB addition/reconfiguration
• UE releases
• SgNB releases
• SA / NSA handover
• BLER
• Packet delay
• CQI
• SINR
• RSSI
• Data volume and throughput
• Number of NEs
48 RA57340-V-22R2 © Nokia 2022
RA57331-V-22R2 48

RA57331-V-22R2 - LE05 - Network Usage Analysis - Internal - Version

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

RA57331-V-22R2 - LE05 - Network Usage Analysis - Internal - Version

Uploaded by

Copyright:

Available Formats

Network Usage Analysis

5G Radio Optimization Part 2, Nokia internal version

Copyright and confidentiality

2 RA57331-V-22R2 © Nokia 2022

Revision history and metadata

• sketch optimization-related processes on overview level

• distinguish measurements, counters and KPIs

• recall the Nokia 5G Performance Management Architecture

• list measurement types and KPI use cases

3 RA57331-V-22R2 © Nokia 2022

3 RA57340-V-22R2 © Nokia 2022

4 RA57331-V-22R2 © Nokia 2022

4 RA57340-V-22R2 © Nokia 2022

5 RA57331-V-22R2 © Nokia 2022

5 RA57340-V-22R2 © Nokia 2022

6 RA57331-V-22R2 © Nokia 2022

6 RA57340-V-22R2 © Nokia 2022

7 RA57331-V-22R2 © Nokia 2022

7 RA57340-V-22R2 © Nokia 2022

8 RA57331-V-22R2 © Nokia 2022

8 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

9 RA57331-V-22R2 © Nokia 2022

9 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

10 RA57331-V-22R2 © Nokia 2022

10 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

11 RA57331-V-22R2 © Nokia 2022

11 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

12 RA57331-V-22R2 © Nokia 2022

12 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

3. RF and mobility Optimization

13 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

14 RA57331-V-22R2 © Nokia 2022

14 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

15 RA57331-V-22R2 © Nokia 2022

15 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

16 RA57331-V-22R2 © Nokia 2022

16 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

17 RA57331-V-22R2 © Nokia 2022

17 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

18 RA57331-V-22R2 © Nokia 2022

5G Radio Interface Capacity

19 RA57331-V-22R2 © Nokia 2022

5G Radio Interface Capacity

20 RA57331-V-22R2 © Nokia 2022

20 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

21 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

22 RA57331-V-22R2 © Nokia 2022

22 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity

23 RA57340-V-22R2 © Nokia 2022

5G Radio Interface Capacity