EQUEST. 5) The 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 SGW entity. 6) The preparation phase ends when the MME entity sends to the source eNB entity the message S1-AP HANDOVER COMMAND containing the following information: - the TEID identifier of the temporary bearer that the source eNB entity will use in the GTP-U header when it sends traffic to the SGW entity; - the technical characteristics of the radio interface of the target eNB entity in the information element handover command. 7) The source eNB entity starts the execution phase by sending to the mobile the RRC ConnectionReconfiguration message containing the information element Handover Command. VoLTE and ViLTE 8) The source eNB entity transmits to the MME entity the sequence numbers of the PDCP protocol with the message SI-AP SN STATUS TRANSFER. 9) The MME entity forwards the sequence numbers to the target eNB entity in the message SI-AP MME STATUS TRANSFER. Incoming data that have not been acknowledged by the mobile which the target eNB entity will store until the mobile is able to receive are transmitted in the temporary bearer. 10) When the RRC connection is established between the mobile and the target eNB entity, the mobile transmits the message RRC ConnectionReconfigurationComplete, which will trigger the transfer of incoming data stored by the target eNB entity to the mobile. 11) The completion phase starts when the target eNB entity notifies the MME entity with the message S1-AP HANDOVER NOTIFY containing the ECGI identity of the cell. 12) The MME entity forwards to the SGW entity the message GTPv2-C MODIFY BEARER REQUEST containing the ECGI identity of the cell and the TEID identifier of the S1 bearer that the SGW entity will use in the GTP-U header when it sends traffic to the target eNB entity. 13) The SGW entity tr