top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

LTE to 3G IRAT handover fails in preparation phase

+1 vote
1,482 views

Newly integrated 3rd carrier is facing IRAT handover failure with reason "unknown-targetID" and "Failure In Target EPC/eNB Or Target System". Other carriers of same enodeB are doing successful handover with the same WCDMA cell. Sometimes for the affected cell, handover is successful.

Thanks in advance,
Bijit

posted Feb 21, 2016 by Bijit Deb

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button
We have the same problem with IRAT HO...
commented Jul 20, 2017 by Radoslav Balev

Similar Questions
0 votes
LTE: What are actions taken at source eNodeB or MME in case of partial resource allocation as part of HO procedure?

When target eNodeB is not able to allocate resource for all the bearers which comes as part of Handover Request message, it sends handover request ack with partial success since "E-RABs Failed to Setup List" is present in HOReqAck message.
What MME or source eNodeB does in that case ? Does any action taken by MME for the E-RABs which failed to setup at target eNodeB or some other actions taken ?

+1 vote
LTE HO : Why two MME UE S1AP IDs present within the S1-AP HO Request message ?

I found two MME UE S1-AP IDs i.e. MME UE S1AP ID (Mandatory) and MME UE S1AP ID 2 (optional).
I got why mandatory one is present but what's use of optional one.

Can someone please explain it ?

+2 votes
LTE HO: Is it possible after successful resource allocation at target eNodeB, source eNodeB sends HO Cancel ?

Is it possible, source eNodeB has received "handover command" message from MME and now it want to cancel handover procedure ?
What could be the possible reasons when source eNodeB want to cancel ongoing handover procedure ?

+1 vote
LTE: What target eNodeB does in case it receives "Path switch request failure" from MME ?

As one failure message is defined in specification for the path switch procedure then what would be the behavior of target eNodeB after getting failure response from the MME ? Action would be vendor specific or standard action has been defined for this scenario ?

...