- This topic has 26 replies, 1 voice, and was last updated 10 years, 11 months ago by pix.
4th May 2007 at 07:27 #47171Rajiv GujralGuest
Im facing handover problems in many cell especially Inter BSC handovers and in the trace im getting “Hanodver Failure RR Cause: Protocol Error” or “Timer Expired”.
If anyone can help me out in solving the problem.
Rajiv4th May 2007 at 12:14 #47172PixGuest
Possible causes :
1. Channel type combination not supported or invalid data
2. or CIC is present for SDCCH connection;
3. or CIC is missing for a TCH connection;
4. or Cell identifier for target cell is not present for a Multicell
5. or IE identifier is inconsistent (i.e. missing mandatory
field, Encryption Information, Classmark Information 1 or
2, or Cell Identifier (Serving cell));
6. or erroneous IE contents (Encryption Information);
7. or only one among OIEs “Group Call Reference” and
“Talker Flag” ist present4th May 2007 at 12:47 #47173PixGuest
I can’t post my answer…4th May 2007 at 12:49 #47174PixGuest
By comparing the HO REQUIRED, HO REQUEST and HO COMMAND (and more) on each side, you should be able to detect exactly where is located your problem.
As for the timer expiry : which timer ? If you know which timer is expiring, you will know which message the MSC or BSC is waiting and not receiving. And you’ll know exactly what is going wrong.
External HO problems are very interesting to solve, because you must work with QoS, OMC and NSS people.5th May 2007 at 10:48 #47175IndranilGuest
Pls clarify the point
” or only one among OIEs “Group Call Reference” and
“Talker Flag” ist present” as it is not clear to me.
I am waiting for ur reply.
Cheers//5th May 2007 at 11:05 #47176PixGuest
i think it is in regards with “group calls”, which i doubt is widely used…7th May 2007 at 06:54 #47177Rajiv GujralGuest
If u can explain me from where in can check “invalid data rate” or “Cell identifier for target cell is not present for a Multicell
BSS”. In trace its only “Timer Expired” im getting and no other info(no details regarding which timer is, and on which end it is expiring). Also plz let me know from where will i start to solve this problem.9th May 2007 at 09:29 #47178TomarGuest
Hi Rajiv Gujral,
Please check message flows for your vendor. You could find witch timer is expired. I saw sometimes, that for Siemens equipment, if expires timer T7, there is problem with wrong definition of CGI in source/target BSC/MSC. It is possible to see in counters.
That my recommendation: At firs check if there are right definitions of handovers. Not only in BSC (target cells), but also in MSC (outer cells) in both directions.
BR Tomar9th May 2007 at 17:06 #47179pixGuest
yes, exactly, check the message flows, for outgoing HO (for the serving BSC) and incoming HO (for the target BSC).
You can find the message associated to which timer.
In the same way, you can associate QoS Counters to the message flow. Check where is the discrepancy in the QoS counters, and you’ll see exactly which message is missing.
That will lead you to the equipment which is not performing its job correcly (and which wasn’t configured properly 🙂 )7th June 2007 at 10:44 #47180JICGuest
In our network we have a problem with inter BSC handovers, we tried to do TEMs drives and we have isolated 1 BSCs which is giving us inter BSC Handover problems. Iam getting T200 expiry18th September 2008 at 13:39 #47181EmmanuelGuest
We recently integrated an iBSC to an existing one. The vendor is ZTE, we defined external cells to the new BSC and they are handing over to it quite well, but the iBSC is not handing over to these cells.
Can anyone please help me in resolving this issue as it is resulting to high drop calls and even bad speech quality as the MS while driving cannot handover to the adjacent cells?
Thanks for your suggestions.
Emmanuel.18th September 2008 at 17:44 #47182pixGuest
if external cells are correctly defined, then it’s a mismatch between the BSC and the MSC.
ZTE -> external cells is not working, it means:
1/ either the iBSC does not manage to “contact” these cells -> HO COMMAND is not sent to the MS. HO is not triggered, there is no HO failure.
2/ the iBSC understands those cells are neighbors, a HO CMD is sent to the MS, but the MS cannot access the external cells. HO FAILURE occurs.
Which case is it ?
Case 1 i suppose ?
therefore you should perform an A INTERFACE trace. Do you see a HO REQUIRED from iBSC to MSC ?
do you see a HO REQUEST from MSC to target BSC ?
and so on…
find where is the “missing” message. If the HO REQUIRED is missing, it means the problem is in the iBSC.
if the HO REQUEST is missing, the problem lies in the MSC.
Initial check, before traces:
in OMCR ZTE, the external cells are defined
in MSC, the neighbor cells of iBSC are well defined.
Pix18th September 2008 at 20:00 #47183EmmanuelGuest
Thanks you very much for the suggestions.
The scenario is case 1.
External cells are defined in both BSCs and the MSC as neighbours.
I did dedicated mode drive test with the call originated from the test site while the A interface signaling trace was runnnig. We will analyze the log file and I will update this forum on findings.
Thanks once again for the support.18th September 2008 at 20:09 #47184pixGuest
ok, thanks 🙂19th September 2008 at 13:39 #47185EmmanuelGuest
The result of the trace shows that there is no “HO required” message from the iBSC to MSC, meaning the issue is the iBSC…..I am a little bit stuck here.
Please let me know the next step.
Thanks a lot.