Professional Documents
Culture Documents
KPI Analysis 2G
KPI Analysis 2G
Receipt of a valid CHANNEL REQUIRED (BTS --> BSC) (immediate assignment procedure, SDCCH assignment request
only)
Receipt of a valid ASSIGNMENT REQUEST (MSC --> BSC) (assignment procedure, SDCCH assignment request only)
Receipt of an INTERCELL HANDOVER CONDITION INDICATION (BTS --> BSC) during the SDCCH phase (SDCCHSDCCH handover, intra-BSC)
Receipt of a HANDOVER REQUEST (MSC --> BSC) containing the channel type SDCCH (incoming SDCCH-SDCCH
handover, Inter-BSC)
Dimensioning
Tolerable Values: 0.1 to 0.5 %
Max SDCCHs per TRX: 2 in Nokia & 4 in Siemens
Dynamic Channel Configuration
TCH Call Request is number of TCH requests for a normal assignment (both successful and
unsuccessful). Its updated When the RRM receives a TCH request in a call attempt
TCH Norm Seiz is number of successful TCH requests for a normal assignment. Its updated when the
Radio Resource Manager allocates a TCH as a response to a TCH request in a call attempt
Compensation Factor
msc_o_sdcch_tch: MSC Controlled Successful Outgoing Directed Retries
. bsc_o_sdcch_tch: BSC Controlled Successful Outgoing Directed Retries
cell_sdcch_tch: Internal Directed Retries when Super Reuse TRX/Intelligent Underlay Overlay feature is deployed
bsc_i_unsucc_a_int_circ_type:
Counter is incremented when the internal inter-cell handover attempt has been interrupted because
BSC wishes to change the A-interface circuit pool before TCH allocation
ho_unsucc_a_int_circ_type:
Counter is incremented when the internal intra-cell handover attempt has been interrupted because
BSC wishes to change the A-interface circuit pool before TCH allocation
msc_controlled_in_ho:
Counter is incremented when the handover attempt has been failed due to unsuccessful TCH allocation
attempt because of the mismatch between the requested TCH channel type and A-interface circuit type.
The cause Switch circuit pool will be sent in the HANDOVER FAILURE message to
the A-interface
Dimensioning
Tolerable value: 2%
Half Rate (Trade Off between Quality & Capacity)
Traffic Balancing between 900 & 1800 layers
An intra-cell handover occurs when an MS is transferred from one channel to another within a cell. This
usually includes Full Rate-Half Rate & Half Rate-Full Rate Handovers.
BSC Controlled Handover:
This type of handover involves an MS being transferred from one cell to another, when both cells are being
controlled by the same BSC. This type of handover is generally controlled by the BSC. This can be both
incoming & outgoing
MSC Controlled Handover:
This type of handover involves an MS being transferred from one cell to another, when the target cell is
controlled by a different BSC to that of the source cell. This type of handover is always controlled by the
MSC. This can be both incoming & outgoing
HOSR =
HOSR =
Successful HOs
---------------------------HO Attempts
MSC Controlled Successful HOs + BSC Controlled Successful HOs + Intra Cell
Successful HOs
------------------------------------------------------------------------------------MSC Controlled HO Attempts+ BSC Controlled HO attempts + Intra Cell HO Attempts
ImmAssSuccRate
ImmAssAGCHSuccRate
ImmAssSeizRate
AssSuccRate
SDCCHSuccRate
SUIMASCA
ATIMASCA
3.
4.
Phantom RACHs: These are channel required messages not foreseen for the
observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH
is then started, but will not be successful, because no MS will reply with a SABM
message and therefore a BTS Timer will expire. These unforeseen messages will
also be counted.
The RACH attempt for Immediate Assignment has to be evaluated by the procedures as below:
RSSI
SOVA( BSS Soft Decision Criterion )
SNR
Convolution Code
Training sequence
Additional criteria to discard Phantom RACH
CRC check
Received signal level
( Discard the RACH that the signal level < RACHBT)
MS - BTS distance check
Increase the RACHBT will cause more weak RACH to be discarded. This will cause
the increase of NINVRACH sub counter 1.
Im mAssAGCHSuccRate
NACSUCPR _ AGCH
TACCBPRO _ AGCH
Im mAssSeizRate
NSUCCHPC
SDCCHSetupSuccRate 1
NRFLSDCC
NSUCCHPC{ APSD CRSD ECSD LUSD OCSD OPSD}
Note:
Calls that are dropped during Handover on the old (source) channel are also pegged
as dropped calls in source cell
This formula includes the drops that occur between ASSIGNMENT_COMPLETE and
DISCONNECT commands
We are not using the Re-Assignments feature in our network.
TCH Drop Call Rate basically represents any call which is dropped possibly due to any failure. The main
reasons for these failures can be
Radio Failures
Abis Failures
Transcoder Failures
A-Interface Failures
Radio Failures
ass_fail_msg_c
conn_fail_c
conn_fail_rad_inf_fail_c
CONNECTION FAILURE message is received from the MS and its cause is radio interface failure .
conn_fail_rad_link_fail_c
err_ind_c
ass_fail_c
error_report_c
timing_advance_c
Distance between the MS and the BTS has reached the maximum value allowed
ms_is_lost_c
source_fail_c
Main
ABIS Failure:
Number of TCH transaction failures due to an Abis interface failure during normal call &
during Handover on old channel
The failure reasons may include missing acknowledgement of channel activation, missing
indication of call establishment, receipt of an error indication, corrupted messages,
missing measurement results from the BTS, excessive timing advance or some internal
reasons. The fluctuations of Abis links (between BSC & BTS) can also be the main
reason for these failures.
Transcoder Failure:
Number of radio TCH transactions ended due to a transcoder failure during normal call &
during Handover on old channel. This counter is updated when
conn_fail_rem_trans_fail_c is updated which is when CONNECTION FAILURE
message is received and its cause is remote transcoder failure. The main reason for
these drops can be the fluctuation of Aters (Between BSC & Transcoder).
A-Interface Failure:
Number of TCH transaction failures due to an A interface failure normal call & during
Handover on old channel. The main reason for these failures are related to MSC which
may include SCCP connection establishment failure, erroneous & invalid BSSMAP
messages, unsupported speech coder version & TCH type, fault in the 2-Mbit PCM
connection etc.
BTS Failures (When a TCH transaction ends because of a TRX blocked by a BTS)
BCSU resets (When a TCH transaction ends because of a TRX blocked by a BCSU restart)
LAPD Failures (When a TCH transaction ends because of a TRX blocked by an LAPD failure
Failure due to user Actions (When the user disconnects a busy TCH by blocking the TSL/TRX
with an MML command)