EARFCN

E-UTRAN Absolute Radio Frequency Channel Number

Identifier →
Introduced in Rel-8

EARFCN is a unique numerical identifier that specifies the center frequency of a radio channel in LTE and 5G NR networks for standardized global frequency reference and management.

Category
Identifier
Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Specifications
32 specs
EARFCN Description Purpose Related Classification Detected Changes Specifications

Description

The E-UTRAN Absolute Radio Frequency Channel Number (EARFCN) is a fundamental identifier within 3GPP specifications for Long-Term Evolution (LTE) and its evolution into 5G New Radio (NR). It serves as a channel number that uniquely maps to a specific center carrier frequency used for communication between User Equipment (UE) and the evolved NodeB (eNB) or gNB. The mapping is defined by a formula that converts the EARFCN value into an absolute frequency in kHz, with separate formulas defined for the uplink and downlink directions. This system abstracts the physical frequency, allowing network commands and configurations to refer to a simple number rather than a raw frequency value, simplifying software and protocol design.

The architecture of frequency identification relies on EARFCN being part of system information broadcast by the cell and used in measurement reporting and handover commands. Key components include the channel raster, which defines the set of allowed EARFCN values and their corresponding frequencies, ensuring that all UEs and base stations tune to the same precise frequency for a given EARFCN. The specifications define different ranges for EARFCN in different operating bands (e.g., Band 1, Band 3), and the value itself indicates whether it is for the uplink or downlink based on the band-specific mapping tables. Its role is central to radio resource management, enabling functions like carrier aggregation, where multiple EARFCNs can be assigned to a single UE to increase bandwidth.

In operation, when a network operator deploys a cell, they configure its operating frequency by setting the EARFCN. The UE, upon scanning or receiving system information, reads the EARFCN and uses the standardized formula to calculate the exact frequency to which it must tune its radio. For measurement reports, the UE identifies neighboring cells by their detected EARFCN. The system supports a wide range of values to cover all licensed spectrum from below 1 GHz to millimeter wave frequencies, with extensions in later releases to accommodate new spectrum allocations. The precision and unambiguous nature of EARFCN are vital for avoiding interference and ensuring seamless mobility across networks from different vendors and operators.

Purpose & Motivation

EARFCN was created to address the need for a unified, scalable, and technology-agnostic method to identify radio channels in LTE networks, replacing the earlier UMTS Absolute Radio Frequency Channel Number (UARFCN) used for 3G. Prior to LTE, different radio access technologies (GSM, UMTS) used their own channel numbering schemes, which complicated multi-mode device design and network interworking. The transition to OFDMA-based LTE required a new scheme that could efficiently represent the wider channel bandwidths and diverse spectrum allocations envisioned for 4G.

The primary problem EARFCN solves is the abstraction of physical frequency details from higher-layer protocols and network management systems. By using a simple integer, network configuration, neighbor cell lists, and handover commands become independent of the actual MHz or GHz values, simplifying software implementation and reducing errors. This abstraction is especially important for global roaming, as a device can interpret an EARFCN from any network worldwide and correctly calculate the local operating frequency based on the standardized formulas. It also future-proofs the system, as new frequency bands can be added by extending the EARFCN range without altering the core protocol mechanics.

Historically, the motivation stemmed from the increasing complexity of spectrum management with the advent of LTE, which was designed to operate in paired (FDD) and unpaired (TDD) spectrum across a continuum from traditional cellular bands to new, higher frequencies. EARFCN provides a consistent reference point that scales across all these scenarios, enabling features like carrier aggregation, where a device simultaneously uses multiple EARFCNs. Its creation was a foundational step in ensuring that LTE and subsequent 5G NR could be deployed flexibly across the globe's fragmented radio spectrum.

Classification

Part ofE-UTRAN
Specific typesMDL
Related approachesUARFCNNR-ARFCN

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change

In Release 15, a correction was made regarding the offset between the NB-IoT channel number and the E-UTRAN Absolute Radio Frequency Channel Number (EARFCN). This change specifically addressed the calculation or mapping for Narrowband Internet of Things (NB-IoT) channels within the EARFCN framework.

  • Correction on Offset of NB-IoT Channel Number to EARFCN TS 36.423CR1093
Rel-18 1 change

In Release 18, the primary update to the EARFCN function was a specific correction applied to bands 107 and 108. This change, documented in a CR to the 36.104 specification, ensured the accurate definition of the Absolute Radio Frequency Channel Numbers for these particular LTE terrestrial broadcast bands. The adjustment was part of ongoing maintenance to align the channel numbering with the correct frequency ranges for these bands.

  • (LTE_terr_bcast_bands_part2-Core) CR to 36.104: Correction of EARFCN for bands 107 and 108 TS 36.104CR4990

Explore further

Broader topics and technologies where EARFCN plays a role.

Defining Specifications

3GPP specifications that define or reference EARFCN, 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 24.368 vj40 NAS Configuration Management Object Rel-19
TS 31.102 vj40 USIM Application Specification Rel-19
TS 36.101 vj30 LTE UE Radio Transmission & Reception Requirements Rel-19
TS 36.102 vj10 E-UTRA UE Satellite Access RF Requirements Rel-19
TS 36.104 vj10 Base Station (BS) radio transmission and reception Rel-19
TS 36.106 vj00 E-UTRA FDD Repeater RF Requirements Rel-19
TS 36.108 vj10 Satellite Access Node RF Requirements Rel-19
TS 36.112 vj00 E-UTRAN LMU Conformance Requirements Rel-19
TS 36.116 vj00 E-UTRA Relay RF Requirements Rel-19
TS 36.117 vj00 E-UTRA Relay RF Test Methods & Requirements Rel-19
TS 36.141 vj00 E-UTRA BS Conformance Testing Rel-19
TS 36.143 vj00 E-UTRA FDD Repeater RF Testing Rel-19
TS 36.181 vj30 E-UTRA RF Test Methods for Satellite Access Node Rel-19
TS 36.423 vj10 X2 Application Protocol (X2AP) Specification Rel-19
TS 36.521 vj00 E-UTRA UE Conformance ICS Proforma Rel-19
TS 36.744 ve00 CBRS 3.5GHz Band Specification for US Rel-14
TS 36.755 vf00 US 600 MHz LTE Band 71 Technical Report Rel-15
TS 36.761 vf00 Extended-Band 12 Study Report Rel-15
TS 36.790 vf00 LAA/eLAA for CBRS 3.5GHz Band in US Rel-15
TR 36.791 vg00 E-UTRA 2.4 GHz TDD Band for US Rel-16
TS 36.858 ve00 LTE 2.6 GHz SDL Band Technical Report Rel-14
TS 37.104 vj10 MSR Base Station RF Characteristics Rel-19
TS 37.113 vj00 EMC Requirements for Multi-Standard Radio Base Stations Rel-19
TS 37.141 vj10 RF Test Methods for Multi-Standard Radio Base Stations Rel-19
TS 37.145 vj10 AAS Base Station Conducted Conformance Testing Rel-19
TS 37.802 va10 MSR BS RF Requirements for Non-Contiguous Spectrum Rel-10
TS 37.812 vb30 Multi-band Multi-standard Radio BS Requirements Rel-11
TS 37.814 vc00 L-band Supplemental Downlink for UTRA/E-UTRA Rel-12
TR 37.900 vj00 Multi-Standard Radio (MSR) Base Station Requirements Rel-19
TR 38.860 vh00 NR; Study on Extended 600 MHz NR band Rel-17
TR 38.892 vi00 Technical Report Rel-18
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.