name: TRACKING AREA UPDATE REQUEST
full_form: Tracking Area Update Request Message
context: The use of ciphering in a network is an operator option subject to MME configuration. When operation of the network without ciphering is configured, the MME shall indicate the use of "null ciphering algorithm" EEA0 (see clauseÂ 9.9.3.23) in the current security context for all UEs. For setting the security header type in outbound NAS messages, the UE and the MME shall apply the same rules irrespective of whether the "null ciphering algorithm" or any other ciphering algorithm is indicated in the security context.
  When the UE establishes a new NAS signalling connection, it shall send the initial NAS message
  -	partially ciphered, if it is a CONTROL PLANE SERVICE REQUEST message including an ESM message container information element or a NAS message container information element; and
  -	unciphered, if it is any other initial NAS message.
  The UE shall partially cipher the CONTROL PLANE SERVICE REQUEST message by ciphering the value part of the ESM message container IE or the value part of the NAS message container, using the ciphering algorithm of the current EPS security context.
  The UE shall send the ATTACH REQUEST message always unciphered.
  The UE shall send the TRACKING AREA UPDATE REQUEST message always unciphered.
  Except for the CONTROL PLANE SERVICE REQUEST message including an ESM message container information element or a NAS message container information element, the UE shall start the ciphering and deciphering of NAS messages when the secure exchange of NAS messages has been established for a NAS signalling connection. From this time onward, unless explicitly defined, the UE shall send all NAS messages ciphered until the NAS signalling connection is released, or the UE performs intersystem handover to A/Gb mode or Iu mode.
  The MME shall start ciphering and deciphering of NAS messages as described in clauseÂ 4.4.2.3. From this time onward, except for the SECURITY MODE COMMAND message, the MME shall send all NAS messages ciphered until the NAS signalling connection is released, or the UE performs intersystem handover to A/Gb mode or Iu mode.
  Once the encryption of NAS messages has been started between the MME and the UE, the receiver shall discard the unciphered NAS messages which shall have been ciphered according to the rules described in this specification. The MME shall discard any CONTROL PLANE SERVICE REQUEST message including an ESM message container information element or a NAS message container information element which has not been partially ciphered according to the rules described above.
  If the "null ciphering algorithm" EEA0 has been selected as a ciphering algorithm, the NAS messages with the security header indicating ciphering are regarded as ciphered.
  Details of ciphering and deciphering of NAS signalling messages are specified in 3GPPÂ TSÂ 33.401Â [19].
description: This message is sent by the UE to update its tracking area.
explanation: Categorized as a Message because it is used for communication between network components.
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,B-Network Function,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Device,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Message,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Device,O,O,O,B-Message,I-Message,O,O,O,O,B-Device,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,B-Network Function,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,B-Mode,I-Mode,O,B-Interface,O,O,B-Network Function,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,B-Mode,I-Mode,O,B-Interface,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,B-Network Function,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O
biotag_Description: O,O,O,O,O,O,B-Device,O,O,O,O,O