tion-Request) message. 5) The PCRF entity requests the PGW entity to release of dedicated bearer in the DIAMETER RAR message. 6) The PGW entity acknowledges the DIAMETER RAR request by the RAR DIAMETER RAA message. 7) The PCRF entity acknowledges the DIAMETER STR request by the DIAMETER STA (Answer-Session-Termination) message. VoLTE and ViLTE 8), 9), 10) Alice's UA entity (or Bob's) receives the 200 OK response to the BYE request from the domain homeB net (or homeA net). 11) Upon receipt of the DIAMETER RAR message, the PGW entity initiates the removal of dedicated bearer by the GTPv2 C-BEARER DELETE REQUEST message. 12) The SGW entity transmits the GTPv2 C-BEARER DELETE REQUEST message to continue the dedicated bearer release request. 13) The MME entity sends the ESM DEACTIVATE EPS BEARER CONTEXT REQUEST message to Alice's UA entity (or Bob's) to inform about the deactivation of the dedicated bearer. The ESM DEACTIVATE EPS BEARER CONTEXT REQUEST message is carried by the RRC ConnectionReconfiguration message on the radio interface LTE-Uu and the S1-AP E-RAB RELEASE COMMAND message on the S1-MME interface. 14) The UA entity confirms the deactivation of the dedicated bearer in the ESM DEACTIVATE EPS BEARER CONTEXT ACCEPT message. The ESM DEACTIVATE EPS BEARER CONTEXT ACCEPT message is carried by the RRC ConnectionReconfigurationComplete message on the radio interface LTE-Uu and the S1-AP E-RAB RELEASE RESPONSE message on the S1-MME interface. 15) The MME entity responds to the SGW entity with the GTPv2-C DELETE BEARER RESPONSE message that acknowledges the release request of the dedicated bearer. 16) The SGW entity responds to the PGW entity with the GTPv2-C DELETE BEARER RESPONSE message that acknowledges the release request of the dedicated bearer. 3.6.2. Received side The procedure for clearing the VoLTE session initiated by the UA entity, at the received side, is described in Figure 3.8. Basic Procedures 1), 2), 3) Bob's UA entity (or Alice's) receives the BYE request, from domain homeA. net (or homeB net), e