name: NAI
full_form: Network Access Identifier
context: in EAP SIM [51] and EAP AKA as appropriate Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name. The result will be a root NAI of the form: "0<IMSI>@wlan.mnc<MNC>.mcc<MCC>.3gppnetwork.org", for EAP AKA authentication and "1<IMSI>@wlan.mnc<MNC>.mcc<MCC>.3gppnetwork.org", for EAP SIM authentication Using the example above, for EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the root NAI then takes the form 0234150999999999@wlan.mnc015.mcc234.3gppnetwork.org. Decorated NAI: takes the form of a NAI and shall have the form 'homerealm!username@otherrealm' . realm part: consists of 'otherrealm' is the realm built using the PLMN ID (visitedMCC + visited MNC) of the PLMN selected as a result of WLAN PLMN selection. 'Homerealm' is the realm as specified using the HPLMN ID ('homeMCC' + 'homeMNC)'. The username part format of the Root NAI shall comply with IETF RFC 4187 when EAP AKA authentication is used and with IETF RFC 4186 when EAP SIM
description: The Network Access Identifier (NAI) is a parameter used to identify the end-user in various telecommunications contexts, including EAP SIM and EAP AKA authentication. It is constructed from the IMSI, MCC, and MNC, and can take different forms such as root NAI or decorated NAI.
explanation: The text describes NAI as a parameter used for identification within specific telecommunication processes like EAP authentication.
section_title: 5.3.1.2.2Representation of the Identity of the End-User through his Keys
biotag_Context: O,B-Protocol,B-Device,O,O,B-Protocol,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Protocol,B-Protocol,O,O,O,O,B-Protocol,B-Device,O,O,O,O,O,O,B-Protocol,B-Protocol,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Network,B-Network,O,O,O,O,O,O,O,O,O,B-Parameter,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Organization,B-Specification,O,O,B-Protocol,B-Protocol,O,O,O,O,O,B-Organization,B-Specification,O,O,B-Protocol,B-Device
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Device,O,B-Protocol,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O