Introduction

Based on Tele2 Anderss request email, we found extreme amount of Ping-pong HOs under the
site T314003 (one UE made 112 HO in 116 seconds, approximate 1 HO per second) on 23rd May.
Huawei put this problem in Tele2 LTE Technical Open Issue List, and gave the following reasons:

"This is the problem that HO delay is allowed to be 2 dB (A3 offset is 1dB and A3 Hysteresis is 1dB), which
is suitable for high load network and make HO success rate much higher.
Based on this is quite light load network, 2dB seems too easy to trigger a HO on the edge of two cells in
overlapping area.
But we do not know how fast the load level will grow up when Tele2 launches LTE Commercial UE in a big
scale in September, so we still keep this setting as default.
And for some specified sites, Huawei also gave the following suggestions:

The optional suggestions in priority sequence to mitigate the situation:

1, L3 filter coefficient from default 6 to 9

2, Time to trigger from 320ms to 640ms

3, CIO from 0dB to -1dB

So, start on 26th May, Huawei modified some sites parameters, and also traced the OSS
statistics, here below is the history of modifications.

16:00 26th May, T314266 and T314359s L3 filter coefficient modified from FC6 to FC9
10:00 27th May, T314573, T314515, T314510, T314869, T314504 and T314809s L3 filter
coefficient modified from FC6 to FC9
11:30 30th May, Time to Trigger (TTT) between the cells L3148694 <-> L3145045,
L3145154 <-> L3145105 is modified from 320ms to 640ms

Here below in this document, we will analysis the OSS statistics by Ping-pong HO pairs, the
statistics before and after parameter modifications will be compared, and also assisted with the
traced logs in eNodeB by using LMT.
The first pair: T314266 and T314359
From our trace and OSS statistics, the Ping-pong HO happened between the cells L3142666 and
L3143596, here below is the details:

We can see from the statistics that the HO times reduced significantly after we modified the L3
filter coefficient, and most important, the HO failures and call drops are both reduced
dramatically.

And from our LMT trace log (RRC measurement report), we can see the signal level is very good
(see below, RSRP > -140 + 40 dBm =-100 dBm), which means that the overlapping zone between
L3142666 and L3143596 is a little bit too big for L2600.
The second pair: intra-site HO of T314573
From our trace and OSS statistics, the Ping-pong HO happened between the cells L3145734 and
L3145735 and high HO failures, here below is the details:

We can see from the OSS statistics that although the HO times didnt decrease too many, but
HO failures and call drops reduced largely. Why the HO attempts didnt decrease? From our
analysis, this is because the signal environment in this area is very complicated, please see the
map below, four sites have coverage in this area including T314573, T314274, T314304 and
T314275, and the distance between these sites and the possible user is only around 400 meters.
 And from our trace logs, we can see the signal level in this area is very poor, the RSRP is around
-140 +20 dBm = -120 dBm, thats why it still causes HO failures and call drops after parameter
modification. PCI = 226 is the cell L3145735.
The third pair: T314515 and T314510
From our trace and OSS statistics, the Ping-pong HO happened between the cells L3145154 and
L3145105, here below is the details:

We can see that after we modified the L3 filter coefficient of those two sites, the HO attempts
and especially the HO failures didnt decrease on 28th May (Saturday), and then on 30th May
(Monday), the time to trigger (TTT) between the related cells were configured, and we can see
the progress.

While for this area, the signal quality is still poor due to coverage, the neighbor cells are almost
1300 meters between each other, see the below map:
And the signal quality for example RSRP is around -120 dBm, which indicates it is a poor
coverage area. PCI = 307 is the cell L3145105
The fourth pair: T314869 and T314504
From our trace and OSS statistics, the Ping-pong HO happened between the cells L3148694 and
L3145045, here below is the details:

We can see that after we modified the L3 filter coefficient of those two sites, the HO attempts
and especially the HO failures didnt decrease on 28th May (Saturday), and then on 30th May
(Monday), the time to trigger (TTT) between the related cells were configured, and we can see
the progress.
The fifth pair: intra-site HO for T314809
From our trace and OSS statistics, the Ping-pong HO happened between the cells L3148094 and
L3148095 and high HO failures, here below is the details:

We can see from the statistics that the HO times reduced significantly after we modified the L3
filter coefficient, and most important, the HO failures and call drops are both reduced
dramatically.