Description
The System Frame Number (SFN) is a fundamental timing parameter in cellular networks, serving as a modulo counter that uniquely identifies each radio frame within a cell's transmission timeline. In LTE, the SFN cycles from 0 to 1023, corresponding to a period of 10.24 seconds (1024 frames * 10 ms/frame). In 5G NR, two ranges are defined: the 10-bit SFN (0-1023) for fundamental timing and the 12-bit Hyper-SFN (H-SFN, 0-4095) for extended timing procedures, especially for IoT and reduced capability devices. The SFN is broadcast within the Master Information Block (MIB) on the Physical Broadcast Channel (PBCH). In LTE, the 8 most significant bits of the SFN are carried in the MIB, while the 2 least significant bits are derived from the PBCH decoding timing. In NR, the PBCH payload carries part of the SFN, and the full value is obtained by combining this with information from the PBCH's Demodulation Reference Signals (DM-RS) and the radio frame timing. The SFN is crucial for time-synchronized network operations. It determines the scheduling of System Information Blocks (SIBs), which are transmitted in specific radio frames and subframes according to formulas based on SFN. It governs paging occasions, where UEs wake up to check for pages only in frames where SFN mod T = T_Offset, with T being the paging cycle. For measurements, UEs use SFN to time-stamp measurement reports (e.g., for handover) and to synchronize discontinuous reception (DRX) cycles. In positioning protocols like LTE Positioning Protocol (LPP) and NR Positioning Protocol (NRPP), SFN is used as a common time reference for Observed Time Difference of Arrival (OTDOA) measurements. Essentially, the SFN provides a cell-specific 'clock' that aligns all UE and network activities within the cell's radio resource grid.
Purpose & Motivation
The SFN was introduced from the earliest 3GPP releases (R99) to provide a standardized, cell-level time reference, addressing the need for deterministic scheduling and synchronization in digital cellular systems. Prior analog systems lacked such a unified, broadcast timing counter, making coordinated channel access and power-saving mechanisms difficult. The SFN solves several critical problems: it enables efficient sleep modes (DRX/paging) by allowing UEs to predict exactly when to wake up based on a known cycle, drastically saving battery life. It allows for the periodic and predictable broadcasting of system information, ensuring all UEs can acquire vital network parameters without continuous monitoring. It provides a common timebase for handover measurements and reporting, ensuring the network can accurately compare measurements from different UEs or different times. Furthermore, it supports advanced features like Multimedia Broadcast Multicast Service (MBMS) where synchronized transmission from multiple cells (MBSFN) requires precise frame alignment. The evolution to include H-SFN in later releases (for LTE-M, NB-IoT, and NR) was motivated by the need for even longer timing cycles for ultra-low-power IoT devices, enabling extended DRX cycles beyond 10.24 seconds and more efficient scheduling for small, infrequent data transmissions.
Key Features
- Uniquely identifies radio frames (0-1023 in LTE, also 0-4095 H-SFN in NR)
- Broadcast in the MIB via PBCH
- Governs deterministic scheduling of SIBs and paging occasions
- Serves as a time reference for UE measurements and reporting
- Fundamental for DRX cycle alignment and UE power saving
- Used as a timing reference in positioning protocols (OTDOA)
Evolution Across Releases
Initial definition for UMTS. Established the SFN as a 12-bit counter (0-4095) for FDD mode, providing a timing reference for cell synchronization, paging channel scheduling, and system information block transmission in the 3G WCDMA framework.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 25.123 | 3GPP TS 25.123 |
| TS 25.133 | 3GPP TS 25.133 |
| TS 25.171 | 3GPP TS 25.171 |
| TS 25.172 | 3GPP TS 25.172 |
| TS 25.173 | 3GPP TS 25.173 |
| TS 25.211 | 3GPP TS 25.211 |
| TS 25.212 | 3GPP TS 25.212 |
| TS 25.214 | 3GPP TS 25.214 |
| TS 25.221 | 3GPP TS 25.221 |
| TS 25.222 | 3GPP TS 25.222 |
| TS 25.223 | 3GPP TS 25.223 |
| TS 25.224 | 3GPP TS 25.224 |
| TS 25.225 | 3GPP TS 25.225 |
| TS 25.402 | 3GPP TS 25.402 |
| TS 25.423 | 3GPP TS 25.423 |
| TS 25.800 | 3GPP TS 25.800 |
| TS 25.912 | 3GPP TS 25.912 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.802 | 3GPP TS 26.802 |
| TS 36.133 | 3GPP TR 36.133 |
| TS 36.171 | 3GPP TR 36.171 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.355 | 3GPP TR 36.355 |
| TS 36.401 | 3GPP TR 36.401 |
| TS 36.855 | 3GPP TR 36.855 |
| TS 36.878 | 3GPP TR 36.878 |
| TS 37.355 | 3GPP TR 37.355 |
| TS 37.571 | 3GPP TR 37.571 |
| TS 38.133 | 3GPP TR 38.133 |
| TS 38.171 | 3GPP TR 38.171 |
| TS 38.212 | 3GPP TR 38.212 |
| TS 38.213 | 3GPP TR 38.213 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.401 | 3GPP TR 38.401 |
| TS 38.522 | 3GPP TR 38.522 |
| TS 38.523 | 3GPP TR 38.523 |
| TS 38.913 | 3GPP TR 38.913 |