CFN

Connection Frame Number

Radio Access Network →
Introduced in R99

CFN is a 12-bit counter used in UMTS to number radio frames, providing a common time reference between the Node B and RNC for synchronization across the UTRAN interface.

Category
Radio Access Network
Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
14 specs
CFN Description Purpose Related Classification Detected Changes Specifications

Description

The Connection Frame Number (CFN) is a fundamental synchronization mechanism within the UMTS Radio Access Network (UTRAN), specifically for Dedicated Channels (DCH). It is a 12-bit counter that cycles from 0 to 4095, uniquely numbering each 10 ms radio frame associated with a specific transport channel connection. The CFN is assigned by the Radio Network Controller (RNC) when a radio link is established and is communicated to the User Equipment (UE) and the Node B. Its primary role is to create a shared, unambiguous time reference for the duration of a connection, which is essential because the RNC and Node B may have independent system frame number (SFN) timelines.

Architecturally, the CFN operates at the Transport Channel level, sitting between the MAC layer and the physical layer. The RNC maps the CFN to the Node B's SFN at the point of transmission, a process defined by the Frame Offset and Chip Offset parameters. This mapping ensures that data blocks, scheduled for transmission by the RNC, are correctly aligned with the Node B's physical radio frame structure. The CFN is carried in key signaling messages over the Iub and Iur interfaces, such as in the Radio Link Setup procedure and within Frame Protocol (FP) data frames, to maintain alignment between these network elements.

In operation, the CFN governs several critical procedures. It is used for the timing of compressed mode patterns, where transmission gaps are scheduled based on the CFN. During soft handover, the CFN allows the RNC to coordinate the identical transmission of data from multiple Node Bs to the UE, ensuring macro-diversity combining can occur correctly. It also plays a vital role in synchronization procedures (e.g., radio link synchronization) and in the calculation of timing adjustments for data arrival at the Node B. Without the CFN, coordinating time-sensitive operations across the distributed UTRAN architecture would be significantly more complex and error-prone.

Purpose & Motivation

The CFN was introduced to solve the fundamental problem of time coordination between the controlling RNC and the radio transmission point, the Node B, in the asynchronous UTRAN architecture. In GSM, timing was more centralized via the Base Station Controller (BSC). However, UMTS introduced a more distributed, packet-oriented RAN where the RNC and Node B could have independent clock sources. This created a need for a connection-specific timing reference that was decoupled from the absolute cell timing (SFN).

Prior to CFN, there was no standardized method to ensure that data blocks sent from the RNC would be transmitted by the Node B at the correct instant relative to the radio interface timing. The CFN provides this abstraction layer. It allows the RNC to schedule and manage data transfer (including handover and power control commands) using a simple, predictable counter that is then locally mapped by each Node B to its own SFN timeline. This solves issues of timing drift and misalignment between network elements.

Its creation was motivated by the requirements for advanced UMTS features like soft handover and compressed mode. For soft handover, the same data must be transmitted from multiple cells at precisely the same time for the UE to combine them. The CFN, common across all radio links in the active set, provides this precise coordination point. For compressed mode, which creates gaps for inter-frequency or inter-system measurements, the pattern is defined relative to the CFN, ensuring the UE and network agree on when these transmission gaps will occur, regardless of the underlying cell's SFN.

Classification

Specific typesTGCFN
Related approachesSFN

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change

In Release 16, the CFN function itself was not directly modified; instead, the release focused on ensuring consistent terminology by adding new general abbreviations to the foundational terms and definitions document. This update was part of a broader effort to prevent inconsistent use of terminology across all 3GPP specifications. The change ensures that all technical documents use standardized terms for core network concepts like Connection Admission Control (CAC) and connection modes.

  • Add new general abbreviations MCC Note: CR cover sheet wrongly shows CR number as "1118". TS 21.905CR0118

Explore further

Broader topics and technologies where CFN plays a role.

Defining Specifications

3GPP specifications that define or reference CFN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 25.123 vj00 Radio Resource Management for TDD Rel-19
TS 25.133 vj00 UTRAN RRM Requirements for FDD Rel-19
TS 25.212 vj00 UTRA FDD Layer 1 Multiplexing & Channel Coding Rel-19
TS 25.222 vj00 UTRA TDD Multiplexing & Channel Coding Rel-19
TS 25.225 vj00 UTRA TDD Physical Layer Measurements Rel-19
TS 25.402 vj00 UTRAN Synchronisation Mechanisms Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TS 25.425 vj00 UTRAN Iur Interface User Plane Protocols Rel-19
TS 25.427 vj00 UTRAN Iub/Iur User Plane Protocols Rel-19
TS 25.433 vj00 Node B Application Part (NBAP) Protocol Rel-19
TS 25.435 vj00 UTRAN Iub Interface User Plane Protocols Rel-19
TS 25.706 vd00 Downlink Enhancements for UMTS Study Rel-13
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19