name: CFN
full_form: Connection Frame Number (counter). CFN is the frame counter used for the L2/transport channel synchronisation between UE and UTRAN. A CFN value is associated to each TBS and it is passed together with it through the MAC-L1 SAP. CFN provides a common frame reference (at L2) to be used e.g. for synchronised transport channel reconfiguration (seeÂ TS 25.423 [2]Â and TS 25.433 [3]).
context: [FDD - Based on the received DOFFFDD and the SFN of the cell in which the UE is source, the UE can initialise the CFN with the value given by formula (9.4): CFN = (SFN - ((DOFFFDD * 512) div 38400)) mod 256 (9.4) This formula gives the CFN of the downlink DPCH frame or of the F-DPCH frame which starts at the same time as or which starts during the PCCPCH frame with the given SFN.] [TDD - Based on the received DOFFTDD, the UE can initialised the CFN with the value given by formula (9.5): CFN = (SFN- DOFFTDD) mod 256 (9.5)] After the initialisation, the CFN in the UE is increased (mod 256) by 1 every frame. [TDD - Note that for all common and shared channels CFN = SFN mod 256 even during CELL_DCH state.]
description: The Connection Frame Number (CFN) is a counter used for L2/transport channel synchronization between the User Equipment (UE) and the UTRAN. It provides a common frame reference at the L2 layer, enabling synchronized transport channel reconfiguration. The CFN value is associated with each Transport Block Size (TBS) and passed through the MAC-L1 SAP. The UE initializes the CFN based on the received DOFFFDD and SFN of the cell, using formulas specific to FDD or TDD modes.
explanation: CFN is classified as a Parameter because it refers to a configuration setting used in the synchronization process between the UE and UTRAN. The context highlights its role in providing a common frame reference for L2/transport channel synchronization and its association with each TBS, indicating that CFN serves as a specific value or setting within the network.
section_title: 9.3.1	UE changes from CELL_FACH/PCH state to CELL_DCH state: 1 RL
biotag_Context: O,O,O,O,O,O,B-Parameter,O,O,B-Technology,O,O,O,O,O,O,B-Device,O,O,O,B-Device,O,O,O,B-Parameter,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-Parameter,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Technology,O,O,O,O,O,O
biotag_Description: O,O,B-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,B-Parameter,O,B-Technology,O,O,O,O,O,O,O,B-Technology,O,B-Technology,O