Control overhead in LTE refers to the portion of radio resources (time, frequency, and power) that is consumed by control signaling rather than actual user data. Think of it like a postal delivery system: only part of each delivery truck’s capacity carries the actual packages (user data), while the rest is taken up by paperwork, labels, and routing information (control signals). The network cannot work without these control signals, but every bit spent on them is a bit that cannot carry your YouTube video or web page.
The LTE Resource Grid: Where It All Lives
Before understanding overhead, you need to picture how LTE organizes its radio resources. LTE uses a structure called the Resource Grid, which is a time-frequency grid.
- Resource Element (RE): The smallest unit. One subcarrier (15 kHz wide) × one OFDM symbol (~71 µs long).
- Resource Block (RB): A group of 12 subcarriers × 7 symbols = 84 REs (in Normal Cyclic Prefix mode). This is the smallest unit that can be allocated to a user.
- Subframe: 1 ms in duration, containing 14 symbols. This is also called the TTI (Transmission Time Interval), the scheduling period.
- Frame: 10 ms, containing 10 subframes.
At every TTI, the MAC layer scheduler assigns RBs to users. But before any user data can be placed on the grid, several control channels must claim their share of the REs.
What Is Control Overhead?
Control overhead = all REs consumed by control channels, reference signals, and synchronization signals. These are REs that cannot be used for user data (PDSCH in downlink, PUSCH in uplink).
The formula for cell capacity tells the whole story:
Capacity = Available RBs - Control Overheads - Custom Configs
Every control channel you add reduces the space left for data. The goal of good network planning is to keep control overhead as lean as possible while still keeping the network functional and reliable.
Downlink Control Channels and Their Overhead
The downlink (eNodeB sending to UE) carries the most control overhead because the base station must coordinate all connected users simultaneously.
PSS and SSS (Synchronization Signals)
These are the Primary Synchronization Signal and Secondary Synchronization Signal. They are sent twice per frame (every 5 ms) on the middle 62 subcarriers of the bandwidth. Their job is to let a UE (your phone) first detect and synchronize to the cell. They consume 144 REs each per radio frame. Though their overhead is small (around 0.25% for 3 MHz bandwidth), they are non-negotiable since without them no UE can ever connect.
PBCH (Physical Broadcast Channel)
This channel broadcasts essential cell information to all users, such as the system bandwidth, the System Frame Number (SFN), and HARQ indicator channel configuration. It uses 72 subcarriers across 4 symbols in the first slot of every 4th frame and contributes about 0.95% overhead.
PCFICH (Physical Control Format Indicator Channel)
This is a small but critical channel. It uses only 16 REs on symbol 0 of every subframe and carries a 2-bit value called the CFI (Control Format Indicator). The CFI tells the UE how many OFDM symbols (1, 2, or 3) in the current subframe are used by the PDCCH (see below). Without PCFICH, the UE would not know where control information ends and user data begins. Its overhead is about 0.63%.
PDCCH (Physical Downlink Control Channel)
This is the most impactful control channel in terms of overhead. PDCCH carries DCI (Downlink Control Information), which tells each UE:
- Which RBs are assigned to it for this subframe.
- What MCS (Modulation and Coding Scheme) to use.
- Uplink power control commands.
PDCCH occupies the first 1 to 3 OFDM symbols across the entire bandwidth in each subframe - the exact number is signaled by PCFICH via the CFI value. This means:
- If CFI = 1: PDCCH uses 1 symbol, PDSCH uses the remaining 13 symbols.
- If CFI = 3: PDCCH uses 3 symbols, PDSCH can only use 11 symbols - roughly a 15% reduction in data throughput.
PDCCH is organized in units called CCEs (Control Channel Elements), where 1 CCE = 9 REGs = 36 REs. A single user’s scheduling grant requires 1, 2, 4, or 8 CCEs depending on channel quality (users with poor signal need more CCEs for reliability). Up to 17% of all LTE network resources can be consumed by PDCCH in a fully loaded cell.
PHICH (Physical HARQ Indicator Channel)
This channel sends ACK/NACK feedback to UEs in the uplink direction - confirming whether a UE’s uplink data packet was received correctly or needs to be retransmitted. This is part of the HARQ (Hybrid Automatic Repeat Request) protocol. PHICH uses symbol 0 and its size scales with bandwidth, consuming between 120 and 1560 REs per frame depending on the bandwidth.
CRS (Cell-specific Reference Signals)
These are pilot signals inserted throughout the time-frequency grid so UEs can estimate channel quality. They are used for demodulation and for measuring RSRP (signal strength). The overhead scales with the number of antenna ports - with 2 antenna ports, CRS takes about 4.7% of resources at 3 MHz bandwidth.
A Real Overhead Breakdown Example
To make this concrete, here is what the overhead looks like for a 3 MHz, 2×2 MIMO cell:
| Channel/Signal | Overhead % |
|---|---|
| CRS (Reference Signals) | 4.7% |
| PSS/SSS (Sync Signals) | 0.25% |
| PBCH (Broadcast) | 0.95% |
| PCFICH (Control Format) | 0.63% |
| PHICH (HARQ Feedback) | 0.95% |
| PDCCH (Scheduling) | 9.5% |
| DTX (unused REs) | 5.5% |
| PDSCH (User Data) | 76.3% |
Only 76.3% of the radio frame is available for actual user data. The rest is overhead. Increasing PDCCH symbols from 1 to 3 can reduce maximum cell capacity by as much as 5 Mbps in a 3 MHz cell.
Uplink Control Overhead
In the uplink direction (UE sending to eNodeB), the main control channel is PUCCH (Physical Uplink Control Channel). PUCCH carries:
- CQI (Channel Quality Indicator): The UE reports the current channel quality to the scheduler so it can choose the right MCS.
- HARQ ACK/NACK: Confirming whether downlink packets were received.
- Scheduling Requests (SR): The UE asks for uplink resources.
PUCCH occupies a configurable number of RBs at the edges of the frequency band (to avoid interfering with PUSCH in the middle). Each additional RB allocated to PUCCH adds about 1-2% to the total system overhead. When PUSCH is already scheduled for a UE, control information can be piggybacked onto PUSCH to save resources, so PUCCH is only transmitted when there is no PUSCH scheduled.
Why Control Overhead Matters for Your Project
Understanding control overhead is essential for the MAC scheduler because the scheduler must account for the fact that not all REs in a subframe are available for data. The actual data capacity the scheduler can allocate to users is determined by:
Available REs for PDSCH = Total REs - Control Overhead REs
A well-designed scheduler avoids “over-scheduling” (assigning more data than the remaining REs can carry) and must adapt dynamically to the CFI value each TTI to know the true available data region. This is a foundational constraint that any AI-based or classical scheduler must respect.