You are on page 1of 43

Basic Optimization Techniques

May 2008
FARHAN EJAZ

Key Performance Indicator’s (KPI)
 CSSR (Call Setup Success Rate)
i. TCH Traffic/TCH Blocking
ii. SDCCH Traffic/SDCCH Blocking
iii. SDCCH Success Rate (SDR)

 Drop Call Rate (DCR)
 HOFR (Handover Failure)
 HOFR LOS (HO Failure due to lack of resource)

CSSR (Call Setup Success Rate)

CSSR Analysis:
– High TCH Blocking Rate (low TCH Access Rate)

– High SDCCH Blocking Rate (low SD Access Rate)
– Low SDCCH Success Rate (high SDCCH Drop Rate)
 Check for normal RF conditions
• BCCH

• Tilts etc.
• Check from Report 166 what might be the causes for low SDCCH success rate

 Shifting of SDCCH to BCCH TRX moving it from Hopping TRX.

TCH Traffic and TCH Blocking

Inadequate SDCCH/AGCH channel capacity preventing TCH assignment.

Inadequate TCH resources resulting in channel assignment failure.

 TCH Traffic and TCH Blocking
• TCH Traffic for MOC and MTC call
 Traffic in erlang

• 1 erlang means 1 subscriber occupied 1 circuit for 1 hour
• 1 erl = 1 (sub) * occupy time (sec)/3600
• High Blocking rate => High Traffic , Low Availability

TCH Traffic and TCH Blocking Rate .

Traffic Distribution & possible solutions .

Case Study: TCH_RAW_BLK .

Congested Cell DCS/GSM Traffic Balancing through parameters .

By Using Aggressive FRU/FRL Settings .

Coverage Prediction using ASSET 3G .

for that purpose we need to raise it on Service Desk.TCH_UNAVAIL Impacting CSSR If TCH_Unavail is high on site then we have to resolve it on priority basis. . but 1st confirm that the issue is there for some time.

Solutions for Reducing TCH Blocking Solution  Remove any TCH_UNAVAIL issue  Use aggressive FRU & FRL settings  Coverage Control (Down tilting. Aggressive PBGT settings)  Increase Capacity (Add more TRX)  Plan new sites in that area for Traffic Sharing . Reduce Antenna height)  Parameter (Traffic Sharing.

low Availability Solution  Increase Capacity (add more SDCCH Timeslot)  Reduce unnecessary Location update .SDCCH Traffic & SDCCH Blocking SDCCH Usage  SMS  Location Update  IMSI Detach/Attach  MOC&MTC Call  Supplementary Service (Call waiting. call forwarding)  High Blocking => High SD Traffic.

SDCCH Traffic & SDCCH Blocking Rate .

SD’s on 900. then we can define SD TS on DCS SD BLK might be high due to high # of location updates/IMSI Attach & Detach or DR HO attempts .High SD_BLK Segment Analysis If SD BLK is high and we already have defined max.

Effect of SD_AVAIL on SD BLK .

.SD_BLK due to Location Updates Too many location updates on this segment we can use aggressive “cellreselecthysterisis” settings to avoid too many cell reselection in idle mode.

SD Utilization by IMSI Attach/Detach .

SD Drops SD Drops Reason:  Low Signal Level  Interference  Hardware Fault (BSC/BTS/TRX/TSL/Transmission) .

SD Drops Analysis using report :: 166 .

DROP CALL RATE (DCR) Drop on Handover  Interference on target cell  Incorrect serving cell Low Signal Level/Quality  RxLev/RxQual thresholds exceeded  MS enter high attenuation area (building/tunnel etc)  High Co .Adjacent and/or External Interference  Excessive interference on TCHs  Excessive interference on CCHs Hardware degradation .

DCR_USR from Optima Stats .

DCR Distribution from Optima .

DCR Analysis using Report :: 163 .

196 :: Quality Report .

Interference due to Co-BCCH / Co-BSIC .

Analyzing Quality issue using TEMS LOGS .

Impact of Interference on DCR & CSSR .

TA Report 232 .

Per NBR Attempt Report :: 153 .

Drop due to Non RF reason (TXN or NSS end) .

Call Drop due to Intracell HO Failure .

Radio Link Timeout Expiry due to HO Failure .

Radio Link Timeout Expiry due to Weak Coverage Patch .

Lack of Dominant Server .

Handover Failure (HOFR)  Handover Failure Rate  Co-BSIC/BCCH problem  Freq Clash  Traffic from large TA’s  HW suspected issue  Missing neighbors of any neighbor site  Low Signal level  Bad Quality  HOFR LOS = 100*HO Fail due to Neighbor Congested/Total HO request  HOFR LOS solution  Solve TCH Blocking of Target cell .

 Utilize automated neighbour detection  Identify inconsistent neighbour profiles  Modify appropriate neighbour lists .Optimizing Neighbour Lists  Effects of poor maintenance:  Unwanted legacy neighbours  Oversized neighbour lists  Co-channel neighbour definitions  Missing neighbours  Unintentional 1-way neighbour definitions  Optimise by:  Analyze neighbour performance from statistics.

BCC and frequency (076)  Cells having high HO failure ratio (150)  Adjacencies having high HO failure ratio (153) .Reports for HOSR/HOFR Analysis  Adjacency discrepancies (060)  Frequency check of adjacent cells (062)  Adjacent cell double frequencies (069)  Adjacent cells with the same NCC.

Report :: 74 .ADJACENCIES OF CELLS .

Analyzing 074 Using MapInfo Tools .

ADJACENT CELLS WITH THE SAME NCC.BCC AND FREQUENCY .Report :: 76 .

customer habits (voice/data usage).  Investigating customer distribution.  Checking any fault reports to limit possible hardware problems prior to test.  Checking trouble ticket history for previous problems. major roads.Routine Optimization Check Points  Cluster definitions by investigating BSC borders. .  Running specific traces on Network to categorize problems. main cities. freeways.