n the message GTPv2-C CREATE INDIRECT FORWARDING TUNNEL REQUEST. 8) The new SGW entity acknowledges the creation of the temporary bearer by the message GTPv2-C CREATE INDIRECT FORWARDING TUNNEL RESPONSE containing the TEID identifier of the temporary bearer that the former SGW entity will use in the GTP-U header when it will send traffic to the new SGW entity. 9) The new MME entity responds to the former MME entity with the message GTPv2-C FORWARD RELOCATION REQUEST containing the following information: - the TEID identifier of the temporary bearer that the former SGW entity will use in the GTP-U header when it sends traffic to the new SGW entity; - the technical characteristics of the radio interface of the target eNB entity in the information element Handover Command. 10) The former MME entity forwards the TEID identifier relating to the temporary bearer to the former SGW entity in the message GTPv2-C CREATE INDIRECT FORWARDING TUNNEL REQUEST. 214 VoLTE and ViLTE 11) The former SGW entity acknowledges the creation of the temporary bearer with the message GTPv2-C CREATE INDIRECT FORWARDING TUNNEL RESPONSE containing the TEID identifier of the temporary bearer that the source eNB entity will use in the GTP-U header when it will send traffic to the former entity SGW. 12) The preparation phase ends when the former MME entity transmits to the source eNB entity the message S1-AP HANDOVER COMMAND containing the following information: - the TEID identifier from the temporary bearer that the source eNB entity will use in the GTP-U header when it sends traffic to the former SGW entity; - the technical characteristics of the radio interface of the target eNB entity in the information element handover command. 7.3.2.2. Execution phase The S1-based handover procedure with relocation of the MME and SGW entities is described in Figure 7.8 for the execution phase. Source Target Former Former RRC ConnectionReconfiguration S1-AP eNB STATUS TRANSFER GTPv2-C FORWARD ACCESS CONTEXT NOTIFICATION GTPv2-C FORWARD ACCESS CONTEXT ACKNOW