name: UARFCN
full_form: UTRA Absolute Radio Frequency Channel Number
context: To support USTS in Iur Interface, the followings will be done. And these are very similar to Iubâs. - SRNC should indicate to DRNC whether or not the UE is in USTS mode. Therefore, USTS indicator should be added in RNSAP messages, RADIO LINK SETUP REQUEST and RADIO LINK RECONFIGURATION PREPARE. - To let SRNC know whether or not DRNCâs Node B supports USTS, USTS Support Indicator should be added in RNSAP messages, RADIO LINK SETUP RESPONSE (in neighbouring cell informaiton). - To transmit the of DRNCâs node B to SRNC, should be added in RNSAP messages, RADIO LINK SETUP RESPONSE in the case of set up with USTS and RADIO LINK RECONFIGURATION READY in the case of mode change from non-USTS to USTS when USTS indicator has been received by DRNC. - USTS Scrambling Code and USTS Scrambling Code Offset will be sent to DRNC from SRNC through RADIO LINK SETUP REQUEST and RADIO LINK ADDITION REQUEST in the case of handover - To send the USTS Scrambling Code assigned by DRNC to SRNC, USTS Scrambling
description: The UTRA Absolute Radio Frequency Channel Number (UARFCN) is a parameter used to define the radio frequency channel numbers for specific bands in the Universal Terrestrial Radio Access Network (UTRAN). In this context, a new range of UARFCN values is defined for Band X, covering 2x60 MHz and added after the UARFCN numbers defined for Band VIII. The resulting parameters to define the Band X UARFCN range are specified in tables within the 3GPP TS 25.806 document.
explanation: The context provided highlights the definition of a new UARFCN range for Band X, including specific details about the frequency coverage and the addition of new UARFCN numbers after those defined for Band VIII. This information is used to classify UARFCN as a parameter, given its role in specifying radio frequency channel numbers for particular bands within the UTRAN.
section_title: 8.3.2.	Definition of a new UARFCN range for Band X
biotag_Context: O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,B-Device,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,I-Network Function,O,O,B-Protocol,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,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-Protocol,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,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,B-Network Function,O,O,B-Protocol,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O