 MME entity forwards to the new SGW entity in the message GTPv2-C MODIFY BEARER REQUEST containing the ECGI identity of the cell and 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. Source Target Former Former S1-AP HANDOVER NOTIFY GTPv2-C FORWARD RELOCATION COMPLETE NOTIFICATION GTPv2-C FORWARD RELOCATION COMPLETE ACKNOWLEDGE GTPv2-C MODIFY BEARER REQUEST GTPv2-CMODIFY BEARER REQUEST GTPv2-C MODIFY BEARER RESPONSE GTPv2-C MODIFY BEARER RESPONSE GTP-U EM (S1 Bearer) GTP-U EM (Temporary Bearer) GTP-U EM (Temporary Bearer) GTP-U EM (Temporary Bearer) Radio Bearer S1 Bearer S5 Bearer S1-AP UE CONTEXT RELEASE REQUEST S1-AP UE CONTEXT RELEASE COMPLETE GTPv2-C DELETE INDIRECT FORWARDING TUNNEL REQUEST GTPv2-C DELETE INDIRECT FORWARDING TUNNEL RESPONSE GTPv2-C DELETE SESSION REQUEST GTPv2-C DELETE SESSION RESPONSE GTPv2-C DELETE INDIRECT FORWARDING TUNNEL REQUEST GTPv2-C DELETE INDIRECT FORWARDING TUNNEL RESPONSE Figure 7.9. Handover based on S1 with relocation completion phase 5) The new SGW entity forwards the ECGI identifier of the cell to the PGW entity in the message GTPv2-C MODIFY BEARER REQUEST. The PGW entity transfers the ECGI identifier of the cell to the PCRF entity in the DIAMETER RRC message. Handover The PCRF entity responds to the PGW entity with the DIAMETER CCA message to acknowledge the request. 6) The PGW entity responds to the new SGW entity with the message GTPv2-C MODIFY BEARER RESPONSE to acknowledge the request. 7) The new SGW entity responds to the new MME entity with the message GTPv2-C MODIFY BEARER RESPONSE to acknowledge the request. 8) The target eNB entity transmits to the mobile the traffic received from the source eNB entity by the temporary bearer until it receives the message GTP-U EM of the new SGW entity, from which the traffic will be received directly by the S1 bearer. 9) The release of the context of the mobile at the source eNB entity is triggered by the former MME entity by sending the messa