Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Physical Layer

TFCI

Transport Format Combination Indicator

Physical Layer →

TFCI is a field in the DPCCH that signals the transport format combination used for the DPDCHs, enabling the receiver to correctly decode the data by identifying the transmitter's multiplexing and coding configuration.

Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
24 specs
TFCI Description Purpose What changed Neighbours Specifications

Description

The Transport Format Combination Indicator (TFCI) is a critical physical layer control element in 3GPP UMTS (UTRAN) and its evolution. It is transmitted as part of the Dedicated Physical Control Channel (DPCCH) in the uplink and downlink. Its primary function is to explicitly signal to the receiver which specific combination of Transport Formats (TFs) is active for the associated Dedicated Physical Data Channels (DPDCHs) within the same Coded Composite Transport Channel (CCTrCH) for the current radio frame (10 ms). A Transport Format defines parameters like transport block size, number of blocks, and channel coding scheme for one transport channel. A Transport Format Combination (TFC) is a valid set of TFs, one from each transport channel multiplexed into the CCTrCH. The TFCI value is a binary code that maps directly to one pre-negotiated TFC from a Transport Format Combination Set (TFCS).

Upon receiving a radio frame, the physical layer extracts the TFCI bits from the DPCCH. The receiver then uses this TFCI value as an index to look up the corresponding Transport Format Combination within the TFCS that was configured by higher layers (RRC) during the radio bearer setup or reconfiguration. This lookup provides the receiver with the exact knowledge of how many transport blocks are present for each transport channel, their sizes, and the coding scheme used. This information is absolutely necessary for the receiver to correctly demultiplex, de-rate-match, and decode the data bits on the DPDCH(s). Without the TFCI, the receiver would have to blindly attempt to decode using all possible TFCs, which is computationally prohibitive.

The TFCI field length is configurable (e.g., 0, 2, 3, 4, 5, 6, 7, 8, 9, or 10 bits) depending on the size of the TFCS. A TFCI length of 0 bits indicates that the TFC is fixed and does not need to be signaled dynamically. The mapping between TFCI codes and TFCs is defined by the network. In some operational modes, like compressed mode for measurements, the TFCI may carry additional information or its interpretation may change. The reliable transmission of the TFCI is paramount, as its corruption would lead to a complete failure in decoding the associated data frame. Therefore, the TFCI bits are themselves encoded with a robust (32,10) sub-code of a second-order Reed-Muller code to ensure high detection reliability.

Purpose & Motivation

The TFCI was introduced to solve the fundamental problem of dynamic and variable-rate data transmission in WCDMA-based UMTS networks. Unlike GSM's fixed timeslot structure, UMTS supports highly flexible data rates that can change every 10 ms frame to match the instantaneous requirements of services like voice, video, or web browsing. This flexibility is achieved by allowing multiple transport channels with different characteristics (e.g., signaling and user data) to be multiplexed together (CCTrCH) and for their individual formats to change from frame to frame.

Without an explicit indicator, the receiver would have no way of knowing which combination of formats was used for a given frame. Blind detection of all possible combinations from a potentially large set is computationally complex and error-prone, especially for battery-powered mobile devices. The TFCI provides an efficient, low-overhead signaling mechanism that resolves this ambiguity instantly. It enables fast adaptation of the physical layer to varying traffic conditions and QoS demands, which is essential for supporting the mix of circuit-switched and packet-switched services that UMTS was designed for. The TFCI is a cornerstone of the WCDMA physical layer that makes advanced features like variable spreading factors, adaptive multi-rate (AMR) codecs, and efficient multiplexing of diverse logical channels practically feasible.

What changed in its specifications

The latest release-to-release comparison of specifications that define TFCI. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 25.101Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.101: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.101 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

Introduced as a fundamental component of the WCDMA physical layer for UMTS. Defined the TFCI field in the DPCCH slot format, its encoding using the (32,10) sub-code, and its role in signaling the TFC for variable rate transmission. Established the binding between TFCI values and the Transport Format Combination Set configured by RRC.

Enhanced support for HSDPA. While HS-DSCH uses its own separate signaling (HS-SCCH) for format indication, the associated DCH (for signaling and possibly voice) still uses TFCI. TFCI operation was maintained for non-HSDPA channels and for the DCH in HSDPA-capable connections.

Continued relevance for HSUPA (Enhanced Uplink). The E-DCH uses its own E-TFCI on the E-DPCCH for uplink data, but the associated DPCCH for control (including for non-E-DCH transport channels) may still carry TFCI. Specifications ensured coexistence and clarified usage.

TFCI remains part of the UMTS (UTRAN) specifications as LTE was introduced. For DC-HSDPA and other HSPA+ features, the underlying WCDMA carrier physical layer still relies on TFCI for dedicated channel operation where applicable.

TFCI is maintained in the specifications for legacy UTRAN support and for potential use in NB-IoT over UTRA, ensuring backward compatibility for existing networks and devices.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 25.101 vj00 UTRA FDD UE RF Requirements Rel-19 read
TS 25.201 vj00 UTRA Physical Layer General Description Rel-19 read
TS 25.211 vj00 UTRA FDD Layer 1: Transport & Physical Channels Rel-19 read
TS 25.212 vj00 UTRA FDD Layer 1 Multiplexing & Channel Coding Rel-19 read
TS 25.221 vj00 UTRA TDD Physical Layer Specification Rel-19 read
TS 25.222 vj00 UTRA TDD Multiplexing & Channel Coding Rel-19 read
TS 25.224 vj00 UTRA TDD Physical Layer Procedures Rel-19 read
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 25.302 vj00 UTRA Physical Layer Services Rel-19 read
TS 25.308 vj00 HSDPA Overall Description Rel-19 read
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19 read
TS 25.322 vj00 RLC Protocol Specification Rel-19 read
TS 25.415 vj00 Iu Interface User Plane Protocol Rel-19 read
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19 read
TS 25.427 vj00 UTRAN Iub/Iur User Plane Protocols Rel-19 read
TS 25.433 vj00 Node B Application Part (NBAP) Protocol Rel-19 read
TR 25.914 vj00 3G UE Radio Performance Test Methods Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TS 34.114 vc20 Radiated Performance Test Procedure for UE/MS Rel-12 read
TS 37.544 vg70 UE Radiated Performance Test Procedures Rel-16 read
TS 43.051 vj00 GERAN Stage 2 Service Description Rel-19 read
TS 43.129 vj00 PS Handover in GERAN A/Gb and GAN Modes Rel-19 read
TR 45.902 vj00 Flexible Layer One (FLO) for GERAN Rel-19 read