>
HomeLTE 4GPHY โ€” Physical LayerPHY Overview
๐Ÿ“ถ PHY โ€” Physical LayerBeginner

Physical Layer Overview in LTE 4G

What the LTE physical layer delivers to the MAC, and the map of the 36.2xx specification series.

📚 3GPP-basedTS 36.201TS 36.211

The LTE physical layer is the bottom of the radio stack: it takes a block of bits handed down by the MAC and turns it into a radio waveform, and does the reverse on reception. It hides all the messy business of coding, modulation and OFDM behind a small, tidy set of transport channels, so the layers above never touch a subcarrier. This page is grounded in TS 36.201 (the layer-1 general description) and the family of 36.2xx specifications that define every stage in detail.

Introduction

The physical layer (PHY, or Layer 1) is where LTE stops being a protocol and becomes electromagnetic energy in the air. Everything above it — RRC state machines, MAC scheduling, RLC segmentation — ultimately produces a transport block of bits that the PHY must carry across the radio channel and reconstruct at the far end. The PHY is the only layer that deals with turbo codes, QAM constellations, OFDM symbols and antenna ports; everything else reasons in bits and blocks.

It runs constantly, in both directions, for the entire life of a connection. From the very first moment a UE powers on it is using the PHY — correlating against the PSS/SSS to find a cell, decoding the PBCH to read the MIB, then decoding PDCCH grants and PDSCH data once connected. Every millisecond a scheduled UE has, the PHY encodes or decodes at least one transport block and reports back HARQ acknowledgements and channel measurements. It is the busiest and most latency-critical layer in the stack.

Understanding the PHY matters because almost every "why is throughput low / why won't it attach / why is coverage poor" question eventually lands here: on modulation order, code rate, reference-signal overhead, or how many resource elements actually carried the transport block. Knowing the fixed shape of the LTE PHY — one numerology, one transmit chain, a handful of transport and physical channels — lets you reason about all of that from first principles.

Why the physical layer exists

๐Ÿ’ก

In plain words: think of the PHY as a courier company for the rest of the stack. The MAC drops off a sealed parcel (a transport block) once every 1 ms and says only "deliver this." It does not care whether the courier uses a van or a bike, which roads it takes, or how it packs the box to survive the trip — it just wants the parcel to arrive intact. The PHY does all the packing (coding), labelling (modulation), route-planning (resource mapping) and damage-reporting (HARQ), and hides every bit of it behind that one simple drop-off counter: the transport channel.

Concretely, the PHY exists to solve one hard problem the upper layers must not be burdened with: moving bits reliably across a hostile, time-varying radio channel. That means three jobs. First, protect the bits — add a CRC so errors are detectable and channel coding (turbo for data) so many of them are correctable, then let HARQ retransmit what survives neither. Second, fit the bits to the channel — choose a modulation and code rate matched to the current signal quality, and lay the coded symbols onto exactly the time-frequency resources the scheduler granted. Third, make the signal findable and measurable — transmit synchronisation and reference signals so the receiver can lock timing, estimate the channel, and report quality back up.

What

Layer 1 of the LTE air interface: it exposes transport channels upward to the MAC and physical channels downward to the antenna, and performs the coding/modulation/OFDM processing that connects the two. Defined in general terms by TS 36.201.

Why

Higher layers should reason about "a block of bits to deliver this TTI," not about turbo coding or subcarrier spacing. The transport-channel abstraction lets the MAC schedule and the PHY optimise the radio independently.

How

Per TTI the MAC delivers a transport block; the PHY adds a CRC, channel-codes it, maps it to a physical channel, modulates and OFDM-transmits it, then reports back HARQ acknowledgements and measurements.

What the Physical Layer Delivers

Think of the physical layer (PHY, or Layer 1) as a service provider with exactly one customer above it: the MAC. The PHY offers the MAC a handful of transport channels, and everything the PHY actually does — coding, rate matching, modulation, mapping onto the air — is done to serve data flowing over those transport channels. The MAC never sees an OFDM symbol or a resource element; it just hands down a transport block once per Transmission Time Interval (TTI, 1 ms in LTE) and trusts the PHY to deliver it.

What

Layer 1 of the LTE air interface. It exposes transport channels upward to the MAC and physical channels downward to the antenna, and performs the coding/modulation/OFDM processing that connects the two. Defined in general terms by TS 36.201.

Why

Higher layers should reason about "a block of bits to deliver this TTI," not about turbo coding or subcarrier spacing. The transport-channel abstraction lets the MAC schedule and the PHY optimise the radio independently.

How

Per TTI the MAC delivers a transport block; the PHY adds a CRC, channel-codes it, maps it to a physical channel, modulates and OFDM-transmits it, then reports back HARQ acknowledgements and measurements.

The service the PHY offers is described entirely in terms of transport channels, each with its own characteristics — whether it is shared or dedicated, broadcast to all or addressed to one, and what error-protection and multiplexing options it supports. In the downlink the workhorse is the Downlink Shared Channel (DL-SCH), which carries almost all user data and most higher-layer control. Alongside it sit the Broadcast Channel (BCH) for the fixed Master Information Block, the Paging Channel (PCH) for reaching idle UEs, and the Multicast Channel (MCH) for MBMS content delivered over a single-frequency network. In the uplink there are just two: the Uplink Shared Channel (UL-SCH) for user data and control, and the Random Access Channel (RACH), the contention channel a UE uses to first get the network's attention.

Transport channelDirectionCarries
DL-SCHDownlinkUser data and most higher-layer signalling; supports HARQ, dynamic scheduling, and adaptive modulation/coding.
BCHDownlinkThe fixed-format Master Information Block (MIB) — the minimum a UE needs to acquire the cell.
PCHDownlinkPaging messages that wake idle UEs; multiplexed onto the same shared resources as DL-SCH.
MCHDownlinkMBMS (broadcast/multicast) content, transmitted synchronously across cells in an MBSFN.
UL-SCHUplinkUser data and control from the UE; supports HARQ and link adaptation.
RACHUplinkThe random-access preamble used to initiate a connection or regain uplink synchronisation.
🎯

One customer, a small menu: the PHY's entire upward-facing API is these six transport channels. Everything below — turbo codes, QAM, IFFTs — exists only to move transport blocks across them reliably. When you can name the transport channel, you already know most of what the MAC expects.

The 36.2xx Spec Map

The LTE physical layer is described across a small, well-organised family of specifications. Knowing which document holds what saves enormous time — an exam or interview question about "where is turbo coding defined?" is really a question about the 36.2xx map. The five documents divide the problem cleanly: one overview, one for what is transmitted, one for how bits are protected, one for how the PHY behaves over time, and one for what it measures.

SpecTitleWhat it contains
TS 36.201LTE physical layer; General descriptionThe overview and glue: what the PHY does, how the other 36.2xx documents fit together, and the transport-channel service to the MAC.
36.211Physical channels and modulationPhysical channels and signals, the resource grid, frame structure, modulation, reference signals, and how everything maps onto resource elements.
36.212Multiplexing and channel codingCRC attachment, code-block segmentation, turbo/convolutional coding, rate matching, and the coding of control information (e.g. DCI).
36.213Physical layer proceduresHow the PHY behaves in time: HARQ, power control, CQI/CSI reporting, random-access procedures, and PDCCH decoding rules.
36.214Physical layer; MeasurementsDefinitions of the layer-1 measurements — RSRP, RSRQ, RSSI and friends — that feed mobility and scheduling.
📘

Memory hook: 36.211 = channels (what is sent, where), 36.212 = coding (how bits are protected), 36.213 = procedures (how it behaves over time), 36.214 = measurements (what is reported). TS 36.201 is the map that ties them together. Almost any PHY question maps onto exactly one of these.

Two Multiple-Access Schemes: OFDMA and SC-FDMA

LTE deliberately uses a different multiple-access scheme in each direction. The downlink uses OFDMA (Orthogonal Frequency Division Multiple Access): the wideband channel is split into many narrow 15 kHz subcarriers, and different UEs are served on different groups of subcarriers and symbols. OFDMA is robust against multipath — a long cyclic prefix absorbs delay spread so each subcarrier sees a flat channel — and it is easy to schedule in two dimensions, time and frequency, which is exactly what a base station with plenty of power wants.

The uplink instead uses SC-FDMA (Single-Carrier FDMA), also called DFT-spread OFDM. It is almost the same as OFDMA, with one extra step inserted before the OFDM modulator: a DFT (Discrete Fourier Transform) "spreads" the data symbols across the assigned subcarriers first. This small change makes the transmitted waveform behave much more like a single carrier, which dramatically lowers its Peak-to-Average Power Ratio (PAPR).

🎯

Why the uplink is different: a high PAPR forces a power amplifier to back off from its efficient operating point. The eNB can afford that; a battery-powered UE cannot. Low-PAPR SC-FDMA lets the UE's power amplifier run closer to saturation — more coverage and more battery life for the same transmit power. It is a direct trade of receiver complexity (equalising a single-carrier signal is harder, and the eNB does it) for transmitter efficiency (which the UE badly needs).

Both schemes share the same 15 kHz subcarrier spacing, the same slot/subframe timing, and the same resource grid, so a UE's receiver and transmitter reuse most of the same OFDM machinery. The DFT-spread stage is the only structural difference — which is why SC-FDMA is often just described as "OFDM with a DFT precoder in front."

DownlinkUplink
Access schemeOFDMASC-FDMA (DFT-spread OFDM)
Subcarrier spacing15 kHz (fixed)15 kHz (fixed)
PAPRHigher (acceptable at eNB)Low (protects UE power amplifier)
Extra processing stepNone before OFDMDFT precoding before OFDM
Main data channelPDSCHPUSCH

Physical Channels, Physical Signals, and the Mapping

Downward, the PHY does not expose transport channels — it exposes physical channels and physical signals, and the difference matters. A physical channel carries information that originated above the PHY: a transport channel's bits, or Layer-1 control. A physical signal carries nothing from higher layers at all — it exists purely so the receiver can do its job: synchronise, estimate the channel, or measure signal quality.

What

Physical channels (PDSCH, PDCCH, PBCH, PUSCH, PUCCH, PRACH…) carry higher-layer or control bits. Physical signals (reference signals, synchronisation signals) carry no higher-layer data.

Why

The receiver cannot demodulate a channel it cannot measure or find. Signals like the CRS and PSS/SSS give the UE the timing, frequency, and channel estimates without which the physical channels are undecodable.

How

Both are just patterns of complex symbols on resource elements. TS 36.211 defines exactly which REs each channel and signal occupies, so nothing collides on the grid.

The key physical signals in LTE are the Cell-specific Reference Signal (CRS), scattered across the whole downlink band so any UE can estimate the channel and measure RSRP; the Primary and Secondary Synchronisation Signals (PSS/SSS) that a UE finds first to acquire timing and the physical cell ID; and, on the uplink, the Demodulation Reference Signal (DM-RS) and Sounding Reference Signal (SRS). LTE is fundamentally a CRS-based system: the always-on, cell-wide reference signal is the backbone of downlink demodulation and measurement. The physical cell identity itself is PCI = 3 × NID(1) + NID(2), where the SSS carries the cell-group NID(1) (0–167) and the PSS the sector NID(2) (0–2), giving 504 distinct PCIs — and it is the PCI that seeds the CRS frequency shift and scrambling.

Each transport channel maps to one or more physical channels. This transport-to-physical mapping is the seam between the two worlds — the MAC's DL-SCH becomes bits on the PDSCH, and so on down the list.

Transport channelPhysical channelNotes
DL-SCHPDSCHScheduling grants for it ride on the PDCCH.
PCHPDSCHPaging is multiplexed onto the shared data channel.
BCHPBCHCarries only the MIB, with a fixed format.
MCHPMCHMBMS content over MBSFN subframes.
UL-SCHPUSCHUplink data and multiplexed control.
RACHPRACHCarries the random-access preamble.

Two physical channels have no transport channel above them because they carry Layer-1 control created inside the PHY itself: the PDCCH, which carries Downlink Control Information (DCI) — the scheduling grants that tell a UE where its PDSCH is — and the PUCCH, which carries Uplink Control Information (HARQ ACK/NACK, CQI, scheduling requests) when the UE has no PUSCH to piggyback on. A PDCCH is addressed by scrambling its CRC with a 16-bit RNTI (e.g. C-RNTI, SI-RNTI, P-RNTI, RA-RNTI), so a UE decodes only the DCI meant for it. Two further control channels round out the downlink control region: the PCFICH, which tells the UE how many symbols (1–3, or up to 4 on the narrowest bandwidths) the control region occupies, and the PHICH, which carries the uplink HARQ ACK/NACK.

The Downlink Transmit Chain, Step by Step

The best way to understand the PHY is to follow one downlink transport block from the MAC all the way to the antenna. Each stage has a single job, and the stages are pipelined in a fixed order defined across 36.212 (coding) and 36.211 (physical mapping).

Transport block from MAC (per 1 ms TTI) CRC attachment Code-block segmentation (+ per-CB CRC) Turbo coding (rate 1/3) Rate matching (+ HARQ redundancy version) Scrambling Modulation (QPSK / 16QAM / 64QAM) Layer mapping Precoding (antenna ports) Resource-element mapping OFDM modulation (IFFT + CP) → antenna TS 36.212 TS 36.211
Figure 1. The LTE downlink transmit chain. The coding stages (CRC through rate matching) live in TS 36.212; the physical stages (scrambling through OFDM) live in TS 36.211.

Walking the pipeline: CRC attachment appends a 24-bit checksum (the gCRC24A polynomial) to the whole transport block so the receiver can detect errors and drive HARQ. Code-block segmentation then splits a large transport block into smaller code blocks — the turbo coder has a maximum input size of 6144 bits, so anything bigger is cut into pieces, each getting its own 24-bit CRC (gCRC24B) so the receiver can tell which code blocks failed; filler bits pad the first block up to a valid turbo interleaver size (one of 188 defined block lengths, 40–6144 bits). Turbo coding adds redundancy: a rate-1/3 turbo code — two 8-state constituent convolutional encoders separated by a Quadratic-Permutation-Polynomial (QPP) internal interleaver, decoded iteratively — is the LTE workhorse, producing three output streams (one systematic, two parity), while a lighter tail-biting convolutional code (constraint length 7, rate 1/3) protects small control payloads like the PBCH, PCFICH and PDCCH. Rate matching punctures or repeats the coded bits to fit the number of resource elements the scheduler allocated, using a circular buffer, and it is here that the HARQ redundancy version (RV 0–3) is selected, so each retransmission can send a different starting point in that buffer.

From there the chain is physical. Scrambling multiplies the bits by a cell-and-UE-specific Gold sequence (initialised from the C-RNTI, cell ID and slot) so neighbouring cells look like mutual noise, spreading interference rather than letting it correlate. Modulation maps groups of bits onto QPSK (2 bits/symbol), 16QAM (4), 64QAM (6) or, from Rel-12, 256QAM (8) constellation symbols — higher order packs more bits per symbol but needs a cleaner channel (higher SINR). Layer mapping distributes the modulation symbols across one or more of up to 8 MIMO layers (up to two codewords), and precoding combines those layers onto the physical antenna ports — together they are how spatial multiplexing and transmit diversity happen. Resource-element mapping then places each symbol on a specific subcarrier and OFDM symbol in the resource grid, carefully stepping around the REs reserved for the CRS and other signals. Finally the OFDM modulator (an IFFT of up to 2048 points plus a cyclic prefix) turns the filled grid into the time-domain waveform sent from the antenna.

The Uplink Chain and the 1 ms TTI

The uplink chain is nearly identical to the downlink — CRC, code-block segmentation, turbo coding, rate matching, scrambling, and modulation all appear in the same order — with one structural twist and a few relabellings. The twist is the DFT-spread (transform-precoding) stage: after modulation, the symbols destined for the PUSCH pass through a DFT that spreads them across the assigned subcarriers before they reach the OFDM modulator. That single inserted transform is what turns OFDMA into the low-PAPR SC-FDMA the UE needs, as described above. The data itself is the UL-SCH riding on the PUSCH, with uplink control multiplexed in or carried separately on the PUCCH.

💡

Where the DFT sits: in the downlink, modulation is followed directly by layer mapping and OFDM. In the uplink, a DFT is slipped in between modulation and RE mapping. Everything else — coding, scrambling, the IFFT, the cyclic prefix — is shared machinery. One consequence of the DFT constraint: an uplink allocation must be a set of RBs whose count factorises as 2a·3b·5c (so the DFT size stays efficient), which is why not every RB count is a legal PUSCH grant.

Timing is where LTE is deliberately rigid. The subcarrier spacing is fixed at 15 kHz, which cascades into everything: an OFDM symbol lasts about 66.7 ยตs (1 / 15000 s) plus its cyclic prefix, a resource block is 12 subcarriers (180 kHz) by one slot, one slot is 0.5 ms, two slots make a 1 ms subframe, and ten subframes make a 10 ms radio frame. That 1 ms subframe is the TTI — the fundamental scheduling and transmission interval. Every transport block corresponds to one TTI, HARQ timing is counted in TTIs (FDD downlink uses a fixed 8-TTI HARQ round-trip), and the whole transmit chain above runs once per TTI per transport block. Because there is only one numerology, the frame timing and resource grid are identical for every LTE deployment: simpler to build, at the cost of the flexibility NR later added.

How LTE PHY Differs from NR

If you already know 5G NR, the fastest way to fix LTE in memory is by contrast. NR kept the same overall architecture — transport channels above, physical channels below, an OFDM-based transmit chain — but changed three things that ripple through the whole PHY.

🔀

LTE ↔ NR: LTE is a fixed physical layer — one 15 kHz numerology, one 1 ms TTI, turbo coding, an always-on CRS, SC-FDMA on the uplink. NR is a parameterised one — a menu of numerologies (2μ × 15 kHz), slot lengths that shrink with μ plus mini-slots, LDPC for data and polar for control, a "lean" carrier with no always-on reference signal, and a choice of CP-OFDM or DFT-s-OFDM in the uplink. Every LTE constant below becomes an NR configuration option.

AspectLTE5G NR
NumerologyFixed 15 kHz subcarrier spacing everywhereScalable: 15/30/60/120/240 kHz (2μ × 15 kHz)
TTIFixed 1 ms subframeSlot length shrinks with numerology; mini-slots for low latency
Data channel codingTurbo code (rate 1/3)LDPC for data, polar for control
Reference signalsAlways-on cell-wide CRSUE-specific DM-RS; no always-on CRS (lean carrier)
Uplink waveformSC-FDMA onlyCP-OFDM or DFT-s-OFDM (network chooses)

The coding change is the one interviewers love: LTE uses turbo coding for the shared data channels, while NR replaced it with LDPC (Low-Density Parity-Check) codes, which decode more efficiently at the very high throughputs and large block sizes NR targets, and polar codes for control. The reference-signal change is just as consequential: LTE is CRS-based, transmitting a cell-wide reference signal continuously whether or not there is traffic, whereas NR is deliberately "lean," relying on UE-specific DM-RS that is only sent when data is scheduled — better energy efficiency and less always-on interference. And where LTE fixes one numerology, NR offers a menu so it can serve both wide mmWave carriers and ultra-low-latency traffic. LTE's single 15 kHz choice was a good fit for the sub-6 GHz bands and delay spreads it targeted; NR simply needed more range.

⚠ Common pitfalls / gotchas

  • Confusing transport channels with physical channels. DL-SCH is a transport channel; PDSCH is the physical channel that carries it. Saying "the UE decodes the DL-SCH" is loose — it decodes the PDSCH.
  • Assuming CRS behaves like NR DM-RS. LTE CRS is always on and cell-wide (measurement and demodulation both key off it); NR DM-RS is UE-specific and only present when data is scheduled. Carrying the NR mental model back to LTE breaks reasoning about interference and cell-search.
  • Forgetting the code-block CRC. A large transport block is segmented and each code block gets its own CRC. HARQ retransmits the whole transport block, but the per-CB CRC is what lets early-termination decoders stop once every block passes.
  • Treating higher modulation as always better. 256QAM only helps above a high SINR threshold; below it, the block error rate makes a lower order with more redundancy deliver more throughput.

Summary

The LTE physical layer is a single, fixed machine with one customer. Upward it offers the MAC six transport channels — DL-SCH, BCH, PCH, MCH in the downlink and UL-SCH, RACH in the uplink — and takes a transport block once per 1 ms TTI. Downward it exposes physical channels (PDSCH, PDCCH, PBCH, PUSCH, PUCCH, PRACH…) and physical signals (CRS, PSS/SSS, DM-RS, SRS), and everything in between — CRC, turbo coding, rate matching, scrambling, modulation, layer mapping, precoding, RE mapping, OFDM — exists to move that block reliably across the air.

Two design choices define the LTE PHY: OFDMA down, low-PAPR SC-FDMA up (protecting the UE's power amplifier), and a single 15 kHz numerology that fixes the whole frame and grid so every deployment shares one shape. The 36.2xx family documents it — 36.201 the map, 36.211 channels, 36.212 coding, 36.213 procedures, 36.214 measurements.

If you remember the transport-to-physical mapping, the order of the transmit chain, and the three things NR later made configurable (numerology, coding, reference signals), you can reconstruct almost any LTE PHY answer from first principles.

Quick Q&A

Q&A Quick Q&A

Q. What does the physical layer actually hand up to the MAC?

A. Transport channels — in the downlink DL-SCH, BCH, PCH and MCH; in the uplink UL-SCH and RACH. The MAC delivers a transport block per 1 ms TTI over a transport channel and never deals with subcarriers, coding or modulation directly.

Q. Why does LTE use SC-FDMA on the uplink but OFDMA on the downlink?

A. SC-FDMA (DFT-spread OFDM) has a much lower Peak-to-Average Power Ratio than OFDMA. Low PAPR lets the battery-powered UE's power amplifier run efficiently near saturation, improving uplink coverage and battery life. The eNB on the downlink has ample power, so it can afford OFDMA's higher PAPR in exchange for easier two-dimensional scheduling.

Q. Which 36.2xx spec would you open to check how turbo coding and rate matching work, versus HARQ timing?

A. 36.212 for multiplexing and channel coding (CRC, code-block segmentation, turbo/convolutional coding, rate matching). 36.213 for physical-layer procedures such as HARQ operation, power control and CQI reporting.

Q. What is the difference between a physical channel and a physical signal?

A. A physical channel (e.g. PDSCH, PBCH, PUSCH) carries information from higher layers or Layer-1 control. A physical signal (e.g. CRS, PSS/SSS, DM-RS) carries no higher-layer data; it exists only so the receiver can synchronise, estimate the channel, or measure signal quality.

Q. Name the extra step in the uplink transmit chain and why it is there.

A. A DFT-spread (transform precoding) stage inserted just before OFDM modulation. It makes the transmitted waveform single-carrier-like, lowering PAPR so the UE's power amplifier is more efficient.

Q. Give two things NR changed relative to the LTE PHY.

A. NR replaced turbo coding with LDPC (data) and polar (control) codes, and dropped the always-on CRS in favour of UE-specific DM-RS. NR also made the numerology scalable rather than fixing it at 15 kHz.

Where the physical layer connects

This overview sets the stage for the concrete structures the PHY builds on — the timing skeleton, the two-dimensional resource map, and the specific channels that ride on it.

Frame Structure — slots, subframes and the 10 ms radio frameResource Grid — subcarriers, symbols and resource blocksPhysical Channels — PDSCH, PUSCH, PDCCH and the rest