Friends, I got a missing neighbor between these two sites but the no handover failure, so does it mean that there’s a mistake in the neighbor relation between these two sites or there is another reasons for missing neighbor event… Thanks
Missing neighbour doesnt mean there is handover failure, there are many reason for HO failure, eg, target cell is blocking or have bad KPI so source cell couldnt perform HO when HO is triggered.
For your inquiry above, i think TEMS have methode to justify the missing neighbour event.
If im not wrong, when we perform drivetest using scanner and ue, tems always compare the best server from the scanner and best server from ue, if there is difference between best scanner and best ue, so it will count as missing neighbour.
CMIIW.
but for sure you must ensure that the neighbour must be defined apropriately in the database. Some time tems do the illogical missing neighbour event, so you should crosschek between the drivetest and live network database
Friends, I got a missing neighbor between these two sites but the no handover failure, so does it mean that there’s a mistake in the neighbor relation between these two sites or there is another reasons for missing neighbor event… Thanks
In GSM most neighbor relations are symmetric, also called mutual which means that you will be able to do handover from CellA to CellB , and from CellB to CellA. when you do a handover from CellA to CellB TEMS checks the neighbor list if handover from CellB to CellA is defined in CellB. If not defined a missing neighbor detection is triggered, that is most likely the reason you are getting that message. So if you do the drive test in the opposite direction the handover from CellB to CellA will not take place. just doubleclick over the missing neighbor report to see the source and target cell relation you must define in the bsc. Br, you know where the reputation and thanks buttons are if it helped
please I need any strategy for neighbor relations......when I should add and what to add ....what to delete and avoid
Thanks and reputation for all
Hi frien,
The neighbour should be defined effectively as the database has maximum neighbour definition. And should be inline with operator strategy, eg operator has more DCS spectrum than GSM...
1. define the neighbour on the first layer, for rural area define till second layer etc
2. the neighbour definition should be bothway as previous post by elche
3. parameter should consistent each other, as i have post on other post
4. GSM GSM HO,GSM DCS HO, DCS GSM HO and DCS DCS HO parameter should be define properly (layering strategy) both on idle and dedicated mode, to absorb traffic on DCS, avoid ping pong HO.
5. Handover feature could be implemented to improve the performance, eg Quality HO margin, traffic HO, fast uplink, speed sensitive handover.
6. Monitor the statistical performance
I suggest using your vendor specific tool for gathering call traces and analyzing them to get potential not added neighbors and added yet not needed neighbors, as call traces represent actual measurement reports; and the more the better!
Bookmarks