top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

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

+1 vote

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 ?

posted Nov 20, 2016 by Neelam

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

In case of failure response from MME, eNodeB can initiate UE context release procedure towards MME.

answer Nov 21, 2016 by Vimal Kumar Mishra
Hi Vimal,
-> With X2 HO,Target has accepted all the e-rabs and even UE has sent RCR complete towards TeNb.
-> At this point TeNb has sent PATH SWITCH REQ towards MME and received failure.
-> How to handle this case when all e-rabs are admitted at target (after RCR complete we usually send UE context release from target to source).
-> Does MME need to handle this case and trigger detach procedure with target for UE.
Similar Questions
+2 votes

I have a use case in which
ENodeB sends "S1-Setup Request" message to MME. TAC within the request is unknown for MME but at least one PLMN from the list of broadcasted PLMN is known by MME. How MME shall react ?

+3 votes

What MME shall perform when receiving S1 path switch request (changing tac and lac for the UE) after a NAS tau request. Shall MME respond to UE with TAU reject (which cause code ) or not ?

0 votes

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 ?

+2 votes

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

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 ?