New Node Performance Dashboard

National Tools Performance

NPPI National Planning, Performance & T-Mobile Confidential

1 Intelligence
New Node Performance Challenges
T-Mobile is investing heavily on modernizing our network and we
don’t have an advanced analytics that specifically focus for new
nodes

LTE Massive Outdoor Small

MIMO Cell

Micro Cell Outdoor DAS

RRH FEMTO Indoor

Cell DAS

3. Traditional
Optimization is not
sufficient anymore

NPPI National Planning, Performance &

2 Intelligence T-Mobile Confidential
New Node Performance Analytics
Solution for automated and effective way to identify new nodes,
immediate performance impact assessment & accountability
commitment
• What is the purpose?
• The solution will evaluate all new nodes impact based on automated
Pre/Post KPI assessment and calculated One score points that will award to
market for successful on-boarding. The solution will be developed in
IMNOS.

• How the tool will make an impact?

• Given T-Mobile expectation for the immediate investment return from the
new nodes. This new analytics will basically increase the focus and
commitment from the market to optimize new nodes

• Who will be the users?

• This will be primarily used by RF Market Engineers, Engineering
Managers and Directors
NPPI National Planning, Performance &
3 Intelligence T-Mobile Confidential
New Node Analytics Workgroup
This is the team behind for the creation of New Node Analytics

Regional Performance FSC Performance & Tools

• Nelson Ghogomu
• Sumit Sethi • Kiran Chaggar
• Alex Lefter • Michael Bascao
• Eduardo Melero-Bravo • Claudette Villanueva
• Alex Gardini • Ligia Lima
• SyedBasit Akram
• Maged Elsharkawy IMNOS
• Sivakumar Periyasamy • Naim Heddadji
• Costel Dragomir • Milind Divate
• Drew Locke
• Kien Tang
• Tuan Vu
NPPI National Planning, Performance &
4 Intelligence T-Mobile Confidential
 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
Assess performance of
the new node with
Methodology: the new node at site
respect to it’s Top 95%
level.
Nbrs.

Co-site neighbor cells will

always be part of the For the non-co-site neighbor cells:
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
handovers) to non-co- handover attempts to source site (500 for Small
site neighbors. non-co-site neighbors. Cell solutions).

NPPI National Planning, Performance &

5 Intelligence T-Mobile Confidential
 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
(a)   “> 30% Traffic Increase”  Midband Users >130% PRE Midband Users (Traffic Gain) and Sector Users/5Mhz > “MidLow_Unb”  Users/5MHz
Technology Add (MidBand) 80% Congestion Threshold Lowband >  Users/5MHz Midband &
Users/5MHZ Midband Post > Pre &
(b)   “High Users”  > 80% Congestion Threshold & Users/5Mhz Midband Post> Pre Users/5MHz Midband > 25
(a)   “>30% Traffic Increase(Low)”  Lowband Users > 130% PRE Lowband(Traffic Gain) & >80% Congestion “MidLow_Unb”  Users/5MHz
Technology Add (LowBand) Threshold  Lowband >  1.2*Users/5MHz
(b)   “High Users(Low)” Lowband Users/5Mhz > 80% Congestion Threshold & Users/5MHZ Lowband Post > 1.05 Midband & Users/5MHz Lowband >
*Pre 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
Small Cell (a)   “Congesting”  SC Users/5MHz > 15
(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

See Backup Slides for details.

NPPI National Planning, Performance & T-Mobile Confidential
6 Intelligence
 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%)

NPPI National Planning, Performance & T-Mobile Confidential

7 Intelligence
Criteria for a solution to pass
 Control KPIs are aggregated over 14 days, both for the Pre and for the Post
Analysis.
 Algorithm to freeze stable sites KPI:
 A solution is marked as “Passed” if Points > 95. 
 At this point, all KPIs are frozen, Post Analysis Start date is frozen and
solution gets 100 points.
 Otherwise, status is marked as “Fail”. 
 Solutions are evaluated every week.

 Dashboard data will be refreshed every Tuesday.

 South Region Capacity Team Report will be updated on Monday.
 Afterwards, TTS will refresh the dashboard on Tuesday.

Market and Region Points:

• NNP points are allocated (averaged) at market, region and national level.
• COW/Temp and DAS/In-Building Sites are not shown in the NNP dashboard

NPPI National Planning, Performance & T-Mobile Confidential

8 Intelligence
NNP Q1 ‘21
 Dashboard View: Cluster View
 Only solutions with Activation Date in Q4 ‘20 and Q1 ‘21 are taken into
account.
 Use 50 points for Capacity, 50 for performance. Total 100 points,
“Standard NNP”.
 OneScore: 16 points
1. Market Points: maximum of 8 points. 0, 4 or 8 points, based on
Points NNP Points OneScore
thresholds below.
< 96 0
>= 96 and < 98 4
>= 98 8

2. National Points: maximum of 8 points

NPPI National Planning, Performance &
9 Intelligence
 Baseline Reference Date NNP

The first time the solution

shows on the dashboard,
the “On-Air Date” matches
the “Baseline Reference
Date”.
“On-Air Date” can change
in the following weeks. See
details in this slide.
Solution Construction Start Date: Post Analysis Start Date: Site status warning if Fail
 From Element (only shown for  Current Date – 14 days Not count against market
reference)
-25 -24 -23 -22 -21 -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
6/12

6/15
6/16
6/17
6/18
6/19
6/20
6/21
6/22

6/24

6/29

7/10

7/17
7/18
7/19
7/20
7/21
7/22
7/23
7/24
7/25
7/26
6/10
6/11

6/13
6/14

6/23

6/25
6/26
6/27
6/28

6/30

7/11
7/12
7/13
7/14
7/15
7/16
7/1
7/2

7/4
7/5
7/6
7/7
7/8
7/9
7/3
Pass or
Fail
Baseline Reference Date
Pre Analysis Start Date: Baseline Reference Date:
 Baseline Reference Date – 25 days  New cell detected in OSS
 Cell unlocked, unbarred and unreserved.
 Cell shows non-null PM data for 3 days *
out of 14 analysis days 

*) RTWP is evaluated only for the last 7 days of the Post Analysis Period.
NPPI National Planning, Performance & T-Mobile Confidential
10 Intelligence
 Additional Features
Summary Issue key Status

Need to have 14 days in pre and post analysis. If there are missing some days in the post period, site should
RFA-17439 Closed
show as grey and not counted as degraded/improved.

Change the baseline dates reference for the two overlapping solutions deployed within 30 days period. In this
case, the Pre-Analysis Start Date shall be the oldest one of the 2 solutions. RFA-17813 Closed

Remove RTWP for Nokia AAFIA sites in NNP and give them 8.33 pts. RFA-17891 Closed
Bandwidth Expansions are shown in the dashboard, but do not count towards market or region points. RFA-18975 Closed
Give full RTWP points in case of RTWP Hot. RFA-19669 Closed
Exclude Ericsson AAS Sector Add solutions from market average, until Ericsson can support more than one
sector per site. RFA-19785 Closed

To be more accurate for the new 6 sector sites, leakage is aggregated at the site level. Therefore, the logic RFA-17978 Closed
uses the top 95% neighbor cells, gets the leakage at site level and compares the pre-post.

For RTWP, calculation needs to be changed from average to aggregate values for 7 days. For Nokia, it doesn't
matter. But for Ericsson it does, and it can cause different results in NNP and OneScore RTWP KPI. RFA-19757 Hold - TMO

If the baseline contains 1 major holiday, baseline should be moved back so that to ends right before the start
RFA-19795 Closed
of the holiday week.

If solution has lost more 20% traffic (Average RRC Users) compared to the baseline pre-COVID19 (weeks of
RFA-20525 Closed
March 6th and 13th), then it should get 8.3 points for the VoLTE Erlangs KPI.

If macro target offload sector has lost more 20% traffic (Average RRC Users) compared to the baseline pre- Internal Closed
COVID19 (weeks of March 6th and 13th), then the small cell gets 50 points for Capacity.

NPPI National Planning, Performance & T-Mobile Confidential

11 Intelligence
 Additional Features (II)
Summary Issue key Status
“Time to Fix” column has been added to the dashboard. It displays the time it took for that solution to pass
RFA-21214 Closed
since it came on-air.
If the solution’s bandwidth has been reduced between the baseline and the Post Analysis Period, relaxed
criteria shall be applied to the Throughput KPI:
If
Throughput >= 2 Mbps OR
Throughput >= 0.95*Throughput (Pre)
Then, 8.33 points (Color – GREEN) RFA-21597 Closed
ElseIf
Throughput is between 2 Mbps and 1 Mbps OR
Throughput  >= 0.7*Throughput (Pre)
Then, 4.165 points (Color – YELLOW)
Else, 0 points. (Color – RED)
B41 solutions added to NNP Dashboard. RFA-22036 Closed

NPPI National Planning, Performance & T-Mobile Confidential

12 Intelligence
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 : Every Tuesday, when the dashboard is refreshed, the U/U/U status of the solution is
checked:
 Cell Split: U/U/U at least once cell of the new site.
 Lowband Add: U/U/U all cells in the new Lowband layer.
 Midband Add: U/U/U all cells in the new Midband layer.
 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 Expansion: U/U/U all cells in the layer where bandwidth has been expanded.
Every Tuesday, when the dashboard is refreshed, Condition 1 is checked for every solution:
 If the solution already has an “On-Air Date”:
 If Condition 1 is TRUE, no action.
 If Condition 1 is FALSE, solution is removed 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, solution goes to the dashboard and “On-Air Date” is previous’
Friday date.
 If Condition 1 is FALSE, solution is kept out of the dashboard.

NPPI National Planning, Performance & T-Mobile Confidential

13 Intelligence
 Relaxed Thresholds for NSD solutions
 If a new site has an assigned “Target Offload Sector”, the solution is marked as a “Cell Split”. This is irrespective
of whether the POR “Plan Type Desc” is “Cell Split” or others (e.g. “coverage”, “Market Infill”…)
 Otherwise, the new site will be marked “NSD” in the Capacity KPI.
 The relaxed thresholds below are applied to the following types of solutions (RFA-20369):
 (“Network Activity” = Cell Split AND “Target Offload Sector” = N/A) OR
 (“Network Activity” = Small Cell AND “Target Offload Sector” = N/A) OR
 (All cells in the cluster are cells from the same site, i.e. the cluster doesn't have any cells from other sites)

VoLTE ERLANGS SIP DCR VoLTE AFR LEAKAGE THROUGHPUT

• If • If • If • If • If
VoLTE Erlang (Post) > 0 SIP Drops (Post) <= 20 AFR (Post) <= 1% OR Leakage <= 10% OR Throughput >= 2 Mbps
•Then, 8.33 points. OR AFR (Post) <= 1.05*AFR Leakage <= OR
•Else, 0 points. SIP DCR (Post) <= 2% (Pre) 1.05*Leakage (Pre) Throughput >=
OR •Then, 8.33 points. •Then, 8.33 points. 0.95*Throughput (Pre)
SIP DCR (Post) <= •If  •If  •Then, 8.33 points.
1.05*SIP DCR (Pre) AFR (Post) is between Leakage is between •If 
• Then, 8.33 points. 1% and 2% OR 10% and 20% OR Throughput is between
• If  AFR (Post) <= 1.3*AFR Leakage <= 2 Mbps and 1 Mbps OR
SIP DCR (Post) is (Pre) 1.3*Leakage (Pre) Throughput  >=
between 2% and 5% OR •Then, 4.165 points. •Then, 4.165 points. 0.7*Throughput (Pre)
SIP DCR (Post) <= •Else, 0 points. •Else, 0 points. •Then, 4.165 points.
1.3*SIP DCR (Pre) •Else, 0 points.
•Then, 4.165 points.
•Else, 0 points.
 Additionally, these thresholds are also applied to all solutions that came on-air during the first COVID-19
lockdown (between 3/15 and 6/30 of 2020). The only difference for this “COVID-19” sites is the Leakage KPI,
where the green threshold is 5% (instead of 10%) and the yellow threshold is 10% (instead of 20%).
NPPI National Planning, Performance & T-Mobile Confidential
14 Intelligence
Solutions not counting toward market avg
The following solutions are shown in the dashboard but don’t count toward the market average:
 Lowband Expansions
 Midband Expansions
 Ericsson AAS Sector Adds
 Sites that are failing the first time that they show on the dashboard (Post Analysis Start Date = On-Air
Date). Status will be shown as “Warning” instead of “Fail” just for that week.

NPPI National Planning, Performance & T-Mobile Confidential

15 Intelligence
 Backup slides

NPPI National Planning, Performance &

16 Intelligence T-Mobile Confidential
 Pre-Analysis Buffer NNP

-30 -29 -28 -27 -26 -25 -24 -23 -22 -21 -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

7/11

7/14
6/10
6/11
6/12
6/13
6/14
6/15
6/16
6/17
6/18
6/19
6/20
6/21
6/22
6/23
6/24
6/25
6/26
6/27
6/28
6/29
6/30

7/10

7/12
7/13

7/15
7/16
7/17
7/18
7/19
7/20
7/21
7/22
7/23
7/24
7/25
7/26
6/6
6/7

6/9

7/2

7/5

7/7
7/8
6/5

6/8

7/1

7/3
7/4

7/6

7/9
Longest buffer (8 days)

Shortest buffer --> 2 days

Baseline / Pre-Analysis
Pre-Analysis Buffer
Solution Activation Date
14-days Rolling Post-Analysis
First week to evaluate New Node
Second week to evaluate New Node
Consistent PM data and U/U/U

NPPI National Planning, Performance & T-Mobile Confidential

17 Intelligence
 Sector Add
Case a: Site level users shall not exceed (100+15)% * #Sectors_Added of the pre users/5MHz and sector level users/5MHz shall not exceed 80% of
max user capacity
• Site_RRC_Users_post(Mid) > (1 + 0.15 * #Sectors_Added) * Site_RRC_Users_pre(Mid) and 
• Sector_RRC_Users_5MHz_post(Mid) > 0.8 * UserCapacity_Max (measured at sector level, take the maximum of all sectors).

Observation -> “>30% traffic increase”  

Case b: Sector level post users/5MHz shall not exceed 80% of max user capacity, and if it does, it must have reduced by at least 25%.
• Sector_RRC_Users_5MHz_post(Mid) > 0.8 * UserCapacity_Max (measured at sector level, take the maximum of all sectors) and
• Sector_RRC_Users_5MHz_post(Mid) > 0.75 * [Sector_RRC_Users_5MHz_pre(Mid)] (measured at sector level, take the maximum of all sectors for
the post and compare to the maximum of all sectors for the pre).

Observation -> “Sector add still congesting”

NPPI National Planning, Performance & 18

18 Intelligence
 Sector Add
Case c: Site level traffic on mid band layer drops below 80% of the pre levels and the low traffic is not due to seasonality.
• Site Level Users/5Mhz < 80%
• Site Level Users > 150% Seasonal Low traffic

Observation -> “Low Mid Traf”

Case d:
• Otherwise

Observation -> “Sector add ok”

NPPI National Planning, Performance & 19

19 Intelligence
 BW Change (Mid Band)
Case a: Site level users shall not exceed 130% of the pre users and sector level users/5MHz shall not exceed 80% of max user capacity
• Site_RRC_Users_post(Mid) > 1.3 * Site_RRC_Users_pre_Mid and
• Sector_RRC_Users_5MHz_post(Mid) > 0.8 * UserCapacity_Max (measured at sector level, take the maximum of all sectors).

Observation -> “BW Changed: >30% Traffic Increase”

NPPI National Planning, Performance & 20

20 Intelligence
 BW Change (Mid Band)
Case b: Flag if sector level users/5MHz post (midband) is higher than pre and if sector level users/5MHz post (lowband) is higher than midband
• Sector_RRC_Users_5MHz_Post(Mid) > Sector_RRC_Users_5MHz_Pre(Mid) (measured at sector level, take the maximum of all sectors for the post
and compare to the maximum of all sectors for the pre) and
• Sector_RRC_Users_5MHz_Post(Low) > Sector_RRC_Users_5MHz_Post(Mid) (measured at sector level, take the maximum of all sectors for Lowband
and compare to the maximum of all sectors for Midband) and
• Sector_RRC_Users_5MHz_Post(Mid) > 25.

Observation -> “BW Changed: MidLow_Unb”

NPPI National Planning, Performance & 21

21 Intelligence
 BW Change (Mid Band)
Case c: Sector level users/5MHz shall not exceed 80% of max user capacity

• Sector_RRC_Users_5MHz_Post(Mid) > 0.8 * UserCapacity_Max (measured at sector level, take the maximum of all sectors).
• Sector_RRC_Users_5MHz_Post(Mid) > Sector_RRC_Users_5MHz_Pre(Mid) (measured at sector level, take the maximum of all sectors for the post
and compare to the maximum of all sectors for the pre)

Observation -> “BW Changed: High Users”

NPPI National Planning, Performance & 22

22 Intelligence
 BW Change (Mid Band)
Case d:
• Otherwise

Observation -> ”BW Changed: OK”

NPPI National Planning, Performance & 23

23 Intelligence
 BW Change (Low Band)
Case a: Site level users shall not exceed 130% of the pre traffic and sector level users/5MHz shall not exceed 80% of max user capacity
• Site_RRC_Users_post(Low) > 1.3 * Site_RRC_Users_pre(Low) and
• Sector_RRC_Users_5MHz_post(Low) > 0.8 * UserCapacity_Max (measured at sector level, take the maximum of all sectors).

Observation ->  “BW Changed: >30% Traffic Increase(Low)”

NPPI National Planning, Performance & 24

24 Intelligence
 BW Change (Low Band)
Case b: Flag if sector level users/5MHz post (lowband) is higher than midband and if sector level users/5MHz post (lowband) is higher than 25.
• Sector_RRC_Users_5MHz_post(Low) > 1.2*Sector_RRC_Users_5MHz_post(Mid) (measured at sector level, take the maximum of all sectors for
Lowband and compare to the maximum of all sectors for Midband) and 
• Sector_RRC_Users_5MHz_post(Low) > 50% of the Congestion Threshold (measured at sector level, take the maximum of all sectors).

Observation -> “BW Changed: MidLow_Unb”

NPPI National Planning, Performance & 25

25 Intelligence
 BW Change (Low Band)
Case c: Sector level users/5MHz (lowband) shall not exceed 80% of max user capacity
• Sector_RRC_Users_5MHz_post(Low) > 0.8 * UserCapacity_Max (measured at sector level, take the maximum of all sectors).
• Sector_RRC_Users_5MHz_post(Low) > Sector_RRC_Users_5MHz_pre(Low)

Observation -> “BW Changed: High Users(Low)”

NPPI National Planning, Performance & 26

26 Intelligence
 BW Change (Low Band)
Case d:
• Otherwise

Observation -> “BW Changed: OK”

NPPI National Planning, Performance & 27

27 Intelligence
 Cell Split (New Site for Capacity)
Case a: Flag if target offload sector level users/5MHz post (midband) is higher than 60% of pre and congesting
In the target offload sector:
• Sector_RRC_Users_5MHz_post(Mid) > 0.6 * Sector_RRC_Users_5MHz_pre(Mid) and
• Sector_RRC_Users_5MHz_post(Mid) > 80% of Congestion threshold

Observation -> “Low Offload(1MACRO)”

NPPI National Planning, Performance & 28

28 Intelligence
 Cell Split (New Site for Capacity)
Case a: Flag if target offload sector level users/5MHz post (midband) is higher than 70% of pre and congesting
In the target offload sector:
• Sector_RRC_Users_5MHz_post(Mid) > 0.7 * Sector_RRC_Users_5MHz_pre(Mid) and
• Sector_RRC_Users_5MHz_post(Mid) > 80% of Congestion threshold

Observation -> “Low Offload(2MACRO)”

NPPI National Planning, Performance & 29

29 Intelligence
 Cell Split (New Site for Capacity)
Case b: Sector level post traffic shall not exceed 80% of max user capacity
• Sector_RRC_Users_5MHz_post(Mid) > 0.8 * UserCapacity_Max (measured at sector level, take the maximum of all sectors)

Observation -> “CELL SPLIT: Congesting”

NPPI National Planning, Performance & 30

30 Intelligence
 Cell Split (New Site for Capacity)
Case c:
• Otherwise

Observation -> “Cell Split: OK”

NPPI National Planning, Performance & 31

31 Intelligence
 NSD (New Site Design)
Case a: Sector level post traffic shall not exceed 80% of max user capacity
• Sector_RRC_Users_5MHz_post(Mid) > 0.8 * UserCapacity_Max (measured at sector level, take the maximum of all sectors)

Observation -> “NSD: Congesting”

NPPI National Planning, Performance & 32

32 Intelligence
 NSD (New Site Design)
Case b:
• Otherwise

Observation -> “NSD: OK”

NPPI National Planning, Performance & 33

33 Intelligence
 Small Cell
Case a: Flag if:
• small cell sector level users/5MHz post (midband) is less than 3, or
• if target offload sector level users/5MHz pre (midband) is greater than 0 and small cell sector level users/5MHz is less than 10% of
target offload sector users/5MHz pre minus post (midband)

• SmallCell_Sector_RRC_Users_5MHz_post(Mid) < 3 or
• Toffload_Sector_RRC_Users_5MHz_pre(Mid) > 0 and SmallCell_Sector_RRC_Users_5MHz_post(Mid) < 0.1 *
(Toffload_Sector_RRC_Users_5MHz_pre(Mid) - Toffload_Sector_RRC_Users_5MHz_post(Mid))

Observation -> ”Small Cell: LowOffload”

NPPI National Planning, Performance & 34

34 Intelligence
 Small Cell
Case b: Flag if small cell sector level users/5MHz is greater than 15

• SmallCell_Sector_RRC_Users_5MHz_post(Mid) > 15

Objective: Observation -> ”Small Cell: Congesting”

NPPI National Planning, Performance & 35

35 Intelligence
 Small Cell
Case c:

• Otherwise

Observation -> ”Small Cell: OK”

NPPI National Planning, Performance & 36

36 Intelligence
Control and Monitored KPI Reference
Control KPIs are typical KPIs that market and national engineering use for different network activities.

Type KPI
Control VoLTE Erlangs
Control SIP DCR
Control VoLTE AFR
Control Leakage
Control Average UE DL Throughput
Case 1 / Ericsson - High N&I (All antenna lines > -106 dBm) (Q3 2020)
Case 1 / Nokia – High RTWP (All antenna lines >-86 dBm:20MHz, >-87.2
dBm:15MHz, >-89 dBm:10MHz, <-92 dBm:5MHz) (Q3 2020)
Case 2 - Not All Rx Antenna Lines are working (Ant count is 1 or 3)
Control RTWPDocument
(RTWP KPI is evaluated for ALL cells in the site where the new solution Case 3 - Imbalance Antenna Lines (5 dB)
has been implemented. This is regardless what type of solution has been Case 4 / Ericsson - Low N&I (All antenna lines N&I < -121.9 dBm)
implemented and regardless whether Cluster Level or Site Level mode has Case 4 / Nokia – Low RTWP (All antenna lines <-101.5 dBm:20MHz, <-102.7
been selected) dBm:15MHz, <-104.5 dBm:10MHz, <-107.5 dBm:5MHz)
Monitored RRC Users / 5 MHz
Monitored VoLTE Calls
Monitored LTE Data AFR
Monitored RRC Re-establishment Failure Rate
Monitored Intra LTE HO Failure Rate
Monitored % Poor CQI
Monitored UE Power Headroom
Monitored Traffic DL
Monitored ERAB DCR
Monitored Volte Calls Going to 3Gor2G
Monitored Congestion
Monitored Average Cell Throughput

NPPI National Planning, Performance & T-Mobile Confidential

37 Intelligence
 Thanks!

NPPI National Planning, Performance &

38 Intelligence T-Mobile Confidential