Cross feeder study was done by Drive test analysis and daily stats monitoring.

Drive Test Analysis:

We take example of DCS cross feeder in case of concentric sites:

MS is detecting very good Rx_level of serving BCCH (900 band) and camps on this cell
but after some time it will make zone HO to DCS and as it goes to DCS its level becomes
so much degraded(near -100dbm) so it again make emergency HO (cause 10,11) back to
GSM.
So many ping pong HOs are observed in this area resulting in degraded quality. Also
DCR HO increases, call efficiency degraded and incoming HSR is much degraded
resulting degraded HSR of neighboring sites.
This is possibility of cross feeder.
Attached is one log file having cross feeder on FSD7957.

Stats Analysis:

Same above case can be analyzed by daily stats. First we have to check on site level stats
either problem is in one cell or more than one cell. If problem is more than one cell then
in case of cross feeder it should start on the same day. If we see on daily TRX level same
number of TRXs are showing bad incoming HO efficiency and call efficiency also
having high DCR HO. One can send this case for health check but no improvement after
health check or reset TRXs will be observed because in actual problem is something else.

e.g.

TRX#2 of sector B, C can be problematic at the same time and same day.

Also from Rx_Qual vs. Rx_level matrix on TRX level we can predict same thing like in
this case on problematic TRXs most of the samples will be in bad Rx_level range while
other same hopping TRXs will be showing most of the samples in good Rx_level range.


Note : Through these findings cross feeder on 9 sites was found in FSD city before this
all these issues were raised just for health check and SUMA replacement.