TPC-RNTI

Transmit Power Control Radio Network Temporary Identifier

Identifier →
Introduced in Rel-8

TPC-RNTI is a specific Radio Network Temporary Identifier used in LTE to address UEs for transmitting Transmit Power Control commands via the PDCCH, enabling network-directed uplink power control.

Category
Identifier
Introduced
Rel-8
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
1 specs
TPC-RNTI Description Purpose Related Classification Detected Changes Specifications

Description

The Transmit Power Control Radio Network Temporary Identifier (TPC-RNTI) is a type of Radio Network Temporary Identifier defined in 3GPP LTE specifications, primarily in TS 36.331 (Radio Resource Control protocol). An RNTI is a unique identifier assigned to a UE or a group of UEs for addressing control information on the Physical Downlink Control Channel (PDCCH). The TPC-RNTI is specifically used to convey Transmit Power Control commands to UEs for adjusting their uplink transmit power on the Physical Uplink Shared Channel (PUSCH) and/or Physical Uplink Control Channel (PUCCH). Unlike UE-specific RNTIs like C-RNTI, the TPC-RNTI can be configured to address multiple UEs in a group, allowing efficient broadcast or multicast of power control commands.

Operationally, the TPC-RNTI is configured by the eNodeB via RRC signaling, typically during connection setup or reconfiguration. The eNodeB uses this RNTI to scramble the Cyclic Redundancy Check (CRC) of a Downlink Control Information (DCI) format that carries TPC commands. UEs monitor the PDCCH for DCI formats scrambled with their assigned TPC-RNTI. Upon detection, they decode the DCI to extract the TPC command, which is a bit field indicating an absolute or relative power adjustment. The UE then applies this adjustment to its uplink transmission power for the relevant channel(s). This mechanism is part of the closed-loop power control for PUSCH and PUCCH, complementing open-loop estimates, to ensure the received power at the eNodeB meets a target level despite path loss and interference variations.

The TPC-RNTI plays a key role in LTE uplink power control architecture, which includes components like the eNodeB's power control algorithm, the UE's power calculation function, and the PDCCH for command delivery. Its use is particularly important in scenarios with dynamic scheduling and shared channel resources, where precise power control minimizes interference to other cells and improves system capacity. The TPC-RNTI is distinct from other RNTIs like SI-RNTI (for system information) or P-RNTI (for paging), as it is dedicated to power control signaling. Its configuration and management are handled by the RRC layer, ensuring that UEs correctly interpret power control commands directed to them, thereby maintaining uplink quality and network efficiency.

Purpose & Motivation

The TPC-RNTI was introduced in LTE (Release 8) to provide a standardized and efficient mechanism for network-controlled uplink power adjustment. In previous systems like UMTS, power control commands were embedded in dedicated physical channels, but LTE's shared channel architecture required a more flexible approach. The TPC-RNTI enables the eNodeB to send power control commands to UEs via the common PDCCH, which is monitored by all active UEs, allowing for dynamic and UE-specific or group-specific power adjustments without dedicated signaling overhead.

This identifier solves the problem of how to efficiently manage uplink power in an OFDMA-based system where multiple UEs share time-frequency resources. By using TPC-RNTI, the network can quickly adapt UE transmit power to changing radio conditions, reducing inter-cell interference and improving overall spectral efficiency. It also helps conserve UE battery life by preventing unnecessary over-transmission. The creation of a dedicated RNTI for this purpose reflects LTE's design principle of separating control and user plane with efficient identifiers, enabling scalable and robust power control essential for the high-performance goals of 4G and beyond.

Classification

Part ofRNTI

Detected Changes Across Releases

from 3GPP Change Requests

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

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

Rel-15 15 changes

In Release 15, the TPC-RNTI function saw enhancements related to uplink power control for new PUCCH formats and corrections for random access power control in TDD. Specifically, the release introduced uplink power control information for PUCCH format 4 and 5 within the System Information Block (SIB) to improve control signaling efficiency. Additionally, it included corrections to the random access power control procedures for TDD systems as specified in TS 36.331.

  • Control Plane latency reduction TS 36.331CR3453
  • Corrections to random access power control for TDD in 36.331 TS 36.331CR3580
  • correction on power control TS 36.331CR3663
  • Supporting MME and AMF overload control TS 36.331CR3745
  • CR to 36.331 on alignment of use of fullI-RNTI and I-RNTI in paging and InactiveConfig (Alt.2) TS 36.331CR3810
  • Power boost values for MWUS TS 36.331CR4023

+ 9 more changes

Rel-16 5 changes

In Release 16, the TPC-RNTI function was enhanced to support UE power savings, with related corrections and clarifications made to the RRC protocol specification. The release also introduced power sharing for Dual Active Protocol Stack (DAPS) handover procedures. These updates were part of a set of Change Requests focused on improving power control and efficiency for connected mode UEs.

  • CR for 36.331 for Power Savings TS 36.331CR4245
  • Incorrect restriction for RLC UM radio bearers TS 36.331CR4385
  • Misc. corrections CR for 36.331 for Power Savings TS 36.331CR4437
  • Introducing power sharing for DAPS handover TS 36.331CR4517
  • Clarify systemInfoUnchanged-BR also transmitted in RSS TS 36.331CR4668
Rel-18 1 change

In Release 18, no specific new functionality for the TPC-RNTI itself is detailed in the provided grounding context. The associated Change Request titles indicate a focus on the clarification of satellite identifiers within the broader specification framework. Therefore, the update pertains to the overall system context in which TPC-RNTI operates, rather than introducing a direct change to the TPC-RNTI mechanism or its procedures.

  • Clarification of satellite identifiers TS 36.331CR5152
Rel-19 1 change

In Release 19, the TPC-RNTI function was enhanced to support power boost for Rel-19 NB-IoT in Non-Terrestrial Networks (NTN). This introduction is based on the CR titled "Support of power boost in Rel-19 NB-IoT NTN," which indicates a new application of TPC commands for this specific scenario. The change leverages existing physical layer procedures to enable improved uplink power control for NB-IoT devices operating via satellite.

  • Support of power boost in Rel-19 NB-IoT NTN TS 36.331CR5198

Explore further

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

Defining Specifications

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

SpecificationTitleRelease
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19