Version Date Author

Comments
Figure1:TCH Drop Call Ratio-Formulas
Figure2: TCH Drop call ratio (dcr_32a)
Figure3: TCH Drop call ratio (dcr_32a) -reasons

TCH DROP counters

Root Cause
RF reason Rf call c1013 Radio failures
RF reason Rf old c1014 Radio failures on old channel in HO
HW problems Tc fail c1029 Transcoder failures
HW problems Tc old c1030 Transcoder failures of old channel in HO
RF/HW reason Abis call c1084 Abis failures
RF/HW reason Abis old c1085 Abis failures on old channel in HO
RF/HW reason Aif call c1087 A if failures
RF/HW reason Aif old c1088 A if failures on old channel in HO
HW problems Lapd c1046 Lapd failures
HW problems BTS c1047 BTS failures
user Usr c1048 Failures due to user actions
reset BCSU c1049 Failures due to BCSU reset
HW problems Cfg c1050 Failures due to radio network configuration action
RF reason Act c1081 Failures due to channel activation nack
RF/HW reason BSC i HO c4084 Drop calls in BSC controlled incoming HOs
RF/HW reason BSC o HO c4085 Drop calls in BSC controlled outgoing HOs
timer T3101 Expired (S9)
timer T9103 Expires
timer T3107 Expired

TCH DROP KPIs

dcr_31a TCH drop call ratio after TCH seizure beforer re-establisment. On the
area level. This KPI indicates how much calls are dropped after TCH
seizure.
Experiences on Use: In good networks where optimisation has been done
already for two to three years, values have been around 2 to 3 per cent
(and in networks in which no optimisation has been done yet the values
remain even above 10 per cent. A value of 5 per cent is achievable in
many networks despite their bad initial coverage planning. Interference
also raises the figure. Be careful when setting the target values since the
factors (whether caused by the customer or Nokia) can be time-
consuming and expensive to prove. If used on cell level, the values can
be even over 100 per cent if a cell takes HOs in but then drops them.
dcr_32a TCH drop call ratio, after re-establishment Use: On the area level.
Experiences on Use: In good networks where optimisation has been done
already for two to three years, values are around 2 to 3 per cent. In
networks in which no optimisation has been done yet the values are even
as high as 10 per cent. A value of 5 per cent is achievable in many
networks despite their bad initial coverage planning. The values in the
best networks are below 1.5%. Interference also raises the figure. If used
on the cell level, the values can be even over 100 per cent if a cell takes
handovers in but then drops them. Call re-establishments can markedly
improve the drop call ratio (for example, from 2.3 to 2.0 %). Since this is
an improvement from the MS users point of view, this figure suits better to
management reports. The biggest reason for having low figures usually is
in basic network planning. If coverage is not adequate this KPI cannot
show good values.
Segment related problems: There might be some problems with
tch_norm_size if used on BTS level and the BTS is part of the
multisegment.

dcr_8h TCH drop call %, after TCH assignment, without considering re-
establishments.
Use: This formula is developed to better match with the formulas of other vendors
(Ericsson and Motorola). It considers the impact of the call re-establishment.
Known problems: See dcr_8.
dcr_5b TCH dropped conversation ratio, re-est. considered. Use: On the area level.
Tells the ratio of calls dropped while A and B are talking, that is after conn_ack.
Inter-BSC handovers are subtracted in the denominator because they trigger
conver_started. Compensation is 100% true only if the area has no inter- BSC
HOs from outside the area. Theoretically should always be less than dcr_3 or
dcr_3a.
RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS
:
Known problems: See dcr_5.
1)
conver_started is not triggered for call re-establishments.
dropped_calls is triggered once for the first re-establishment. After that
setup_failure is triggered if the call is a dropped call.
If a call is ?saved? by re-establishment multiple times, setup_failure will be
triggered several times accordingly.
2)
Drop call by pre-emption (first priority call request to be established, all TCH
seized, lower priority calls on) triggers
dropped_calls. Therefore this counter does not indicate only technical drops.

dcr_10e Drops per erlang, before re-establishment. Use: On the area and BTS level.
dcr_10f Drops per erlang, after re-establishment. Use: On the area and BTS level.
dcr_4h TCH drop-out ratio, before call re-establishment. Use: On the BTS level. To rank
cells by the share of TCH drop call failures per TCH seizure (normal or HO). Intra-
cell HO is excluded, which is meaningful in the case of IUO. Inter-cell HOs are
counted only as a net value.
Known problems: Does not work 100% right if there are lot HO from 2G-3G or vice
versa. New version dcr_4i shall be used.
Figure1:Summary of SDCCH Formulas
Figure2:SDCCH Success Ratio (csf_2e)

SDCCH DROP counters

Root cause
RF reason Rf (%) call c1003 Drops due to Radio failure during call
RF reason Rf (%) old c1004 Drops due to Radio failure in HO
HW reason /RF reason A bis (%) call c1075 Drops due to 'Abis' failure during call (e.g. Ghos
HW reason /RF reason A bis (%) old c1076 Drops due to 'Abis' failure in HO
HW reason /RF reason Aif (%) call c1078 Drops due to 'Aif' failure during call
HW reason /RF reason Aif (%) old c1079 Drops due to 'Aif' failure in HO
HW reason Lapd (%) c1035 Drops due to Lapd problems
HW reason BTS (%) c1036 Drops due to BTS problems
user User (%) c1037 Drops due to user actions
reset BCSU (%) c1038 Drops due to BCSU reset
HW reason Cnfg act (%) c1039 Drops due to radio network configuration
Timer T3101 Expiry % c57020 Drops due to T3101 expiry
SDCCH requests c1000
HO in c1006
To FACCH call setup c1099
LU c3019
MTC (incl SMS) c3012
MOC (incl SMS,SS) c3013
supplementary servicec3044
IMSI detach (S7) c3033
call re-establishment c3020
emergency call c3021

SDCCH DROP KPIs

sdr_1a Drops total. Ratio of SDCCH drops / SDCCH bids.Use: To
follow up the performance of SDCCH from a technical point of
view.
Experiences on Use: 1) High SDCCH drop rates usually result
from ghost accesses. A BTS decodes them from environmental
or background noise and filters out most of them. However, all
of them cannot be filtered out and the RACH request is passed
on to the BSC for processing and for the allocation of a SDCCH
channel. The counter GHOST CCCH RES (3030) is updated
each time a CHANNEL REQUIRED is rejected because of an
invalid establishment cause. In GSM ph.1 there exist altogether
eight establishment causes, three of which are undefined as
invalid, for example, resulting in that this counter shows only 3/8
of all the ghost accesses the BTS has decoded. For the rest, a
SDCCH is allocated and this will result in
SDCCH_ABIS_FAIL_CALL failure. Because of ghost attempts
the SDCCH drop ratio is high with low traffic. As the amount of
call attempts increases, the influence of ghosts becomes
smaller and the drop ratio approaches its real value. 2) The rate
of ghosts coming to SDCCH dropped when BTS B9 with
improved ghost filtering was taken into use.
Known problems: In SDCCH failure counters it is not possible to
separate LU and call seizures.

trf_30 SDCCH bids. SDCCH assignments and SDCCH HO

seizures.

rach_6 SDCCH Ghosts.Ghost requests rejected by BSC due to

an illegal establishment cause.The real amount of ghosts
is about 8/3*counter3030 in GSM ph.1!
sdr_3b Ghost%.SDCCH ghost requests in ratio to SDCCH
bids.This PI gives you number of ghost accesses which
try to seize SDCCH but are rejected before seizing
SDCCH due to an illegal establishment cause.

csf_2e SDCCH success ratio, including LU.Use: Indicates how

well the SDCCH phase is completed.
Experiences on Use: The best values seen are around
98 %.
Known problems: The formula does not separate the
SDCCH call seizures from other seizures (such as LU
and SS). The failure rate in the case
of a call or e.g. LU can greatly differ from one another,
wherefore you cannot use this formula for SDCCH call
success ratio
calculation.
sdr_4 SDCCH drop ratio without timer T3101 expiry.Ratio of
dropped SDCCH without considering the drops caused
by timer T3101.
Use: See sdr_1a. .
Known Problems: See sdr_1a. RECOMMENDED
SUMMARY LEVELS: Area; SEG; BTS

ava_63 Share of SDCCH availability.Indicates how big a share of

all SDCCH resources has been available for traffic.
Failures (downtime) of TRX containing SDCCH affect this
KPI.
Note: This KPI has to be counted separately for extended
and normal area (trx_type: 0 = normal, 1 = extended).
Known problems: Affected by locked TRX under
unlocked BCF and BTS.

blck_15 Blocked SDCCH seizure attempts

sd_1b Ghosts detected on SDCCH and other failures.This part
of ghost RACH accesses comprises: - ghosts which have
an occasionally valid establishment cause. These should
comprise statistically 5/8 of all ghosts in GSM phase 1.
Another 3/8 of ghosts are detected already before
SDCCH based on some invalid establishment cause. In
GSM2 the ratio 5/8 and 3/8 is no longer valid. - multiple
seizures of SDCCH . :

trf_7b SDCCH usage ratio. Comparison has shown that this

formula works as well as trf_7. See test results Dynamic
SDCCH allocation can add SDCCH capacity dynamically
and therefore make the counting of SDCCH usage %
obsolete. .

csf_13b SDCCH call success probability.Ratio of calls

successfully transferred to TCH from SDCCH.
Use: On the area level. Indicates the probability of a call
being successfully transferred from SDCCH to TCH.
Segment related problems: tch_call_req is updated only
for master BTS.
csf_12 Activation related SDCCH access probability.Use: On the
area level.
ailure during call

ilure during call (e.g. Ghosts having a legal establishment cause)

ure during call

etwork configuration
Handover counters
TO ADJACENT CELL
HO => Att c15001 Number of HO attempts to the adjacent cell
HO <= Att c15003 Number of HO attempts to the adjacent cell
Number of handovers c1008 TCH seizures for HO

HO REASONS
Root Cause
Interference UL qua c4023 UL quality
Coverage UL lev c4024 UL level
Interference DL qua c4025 Downlink quality
Coverage DL lev c4026 Downlink level
Distance Dist high c4027 Distance exceeds limit
Traffic MSC c4028 MSC invocation (traffic reason)
Interference UL itf c4029 Uplink interference
Interference DL itf c4030 Downlink interference
Umbrella Umbr c4031 Umbrella
Better cell Pbgt c4032 Power Budget
O&M OMC c4033 Operation and maintenance (forced by user)
DR DR c4079 Directed retry
pre-mption PrEm c4086 Pre-emption (S3)
quality RFD c4087 Rapid field drop (S4)
Distance Dist low c4088 Low distance (S4)
Quality CI Bad c4089 Bad C
Quality CI Good c4090 Good C
Speed Slow Mov MS c4091 Slow moving MS (S5)
Speed MS spee slow c4105 Slow speed of MS (S6)
Speed MS spee high c4106 High speed of MS (S6)
A interface /HW CTC c4099 HO to change Aif circuit type (S5)
quality ERFD c4111 Enhanced Rapid field drop (S7)
Trafic TRHO c4035 BSC controlled TRHO (S8)
Traffic DADL c4129 DADLB (S8)
Data GPRS c4130 HO to enable GPRS territory upgrade (S9)
HSCSD HSCSD c4141 Intracell HO attempt for a single slot call for enablin
Interference Rx Bad c4109 Bad Rx level (S7)
Quality Rx Good c4110 Good Rx level
direct access Dir Acc c4128 Direct access attempts (S7)
Quality Inter band due lev c4163 TCH-TCH HO from non-BCCH due to weak downli
3G ISHO c4180 TCH-TCH HO from GSM to WCDMA RAN (S11)
3G Intersys dir acc c4181 SDCCH-TCH from GSM to WCDMA RAN due to di
HR AMR FR-HR c4142 HO attempts from AMR FR to AMR HR (S10)
HR AMR HR-FR c4143 HO attempts from aMR HR to AMR FR (S10)
Quality Inter band SDCCH c4133 Attempts to perform based on duration of an SDCC
Quality Inter band TCH c4135 Attempts to perform a TCH-TCH HO between BTS
SDCCH Inter BTS type SDCCH c4137 Attempts to perform SDCCH to SDCCH based on d
BTS type Inter BTS type TCH c4139 Attempts to perform TCH to TCH HO between diffe
Nbr of HO att ho_13h Number of HO attempts
 UNDEFINED ADJACENT CELLS
NCC c13003 Nework Colour Code of UAC.
BCC c13003 Base Sation Colour Code of UAC.
BCCH c13003 BCCH carrier number (ARFN) of UAC.
Nbr of samples c13002 Nbr of samples f stregth
Avg DL sig str c13001 Average DL signal strength received from UAC.

Outgoing MSC ctrl HO

Successes c4004
MSC ctrl ho not allowed c4037
Blocked c4055
Return to old c4006
End of HO c4007
End of HO BSS c4008
Call clear c4041
Wrong Aif circuit type c4102
Adjacent cell error c4100
Drop calls (S7) c4107

Outgoing BSC ctrl HO

Successes c4014
BSC ctrl ho not allowed c4038
Blocked c4072
Return to old c4015
End of HO c4016
End of HO BSS c4017
Call clear c4042
Wrong Aif circuit type c4096
Drop calls c4084

Intra cell HO
Intra cell ho not allowed c4036
Blocked c4019
Return to old c4022
MS lost (drop call) c4020
Radio chnactfailure c4021
Call clear c4039
Wrong Aif circuit type c4098
Drop calls c4085

HO KPIs on the Adjacency level

HO => Blck % blck_19 Handover blocking to target cell.Note: High values shown if the target
blocked by user.
This is because the cell can still be a candidate. As far as MSs can lis
BCCH TRX and reports it, the BSC tries handover to this cell. If all tim
blocked it will fail due to no resourcies available, all ready before ho c
So it's not a real ho fail.

NOTES:
Known problems: In S11.5 or older releses the counters HO_ATT_TO
HO_FAIL_RES_TO_ADJ are updated before pool switching that can
AMR is in use and there are non-AMR cells in the network (or AMR c
resources run out of capacity). HO_ATT_TO_ADJ is updated once ag
pool switching. This lead the situation that KPI shows some blocking
are no blocking at all in network (HO_FAIL_RES_TO_ADJ is updated
pool switching). Since S12 in pool change the counters HO_ATT_TO
updated only once, and HO_FAIL_RES_TO_ADJ is not updated if the
real blocking.

HO => Fail % hfr_58 HO failures to target cell.Use: On the adjacency level. Gives th
% of the real (non blocked) HO attempts.
NOTES:
Known problems: Not accurate because
1) for calls that are cleared by MS user during the HO process
ho_att_to_adj counter is incremented and cannot be
compensated in the numerator.
2) HO that is interrupted due to another procedure (e.g. assign
increments attempt counters but cannot be compensated
in the numerator.
3)In S11.5 or older releses the counters HO_ATT_TO_ADJ an
HO_FAIL_RES_TO_ADJ are updated before pool switching th
occur when AMR is in use and there are non-AMR cells in the
(or AMR circuit resources run out of capacity). HO_ATT_TO_A
updated once again alter pool switching, and HO_SUCC_TO_
updated after successful HO. Since S12 in pool change the co
HO_ATT_TO_ADJ (and HO_SUCC_TO_ADJ) are updated on
HO <= Fail % hfr_59 HO failures from target cell.On the adjacency level. Gives the
of the real (non blocked) HO attempts.
NOTES:
Known problems: Not accurate because
1) for calls that are cleared by MS user during the HO process
ho_att_from_adj-counter is incremented and cannot be
compensated in the numerator.
2) HO that is interrupted due to another procedure (e.g. assign
increments attempt counters but cannot be compensated
in the numerator.
3)In S11.5 or older releses the counters HO_ATT_FROM_ADJ
HO_FAIL_RES_FROM_ADJ are updated before pool switchin
occur when AMR is in use and there are non-AMR cells in the
(or AMR circuit resources run out of capacity). HO_ATT_FROM
updated once again alter pool switching, and HO_SUCC_FRO
updated after successful HO. Since S12 in pool change the co
HO_ATT_FROM_ADJ (and HO_SUCC_FROM_ADJ) are upda
once.

General HO KPIs
HO <= Blck % blck_20 Handover blocking from target cell.High values shown if the ta
blocked by user.
This is because the cell can still be a candidate. As far as MSs
listen to BCCH TRX and reports it, the BSC tries handover to t
all time slot are blocked it will fail due to no resourcies availabl
ready before ho command. So it's not a real ho fail.

NOTES:
Known problems: In S11.5 or older releses the counters
HO_ATT_FROM_ADJ and HO_FAIL_RES_FROM_ADJ are u
before pool switching that can occur when AMR is in use and t
non-AMR cells in the network (or AMR circuit resources run ou
capacity). HO_ATT_FROM_ADJ is updated once again alter p
switching. This lead the situation that KPI shows some blockin
there are no blocking at all in network (HO_FAIL_RES_FROM
updated before pool switching). Since S12 in pool change the
HO_ATT_FROM_ADJ is updated only once, and
HO_FAIL_RES_FROM_ADJ is not updated if there are no rea
HO calls ratio% trf_13g HO / call ratio.Indicates how stationary of mobile the traffic is.
bigger the number, the more mobile is the traffic. Using this KP
with stationary traffic can be found. This is largely dependent o
much the coverage areas overlap. Usable for non-IUO network
cell HOs are not included as they are not directly related to mo
RECOMMENDED SUMMARY LEVELS: Area; SEG

HO drop ratio hfr_68b HO drop ratio.Defines how big a share of the started handover
dropped. Indicates the quality of the handovers.
Segment related problems: Does not work on BTS level if the
part of the multisegment. A reason for this is that an attempt co
triggers for
a target BTS only if a HO is successful. In the case of a hando
failure, the attempt counter triggers only for the master
BTS. RECOMMENDED SUMMARY LEVELS: Area; SEG
Total HO failure hfr_2a Total HO failure ratio, excluding ISHO.On the area or network
However, this formula does not work on BTS level if BTS is pa
with several BTS and there are HOs from other cells. The reas
the incoming HO from another cell triggers the incoming HO a
counter in the master BTS but the HO success counter can be
in another BTS. This is the case only if the HO is unsuccessfu
Experiences on Use: In a network gave the result of 8 % instea
of hfr_1. In a good network the value can be less than 3 per ce
in a very bad network values higher than 15 per cent may occu
Directed Retry is enabled, the MS may, when congestion of th
cell SDCCH occurs, be moved from the best cell to a worse on
the MS tries to make a handover back but fails if the first cell is
congested. This leads to incrementation of the HO failure ratio
Common reasons for a handover to fail:
- incorrect parameter settings of adjacencies
- badly defined neighbours (UL coverage becomes a problem)
- UL coverage generally. Cell imbalanced.
- TCH blocking in the target cell
- UL interference (target BTS never gets the HO access)

Known problems: Blocking is included. Blocking makes this ind

show high values especially in the case of IUO, but it does not
necessarily mean that there are some technical problems.
ISHO not included. Use hfr_2b instead.

RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS

HO failure due to blocking hfr_55b HO failure ratio due to radio interface blocking.On the area lev
Segment related problems: Does not work on BTS level if the
part of the multisegment. A reason for this is that an attempt co
triggers for
a target BTS only if a HO is successful. In the case of a hando
failure, the attempt counter triggers only for the master
BTS.
RECOMMENDED SUMMARY LEVELS: Area; SEG
Outgoing MSC ctrl HO attempts ho_9a Segment related problems: Does not work on BTS level if the
part of a multisegment. The reason is that a HO attempt count
triggered for
a master BTS (BCCH BTS) first. If the HO is successful then th
counter is updated for the BTS in question. The
problem occurs if the HO is unsuccessful. In that case, the atte
counter remains in master BTS and would not be updated for t
that caused the HO failure.

Failures hof_6b MSC outgoing HO failures.Segment related problems: Does n

BTS level if the BTS is part of the multisegment. A reason for t
an attempt counter triggers for
a target BTS only if a HO is successful. In the case of a hando
failure, the attempt counter triggers only for the master
BTS.

Outgoing BSC ctrl HO attempts ho_11 BSC outgoing HO attempts.Segment related problems: Does n
on BTS level if the BTS is part of a multisegment. The reason
HO attempt counter is triggered for
a master BTS (BCCH BTS) first. If the HO is successful then th
counter is updated for the BTS in question. The
problem occurs if the HO is unsuccessful. In that case, the atte
counter remains in master BTS and would not be updated
for the BTS that caused the HO failure.

BSC HO Failure hof_8b BSC outgoing HO failures.Segment related problems: Does no

BTS level if the BTS is part of the multisegment. A reason for t
an attempt counter triggers for
a target BTS only if a HO is successful. In the case of a hando
failure, the attempt counter triggers only for the master
BTS.
Intra cell HO attempts ho_24 Intra-cell HO attempts.Segment related problems: Does not wo
BTS level if the BTS is part of a multisegment. The reason is th
attempt counter is triggered for
a master BTS (BCCH BTS) first. If the HO is successful then th
counter is updated for the BTS in question. The
problem occurs if the HO is unsuccessful. In that case, the atte
counter remains in master BTS and would not be updated
for the BTS that caused the HO failure.

Successes ho_27a Intra-cell HO successes

Intra HO Failure hof_9c Segment related problems: Does not work on BTS level if the
part of the multisegment. A reason for this is that an attempt co
triggers for
a target BTS only if a HO is successful. In the case of a hando
failure, the attempt counter triggers only for the master
BTS.
 the adjacent cell
the adjacent cell

n (traffic reason)

maintenance (forced by user)

Aif circuit type (S5)

d field drop (S7)

GPRS territory upgrade (S9)

empt for a single slot call for enabling HSCSD call

ttempts (S7)
rom non-BCCH due to weak downlink (S10.05)
rom GSM to WCDMA RAN (S11)
om GSM to WCDMA RAN due to direct access (S11)
om AMR FR to AMR HR (S10)
om aMR HR to AMR FR (S10)
form based on duration of an SDCCH reservation
form a TCH-TCH HO between BTS on different quality
form SDCCH to SDCCH based on duration of CCH
form TCH to TCH HO between different BTS type
 Code of UAC.
olour Code of UAC.
umber (ARFN) of UAC.

nal strength received from UAC.

ell.Note: High values shown if the target cell is

till be a candidate. As far as MSs can listen to

BSC tries handover to this cell. If all time slot are
sourcies available, all ready before ho command.

older releses the counters HO_ATT_TO_ADJ and

updated before pool switching that can occur when
non-AMR cells in the network (or AMR circuit
. HO_ATT_TO_ADJ is updated once again alter
situation that KPI shows some blocking even there
rk (HO_FAIL_RES_TO_ADJ is updated before
pool change the counters HO_ATT_TO_ADJ is
FAIL_RES_TO_ADJ is not updated if there are no

se: On the adjacency level. Gives the failure

) HO attempts.

urate because
by MS user during the HO process the
cremented and cannot be
ator.
ue to another procedure (e.g. assignment)
rs but cannot be compensated

the counters HO_ATT_TO_ADJ and

are updated before pool switching that can
and there are non-AMR cells in the network
run out of capacity). HO_ATT_TO_ADJ is
pool switching, and HO_SUCC_TO_ADJ is
O. Since S12 in pool change the counters
O_SUCC_TO_ADJ) are updated only once.
 l.On the adjacency level. Gives the failure %
O attempts.

urate because
by MS user during the HO process the
s incremented and cannot be
ator.
ue to another procedure (e.g. assignment)
rs but cannot be compensated

the counters HO_ATT_FROM_ADJ and

DJ are updated before pool switching that can
and there are non-AMR cells in the network
run out of capacity). HO_ATT_FROM_ADJ is
pool switching, and HO_SUCC_FROM_ADJ is
O. Since S12 in pool change the counters
d HO_SUCC_FROM_ADJ) are updated only

rget cell.High values shown if the target cell is

n still be a candidate. As far as MSs can

eports it, the BSC tries handover to this cell. If
will fail due to no resourcies available, all
. So it's not a real ho fail.

or older releses the counters

HO_FAIL_RES_FROM_ADJ are updated
can occur when AMR is in use and there are
ork (or AMR circuit resources run out of
M_ADJ is updated once again alter pool
uation that KPI shows some blocking even
in network (HO_FAIL_RES_FROM_ADJ is
hing). Since S12 in pool change the counters
pdated only once, and
DJ is not updated if there are no real blocking.
 w stationary of mobile the traffic is. The
re mobile is the traffic. Using this KPI, cells
e found. This is largely dependent on how
overlap. Usable for non-IUO network. Intra-
as they are not directly related to mobility.
ARY LEVELS: Area; SEG

big a share of the started handovers is

ality of the handovers.
: Does not work on BTS level if the BTS is
A reason for this is that an attempt counter

s successful. In the case of a handover

r triggers only for the master
UMMARY LEVELS: Area; SEG
 uding ISHO.On the area or network level.
s not work on BTS level if BTS is part of SEG
e are HOs from other cells. The reason is that
ther cell triggers the incoming HO attempt
but the HO success counter can be triggered
case only if the HO is unsuccessful.
network gave the result of 8 % instead of 7 %
k the value can be less than 3 per cent, while
es higher than 15 per cent may occur. - If
the MS may, when congestion of the source
oved from the best cell to a worse one. Then
ndover back but fails if the first cell is still
ncrementation of the HO failure ratio.
ndover to fail:
ngs of adjacencies
(UL coverage becomes a problem)
Cell imbalanced.
et cell
TS never gets the HO access)

is included. Blocking makes this indicator

y in the case of IUO, but it does not
e are some technical problems.
r_2b instead.

ARY LEVELS: Area; SEG; BTS

o interface blocking.On the area level.

: Does not work on BTS level if the BTS is
A reason for this is that an attempt counter

s successful. In the case of a handover

r triggers only for the master

ARY LEVELS: Area; SEG

: Does not work on BTS level if the BTS is
e reason is that a HO attempt counter is

) first. If the HO is successful then the attempt

BTS in question. The
s unsuccessful. In that case, the attempt
BTS and would not be updated for the BTS
.

.Segment related problems: Does not work on

t of the multisegment. A reason for this is that
s for
s successful. In the case of a handover
r triggers only for the master

s.Segment related problems: Does not work

part of a multisegment. The reason is that a
gered for
) first. If the HO is successful then the attempt
BTS in question. The
s unsuccessful. In that case, the attempt
BTS and would not be updated
e HO failure.

Segment related problems: Does not work on

t of the multisegment. A reason for this is that
s for
s successful. In the case of a handover
r triggers only for the master
ment related problems: Does not work on
t of a multisegment. The reason is that a HO
d for
) first. If the HO is successful then the attempt
BTS in question. The
s unsuccessful. In that case, the attempt
BTS and would not be updated
e HO failure.

: Does not work on BTS level if the BTS is

A reason for this is that an attempt counter

s successful. In the case of a handover

r triggers only for the master
Figure 1:RX Quality and RX Level
Figure 2:RX Quality and RX Level: Checks
Figure 3:RX Statistics measurements

Here are some examples how different kind

Like Normal distribution

Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 10645 8516 6813 5450 4360 3488 2791 2232
CL15 47043 37634 30108 24086 9865 7543 5643 2345
CL20 56204 44963 35971 28776 6574 10324 345 65
CL30 200863 160690 128552 102842 17654 9876 145 28
CL40 12785 10228 8182 6546 456 112 24 23
CL63 4583 1123 583 452 261 76 26 2

HW problem, Q4 amount of samples is strange

Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 5323 4258 3406 2725 2180 1744 1395 1116
CL15 23522 18817 15054 12043 18765 3772 2822 1173
CL20 28102 22482 17985 14388 36542 5162 173 33
CL30 67544 54035 43228 34582 150073 4938 73 14
CL40 6393 5114 4091 3273 9876 56 12 12
CL63 2292 562 292 226 6756 38 13 1

HW Problem, TRX/combiner etc is broken

Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 200863 160690 128552 102842 17654 9876 7865 6543
CL15 16543 13234 10588 8470 6776 2822 1173 234
CL20 2654 2123 1699 1359 1087 173 33 65
CL30 4543 3634 2908 2326 1861 73 14 28
CL40 5114 4091 3273 2618 2095 12 12 23
CL63 24 54 8 87 7 0 0 0

Figure 4:Problem examples

Quality counters
Rf call c1013 Radio failures
CL c53002 CLASS_UPPER_RANGE
Quality c53007 FREQ_UL_QUAL0
…
Quality c53049 FREQ_UL_QUAL7
Quality c53055 FREQ_DL_QUAL0
…
Quality c53097 FREQ_DL_QUAL7

See figure4, problems examples

Quality KPIs

% in q0..7 dlq_2a Downlink, cumulative share of measurement samples in quality classes 0 to 7.This
DL PI gives a cumulative percentage of call samples (AMR, non-AMR) in classes 0 to
X. X = 5 is normally used as a quality indicator. If X = 5 and this figure is 100 %,
then the MS users obviously have not perceived any quality problems.
RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS Known problems: If DL
DTX is used, there is a shift to a worse quality %, but a MS does not perceive this.

% in q0..7 ulq_2a Uplink, cumulative share of measurement samples in quality classes 0 to 7. This PI
UL gives the cumulative percentage of call samples in classes 0 to X. X = 5 is normally
used as a quality indicator. If X = 5 and this figure is 100 %, the MS users obviously
have not perceived any quality problems.
RECOMMENDED SUMMARY LEVELS: Area; SEG; BTS
Call time trf_32b Call time counted as a sum over the whole period. Known problems: In a high load
situation it is possible that not all call time is measured. In other words, call time can
show a lower value than it
has in reality.
s how different kind of problems can be found

HW Problem, TRX/combiner etc is broken

Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 5323 4258 3406 2725 2180 1744 4563 9765
CL15 11761 9409 7527 6022 9383 1886 65432 7675
CL20 14051 11241 8993 7194 18271 2581 65438 63562
CL30 33772 27017 21614 17291 75037 2469 18765 14523
CL40 3196 2557 2046 1636 4938 28 3659 2648
CL63 1146 281 146 113 3378 19 100 174

Interference problem
Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 5323 4258 3406 2725 2180 1744 1395 1116
CL15 23522 13234 10588 8470 13234 10588 8470 6776
CL20 28102 2123 1699 1359 2123 1699 1359 1087
CL30 67544 3634 2908 2326 3634 2908 2326 1861
CL40 6393 4091 3273 2618 4091 3273 2618 4532
CL63 9987 7543 4323 3454 2275 1187 876 654