name: IDNNS
full_form: Intra Domain NAS Node Selection
context: In R99/R4/R5, the uplink scheduling and rate control resides in the RNC. UE transmission can be controlled using DRAC and TFCS Restriction. The DRAC (Dynamic Resource Allocation Control) procedure is used by the network to dynamically control the allocation of resources on an uplink DCH. The method is based on statistical scheduling. In each TTI, the UE determines whether it can transmit or not based on the DRAC static parameters which have been determined by the RNC ("Transmission Time Validity" and "Time duration before retry"). DRAC parameters are broadcasted in SIB 10. The UE determines the most stringent DRAC parameters from the last received values from each cell of its active set. It also determines the allowed subset of TFCS according to the selected maximum bit rate value. Rules have been defined so that the UE always know which DRAC static parameters to use: in case several SIB10 messages from different cells are scheduled at the same time, the UE shall only listen to the
description: Intra Domain NAS Node Selection (IDNNS) is a procedure used in the Access Stratum to select a NAS node for routing purposes. It involves the transmission of a routing parameter with a fixed length of 10 bits, which contains the Network Resource Identifier (NRI) value, along with an indication of the identity from which the routing parameter is derived.
explanation: IDNNS is classified as a Procedure because it describes a specific sequence of operations involved in selecting a NAS node for routing purposes within the Access Stratum. The context highlights its role in the RRC INITIAL DIRECT TRANSFER message and the transmission of routing parameters, indicating a procedural aspect.
section_title: 6.1.4	Network Resource Identifier
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Procedure,O,B-Parameter,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,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Message,O,O,B-Device,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,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Network Function,I-Network Function,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-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O