A frequency in the BA list but not in the neigbour list. Let us take the case:
Case 1:
BSC finds that the frequency is a better candidate for handover.
Then BSC checks the neigbour list for the reported BSIC. And BSC doesnot find the said BSIC in the neighbour list. Hence no handover command message will be sent to MS.
Drawback: You looses a possible good candidate.
Case 2:
BSC finds that the frequency is a better candidate for handover.
Then BSC doesnot performs the neigbour list check.Handover command message will be sent to MS.
After that BSC performs the neighbour list check and founds that BSIC is not the neighbour. But until now it is too late. The handover command message has already been sent to MS.
Advantage: The MS attempts HO and fails. You have a easy way to find out the best candidate which is being missed or a missing neighbour.
So…
Is it possible to configure the HO sequence/settings according to the need.
regards
Note: Practical data is available where it is shown in the TEMS log files that HO fails are due to missing definations of neighbours.
Hence it is sure that HO command is being given by the BSC inspite of the fact that a BSIC is not a neighbour.