- This topic has 16 replies, 1 voice, and was last updated 12 years, 8 months ago by milenio.
16th December 2008 at 12:13 #55046AntapéGuest
i have couples of cells with one way ho success rate very low, my ho parameters are ok. please give solution!!!16th December 2008 at 17:26 #55047pixGuest
check preparation success rate and efficiency rate, check the cause of the failure (thanks to indicators in your PM Viewer) : congestion, radio BSS prep failure or BSS failure ?
didn’t we have a discussion about this already ?17th December 2008 at 13:44 #55048AntapéGuest
the example of this problem:
cell1 to cell2:100%ho success
cell2 to cell1: 7%ho success
with no congestion in cell1 and good ho success with other neighbours.
The preparation is good also but the execution is bad.
i think to decrease homarginlev in one sense since most of ho cause in cell2 is due to weak ul level. what do you think?19th December 2008 at 13:52 #55049Johnson CrewGuest
What could account for the difference in values between HO decision and attempts on an ericsson network?20th December 2008 at 17:55 #55050pixGuest
poor execution from cell 2 to cell 1 has nothing to do with congestion, but probably more with a broken TRX in cell 1
what is the call setup success rate of cell 1 ?
more precisely, what is the TCNAFLR (tch normal assignment failure rate) ?
if cell 1 is working perfectly, then you should check the radio conditions in the area where MS are most probably doing the HO from cell 2 to cell 1. Check interference, or obstacles, that could stop the radio link suddenly. However, with 7% success rate, I would assume it’s more of a TRX hardware problem than a radio problem.22nd December 2008 at 12:39 #55051AntapéGuest
cell1 has 1.15% of tch assignment fail.I think it is not HW problem since other cell1 neighbours has successefull HO, only low HOSR with cell2.
Thanks!22nd December 2008 at 15:43 #55052PixGuest
Ok, that’s a little strange… If you’re certain you don’t have any kind of interference, if you’re sure the coverage at the intersection of both cells is good, and finally, if you’re sure the HW is good (it looks like it is good) then the only possible issue is a kind of software bug.
I’m sorry, I cant help anymore than this…23rd December 2008 at 20:18 #55053EvgenGuest
Antapé, which type of HO from cell 2 to cell 1 (intraBSC, interBSC or interMSC)? Which HOSR on cell2 for outgoing HO to other neighbours.29th December 2008 at 18:30 #55054krishnanGuest
During drive test ,my voice call get muted for few seconds e whenever hand off takes place and then call get drop.Pl tell me the reaons.30th December 2008 at 13:39 #55055AntapéGuest
it’s intraBSC ho, HOSR from cell2 to other very good. this is why i do not catch this problem.
Thanks!6th February 2009 at 02:49 #55056tranhungGuest
we are using nokia BSS, problem with HOSR as:if “freq list is taken from the adjacent cells” HOSR get 95%- 96% only. When we create BA list include all freqs adjacent cells, HOSR increase to 98%. help me why?6th February 2009 at 09:36 #55057PixGuest
I don’t understand the differences between the two choices…
freq list is taken from the adjacent cells
we create BA list include all freqs adjacent cells
Could you give an example of BA list?7th February 2009 at 03:42 #55058tranhungGuest
I ask another question clearly:
Parameter : “Measurement BCCH Allocation list” need set 0 or 1 Why?, what happen if set 1 or 0 ( We using BSC/BTS Nokia.
Thank alot7th February 2009 at 15:03 #55059PixGuest
your first question got an answer already ?
for the second question, i still can’t answer: this parameter name doesn’t ring any bell (i don’t work with nokia system). Perhaps you can write down the description of this parameter? Its properties? Then I could tell you what it does.7th February 2009 at 17:48 #55060Azzazi_RFoptimization_engGuest
you may do the following:
1- check HO type from Cell2 to Cell
2- check HO margin and hreqav between them.
3- make drive test and ensure the HO conditions are satisfied in the field or not.
4- you can delete the neighbor relation between them and redefine it again (maybe it is a software bug)