name: LTE-Uu
full_form: LTE Uu Interface
context: The non-access stratum (NAS) described in the present document forms the highest stratum of the control plane between UE and MME at the radio interface (reference point "LTE-Uu"; see 3GPPÂ TSÂ 23.401Â [10]).
  Main functions of the protocols that are part of the NAS are:
  -	the support of mobility of the user equipment (UE); and
  -	the support of session management procedures to establish and maintain IP connectivity between the UE and a packet data network gateway (PDN GW).
  NAS security is an additional function of the NAS providing services to the NAS protocols, e.g. integrity protection and ciphering of NAS signalling messages.
  For the support of the above functions, the following procedures are supplied within this specification:
  -	elementary procedures for EPS mobility management in clauseÂ 5; and
  -	elementary procedures for EPS session management in clauseÂ 6.
  Complete NAS transactions consist of specific sequences of elementary procedures. Examples of such specific sequences can be found in 3GPPÂ TSÂ 23.401Â [10].
  The NAS for EPS follows the protocol architecture model for layerÂ 3 as described in 3GPPÂ TSÂ 24.007Â [12]; however, due to the objective of EPS to provide the subscriber with a "ready-to-use" IP connectivity and an "always-on" experience, the protocol supports a linkage between mobility management and session management procedures during the attach procedure (see clauseÂ 4.2).
  Signalling procedures for the control of NAS security are described as part of the EPS mobility management in clauseÂ 5. In addition to that, principles for the handing of EPS security contexts and for the activation of ciphering and integrity protection, when a NAS signalling connection is established, are provided in clauseÂ 4.4.
description: The LTE-Uu interface is the radio interface between UE and MME, where NAS signaling takes place.
explanation: Categorized as an Interface since it enables communication between network components.
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,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,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,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,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,B-Network,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,O,B-Protocol,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,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,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,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,B-Interface,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O