4G NNP KPI Understanding and

Optimization
Dileep Kumar
Arpit Dhawan

1 © 2022 Nokia
Nokia internal use
Point to be covered:

• 4G NNP KPI Understanding

 Capacity KPI
 Volte Erlang
 SIP DCR%
 VOLTE AFR%
 Leakage
 UE DL Throughput
 RTWP

• 4G NNP KPI Optimization

 Basic checks
 Parameter alignment as per market guidelines/ pre configuration
 Soft Optimization

2 © 2022 Nokia
Nokia internal use
 4G NNP KPI Understanding

3 © 2022 Nokia
Nokia internal use
NNP Evaluation Methodology
NNP Points per solution (max 100)

Capacity Points (max 50) Performance Points (max 50)

VoLTE Erlang SIP DCR VoLTE AFR Leakage UE DL Throughput RTWP

NNP Dashboard views:

Cluster Level (default view, used for OneScore) Site Level

Assess performance of the

Assess performance of the
new node with respect to it’s Methodology:
new node at site level.
Top 95% Nbrs.

Co-site neighbor cells will

For the non-co-site neighbor cells:
always be part of the cluster.

Calculate the top 95% . Remove from cluster all Remove from cluster all
neighbor list using the target cells whose target cells that have less
handover attempts contribution is less than than 10,000 handover
(subtracting ping-pong 2.5% of the total the attempts from the source site
handovers) to non-co-site handover attempts to non- (500 for Small Cell
neighbors. co-site neighbors solutions).

4 © 2022 Nokia
T-Mobile Confidential
Nokia internal use
Capacity KPI (max 50 points)
 Any new node that met the objective will be rewarded with 50 Points otherwise 0 Points.
 RRC Connected Users per 5 MHz:
– Threshold for sectors in 2 Mbps polygon: 50 users (65 if inactivityTimer = 10 s)
– Threshold for sectors in 4 Mbps polygon: 35 users (40 if inactivityTimer = 10 s)

Solution Congestion/Offload Criteria(Fail Scenarios) Traffic Balancing (Fail Scenarios)

(a) “>30% Traffic Increase”  Site Level Users >15% * #Sectors Added * Site Level Users PRE (Traffic Gain) & Sector Users/5Mhz>80% Congestion
Threshold
Sector Add
(b) “Still Congesting”  Sector Users/5Mhz > 80% of Congestion Threshold & <25% Offload
(c) “Low Mid Traf.”  Site Level Users < 80% PRE Site Level Users (Traffic loss) & Site Level Users > 150% Seasonal Low Traffic

“MidLow_Unb”  Users/5MHz
(a) “> 30% Traffic Increase”  Midband Users >130% PRE Midband Users (Traffic Gain) and Sector Users/5Mhz > 80% Congestion Threshold Lowband > Users/5MHz Midband &
Technology Add (MidBand)
(b) “High Users”  > 80% Congestion Threshold & Users/5Mhz Midband Post> Pre Users/5MHZ Midband Post > Pre &
Users/5MHz Midband > 25

“MidLow_Unb”  Users/5MHz
(a) “>30% Traffic Increase(Low)”  Lowband Users > 130% PRE Lowband(Traffic Gain) & >80% Congestion Threshold Lowband > 1.2*Users/5MHz
Technology Add (LowBand)
(b) “High Users(Low)” Lowband Users/5Mhz > 80% Congestion Threshold & Users/5MHZ Lowband Post > 1.05 *Pre Midband & Users/5MHz Lowband >
0.5*Congestion_Threshold

(a) “Low Offload(1MACRO)”  Offload Sector Users/5MHz > 80% of Congestion Threshold & Offload Sector < 40% Offload
Cell Split (b) “Low Offload(2MACRO)”  Offload Sector Users/5MHz > 80% of Congestion Threshold & Combined Offload Sector < 30% Offload
(c) “Congesting”  Cell Split Sector > 80% Congestion Threshold & Offload Sector Users/5Mhz > 0

NSD (a) “Congesting”  NSD > 80% of Capacity Threshold and No record of Offload Sector
(a) “Congesting”  SC Users/5MHz > 15
Small Cell
(b) “Low Offload”  SC Users/5MHz < 3 OR SC < 10% of Offload Sector Users Pre-Post

“L25 Add OK - PRE OCT162020 ACTIVATION”

(a) “L25 Add: Congesting”  L25 Sector Users > 80% of Congestion Threshold & Midband Sector < 80% Congestion Threshold
“L25 Add OK”
Technology Add (a) “L25 Add: Congesting”  L25 Sector Users > 80% of Congestion Threshold & Midband Sector < 80% Congestion Threshold
(L25) (b) “L25 Add: LowOffload – Midband Still Congesting”  Midband Sector > 80% Congestion Threshold & Midband Sector Offload < 20% (Pre – Post) & L25 Sector Users < 80% of Congestion
Threshold
(c) “L25 Add: >30% Midband Traffic Increase”  Site Level Midband Users > 130% PRE Midband Users & MB Sector Users > 80% of Cong. Threshold
(d) “L25 Add: >30% Lowband Traffic Increase”  Site Level Lowband Users > 130% PRE Lowband Users & LB Sector Users > 80% of Cong. Threshold
5 © 2022 Nokia
T-Mobile Confidential
Nokia internal use
Performance KPIs (max 50 points)
Performance KPIs
 Volte Erlang
 SIP DCR%
 VOLTE AFR%
 Leakage
 UE DL Throughput
 RTWP (KPI reference slide for RTWP criteria)
 RTWP KPI is evaluated for ALL cells in the site where the new solution has been implemented.
This is regardless what type of solution has been implemented and regardless whether Cluster
Level or Site Level mode has been selected.

Point system for every Performance KPI:

 KPI improved, or degraded not more than 5% - Full points (8.33)
 KPI degraded between 5 & 30% - Half points (4.16)
 KPI degraded more than 30% - ZERO Points
 Additionally, if the post value is below the "hard" threshold, the KPI gets Full points (8.33).
 Hard Thresholds are only applicable to SIP DCR (0.3%), VoLTE AFR (0.32% for Nokia and 0.25%
for Ericsson) and Leakage (0.43%) - Applicable to all solutions other than NSD

6 © 2022 Nokia
T-Mobile Confidential
Nokia internal use
Checking U/U/U Status
The below Unlocked/Unbarred/Unreserved check is done to identify the solution’s “On Air Date”. This is done on top of the current methodology used by
the Capacity Team to identify the “Baseline Reference Date”.

CONDITION 1 : The below unlocked/unbarred/unreserved check shall be done on top of the current methodology used by Basit to identify the Solution
Activation Date. If a solution doesn’t fulfill Condition 1, it shall be removed from the dashboard.
Daily when the dashboard is refreshed, check the unlocked/unbarred/unreserved status of the solution.
Cell Split: U/U/U at least one cell of the new site.
Lowband Add:
 Lowband Add: L7 - U/U/U all cells in the L7 layer (cell name starts with "D")
 Lowband Add: L6 - U/U/U all cells in the L6 layer (cell name starts with "E")
Midband Add:
 Midband Add: L21- U/U/U all cells in the L21 layer (cell name starts with "L")
 Midband Add: L21_Carrier_2- U/U/U all cells in the L21 layer (cell name starts with "L")
 Midband Add: AWS3 - U/U/U all cells in the AWS3 layer (cell name starts with "F")
 Midband Add: L19 - U/U/U all cells in the first L19 layer (cell name starts with "B" and ends with "1")
 Midband Add: L19_Carrier_2- U/U/U all cells in the secondL19 layer (cell name starts with "B" and ends with "2")
L25 Add:
 L25 Add - U/U/U all cells in the first L25 layer (cell name starts with "T" and ends with "1")
 L25_Add: Carrier_2- U/U/U all cells in the second L25 layer (cell name starts with "T" and ends with "2")
 L25_Add: Carrier_3- U/U/U all cells in the third L25 layer (cell name starts with "T" and ends with "3")
Sector Add - U/U/U at least one cell of the new sector.
Small Cell - U/U/U at least one cell of the new cell.
Bandwidth
7
Expansion: follow the same rules as for Lowband Add, Midband Add and L25 Add.
© 2022 Nokia
T-Mobile Confidential
Nokia internal use
Checking U/U/U Status
CONDITION 1 : The below unlocked/unbarred/unreserved check shall be done on top of the current methodology used by Basit to identify the
Solution Activation Date. If a solution doesn’t fulfill Condition 1, it shall be removed from the dashboard.
Daily when the dashboard is refreshed, check Condition 1 for every solution.
 If the solution already has an “On-Air Date”:
 If Condition 1 is TRUE, no action.
 If Condition 1 is FALSE, remove solution from the dashboard.
 If the solution doesn’t have an “On-Air Date” (either because it’s new or because it was removed in a previous weekly report):
 If Condition 1 is TRUE, “On-Air Date” shall be previous’ Friday date.
 If Condition 1 is FALSE, remove solution from the dashboard.

Nokia the parameters to looks for:

 LNCEL_administrativeState
 SIB_primPlmnCellres
 SIB_cellBarred

Other NNP Dashboard criterion:

 Cell Availability greater than 90%
 48 hr Alarm clearance

8 © 2022 Nokia
T-Mobile Confidential
Nokia internal use
Checking U/U/U Status
CONDITION 1 : The below unlocked/unbarred/unreserved check shall be done on top of the current methodology used by Basit to identify the
Solution Activation Date. If a solution doesn’t fulfill Condition 1, it shall be removed from the dashboard.
Daily when the dashboard is refreshed, check Condition 1 for every solution.
 If the solution already has an “On-Air Date”:
 If Condition 1 is TRUE, no action.
 If Condition 1 is FALSE, remove solution from the dashboard.
 If the solution doesn’t have an “On-Air Date” (either because it’s new or because it was removed in a previous weekly report):
 If Condition 1 is TRUE, “On-Air Date” shall be previous’ Friday date.
 If Condition 1 is FALSE, remove solution from the dashboard.

Nokia the parameters to looks for:

 LNCEL_administrativeState
 SIB_primPlmnCellres
 SIB_cellBarred

Other NNP Dashboard criterion:

 Cell Availability greater than 90%
 48 hr Alarm clearance

9 © 2022 Nokia
T-Mobile Confidential
Nokia internal use
 4G NNP KPI RCA and
Optimization

10 © 2022 Nokia
Nokia internal use
Capacity KPI Optimization:
 PBL alignment
 Load balancing (IRFIM/LNHOIF/AMLEPR definition check and parameter alignments.)PBL Setting
 Cell utilization (Check BH RRC Users)
 Traffic Balancing and traffic sharing to neighbouring cells.
Basic Checks

VoLTE Erlang:
 Power parameter optimization (pMAX/dlcellpwrred/dlrsboost/PRACHCS- Source & Target cells)
 RET Optimization
 HO Optimization (CIO, A3Offset and hysteresis tuning etc)

11 © 2022 Nokia
Nokia internal use
SIP DCR Optimization:
 Site configuration checks.
 Alarm, RTWP & UL Interference check
 Parameters Audit as per parameter baseline.
 PCI collision and Confusion check.
 Physical RF optimization.
 Mobility optimization

12 © 2022 Nokia
Nokia internal use
VoLTE AFR:
 Average UE distance or TA pattern analysis
 Alarm and RTWP imbalance check
 Azimuth and Antenna height pre-post comparison

13 © 2022 Nokia
Nokia internal use
Throughput KPI:

14 © 2022 Nokia
Nokia internal use
Parameter and Feature optimization for Throughput KPI:
Parameter/ Feature
Problem
Tech Problem Subcategory Possible Parameter/ Feature Remarks
Category Parameter Range Pre Recommended
Optimization
LTE Coverage Overshooting RET - - - Reduce in step.
LTE Coverage Overshooting dlrsboost -3,0,1.77,3,4.77,6 dB - - Reduce in step.
LTE Coverage Overshooting dlcellpwrred 0…...20 dB - - increase in step.
indicates the maximum number of HARQ transmissions in DL that is
LTE Radio schedular harqMaxTrDl 1 to 16 5 7
configured for each UE at initial access to a specific cell.
Indicates the maximum number of HARQ transmissions in UL that is
LTE Radio schedular harqMaxTrUl 1 to 28 5 7
configured for each UE at initial access to a specific cell.
LTE Radio Bad radio dlOlqcEnable True/ False FALSE TRUE If dlOlqcEnable is set to 'true', dlTargetBler must be configured.
LTE Radio Bad radio dltargetBLER 0.1…..99.9% 10 12 BLER target for downlink LA in %.
Load Balancing and HO- Optimize According to Margin for the Event A3 for SCell discovery measurement- A neighbor
LTE Capacity A3offset -15 to 15 dB -
Mobility requirement becomes offset better than the PCell.
Missing Freq definition
LTE Capacity Load Balancing and HO - - - -
(IRFIM/LNHOIF)
Transport/ Load LTE-1.4, 3,5,10,15,20 MHz
LTE Capacity dlchBW/ chBw - - increase according to requirement and market guideline.
Balancing NR- 20,30,40,50,60,70,80,90,100 MHz
LTE/NR Capacity Load Balancing and HO Missing Anchor definition - - - -
NR Coverage Overshooting tilt Offset 6,5,4…..-4,-5,-6 - - increase in step. (-ve to +ve)
Low Throughput- UL
NR Radio ulprogranttimer 0 to 3000 ms (step 10) Blank 1200 ms Duration time for uplink proactive grants
Grants issue
Threshold for consecutive DTX for CSI/BSI reports to detect radio
NR Radio RLF based CSI/BSI rlpDetCsiBsiThreshold 0 to 10000 75 10000
link problems.
ulSChedTimeInterval (N41 only/ N71 Targeted time interval for proactive UL resource assignment for each
NR Radio schedular 0.2 to 1000 - 4
remained same) connected user.
Bad radio(T310
This timer is used for detecting physical layer problems for the PS-
supervises the recovery
NR Radio t310 0,50,100,200,500,1000, 2000, 4000, 6000 ms - 2000 Cell, i.e. upon receiving N310 consecutive 'out-of-sync' indications
from physical layer
from lower layers
problems)
NR Radio schedular/ Beamforming actPdschAtSsbSlots True/ False FALSE TRUE Activation flag for PDSCH at SSB slots

NR Radio schedular/ Beamforming actPdschRmCsirsForTracking True/ False FALSE TRUE Activation flag for CSI-RS for tracking rate matching for PDSCH
NR Radio schedular actPRACHMultiplexing True/ False FALSE TRUE Activation flag for PRACH slot uplink channel multiplexing
NR Radio schedular csireportperiodicity 20, 40, 80, 160, 320 slots - 80 slots This parameter defines the CSI reporting periodicity

NR Radio DRX drxInactivityTimer 0,1,2,3,4,5,6,8,10,20,30,40,50,60,80 ms - 80ms DRX active time after a PDCCH which indicates a new transmission.
NR Radio schedular actProactUlScheduling True/ False FALSE TRUE Activation flag for UL proactive scheduling
NR Radio DRX actCDrx True/ False FALSE TRUE Activation flag for the connected DRX function
5GC002538 PDSCH Extension in SSB
NR Radio schedular/ Beamforming True/ False FALSE TRUE -
and TRS slots
15 © 2022 Nokia
Nokia internal use
PRACHCS TMO Guidelines:

16 © 2022 Nokia
Nokia internal use
Nokia internal use