Softhandover Overhead problem

[raghchau]

In my network, soft handover overhead is very high(58%).

Can anyone suggest means to improve this?

[auto_art]

In my network, soft handover overhead is very high(58%).

Can anyone suggest means to improve this?
hi

check for pilot pollution
also..it not alarming if ur nw doesnt have much traffic..in new launced nw it generaly gives high values due to less traffic

[raghchau]

You are right..It is newly launched network but it is increasing gradually.

Initially it was 32% but in further 2 months it has increased to 58%.

Can you suggest some specific parameters to tune for this..

[auto_art]

You are right..It is newly launched network but it is increasing gradually.

Initially it was 32% but in further 2 months it has increased to 58%.

Can you suggest some specific parameters to tune for this..


its not much alarming..wait for some let traffic to rise...first...

there are not as parameter..noly way to reduce it to tune HO.

[maasricht]

Which vendor please specify?

[raghchau]

It is for Huawei system..

[adewijaya]

In my network, soft handover overhead is very high(58%).

Can anyone suggest means to improve this?

normally is 30%-40% for SHO Overhead, please consider with Time Propagation Delays on that sector and Pillot Polution Plot review, too many SHO make system high load on signalling.

[dimooon11]

58% is quite high ratio.
first eliminate all overshooting cells from your network - downtilt antenna, only after this you can think about look into parameter tuning, not before

[Tomas Delgado]

Mate try this, sometimes it works sometimes not, try with the parameter SHOqualmin and change it from -24 to -20 and see what happens.

[hesh]

Mate try this, sometimes it works sometimes not, try with the parameter SHOqualmin and change it from -24 to -20 and see what happens.

Although SHOqualmin is the param you can play with and some more parameters are also there like TRIGTIME1A ( you can increase like from 160 to 320) and FILTER COEFFICIANT can be increase (like 2 to 3)but again...this is tradeoff between SHO and Call drop...it could delay the SHO but may increase the Call drop.

So better idea is go with Hard optimization(tilt,azimuth change)..and limit the overshooting servers.

Hope this could help.

[Rodbar]

I think it is not the time to work with parameters. Is much better to make a physical optimization and then proceed to parameters change. Try to check electrical and mechanical tilt and azimuths first.

Regards,

RB

[raghchau]

As cluster & market optimizations have already been done,all the physical optimization we made. Now we are planning to run Schema cycle to further reduce pilot pollution issues.

[auto_art]

As cluster & market optimizations have already been done,all the physical optimization we made. Now we are planning to run Schema cycle to further reduce pilot pollution issues.

yeaah schema is good...it surely gonna help u.

[plannerguy]

Hi


1)Pls take the SHO report cell wise and base don same do a drive test in that cluster .
2)Do physicall optimization for site.

3)if it fails go for Parametric optimization.

4)finally go for pillot power decrease(Not recommened , but if now way then can be executed)

Regards
Plannerguy

[mobilink999]

I will say not to go Hesh method as this is not very fruitful. Better go for cluster drive and and then selectively reduce overlap area. It will be reflected in SHO factor. Any soft approach is bound to have some trade off.