 2) The former MME entity selects a new MME entity and transmits the message GTPv2-C FORWARD RELOCATION REQUEST containing the following information: - the IP address of the PGW entity; - the TEID identifier relative to the S5 bearer that the new SGW entity will use in the GTP-U header when it sends traffic to the PGW entity. 3) The new MME decides to relocate the SGW entity and passes to the new SGW entity the message GTPv2-C CREATE SESSION REQUEST containing the information received. Source Target Former Former Radio Bearer S1 Bearer S5 Bearer S1-AP HANDOVER REQUIRED GTPv2-C FORWARD RELOCATION REQUEST GTPv2-C CREATE SESSION REQUEST GTPv2-C CREATE SESSION REQUEST S1-AP HANDOVER REQUEST S1-AP HANDOVER REQUEST ACK GTPv2-C CREATE INDIRECT FORWARDING TUNNEL REQUEST GTPv2-C CREATE INDIRECT FORWARDING TUNNEL RESPONSE GTPv2-C FORWARD RELOCATION RESPONSE GTPv2-C CREATE INDIRECT FORWARDING TUNNEL REQUEST GTPv2-C CREATE INDIRECT FORWARDING TUNNEL RESPONSE S1-AP HANDOVER COMMAND Figure 7.7. Handover based on S1 with relocation preparation phase Handover 4) The new SGW entity responds with the message GTPv2-C CREATE SESSION REQUEST containing the TEID identifier of the S1bearer that the target eNB entity will use in the GTP-U header when it sends traffic to the new SGW entity. 5) The new MME entity transmits to the target eNB entity the message S1-AP HANDOVER REQUEST to perform the reservation of resources. 6) The target eNB entity responds to the new MME entity with the message S1-AP HANDOVER REQUEST ACK containing the following information: - the TEID identifier of the temporary bearer that the new SGW entity will use in the GTP-U header when it sends traffic to the target eNB entity; - the TEID identifier of the S1 bearer that the new SGW entity will use in the GTP-U header when it sends traffic to the target eNB entity; - the technical characteristics of the radio interface in the information element handover command. 7) The new MME entity forwards the TEID identifier relating to the temporary bearer to the SGW entity i