E-RNTI

E-DCH Radio Network Temporary Identifier

Identifier →
Introduced in Rel-6

E-RNTI is a temporary identifier assigned by the Node B to a UE to address and identify it on the Enhanced Dedicated Channel (E-DCH) in UMTS/HSPA, used on shared control channels like E-AGCH and E-RGCH.

Category
Identifier
Introduced
Rel-6
Where
Radio Access Network › UTRAN (3G)
Specifications
8 specs
E-RNTI Description Purpose Related Classification Specifications

Description

The E-DCH Radio Network Temporary Identifier (E-RNTI) is a 16-bit identifier used in the UMTS/HSPA radio access network (UTRAN) to uniquely address a User Equipment (UE) within the context of its Enhanced Dedicated Channel (E-DCH) operation. Unlike the longer-term U-RNTI assigned by the RNC, the E-RNTI is assigned by the serving Node B during the setup of the E-DCH and can be changed by the Node B, for instance, during a serving cell change. Its primary function is to allow the Node B to send control information intended for a specific UE over shared downlink physical channels. The two key channels that use the E-RNTI for addressing are the E-DCH Absolute Grant Channel (E-AGCH) and the E-DCH Relative Grant Channel (E-RGCH). On the E-AGCH, which carries absolute serving grant values, the E-RNTI is used to scramble the transmitted bits, ensuring only the targeted UE can correctly decode the grant. On the E-RGCH, which carries relative up/hold/down commands, the E-RNTI determines the specific orthogonal signature (a channelization code within a defined set) used for transmission. The UE continuously monitors these shared channels, checking for messages scrambled or signaled with its assigned E-RNTI. This mechanism is highly efficient as it avoids the need for dedicated signaling links for scheduling commands, allowing a single shared channel resource (like a set of channelization codes) to be time-multiplexed among multiple UEs. The E-RNTI is a critical enabler of the fast, cell-centric scheduling architecture of HSUPA, as it provides the necessary addressing layer between the Node B's scheduler and the individual UE's MAC-e/es entity.

Purpose & Motivation

The E-RNTI was introduced in 3GPP Release 6 alongside HSUPA to address the need for efficient, low-latency addressing in the new fast Node B scheduling paradigm. In the pre-HSUPA UMTS architecture, control signaling was primarily between the RNC and the UE, using identifiers like the U-RNTI, which was not designed for the millisecond-level scheduling decisions required for the E-DCH. The purpose of the E-RNTI is to provide a temporary, cell-level identifier that allows the Node B's physical layer to directly and unambiguously communicate scheduling commands (grants) to a specific UE over shared physical resources. This solves the problem of how to efficiently deliver per-UE control information without establishing numerous dedicated control channels, which would waste scarce downlink code resources. By using a short 16-bit identifier for scrambling and code selection, the system achieves a good balance between addressing space and signaling overhead. The E-RNTI is central to the operation of the E-AGCH and E-RGCH, enabling the rapid, targeted resource allocation that gives HSUPA its high uplink performance and capacity gains over Release 99 DCH.

Classification

Part ofU-RNTI
Specific typesS-E-RNTI
Related approachesE-AGCHE-RGCH

Evolution Across Releases

Rel-6 Initial

Introduced as the key addressing identifier for HSUPA's fast scheduling framework. Defined as a 16-bit value assigned by the Node B, used to scramble E-AGCH messages and to select the specific code for E-RGCH transmission, enabling direct Node-B-to-UE control signaling for the E-DCH.

Explore further

Broader topics and technologies where E-RNTI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 25.212 vj00 UTRA FDD Layer 1 Multiplexing & Channel Coding Rel-19
TS 25.309 v1600 FDD Enhanced Uplink Support Rel-6
TS 25.319 vj00 Enhanced Uplink for UTRA FDD/TDD Rel-19
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TS 25.433 vj00 Node B Application Part (NBAP) Protocol Rel-19
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19