 6) The NAS signaling security setting is enabled by the MME entity sending the EMM SECURITY MODE COMMAND message controlled with the integrity key IKNAS. This message contains algorithms to derive the KASME key. The mobile derives the KASME key to generate the CKNAS, IKNAS and KeNB keys and checks the integrity of the EMM SECURITY MODE COMMAND message. 7) The mobile responds with the EMM SECURITY MODE COMPLETE message encrypted with the CKNAS key and controlled with integrity key IKNAS. After the mutual authentication phase and the security of NAS messages, the MME entity registers the mobile with the HSS entity. 8) The MME entity sends the DIAMETER Update-Location-Request (ULR) message to the HSS entity to register the mobile and obtain its service profile. The HSS entity records the identity of the MME entity which attached the mobile and the identity of the TAI location area. 9) The HSS entity responds to the MME entity with the DIAMETER Update-Location-Answer (ULA) message that contains the profile of the mobile: - the authorized access point names (APN); - the characteristics of quality of service (QOS) for each default bearer that must be established. The MME entity selects the serving gateway (SGW) entity in its group and the PDN gateway (PGW) entity from a domain name server (DNS) resolution of the APN. 10) The MME entity sends the GTPv2-C CREATE SESSION REQUEST message to create a context at the SGW entity. The GTPv2-C CREATE SESSION REQUEST message contains the IP address of the PGW entity, the APN and the default bearer profile. Basic Procedures 11) The SGW entity sends the GTPv2-C CREATE SESSION REQUEST message to create a context at the PGW entity. The GTPv2-C CREATE SESSION REQUEST message contains the tunnel endpoint identifier (TEID) that the PGW entity will use at the GPRS tunneling protocol user plane (GTP-U) level for the S5 bearer. 12) The PGW entity sends to the policy and charging rules function (PCRF) the DIAMETER Credit-Control-Request (CCR) message for authorization to open the default b