earer. The PCRF entity compares the profile of the mobile with the rules defined for the network and stored in the subscription profile repository (SPR) database. 13) The PCRF entity responds to the PGW entity by a DIAMETER Credit-Control-Answer (CCA) message containing the rules to be applied to the default bearer (filter parameters and charging mode). 14) The PGW entity responds to the SGW entity by a GTPv2-C CREATE SESSION RESPONSE message which contains the following information: - the TEID identifier that the SGW entity will use at the GTP-U protocol level for the S5 bearer; - the mobile configuration (IP address of the mobile, IP address of its DNS server). 15) The SGW entity responds to the MME entity with a GTPv2-C CREATE SESSION RESPONSE which contains the following information: - the TEID identifier that the eNB entity will use at the GTP-U protocol level for the S1 bearer; - the mobile configuration. 16) The MME entity responds to the mobile with the EMM ATTACH ACCEPT message containing the following information: - the mobile configuration; - its GUTI temporary identity. 74 VoLTE and ViLTE The EMM ATTACH ACCEPT message carries the ESM ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. The EMM ATTACH ACCEPT message is carried by the S1-AP INITIAL CONTEXT SETUP REQUEST message on the S1-MME interface and by the RRC ConnectionReconfiguration message on the LTE-Uu radio interface. The S1-AP INITIAL CONTEXT SETUP REQUEST message allows for the creation of the mobile context at the eNB entity level and contains the following information: - the TEID identifier assigned by the SGW entity; - the QoS parameters; - the Kenb key derived from the KASME key. The eNB entity derives the key for creating the following keys: - the KRRCenc key for RRC message encryption; - the KRRCint key for RRC message integrity control; - the KUPenc key for traffic encryption. The RRC ConnectionReconfiguration message initializes mounting of the data radio bearer (DRB). 17) The eNB entity requests the mobile to secure the radio inte