P. 1
Optimization Guide (2)

Optimization Guide (2)

|Views: 148|Likes:

More info:

Published by: Patrick Babatunde Sanni on Nov 04, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

07/15/2013

pdf

text

original

TCH assign failure congestion Problem detection: TCH assign. Congestion max.

> 2 % (Critical , action needed) TCH Load BH (Erlang / capacity ) > 90 % (forecast) Investigation:

Check for hardware availability by comparing: RTCH_nb (TCRRN) with RTCH_available_avg (TCAVAN)

Any TRXs down or not carrying traffic?

Yes

Report to BSS support team

NO

Check through thematic map TCH load BH on cell neighbors. HO Inc congestion on neighbors.

NO

Any neighbor site(s) down not carrying traffic?

Yes

All neighbors are loaded (> 80%) + High Inc HO congestion

NO

Check with RNP if planned coverage overlap with neighbors is sufficient for smooth HO flow.

Yes

Check better condition parameters for each couple. Check High HO Inc execution failure on neighbors, if yes follow same investigation in call drop HO sheet. Check through drive test (RMS) coverage for serving loaded cell vs. neighbor free cell. Antenna optimization needed? Hardware check needed?

Yes Request for upgrades, Calculate # of combiners needed and check with RNP if there will be no coverage problem if additional combiner is used Request for Densification sites RNP

NO Densification sites needed

Traffic sharing Enable FDR on serving cell Enable Traffic HO for each couple and adjust relevant parameters according to drive test analysis. (or leave default values according to # of TRX) Enable Fast traffic HO, but monitor HO/call rate and call drop HO specially for cells with many inter BSC adjacencies

Apply # LU reduction procedure in SDCCH Congestion sheet NO NO Yes NO Reduce queuing Solve TCH blocking prob.: RTCH_assign_queued_rate >50%? T11 is set to values higher than default ( > 6 seconds) ? High SD duration average (> 5 s) Yes Check TRX carrying SD TS for alarms Check TCU handling TRX with SD TS for alarms Reset TCU High TCH call drop HO Yes Same investigation should be followed Extreme queueing ? Check if TRX carrying SD is problematic .SDCCH drop rate Problem detection: High SDCCH drop rate > 0. see if it was set previously to high values (> 6db) (to reduce # of LU. but can increase SD Drop) LU procedure leads to higher duration on SD (4s).5 % Investigation: BSS drop > 40% of total drops NO Radio drops > 40% of total drops NO HO drops > 40% of total drops Yes Yes Check for Extreme queueing Situation i. (refer to TCH congestion solving sheet) Reduce T11 value (TCH congestion should be monitored) Enable SD HO Reduce averaging window Reduce HO margin (optional) Disable SDCCH HO.e. but with careful monitor of SD drop radio Move SDCCH TS to another TRX preferably handled by different TCU High TCH drop radio Yes Call drop radio investigation should be followed . if Yes move SD TS to another good TRX Check value of cell_reselect_hyst.

Densification site – Request for RNP study.Make sure all neighbor relations are defined handover and reselection 3. Check the value of BTS_Q_LENGTH: for values > default 2 TRX 4 TRX 6 TRX 4 6 10 Check % RTCH requests queued: high percentage (> 40%) can lead to SDCCH resources blocking for T11 period of time. 4. congestion > 0. High % LU (> 50%) Action: Check HO flow to study if cell needs to be downtilted to reduce overlap with neighbors in different LAC Increase cell_reslect_hyst on LAC border cells to reduce # of LU (monitor of SDCCH drop radio is necessary) Check with architecture the possibility to re-design LAC plan to minimize as much as possible LU Check value of T3101 and see if it is set to default value Increase SD capacity if possible: Consider TCU load Consider TCH blocking High % other services: a) IMSI attach b) IMSI detach c) SMS d) Supplementary services Action: 1-Increase SD capacity if possible: Consider TCU load Consider TCH blocking 2.5 % SDCCH Load BH (Erlang / capacity ) > 90 % Investigation: NO High signaling load? > 4 Yes Check SDCCH traffic model for split of services SDCCH capacity is not optimized.SDCCH assign failure congestion Problem detection: SDCCH assign. Recalculate SD/TCH time slots needed using traffic model to reach optimum situation. Signaling load = SDCCH requests / TCH requests .Use the parameter cell_reselect_offset to increase neighbor’s re-selection.

feeder or connections prob.Call drop radio Problem detection: 1. High rate of outgoing HO failures (follow HO drop investigation) NO High % UL level Yes High % DL level NO Check for unbalanced path loss (RMS) NO High % DL quality Check Frequency plan Check drive test for overshooting problem High %UL interference & quality Check for antenna. Investigation: No Yes HO per call rate (>10%) Isolated cell Yes Densification sites are needed NO Hardware Problem Yes No Check HO causes Report to BSS team Check adjacencies for missing relations Check if No HO if possible due to 1. 2. Check external interferer (idle interference) UL level threshold Yes *Check for coverage problems (holes) *Check missing neighbors HO per call rate = number of “outgoing Handovers success / TCH seizures” . congestion on neighbors 2. High call drop rate on the cell > 1 %. % Radio drops > 40% of total dropped calls on the cell.

% HO drops > 30% of total dropped calls on the cell.Call drop HO Problem detection: 1. Investigation: No High HO out execution failure rate? >40 % Yes Identify critical pair of cells. High call drop rate on the cell > 1 %. check if relation is defined correctly (external cells) Check for synchronization problems Check neighbor plan for unnecessary (Far) neighbor declarations. (with Out HO drop > 5 %) using Type 26 (on demand counter) NO Majority of failure is Inter BSC? Yes Good % of better condition (>40%) NO *Check better conditions parameters. Yes Check DL Qual / UL Qual on target cell to locate interference problem. *Check for severe interference on serving cell * Check for coverage continuity Check for BCCH/BSIC duplication in cell adjacencies Check for database inconsistency between OMC-R and BSC Check for BCCH/BSIC duplication in cell adjacencies For neighbors in different OMC-R . Check DL Lev /UL Lev on both serving & target cell for coverage problem . 2. Check DL Lev /UL Lev on target cell for coverage problem High % ROC? Yes NO Check DL Qual / UL Qual on both serving & target cell to locate interference problem.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->