name: 3GPP TS 33.102
full_form: 3rd Generation Partnership Project Technical Specification 33.102
context: In an EPS authentication challenge, the UE shall check the authenticity of the core network by means of the AUTN parameter received in the AUTHENTICATION REQUEST message. This enables the UE to detect a false network.
  During an EPS authentication procedure, the UE may reject the core network due to an incorrect AUTN parameter (see 3GPPÂ TSÂ 33.401Â [19]). This parameter contains three possible causes for authentication failure:
  a)	MAC code failure:
  If the UE finds the MAC code (supplied by the core network in the AUTN parameter) to be invalid, the UE shall send an AUTHENTICATION FAILURE message to the network, with the EMM cause #20 "MAC failure". The UE shall then follow the procedure described in clauseÂ 5.4.2.7, itemÂ c.
  b)	Non-EPS authentication unacceptable:
  If the UE finds that the "separation bit" in the AMF field of AUTN supplied by the core network is 0, the UE shall send an AUTHENTICATION FAILURE message to the network, with the EMM cause #26 "non-EPS authentication unacceptable" (see clauseÂ 6.1.1 in 3GPPÂ TSÂ 33.401Â [19]). The UE shall then follow the procedure described in clauseÂ 5.4.2.7, item d.
  c)	SQN failure:
  If the UE finds the SQN (supplied by the core network in the AUTN parameter) to be out of range, the UE shall send an AUTHENTICATION FAILURE message to the network, with the EMM cause #21 "synch failure" and a re-synchronization token AUTS provided by the USIM (see 3GPPÂ TSÂ 33.102Â [18]). The UE shall then follow the procedure described in clauseÂ 5.4.2.7, itemÂ e.
  If the UE returns an AUTHENTICATION FAILURE message to the network, the UE shall delete any previously stored RAND and RES and shall stop timer T3416, if running.
  If the UE has a PDN connection for emergency bearer services established or is establishing such a PDN connection, additional UE requirements are specified in clauseÂ 5.4.2.7, under "for items c, d, e".
  If the UE is attached for access to RLOS and has a PDN connection for RLOS established or is establishing such a PDN connection, additional UE requirements are specified in clauseÂ 5.4.2.7, under "for items c, d, e".
description: The 3GPP TS 33.102 specification defines the security aspects of the EMM protocol and related functionality.
explanation: Categorized as a Specification because it is a formal document that describes specific technical details.
biotag_Context: O,O,B-Network,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Message,I-Message,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network,O,O,O,B-Device,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,B-Protocol,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Device,O,O,O,B-Message,I-Message,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Message,I-Message,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Device,O,O,O,B-Message,I-Message,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Message,I-Message,O,O,O,O,O,B-Device,O,O,O,O,O,B-Parameter,O,B-Message,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Service,O,O,O,B-Network,O,O,B-Service,O,O,O,O,O,O,B-Network,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Specification,I-Specification,I-Specification,O,O,O,O,O,O,O,B-Protocol,O,O,O,O