NUL

Uplink EARFCN / Uplink LARFCN

Physical Layer →
Introduced in Rel-8

NUL is the Uplink Absolute Radio Frequency Channel Number in LTE or Uplink Local Area Radio Frequency Channel Number in NR, a scalar that uniquely identifies the carrier frequency for UE-to-base-station transmission.

Category
Physical Layer
Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Specifications
13 specs
NUL Description Purpose Related Classification Detected Changes Specifications

Description

NUL, denoting Uplink Absolute Radio Frequency Channel Number (EARFCN) in LTE or Uplink Local Area Radio Frequency Channel Number (LARFCN) in 5G NR, is a fundamental parameter in mobile radio systems. It is a dimensionless integer that provides a standardized method for referencing specific uplink radio carrier frequencies without stating the actual frequency value in Hertz. This abstraction simplifies protocol signaling, configuration, and testing specifications. Each NUL value maps to a specific uplink center frequency through a defined formula that incorporates a channel raster and a reference frequency.

In terms of how it works, the NUL is used extensively in Radio Resource Control (RRC) signaling and UE capability specifications. For example, when a network configures a UE to operate on a particular frequency band, it does so by signaling the appropriate NUL value (or a range of values) for the uplink. The UE's radio receiver and transmitter are then tuned to the corresponding physical frequency derived from this NUL. The mapping formulas differ between LTE and NR and are band-specific. In LTE, the formula is F_UL = F_UL_low + 0.1*(NUL - N_Offs_UL). In NR, the formula is more generalized: F_UL = F_REF + (NUL * k), where k is the channel raster step size (e.g., 5 kHz, 15 kHz, 60 kHz).

Key components involved are the UE's radio transceiver, which must interpret the NUL, and the base station (eNodeB/gNodeB), which assigns it. The NUL is part of the carrier configuration information broadcast in System Information Block (SIB) messages and sent in dedicated RRC messages like RRCConnectionReconfiguration. It is also a critical parameter in RF conformance test specifications (e.g., 36.521-1 for LTE), where test equipment uses the NUL to define the test frequency for uplink measurements such as power, modulation quality, and unwanted emissions.

Its role in the network is pivotal for frequency management and UE operation. It allows the network to direct UEs to specific uplink channels within the licensed spectrum. This is crucial for load balancing, interference management, and the operation of carrier aggregation, where a UE may be assigned multiple NULs for simultaneous uplink transmission on different component carriers. The NUL, paired with its downlink counterpart (NDL), provides a complete channel numbering system for the paired spectrum.

Purpose & Motivation

NUL exists to provide a simple, scalable, and technology-agnostic way to refer to uplink radio carrier frequencies within 3GPP standards. Before channel numbers like EARFCN, systems referenced frequencies directly in MHz or kHz, which was cumbersome and prone to error in signaling protocols. The creation of a channel number system abstracts away the complex decimal frequency values and provides a clean integer index that is easier to encode, transmit, and process in digital messages.

The historical motivation stems from GSM, which introduced the ARFCN (Absolute Radio Frequency Channel Number). This concept was successfully carried forward into UMTS as UARFCN and then into LTE as EARFCN. For NR, it was evolved into LARFCN to accommodate a much wider frequency range (from sub-1 GHz to mmWave) and flexible numerologies. The NUL specifically addresses the need for a unique identifier for the *uplink* carrier, which is especially important in Frequency Division Duplex (FDD) systems where uplink and downlink frequencies are different.

It solves several key problems: First, it enables efficient RRC signaling, as transmitting a small integer is far more bandwidth-efficient than a floating-point frequency. Second, it ensures global interoperability; a UE from any vendor, when configured with an NUL value of 'X' for a given band, will tune to exactly the same frequency anywhere in the world. Third, it simplifies testing and certification; test cases are written against NUL values, ensuring that UEs are tested on the correct frequencies relative to the channel raster defined in the standard. This system was crucial for the scalable deployment of LTE and NR across hundreds of frequency bands globally.

Classification

Part ofLARFCN
Related approachesNDL

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-8, normative work from Rel-16.

Rel-16 6 changes

In Release 16, the primary focus for uplink procedures was on corrections and clarifications to specific MAC layer mechanisms. These included refinements to the handling of uplink grants within a bundle, the intra-UE prioritization procedure, and the uplink skipping procedure introduced in this release. The changes aimed to ensure proper operation of configured uplink grants, their priority management, and grants received in Random Access Response.

  • Correction on DRX with bundle transmission of configured uplink grant TS 38.321CR0987
  • Correction for Priority of Uplink Grant TS 38.321CR0998
  • Correction for Uplink Grant Received in RAR and Addressed to Temporary C-RNTI TS 38.321CR1026
  • Clarification on which uplink grants participate to the intra-UE prioritization procedure TS 38.321CR1066
  • Correction on MAC handling of uplink grants within a bundle TS 38.321CR1070
  • Correction on R16 uplink skipping procedure TS 38.321CR1122
Rel-17 1 change

In Release 17, a specific correction was introduced for uplink Timing Advance (TA) maintenance procedures when used for positioning purposes. This enhancement clarified the operation within the LCR TDD system, ensuring accurate synchronization and burst timing for the uplink signal path between the mobile and the base station. The update focused on the precise calculation of the uplink burst timing based on triggers from the NodeB.

  • Correction on uplink TA maintenance for positioning TS 38.321CR1535
Rel-18 2 changes

In Release 18, the primary update for the NUL function involved a correction to the EARFCN (E-UTRA Absolute Radio Frequency Channel Number) specifically for bands 107 and 108, as detailed in the specification for terrestrial broadcast bands. This change ensured accurate channel numbering for the uplink signal path in these frequency bands. No new procedures or capabilities for uplink LARFCN were introduced beyond this correction.

  • (LTE_terr_bcast_bands_part2-Core) CR to 36.104: Correction of EARFCN for bands 107 and 108 TS 36.104CR4990
  • Corrections to validity of configured uplink grant for SDT TS 38.321CR1979

Explore further

Broader topics and technologies where NUL plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 25.116 vj00 LCR TDD Repeater RF Characteristics Rel-19
TS 25.153 vj00 LCR TDD Repeater RF Requirements & Testing Rel-19
TS 36.101 vj30 LTE UE Radio Transmission & Reception 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.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.755 vf00 US 600 MHz LTE Band 71 Technical Report Rel-15
TS 36.790 vf00 LAA/eLAA for CBRS 3.5GHz Band in US Rel-15
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TR 38.892 vi00 Technical Report Rel-18