-
Member
Reputation: 41
Co-BSIC / Co-BCCH
What are the effects of Co-BSIC and Co-BCCH on handover?
What is the effect when you have only Co-BSIC? Will handover fail?
Thank you
-
2009-05-05 09:41 PM
# ADS
Circuit advertisement
-
Originally Posted by
alkesh
What are the effects of Co-BSIC and Co-BCCH on handover?
What is the effect when you have only Co-BSIC? Will handover fail?
Thank you
What is the effect when you have only Co-BSIC? Will handover fail? ---- > no effect
What are the effects of Co-BSIC and Co-BCCH on handover -----> HO Fail + rach phantom
-
VIP Member
Reputation: 897
Originally Posted by
kais
What is the effect when you have only Co-BSIC? Will handover fail? ---- > no effect
What are the effects of Co-BSIC and Co-BCCH on handover -----> HO Fail + rach phantom
As far as i know, in SIEMENS co-bcch and co-bsic can not handover because the database will not take the values. It will give error !!!
Even in SIEMENS, you can not provide SAME BCCH with different BSIC as a NON-TGT NEIGHBOUR !
-
-
Member
Reputation: 44
Originally Posted by
kais
What is the effect when you have only Co-BSIC? Will handover fail? ---- > no effect
What are the effects of Co-BSIC and Co-BCCH on handover -----> HO Fail + rach phantom
Yeah... that's right.
Co-BSIC and Co-BCCH --> impact to increase HO-Failure and Low RACH success rate.
-
VIP Member
Reputation: 897
Originally Posted by
radenmohawk
Yeah... that's right.
Co-BSIC and Co-BCCH --> impact to increase HO-Failure and Low RACH success rate.
Co-BCCH and Co-BSIC can not be neighbor then how can u have HO Failures?
-
Member
Reputation: 91
Originally Posted by
lccengr
As far as i know, in SIEMENS co-bcch and co-bsic can not handover because the database will not take the values. It will give error !!!
Even in SIEMENS, you can not provide SAME BCCH with different BSIC as a NON-TGT NEIGHBOUR !
it's right when you are aplying these parameter and you submit the LMT wil not execute this MML command and will prompt you that this is not alowed freq or value this is like a internal check in siemens database to avoid confusing situation
please for the other experts on other vendor make comment about your equipment to know on these mismatch impact
-
NSN BSC also doesnt allow Co BCCH-BSIC cases for nbr cells,
The BSIC of two cells should be different ONLY if they use the same BCCH.
The TSC shall be equal to the BSIC.
Finally, the impact of co BSIC and co BCCH : SDCCH Assignment failures (and or Random Access failures), HO failures, and possibly wrong decoding of TCH (interference) due to same TSC.
One RACH sent to one cell will also be decoded to the other cells. Both cells will send an Immediate assignment, but only one will receive an answer from MS. The other one will count this as a sdcch assignment failure due to poor radio
BR\
-
Member
Reputation: 44
Originally Posted by
lccengr
Co-BCCH and Co-BSIC can not be neighbor then how can u have HO Failures?
Yeah.. I mean in the case if those cells not created as neighbor but have same BCCH and BSIC..
-
VIP Member
Reputation: 897
Originally Posted by
radenmohawk
Yeah.. I mean in the case if those cells not created as neighbor but have same BCCH and BSIC..
If the cells are not created as neighbors then there is no HANDOVER !!!
The answer to his query is very simple, Co-BCCH and Co-BSIC can not be neighbor, HO is impossible in it that is why the BSS System can not take the values and internal check gives u an error when u try to make Co-BCCH and Co-BSIC as neighbors.
In Siemens, Co-BCCH can not be a neighbor, even if the BSICs are different it will not take the Co-BCCH as a neighbor.
Everyone is a genius at least once a year. The real geniuses simply have their bright ideas closer together.
Regards,
Venom
Bookmarks