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 reason
HW problems
HW problems
RF/HW reason
RF/HW reason
RF/HW reason
RF/HW reason
HW problems
HW problems
user
reset
HW problems
RF reason
RF/HW reason
RF/HW reason
timer
timer
timer

Rf call
c1013
Rf old
c1014
Tc fail
c1029
Tc old
c1030
Abis call c1084
Abis old c1085
Aif call
c1087
Aif old
c1088
Lapd
c1046
BTS
c1047
Usr
c1048
BCSU
c1049
Cfg
c1050
Act
c1081
BSC i HO c4084
BSC o HO c4085
T3101 Expired (S9)
T9103 Expires
T3107 Expired

TCH DROP KPIs

Radio failures
Radio failures on old channel in HO
Transcoder failures
Transcoder failures of old channel in HO
Abis failures
Abis failures on old channel in HO
A if failures
A if failures on old channel in HO
Lapd failures
BTS failures
Failures due to user actions
Failures due to BCSU reset
Failures due to radio network configuration action
Failures due to channel activation nack
Drop calls in BSC controlled incoming HOs
Drop calls in BSC controlled outgoing HOs

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 timeconsuming 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 reestablishments.

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). Intracell 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 reason
HW reason /RF reason
HW reason /RF reason
HW reason /RF reason
HW reason /RF reason
HW reason
HW reason
user
reset
HW reason
Timer

SDCCH DROP KPIs

Rf (%) call
c1003
Drops due to Radio failure during call
Rf (%) old
c1004
Drops due to Radio failure in HO
A bis (%) call
c1075
Drops due to 'Abis' failure during call (e.g. Ghos
A bis (%) old
c1076
Drops due to 'Abis' failure in HO
Aif (%) call
c1078
Drops due to 'Aif' failure during call
Aif (%) old
c1079
Drops due to 'Aif' failure in HO
Lapd (%)
c1035
Drops due to Lapd problems
BTS (%)
c1036
Drops due to BTS problems
User (%)
c1037
Drops due to user actions
BCSU (%)
c1038
Drops due to BCSU reset
Cnfg act (%)
c1039
Drops due to radio network configuration
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 service c3044
IMSI detach (S7)
c3033
call re-establishment
c3020
emergency call
c3021

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
HO <= Att
Number of handovers

HO REASONS
Root Cause
Interference
Coverage
Interference
Coverage
Distance
Traffic
Interference
Interference
Umbrella
Better cell
O&M
DR
pre-mption
quality
Distance
Quality
Quality
Speed
Speed
Speed
A interface /HW
quality
Trafic
Traffic
Data
HSCSD
Interference
Quality
direct access
Quality
3G
3G
HR
HR
Quality
Quality
SDCCH
BTS type

c15001
c15003
c1008

Number of HO attempts to the adjacent cell

Number of HO attempts to the adjacent cell
TCH seizures for HO

UL qua
UL lev
DL qua
DL lev
Dist high
MSC
UL itf
DL itf
Umbr
Pbgt
OMC
DR
PrEm
RFD
Dist low
CI Bad
CI Good
Slow Mov MS
MS spee slow
MS spee high
CTC
ERFD
TRHO
DADL
GPRS
HSCSD
Rx Bad
Rx Good
Dir Acc
Inter band due lev
ISHO
Intersys dir acc
AMR FR-HR
AMR HR-FR
Inter band SDCCH
Inter band TCH
Inter BTS type SDCCH
Inter BTS type TCH
Nbr of HO att

c4023
c4024
c4025
c4026
c4027
c4028
c4029
c4030
c4031
c4032
c4033
c4079
c4086
c4087
c4088
c4089
c4090
c4091
c4105
c4106
c4099
c4111
c4035
c4129
c4130
c4141
c4109
c4110
c4128
c4163
c4180
c4181
c4142
c4143
c4133
c4135
c4137
c4139
ho_13h

UL quality
UL level
Downlink quality
Downlink level
Distance exceeds limit
MSC invocation (traffic reason)
Uplink interference
Downlink interference
Umbrella
Power Budget
Operation and maintenance (forced by user)
Directed retry
Pre-emption (S3)
Rapid field drop (S4)
Low distance (S4)
Bad C
Good C
Slow moving MS (S5)
Slow speed of MS (S6)
High speed of MS (S6)
HO to change Aif circuit type (S5)
Enhanced Rapid field drop (S7)
BSC controlled TRHO (S8)
DADLB (S8)
HO to enable GPRS territory upgrade (S9)
Intracell HO attempt for a single slot call for enablin
Bad Rx level (S7)
Good Rx level
Direct access attempts (S7)
TCH-TCH HO from non-BCCH due to weak downli
TCH-TCH HO from GSM to WCDMA RAN (S11)
SDCCH-TCH from GSM to WCDMA RAN due to d
HO attempts from AMR FR to AMR HR (S10)
HO attempts from aMR HR to AMR FR (S10)
Attempts to perform based on duration of an SDCC
Attempts to perform a TCH-TCH HO between BTS
Attempts to perform SDCCH to SDCCH based on d
Attempts to perform TCH to TCH HO between diffe
Number of HO attempts

UNDEFINED ADJACENT CELLS

NCC
c13003
BCC
c13003
BCCH
c13003
Nbr of samples
c13002
Avg DL sig str
c13001

Outgoing MSC ctrl HO

Successes
MSC ctrl ho not allowed
Blocked
Return to old
End of HO
End of HO BSS
Call clear
Wrong Aif circuit type
Adjacent cell error
Drop calls (S7)

c4004
c4037
c4055
c4006
c4007
c4008
c4041
c4102
c4100
c4107

Outgoing BSC ctrl HO

Successes
BSC ctrl ho not allowed
Blocked
Return to old
End of HO
End of HO BSS
Call clear
Wrong Aif circuit type
Drop calls

c4014
c4038
c4072
c4015
c4016
c4017
c4042
c4096
c4084

Intra cell HO
Intra cell ho not allowed
Blocked
Return to old
MS lost (drop call)
Radio chnactfailure
Call clear
Wrong Aif circuit type
Drop calls

c4036
c4019
c4022
c4020
c4021
c4039
c4098
c4085

HO KPIs on the Adjacency level

Nework Colour Code of UAC.

Base Sation Colour Code of UAC.
BCCH carrier number (ARFN) of UAC.
Nbr of samples f stregth
Average DL signal strength received from UAC.

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 ci
resources run out of capacity). HO_ATT_TO_ADJ is updated once ag
pool switching. This lead the situation that KPI shows some blocking e
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.

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.

General HO KPIs
HO <= Blck %

NOTES:
Known problems: In S11.5 or older releses the counters
HO_ATT_FROM_ADJ and HO_FAIL_RES_FROM_ADJ are up
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 the
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

Failures

Outgoing BSC ctrl HO attempts

BSC HO Failure

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
that caused the HO failure.

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.

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.

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
on-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
un out of capacity). HO_ATT_TO_ADJ is
ool 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
un out of capacity). HO_ATT_FROM_ADJ is
ool 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. Intraas they are not directly related to mobility.
ARY LEVELS: Area; SEG

big a share of the started handovers is

lity 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
ved 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)
ell imbalanced.
t 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

CL10
CL15
CL20
CL30
CL40
CL63

Q0
10645
47043
56204
200863
12785
4583

CL10
CL15
CL20
CL30
CL40
CL63

Q0
5323
23522
28102
67544
6393
2292

CL10
CL15
CL20
CL30
CL40
CL63

Q0
200863
16543
2654
4543
5114
24

Like Normal distribution

Q1
8516
37634
44963
160690
10228
1123

Q2
6813
30108
35971
128552
8182
583

Q1
4258
18817
22482
54035
5114
562

Q2
3406
15054
17985
43228
4091
292

Q5
3488
7543
10324
9876
112
76

Q3
2725
12043
14388
34582
3273
226

Q4
2180
18765
36542
150073
9876
6756

Q5
1744
3772
5162
4938
56
38

HW Problem, TRX/combiner etc is broken

Q1
160690
13234
2123
3634
4091
54

Q2
128552
10588
1699
2908
3273
8

Quality counters
c1013
c53002

Q4
4360
9865
6574
17654
456
261

Q6
2791
5643
345
145
24
26

HW problem, Q4 amount of samples is strange

Figure 4:Problem examples

Rf call
CL

Q3
5450
24086
28776
102842
6546
452

Radio failures
CLASS_UPPER_RANGE

Q3
102842
8470
1359
2326
2618
87

Q4
17654
6776
1087
1861
2095
7

Q5
9876
2822
173
73
12
0

Q7
2232
2345
65
28
23
2

Q6
1395
2822
173
73
12
13

Q7
1116
1173
33
14
12
1

Q6
7865
1173
33
14
12
0

Q7
6543
234
65
28
23
0

Quality
Quality
Quality
Quality

c53007

c53049
c53055

c53097

FREQ_UL_QUAL0
FREQ_UL_QUAL7
FREQ_DL_QUAL0
FREQ_DL_QUAL7

See figure4, problems examples

Quality KPIs
% in q0..7 dlq_2a
DL

Downlink, cumulative share of measurement samples in quality classes 0 to 7.This

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
UL

Uplink, cumulative share of measurement samples in quality classes 0 to 7. This PI

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

CL10
CL15
CL20
CL30
CL40
CL63

Q0
5323
11761
14051
33772
3196
1146

CL10
CL15
CL20
CL30
CL40
CL63

Q0
5323
23522
28102
67544
6393
9987

HW Problem, TRX/combiner etc is broken

Q1
4258
9409
11241
27017
2557
281

Q2
3406
7527
8993
21614
2046
146

Q3
2725
6022
7194
17291
1636
113

Interference problem
Q1
4258
13234
2123
3634
4091
7543

Q2
3406
10588
1699
2908
3273
4323

Q3
2725
8470
1359
2326
2618
3454

Q4
2180
9383
18271
75037
4938
3378

Q5
1744
1886
2581
2469
28
19

Q6
4563
65432
65438
18765
3659
100

Q7
9765
7675
63562
14523
2648
174

Q4
2180
13234
2123
3634
4091
2275

Q5
1744
10588
1699
2908
3273
1187

Q6
1395
8470
1359
2326
2618
876

Q7
1116
6776
1087
1861
4532
654