name: TAU
full_form: Tracking Area Update
context: Before the UE can initiate the TAU procedure, the UE needs to transition to ECM-CONNECTED state. The UE shall use the current EPS security context to protect the TAU Request and include the corresponding GUTI and eKSI value. The TAU Request shall be integrity-protected, but not confidentiality-protected. UE shall use the current EPS security context algorithms to protect the TAU Request message. For the case that this security context is non-current in the MME, the rules in clause 6.4 apply. If the "active flag" is set in the TAU request message or the MME chooses to establish radio bearers when there is pending downlink UP data or pending downlink signalling, radio bearers will be established as part of the TAU procedure and a KeNB derivation is necessary.If there was no subsequent NAS SMC, the uplink NAS COUNTof the TAU request message sent from the UE to the MME is used as freshness parameter in the KeNB derivation using the KDF as specified in clause A.3. The TAU request shall be
description: The Tracking Area Update (TAU) procedure is a process in the E-UTRAN network where a UE updates its tracking area to inform the MME of its current location. This procedure involves the UE sending a TAU Request message to the MME, which includes the UE's GUTI and eKSI value, and is protected by the EPS security context.
explanation: The provided text explicitly describes the steps involved in the TAU procedure, including the UE sending a TAU Request message to the MME with specific information like GUTI and eKSI. This detailed description of a defined process within the E-UTRAN network justifies classifying TAU as a Procedure.
section_title: 7.2.7	Key handling for the TAU procedure when registered in E-UTRAN
biotag_Context: O,O,B-Device,O,O,O,B-Procedure,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Parameter,O,B-Parameter,O,O,B-Procedure,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network,O,O,O,O,O,O,B-Procedure,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,O,O,O,B-Procedure,O,O,O,O,B-Network Function,O,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,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,B-Procedure,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Procedure,O,O,O
biotag_Description: O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Network,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Device,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,O,O,O,B-Network,O,O