3g kpi-rules
TRANSCRIPT
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 1/61
0 © Nokia Siemens Networks Presentation / Ksu /2008
For internal use
KPI- Rules
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 2/61
1 © Nokia Siemens Networks Presentat ion / Ksu / 2008
For internal use
KPI list, CS
SDCCH Blocking (blck_5a)
SDCCH_Drop (sdr_ 1a, sdr_4)
CSSR, Call Setup Success Rate ( csf_ 11, csf_ 13a, csf_ 15)
TCH Blocking (blck_8i)
Interference, coverage TCH_Drop (dcr_ 32a, dcr_5a)
HO Fails (hfr_2a)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 3/61
2 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI list, PS
GPRS attach success ratio (sgsn_507, sgsn_569c) PDP context activation success ratio MO (sgsn_535a)
Signaling problems before TBF ( pgn_ 3a,pgn_ 10, blck_21b,rach_4,rach_9)
TBF Failure (1-TBF Success ratio = 1 ± TBF_67)
Throughput (trf_234, trf_236, trf_233c, trf_235b,llc_ 3a)
PS Blocking (TBF_ 16a,TBF_ 33a)
Cell re-selection (TBF_64)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 4/61
3 © Nokia Siemens Networks Presentat ion / Ksu /2008
For internal use
KPI ± rules , CS
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 5/61
4 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, SDCCH Blocking
SDCCHBlocking
>X%
Check unavailabilityin the cells,
SDCCHblocking is high
yes
Yes, make
ND_2
11
ND_130Cngt_2Blck_5
Blck_5b
ND_139,ND_131ND_130, uav_22
csf_1a,csf_11 Ava_45a
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 6/61
5 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, SDCCH Drop
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 7/61
6 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, SDCCH Drop (RF)
See do
Call rela¡
edDX
auses ¢ £ ¤ SC,
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 8/61
7 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, SDCCH Drop ( bis)
Abi
bi d p .I id bi il ll
xpi d
AnyI p nts Yes
No
No
Yes
P_nbsc_rx _stat ist iP_nbsc _traff ic
Counters(1072-1080)
P_nbsc_service, counter
57020
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 9/61
8 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, SDCCH Drop (A)
A
>X%
A in r pr l ms. A l rms ar ch ck an Ain r ace t race is
done
o
Ye
alarms
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 10/61
9 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, SDCCH Drop (other)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 11/61
10 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, CSSR, C ll Setup Success R te
SDCCH access ( csf_ 11)
SDCCH success(csf_ 13a, csf_ 13b)
TCH access(csf_ 15)
get
service
get
SDCCH
establish
SDCCH
connection
get
TCH
establish
TCH
connection
call
phase
release
phase
Call Completion Rate (CCR) or
Dropped Call Rate (DCR)
Call Setup Success Rate CSSR or
Call Setup Failure (CSF)
SDCCH
Blocking
(system)
and
SDCCH
call
Blocking
TCH
Blocking
(system)
and
TCH Call
Blocking
SDCCH
Success Rate
Overall Call Success Rate (OCSR) orOverall Call Failure (OCF)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 12/61
11 © Nokia Siemens Networks Presentat ion / Ksu / 2008
For internal use
057019 SERVED_SDCCH_REQ Number of serve SDCCH requests.
UPDATED: When an SDCCH channel is successfully reserved. This counter is updated with allSDCCH requests, except in handovers.
057018 SERVED_FACCH_REQ Number of serve FACCH c ll requests.
UPDATED: When a TCH channel is successfully reserved for an FACCH call set-up. A TCH isreserved, because there is a congestion situation on the SDCCH.
057017 SDCCH_REQNumber of SDCCH requests. When n SDCCH ch nnel is requeste fromthe RRM.
This counter is updated with all SDCCH requests, except in handovers.
KPI- Rules, CSSR : csf_ 11 (Prob bility of h ving nv il ble SDCCH when nee e )
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 13/61
12 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
MS BTS BSC MSC
Paging_Command
Paging
Paging
Paging_Request
To all BTS in LA
INTAT
Radio access part (CCCH)
Channel_Request
Channel_Required
Channel_Activation
Channel_Activation_Ack
Immediate_Assign_Command
Immediate_Assign
DDCH establishment partSabm
Establish_Indication
Paging_Response
Ua
57017 SDCCH_REQ, 57018 SERVED_FACCH_REQ, 57019SERVED_SDCCH_REQ
csf_ 11
KPI- Rules, CSSR : csf_ 11 (Prob bility of h ving n v il bleSDCCH when nee e )
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 14/61
13 © Nokia Siemens Networks Presentat ion / Ksu / 2008
For internal use
Counter explanation:
057028 TCH_CALL_REQ Number of TCH c¥ ll requests.
UPDATED: When the TCH channel is requested from the RRM. This counter includes all TCH requests, except TCH to TCH handovers.
057023 SDCCH_NEW_CALL_ASSIGN Number of SDCCH new c¥ ll
¥ ssignments.
UPDATED: W hen an ESTABLISH_INDICATION message is received on the SDCCH from the BTS in a case of a new call (including MOC, MTC, and emergency call). This counter is not updated in case of an IMSI detach or location update.
057024 SDCCH_HO_CALL_ASSIGN Number of SDCCH h¥ n
¦ over c
¥ ll
¥ ssignments.
UPDATED: When an ASSIGNMENT_COMPLETE or a HANDOVER_COMPLETE message is received on the SDCCH from the BTS in case of an SDCCH to SDCCH handover (including only calls: MOC, MTC, emergency call and re-establishments). In case of anexternal SDCCH to SDCCH handover or after an external handover, this counter is updated withall SDCCH assignments.
057022 SDCCH_RE_EST_ASSIGN Number of SDCCH re-est¥ blishment
¥ ssignments.
UPDATED: When an ESTABLISH_INDICATION message for a call re-establishment is received on the SDCCH from the BTS.
057026 SDCCH_RE_EST_RELEASE Number of SDCCH re-est ¥ blishment rele ¥ ses.
UPDATED: When the SDCCH is released (after a RF_CHANNEL_RELEASE message) without any problems and the SDCCH channel is reserved for a re-establishment. Thiscounter is not updated after an external SDCCH to SDCCH handover.
057025 SDCCH_SMS_ASSIGN Number of SDCCH SMS¥ ssignments.
UPDATED: MS originated: When an ESTABLISH_INDICATION message is received on the SDCCH from the BTS in case of an SMS. MS terminated: When anESTABLISH_CONFIRM message is received on the SDCCH from the BTS in case of an SMS.
057027 SDCCH_HO_RELEASE Number of SDCCH h¥ n
¦ over rele
¥ ses.
UPDATED: When the SDCCH is released without any problems and the SDCCH channel is reserved for a handover.
003059 CALL_ASSIGN_AFTER_SMS Number of c¥ lls st
¥ rte
¦
¦ irectly
¥ fter
¥ n SMS on the
¥ lre
¥ ¦ y reserve
¦ SDCCH.
UPDATED: When an ASSIGNMENT REQUEST message is received directly after a successful SMS on SDCCH from the MSC.
KPI- Rules, CSSR : csf_ 13a (Probability of completing all theSDCCH signalling without rop)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 15/61
14 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
MS BTS BSC MSC
Paging
Radio access part (CCCH)Channel_Request
Channel_Required
Channel_Activation
Channel_Activation_Ack
Immediate_Assign_Command
Immediate_Assign
DDCH establishment partSabm
Establish_Indication
Paging_Response
Ua 57021 SDCCH_ASSIGN, 57022 SDCCH_RE_EST_ASSIGN[in re-establishment], 57023 SDC57025 SDCCH_SMS_ASSIGN 57033 TCH_NEW_CALL_ASSIGN [in FACCH call setup]
csf_ 13a
csf_ 11
Assignment_Request
Start T9108
Physical_Context_Request
Physical_Context_ConfirmationStop T9108
SDCCH signalling up to TCH seizure
Authentication_Request Authentication_Request
Authentication_Response Authentication_Response
Identification_RequestIdentification_Request
Identification_Response Identification_Response
Ciphering_Mode_CommandEncryption_CommandCiphering_Mode_CommandCiphering_Mode_Complete Ciphering_Mode_Complete
SetupSetup
Call_Proceeding Call_Proceeding
57028 TCH_CALL_REQ, 57030 SERVED_TCH_CALL_REQ, 57031 SERVED_DR_REQ
3059 TCH_ASSIGN_AFTER_SMS
KPI- Rules,CSSR
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 16/61
15 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
Counter explanation:
057018 SERVED_FACCH_REQ Number of serve FACCH call requests.
UPDATED: When a TCH channel is successfully reserved for an FACCH call set-up. A TCH is reserved, because there is acongestion situation on the SDCCH.
057031 SERVED_DR_REQ Number of serve DR requests.
UPDATED: When the TCH channel is successfully reserved in case of a normal directed retry. This counter is also updated with S6feature TCH Assignment to Super -reuse TRX in IUO (intra-cell/inter -cell directed retry). This counter is not updated with S7 featureDirect Access to Super -reuse TRX in IUO.
057030 SERVED_TCH_CALL_REQ Number of serve TCH call requests.
UPDATED: When the TCH channel is successfully reserved for a normal call. This counter is also updated with S7 feature Direct Access to Super -reuse TRX in IUO. This counter is not updated in a case of TCH to TCH handover, normal directed retry or S6feature TCH Assignment to Super -reuse TRX in IUO (intra-cell/inter -cell directed retry).
057033 TCH_NEW_CALL_ASSIGN Number of TCH new call assignments.
UPDATED: When an ASSIGNMENT_COMPLETE message is received on TCH from the BTS in a case of a new call. In a case of FACCH call set-up due to SDCCH congestion, this counter is updated, when an ESTABLISH_INDICATION message isreceived on the TCH from the BTS. In case of normal directed retry (inter -cell directed retry), this counter is updated, when aHANDOVER_COMPLETE message is received on the TCH from the BTS. This counter is also updated with S6 feature TCH Assignment to Super -reuse TRX in IUO (intra-cell/inter -cell directed retry) and with S7 feature Direct Access to Super -reuse TRX inIUO. If external SDCCH to SDCCH handover is made after a re-establishment, this counter is also updated.
KPI- Rules, CSSR : csf_ 15 (Probability of successfully gettingthe MS on the TCH
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 17/61
16 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
MS BTS BSC MSC
Assignment_Request
Start T9108
Physical_Context_RequestPhysical_Context_Confirmation
Stop T9108
Start T9103
Channel_Activation
Stop T9103
Channel_Activation_Ack
Assignment_Command StartT10,T3107
TCH seized
SDCCH signalling up to TCH seizure Authentication_Request Authentication_Request
Authentication_Response Authentication_Response
Identification_RequestIdentification_Request
Identification_Response Identification_Response
Ciphering_Mode_CommandEncryption_CommandCiphering_Mode_Command
Ciphering_Mode_Complete Ciphering_Mode_Complete
SetupSetup
Call_Proceeding Call_Proceeding
(TA info)
TCH DROPS AFTER SEIZURE TCH_RADIO_FAIL /c1013+TCH_RF_OLD_HO /c1014+TCH_ABIS_FAIL_CALL /c1084
+TCH_ABIS_FAIL_OLD /c1085+TCH_A_IF_FAIL_CALL /c1087+TCH_A_IF_FAIL_OLD /c1088+TCH_TR_FAIL /c1029+TCH_TR_FAIL_OLD /c1030+TCH_LAPD_FAIL /c1046+TCH_BTS_FAIL /c1047+TCH_USER_ACT /c1048+TCH_BCSU_RESET /c1049+TCH_NETW_ACT /c1050+TCH_ACT_FAIL_CALL /c1081
57028 TCH_CALL_REQ, 57030 SERVED_TCH_CALL_REQ, 57031 SERcsf_ 14drops after this point
Assignment_Command (SDCCH)
Start T200 SABM (FACCH)Establish_Indication
UA (FACCH)Stop T200
Assignment_Complete (FACCH) Assignment_Complete
StopT10,T3107
Assignment_Complete
SDCCH signalling: MS moves on TCH, SDCCH released
MS on TCHTCH DROPS AFTER ASSIGNMENT
(Connection Failure from BTS, DX
cause >= 300)spare057044 /c57044 (S10.5)
d rop _ after _TCH_ assign c1202(S11) drops after this point
csf_ 15
csf_ 13
Dcr_ 8e
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 18/61
17 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, TCH Blocking
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 19/61
18 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI- Rules, cover age problems (dlq_ 2a and ulq_ 2a)
§ ere are some examples ̈ o©
diff eren
ind of problems can be f ound
Like ormal dis
r ibu
ion §
Problem,
R
/combiner e
c is broken 0 1 Q2 Q Q4 Q5 Q6 Q7 Q0 Q1 Q2 Q Q4 Q5 Q6 Q7
L
10645 8516 681
5450 4
60 3488 2791 2232 CL
5323 4258 3406 2725 2180 1744! " # $ % & # "
CL "
47043 37634 30108 24086 9865 7543 5643 2345 CL "
11761 9409 7527 6022 9383 1886# " ! $
2& # & "
CL2
56204 44963 35971 28776 6574 10324 345 65 CL2
14051 11241 8993 7194 18271 2581# " ! $ ' # $ " #
2CL
$
200863 160690 128552 102842 17654 9876 145 28 CL$
33772 27017 21614 17291 75037 2469 ' & # " ! "
2$
CL!
12785 10228 8182 6546 456 112 24 23 CL!
3196 2557 2046 1636 4938 28$ # " %
2# ! '
CL# $
4583 1123 583 452 261 76 26 2 CL# $
1146 281 146 113 3378 19 & !
HW problem, ( 4 amoun
of samples is s
r ange In
er f erence problemQ0 Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL
5323 4258 3406 2725 2 '
1744 1395 1116 CL
5323 4258 3406 2725 2 '
&
44 1395 1116CL15 23522 18817 15054 12043 18765 3772 2822 1173 CL15 23522 13234 10588 8470 13234 10588 8470 6776CL20 28102 22482 17985 14388 36542 5162 173 33 CL20 28102 2123 1699 1359 2123 1699 1359 1087CL30 67544 54035 43228 34582 150073 4938 73 14 CL30 67544 3634 2908 2326 3634 2908 2326 1861CL40 6393 5114 4091 3273 9876 56 12 12 CL40 6393 4091 3273 2618 4091 3273 2618 4532CL63 2292 562 292 226 6756 38 13 1 CL63 9987 7543 4323 3454 2275 1187 876 654
HW Problem,
R
/combiner e
c is brokenQ0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 200863 160690 128552 102842 17654 9876 7865 6543CL15 16543 13234 10588 8470 6776 2822 1173 234CL20 2654 2123 1699 1359 1087 173 33 65CL30 4543 3634 2908 2326 1861 73 14 28CL40 5114 4091 3273 2618 2095 12 12 23CL63 24 54 8 87 7 0 0 0
1
2
3
1. Lots of Q4 samples. Distribution is not OK HW problem. Site reset will help
2. Lots of bad signal level samples. TRX/Combiner is broken. If no HW problem
Site is totally in wrong place, site is like transferring traffic to another cell ( causelevel HO). Typically a HW problem
3. Lots of Q6 and Q7 samples. Distribution is not OK, no Q5 samples HW
problems. Site reset or broken TRX
4. Typical normal interference problem.
Here are some examples how different kind of HW problems can be found
4
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 20/61
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 21/61
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 22/61
21 © Nokia Siemens Networks Presentat ion / Ksu / 2008For internal use
KPI- Rules, Interference, UL, e amples
) 0
1
2 0 ) 0
1
2 1 UL_q2 UL_q
3 UL_q
4
UL_q5
UL_q6
UL_q7
DL_q0 D L_ q1 D L_ q2 DL_q3
DL_q4
DL_q5
DL_q6
DL_q7
8
100 9 @ m 2 5 1 A A 2 3 0 6 6 8 20 5 5 2 184
1 7 181 5 6 1828 6 1 6 A 8 3 124
7 8 2 7 8 6 2 5 5 3 7 5 5 2 A 6 0 6 A 6 10 A 6 10 7 5 3 8 A
4
11 A
8
A 5 dBm 12 3 6 5 3 11
5 1
4
0 3 6 A 2 5 1
A 3 5 1 221
7 2 8 A 0 A
4 4
2 3 6 3 8 5 3 3 5 7 6 28 A 3 22 6
4
13 7 2 5 8
4
- A 0dBm 6 2 A 3 8 24
7 1
4 4
288 3 5 3 12 A 6 2 2 A
14
2228 2 7 3 2 2 5 5 0 2 3 5 6 1
5 10 111
4
7 7
4 4
04
-80dBm 2 7 00 5 5 1
6 5 1
4
A 1
7 7 824
0 16 222
4
6 2 15 2 3
13 5 5
15 5 2 7
16 812 1081
3
4
3
- 7 0dBm 28 3 1
3 A 28 8 7 10 6 0
4 4
5 04
A 1 12 3
15
1 81 101 1A
1 88
-4
7 dBm 7 5
1 04
10 25
1 0 05 A A
4 4
A
17
17
12 2A 6 5
10
Huge amount of UL bad samples. Cells is not working properly, it is like transferring traffic, UL quality/ UL level HO¶s aretriggering immediately. These kind of cells must be investigated.
UL_q0 UL_q1 UL_q2 UL_qB
UL_qC
UL_qD
UL_qE
UL_qF
-100dBmC G
0 1B
F B E
8E
0D
101C
1B
F
8 18B
0 2D
8E
-G D
dBm 8C
10B F E
8B
22D B
02B
2F E F
2B
0C
1D E
1 18D G
-G
0dBm
B
8D
12D
2
C G B
0
E E
2
B
2
B
1
E G
2 1
D F
0 11
G
1 12
E
8-80dBm 21
G
1B F C E
00 2C D B
2B
11 1C F
0 1F
2C
18E C
1221
-F
0dBmD
0G
D G
1 2D
0C
1812B
0D
0 12F
1 1C E
D
1E C G B B
F
-C F
dBm 2C C B
02D
82F
11 1B E B
1F
1B
8F B E F
1 8F
UL_q0 UL_q1 UL_q2 UL_qB
UL_qC
UL_qD
UL_qE
UL_qF
-100dBmF
000C
D
020B
D
00 2D
E C
22B
2 1G C E
21G
0 2D F
G
-G D
dBm 80B B G B G
2 28E C E
1B
28 2D
0 2F D G
2
-G
0dBm 10E
88B
2B B B
18E
02 1G G
1C E
2B C E C
-80dBm 2C E
8G
2 22F B
1C
8E
0 2G
8B B
8B G D E
0
-F
0dBm 2D
C
8F D
1D D
2G
8G B
D
20B
1B
D
1E E
1D
-C F
dBm 2B
288 21 2F
10B
10G
11C
1 0
Some UL interference in good signallevel. UL power control is not
working properly. Ul power control isgood indicator, if power is ad justed,there are no big problems in UL direction
There is no UL interference, or just alittle. MS is ad justing power properly,
there are only little samples in good UL signal level.
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 23/61
22 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
H
0H
I
H
2H
P
H
Q
H
R
H
S
H
T
-100dBmI
0S Q
R
8R
I
S S
8I
P R
Q R
0Q P S
0P Q
88 2T
U
I
22P
2
-95dBmQ T
0Q P P T S P Q P
0I 08 2
Q
08S U
8S R T R Q P R S Q P
2P Q R
-90dBm
R S
20
Q Q Q U S P P R
U T
I
28
T T S
I
S R T
Q R
S T
S
8
Q R
S R
-80dBm 2008S P
I
S
0S U
0I 28
R R
2I 028
Q
2I
T S
R Q P S
R P
I
Q R
28
-70dBmI 2
T
8R
I 0228 8
I 82
S R Q S Q R S
I I 2 2
Q
2P
-47dBmQ
R
8P
I I 2P
R
8P Q
R
2 2S
I
T S
2S
2
KPI- Rules, Interference, DL
Bad interference problem ĺ signal level good (<-80dBm)and sometimes no better cell available. If better cellavailable and uality samples are or worse ĺ HO (reason
uality or interference, depends on the parameter)Interference is causing drops.
Really bad interference problem ĺ signal level is reallygood (<- 0dBm) and usually no better cell available ĺ noHO ĺ samples can be seen in the table. Interference is
causing drops.
Situation is ³network is working properly´ If there are ualityor worse samples ĺ uality HO. Most of the samples aresamples. If lots of .. samples ĺ interference
problem and interference must be analyzed / removed. If uality HOs but no .. samples ĺ better cell is available
ĺ no interference problems. In these signal levelsoverlapping exists and if handover reason is no PBGT, it willbe uality HO. By parameter amount of uality HOs can beadjusted
H
0H
I
H
2H
P
H
Q
H
R
H
S
H
T
-100dBm I 0
S Q R
8R
I
S S
8I
P R Q R
0Q P S
0P Q
88 2T U
I 22
P
2
-95dBmQ
T
0Q P P
T S P Q P
0 I 08 2Q
08S U
8S
R T R Q P
R S Q P
2P Q
R
-90dBmR
S
20Q Q Q U S P P
R U
T
I 28T T
S
I
S R T
Q R
S T
S
8Q
R S
R
-80dBm 2008S P
I
S
0S U
0I 28
R R
2I 028
Q
2I
T S
R Q P S
R P
I
Q R
28
-70dBmI 2
T
8R
I 0228 8
I 82
S R Q S Q R S
I I 2 2
Q
2P
-47dBmQ
R
8P
I I 2P
R
8P Q
R
2 2S
I
T S
2S
2
H
0H
I
H
2H
P
H
Q
H
R
H
S
H
T
-100dBm I 0
S Q R
8R
I
S S
8I
P R Q R
0Q P S
0P Q
88 2T U
I 22
P
2
-95dBmQ T
0Q P P T S P Q P
0I 08 2
Q
08S U
8S R T R Q P R S Q P
2P Q R
-90dBmR
S
20Q Q Q U S P P
R U
T
I 28
T T S
I
S R T
Q R
S T
S
8Q
R S
R
-80dBm 2008S P
I
S
0S U
0I 28
R R
2I 028
Q
2I
T S R Q P S R P
I
Q R
28
-70dBm I 2
T
8R
I 0228 8
I 82
S R Q S Q R S
I I 2 2
Q
2P
-47dBmQ
R
8P
I I 2
P R
8P Q
R
2 2S
I
T S
2S
2
H
0H
I
H
2H
P
H
Q
H
R
H
S
H
T
-100dBm I 0
S Q R
8R
I
S S
8I
P R Q R
0Q P S
0P Q
88 2T U
I 22
P
2
-95dBmQ T
0Q P P T S P Q P
0I 08 2
Q
08S U
8S R T R Q P R S Q P
2P Q R
-90dBmR S
20Q Q Q U S P P R U T
I 28
T T S
I
S R T Q R S T S
8Q R S R
-80dBm 2008S P
I
S
0S U
0I 28
R R
2I 028
Q
2I
T S
R Q P S
R P
I
Q R
28
-70dBm I 2
T
8R
I 0228 8
I 82
S R Q S Q R S
I I 2 2
Q
2P
-47dBmQ R
8P
I I 2
P R
8P Q R
2 2S
I
T S
2S
2
Bad uality samples due to signal level problems. If PBGToverlapping is not existing ĺ lots of uality HOs + levelHOs (margin are lower than in PBGT).
Not interference problem, more signal level problem.
Check how much samples vs. HOs ĺ are
better cells available or not.
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 24/61
23 © Nokia Siemens Networks Presentat ion / Ksu / 2008For internal use
KPI- Rules, Interference, DL, e amples
V W
X
Y
0V W
X
Y ` V W
X
Y
2V W
X
Y
3V W
X
Y
a
V W
X
Y b V W
X
Y c V W
X
Y d
e ̀00
f g m ̀ 20b d 282d 3 ̀ 08 3 h b 2
a
d 83 c 200 d 0 ̀ 3 8 ` b c
e h b f g m
a a
8 ̀8
a
8` ` b
0a
` b 8
c c c b 8
d d 223
d 2
b h c d 8
̀
e h 0f g m h 8
b 8
d d ̀0
d d
a
00 833a
8a
d 0 8
d 8
` d 82
b c ` c 2
e 80f g m 22b h ` h d
a
b 0
d d 3
̀8
a a
b d d 2
c d
a a
` b c h b 33
c h
e d 0
f g m 88
d 08
̀0
̀
a
h d ` h h 8
d b ` c 88
c 8
h 3
c d
e
a
d f g m ` b 88 ̀ 8
a
̀ 0 h ̀ 22 ̀ 0a
` c d ` h h ` 8a
V W
X
Y 0
V W
X
Y ` V W
X
Y 2
V W
X
Y 3
V W
X
Y
a
V W
X
Y b V W
X
Y c V W
X
Y d
e ̀00
f g m 800
c ` c 3
c ` c 8
̀2
` h d 23
d h 2
b ̀0 202
b ̀2
h 0
e h b f g m 2
a
h b ` ` c 3
c ` c 2
d ` d c d ` 03
d
a
3` ` d b b
3
e h 0f g m b d b b h 2
` d ` ` 88
a
` c b ` d 8
̀330
` c ̀
a
d
e 80
f g m 200
c 02
b d d `
a
c 8
c
a
̀30
` d 3
c b c c 2
b
a
h d
e d 0
f g m 30
a
20c b
a
c
a a
3 ̀0 3
d h c ` 3
` b 3
b 0
` b 3
̀0
b
e
a
d f g m ̀
080a
d 2
̀3
a
` h 08
` c 23
c 8
h 230
̀2
h c
a
There are almost as much samples Q an Q samples as
Q samples ĺ even interference is really ba or there isno better cell available ( no ho¶s after ba uality samples).These kin of interference cells shoul be optimize ,otherwise there are lots of rops etc
There are no as much Q «Q samples as Q samples ĺ
after interference samples Quality HO is one or theinterference situation is not so ba , for example sampling isQ0,Q2,Q ,Q2,Q ,Q0,Q2,Q3,Q ,Q2 ĺ uality HO is nottriggering
V W
X
Y 0 V W
X
Y ` V W
X
Y 2 V W
X
Y 3 V W
X
Y
a
V W
X
Y b V W
X
Y c V W
X
Y d
e ̀ 00f g m d 0
b b ̀3
h 8
̀3
d
a
` h 0
c 2
` c 3 2003
̀
a
c 8 832
e h b f g m 20
̀0
h ̀30
d ̀2
d
a
` ` c ` c h
a
332 2` ̀
8a
e h 0f g m 3a
b 3 ` ̀ 0 b 3 d
a
b b 8 d 2 d 3 ̀ 3 ` h
a a
̀
e
80f g
m ̀0
d b 3
h 8
d b b ` 8
c 30
` c ` h 8
` ̀3
a
d
e d 0f g m ` d d c `
a
283 3` c c c
3c ̀
32 2h h
e
a
d f g m b
8d ̀
8d 8
h ` ` h 8
b
a a
0b
a
32
There are ba uality samples only ue to signal levelproblems.
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 25/61
24 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI- Rules, Interference (internal e ternal)
Internal Interference ± Interference can be seen from stats or can be measured by scanner.
± Neighbor cells (DL) or mobiles (UL) are causing interference.
± By frequency / network planning interference can be decreased.
External Interference
± Interference can be seen from stats or can be measured by scanner.
± External radio frequencies are causing interference
ƒ Military use
ƒ In the border area, interference is coming from other country.
ƒ Some external wireless system (for example some wireless industrysystem) is causing interference
ƒ Increased I level can be also due to external interference
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 26/61
25 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
TCH SEIZURES FOR NEW CALL
tch_norm_seizi
c1009
+tch_seiz_ due_sdcch_coni
c1099 (S5)
+msc_i_sdcch_tchi
c4044
+bsc_i_sdcch_tchi
c4057
+cell_sdcch_tchi
c4074
-tch_succ_seiz_for_ dir_ acci
c1165 (S7)
-tch_ re _ est _ assign /c57032 (S7)
TCH DROPS AFTER SEIZURE TCH_RADIO_FAIL /c1013+TCH_RF_OLD_HO /c1014
+TCH_ABIS_FAIL_CALL /c1084+TCH_ABIS_FAIL_OLD /c1085+TCH_A_IF_FAIL_CALL /c1087+TCH_A_IF_FAIL_OLD /c1088+TCH_TR_FAIL /c1029+TCH_TR_FAIL_OLD /c1030+TCH_LAPD_FAIL /c1046+TCH_BTS_FAIL /c1047+TCH_USER_ACT /c1048+TCH_BCSU_RESET /c1049+TCH_NETW_ACT /c1050+TCH_ACT_FAIL_CALL /c1081
-tch_ re _ est _ assign /c57032 (S7)
DROPS
CALLS
100 * %
STARTED CONVERSATIONS
conver_started p
c57015
- msc_i_tch_tchp
c4043
CONVERSATION DROPS dropped _calls /c57007
TCH DROPS AFTER ASSIGNMENT tch_ new _call _ assign /c57033+tch_ho _ assign /c57034
-tch_ norm _ release /c57035-tch_ho _ release /c57036
-tch_ re _ est _ assign /c57032
TCH ASSIGNMENTS FOR NEW CALLtch_ new _call _ assign /c57033
-tch_ re _ est _ assign /c57032
TCH RELEASEDisconnect from MS
RF CHN RELEASERf_channel_release_ack
from BTS
CONVERSATION STARTEDconn_ack to BTS
TCH ASSIGNEDAssignment_complete from BTS
TCH SEIZEDBSC allocates a TCH as a response toTCH request (Channel Activation)
Dcr_ 8h
Dcr_ 5a
Dcr_ 3j
KPI- Rules, TCH Drop Call Ratios
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 27/61
26 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI- Rules, TCH Drop
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 28/61
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 29/61
28 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI- Rules, TCH Drop (abis)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 30/61
29 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI- Rules, TCH Drop (A)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 31/61
30 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI- Rules, TCH Drop (TR)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 32/61
31 © Nokia Siemens Networks Presentat ion / Ksu / 2008For internal use
KPI- Rules, TCH Drop (Other)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 33/61
32 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI- Rules, HO f ail
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 34/61
33 © Nokia Siemens Networks Presentat ion / Ksu / 2008For internal use
KPI- Rules, HO f ail
sum(msc_o_succ_ho + bsc_o_succ_ho + cell_succ_ho)
Total HO success ratio = 100 * (-------------------------------------------------------------------------------- ) (ho_65)
sum(msc_o_ho_cmd + bsc_o_ho_cmd_assgn + bts_ho_assgn)
sum(a.msc_o_succ_ho + a.bsc_o_succ_ho + a.cell_succ_ho +a.msc_to_wcdma_ran_succ_tch_ho)
Total HO failure ratio = 100 * (1- -------------------------------------------------------------------------------------) (hfr_2b)
sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn +
b.bts_ho_assgn+a.msc_gen_sys_wcdma_ran_ho_com)
/* handovers failing due to blocking */
sum(a.msc_o_fail_lack + a.bsc_o_fail_lack + a.cell_fail_lack
+ a.msc_to_wcdma_ran_fail_lack)
HO failure ratio due to RF blocking = 100 * ---------------------------------------------------------------------------------------
/* all HO attempts */sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn +
b.bts_ho_assgn + a.msc_gen_sys_wcdma_ran_ho_com)
(hfr_55a)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 35/61
34 © Nokia Siemens Networks Presentation / Ksu /2008For internal use
KPI ± rules , PS
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 36/61
35 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI list, PS
GPRS attach success ratio (sgsn_507, sgsn_569c)
PDP context activation success ratio MO (sgsn_535a)
Signaling problems before TBF ( pgn_ 3a,pgn_ 10, blck_21b,rach_4,rach_9)
TBF Failure (1-TBF Success ratio = 1 ± TBF_67)
Throughput (trf_234, trf_236, trf_233c, trf_235b,llc_ 3a)
PS Blocking (TBF_ 16a,TBF_ 33a) Cell re-selection (TBF_64)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 37/61
36 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, GPRS attach
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 38/61
37 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, GPRS attach
GPRS att ach, SGSN
Proble s wit h rsatt ach
Is f ailure co e #14,
Get t he GPRS att ach f ailures st at ist ic based on causecode f rom t he Net act Tools K P I Browser / Report
Browser) or Analyzer (e. . Net hawk Analyzer)SGSN count ers
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 39/61
38 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, GPRS attach
G RS att a , t e t tool
P roble wiatt a
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 40/61
39 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, PDP conte t activations
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 41/61
40 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, Signaling problems before TBF
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 42/61
41 © Nokia Siemens Networks Presentat ion / Ksu / 2008For internal use
KPI-rules, Signaling problems before TBF(PCH paging)
PCH
CS:
-p
-pPS:-p
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 43/61
42 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, Signaling problems before TBF(AGCH)
AG H
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 44/61
43 © Nokia Siemens Networks Presentat ion / Ksu / 2008For internal use
KPI-rules, Signaling problems before TBF(RACH)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 45/61
44 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, Signaling problems before TBF(SDDCH)
Check SDCCH Blocking earlier (CS)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 46/61
45 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, TBF Failure
TBF f ilu e
TBF f ilu
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 47/61
46 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
KPI-rules, Throughput
Thr u hput
Thr u hput / TS isl w
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 48/61
47 © Nokia Siemens Networks Presentation / Ksu /2008For internal use
Maximize Throughput ± Optimization Flowcharts
RLC MAC TSL Data Rate Maximization
Multislot Usage Maximization
E2E Data Rate Maximization
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 49/61
48 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
RLC MAC TSL Data Rate Maximization
trf_235b < 10 kbps or
trf_236 < 30 kbpsGSM audit (list1)
yes
GSM optimization (list2)
GSM Network
Maximize multislot usage
trf_235b < 10 kbps or
trf_236 < 30 kbps
yes
no
Maximize TSL data r ate
no
Maximize TSL data r ate List1
Signal level, C/I level, capacity audit
Parameter and feature setup audit
Neighbor audit
Site arrangement audit
List2
Signal level, C/I level, capacity optimization
Parameter and feature setup optimization
Neighbor and Location area optimization
Site arrangement optimization (antenna tilt,
effective antenna height, etc)
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 50/61
49 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
RLC MAC TSL Data Rate Maximization
trf_235b < 10 kbps or
trf_236 < 30 kbps
EDAP and PCU connectivity capacityoptimization
(Refer to slide 9 and 10)
yes
Maximize multislot usage
trf_235b < 10 kbps or
trf_236 < 30 kbps
yes
no
Maximize TSL data r ate
no
Maximize TSL data r ate
Connectivity
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 51/61
50 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
RLC MAC TSL Data Rate Maximization Resource allocation
trf_235b < 10 kbps or
trf_236 < 30 kbpsCell (re)-selection parameter optimization (list1)
yes
BTS selection parameter optimization (list2)
trf_235b < 10 kbps or
trf_236 < 30 kbps
yes
no
Maximize multislot usage
trf_235b < 10 kbps or
trf_236 < 30 kbps
yes
no
Maximize TSL data r ate
no
Maximize TSL data r ate List1
Deployment strategy optimization
C1 and HYS parameter optimizationC2 parameter optimization
NCCR feature optimization
List2
Deployment strategyoptimization
NBL and DIRE parameter optimization
LSEG, GPL and GPU
parameter optimization
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 52/61
51 © Nokia Siemens Networks Presentat ion / Ksu / 2008For internal use
RLC MAC TSL Data Rate Maximization
trf_235b < 10 kbps or
trf_236 < 30 kbps
Uplink Penalty and
Uplink Threshold parameter audit / changing to recommended set
yes
TBF release and BS_CV_Max parameter audit / changing to recommended set
trf_235b < 10 kbps or
trf_236 < 30 kbps
yes
no
Maximize multislot usage
trf_235b < 10 kbps or
trf_236 < 30 kbps
yes
no
Maximize TSL data r ate
no
Maximize TSL data r ate
Feature parameterization
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 53/61
52 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
RLC MAC TSL Data Rate Maximization
trf_235b < 10 kbps or
trf_236 < 30 kbps
LA (MCA) optimization and
PC parameter audit / changing to recommended set
yes
Multiplexing usage audit and optimization (list1)
trf_235b < 10 kbps or
trf_236 < 30 kbps
yes
no
Maximize multislot usage
trf_235b < 10 kbps or
trf_236 < 30 kbps
yes
no
Maximized TSL data
r ate
no
Maximize TSL data r ate
Feature parameterization
List1
Reduce TSL sharing
Avoid GPRS and EGPRSmultiplexing on the same
RTSL
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 54/61
53 © Nokia Siemens Networks Presentat ion / Ksu / 2008For internal use
Multislot Usage Maximization
CMAX=CDEF OR
0.75*CMAX <peak_gprs_territory
check list1CDEF > ava_44
List1
If AMR and/or HR isused add Dual rate TSL
If Dual rate not possible
add TRX (need to checkthe PCU, A-bis and Gbcapacity)
CS traffic management
(change HOparameters, resource
managementparameters)
Increase nbr of dedicated PS timeslots
Increase CMAX
(or add/enable TRXs with GTRX=y)
check territory upgrade reasonsHo_61 = ³big´
PS triggers
Trf_241
Increase CDEF
CS triggers
Trf_240
Decrease CDEF if PS traffic is small,
otherwise check the listed items
max(tbf_ 37c, tbf_ 38c)>1.2
AND
max(tbf_ 15, tbf_ 16) >0.5% AND
blck_ 33 > 10%
Check list1
yes
yes
yes
yes
Maximize multislot usage
Maximize multislot usage
PSW Territory
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 55/61
54 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
Multislot Usage Maximization
EDAP and PCU connectivity capacity optimization
(Refer to slide 9 and 10)
yes
Maximized multislot usage
Maximize multislot usage
dap_7a > 150 min/GB
blck_ 32 > 0.1%
dap_9 > 30 min/GB
no
Connectivity
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 56/61
55 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
Multislot Usage Maximization
C_076007=³big´ AND
C_076004 = 100%
C_076007=³big´ AND
C_076004 < 100%
Blck_ 32 > Th3
Increase EDAP if Gb link size supports
and llc_ 3=smaller than BSC average in cells
PCU re-planning if llc_ 3=smaller than average
in BSC for cells connected to EDAP
Add new PCUs or PCU re-planning
Next
EDAP/Cell
Yes
Yes
Yes
Maximize multislot usage
Connectivity
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 57/61
56 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
Multislot Usage Maximization
Dap_7a (or Dap_ 13) > Th1
Dap_9, Dap_ 10 > Th2
(Dap_ 15(DL), Dap_ 14(UL))
Blck_ 32 > Th3
Increase EDAP if Gb link size supports
and llc_ 3=smaller than average in BSC for
cells connected to EDAP
PCU re-planning if llc_ 3=smaller than average
in BSC for cells connected to EDAP
Add new PCUs or PCU re-planning
Next EDAP/Cell
Yes
Yes
Yes
Connectivity
Maximize multislot usage
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 58/61
57 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use
E2E Data Rate Maximization (limited)
llc_ 3 < x kbps
trf_235b < 10 kbps or
trf_236 < 30 kbps
Flow control capacity (Refer to slide 12)
and parameter audit / changing to
recommended set (refer to TN819)
yes
HLR parameter audit / changing to
recommended set for different HLR profiles (list1)
yes
Maximized multislot usage
no
Maximize E2E data rate
llc_ 3 < x kbps
no
List1
Delivery order
Residual BER
SDU error rate
Delivery of erroneous SDUs
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 59/61
58 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
Gb Performance Analysis ± FR for EGPRS
Frl_8a> utilization threshold
Yes
Increase Gb capacity
Frl_8a : Maximum received load % ( DL)
Gbbandwidth[kbps]
Restricting Gblink
utilization[%]
128 25
256 61
384 68
512 68
640 70
768 75
896 85
1024 90
Note: Maximum received load threshold depend on used application!
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 60/61
59 © Nokia Siemens Networks Presentation / Ksu / 2008
For internal use
KPI-rules, PS Blocking
P _ lo in>X%
of or ard_ loard en i is
i por an o r
C ase C los
no
_802 _290
7/29/2019 3G KPI-rules
http://slidepdf.com/reader/full/3g-kpi-rules 61/61
For internal use
KPI-rules, Cell re-selection