name: RNTI
full_form: Radio Network Temporary Identity
context: The Iu UP protocol is located in the User plane of the Radio Network layer over the Iu interface: the Iu UP protocol layer. The Iu UP protocol is used to convey user data associated to Radio Access Bearers. One Iu UP protocol instance is associated to one RAB and one RAB only. If several RABs are established towards one given UE, then these RABs make use of several Iu UP protocol instances. In general, Iu UP protocol instances exist at Iu access point as defined in TS 25.410 [2] i.e. at CN and UTRAN. However, as described in TS 23.153 [13], if TrFO is possible and the Iu UP protocol instances operate in support mode the Iu UP protocol instance in CN may resume performing Iu UP specific functions or vanish completely during stable call states. In this case the partner peer entity actually interacting with the UTRAN Iu UP protocol instance (i.e. performing all Iu UP specific functions except UP initialisation) may either be located within another UTRAN or within a CN node that is not the
description: Radio Network Temporary Identity (RNTI) is a type of identifier used in UTRAN/GERAN Iu mode to identify User Equipment (UE) within the radio network. There are six types of RNTI, each serving different purposes such as identifying UE to Serving RNC/BSS, addressing UE/MS, and identifying UE to Drift RNC. The allocation and uniqueness of RNTI vary depending on its type and usage.
explanation: RNTI is classified as an Identifier because it is used to uniquely identify User Equipment within the radio network, as described in the context. The various types of RNTI (s-RNTI, d-RNTI, c-RNTI, u-RNTI, DSCH-RNTI, HS-DSCH RNTI, and E-DCH RNTI) serve distinct identification purposes within UTRAN/GERAN Iu mode.
section_title: 6.1.7	UE Identifiers
biotag_Context: O,B-Interface,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Interface,O,O,B-Interface,B-Protocol,O,O,O,B-Interface,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,B-Protocol,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,B-Protocol,O,O,O,O,B-Interface,B-Protocol,O,O,O,O,B-Interface,O,O,O,O,O,B-Specification,O,O,O,O,B-Network,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,B-Interface,B-Protocol,O,O,O,O,O,O,O,B-Interface,B-Protocol,O,O,O,B-Network,O,O,O,B-Interface,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,B-Interface,B-Protocol,O,O,O,O,O,B-Interface,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Network,O,O,O,B-Network,O,O,O,O,O
biotag_Description: B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,B-Mode,I-Mode,O,O,B-Device,I-Device,O,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-Device,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O