abase to retrieve the level of QoS to apply (QCI = 1) and transmits the DIAMETER RAR (Re-Auth- Request) message to the PGW entity containing the characteristics of the stream to establish. VoLTE and ViLTE 11) The PGW entity sends to the SGW entity the GTPv2-C CREATE BEARER REQUEST message containing the TEID identifier of the S5 bearer that the SGW entity will need to use in the GTP-U header when sending traffic to the PGW entity. 12) The SGW entity sends to the MME entity the GTPv2-C CREATE BEARER REQUEST message containing the TEID identifier of the S1 bearer that the eNB entity will need to use in the GTP-U header while sending traffic to the SGW entity. 13) The MME entity sends to the mobile the ESM ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message carried by the S1-AP E-RAB SETUP REQUEST message on the S1-MME interface and by the RRC ConnectionReconfiguration message on the LTE-Uu interface. The S1-AP E-RAB SETUP REQUEST message contains the TEID identifier that the MME entity has received from the SGW entity. The RRC ConnectionReconfiguration message contains the logical channel identifier (LCID) of the dedicated bearer. 14) The mobile responds to the MME entity by the ESM ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message carried by the RRC ConnectionReconfigurationComplete message on the LTE-Uu interface and by the S1-AP E-RAB SETUP RESPONSE message on the S1-MME interface. The S1-AP E-RAB SETUP RESPONSE message contains the TEID identifier of the S1 bearer that the SGW entity will need to use in the GTP-U header when it sends traffic to the eNB entity. 15) The MME entity responds to the SGW entity by the GTPv2-C CREATE BEARER RESPONSE message containing the TEID identifier that the MME entity has received from the eNB entity. 16) The SGW entity responds to the PGW entity with the C-GTPv2 CREATE BEARER RESPONSE message containing the TEID identifier of the S5 bearer that PGW entity will need to use in the GTP-U header when it sends traffic to the SGW entity. Basic Procedures The dedicated bearer has