Académique Documents
Professionnel Documents
Culture Documents
By
Grant Chivandire
Level Handover
DL/UL RxLev < HO Threshold DL/UL
Quality Handover
Quality level < Quality thresholds
Interference Handover
High RxLev but poor quality
Late Handover
Check handover margins between neighbours
Hierarchical Cell Structure
Power control
Missing Neighbours
No handover to neighbour cell that seems like best server
Sudden appearance of strong cell in neighbour list after handover
Stepping stone effect
Fake Neighbours
Good candidate but handover does not take place leading to a call
drop
Fake neighbour – same BCCH with defined neighbour, itself not
defined
Missing BCCH in measurement list, NCC Perm, Co-BCCH
Grant Chivandire - Radio Planning and
10
Optimisation Specialist
Handover Issues – Problems (cont…)
Overshooting
Island effect
No good candidate to handover to
Timing Advance much greater than half of your inter-site distance
Swapped sectors
Defined neighbours will show poor levels
May exhibit “stepping stone” effect
May lead to drag and drops
Log file
Central_longCalls_20090514_CELLC_CENTRAL004.dlf
Analysis
High interference at call drop
Handover failure 8seconds before call drop
Serving Cell =>BCCH=1012, BSIC=57, CI=41776, RxLev=-78, RxQual=7
Confirm serving cell details with Signalling messages and other
database – BSCplan, Asset etc
Channel => Hopping TCH
Handover Failure => look at Handover Command and Handover Failure
messages
Check if neighbour is defined properly in database
Measurement Reports => observe target cell is 4th candidate in
neighbour list
Grant Chivandire - Radio Planning and
15
Optimisation Specialist
Case Analysis 1 (cont…)
Analysis
Confirm neighbour cell information in database
Notice the proximity of the MS to nearest neighbour cells
Formulate ideal behaviour – why did the MS try to handover to the
fourth candidate leaving the better 3?
Suspect fake neighbour problem
In Actix map, show CI properties on cells
In database, look for the BCCH of the 3 candidates and identify
defined cell and CI
Notice that the 2nd sector of serving site, a defined neighbour, has the
same BCCH as the first candidate
Missing neighbor has been detected
Analysis
Notice the distance of serving cell compared to nearby cells
Check terrain profile using Asset, clutter using Google Earth and
neighbour candidates levels to see if acceptable
Site is overshooting, consider down tilting
Log file
Central_longCalls_20090514_CELLC_CENTRAL004.dlf
Analysis
High interference at call drop
Handover failure 15seconds before call drop
Repeated inter-cell handover failures following a series of intra-cell
handover
Neighbour defined correctly
Handover failure due to timer expired
Deduce that high interference corrupted signalling information
Notice intra-cell handover did not help interference problem
Review hopping parameters