You are on page 1of 67

RU40 System Introduction

1. Capacity Related New Counters and KPI Analysis


2. WBTS and WCELL Capacity Impact Analysis

2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


RU40 Project Team
Project Management:
Jey Sachchi (jey.sachchi@nsn.com)

RU40 Capacity Stream: RU40 Performance Stream:

Sasi Sasitharan (sasi.sasitharan@nsn .com) Eva Garcia (eva.garcia@nsn.com)


Subhanjan Dasgupta (subhanjan.dasgupta@nsn.com) Sergio Elias (sergio.elias@nsn.com)
Ranjeet B Singh (ranjeer.b.singh@nsn.com) Gurajala Balaji (balaji.gurajala@nsn.com)
Amit Khurana (amit.khurana@nsn.com) Pavan Kumar (pavan.s.kumar@nsn.com)

RU40 Design: RU40 FOA Team:


Martin Elsey (martin.elsey@nsn.com)
Kenni Rasmussen (kenni.rasmussen@nsn.com) Marjanul Bahar (marjanul.bahar@nsn.com)
Thanassis Giortzis (thanassis.giortzis@nsn.com) Michiel Van Rooijen (Michiel.van-roojan@nsn.com)
Ali Raza (alli.rasa@nsn.com)
Prakasn Devnani (praksha.devnani@nsn.com)

2 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Contents
RRC Re-establishment analysis – new counter introduction

RTWP Too Low – new counter introduction

RRC Connection Setup due to AC failures – new counter introduction

RAB Connection Setup Failures for CS voice due to AC – new counter introduction

Percentage of PS Blocks Caused by AC UL power, DL power and Code

Mass Event Handler – new counters introduction

Paging performance and capacity analysis

LTE PS Incoming ISHO Capacity and Performance

WBTS and WCEL Capacity Impact Analysis

3 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


RU40 New Counter Introduction:

Voice calls terminated during RRC Connection


Re-establishment procedure
2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
RT RRC Re-establishment: New Counter Analysis
 In RU40 a new counter has been introduced to monitor number of voice calls terminated during
RRC Connection Re-establishment procedure.

PI Id Counter Name Description


M1006C270 CS_CALL_TERM_RE_E The number of CS voice calls terminated during RRC connection re-establishment procedure.
ST This counter can be used to analyze the cases where the user terminates the call because it
becomes mute for a while during re-establishment, and thus the user experiences a drop even if the call
could recover soon after that.

 This counter can be used to analyse the cases where the user terminates the call because it
becomes mute for a while during re-establishment, and thus the user experiences a drop even if
the call could recover soon after that.
 The RRC Re-establishment feature allows re-establishment of a CS RAB after a temporary loss
of radio link synchronisation.
 At present T314 timer is set to 6s (RNC level + PRFILE parameters)

5 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


RT RRC Re-establishment: New Counter Analysis Cont...

UE Node B RNC MGW

ure
Serving RNC
UE in Cell_DCH state
fail
link
dio
Ra NBAP: Radio Link Failure
NBAP: Radio Link Deletion
Coverage hole
T314 Current setting (RNC)= 6s
RANAP: IU Release Command
[RACH] RRC: Cell Update

UE loses coverage:
• BTS sends radio link failure
• RNC starts T314 timer
• UE goes to Cell_FACH state M1006C270 CS_CALL_TERM_RE_EST
The number of CS voice calls terminated during RRC connection re-establishment
procedure. This counter can be used to analyze the cases where the user terminates
UE regains coverage within T314: If T314 expires: the call because it becomes mute for a while during re-establishment, and thus the
• UE sends Cell Update • All RABs and Iu are released by RNC user experiences a drop even if the call could recover soon after that.
• RNC sends Cell Update Confirm, • UE goes to Idle mode
UE in Cell_DCH Updated: When the RNC receives RANAP: IU RELEASE COMMAND or RANAP: RAB
• RNC sends RB reconfiguration ASSIGNMENT REQUEST requesting to release CS RAB while the RNC is waiting for
• UE sends RB reconfiguration confirm
RRC connection re-establishment to happen.

Signalling Flow

6 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


RT RRC Re-establishment: New Counter Analysis Cont...
RT RRC Re-establishment Success Rate and Attempts (KT09)
 The RRC Re-establishment performance for 12000 100

KT09 is shown in 1st chart. 10000 90

RT Re-est Succes Rate


RT Re-sst Attempts
8000 80

6000 70

 The 2nd chart provides the counts of voice 4000 60

calls terminated during RRC Connection Re- 2000 50

establishment procedure (RU40 new counter). 0 40

11/01/2014

13/01/2014

15/01/2014

17/01/2014

19/01/2014

21/01/2014

23/01/2014

25/01/2014

27/01/2014

29/01/2014

31/01/2014

02/02/2014

04/02/2014

06/02/2014

08/02/2014

10/02/2014

12/02/2014

14/02/2014

16/02/2014

18/02/2014

20/02/2014

22/02/2014
 It can be seen that on average there are only Three UK - Sum of RT RRC Connection Re-Establishment Count
T-Mobile - Sum of RT RRC Connection Re-Establishment Count
Three UK - Average of RT RRC Connection Re-establishment Success Rate
around 50-60 calls are terminated by users T-Mobile - Average of RT RRC Connection Re-establishment Success Rate

across the RNC. CS Call Terminations During RRC Connection Re-Establishment - RU40 (KT09)
120

 Good proportion of the voice call terminations 100 Voice calls


terminated during

Call terminations #
are reported from EE network. 80 RRC Connection Re-
60
establishment
procedure.
 Based on the observation (small number of 40 Only ~60
terminations per
terminations), it is evident that T314=6s is an 20
day
appropriate setting for the MBNL network. 0

11/01/2014

19/01/2014

21/01/2014

23/01/2014

31/01/2014

02/02/2014

04/02/2014

12/02/2014

14/02/2014

16/02/2014
13/01/2014

15/01/2014

17/01/2014

25/01/2014

27/01/2014

29/01/2014

06/02/2014

08/02/2014

10/02/2014

18/02/2014

20/02/2014

22/02/2014
7 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
Three UK T-Mobile
RU40 New Counter Introduction:

RTWP Too Low


2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
RTWP Too Low - New Counter Analysis
 This counter provides number of total uplink power (RTWP) measurement report samples in
which the power value is less than -110dBm.
 A new KPI “Total Uplink Too Low Percentage” can be created (see Appendix 1).
 This KPI quantifies the percentage of time that the total uplink interference floor is less than -110
dBm.
 As an example the table below show a site in KT09 reporting 12-13% of the samples remains
within the RTWP Too Low category. Date RNC Name WBTSI d RTWP Tool Low %
2/17/14 KT09 13804 13.02%
2/18/14 KT09 13804 13.15%
2/19/14 KT09 13804 12.95%
2/20/14 KT09 13804 11.57%
2/21/14 KT09 13804 13.33%
2/22/14 KT09 13804 12.15%
2/23/14 KT09 13804 10.62%

 Total uplink interference levels of below this value can indicate potential antenna line failures,
loose feeder , MHA failures, PA failures or failures amongst other devices such as combiners.
 A scheduled report can be executed in Business Object to capture cells with high “RTWP Too
Low” values.
9 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
RU40 New Counter Introduction:

RRC Setup, RAB Setup and PS Block (9 counters)


2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
RRC Connection Setup Failures due to AC: New KPI analysis
 Existing RRC Setup failures due to admission control counter are updated either based on
uplink, downlink or codes.
 RU40 new counters to show detail AC failure causes (Service Level measurement –
M1001)
 Can be used for routine capacity monitoring

PI Id Counter Name Description


The number of RRC setup failures caused by Admission Control because of uplink power
M1001C731 RRC_CONN_STP_FAIL_AC_UL
limitation. M1001C3 is also updated along with this counter.
The number of RRC setup failures caused by Admission Control because of downlink power
M1001C732 RRC_CONN_STP_FAIL_AC_DL limitation. M1001C3 is also updated along with this counter.
The number of RRC setup failures caused by Admission Control because of downlink
M1001C733 RRC_CONN_STP_FAIL_AC_COD
spreading code congestion. M1001C3 is also updated along with this counter.

11 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


RRC Connection Setup Failures due to AC: New KPI analysis Cont...
RRC Setup FR due AC - UL power, DL power and Code Congestion (KT09) RRC Setup FR due AC - UL power, DL power and Code Congestion (KT09)
0.2 7000000 1.2 13000000

6000000 1 12500000

RRC Conn Setup Att


RRC Conn Setup Att

RRC Setup FR (%)


0.15 12000000
RRC Setup FR (%)

5000000 0.8
4000000 11500000
0.1 0.6
3000000 11000000
0.4
2000000 10500000
0.05
1000000 0.2 10000000
0 0 0 9500000

20/01/2014

22/01/2014

28/01/2014

30/01/2014

01/02/2014

07/02/2014

09/02/2014

14/02/2014

16/02/2014

22/02/2014
16/01/2014

18/01/2014

24/01/2014

26/01/2014

03/02/2014

05/02/2014

11/02/2014

13/02/2014

18/02/2014

20/02/2014
18/01/2014

22/01/2014

24/01/2014

28/01/2014

03/02/2014

09/02/2014

13/02/2014

15/02/2014

19/02/2014

21/02/2014
16/01/2014

20/01/2014

26/01/2014

30/01/2014

01/02/2014

05/02/2014

07/02/2014

11/02/2014

17/02/2014
Three UK - Sum of Rrc Conn Stp Att T-Mobile - Sum of Rrc Conn Stp Att
Three UK - Average of RRC Setup FR due AC UL POWER RNC_3200a T-Mobile - Average of RRC Setup FR due AC UL POWER RNC_3200a
Three UK - Average of RRC Setup FR due AC DL POWER RNC_3201a 3 New KPIs T-Mobile - Average of RRC Setup FR due AC DL POWER RNC_3201a 3 New KPIs
Three UK - Average of RRC Setup FR due AC Code RNC_3202a T-Mobile - Average of RRC Setup FR due AC Code RNC_3202a

 Based on the counters available in RU40, there are 3 new KPIs can be created (Appendix 2)
 These KPIs can be used quantify RRC Setup failures which are rejected because of RNC
connection admission control determines there is limited uplink power, downlink power and
downlink spreading code congestion.
 For example in KT09:
 Very small % of attempts are rejected due to code congestion on some selected days
 Very small % of attempts are rejected due to downlink power on some selected days
12 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
RAB Connection Setup Failures for CS Voice Due to AC: New KPI analysis
 RAB Setup failure for CS voice counter is updated either based on uplink, downlink or codes
 In RU40 there are 3 new counters available to show details AC failure causes - 3 new KPIs
can be created (Appendix 3)
PI Id Counter Name Description
The number of RAB setup failures caused by admission control because of uplink power limitation
M1001C734 RAB_STP_FAIL_CS_VOICE_AC_UL
for CS voice. M1001C80 is also updated along with this counter.
The number of RAB setup failures caused by admission control because of downlink power
M1001C735 RAB_STP_FAIL_CS_VOICE_AC_DL
limitation for CS voice. M1001C80 is also updated along with this counter.
The number of RAB setup failures caused by admission control because of downlink spreading code
M1001C736 RAB_STP_FAIL_CS_VOICE_AC_COD
congestion. M1001C80 is also updated along with this counter.

RAB Setup Access FR for CS Voice due to UL power, DL power and Code RAB Setup Access FR for CS Voice due to UL power, DL power and Code
Congestion (KT09) Congestion (KT09)
1200000 500000
1.4 1.4

RAB Setup CS Voice Att


RAB Setup CS Voice Att
1.2 1000000 1.2 400000

RAB Access FR (%)


RAB Access FR (%)

1 800000 1
300000
0.8 600000 0.8
0.6 0.6 200000
400000
0.4 0.4
200000 100000
0.2 0.2
0 0 0 0

18/01/2014

22/01/2014

28/01/2014

01/02/2014

05/02/2014

09/02/2014

13/02/2014

19/02/2014
16/01/2014

20/01/2014

24/01/2014

26/01/2014

30/01/2014

03/02/2014

07/02/2014

11/02/2014

15/02/2014

17/02/2014

21/02/2014
18/01/2014

22/01/2014

28/01/2014

01/02/2014

05/02/2014

09/02/2014

13/02/2014

19/02/2014
16/01/2014

20/01/2014

24/01/2014

26/01/2014

30/01/2014

03/02/2014

07/02/2014

11/02/2014

15/02/2014

17/02/2014

21/02/2014

T-Mobile - Sum of Rab Stp Comp Cs Voice Three UK - Sum of Rab Stp Comp Cs Voice
T-Mobile - Average of RAB Setup Access FR for CS Voice due to UL PW RNC_3203a Three UK - Average of RAB Setup Access FR for CS Voice due to UL PW RNC_3203a
13 T-Mobile - Average of RAB Setup Access FR for CS Voice due to DL PW RNC_3204a 3 New KPIs©2013 Nokia SolutionsThree
andUKNetworks.
- Average of All
RABrights reserved.
Setup Access FR for CS Voice due to DL PW RNC_3204a 3 New KPIs
T-Mobile - Average of RAB Setup Access FR for CS Voice due to Code- RNC_3205a Three UK - Average of RAB Setup Access FR for CS Voice due to Code- RNC_3205a
2/28/2014
Percentage of PS Blocks Caused by AC UL power, DL power and Code
Congestion
 There are 3 new counters introduced (Packet Call measurement – M1022) - 3 new KPIs are
introduced (see Appendix 4)
PI Id Counter Name Description
M1022C234 PS_SETUP_FAIL_AC_UL_NRT The number of packet call setup failures caused by admission control because of uplink power
limitation for PS NRT calls. M1022C9 or M1022C10 is also updated along with this counter.
M1022C235 PS_SETUP_FAIL_AC_DL_NRT The number of packet call setup failures caused by admission control because of downlink
power limitation for PS NRT calls. M1022C9 or M1022C10 is also updated along with this
counter.
M1022C236 PS_SETUP_FAIL_AC_COD_NRT The number of packet call setup failures caused by admission control because of downlink
spreading code congestion. M1022C9 or M1022C10 is also updated along with this counter.

 The new KPIs in the next slides quantifies the percentage of PS Connection Blocks caused by
Admission Control due to:
 Uplink power limitation
 Downlink power limitation
 Spreading code congestion

 All RRC Setup, RAB Setup and PS Blocks KPIs are created in BO and they useful for routine
14 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
capacity monitoring
Percentage of PS Blocks Caused by AC UL power, DL power and Code
Congestion Cont...
PS Setup FR due to AC UL PW NRT RNC 3206a New KPI PS Setup FR due to AC DL PW NRT RNC 3207a New KPI
0.14 1.4
PS Setup FR due to AC UL PW NRT (%)

PS Setup FR due to AC DL PW NRT (%)


0.12 1.2
0.1 1
0.08 0.8
0.06 0.6
0.04 0.4

0.02 0.2
0
0

01/01/2014
04/01/2014
07/01/2014
10/01/2014
13/01/2014
16/01/2014

25/01/2014
28/01/2014
31/01/2014
03/02/2014
06/02/2014
09/02/2014
12/02/2014
19/01/2014
22/01/2014

15/02/2014
18/02/2014
21/02/2014
21/01/2014
23/01/2014
25/01/2014
27/01/2014
29/01/2014

02/02/2014
04/02/2014
06/02/2014
08/02/2014
10/02/2014

16/02/2014
18/02/2014
20/02/2014
19/01/2014

31/01/2014

12/02/2014
14/02/2014
Three UK T-Mobile Three UK T-Mobile

PS Setup FR due to AC Code NRT RNC 3208a New KPI


 These new KPIs to be closely monitored and
PS Setup FR due to AC Code NRT (%)

0.16
0.14
0.12
proactive actions can be taken.
0.1
0.08
 At present PS Setup Failure AC Uplink power,
0.06 Downlink power and Code Congestion are low for
0.04
0.02 both EE and 3UK networks, instantaneous peaks
0
are observed due increase in traffic.
20/01/2014

24/01/2014
26/01/2014
28/01/2014
30/01/2014
01/02/2014
03/02/2014

07/02/2014
09/02/2014

13/02/2014
15/02/2014
17/02/2014
19/02/2014
21/02/2014
22/01/2014

05/02/2014

11/02/2014

15 2/28/2014 Three UK T-Mobile ©2013 Nokia Solutions and Networks. All rights reserved.
RU40 New Counter Introduction:

Mass Event Handler


2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
Mass Event Handler: New Counter Introduction
 There are 2 new counters introduced in RRC Signalling Measurements (M1006)
PI Id Counter Name Description
M1006C301 MEH_INCR_TVM_PEND The number of times when the RNC configures increased Traffic Volume Measurement pending time for
_TIM the UE due to high cell load detected by MEH functionality. Counter is updated when the RNC sends RRC:
MEASUREMENT CONTROL to the UE with an increased Traffic Volume Pending time due to high cell
load.
M1006C302 MEH_INCR_CQI_CYCL The number of HS-DSCH allocations where increased CQI feedback cycle is configured for the UE due to
E high cell load detected by MEH functionality. Counter is updated when the first HS-DSCH flow is allocated
for the UE in a cell. This can be initial allocation during RAB setup, state transition to Cell_DCH, user plane
setup from DCH 0/0, serving cell change, channel type switch or HHO

MEH_INCR_TVM_PEND_TIM MEH_INCR_CQI_CYCLE

 Both FOA RNCs are showing large attempts where increased CQI feedback cycle and increased
traffic volume measurement pending time are applied at high cell load conditions (Detected by
MEH functionality).
17 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
Mass Event Handler: New Counter Introduction Cont.....
 There are 2 new counters introduced in RU40 in Cell Resource Measurements (M1000)
PI Id Counter Name Description
M1000C406 MEH_ACTIVE_DURATI The state of MEH is sampled once per second and if the state is active, the counter is incremented by
ON value 1. Sampling interval 1s
M1000C407 MEH_ACTIVATIONS The number of times when Mass Event Handler load state is activated in a cell. Counter is updated when
the state of MEH restriction changes from inactive to active.

 Mass Event Handler Active Duration (seconds):


 This KPI provides the total duration for which the cell is in a Mass Event Handler load state.
 Improvement of this KPI is possible through offloading traffic to other cells or systems or by
optimisation actions such as limiting cell coverage, antenna tilts or azimuth changes.
 Capacity upgrades can also be used to prevent high occurrences of Mass Event Handler
use.

 Average Duration Of Mass Event Handler Load State (seconds):


 This KPI provides the average duration for which the cell is in a Mass Event Handler load
state.
 This KPIs is the ration of MEH Active Duration and number of MEH activations
18 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
Mass Event Handler: New Counter Introduction Cont.....
 Heavily loaded sites in KT09 shows increased MEH usage (MEH duration + Number of MEH activations)
 Voice and PS Accessibility severely impacted during the weekend due to B2B site 40530/90530 going out of service. Back in service ~12:00
on Weds 5th. This B2B accounts for ~5% of all PS attempts on KT09. This has forced traffic onto neighboring B2B 40414/60414, which has
become seriously overloaded. As a result, 40414/60414 and 40530/90530 have been excluded from the stats.

MEH Duration (KT09 sites) MEH Activations (KT09 sites)


250000 140
40414
120
200000
91628 100
150000 80

100000 60
60414
40
50000
20
0 0
28/01/2014

29/01/2014

30/01/2014

31/01/2014

01/02/2014

02/02/2014

03/02/2014

04/02/2014

05/02/2014

06/02/2014

07/02/2014

28/01/2014

31/01/2014

01/02/2014

02/02/2014

03/02/2014

04/02/2014

05/02/2014

06/02/2014

07/02/2014

08/02/2014
08/02/2014

29/01/2014

30/01/2014
13818 14984 16803 21359 40530 41592 41628 13818 14984 16803 21359 40530
48853 49347 60414 90362 90382 90524 90530 41592 41628 48853 49347 60414
91132 91347 91628 94669 40414 90362 90382 90524 90530 91132
19 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
LTE PS Incoming ISHO Performance

2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


LTE PS Incoming ISHO Performance
 The following LTE PS Incoming ISHO performance measures are analysed for FOA RNCs.
 LTE Incoming Handover Prepare Success Rate (%)
 LTE Incoming Handover Success Rate (%)

 There were no impacts were observed due to the activation of RU40

 Performance charts are not included in this slide pack

21 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Paging Performance and Capacity Analysis:

High and Low Priority drop, Paging Success Rate,


Paging load and Deleted Paging messages
2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
23
Paging Drop High Priority (3UK) Paging Drop High Priority (3UK)

0
100000
200000
300000
400000
500000
600000
2/28/2014
0
100000
120000
140000

20000
40000
60000
80000
01/01/2014 01/01/2014
environment.
03/01/2014 03/01/2014
05/01/2014 05/01/2014
07/01/2014 07/01/2014
09/01/2014 09/01/2014
11/01/2014 11/01/2014
13/01/2014 13/01/2014
15/01/2014 15/01/2014
17/01/2014 17/01/2014
19/01/2014 19/01/2014
21/01/2014 21/01/2014
23/01/2014 23/01/2014

Three UK
Three UK
25/01/2014 25/01/2014
27/01/2014 27/01/2014
29/01/2014 29/01/2014
31/01/2014 31/01/2014
02/02/2014 02/02/2014
T-Mobile

T-Mobile
04/02/2014 04/02/2014
06/02/2014 06/02/2014
Paging Drop High Priority (KT20)

Paging Drop High Priority (KT09)


08/02/2014 08/02/2014
10/02/2014 10/02/2014
12/02/2014 12/02/2014
14/02/2014 14/02/2014
16/02/2014 16/02/2014
18/02/2014 18/02/2014
20/02/2014 20/02/2014
22/02/2014 22/02/2014
0
1

0
5
10
15
20
25
30
35
0.1
0.2
0.3
0.4
0.6
0.7
0.8

0.5
0.9

Paging Drop High Priority (EE) Paging Drop High Priority (EE)
Paging Capacity and Performance Analysis

Paging Drop Low Priority (3UK) Paging Drop Low Priority (3UK)
0
2000000
4000000
6000000
8000000
10000000
12000000
0
1000000
1500000
2000000
2500000
3000000
3500000
4000000

500000

01/01/2014 01/01/2014
03/01/2014 03/01/2014
05/01/2014 05/01/2014
07/01/2014 07/01/2014
09/01/2014 09/01/2014
11/01/2014 11/01/2014
13/01/2014 13/01/2014
15/01/2014 15/01/2014
17/01/2014 17/01/2014
19/01/2014 19/01/2014
21/01/2014
©2013 Nokia Solutions and Networks. AllThree

21/01/2014
rights

23/01/2014 23/01/2014
Three UK

25/01/2014 25/01/2014
27/01/2014 27/01/2014
29/01/2014 29/01/2014
UKreserved.

31/01/2014 31/01/2014
T-Mobile
T-Mobile

02/02/2014 02/02/2014
04/02/2014 04/02/2014
06/02/2014 06/02/2014
Paging Drop Low Priority (KT09)
Paging Drop Low Priority (KT20)

08/02/2014 08/02/2014
10/02/2014 10/02/2014
12/02/2014 12/02/2014
15/02/2014 15/02/2014
 High Priority and Low Priority Paging Drops: Drop volumes are comparable to RU30

17/02/2014 17/02/2014
19/02/2014 19/02/2014
21/02/2014 21/02/2014
0
0
500

1000
2000
3000
4000
5000
6000
7000
1000
1500
2000
2500
3000

Paging Drop Low Priority (EE) Paging Drop Low Priority (EE)
Paging Capacity and Performance Analysis Cont....
 Paging Success Rate in Cell_PCH: Step change observed with RU40 upgrade due to a
planned correction in cell update counter to improve counter behaviour and bring the PCR below
100%.
Paging Success Rate in Cell_PCH State (%) - KT20 Paging Success Rate in Cell_PCH State (%) - KT20
105 104

102
100
100
95
98
90
96 Success Rate is above 100%
85 94
Success Rate is above 100%
80 92

75 90

03/01/2014
05/01/2014

11/01/2014
13/01/2014
15/01/2014

21/01/2014
23/01/2014

29/01/2014
31/01/2014
02/02/2014

08/02/2014
10/02/2014

16/02/2014
19/02/2014
01/01/2014

07/01/2014
09/01/2014

17/01/2014
19/01/2014

25/01/2014
27/01/2014

04/02/2014
06/02/2014

12/02/2014
14/02/2014
03/01/2014
05/01/2014

11/01/2014
13/01/2014
15/01/2014

21/01/2014
23/01/2014

29/01/2014
31/01/2014
02/02/2014

08/02/2014
10/02/2014

16/02/2014
19/02/2014
01/01/2014

07/01/2014
09/01/2014

17/01/2014
19/01/2014

25/01/2014
27/01/2014

04/02/2014
06/02/2014

12/02/2014
14/02/2014
Three UK T-Mobile Three UK T-Mobile

 The correction was implemented to the counter [CELL_UPD_AFTER_PAG_CELL_PCH] which


forms the numerator of the PSR formula as follows.
Paging Success Rate in Cell_PCH State (RNC_1215b): 100* SUM [CELL_UPD_AFTER_PAG_CELL_PCH]
--------------------------------------------------------------
SUM [PAGING_OCCASION_CELL_PCH]

24 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Paging Capacity and Performance Analysis Cont...
 There is no change to the existing Paging Success Rate formula. The PCR formula in Ryder
Extensive template is still valid.
KPI Store
From MBNL/Ericsson official KPI document

 No deleted paging messages observed in pre and post RU40 environments


 Both EE and 3UK CS Core Networks reports stable paging performance (Idle+PCH) from the
Core Network point of view.
 Paging load performance on both FOA RNCs showed no impact due to RU40 introduction.
 Paging delay for 3UK is slightly higher (40ms) compared to EE.

25 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


RU40 System Introduction

WBTS and WCELL Capacity Impact Analysis

2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Introduction
 WBTS and WCELL capacity measures are analysed for FOA RNCs based RAN counters and
KPIs.
 This slide pack mainly cover the results from KT09 which was upgraded to RU40 on 27/01/2014.
 The live network FOA began with 2 weeks benchmarking and characterisation and followed by 2
weeks post activation monitoring and analysis.
 The FOA RNC is bordered by 9 RNCs
 Current software versions:
 RNC: RN 7.0 CD1.0
 WBTS: WN7.0
 RNC KT09 description:
RMKT09
RNC Name RMKT09
RNC ID 146
RNC Type RNC2600
Number of WBTSs 262
Number of blocked WBTSs 8
Number of WCEL 2113
Number of HSDPA enabled cells 1810
Number of HSUPA enabled cells 1808

27 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS and WCELL Capacity Impact Analysis Methodology
 WBTS capacity impact analysis is based on the following measures together with relevant breach
thresholds.
 Top busy sites are analysed to quantify the impacts due to RU40 upgrade

WBTS Capacity

CE/SU Usage/ HSDPA Users/ Radio Link


Utilisation Throughput Capacity

 WCELL capacity impact analysis concentrates on the capacity measures presented in the block
diagram.
Radio Interface

Uplink Downlink Common Channelisation


28 2/28/2014
Interference Power Channel Code Tree
©2013 Nokia Solutions and Networks. All rights reserved.
WBTS Capacity: Licensed and Configured Users/Throughput (M5008) - 3UK
 The busiest site from 3UK showed no KT09: WBTS41628
(3UK)
impact due to RU40 upgrade.

 For both, HSUPA and HSDPA it is possible


to monitor licensed number of users and
throughput . The resulting values come from
HSDPA and HSUPA processing set license
keys loaded on the BTS.
 In order to detect possible commissioning
KT09: WBTS41628
problems, there is a dedicated counter to (3UK)
monitor configures HSDPA and HSUPA
user/throughput. This value comes from BTS
commissioning parameters.
 Licensed type of counters are based on
installed license keys
 Configured type of counters are based on
commissioned number of HSPA processing
sets
29 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
WBTS Capacity: Licensed and Configured Users/Throughput (M5008) - EE
 The busiest site from EE showed no KT09: WBTS91628
(EE)
impact due to RU40 upgrade.

 For both, HSUPA and HSDPA it is possible


to monitor licensed number of users and
throughput . The resulting values come from
HSDPA and HSUPA processing set license
keys loaded on the BTS.
 In order to detect possible commissioning
KT09: WBTS91628
problems, there is a dedicated counter to (EE)
monitor configures HSDPA and HSUPA
user/throughput. This value comes from
BTS commissioning parameters.
 Licensed type of counters are based on
installed license keys
 Configured type of counters are based on
commissioned number of HSPA processing
sets
30 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
WBTS Capacity: Subunit Usage (M5008 measurements)
KT09: WBTS41628
 The busiest sites showed no impacts (3UK)
due to RU40 activation.

Max HSUPA

M5008C35
Usage
Max used CEs
M5008C6,C9
Total Subunits

Max SU utilization
M5008C39

M5008C38

KT09: WBTS91628
M5008C12/C15
Max. R99 used

(EE)
CE DL/UL
HSDPA

(fixed)
usage

31 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: Subunit Usage (M5008 measurements) Hourly Stats
KT09: WBTS41628
 The busiest sites showed no (3UK)
impacts due to RU40 activation.

Max HSUPA

M5008C35
Usage
Max used CEs
M5008C6,C9
Total Subunits

Max SU utilization
M5008C39

KT09: WBTS91628
(EE)
M5008C38

M5008C12/C15
Max. R99 used
CE DL/UL
HSDPA

(fixed)
usage

32 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: Used R99 CE (M5008 and M5006 measurements)
KT09: WBTS41628
 The busiest sites showed no impacts due (3UK)
to RU40 activation.

 Difference between M5006C3/M5006 and


M5008C12/M5008C15 is only aggregation
level (in case of BTS with 1 LCG results are
identical).
 In Flexi Rel.2 HW these counters
calculates all DCH and additional CCCH
used resources. KT09: WBTS91628
(EE)
 If there is Rel.3 HW these counters
calculates all DCH used resources only.
 M5006 counters can be used for LCG level
monitoring.

33 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: BTS Capacity Monitoring – R99 CE Utilisation
KT09: WBTS41628
 The busiest sites showed no impacts due (3UK)
to RU40 activation.

 In case of multiple LCG – R99 CE


utilisation distribution KPI’s cam be used.
 Should be monitored per LCG
 CE R99 utilisation distribution rate
provides information about the percentage
of measured events which indicate the KT09: WBTS91628
(EE)
Channel Elements Usage Ratio.
 Own distribution KPIs for uplink and
downlink.

34 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: HSPA Processing Set Utilisation
 WBTS Level monitoring counters (M5008) are used to monitor HSPA Processing Set Utilisation.
 Minimum, Maximum and Average utilisation are monitored separately for HSDPA and HSUPA.

PI Id Counter Name % PI Id Counter Name %


M5008C22 MIN_HSDPA_PS_UTIL_RAT % M5008C25 MIN_HSUPA_PS_UTIL_RAT %
M5008C23 AVG_HSDPA_PS_UTIL_RAT % M5008C26 AVG_HSUPA_PS_UTIL_RAT %
M5008C24 MAX_HSDPA_PS_UTIL_RAT % M5008C26 MAX_HSUPA_PS_UTIL_RAT %

35 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: HSPA Processing Set Utilisation Cont.... KT09: WBTS41628
(3UK)
 The busiest sites showed no impacts due
to RU40 activation.

 HSUPA PS utilisation ratio is calculated as


percentage of the used PS from the licensed
PS.
 PS utilisation ratio is based on 3
conditions:
 Throughput utilisation
KT09: WBTS91628
 Number of users, and (EE)
 HW utilisation of HSUPA
 For the purpose of this counter, in each
sample period, all conditions are calculated.
The biggest percentage value is used.

36 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: HSDPA Processing Set Utilisation
KT09: WBTS41628
 The busiest sites showed no impacts due (3UK)
to RU40 activation.

 HSDPA PS utilisation ratio is calculated as


percentage of the used PS from the licensed
PS.
 HSDPA PS utilisation ratio is based on 2
conditions:
 Throughput utilisation and
 Number of users KT09: WBTS91628
(EE)
 For the purpose of this counter, in each
sample, both conditions need to be
calculated. The bigger percentage should be
used.

37 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: HSPA Users and User Utilisation (M5008 measurements)
 The busiest sites showed no impacts due to RU40 activation (user utilisation and setup failures
– HSDPA)
KT09: WBTS41628 KT09: WBTS91628
(3UK) (EE)

38 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: HSPA Users and User Utilisation (M5008 measurements)
 The busiest sites showed no impacts due to RU40 activation (user utilisation and setup failures
– HSUPA)
KT09: WBTS41628 KT09: WBTS91628
(3UK) (EE)

39 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: Radio Link Setup Load in BTS
 The control plane at the BTS refers to processing of C-NBAP and D-NBAP messages.
 The system uses C-NBAP for the initial radio link (RL) setup signaling between RNC and BTS
common channel measurements.
 The system uses D-NBAP for signaling of the RL re-configurations, RL additions, and deletions.
 This load can be monitored with M5004 counters, additionally in high load situation, the
following counters may be updated.
 M1001C4 RRC Setup failures due BTS and
 M1006C203 RRC Connection Reject due to Iub Overload
 If there is problem with BTS control plane load - Check the air interface and the BTS BB
capacity. Congestion of these causes overload at the BTS control plane.
 The signaling load in the WBTS measurement (M5004) measures the radio link capacity on the
BTS level.

40 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WBTS Capacity: Radio Link Setup Load in BTS Cont...
 The busiest sites showed no impacts due to RU40 activation (RL Set up Load)

KT09: WBTS41628 KT09: WBTS91628


(3UK) (EE)

41 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WCEL Capacity: Common channel capacity

The busiest cells showed no impacts due to RU40 activation.


KT09: WCEL41628C7 KT09: WCEL91628B2
(3UK) (EE)

42 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WCEL Capacity: HSDPA Channelization Code Usage Duration

The busiest cells showed no impacts due to RU40 activation.


KT09: WCEL41628C7 KT09: WCEL91628B2
(3UK) (EE)

43 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


WCEL Capacity: Spreading Factor Blocking Rate

The busiest cells showed no impacts due to RU40 activation.


KT09: WCEL41628C7 KT09: WCEL91628B2
(3UK) (EE)

44 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Conclusions and Observations
 New counters and KPIs analysis:

 RRC Re-est call termination: Useful counter for routine monitoring to verify number of
users terminating voice calls during RRC Re-establishment procedure. Both FOA RNCs are
reporting low number of termination at present, i.e. Current setting for T314 can be
considered as an optimised value.
 RTWP too low: Using the new counter cells can be identified with Antenna line failures
(e.g. loose feeders or antenna connectors, MHA failures and PA failures etc).
 RRC Connection Setup Failures due to AC (UL power, DL power and Code
congestion): Related KPIs can used for capacity monitoring. The FOA RNCs show no
concerns at present.
 RAB Connection Setup Failures for CS Voice Due to AC (UL power, DL power and
Code congestion): Related KPIs can used for capacity monitoring. The FOA RNCs show
no concerns at present.
 Mass Event Handler: There are number useful counters introduced related to MEH
feature, which can be useful for capacity analysis and hence remedy actions can be taken
accordingly.
45 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
Conclusions and Observations
 Paging Performance:
 There were no impacts on the Paging Success Rate performance
 RAN measurements (paging success rare in Cell_PCH). There was a counter
correction introduced in RU40
 Core Network measurements (Idle + PCH)
 High priority and low priority paging drops volumes are comparable to RU30 levels
 There were no deleted paging messages observed for both FOA RNCs
 In both RU30 and R40 environments, Paging Delay is slightly higher for 3UK network
compared to EE network. This could be due to paging channel (8kbps & 24kbps)
implementation policies
 Stable Paging Load performance and there were no impact due to RU40 introduction.

46 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Conclusions and Observations
 From the WBTS capacity perspective sites belongs to both FOA RNCs are reporting stable
performance. All following major capacity measures presents no noticeable impact due to the
introduction of RU40. Heavily loaded sites in the RNCs are investigated.
 Licensed and Configured Users and Throughput
 Subunit Usage
 R99 Channel Element usage
 HSDPA/HSPA Processing Set utilisation
 Radio link setup load in BTS and Radio Link Setup per second

 From the WCELL capacity perspective both FOA RNCs are showing stable performance for the
following measures and as expected presents no noticeable impact due to RU40 introduction.
 Common Channel performance and capacity
 Channelization Code usage
 SF Blocking performance
 Noise Rise – Ongoing investigation by FOA team (KT20)

47 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix

2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 1: Total Uplink Interference Too Low Percentage
• Total Uplink Interference Too Low Percentage (RU40 KPI):

100 %  SUM(RTWP_TOO_LOW) / SUM(RTWP_CLASS_0 + RTWP_CLASS_1 + RTWP_CLASS_2 +


RTWP_CLASS_3 + RTWP_CLASS_4 + RTWP_CLASS_5 + RTWP_CLASS_6 + RTWP_CLASS_7 +
RTWP_CLASS_8 + RTWP_CLASS_9 + RTWP_CLASS_10 + RTWP_CLASS_11 + RTWP_CLASS_12 +
RTWP_CLASS_13 + RTWP_CLASS_14 + RTWP_CLASS_15 + RTWP_CLASS_16 + RTWP_CLASS_17 +
RTWP_CLASS_18 + RTWP_CLASS_19 + RTWP_CLASS_20 + RTWP_CLASS_21)

49 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 2: RRC Connection Setup Failures due to AC
• RRC Setup Failure Rate due AC Uplink Power (RU40 KPI - RNC_3200a): This KPI quantifies RRC Setup
failures which are rejected because the RNC connection admission control determines there is limited uplink
power.
• If the number of RRC setup failures caused by Admission Control due to uplink power limitation becomes
high then physical or parameter optimisation activities may be required to better utilise or increase the uplink
air-interface capacity.
• Formula: 100xSUM(RRC_CONN_STP_FAIL_AC_UL)
-----------------------------------------------------
(RRC_CONN_STP_ATT)
• RRC Setup Failure Rate due AC Downlink Power (RU40 KPI - RNC_3201a): This KPI quantifies RRC
Setup failures which are rejected because the RNC connection admission control determines there is limited
downlink power.
• If the number of RRC setup failures caused by Admission Control due to downlink power limitation becomes
high then physical or parameter optimisation activities may be required to better utilise or increase the
downlink air-interface capacity.
Formulae: 100 * SUM(RRC_CONN_STP_FAIL_AC_DL)
--------------------------------------------------------------
SUM(RRC_CONN_STP_ATT)

50 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 2: RRC Connection Setup Failures due to AC
 RRC Setup Failure Rate due AC downlink spreading code congestion (RU40 KPI - RNC_3202a): This
KPI quantifies RRC Setup failures which are rejected because the RNC connection admission control
determines there is downlink spreading code congestion.
 If the number of RRC setup failures caused by Admission Control due to downlink spreading code
congestion becomes high then physical or parameter optimisation activities may be required to better utilise or
increase the downlink air-interface capacity.
 Formula: 100 x SUM(RRC_CONN_STP_FAIL_AC_COD)
-----------------------------------------------------------------
SUM (RRC_CONN_STP_ATT)

51 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 3: RAB Connection Setup Failures for CS Voice Due to AC
 RAB Setup Access Failure Rate for CS Voice due to uplink power (RU40 KPI - RNC_3203a): This KPI
quantifies failure rate of CS voice RAB setups which are rejected because the RNC connection admission
control determines there is limited uplink power.
 If the number of RAB setup failures caused by Admission Control due to uplink power limitation becomes
high then physical or parameter optimisation or upgrade activities may be required to better utilise or increase
the uplink air-interface capacity.
 Formula: 100* [RAB_STP_FAIL_CS_VOICE_AC_UL]
----------------------------------------------------------
[RAB_STP_COM_CS_VOICE]

 RAB Setup Access Failure Rate for CS Voice due to downlink power (RU40 KPI - RNC_3204a): This
KPI quantifies the number of CS voice RAB setup attempts which are rejected because the RNC connection
admission control determines there is limited downlink power.
 If the number of RAB setup failures caused by Admission Control due to downlink power limitation becomes
high then physical or parameter optimisation or upgrade activities may be required to better utilise or increase
the downlink air-interface capacity.
 KPI Formula: 100* SUM[RAB_STP_FAIL_CS_VOICE_AC_DL]
-----------------------------------------------------------------
SUM[RAB_STP_COMP_CS_VOICE]
52 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.
Appendix 3: RAB Connection Setup Failures for CS Voice Due to AC
 Percentage of RAB setup access failures for CS voice calls caused by downlink spreading code
congestion (RU40 KPI - RNC_3205a): This KPI quantifies the number of CS voice RAB setup attempts which
are rejected because the RNC connection admission control determines there is downlink spreading code
congestion.
 If the number of RAB setup failures caused by Admission Control due to spreading code congestion
becomes high then physical or parameter optimisation or upgrade activities may be required to better utilise or
increase the downlink air-interface capacity.
 KPI Formula: 100*SUM[RAB_STP_FAIL_CS_VOICE_AC_COD]
-------------------------------------------------------------------
[RAB_STP_COMP_CS_VOICE]

53 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 4: Percentage of PS Blocks Caused by AC UL power, DL power
and Code Congestion
 Percentage of PS Blocks caused by Admission Control Uplink Power (RU40 KPI - RNC_3208a): This KPI quantifies the
percentage of PS connection blocks caused by Admission Control due to uplink power limitation. This KPI should be studied in
combination with the absolute number of blocks, i.e. a high result from this KPI does not imply that the absolute quantity of
blocking is high.
 KPI formula: 100 %  SUM(PS_SETUP_FAIL_AC_UL_NRT)
-------------------------------------------------------------------
SUM(PS_SETUP_FAIL_AC_INT + PS_SETUP_FAIL_AC_BGR + PS_SETUP_FAIL_BTS_INT +
PS_SETUP_FAIL_BTS_BGR + PS_SETUP_FAIL_DMCU_INT + PS_SETUP_FAIL_DMCU_BGR +
PS_SETUP_FAIL_TRANS_INT + PS_SETUP_FAIL_TRANS_BGR + PS_SETUP_FAIL_AC_STRE +
PS_SETUP_FAIL_BTS_STRE + PS_SETUP_FAIL_DMCU_STRE + PS_SETUP_FAIL_TRANS_STRE)
 Percentage of PS Blocks caused by Admission Control Downlink Power (RU40 KPI - RNC_3207a): This KPI quantifies
the percentage of PS connection blocks caused by Admission Control due to downlink power limitation. This KPI should be
studied in combination with the absolute number of blocks, i.e. a high result from this KPI does not imply that the absolute
quantity of blocking is high.
KPI Formula: 100 * SUM(PS_SETUP_FAIL_AC_DL_NRT)
------------------------------------------------------------------
SUM(PS_SETUP_FAIL_AC_INT + PS_SETUP_FAIL_AC_BGR + PS_SETUP_FAIL_BTS_INT +
PS_SETUP_FAIL_BTS_BGR + PS_SETUP_FAIL_DMCU_INT + PS_SETUP_FAIL_DMCU_BGR +
PS_SETUP_FAIL_TRANS_INT + PS_SETUP_FAIL_TRANS_BGR + PS_SETUP_FAIL_AC_STRE +
PS_SETUP_FAIL_BTS_STRE + PS_SETUP_FAIL_DMCU_STRE + PS_SETUP_FAIL_TRANS_STRE)

54 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 4: Percentage of PS Blocks Caused by AC UL power, DL power
and Code Congestion
 Percentage of PS Blocks caused by Admission Control Spreading Code Congestion(RU40 KPI - RNC_3208a): This KPI
quantifies the percentage of PS connection blocks caused by Admission Control due to downlink spreading code congestion.
This KPI should be studied in combination with the absolute number of blocks, i.e. a high result from this KPI does not imply that
the absolute quantity of blocking is high.
KPI Formula: 100 %  SUM(PS_SETUP_FAIL_AC_COD_NRT) / SUM(PS_SETUP_FAIL_AC_INT +
PS_SETUP_FAIL_AC_BGR + PS_SETUP_FAIL_BTS_INT + PS_SETUP_FAIL_BTS_BGR + PS_SETUP_FAIL_DMCU_INT +
PS_SETUP_FAIL_DMCU_BGR + PS_SETUP_FAIL_TRANS_INT + PS_SETUP_FAIL_TRANS_BGR +
PS_SETUP_FAIL_AC_STRE + PS_SETUP_FAIL_BTS_STRE + PS_SETUP_FAIL_DMCU_STRE +
PS_SETUP_FAIL_TRANS_STRE)

55 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 5: MEH Related KPIs
• Mass Event Handler Active Duration - RNC_5461a (seconds): The KPI provides the total duration for
which the cell is in a Mass Event Handler load state.
• Formula: SUM(MEH_ACTIVE_DURATION)

• Average Duration Of Mass Event Handler Load State RNC_3178a (seconds): The KPI provides the
average duration for which the cell is in a Mass Event Handler load state.
• Formula: SUM(MEH_ACTIVE_DURATION) / SUM(MEH_ACTIVATIONS)

56 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 6: LTE PS Incoming ISHO Performance KPIs
• LTE Incoming Handover Prepare Success Rate (%): This KPI quantifies the success rate of the
preparation phase of an incoming LTE handover.
• Formula: 100 % x SUM(LTE_PS_IN_PREP_SUCC) / SUM(LTE_PS_IN_PREP_REQ)
• Preparation for an incoming LTE handover involves admission control and NBAP signalling to the target
Node B. Congestion at the target RNC, target Node B or on the Iub transport network could cause the
relocation prepare to fail.

• LTE Incoming Handover Success Rate (%): This KPI quantifies the overall success rate of an incoming
LTE handover . This KPI accounts for both the preparation and detection phases of the incoming handover. It
also accounts for the final signalling of the Handover to UTRAN Complete message from the UE.
 Formula: 100 %  SUM(LTE_PS_IN_COMPLETE) / SUM(LTE_PS_IN_PREP_REQ)

57 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 7: BTS Capacity Monitoring and Upgrade
 Start with BTS level monitoring – Monitor at least CE usage and HSPA PS utilisation.

KPI/Counter ID Name Object


M5008C39 Number of Subunits in Baseband BTS
M5008C37 Average Used BB Subunits BTS
M5008C34 Average HSUPA Subunit Usage BTS
M5008C11 Average Used CE for R99 DL BTS
M5008C14 Average Used CE for R99 UL BTS
M5008C24 Maximum HSDPA PS Utilisation ratio BTS
M5008C23 Average HSDPA PS Utilisation ratio BTS
M5008C27 Maximum HSUPA PS Utilisation ratio BTS
M5008C26 Average HSUPA PS Utilisation ratio BTS

58 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 8: BTS Capacity Monitoring and Upgrade
 In case of multiple LCG’s – Monitor R99 CE and HSPA users utilisation per LCG

KPI/Counter ID Name Object


RNC_2256a UL CE R99 Utilization Distribution Rate - (80 - <90)% LCG
RNC_2257a UL CE R99 Utilization Distribution Rate - (90 - <100)% LCG
RNC_2258a UL CE R99 Utilization Distribution Rate - (100 or more)% LCG
RNC_2262a DL CE R99 Utilization Distribution Rate - (80 - <90)% LCG
RNC_2263a DL CE R99 Utilization Distribution Rate - (90 - <100)% LCG
RNC_2264a DL CE R99 Utilization Distribution Rate - (100 or more)% LCG
RNC_2268a HSPA UL User Utilization Distribution Rate - (80 - <90)% LCG
RNC_2269a HSPA UL User Utilization Distribution Rate - (90 - <100)% LCG
RNC_2270a HSPA UL User Utilization Distribution Rate - 100% LCG
RNC_2274a HSPA DL User Utilization Distribution Rate - (80 - <90)% LCG
RNC_2275a HSPA UL User Utilization Distribution Rate - (90 - <100)% LCG
RNC_2276a HSPA UL User Utilization Distribution Rate - 100% LCG

59 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 9: R99 Channel Element Pool Based-license
 It is possible to allocate the needed baseband capacity from the possible baseband capacity
(see Possible system module capacity and Possible throughput and user capacity: FSMC/D/E
and FSMF in this chapter) via licenses. There are separate licenses for R99 and HSPA:

R99 License type Level CE vs. R99 license type Level CE R99 license type Level R99 license type Level
subunit vs. subunit CE vs. subunit CE vs. subunit
capacity capacity capacity capacity
Maximum Maximum Maximum Maximum
licensed CEs licensed CEs licensed CEs licensed CEs

Channel elements BTS FSMC/D/E: Channel elements BTS Channel elements BTS Channel elements BTS
One FSMC/D/E: One FSMC/D/E: One FSMC/D/E: One
subunit = 48 R99 subunit = 48 R99 subunit = 48 R99 subunit = 48 R99
CEs CEs CEs CEs
FSMF: One subunit FSMF: One subunit FSMF: One subunit FSMF: One subunit
= 96 R99 CEs = 96 R99 CEs = 96 R99 CEs = 96 R99 CEs
Depends on used Depends on used Depends on used Depends on used
system module system module system module system module
type(s) type(s) type(s) type(s)

60 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 10: BTS Capacity monitoring - HSPA Processing set licenses

There are three types of HSDPA processing set licenses


Max number of Max HSDPA Note that HSDPA Processing
HSDPA Processing Set
HSDPA users per BTS throughput per BTS Set 1 is not taken into
consideration when mixed
HSDPA BTS processing set 1 32 7,2 Mbps
with Processing Set2 and/or
HSDPA BTS processing set 2 72 21 Mbps Set 3

HSDPA BTS processing set 3 72 84 Mbps

And one type of HSUPA processing set license


HSUPA Processing Set Max Number of HSUPA Max HSUPA throughput In RU40 HSUPA PS license allow
users to reach up to 5.8 Mbps and 24
users simultaneously.
HSUPA BTS Processing Set 1 24 5.8 Mbps The HW reservation inside system
module is not reflecting the
number of HSUPA PS licenses

61 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 11: HSUPA/R99 licenses in Flexi BTS (Rel2/Rel3)

 If licensed R99 and HSUPA baseband resources (allowed with the available HSUPA BTS processing sets
and Rel99 CE licenses) exceeds System Module rel.2 capacity, overlapping baseband resources can be
dynamically exchange between R99 and HSUPA users.
 One HSUPA BTS Processing Set license can
Hybrid CF
be utilized by R99 users even without R99 CE R99 CEs
licenses. HSUPA licenses
Hybrid CFs overlapping
 Other HSUPA resources can be also dynamic, R99 CE licenses

but only if they are overlapped by Rel99 CE


licenses
 CF = Cluster Fraction (this is term used by HSUPA licenses Hybrid CF R99 CE licenses
R&D, shown in here as mentioned with many
counter descriptions')
 E.g. M5006C0: Counter shows the maximum Dynamic CFs

amount of licensed R99 CE capacity + R99


HSUPA CFs
CE capacity of first HSUPA processing step (=
48 R99 CEs)

62 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 11: Radio Link Setup Load in BTS
 The control plane at the BTS refers to processing of C-NBAP and D-NBAP messages.
 The system uses C-NBAP for the initial radio link (RL) setup signaling between RNC and BTS common
channel measurements.
 The system uses D-NBAP for signaling of the RL re-configurations, RL additions, and deletions.
 The master control unit (MCU) processes the control plane. In the Flexi BTS, the System Module represents
the MCU.
 The MCUs also have other tasks related to O&M, hardware management, and common (radio-technology-
independent) support functions.
 Therefore, there is a load on the MCU, even if the user traffic is not processed by the WBTS.
 This load can be monitored with M5004 counters, additionally in high load situation, the following counters are
updated.
 M1001C4 RRC Setup failures due BTS and
 M1006C203 RRC Connection Reject due to Iub Overload.
 If there is problem with BTS control plane load - Check the air interface and the BTS BB capacity. Congestion
of these causes overload at the BTS control plane.
 M5004 The signaling load in the WBTS measurement - measures the radio link capacity on the BTS level

63 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 11: Radio Link Setup Load in BTS Cont...
 M5004 Counters:
Counter Id Counter Name Description
M5004C0 NUMBER OF REJECTED RL Number of rejected radio link setup requests because of congestion on MCU (signaling
SETUPS DUE TO CONGESTION load too high) (events during 1s). Counter is updated when BTS reaches the
signaling capacity limits and start to reject new setups
M5004C1 PEAK RL SETUPS PER SECOND Peak radio link setup messages handled per second, where handled means setups
that are not rejected because of congestion (events during 1s).
M5004C2 PEAK RL OPERATIONS PER Peak radio link operations handled per second, where handled means operations that
SECOND are not rejected because of congestion
M5004C3 AVERAGE RL SETUP MESSAGE Average radio link setup request message queuing time before taken into handling in
QUEUING TIME ms. Sampling interval 1min. BTS control plane overload is seen as a high value of
rejected RL setups. The maximum queuing time is 3000 ms, but a value above 500
ms should be observed closely.

64 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 11: Radio Link Setup Load in BTS Cont...

 Radio Link Capacity – Attempts (M5004C1) - Radio Link Setups per second [#]
 Target:
Threshold indicating of capacity
Configuration
limitations at the user plane
1 FSMD >22 RLs/s
2 FSME >56 RLs/s

 Radio Capacity – Delays (M5003C3) – Average Radio Link Setup message queuing time [ms]
 An increase in the RL setup message queuing time indicates that the BTS control plane cannot
process all incoming messages immediately. This is an indication that BTS control plane processor
load is reaching maximum. BTS control plane overload is seen as a high value of rejected RL
setups. The message queuing time adds to the RL setup time, and thus the end-user experience.
The maximum queuing time is 3000 ms, but a value above 500 ms should be observed closely.
 Target: 500ms

65 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 12: HSPA Throughput Utilisation
 HSPA throughput and throughput utilisation can be monitored using following counters and KPIs

Counter ID Counter Name Unit Maximum HSDPA throughput utilization ratio per
M5008C0 HSDPA Maximum MAC-HS Throughput Mbps BTS in reference to maximum licensed throughput.
100 * sum HSDPA_MAX_MACHS_THR
M5008C1 HSDPA Average MAC-HS Throughput Mbps RNC _ 5396a 
sum LIC_HSDPA_THR 
M5008C2 HSUPA Maximum MAC-E Throughput Mbps

M5008C3 HSUPA Average MAC-E Throughput Mbps Maximum HSUPA throughput utilization ratio per
BTS in reference to maximum licensed throughput.
KPI ID KPI Name Unit 100 * sum HSUPA_MAX_MACE_THR
RNC _ 5397a 
sum LIC_HSUPA_THR 
RNC_5396a Max HSDPA throughput utilization ratio %

RNC_5401a Ave HSDPA throughput utilization ratio %

RNC_5397a Max HSUPA throughput utilization ratio %

RNC_5402a Ave HSDPA throughput utilization ratio %

66 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.


Appendix 13: HSPA Users and User Utilisation
 HSPA Users Utilisation KPIs are based M5008
 HSPA Users utilisation ratio per BTS in reference to licensed users
 KPIs below are aggregated in BTS level.
KPI ID KPI Name Unit
Maximum number of HSDPA users utilization
RNC_5398a Max number of HSDPA users utilization %
ratio per BTS in reference to maximum licensed
RNC_5403a Ave number of HSDPA users utilization %
users
RNC_5399a Max number of HSUPA users utilization %
100 * sum MAX _ BTS _ HSDPA _ USERS 
RNC _ 5398a 
RNC_5404a Ave number of HSUPA users utilization % sum LIC _ NUM _ HSDPA _ USERS 

Maximum number of HSUPA users utilization


ratio per BTS in reference to maximum licensed
users

100 * sum MAX _ BTS _ HSUPA _ USERS 


RNC _ 5399a 
sum LIC _ NUM _ HSUPA _ USERS 

67 2/28/2014 ©2013 Nokia Solutions and Networks. All rights reserved.