Transport Block

Description

A Transport Block is the fundamental data unit that the Medium Access Control layer hands to the physical layer for transmission over a radio transport channel. It is not the same as a code block or a codeword; it is the payload that the physical layer may protect with a cyclic redundancy check, segment, channel-code, rate-match, and modulate. On the receiver side, the physical layer decodes the received signal, checks the CRC, and delivers the resulting block back to the MAC layer as a received transport block. This separation lets the MAC scheduler control throughput and reliability while the physical layer controls waveform, coding, and mapping to radio resources.

In LTE and NR, a transport block is associated with a scheduled PDSCH or PUSCH transmission. The network or UE selects a modulation and coding scheme, and the transport block size is derived from the allocated time-frequency resources, the number of spatial layers, and the overhead of reference signals and control information. The MAC layer creates the transport block from one or more MAC sub-PDUs, including MAC headers and upper-layer data. The physical layer then adds a CRC, segments the block into code blocks if needed, applies channel coding, performs rate matching, maps the bits to modulation symbols, and transmits them. In NR, code block groups and multiple transport blocks can be used to support flexible scheduling and reliability targets.

The transport block is also the natural unit for Hybrid Automatic Repeat Request. A successful CRC check allows the receiver to send an acknowledgement, while a failed check triggers a negative acknowledgement and a retransmission. The retransmission may carry the same data with a different redundancy version, and the receiver can combine soft information from multiple attempts. This makes the transport block central to link adaptation, latency control, and reliability. If the transport block is too large for the available resources, the physical layer segmentation and code block processing manage the tradeoff between error correction and overhead.

A transport block can be viewed as a MAC PDU from the perspective of the radio link. It contains the data that must be delivered in one scheduled transmission opportunity, and it is protected as a whole. The CRC size can depend on the block length, and the physical layer may split a large transport block into several code blocks so that channel coding can operate efficiently. This structure allows the system to use high coding rates for large blocks and stronger protection for smaller blocks without changing the MAC concept.

Across 3GPP releases, the term has remained the name for the MAC-to-PHY block, while the radio technology around it has changed. In early UTRAN usage, it described blocks carried over shared transport channels. In LTE, it became the unit scheduled by the eNodeB for PDSCH and PUSCH. In NR, it supports flexible numerologies, LDPC and Polar coding, beam-based transmission, and enhanced reliability mechanisms. The stability of the term helps engineers map MAC behavior to physical-layer performance across generations.

For network engineers, understanding the transport block is essential because it connects scheduling decisions to radio performance. Transport block size, coding rate, HARQ processes, and retransmission behavior determine user throughput, packet delay, and reliability. It also affects QoS enforcement because different services can be mapped to different scheduling and HARQ configurations. In short, the transport block is the bridge between higher-layer data and the physical radio signal.

Purpose & Motivation

The transport block exists to give the MAC layer a clear, manageable unit of data for scheduling radio resources. Without it, the scheduler would have to reason directly about symbols, code blocks, or individual packets, which would couple radio resource management to physical-layer details. By defining a block that contains the data to be transmitted in one scheduled opportunity, 3GPP allows link adaptation, HARQ, and QoS control to operate at a level that is both meaningful to the network and practical for the physical layer.

Historically, radio systems evolved from circuit-switched or channelized designs toward packet-switched, shared-channel operation. Shared channels require fast scheduling because radio conditions change quickly. A transport block provides the granularity needed for fast link adaptation: if channel quality is good, the scheduler can choose a larger transport block and higher coding rate; if quality degrades, it can choose a smaller block and stronger coding. This avoids fixed-rate transmission and improves spectral efficiency.

The concept also addresses reliability and latency. A transport block with a CRC allows the receiver to detect errors quickly and request retransmission. Hybrid ARQ can combine multiple attempts, reducing the need for higher-layer retransmissions. This is especially important for mobile broadband, low-latency services, and IoT, where packet loss, delay, and coverage can vary rapidly. The transport block therefore remains a core abstraction that balances throughput, reliability, and implementation simplicity.