Sei sulla pagina 1di 2

This is summarizing of recognization and analyze on our KPI Problem:

>1: SDCCH Sucess Rate


@Root Possibilities :
�� Interference on BCCH frequency� SDCCH Blocking� SD Drop on Location Update�
A_If, TRC or LAPD Fail� HW faulty� Excessive TA
@Data Collection :
�� ND Report 72 to check BCCH clearance� Alarm Log� TA distribution ND Report
232� Quality and Link Balance ND Report 195 and 196.� Interference UL and ND 196
@Analysis :
1. Check possibility Co. or Adj. Interference and clear the BCCH
frequency.
2. Check SDCCH utilization and add SDCCH if needed.
3. Change TRP or change SDCCH allocation on TRX with good quality based on ND 196.
4. Check TRX alarm (mostly 7745 together with7743 or 7746). Check TRX
configuration.
5. Check TA distribution, coverage distribution and propose physical tune.
6. Optimizing parameter C2 also if Location update is the highest contributor of SD
Drop.
7. Highest contributor: Fail on RADIO, ABIS, A_IF, TR or LAPD.
8. Check TRX alarm (mostly 7745 alone or together with 7743)
9. Check RX Lev Access Min and Max Number of Retransmission. Check RACH Rejected
and SDCCH request

>2: HOSR
@Root Possibilities :
�� Co or Adjacent BCCH� High TCH Blocking on target cell� Wrong TSC setting
regarding BSIC allocation� Bad Neighbor Relation� HW faulty or Unbalance TRX
power among a sector� Others (Inter BSC-Inter MSC)
@Preparation Data :
� BCCH, BSIC planning, ND report 072� Cell Stat or TQM of HO distribution and ND
report 153� Alarm (ZEOH & ZEOL) and site visit� Timing Advance 232� Adjacent
Consistency Check ND060, 62 or 69� ND Report 73 to check Undefined Neighbor.
@Analysis:
1. Check possibility Co. or Adj. Interference then change BCCH frequency.
2. Check neighbor traffic & TCH blocking, check possibility for traffic sharing or
directed retry.
3. TSC
value should be same with BCC, check performance HO out and incoming.
4. Parameter setting ADCE to make delay on
worst target cell or faster HO on best target, focused on High HO Fail. Relate
parameter FMT or AUCL.
5. Check TRX alarm (mostly 7745 together with 7743 or 7746). Check TRX
configuration.
6. Optimize coverage from TA distribution or update missing Neighbor from ND 73.
7. Check the highest
handover cause: by interference, quality, level, power budget, GPRS, etc. Check for
the highest HO failure: by Blocked, Conn. Fail., Return to Old, End of HO,etc. The
highest value is possible as the highest contribution of HO fail.

>3: TCH Drop


@Root Possibilities :
- Interference on BCCH TRX- Interference on hopping TRX(DL Interference)- External
Interference (UL interference)- Bad Neighbor Relation (bad HO)- Low Coverage- HW
Faulty or TRX Power Unbalance- Other : A_If, TR or LAPD.
@Preparation Data :
- BCCH Planning, ND report 072 (DL Interference distribution)- ND Report 216, 196
and Alarm (Interference)- ND Report 204, 153, 195 ( HO fail and Path Balance)- ND
Report 232 ( Coverage cell)- ND Report 163 or TQM drop per causes KPI @Analysis:
1. Check possibility Co. or Adj. Interference. Check clean BCCH frequency.
2. Check DL quality Distribution and Check MAL and MAIO
3. Check UL quality Distribution, check UL interference Pwr Contrl setting to
compensate interference.
4. Check % of HO fail from adjacencies, focused on High HO Fail. Check
TCH_RF_HO_OLD. Check possibility to add some neighbor.
Try to prevent un proper HO and use FMT to reduce drop.
5. Check best serving cell, possibility HO to best serving cell (Macro or Indoor)
make it faster to prevent drop.
6. Check TRX alarm (mostly 7745 together with 7743 or 7746). Check TRX
configuration or reset TRX if needed.
7. Check TA distribution, coverage spillage and proposed physical tune.
8. Check and compare which one the highest: Fail on RADIO, ABIS & A_IF,
TR(transcoder) or LAPD.

Potrebbero piacerti anche