Description
A Resource Block (RB) is the smallest element of radio resources that can be allocated to a user by the scheduler in the LTE and NR air interfaces. It represents a two-dimensional allocation in the time and frequency domains. In LTE, the definition is fixed: one Resource Block in the frequency domain is 12 consecutive subcarriers, each with a spacing of 15 kHz, resulting in a total bandwidth of 180 kHz. In the time domain, one Resource Block spans one slot, which is 0.5 ms (7 OFDM symbols for normal cyclic prefix). Therefore, the basic LTE Resource Block is a grid of 12 subcarriers x 7 symbols (84 Resource Elements for normal CP). The network scheduler allocates integer numbers of these RBs to different UEs in each 1 ms Transmission Time Interval (TTI), which comprises two slots.
In NR, the concept is more flexible to support diverse spectrum bands and use cases. An NR Resource Block is defined as 12 consecutive subcarriers in the frequency domain. However, the subcarrier spacing (SCS) is not fixed at 15 kHz; it can be 15, 30, 60, 120, or 240 kHz (with 480 and 960 kHz for future study). Therefore, the absolute bandwidth of an NR RB scales with the SCS (e.g., 180 kHz for 15 kHz SCS, 3.84 MHz for 240 kHz SCS). In the time domain, NR scheduling is based on slots, but the slot duration also scales inversely with the SCS (e.g., 1 ms for 15 kHz, 0.125 ms for 120 kHz). The NR physical layer is defined in terms of Resource Grids, composed of Resource Elements (one subcarrier for one OFDM symbol). A Resource Block is the grouping used for resource allocation signaling.
The allocation of RBs is dynamic and performed by the Medium Access Control (MAC) layer based on scheduling algorithms that consider channel quality indicators (CQI), buffer status, QoS requirements, and interference coordination. The Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) transport user data mapped onto allocated RBs. The control channels (PDCCH, PUCCH) are also mapped to specific Resource Elements, often at the edges of the carrier bandwidth. The number of RBs in a channel bandwidth defines the channel's transmission bandwidth configuration, which is always less than or equal to the total RF bandwidth to allow for guard bands.
Purpose & Motivation
The Resource Block was created to provide a standardized, granular unit for flexible and efficient spectrum sharing among multiple users in OFDMA-based systems like LTE and NR. Prior technologies like UMTS used code division multiple access (CDMA), where resources were primarily separated by spreading codes, making fine-grained frequency-domain scheduling difficult. The shift to OFDMA required a new fundamental resource unit that could be easily allocated in both time and frequency domains to exploit multi-user diversity and frequency-selective fading.
The RB solves the problem of how to partition the continuous time-frequency resource plane into manageable, allocatable chunks for scheduling, link adaptation, and signaling. It provides the building block for adaptive modulation and coding (MCS selection can be per RB group), interference management techniques like fractional frequency reuse, and carrier aggregation (where RBs can be allocated across multiple component carriers). Its fixed structure in LTE (12 subcarriers) was a design compromise to balance scheduling granularity, control signaling overhead, and implementation complexity. The more flexible RB definition in NR addresses the limitations of the LTE model, allowing efficient operation across a vast range of spectrum from sub-1 GHz to millimeter wave, and for services with vastly different latency and bandwidth requirements, such as massive IoT and ultra-reliable low-latency communications (URLLC).
Key Features
- Defined as 12 consecutive subcarriers in frequency domain
- Time duration is one slot (LTE: fixed 0.5ms, NR: scales with SCS)
- Fundamental unit for dynamic packet scheduling (OFDMA)
- Bandwidth scales with subcarrier spacing in NR
- Used for both data (PDSCH/PUSCH) and control channel mapping
- Enables frequency-selective scheduling and interference coordination
Evolution Across Releases
The term 'Resource Block' was introduced in the context of early LTE (E-UTRA) studies and standardization. The initial concept defined the RB as a fixed block of 12 subcarriers (180 kHz) by one timeslot, establishing the fundamental time-frequency resource unit for the new OFDMA-based air interface. This provided the basis for all physical layer resource allocation and scheduling algorithms.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.979 | 3GPP TS 23.979 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.323 | 3GPP TS 25.323 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.423 | 3GPP TS 25.423 |
| TS 25.912 | 3GPP TS 25.912 |
| TS 25.914 | 3GPP TS 25.914 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 25.993 | 3GPP TS 25.993 |
| TS 26.935 | 3GPP TS 26.935 |
| TS 32.405 | 3GPP TR 32.405 |
| TS 33.821 | 3GPP TR 33.821 |
| TS 34.109 | 3GPP TR 34.109 |
| TS 34.114 | 3GPP TR 34.114 |
| TS 36.104 | 3GPP TR 36.104 |
| TS 36.108 | 3GPP TR 36.108 |
| TS 36.116 | 3GPP TR 36.116 |
| TS 36.117 | 3GPP TR 36.117 |
| TS 36.141 | 3GPP TR 36.141 |
| TS 36.181 | 3GPP TR 36.181 |
| TS 36.216 | 3GPP TR 36.216 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.323 | 3GPP TR 36.323 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.745 | 3GPP TR 36.745 |
| TS 36.761 | 3GPP TR 36.761 |
| TS 36.766 | 3GPP TR 36.766 |
| TS 36.790 | 3GPP TR 36.790 |
| TS 36.833 | 3GPP TR 36.833 |
| TS 36.878 | 3GPP TR 36.878 |
| TS 36.884 | 3GPP TR 36.884 |
| TS 37.104 | 3GPP TR 37.104 |
| TS 37.105 | 3GPP TR 37.105 |
| TS 37.141 | 3GPP TR 37.141 |
| TS 37.145 | 3GPP TR 37.145 |
| TS 37.320 | 3GPP TR 37.320 |
| TS 37.544 | 3GPP TR 37.544 |
| TS 37.718 | 3GPP TR 37.718 |
| TS 37.719 | 3GPP TR 37.719 |
| TS 37.801 | 3GPP TR 37.801 |
| TS 37.802 | 3GPP TR 37.802 |
| TS 37.812 | 3GPP TR 37.812 |
| TS 37.829 | 3GPP TR 37.829 |
| TS 37.900 | 3GPP TR 37.900 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 37.902 | 3GPP TR 37.902 |
| TS 37.911 | 3GPP TR 37.911 |
| TS 38.104 | 3GPP TR 38.104 |
| TS 38.108 | 3GPP TR 38.108 |
| TS 38.141 | 3GPP TR 38.141 |
| TS 38.174 | 3GPP TR 38.174 |
| TS 38.176 | 3GPP TR 38.176 |
| TS 38.181 | 3GPP TR 38.181 |
| TS 38.213 | 3GPP TR 38.213 |
| TS 38.214 | 3GPP TR 38.214 |
| TS 38.323 | 3GPP TR 38.323 |
| TS 38.809 | 3GPP TR 38.809 |
| TS 38.833 | 3GPP TR 38.833 |
| TS 38.864 | 3GPP TR 38.864 |
| TS 38.870 | 3GPP TR 38.870 |
| TS 38.872 | 3GPP TR 38.872 |
| TS 38.877 | 3GPP TR 38.877 |
| TS 38.878 | 3GPP TR 38.878 |
| TS 38.903 | 3GPP TR 38.903 |
| TS 38.921 | 3GPP TR 38.921 |
| TS 38.922 | 3GPP TR 38.922 |
| TS 43.051 | 3GPP TR 43.051 |
| TS 44.060 | 3GPP TR 44.060 |
| TS 44.160 | 3GPP TR 44.160 |