top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

LTE S1-AP handover : How does a source mme find out the target mme as part of MME relocation based handover ?

+5 votes

As part of S1-AP procedure with MME relocation, Handover Required message sent to source MME. Target eNodeBId is present within the handover required. How source MME figure out target cell is being served by XYZ MME and sends "Forward relocation Request" message to XYZ MME.

Please provide reference also if it is there ?

posted Feb 21, 2014 by Vimal Kumar Mishra

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
Source MME selects the target MME based on the target TAI and ENb  Identity received in Handover required message..(TAI information of target MME should be configured in source MME)..

1 Answer

+2 votes

The source eNB forwards the decision about HO to source MME by sending the "Handover Required" message.
In this message the target eNB identity and target TAI is shared.
If there is no direct connection (like over X2 interface) the target TAI is used by source MME to facilitate the selection of a suitable target MME. (Check second link)
If the TAI is served by other MME the Forward Relocation Request message to the target MME, basicly containing the information sent to source MME in "Handover Required" message, plus information about UE Context handled by source MME.

Check here for the whole Handover procedure here

The MME selection based on TAI is in my opinion the same as the one that has place during the Initial Attach, but in this case DNS req is performed by MME not eNB. Please check here

answer Mar 20, 2014 by Bart Barton
Thanks Bart, to share this valuable info as well as references.
My pleasure, always here to help
Similar Questions
+2 votes

In case of S1-handover with the MME relocation, source MME sends an information "Target Identification" to target MME.
What the target MME does by receiving TAC, when an enodeb can be identified uniquely by using combination of (PLMN + Macro/Home ENodeB) ?

Can someone tell me what the purpose behind to send TAC as part of Target Id IE ?

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 ?

+1 vote

In case of hub-and-spoke topology, X2 messaging can travel all the way back to an aggregation point, which may be co-located with EPC. In such scenario both X2 and S1 traverses same physical path (a.k.a X2 over S1). Please consider both Intra-MME and Inter-MME handover scenarios. Would X2 based handover in such a case yield advantage over S1 based handover. Thanks.

+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 ?

+4 votes

My email id is "". I am looking for successful S1-handover (with MME and SGW relocation) logs.

Thanks in advance.