Glossary term · Physical Layer

Transport Block Size

Transport Block Size

Physical Layer →

Transport Block Size is the number of bits carried by a Transport Block, which is the fundamental unit of data exchanged between the physical layer and the MAC layer in a 3GPP system.

Introduced
Rel-4
Where
Services
Specifications
1 specs

3GPP QuarterlyThe next issue by email, at most eight a year.

Category
Physical Layer
Introduced
Rel-4
Where
Services
Specifications
1 specs
Transport Block Size Description Purpose Related Specifications

Description

Transport Block Size (TBS) is defined in 3GPP TS 21.905 as the size, expressed in number of bits, of a Transport Block. A Transport Block (TB) is the basic payload unit that the physical layer (L1) delivers to or receives from the Medium Access Control (MAC) layer during a Transmission Time Interval (TTI). TBS therefore quantifies the amount of data — including MAC headers, MAC Service Data Units (SDUs), and any padding — that is mapped onto the radio resources allocated for a single transmission opportunity. It is a central parameter in link adaptation, because the scheduler must choose a TBS that matches the instantaneous channel quality, the available resource elements, and the target error rate.

In the physical layer processing chain, TBS is the input to the transport block cyclic redundancy check (CRC) attachment, code block segmentation, channel coding (turbo coding in LTE, LDPC in NR), rate matching, and modulation. The number of coded bits that can be carried depends on the modulation order, the number of allocated resource blocks (or physical resource blocks), and the number of layers used for spatial multiplexing. The eNodeB or gNodeB selects a Modulation and Coding Scheme (MCS) and a resource allocation; the combination of MCS index and allocated resources maps to a specific TBS through standardized tables. In LTE, TS 36.213 defines the TBS tables indexed by the MCS index and the number of allocated physical resource blocks (N_PRB). In NR, TS 38.214 defines TBS determination procedures that account for the number of layers, modulation order, code rate, and the number of resource elements per PRB, with additional quantization and overhead assumptions.

TBS is tightly coupled with the concept of the Transport Block Set (TBS in UMTS terminology, often abbreviated TBS or TB set). In UMTS, a Transport Format defines both a dynamic part (e.g., TBS size, TTI) and a semi-static part (e.g., transmission time interval, channel coding type). The dynamic part can change every TTI, allowing the network to adapt the instantaneous data rate to channel conditions and traffic demand. In LTE and NR, the equivalent flexibility is achieved through dynamic scheduling grants, where the Downlink Control Information (DCI) carries the MCS and resource allocation that jointly determine the TBS. Semi-persistent scheduling and configured grants fix the resource allocation for periodic traffic, but the TBS is still derived from the configured MCS and resource block allocation.

Because TBS directly affects spectral efficiency and reliability, it is a key optimization variable in radio resource management. A larger TBS increases throughput but requires more robust coding or higher signal-to-noise ratio to maintain the block error rate (BLER) target. A smaller TBS improves reliability and coverage at the expense of throughput. The scheduler balances these trade-offs using channel quality indicators (CQI), hybrid ARQ (HARQ) feedback, and quality-of-service (QoS) requirements. TBS also influences latency: larger transport blocks take longer to encode, decode, and retransmit, which matters for ultra-reliable low-latency communication (URLLC) services. In NR, the concept of a transport block remains, but the physical layer supports more flexible numerologies, wider bandwidths, and multi-layer transmission, making TBS determination more complex than in LTE.

In summary, TBS is the bridge between MAC scheduling decisions and physical layer transmission. It encapsulates the amount of data to be transmitted in one TTI, and its calculation depends on standardized tables and procedures that ensure the transmitter and receiver agree on the exact payload size. Mastery of TBS concepts is essential for understanding link adaptation, throughput performance, and radio resource management in 3GPP systems.

Purpose & Motivation

Transport Block Size exists to provide a standardized, unambiguous measure of the payload that the physical layer delivers to MAC in a single transmission opportunity. Without a common definition, the transmitter and receiver could not agree on how many bits are being sent, making decoding impossible. TBS enables link adaptation by allowing the scheduler to adjust the amount of data per transmission according to channel conditions, thereby maximizing spectral efficiency while maintaining reliability.

Historically, early cellular systems used fixed or semi-static payload sizes, which limited the ability to adapt to varying radio conditions. The introduction of transport channels and transport formats in UMTS (Release 99 and later) allowed dynamic adaptation per TTI, but required precise definitions of TBS and transport format combinations. LTE and NR refined these concepts with standardized TBS tables and procedures that map resource allocations and MCS to exact bit sizes, supporting high-speed packet access and beyond. TBS thus solves the problem of efficient, reliable, and adaptive data transmission over inherently variable wireless channels.

Release Timeline

Evolution Across Releases

Rel-4 Initial

Initial definition: 'Transport Block Size is defined as the size (number of bits) of a Transport Block.' This established the fundamental concept for UMTS transport channels, enabling dynamic adaptation of payload size per TTI.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4, though LTE introduced new TBS determination procedures in TS 36.213.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4; LTE-Advanced introduced carrier aggregation and higher-order MIMO, increasing TBS ranges.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4; NB-IoT and eMTC introduced new TBS constraints for low-power wide-area use cases.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4; NR introduced new TBS determination procedures in TS 38.214 with flexible numerologies and LDPC coding.

Definition carried over unchanged from Rel-4; NR URLLC enhancements introduced new TBS considerations for low-latency transmissions.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4; NR evolution continued to refine TBS procedures for higher capacity and new services.

Definition carried over unchanged from Rel-4.

Defining Specifications

3GPP specifications that define or reference Transport Block Size, 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