Connection Frame Number

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.

Key Features

• 12-bit counter providing a connection-specific frame numbering (0-4095)
• Serves as a common time reference between RNC and Node B, independent of cell SFN
• Essential for timing coordination during soft handover procedures
• Used to schedule and define compressed mode transmission patterns
• Carried within Frame Protocol and NBAP/RNSAP signaling messages
• Mapped to the Node B's SFN via Frame Offset and Chip Offset parameters

Evolution Across Releases

Defining Specifications