Indicator Changes For UA8.1 Benchmarking Activities Ua8.1 Dr5 Kts

Indicator changes for UA8.
1 benchmarking activities
UA8.1 DR5 KTS
Nicolae Roman
December 2012
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Introduction
• High level performance view and comparison between 3G customers based on data
collected on quarterly timeframe, on daily basis values (14M records).
• 14 customers audited from EMEA, NAR and APAC region
• Benchmark are fully retrieved with NPO7.1 Benchmark report dictionary (version 03.05
containing 362 indicators) and UA8.1 Benchmark report dictionary (version 05.03 containing
360 indicators ) in 2 particular cases:
- NPO upgraded in 8.1 and new 5.03 view used for all RNC’s from the network (by example :
2 RNC’s in UA8.1 and the others in UA7.1)
- one NPO upgraded in 8.1 and new 5.03 view used for all RNC’s assigned to this NPO and
for the other(s) NPO in 7.1 the 03.05 view used to execute the views to RNC level.
• The new UA8_1_Benchmark_indicators_05.03 view is included in the main dictionary
delivery related to NPO upgrade from 7.1 to 8.1.
• The delta between the 2 version in term of indicators are :
03.05 view version indicators (in UA7.1) New 05.03 view version indicators (in UA8.1)
OutgoingInterFrequencyHHOAttemptDistribut
VS_OutGoInterFreqHoAtt_NoRsrcAvailCacFailure(U
ionforiMCTA_IMCTA007_CR_AllCauses(UIMCTA
174_2)(Event)
007_CR_AllCauses)(Event)
VS_OutGoInterFreqHoAtt_Rescue(U174_0)(Event)
VS_OutGoInterFreqHoAtt_Service(U174_1)(Event)
2
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. NEA-Monitoring | UA.8.1 DR5 KTS | 2
Indicator warning by KPI domain
• Traffic :
• Mean HSDPA call duration
• EDCHActivityFactor_HSUPA010_CR
• Category 24 UE to be added in Benchmark (NEW)
• Accessibility :
• IuSCCPSuccessRate_IuSCCP006_R_Ps
• CallSetupSuccessRate_CSSR005_R_Cs & Ps
• Retainability :
• Number of HSDPA drops per hour of call
• Mobility :
• HSDPA to HSDPA Primary cell change per minute of call
• Capacity :
• Average number of HSDPA DL RB established per HSDPA RNC
• Average number of HSUPA UL RB established per HSUPA RNC
• Percentage of BTS with CEM D-BBU Used between 60 and 100 percent
3
Traffic - Mean HSDPA call duration
Mean HSDPA call duration

140
120
100
80
60
40
20
0
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
A1TA (58,6) SFR (20,6) Vodacom (16,9) TNZ (18,2) ORF (10,5)
CU (41,8) VDF_UK (13,9) VDF_PT (32,0) AT&T (33,0) VDF_Qatar (11,5)
mCell (18,4) Globacom (20,2) WIND (15,9) ETS (56,3)
Mean HSDPA call duration = CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA /

(10*RadioBearerSetupSuccess_RB011_R_HSDPA)
4
CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA
3,5E+10
3E+10
2,5E+10
2E+10
1,5E+10
1E+10
5E+09
GQ03 GQ07 GQ01 GQ02 GQ04 GQ05 GQ06

GQ08 OQ01 OQ02 OQ03 OQ04 OQ05
A1TA – UA8.1 RNC’s GQ3 and GQ7 evolution. Indicator problems fixed after EP2 patch installation.(13
Sept. 2012 in case of GQ7).
In case of AT&T, A1TA and CU the values where recomputed excluding the 8.1 RNCs due to wrong values
showed in RB021_CR_HSDPA indicator (counter - U1666_20_Cum (HSDPA)). More details on CR
699726 /AR 1-3894449 opened on this issue.
5
Traffic - CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA(URB021_CR_HSDPA)(Event)
Traffic - CumulatedNumberOfDLBearersEstablished_RB021_CR_Ps(URB021_CR_Ps)(Event)
8.1.3.1 Tap2 GQ7 EP2 upg.
2E+10
1,8E+10
1,6E+10
1,4E+10
1,2E+10
1E+10
8E+09
6E+09
4E+09
2E+09
0
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
2/Aug
4/Aug
6/Aug
8/Aug
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA(URB021_CR_HSDPA)(Event)
2E+10
1,8E+10
1,6E+10
1,4E+10
1,2E+10
1E+10
8E+09
6E+09
4E+09
2E+09
0
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
2/Aug
4/Aug
6/Aug
8/Aug
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
CumulatedNumberOfDLBearersEstablished_RB021_CR_Ps(URB021_CR_Ps)(Event)
URB021_CR_HSDPA=UC1666_20_Cum+UC1666_24_Cum
URB021_CR_PS=UC1666_0_Cum+UC1666_7_Cum+UC1666_8_Cum+UC1666_9_Cum+UC1666_10_Cum+UC1666_11_Cum+UC1666_12_Cum+
UC1666_13_Cum+UC1666_14_Cum+UC1666_15_Cum+UC1666_16_Cum+UC1666_17_Cum+UC1666_18_Cum+UC1666_19_Cum+UC1666_20_C
um+UC1666_21_Cum+UC1666_24_Cum
6
Traffic - CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA(URB022_CR_HSUPA)(Event)

1,4E+10
1,2E+10
1E+10
8E+09
6E+09
4E+09
2E+09
0 2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA(URB022_CR_HSUPA)(Event)
Counter ID 1667
URB022_CR_HSUPA = UC1667_16_Cum+UC1667_20_Cum
3GPP Name VS.UlAsConfIdAvgNbrEstablished
Location REFCELL (Reference)
Unit event
Family RAB Traffic
Meaning, Description indicates an average of the number of
UlAsConfIds established per iRNC, based on
time average over collection period
Triggering Event Any time an UlAsConfId is established or deleted
(even on SRB establishment)
7
Mean HSDPA call duration - recomputed

70
60
50
40
30
20
10
0
01/07/2012 09/07/2012 17/07/2012 25/07/2012 02/08/2012 10/08/2012 18/08/2012 26/08/2012 03/09/2012 11/09/2012 19/09/2012 27/09/2012
A1TA (19,5) SFR (20,6) Vodacom (16,9) TNZ (18,2) ORF (10,5)
CU (10,7) VDF_UK (13,9) VDF_PT (32,0) AT&T (15,2) VDF_Qatar (11,5)
mCell (18,4) Globacom (20,2) WIND (15,9) ETS (56,3)
In case of AT&T, A1TA and CU the values where recomputed excluding the 8.1 RNCs due to wrong
values showed in RB021_CR_HSDPA indicator (counter - U1666_20_Cum (HSDPA)). More details on
CR 699726 /AR 1-3894449 opened on this issue.
8
Traffic - EDCHActivityFactor_HSUPA010_CR
eDCH Activity
•The low eDCH activity factor (time UE transmits E-DCH data on radio / Factor
A1TA
time UE has an E-DCH RB established) values encountered in A1TA and CU 0.08%
SFR 8%
are based on the new 8.1 NPO formula to compute the values of eDCH Vodacom 5%
TNZ 9%
Activity Factor CR00389487 “Request to modify HSUPA indicators in NPO ORF 5%
extended dictionary China Unicom 1%
VDF UK 6%
EDCHActivityFactor_HSUPA010_CR = VDF PT 8%
eDCHActiveUsers_HSUPA008_CR / AT&T N/A
AverageNumberOfULBearersEstablished_RB013_CR_HSUPA VDF Qatar 12%
mCell
Replacing the 7.1 formula : 2%
Globacom Nigeria 3%
•eDCHActiveUsers_HSUPA008_CR/(50*CumulatedNumberOfULBearersEstabl WIND 12%
ished_RB022_CR_HSUPA) ETS Sri Lanka 10%
•In the same time we have also a change for the formula component
“eDCHActiveUsers_HSUPA008_CR”
•from UC10905_1_Cum+UC10905_2_Cum (in 7.1) to :
•(VS_eDCHactiveUsers_2ms_users_Cum +
VS_eDCHactiveUsers_10ms_users_Cum) / E_DCHActiveTti_HSUPA026_CR
(in 8.1.x)
9
Traffic - EDCHActivityFactor_HSUPA010_CR A1TA
0,60%
0,50%
0,40%
0,30%
0,20%
0,10%
0,0%
01/07
04/07
07/07
10/07
13/07
16/07
19/07
22/07
25/07
28/07
31/07
03/08
06/08
09/08
12/08
15/08
18/08
21/08
24/08
27/08
30/08
02/09
05/09
08/09
11/09
14/09
17/09
20/09
23/09
26/09
29/09
CU - EDCHActivityFactor_HSUPA010_CR GQ08 OQ01 OQ02 OQ03 OQ04 OQ05
0,25% 7,%
6,%
0,2%
5,%
0,15% 4,%
0,1% 3,%
2,%
0,05%
1,%
0,% ,%
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
CZ_RNC251 CZ_RNC252 CZ_RNC253 CZ_RNC254

Note : UA7.1 RNC’s are represented on the secondary axis
10
Traffic - EDCHActivityFactor_HSUPA010_CR
0,35% 1,09
0,3% 1,08
0,25% 1,07
0,2% 1,06
0,15% 1,05
0,1% 1,04
0,05% 1,03
0,% 2/Aug 1,02

4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
EDCHActivityFactor_HSUPA010_CR(UHSUPA010_CR)(%) eDCHActiveUsers_HSUPA008_CR(UHSUPA008_CR)(nb)
Note : eDCHActiveUsers_HSUPA008_CR indicator evolution represented on the secondary axis
11
Traffic - Category 24 UE to be added in Benchmark
Q3 - Percentage of Call attempts /UE Cat
100%
90%
80%
Cat14
70%
Cat12
60%
Cat10
50%
Cat9
40%
Cat8
30% Cat7
20% Cat6
10%
0%
A1TA SFR Vodacom TNZ ORF CU VDF UK VDF PT AT&T VDF Qatar mCell Globacom WIND Etisalat
DistributionCallAttempts_HSDPA052_CR_Cat24(UHSDPA052_CR_Cat24)(%)
4,%
3,5%
3,%
2,5%
2,%
1,5%
1,%
,5%
,%
1/Oct
2/Oct
3/Oct
4/Oct
5/Oct
6/Oct
7/Oct
8/Oct
9/Oct
10/Oct
11/Oct
12/Oct
13/Oct
14/Oct
15/Oct
16/Oct
17/Oct
18/Oct
19/Oct
20/Oct
21/Oct
22/Oct
23/Oct
24/Oct
25/Oct
ANNECYI1 ANNECYI2 ANNECYI3 CHAMBERY1 CHAMBERY2 CHAMBERY3 CLERMONT1
CLERMONT2 CLERMONT3 DIJONC1 DIJONC2 DIJONC3 DIJONC4 GRENOBLE1
GRENOBLE2 GRENOBLE3 LYONECUL1 LYONECUL2 LYONECUL3 LYONECUL4 LYONECUL5
LYONECUL6 LYONMONC1 LYONTRIO1 LYONTRIO2 MARSEJOL1 MARSEJOL2 MARSEJOL3
MARSESTM1 MARSESTM2 MARSESTM3 MARSESTM4 MARSESTM5 MARSESTM6 MONTPELL1
MONTPELL2 MONTPELL3 MONTPELL4 MONTPELL5 MONTPELL6 NAVARINTE NICENORD1
NICENORD2 NICENORD3 NICENORD4 RS_STGEN1 TOULON_SF1 TOULON_SF2 TOULON_SF3
12
Traffic - Category 24 UE to be added in Benchmark
Max. Code rate Max. data

Modulation MIMO, at
3GPP number of rate
Category Multi-
Release
HS-DSCH Cell Max. data
[Mbit/s]
codes rate
Release 5 6 5 16-QAM 0.76 3.6
Release 5 7 10 16-QAM 0.75 7.2
Release 5 8 10 16-QAM 0.76 7.2
Release 5 9 15 16-QAM 0.7 10.1
Release 5 10 15 16-QAM 0.97 14
Release 5 11 5 QPSK 0.76 0.9
Release 5 12 5 QPSK 0.76 1.8
Release 7 13 15 64-QAM 0.82 17.6
Release 7 14 15 64-QAM 0.98 21.1
Release 7 15 15 16-QAM MIMO 0.81 23.4
Release 7 16 15 16-QAM MIMO 0.97 28
Release 7 19 15 64-QAM MIMO 0.82 35.3
Release 7 20 15 64-QAM MIMO 0.98 42.2
Release 8 21 15 16-QAM Dual-Cell 0.81 23.4
Release 8 22 15 16-QAM Dual-Cell 0.97 28
13
Accessibility - IuSCCPSuccessRate_IuSCCP006_R_Ps
From 19.07 GQ07 and 25.07 GQ03 the date of upgrade to UA08.1.3.1 Tap 2
version the RNC’s of A1TA network are showing values coming back to 100%.
A1TA - IuSCCPSuccessRate_IuSCCP006_R_Ps
100,2%
100,%
99,8%
99,6%
99,4%
99,2%
99,%
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9

GQ08 OQ01 OQ02 OQ03 OQ04 OQ05
14
Accessibility - IuSCCPSuccessRate_IuSCCP006_R_Ps
From upgrade dates to UA08.1.3.1 Tap 2 version the migrated AT&T RNC’s of
network are showing values of 100%.
AT&T - IuSCCPSuccessRate_IuSCCP006_R_Ps
100,05%
100,00%
99,95%
99,90%
99,85%
99,80%
99,75%
99,70%
99,65%
99,60%
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
INDPMOXCCRAR01 INDPMOXCCRAR03 INDPMOXCCRAR05

INDPMOXCCRAR07 INDPMOXCCRAR14 INDPMOXCCRAR17
15
Accessibility - CallSetupSuccessRate_CSSR005_R_Cs & Ps
Update formula in case of :
CallSetupSuccessRate_CSSR005_R_Cs indicator with RRCConnectionSuccessRate

instead of FirstRRCConnectionSuccessRate.
The new formula in 8.1 is :
RRCConnectionSuccessRateExcRep_RRC021_CR_Cs*IuSCCPSuccessRate_IuSCCP006_R_Cs*
RABEstablishmentSuccessRatePerRequestedRAB_RAB011_R_Cs
replacing
FirstRRCConnectionSuccessRate_RRC013_CR_Cs*IuSCCPSuccessRate_IuSCCP006_R_Cs*RA
BEstablishmentSuccessRatePerRequestedRAB_RAB011_R_Cs
CallSetupSuccessRate_CSSR005_R_Ps indicator with RRCConnectionSuccessRate

instead of FirstRRCConnectionSuccessRate.
The new formula in 8.1 is :
RRCConnectionSuccessRateExcRep_RRC021_CR_Ps*IuSCCPSuccessRate_IuSCCP006_R_Ps*
RABEstablishmentSuccessRatePerRequestedRAB_RAB011_R_Ps
replacing
FirstRRCConnectionSuccessRate_RRC013_CR_Ps*IuSCCPSuccessRate_IuSCCP006_R_Ps*RA
BEstablishmentSuccessRatePerRequestedRAB_RAB011_R_Ps
For upgraded RNC’s the trend is to have decreased values for CSSR005_R_Cs and increased
ones for CSSR005_R_Ps.
16

99,9%
99,8%
99,7%
99,6%
99,5%
99,4%
99,3%
99,2%
99,1%
99,%
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
2/Aug
4/Aug
6/Aug
8/Aug
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
CallSetupSuccessRate_CSSR005_R_Cs CallSetupSuccessRate_CSSR005_R_Ps
17
AT&T - CallSetupSuccessRate_CSSR005_R_Cs
100,%
99,8%
99,6%
99,4%
99,2%
99,%
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
INDPMOXCCRAR01 INDPMOXCCRAR03 INDPMOXCCRAR14 INDPMOXCCRAR17

CallSetupSuccessRate_CSSR005_R_Ps
100,%
99,9%
99,8%
99,7%
99,6%
99,5%
99,4%
99,3%
99,2%
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
INDPMOXCCRAR01 INDPMOXCCRAR03 INDPMOXCCRAR14 INDPMOXCCRAR17

18
Retainability - Number of HSDPA drops per hour of call
In case of A1TA, China Unicom and AT&T the network values for “Number of
HSDPA drops per hour of call” where recomputed excluding the UA8.1 RNC’s
due to errored indicator “RB021_CR_HSDPA” values.
3,5
Number of HSDPA drops per hour of call

3
2,5
1,5
0,5
0
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
Number of HSDPA drops per hour of call = (36000* IuAbnormalReleaseRequest_IU008_R_HSDPA)

/CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA
19
0,01
0,015
0,02
0,025
0,03
0,035
0,04
0,005
0,01
0,015
0,02
0,025
0,03
0,035
0,04
0,045
0,005
0
0
1/Jul 1/Jul
3/Jul 3/Jul
5/Jul 5/Jul
7/Jul 7/Jul
9/Jul 9/Jul
11/Jul 11/Jul
13/Jul 13/Jul
15/Jul 15/Jul
17/Jul 17/Jul
19/Jul 19/Jul
21/Jul 21/Jul
8.1.3.1 Tap2
8.1.3.1 Tap2
23/Jul 23/Jul
25/Jul 25/Jul
27/Jul 27/Jul
29/Jul 29/Jul
31/Jul 31/Jul
2/Aug 2/Aug
4/Aug 4/Aug
6/Aug 6/Aug
8/Aug 8/Aug
10/Aug 10/Aug
12/Aug 12/Aug
GQ7
GQ7
14/Aug 14/Aug
20
16/Aug 16/Aug
18/Aug 18/Aug
20/Aug 20/Aug
22/Aug 22/Aug
24/Aug 24/Aug
26/Aug 26/Aug

28/Aug 28/Aug
30/Aug 30/Aug
1/Sep 1/Sep

NumberOfDropsPerMinuteOfCalls_IU019_R_Ps(UIU019_R_Ps)(nb)
3/Sep 3/Sep
5/Sep 5/Sep
NumberOfDropsPerMinuteOfCalls_IU019_R_HSDPA(UIU019_R_HSDPA)(nb)
7/Sep 7/Sep
9/Sep 9/Sep
11/Sep 11/Sep
13/Sep 13/Sep
EP2 upg.
EP2 upg.
15/Sep 15/Sep
17/Sep 17/Sep
19/Sep 19/Sep
21/Sep 21/Sep
Retainability - NumberOfDropsPerMinuteOfCalls_IU019_R_HSDPA(UIU019_R_HSDPA)(nb)
23/Sep 23/Sep
25/Sep 25/Sep
27/Sep 27/Sep
29/Sep 29/Sep
NEA-Monitoring | UA.8.1 DR5 KTS | 20
Mobility - HSDPA to HSDPA Primary cell change per minute of call
In case of A1TA, China Unicom and AT&T the network values for “HSDPA to
HSDPA Primary cell change per minute of call” where recomputed excluding
the UA8.1 RNC’s due to errored indicator “RB021_CR_HSDPA” values
1,6 Before recomputing
1,4 A1TA (0,20) CU (0,38) AT&T (0,22)
1,2
1
0,8
0,6
0,4
0,2
0
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
1,6 After recomputing
1,4
A1TA (0,62) CU (1,48) AT&T (0,67)
1,2
0,8
0,6
0,4
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
21
Capacity - Average number of HSDPA DL RB established per HSDPA RNC
In case of A1TA, China Unicom and AT&T the network values for “Average number of HSDPA DL RB
established per HSDPA RNC” where recomputed excluding the UA8.1 RNC’s due to errored indicator
“AverageNumberOfDLBearersEstablished_RB013_CR_HSDPA” values
7000 Before recomputing
A1TA (2019) CU (2960) AT&T (2439)
6000
5000
4000
3000
2000
1000
0
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
2000 After recomputing

A1TA (660) CU (762) AT&T (1476)
1500
1000
500
0
01/07/2012 09/07/2012 17/07/2012 25/07/2012 02/08/2012 10/08/2012 18/08/2012 26/08/2012 03/09/2012 11/09/2012 19/09/2012 27/09/2012
22
Capacity - AverageNumberOfDLBearersEstablished_RB013_CR_HSDPA(URB013_CR_HSDPA)(nb)
Capacity - AverageNumberOfDLBearersEstablished_RB013_CR_Ps(URB013_CR_DLPs)(nb)
25000
20000
15000
10000
5000
0
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
2/Aug
4/Aug
6/Aug
8/Aug
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
AverageNumberOfDLBearersEstablished_RB013_CR_HSDPA(URB013_CR_HSDPA)(nb)
25000
20000
15000
10000
5000
0
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
AverageNumberOfDLBearersEstablished_RB013_CR_Ps(URB013_CR_DLPs)(nb)
URB013_CR_HSDPA=CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA/NumberEventsDLBearersEstabl
ishRelease_RB034_CR_HSDPA
URB013_CR_DLPs=CumulatedNumberOfDLBearersEstablished_RB021_CR_Ps/NumberEventsDLBearersEstablishRel
ease_RB034_CR_Ps
23
Capacity - Average number of HSUPA UL RB established per HSUPA RNC
In case of A1TA, China Unicom and AT&T the network values for “Average number of HSUPA UL RB
established per HSUPA RNC” where recomputed excluding the UA8.1 RNC’s due to errored indicator
“AverageNumberOfULBearersEstablished_RB013_CR_HSUPA” values
Before recomputing
6000
A1TA (1309) CU (2408) AT&T (1824)
5000
4000
3000
2000
1000
0
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
After recomputing
700
A1TA (428) CU (605) AT&T (574)
650
600
550
500
450
400
350
300
01/07/2012 10/07/2012 19/07/2012 28/07/2012 06/08/2012 15/08/2012 24/08/2012 02/09/2012 11/09/2012 20/09/2012 29/09/2012
24
Capacity - AverageNumberOfULBearersEstablished_RB013_CR_HSUPA(URB013_CR_ULHSUPA)(nb)

16000
14000
12000
10000
8000
6000
4000
2000
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
2/Aug
4/Aug
6/Aug
8/Aug
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
AverageNumberOfULBearersEstablished_RB013_CR_HSUPA(URB013_CR_ULHSUPA)(nb)
URB013_CR_ULHSUPA = CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA/
NumberEventsULBearersEstablishRelease_RB034_CR_HSUPA
25
Capacity - Percentage of BTS with CEM D-BBU Used between 60 and 100 percent
The metric is not be 100 % accurate from UA7138 as from this release onwards, the counter (10403) is changing of
processor (PQ3 instead of PQ2).
As a result :
•CEM CPU is increasing a lot (PQ3 is the most loaded processor) and being over 60% is not necessary critical (maybe 80 to
90% instead)
•NodeB with mixity (iCEM and xCEM) : the average at NodeB level has no more sense (CPU of different processor can’t be
averaged)
•In your next benchmark, you will see more and more %NodeB with CEM CPU > 60%.
Here is some background:

Capacity
CEM CPU load monitoring on eCEM (and xCEM)
CEM CPU load is monitored through counters U10403_CEM_Avg VS_cpuLoad_CEM_Avg

U10403_CEM_Cum VS_cpuLoad_CEM_Cum
U10403_CEM_Max VS_cpuLoad_CEM_Max
 Apply to both iCEM and x/eCEM U10403_CEM_Min VS_cpuLoad_CEM_Min
U10403_CEM_NbEvt VS_cpuLoad_CEM_NbEvt
 Defined at board level (CEM)
Before UA7138
 Counter related to PQ2 load for all CEMs
  Aggregation of CEM CPU load possible at NodeB level (or Iub level)
From UA7138 (121456 - NodeB Overload Step1)
 Counters related to PQ2 load for iCEM
 Counters related to PQ3 load for xCEM or eCEM – more representative of CEM CPU load
  Aggregation of CEM CPU load NOT possible at NodeB level (or Iub level)
 In case of NodeB with iCEM and x/eCEM mixity: non sense to aggregate PQ2 and PQ3 processor load
1
26
Capacity - Percentage of BTS with CEM D-BBU Used between 60 and 100 percent
Percentage of BTS with CEM D-BBU Used between 60 and 100 percent
30%
25%
20%
15%
10%
5%
0%
1/7 8/7 15/7 22/7 29/7 5/8 12/8 19/8 26/8 2/9 9/9 16/9 23/9 30/9
A1TA (0,2%) SFR (21,6%) Vodacom (6,7%) TNZ (2,6%) ORF (8,6%)
CU (7,1%) VDF_UK (13,4%) VDF_PT (4,2%) AT&T (N/A) VDF_Qatar (12,4%)
Globacom (21,1%) WIND (19,4%) ETS (0,4%)
#10403 Counter_Name: cpuLoad

Apply to: Board/RRH Unit: Percentage Range: 0-100 Type: LOAD
Meaning: % CPU load
Triggering event: the counter is evaluated each second, and the .Min and .Max values are updated each 2
seconds.
Notes: reports the number of seconds in .NbEvt from UA6
27
Conclusion
-The actual analysis is based on the Q3 Benchmark report on the 14 customers audited
- In case of migration to UA8.1 for the indicators showing variation between the reference period (indicator
evolution in UA7.1) and post-upgrade interval (indicator evolution in UA8.1.x) it is recommended to make
the following check:
- the indicator was identified as unstable in actual presentation with a known behaviour
- there is an upgrade or change in the evolution of indicator in UA8.1 release vs. UA7.1 by consulting
the new Basic, Baseline and Extended dictionary and definitions
- splitting the faulty indicator in the composing counter and to verify the counters behaviour
- the process of comparison between networks in different releases (UA7.1 vs.UA8.1) must be conducted
by caution, checking if we are comparing the same thing (Example : CallSetupSuccessRate_CSSR005_R_Ps
indicator with RRCConnectionSuccessRate in 8.1 formula instead of FirstRRCConnectionSuccessRate in 7.1).
In this case we can recompute the 7.1 indicator values based on 8.1 formula and to make the assessment
on this basis.
- usefull informations can be found in document “UA8.1 Performance Monitoring Guidelines v08.02”
providing main methods for performance monitoring in a UMTS network, based on a set of NPO reports.
https://wcdma-ll.app.alcatel-lucent.com/livelink/livelink.exe?func=ll&objId=65476325&objAction=browse
UA8.1.3 was released (GO decision for 813 GA) based on the following SW components :
- RNC – UA08.1.3.1 EP4 Tap3; - Node B – EP3
- NPO – version 4.1 R7; WMS – version 8.1.2 EP2; WPS - version 2.0.13.1
28
NEA Active Monitoring
Q3 2012 complete report link
3G Quarterly QOS Benchmarking – Q3 data
Established WCDMA Quality benchmarks driving actions All degradations are communicated to CTA/GCD teams
to improve network performance with recommendation for
Solving Capacity issues: product deployment
Engineering services: optimization, troubleshooting, etc
NEA/GCD periodic synchronization meetings organized

progress on different KPI & optimizations
SFR, mCell, VDF UK : PS CSSR lower than 97 %
Recommendation: Improvement expected by increasing the
values of PS RAB establishments success rate following the next
RNC’s evolution : BRRNC01 for mCell, RNC_440209_4&5 for SFR
Status: Investigation on going by CTA
 ORF : Degradation of R99 to HSDPA mobility performance
81% > 34% compared to Q2 2012
Recommendation: Investigation on small number of events
triggered on the RNC’s with individual spikes reaching 10 %
Status: Investigation on going by CTA
Vodacom: Very high number of active user per RNC (>3000)
Recommendation: Increase Network Capacity
Status : The addition of new RNC's in the network must continue
Positive trends (a new one is planned till end of year 2012 )
A1TA: General Best Performance KPIs; highest HSDPA cell  Globacom , mCell: Bad performance on Accessibility,
throughput ( 3236 kbits/sec); highest CS Voice CDR : 0.22% Retainability
NEA Analysis: too many transmission issues;
ORF: Important increase on UE Cat. 24 distribution in the network
Status: ALU local team alerted but they have to cope with
SFR , ORF and VDF Qatar : Improvement of accessibility KPI’s frequent transmission support outages (unprotected STM links)
despite of traffic increase
A1TA, China Unicom, VDF PT: Best HSUPA cell throughput –
around 200 kbit/s at the end of Q3 nicolae.roman@alcatel-lucent.com
29
Backup
30
Traffic - RABActivityDL_Traffic022_CR_HSDPA(UTraffic022_CR_HSDPA)(%)
Traffic - RABActivityUL_Traffic023_CR_HSUPA(UTraffic023_CR_HSUPA)(%)
5,%
4,5%
4,%
3,5%
3,%
2,5%
2,%
1,5%
1,%
,5%
,%
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
RABActivityDL_Traffic022_CR_HSDPA(UTraffic022_CR_HSDPA)(%)
10,%
9,%
8,%
7,%
6,%
5,%
4,%
3,%
2,%
1,%
,%
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
2/Aug
4/Aug
6/Aug
8/Aug
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
RABActivityUL_Traffic023_CR_HSUPA(UTraffic023_CR_HSUPA)(%)
UTraffic022_CR=(RABActivityTimeDL_Traffic042_CR+RABActivityTimeDL_Traffic042_CR_Sig)/(100*(CumulatedNumbe
rOfDLBearersEstablished_RB021_CR+CumulatedNumberOfDLBearersEstablished_RB021_CR_Sig))
UTraffic023_CR=(RABActivityTimeUL_Traffic034_CR+RABActivityTimeUL_Traffic034_CR_Sig)/(100*(CumulatedNumbe
rOfULBearersEstablished_RB022_CR+CumulatedNumberOfULBearersEstablished_RB022_CR_Sig))
31
Traffic - CumulativeTimePsRadioBearerEstablished_RB035_CR(URB035_CR)(s)

2E+09
1,8E+09
1,6E+09
1,4E+09
1,2E+09
1E+09
800000000
600000000
400000000
200000000
0 2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
CumulativeTimePsRadioBearerEstablished_RB035_CR(URB035_CR)(s)
URB035_CR = CumulatedNumberOfDLBearersEstablished_RB021_CR_Ps/10
Cumulative time of PS RB established. Indicator used in Benchmark activities.
32
Traffic - MeanCallDuration_RAB021_R_HSUPA(URAB021_R_HSUPA)(s)

900
800
700
600
500
400
300
200
100
0
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
2/Aug
4/Aug
6/Aug
8/Aug
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
MeanCallDuration_RAB021_R_HSUPA(URAB021_R_HSUPA)(s)
URAB021_R_HSUPA = CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA/ (10*(NZ(RadioBearerSetupSuccess_RB011_R_HSUPA)))
33
Retainability - NumberOfRadioDropsPerMinuteOfCalls_HSUPA014_CR(UHSUPA014_CR)(nb)

0,018
0,016
0,014
0,012
0,01
0,008
0,006
0,004
0,002
0
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
NumberOfRadioDropsPerMinuteOfCalls_HSUPA014_CR(UHSUPA014_CR)(nb)
UHSUPA014_CR = (600*VS_EdchCellDeletion_RadioLinkFail)/ CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA
34
Mobility - HSDPAToHSDPAPrimaryCellChangePerMin_HSDPA039_CR(UHSDPA039_CR)(nb)

0,7
0,6
0,5
0,4
0,3
0,2
0,1
0
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
HSDPAToHSDPAPrimaryCellChangePerMin_HSDPA039_CR(UHSDPA039_CR)(nb)
UHSDPA039_CR=(600*(VS_HsdpaMobilitySuccess_HsdpaToHsdpa+VS_HsdpaMobilitySuccess_HsdpaToHsdpaInter
Freq+VS_HsdpaMobilitySuccess_HsdpaDCToHsdpaDCInterFreq+VS_HsdpaMobilitySuccess_HsdpaToHsdpaDCInter
Freq+VS_HsdpaMobilitySuccess_HsdpaDCToHsdpaInterFreq+VS_HsdpaMobilitySuccess_HsdpaDCToHsdpaDC+VS
_HsdpaMobilitySuccess_HsdpaToHsdpaDC+VS_HsdpaMobilitySuccess_HsdpaDCToHsdpa))/VS_DlAsConfIdAvgNbrE
stablished_DlAsCnfHsdpa_Cum
35
Mobility - PrimaryCellChangePerMinute_HSUPA006_CR(UHSUPA006_CR)(nb)

0,7
0,6
0,5
0,4
0,3
0,2
0,1
0
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
2/Aug
4/Aug
6/Aug
8/Aug
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
PrimaryCellChangePerMinute_HSUPA006_CR(UHSUPA006_CR)(nb)
UHSUPA006_CR=600*(HSUPAMobilitySuccess_HSUPA016_CR_ItaFeDCHeDCH+HSUPAMobilitySuccess_HSUPA016_CR
_ItrFeDCHeDCH+HSUPAMobilitySuccess_HSUPA016_CR_ItaFeDCHneDCH+HSUPAMobilitySuccess_HSUPA016_CR_ItrF
eDCHneDCH)/CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA
36
HSUPA - EDCHActivityFactor_HSUPA010_CR(UHSUPA010_CR)(%)

0,35%
0,3%
0,25%
0,2%
0,15%
0,1%
0,05%
0,%
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
EDCHActivityFactor_HSUPA010_CR(UHSUPA010_CR)(%)
UHSUPA010_CR = eDCHActiveUsers_HSUPA008_CR/ AverageNumberOfULBearersEstablished_RB013_CR_HSUPA
37
Throughput - EdchActiveCellThpt_HSUPA022_CR(UHSUPA022_CR)(Kbit/s)

600
500
400
300
200
100
0
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
EdchActiveCellThpt_HSUPA022_CR(UHSUPA022_CR)(Kbit/s)
EdchActiveCellThpt_HSUPA022_CR (Edch cell throughput over RAB activity period in Kbit/s) =

1.024*8000*(DedicatedUplinkKbytesRlcReferenceCell_Traffic048_C_HSUPA)/(RABActivityTimeUL_Traffic034_CR_HSUPA)
UTraffic048_C_HSUPA=UC1555_14+UC1555_15+UC1555_18
UTraffic034_CR_HSUPA =UC1567_14+UC1567_15+UC1567_18 – see next slide
For both indicators the formula was updated in UA8.1 by adding the screening 18 (PS I/B QCHAT HSPA )
38
Traffic - RABActivityTimeUL_Traffic034_CR_Ps(UTraffic034_CR_Ps)(ms)
Traffic - RABActivityTimeUL_Traffic034_CR_HSUPA(UTraffic034_CR_HSUPA)(ms)
8E+09
7E+09
6E+09
5E+09
4E+09
3E+09
2E+09
1E+09
0
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
RABActivityTimeUL_Traffic034_CR_Ps(UTraffic034_CR_Ps)(ms)
3,5E+09
3E+09
2,5E+09
2E+09
1,5E+09
1E+09
500000000
0
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
RABActivityTimeUL_Traffic034_CR_HSUPA(UTraffic034_CR_HSUPA)(ms)
UTraffic034_CR_HSUPA=1567_14+UC1567_15+UC1567_18
UTraffic034_CR_PS=UC1567_0+UC1567_5+UC1567_6+UC1567_7+UC1567_8+UC1567_9+UC1567_10+UC1567_11+UC1
567_12+UC1567_13+UC1567_14+UC1567_15+UC1567_18
Time that RAB is actively transmitting data in the uplink (HSUPA or PS)-Cell level
39
Benchmark HSDPA- NumberOfCellsWithPAOverload_HSDPA082_CR(UHSDPA082_CR)(nb)

450
400
350
300
250
200
150
100
50
0
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
NumberOfCellsWithPAOverload_HSDPA082_CR(UHSDPA082_CR)(nb)
Number of cells with PA overload. Should be calculated on OZ_CELL3G. Indicator used in Benchmark activities.
NumberOfCellsWithPAOverload_HSDPA082_CR = IF((UC10817>0),1,0)
#10817 Counter_Name: HsdpaPAOverload
Apply to: BTSCellHSDPA Unit: EVENT Range: 0-2^31-1 Type: CUM
Meaning: Number of periods for which the total transmitted power (measurement received from PMM)
exceeded 90% of the maximum cell power configured (mean power during 100ms).
Triggering event: Reception of ATM cell indicating PMM measurement
40
NodeB - VS_eDCHstatus_NbEvt(U10907_NbEvt)(Event)

900000000
800000000
700000000
600000000
500000000
400000000
300000000
200000000
100000000
2/Aug
4/Aug
6/Aug
8/Aug
1/Jul
3/Jul
5/Jul
7/Jul
9/Jul
11/Jul
13/Jul
15/Jul
17/Jul
19/Jul
21/Jul
23/Jul
25/Jul
27/Jul
29/Jul
31/Jul
10/Aug
12/Aug
14/Aug
16/Aug
18/Aug
20/Aug
22/Aug
24/Aug
26/Aug
28/Aug
30/Aug
1/Sep
3/Sep
5/Sep
7/Sep
9/Sep
11/Sep
13/Sep
15/Sep
17/Sep
19/Sep
21/Sep
23/Sep
25/Sep
27/Sep
29/Sep
VS_eDCHstatus_NbEvt(U10907_NbEvt)(Event)
#10907 Counter_Name: eDCHstatus Type: LOAD

Meaning: The LOAD EXCESS status of the HSUPA cell
Triggering event: Fixed observation duration of 100ms
Screening: No
Notes: 0: indicates low cell UL load at reporting time, 1: indicates heavy cell UL load at reporting time. The
Cell is termed as heavily loaded if the measured ROT is above the MaxROT configured for the cell.
41
Aditional indicators affected by counter “U1666_x“ evolution fixed after EP2 instalation
AverageNumberOfDLBearersEstablished_RB013_CR_CsVideo_MAX(URB013_CR_DLCsVideo_MAX)(nb)
AverageNumberOfDLBearersEstablished_RB013_CR_CsVoice_MAX(URB013_CR_DLCsVoice_MAX)(nb)
AverageNumberOfDLBearersEstablished_RB013_CR_HSDPA_BHPos(URB013_CR_HSDPA_BHP)(nb)
AverageNumberOfDLBearersEstablished_RB013_CR_HSDPA_MAX(URB013_CR_HSDPA_MAX)(nb)
AverageNumberOfULBearersEstablished_RB013_CR_HSUPA_MAX(URB013_CR_ULHSUPA_MAX)(nb)
AverageNumberOfULBearersEstablished_RB013_CR_HSUPA_atTrafficBusyHour(URB013_CR_ULHSUPA_TBH)(nb)
AverageNumberOfULBearersEstablished_RB013_CR_Ps(URB013_CR_ULPs)(nb)
42
Domino effect
Counter : 1666 (VS.DlAsConfIdAvgNbrEstablished)
1667 (VS.UlAsConfIdAvgNbrEstablished)
Indicator :
URB021_CR - CumulatedNumberOfDLBearersEstablished_RB021_CR_(HSDPA; PS)
URB022_CR - CumulatedNumberOfULBearersEstablished_RB022_CR_(HSUPA; PS)
URB013_CR_HSDPA=CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA/NumberEventsDLBearersEstablishRelease_RB034_CR_HSDPA
URB013_CR_DLPs=CumulatedNumberOfDLBearersEstablished_RB021_CR_Ps/NumberEventsDLBearersEstablishRelease_RB034_CR_Ps
URB013_CR_ULHSUPA = CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA
/NumberEventsULBearersEstablishRelease_RB034_CR_HSUPA
UTraffic022_CR=(RABActivityTimeDL_Traffic042_CR+RABActivityTimeDL_Traffic042_CR_Sig)/(100*(CumulatedNumberOfDLBearersEstablished_RB021_
CR+CumulatedNumberOfDLBearersEstablished_RB021_CR_Sig))
UTraffic023_CR=(RABActivityTimeUL_Traffic034_CR+RABActivityTimeUL_Traffic034_CR_Sig)/(100*(CumulatedNumberOfULBearersEstablished_RB022_
CR+CumulatedNumberOfULBearersEstablished_RB022_CR_Sig))
Mean HSDPA call duration = CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA / (10*RadioBearerSetupSuccess_RB011_R_HSDPA)

PrimaryCellChangePerMinute_HSUPA006_CR=600*(HSUPAMobilitySuccess_HSUPA016_CR_ItaFeDCHeDCH+HSUPAMobilitySuccess_HSUPA016_CR
_ItrFeDCHeDCH+HSUPAMobilitySuccess_HSUPA016_CR_ItaFeDCHneDCH+HSUPAMobilitySuccess_HSUPA016_CR_ItrFeDCHneDCH)/CumulatedNum
berOfULBearersEstablished_RB022_CR_HSUPA
43

Indicator Changes For UA8.1 Benchmarking Activities Ua8.1 Dr5 Kts

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Indicator Changes For UA8.1 Benchmarking Activities Ua8.1 Dr5 Kts

Uploaded by

Copyright:

Available Formats

Indicator changes for UA8.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Mean HSDPA call duration

CU (41,8) VDF_UK (13,9) VDF_PT (32,0) AT&T (33,0) VDF_Qatar (11,5)

mCell (18,4) Globacom (20,2) WIND (15,9) ETS (56,3)

Mean HSDPA call duration = CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA /

GQ03 GQ07 GQ01 GQ02 GQ04 GQ05 GQ06

8.1.3.1 Tap2 GQ7 EP2 upg.

Mean HSDPA call duration - recomputed

CU (10,7) VDF_UK (13,9) VDF_PT (32,0) AT&T (15,2) VDF_Qatar (11,5)

mCell (18,4) Globacom (20,2) WIND (15,9) ETS (56,3)

CZ_RNC251 CZ_RNC252 CZ_RNC253 CZ_RNC254

0,% 2/Aug 1,02

Note : eDCHActiveUsers_HSUPA008_CR indicator evolution represented on the secondary axis

Max. Code rate Max. data

GQ01 GQ02 GQ03 GQ04 GQ05 GQ06 GQ07

INDPMOXCCRAR01 INDPMOXCCRAR03 INDPMOXCCRAR05

CallSetupSuccessRate_CSSR005_R_Cs indicator with RRCConnectionSuccessRate

CallSetupSuccessRate_CSSR005_R_Ps indicator with RRCConnectionSuccessRate

8.1.3.1 Tap2 GQ7 EP2 upg.

INDPMOXCCRAR01 INDPMOXCCRAR03 INDPMOXCCRAR14 INDPMOXCCRAR17

INDPMOXCCRAR01 INDPMOXCCRAR03 INDPMOXCCRAR14 INDPMOXCCRAR17

Number of HSDPA drops per hour of call

GQ01 GQ02 GQ03 GQ04 GQ05 GQ06 GQ07

Number of HSDPA drops per hour of call = (36000* IuAbnormalReleaseRequest_IU008_R_HSDPA)

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

1,6 After recomputing

2000 After recomputing

8.1.3.1 Tap2 GQ7 EP2 upg.

Here is some background:

CEM CPU load is monitored through counters U10403_CEM_Avg VS_cpuLoad_CEM_Avg

 Counter related to PQ2 load for all CEMs

From UA7138 (121456 - NodeB Overload Step1)

 Counters related to PQ2 load for iCEM

#10403 Counter_Name: cpuLoad

NEA/GCD periodic synchronization meetings organized

8.1.3.1 Tap2 GQ7 EP2 upg.

8.1.3.1 Tap2 GQ7 EP2 upg.

URAB021_R_HSUPA = CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA/ (10*(NZ(RadioBearerSetupSuccess_RB011_R_HSUPA)))

8.1.3.1 Tap2 GQ7 EP2 upg.

UHSUPA014_CR = (600*VS_EdchCellDeletion_RadioLinkFail)/ CumulatedNumberOfULBearersEstablished_RB022_CR_HSUPA

8.1.3.1 Tap2 GQ7 EP2 upg.

8.1.3.1 Tap2 GQ7 EP2 upg.

8.1.3.1 Tap2 GQ7 EP2 upg.

UHSUPA010_CR = eDCHActiveUsers_HSUPA008_CR/ AverageNumberOfULBearersEstablished_RB013_CR_HSUPA

8.1.3.1 Tap2 GQ7 EP2 upg.

EdchActiveCellThpt_HSUPA022_CR (Edch cell throughput over RAB activity period in Kbit/s) =

8.1.3.1 Tap2 GQ7 EP2 upg.

8.1.3.1 Tap2 GQ7 EP2 upg.

#10907 Counter_Name: eDCHstatus Type: LOAD

Mean HSDPA call duration = CumulatedNumberOfDLBearersEstablished_RB021_CR_HSDPA / (10*RadioBearerSetupSuccess_RB011_R_HSDPA)

You might also like