Very good idea to do classification based on EcNo or RSCP for IRAT HO causes.

Yo
u can do it easily in Ericsson network based on GPEH data, where entire IRAT HO
process fully presented with all RF information correlated.
As for s52d statement on limited KPIs number and SON, I would like to say that a
s for number of KPIs you are 100% correct that it should a limited number of Key
PI for level one performance monitoring, but for solving issues like IRAT....KP
Is is not sufficient and you need more info about RF environment and causes. IRA
T HO problem is pretty serious you can split at least for two parts:
1. Dedicated mode IRAT HOs that may significantly affect overall network Drop Ra
te especially for CS connections, since it is a HHO with RAT change.
2. Idle mode 3G coverage lost and ping-pong 3G selection/reselection where exces
sive signalling for LU exists in UTRAN and GSM networks, this may cause serious
problem of lost incoming calls in case where LACs between GSM and UTMS are not s
ynchronized (i.e. not the same). During RAT selection and LU your mobile is not
available for incoming calls for 3-5 seconds. Once RAT Reselection occurs too of
ten, then probability to get Mobile Is Off (MIO) too high.
As for SON....to make dynamic changes for IRAT HO parameters per cell basis....I
think this is not efficient at all. The real SON taking care for most significa
nt issues that may affect the root cause for unnecessary IRAT HO....bad RSCP and
bad EcNo....this is can be treated efficiently in SON via antenna etilt optimiz
ation...such SON already exists and performing.....if you would like to know mor
e on this issue I can share some info with you.
Very good idea to do classification based on EcNo or RSCP for IRAT HO causes. Yo
u can do it easily in Ericsson network based on GPEH data, where entire IRAT HO
process fully presented with all RF information correlated.
As for s52d statement on limited KPIs number and SON, I would like to say that a
s for number of KPIs you are 100% correct that it should a limited number of Key
PI for level one performance monitoring, but for solving issues like IRAT....KP
Is is not sufficient and you need more info about RF environment and causes. IRA
T HO problem is pretty serious you can split at least for two parts:
1. Dedicated mode IRAT HOs that may significantly affect overall network Drop Ra
te especially for CS connections, since it is a HHO with RAT change.
2. Idle mode 3G coverage lost and ping-pong 3G selection/reselection where exces
sive signalling for LU exists in UTRAN and GSM networks, this may cause serious
problem of lost incoming calls in case where LACs between GSM and UTMS are not s
ynchronized (i.e. not the same). During RAT selection and LU your mobile is not
available for incoming calls for 3-5 seconds. Once RAT Reselection occurs too of
ten, then probability to get Mobile Is Off (MIO) too high.
As for SON....to make dynamic changes for IRAT HO parameters per cell basis....I
think this is not efficient at all. The real SON taking care for most significa
nt issues that may affect the root cause for unnecessary IRAT HO....bad RSCP and
bad EcNo....this is can be treated efficiently in SON via antenna etilt optimiz
ation...such SON already exists and performing.....if you would like to know mor
e on this issue I can share some info with you.
Very good idea to do classification based on EcNo or RSCP for IRAT HO causes. Yo
u can do it easily in Ericsson network based on GPEH data, where entire IRAT HO
process fully presented with all RF information correlated.
As for s52d statement on limited KPIs number and SON, I would like to say that a
s for number of KPIs you are 100% correct that it should a limited number of Key
PI for level one performance monitoring, but for solving issues like IRAT....KP
Is is not sufficient and you need more info about RF environment and causes. IRA
T HO problem is pretty serious you can split at least for two parts:
1. Dedicated mode IRAT HOs that may significantly affect overall network Drop Ra
te especially for CS connections, since it is a HHO with RAT change.
2. Idle mode 3G coverage lost and ping-pong 3G selection/reselection where exces
sive signalling for LU exists in UTRAN and GSM networks, this may cause serious
problem of lost incoming calls in case where LACs between GSM and UTMS are not s
ynchronized (i.e. not the same). During RAT selection and LU your mobile is not
available for incoming calls for 3-5 seconds. Once RAT Reselection occurs too of
ten, then probability to get Mobile Is Off (MIO) too high.
As for SON....to make dynamic changes for IRAT HO parameters per cell basis....I
think this is not efficient at all. The real SON taking care for most significa
nt issues that may affect the root cause for unnecessary IRAT HO....bad RSCP and
bad EcNo....this is can be treated efficiently in SON via antenna etilt optimiz
ation...such SON already exists and performing.....if you would like to know mor
e on this issue I can share some info with you.