Академический Документы
Профессиональный Документы
Культура Документы
> 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)
Yes
NO
Check through thematic map TCH load BH on cell neighbors. HO Inc congestion on neighbors.
NO
Yes
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
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
SDCCH drop rate Problem detection: High SDCCH drop rate > 0.5 % Investigation:
NO
NO
Yes
Yes Check for Extreme queueing Situation i.e.: 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
Yes
Extreme queueing ? Check if TRX carrying SD is problematic , if Yes move SD TS to another good TRX Check value of cell_reselect_hyst, 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). Apply # LU reduction procedure in SDCCH Congestion sheet NO NO
Yes
NO
Reduce queuing Solve TCH blocking prob. (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, but with careful monitor of SD drop radio Move SDCCH TS to another TRX preferably handled by different TCU
SDCCH assign failure congestion Problem detection: SDCCH assign. congestion > 0.5 % SDCCH Load BH (Erlang / capacity ) > 90 % Investigation:
NO
Yes
SDCCH capacity is not optimized. Recalculate SD/TCH time slots needed using traffic model to reach optimum situation. 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.
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- Make sure all neighbor relations are defined handover and reselection 3- Use the parameter cell_reselect_offset to increase neighbors re-selection. 4- Densification site Request for RNP study.
Call drop radio Problem detection: 1. High call drop rate on the cell > 1 %. 2. % Radio drops > 40% of total dropped calls on the cell. Investigation: No Yes
Isolated cell
Yes
NO
Hardware Problem
Yes
No
Check HO causes
Check adjacencies for missing relations Check if No HO if possible due to 1. congestion on neighbors 2. High rate of outgoing HO failures (follow HO drop investigation) NO
High % UL level
Yes
High % DL level
NO
NO High % DL quality Check Frequency plan Check drive test for overshooting problem High %UL interference & quality Check for antenna, feeder or connections prob. Check external interferer (idle interference) UL level threshold
Yes
Call drop HO Problem detection: 1. High call drop rate on the cell > 1 %. 2. % HO drops > 30% of total dropped calls on the cell. Investigation:
No
Yes
Identify critical pair of cells, (with Out HO drop > 5 %) using Type 26 (on demand counter)
NO
Yes
NO
*Check better conditions parameters. *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 if relation is defined correctly (external cells) Check for synchronization problems Check neighbor plan for unnecessary (Far) neighbor declarations.
Yes Check DL Qual / UL Qual on target cell to locate interference problem. 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. Check DL Lev /UL Lev on both serving & target cell for coverage problem