How to improve the handover

success rate in OMC

Basic propose
AUsing Nastar check the neighbor is reasonable or not, if not,
we can directly delete it, if lost ,we should add.
BIf the neighbor is external cell, we should check the CGI and
BSIC carefully
C Basic parameter check, for example: encryption
algorithm, handover switch, MA.
DAnalysis the handover fail times, do some adjust as whole
E find the top ho failed times cell and register the GSM Cell
to GSM Cell for analysis
F Hardware problem should be solved: both warning and
hidden hardware problem;

Whole analysis

Analysis why it failed and give a litter big threshold for that kind of HO type:
Here is the demo for outgoing analysis (we should consider both attempt times
and failed times)

H372A:Failed Cell
Outgoing
Handovers
(Uplink
Quality)

H372B:Failed Cell
Outgoing
Handovers
(Downlink
Quality)

H
372L:Failed Cell
Outgoing
Handovers
(Other
Causes)

H372D:Failed Cell
Outgoing
Handovers
(Downlink
Strength)

H372C:Failed Cell
Outgoing
Handovers
(Uplink
Strength)

H372F:Failed Cell
Outgoing
Handovers
(Better Cell)

For example:
if we find PBGT success rate is low, we can adjust the Inter-cell HO
Hysteresis , PBGT HO Threshold to reasonable big value for it.
If we find the downlink strength HO success is low, also increase the Edge HO
DL RX_LEV threshold;

But pay attention dont modify them to big value, otherwise some
other KPI will be affected, we should pay attention to the top bad
cell analysis if this kind of adjust no result!

Parameter check
Background:
How Huawei handover algorithm work:
Only neighbor cell RxLev is higher than the threshold, then the neighbor
cell can be allowed in the candidate cell queue, otherwise no handover
will come to this neighbor cell. this is we called M criterion.

- Normally, if we setting this value as a big value, for example , -86dbm is

the threshold for handover candidate cell, the handover success rate
may be improved quickly.
- If the threshold is so high (for example -80dbm), we may meet the risk
that no handover can happen, and the call drop will be increase quickly
and RxQuality will be bad also.
- K-bias will also be used for try to decrease the bad impact on other
KPI( call drop, Rx quality ) .

Parameter check
How to setting:
M rule you will setting here: we suggest 20

Parameter check
If no improve, you should do things as following:
In M2000, analysis the Top10 handover fail times cell and
register GSM cell to GSM cell object for the top 10.
Check every top10 bad cells, see handover to which neighbor cell is the
most bad, then using the K-bias punish the most bad neighbor:

For those bad cell / cell

handover , increase the
Min Access Level
Offset, for example ,we
can setting 10, (if
downlink candidate is 20),
only when the special
bad neighbor cell RxLev
big than -80dbm ,
handover may happen,
normally it will success.

Hardware check
Sometimes, HO parameters modify in top cell but still
low HO success rate.
We should also check hardware problem first:
Alarm information collection
TRX level stat. analysis for hardware fault but no alarm

We can check both the

attempt immediate
assign/assign times and
success times; if there
are big gap between
them , normally TRX
problem/ install quality
problem and such kind of
hardware issue.