>
HomeLTE 4GPHY — Physical LayerPhysical Channels
📶 PHY — Physical LayerBeginner

Physical Channels & Signals in LTE 4G

PDSCH/PDCCH/PCFICH/PHICH/PBCH downlink and PUSCH/PUCCH/PRACH uplink — what each channel carries.

📚 3GPP-basedTS 36.211TS 36.212

Everything the LTE air interface does — carrying your data, telling you where that data sits, syncing your phone to the cell, acknowledging what you sent, sounding the channel — is divided across a fixed roster of named physical channels and physical signals. Learn the roster once and the whole downlink and uplink stop looking like alphabet soup. This page walks every channel and every signal in both directions, then ties them back to the transport channels they carry. It is grounded in TS 36.211 (physical channels and modulation) and TS 36.212 (multiplexing and channel coding).

Introduction

The LTE physical layer (TS 36.211) is where bits finally become radio. Above it, the MAC hands down transport channels — abstract pipes like "downlink shared data" or "the broadcast channel" — and the physical layer's job is to code, modulate, and map those pipes onto real OFDM resource elements in a 1 ms subframe. It does that through a small, fixed set of physical channels. Alongside them it transmits physical signals, which carry no higher-layer payload and exist only so the receiver can find the cell, estimate the channel, and measure quality.

This roster is used constantly and everywhere in the UE lifecycle. From the first moment a modem powers on it is reading physical signals (PSS/SSS/CRS) and the broadcast channel (PBCH); once connected, every scheduled millisecond involves PCFICHPDCCHPDSCH on the downlink and PUCCH/PUSCH on the uplink. Knowing which channel does what — and which ones carry a transport channel versus pure L1 control — is the mental map underneath almost every other LTE topic.

It matters because nearly every "why won't this decode?" question resolves to one channel. A UE that cannot read PCFICH cannot find the control region; one that cannot read PDCCH never learns where its PDSCH is; one whose CRS estimate is poor mis-equalises everything. Get the roster straight and the rest of the air interface becomes legible.

Why the channel roster is needed

💡

In plain words: think of the air interface as a busy shared warehouse. You cannot just shout your parcel into the room. There is a public address system that says how the floor is laid out today (PCFICH), a dispatcher who tells each worker which shelf their parcel is on (PDCCH), the shelving where parcels actually sit (PDSCH/PUSCH), a receipt desk that confirms deliveries (PHICH/PUCCH), and painted floor markings everyone navigates by (the physical signals). Each has one job; the system only works because the jobs are separated.

Concretely, a shared radio channel has to solve several problems at once. It must let one base station serve many UEs from the same spectrum, so it needs a scheduler and a way to signal its decisions (PDCCH carrying DCI). It must let a receiver that has never seen the cell find it and lock timing (PSS/SSS) and then estimate the channel before decoding anything (CRS/DMRS). It must carry bulk data efficiently (PDSCH/PUSCH) and small control messages cheaply without stealing a whole data grant (PCFICH, PHICH, PUCCH). And it must give a brand-new UE a way to get onto the network before it has any dedicated resources (PRACH). The roster is exactly the minimal set of specialised channels that covers those jobs.

What

A fixed set of physical channels (bit-carrying) and physical signals (known patterns) that together implement scheduling, data transfer, acknowledgement, synchronisation and measurement on the LTE grid.

Why

A shared medium needs separated, purpose-built channels: one receiver must be able to find the cell, learn where its data sits, decode it, and acknowledge it — each a distinct job.

How

TS 36.211 assigns each channel and signal specific resource elements per subframe; the UE reads signals first to synchronise and equalise, then reads the control channels, then the data.

Channels vs Signals — the two kinds of thing on the grid

LTE maps everything onto a time/frequency grid of resource elements: 12 subcarriers by one slot form a resource block, and each subframe is 1 ms of 14 OFDM symbols (normal cyclic prefix, 7 symbols per 0.5 ms slot; extended CP gives 12 symbols per subframe / 6 per slot). Two categories of thing live on that grid, and getting the split straight is the first thing an interviewer checks.

A physical channel carries information that came down from higher layers — user data, control commands, system information. Physical channels have a payload that originated above the physical layer (or, for a few pure-L1 control channels, was generated inside the physical layer to serve higher-layer scheduling). A physical signal carries no higher-layer payload at all; it is a known pattern that exists purely so the physical layer can function — synchronisation, channel estimation, measurement, and positioning.

What

Physical channels (PDSCH, PDCCH, PCFICH, PHICH, PBCH, PMCH, PUSCH, PUCCH, PRACH) carry bits; physical signals (PSS, SSS, CRS, DMRS, CSI-RS, PRS, SRS) carry known patterns the receiver already expects.

Why

A receiver cannot decode data until it has found the cell, aligned its timing, and estimated the radio channel. Signals do that groundwork; channels then ride on top of the estimate.

How

Each channel and signal is assigned specific resource elements per subframe by TS 36.211. The UE knows the fixed positions of the signals, uses them to measure and equalise, then reads the channels.

🎯

One-line test: if a higher layer put information into it, it is a channel; if it is a fixed known pattern the receiver measures against, it is a signal. The lone subtlety is that PDCCH, PCFICH and PHICH are channels whose payload is generated inside L1 itself — they still count as channels because they carry information the receiver must decode, not a reference pattern it correlates against.

Downlink Physical Channels

The downlink carries six physical channels. The trick to remembering them is that most of them exist just to make the one that matters — PDSCH — decodable, plus one specialist channel (PMCH) for broadcast/multicast services.

PDSCH (Physical Downlink Shared Channel). The workhorse. It carries actual user data and most higher-layer signalling, plus paging and the system information blocks (SIBs). "Shared" means it is dynamically split among UEs subframe by subframe by the scheduler. Everything else on this list is essentially plumbing that tells you where your PDSCH is, or acknowledges what you sent. PDSCH lives in the data region of the subframe, after the control region, and is demodulated using either CRS or (in the newer transmission modes) UE-specific DMRS. It supports QPSK, 16-QAM and 64-QAM from Rel-8 (256-QAM added in Rel-12), and turbo coding for the transport block.

PDCCH (Physical Downlink Control Channel). Carries Downlink Control Information (DCI) — the scheduling messages. A DCI is either a DL assignment ("your PDSCH is at these resources, this MCS, this HARQ process") or an UL grant ("you may transmit PUSCH here"). The main LTE DCI formats are format 0 (UL grant), 1/1A/1B/1C/1D (various DL assignments; 1A is the compact "fallback" format), 2/2A/2B/2C/2D (spatial-multiplexing DL), and 3/3A (TPC power-control commands). Each DCI's CRC (16 bits) is masked with a UE's RNTI — e.g. C-RNTI for dynamic user data, SI-RNTI for system information, P-RNTI for paging, RA-RNTI/Temporary C-RNTI for random access, SPS-C-RNTI for semi-persistent scheduling — so a UE only acts on the DCIs addressed to it. A PDCCH is built from aggregations of Control Channel Elements (CCEs), each 9 Resource Element Groups (36 REs); the aggregation level is 1, 2, 4 or 8 CCEs, with more CCEs giving more robust coding for a UE in poor coverage. It carries no transport channel — the DCI is generated inside the physical layer. (Rel-11 added the EPDCCH, which lives in the PDSCH region rather than the front control region.)

PCFICH (Physical Control Format Indicator Channel). Carries a single value, the CFI (Control Format Indicator), of 1, 2, or 3. That number tells the UE how many OFDM symbols at the start of the subframe form the control region — i.e. how many symbols hold PDCCH/PHICH/PCFICH before PDSCH begins. The two-bit CFI is coded into a 32-bit block and carried in exactly four Resource Element Groups (16 REs) in the first OFDM symbol, quadrature-spread across the whole band so the UE can always find it. The UE must read PCFICH first, because it defines the boundary for everything else in the subframe. (In the narrowest bandwidth, ≤10 RBs, the actual control span is CFI+1 symbols, but the principle of "how big is the control region" is unchanged.)

PHICH (Physical HARQ Indicator Channel). Carries the 1-bit HARQ ACK/NACK for uplink transmissions. When the UE sends data on PUSCH, the eNB replies on PHICH: ACK means "received, done," NACK means "resend." It is the downlink acknowledgement channel for uplink HARQ, it lives inside the control region, and it too carries no transport channel — just the single HARQ indicator bit. Many PHICHs are code-multiplexed into one PHICH group (a set of REGs) using orthogonal length-4 (normal CP) or length-2 (extended CP) sequences; the number of groups is scaled by the Ng parameter (one of {1/6, 1/2, 1, 2}) broadcast in the MIB.

PBCH (Physical Broadcast Channel). Carries the MIB (Master Information Block) — the small, most-essential system parameters: downlink system bandwidth, the PHICH configuration, and the System Frame Number (SFN). The MIB is only 24 bits, protected by a 16-bit CRC, tail-biting convolutionally coded and QPSK-modulated. PBCH sits in the centre 72 subcarriers around the sync signals, in the first four OFDM symbols of slot 1, so a UE that has just found the cell can read it without yet knowing the full bandwidth. Its 40 ms transmission is split into four self-decodable copies, one per radio frame, so a UE can often decode it from a single copy.

PMCH (Physical Multicast Channel). The specialist. It carries MBMS (Multimedia Broadcast Multicast Service) content — the same stream sent to many UEs at once, such as broadcast TV or emergency messaging. PMCH is transmitted in MBSFN (Multicast/Broadcast Single Frequency Network) subframes, where multiple synchronised cells send identical waveforms so the UE sees them as one strong multipath signal. It uses an extended cyclic prefix and its own MBSFN reference signal for demodulation rather than CRS, and it never mixes with unicast PDSCH in the same subframe region.

📘

Read order in a normal subframe: PCFICH (how big is the control region?) → PDCCH (where is my data / do I have a grant?) → PDSCH (the data itself). PHICH lives in the control region alongside PDCCH. PBCH and the sync signals recur on their own fixed schedule regardless of scheduling.

DL channelFull nameCarriesNotes
PDSCHPhysical Downlink Shared ChannelUser data, paging, SIBs, most signallingScheduled per subframe; demod via CRS or UE-specific DMRS; QPSK/16-/64-/256-QAM
PDCCHPhysical Downlink Control ChannelDCI: DL assignments and UL grantsCRC masked by RNTI; CCE aggregation 1/2/4/8; no transport channel
PCFICHPhysical Control Format Indicator ChannelCFI = 1/2/3 (control-region size)Read first; 4 REGs / 16 REs in symbol 0
PHICHPhysical HARQ Indicator Channel1-bit HARQ ACK/NACK for uplink PUSCHIn control region; code-multiplexed groups (Ng); no transport channel
PBCHPhysical Broadcast ChannelMIB (bandwidth, PHICH config, SFN)Centre 72 subcarriers; 24-bit MIB; 40 ms period, 4 copies
PMCHPhysical Multicast ChannelMBMS multicast/broadcast contentMBSFN subframes; extended CP; MBSFN RS

The Downlink Control Region — an LTE signature concept

Here is the idea that defines LTE's downlink structure. In every 1 ms subframe (14 OFDM symbols in normal CP), the first 1 to 3 OFDM symbols form the control region. That region is spread across the whole system bandwidth and holds PCFICH, PHICH, and PDCCH. Whatever symbols remain form the data region, which is PDSCH. The exact split — 1, 2, or 3 symbols — is signalled per subframe by the CFI on PCFICH. A lightly loaded cell can use one symbol of control and give the rest to data; a heavily loaded cell scheduling many UEs uses three.

This is a favourite contrast question. In LTE the control region is time-multiplexed at the front of the subframe and spans the full band. In 5G NR that changed: NR replaced the always-full-width front-loaded region with the CORESET (Control Resource Set), configurable in both time and frequency, so control need not occupy the whole bandwidth. LTE's fixed front porch is simpler; NR's CORESET is lower-overhead and more flexible.

🔀

LTE ↔ NR: LTE's control region is always at the front of the subframe and always the full band width; its size (1–3 symbols) is advertised per subframe on PCFICH. NR has no PCFICH at all — the UE learns where control lives from the RRC-configured CORESET and search-space sets, and control can sit anywhere in time/frequency. NR also drops PHICH entirely (uplink HARQ is asynchronous and scheduled by DCI), and replaces LTE's turbo/convolutional coding with LDPC (data) and Polar (control).

One downlink subframe (1 ms, 14 OFDM symbols, normal CP) freq (full band) Control region symbols 0–2 PCFICH / PHICH / PDCCH Data region — PDSCH remaining OFDM symbols time (OFDM symbols) → CFI = 1, 2 or 3 sets this width
Figure 1. An LTE downlink subframe: the first 1–3 symbols (set by the CFI on PCFICH) carry PCFICH/PHICH/PDCCH across the full band; the rest of the subframe is PDSCH.

Downlink Physical Signals

Signals carry no user data — they are known patterns the UE measures against. The downlink has synchronisation signals, reference signals, and one positioning signal.

PSS / SSS (Primary / Secondary Synchronisation Signals). These are how the UE finds a cell in the first place. PSS gives coarse timing (symbol/slot alignment) and part of the physical-cell-ID — the in-group identity N_ID(2) ∈ {0,1,2}, carried by one of three length-63 Zadoff–Chu sequences (roots 25, 29, 34). SSS gives frame timing and the cell-ID group N_ID(1) ∈ {0…167}, built from two interleaved length-31 m-sequences. Together they yield the Physical Cell ID, PCI = 3×N_ID(1) + N_ID(2), giving 504 values (0–503, i.e. 168 groups × 3 sectors), and let the UE align to the cell in both time and frequency. They sit in the centre 62 subcarriers so any UE can find them regardless of the cell's bandwidth.

CRS (Cell-specific Reference Signal). The defining LTE reference signal. It is a known pilot pattern spread across the whole band in (nearly) every subframe, on antenna ports 0–3 (a cell uses 1, 2, or 4 ports). The UE uses CRS for channel estimation — to equalise PDSCH and PDCCH — and for measurements: RSRP, RSRQ, and the CQI report all derive from it. The CRS pattern is shifted in frequency by v-shift = PCI mod 6, so neighbours with suitably chosen PCIs do not stack their pilots on the same subcarriers. Because CRS is "always on" and cell-wide, it is also LTE's biggest source of constant overhead, a problem NR deliberately avoided by making all its reference signals on-demand.

DMRS (UE-specific Demodulation Reference Signal). A reference signal that travels with a specific UE's PDSCH (in transmission modes 7–10, on antenna port 5 and ports 7–14) and is precoded exactly the same way the data is. Because the pilot is precoded identically to the data, the UE can demodulate a beamformed transmission without ever being told the precoder — it simply estimates the effective channel from the DMRS. This is what enables transparent beamforming and is the demodulation basis for the later transmission modes.

CSI-RS (Channel State Information Reference Signal). A sparser pilot introduced in Rel-10, transmitted periodically (configurable periods of several to tens of milliseconds) rather than every subframe, used purely for channel-state feedback. The UE measures CSI-RS to compute and report CQI/PMI/RI, especially for higher-order and multi-antenna MIMO (up to 8 ports in Rel-10, more in later FD-MIMO releases) where CRS alone is not enough. It separates the "measure the channel for feedback" job from the "demodulate my data" job that DMRS handles.

PRS (Positioning Reference Signal). A special reference signal designed for location, added in Rel-9. It is transmitted in configured positioning subframes with a diagonal pattern and high power/muting coordination across neighbour cells, so the UE can hear and time-of-arrival many cells (not just its serving one). It underpins the OTDOA (Observed Time Difference Of Arrival) positioning method — the UE measures reference-signal time differences (RSTD) between cells and the network trilaterates its position.

💡

Mental model: PSS/SSS = "find the cell and lock timing"; CRS = "estimate the channel and measure signal quality"; DMRS = "demodulate my beamformed data"; CSI-RS = "measure the channel for MIMO feedback"; PRS = "let the network locate me."

Uplink Physical Channels and Signals

The uplink mirror is smaller: three physical channels and two signals. LTE uplink uses SC-FDMA (a single-carrier variant of OFDMA, also called DFT-spread-OFDM) to keep the UE's power amplifier efficient, but the channel roster is what you must know cold.

PUSCH (Physical Uplink Shared Channel). The uplink workhorse — carries user data and higher-layer signalling from the UE, and can piggyback control information too. The UE may only transmit on PUSCH when it holds a valid UL grant (a DCI format 0 on PDCCH, or a semi-persistent/configured grant). PUSCH normally sits in the central portion of the band, leaving the edges for control, and supports QPSK/16-QAM/64-QAM (256-QAM from Rel-14).

PUCCH (Physical Uplink Control Channel). Carries Uplink Control Information (UCI) when the UE has no PUSCH to send. UCI is three things: the HARQ-ACK for downlink PDSCH, the Scheduling Request (SR) asking for an uplink grant, and channel feedback (CQI/PMI/RI). It uses one of several PUCCH formats (1/1a/1b for SR and HARQ-ACK, 2/2a/2b for CSI, and Rel-10's format 3 for larger ACK payloads under carrier aggregation). PUCCH lives at the two band edges, hopping between them across the slot for frequency diversity, so it does not fragment the central PUSCH region. It carries no transport channel — UCI is L1/L2 control. If the UE is already transmitting PUSCH, the UCI is multiplexed onto PUSCH instead of using PUCCH.

PRACH (Physical Random Access Channel). Carries the random access preamble — the very first uplink transmission a UE makes when it has no connection, or has lost uplink timing sync. It is how the UE gets onto the network and obtains a timing advance before any dedicated resources exist. It is preamble-only: it carries a chosen preamble sequence (a Zadoff–Chu root sequence with a cyclic shift), not user data — up to 64 preambles per cell, of which some are reserved for contention-free access. The eNB detects the preamble, replies with a Random Access Response, and only then can the UE send real data on PUSCH.

Uplink signals: DMRS and SRS. The uplink demodulation reference signal (DMRS) travels with PUSCH and PUCCH so the eNB can estimate the channel and demodulate what the UE sent — every uplink data or control transmission carries its own DMRS (for PUSCH, in the middle symbol of each slot, symbol 3 under normal CP). The sounding reference signal (SRS) is a wideband pilot the UE sends, normally in the last symbol of a subframe, so the eNB can measure the uplink channel across frequency, even in bands where the UE is not currently transmitting data. SRS feeds uplink frequency-selective scheduling and, in TDD, downlink channel estimation via reciprocity. Both uplink pilots are Zadoff–Chu-based for low peak-to-average power ratio.

🎯

Uplink control lives in two places: no data to send → UCI on PUCCH; already sending data → UCI multiplexed onto PUSCH. And the very first uplink of all goes on PRACH.

UL channelFull nameCarriesPrecondition
PUSCHPhysical Uplink Shared ChannelUser data + optional UCI (UL-SCH)Valid UL grant (DCI 0 / configured grant)
PUCCHPhysical Uplink Control ChannelUCI: HARQ-ACK, SR, CQI/PMI/RINo concurrent PUSCH; no transport channel
PRACHPhysical Random Access ChannelRandom access preamble (RACH)Contention/dedicated RACH occasion

Physical Signals at a Glance

Signals never carry a transport channel and never carry user bits — they are the scaffolding. Here they are side by side across both links, so you can see which job each one does.

SignalDirectionPurposeUsed by / for
PSSDownlinkCoarse timing + in-group ID N_ID(2) (0–2)Initial cell search; part of PCI
SSSDownlinkFrame timing + cell-ID group N_ID(1) (0–167)Completes PCI (0–503)
CRSDownlinkChannel estimation + measurementPDSCH/PDCCH demod; RSRP/RSRQ/CQI
DMRS (DL)DownlinkUE-specific demodulationBeamformed PDSCH, TM 7–10
CSI-RSDownlinkChannel-state feedbackCQI/PMI/RI for MIMO
PRSDownlinkPositioningOTDOA time-difference measurement
DMRS (UL)UplinkDemodulation of uplinkPUSCH / PUCCH channel estimation
SRSUplinkWideband channel soundingUL freq-selective scheduling; TDD reciprocity
💡

Symmetry note: both directions have a DMRS (demodulate what was just sent) but only the downlink has an "always-on" cell-wide pilot (CRS) and only the uplink has a dedicated wideband sounding pilot (SRS). Positioning (PRS) is downlink-only.

Mapping Physical Channels to Transport Channels

Physical channels do not invent their payload — most of them carry a transport channel handed down by the MAC layer (TS 36.212 defines the coding for each). Knowing which physical channel carries which transport channel is a classic exam question, and the mapping is almost one-to-one, with two instructive exceptions.

Transport channelPhysical channelDirectionWhat it is
DL-SCHPDSCHDownlinkDownlink shared data — the bulk of user and signalling traffic, plus SIBs.
BCHPBCHDownlinkThe broadcast channel carrying the MIB.
PCHPDSCHDownlinkPaging — carried on PDSCH, pointed to by a paging DCI (P-RNTI) on PDCCH.
MCHPMCHDownlinkMulticast channel carrying MBMS content in MBSFN subframes.
UL-SCHPUSCHUplinkUplink shared data.
RACHPRACHUplinkThe random-access preamble transport channel.

Notice the two lessons. First, the asymmetry: both DL-SCH and PCH ride on the same physical channel, PDSCH — the DCI on PDCCH (and the RNTI its CRC is masked with) is what tells the UE which one a given PDSCH instance actually is. Second, some physical channels carry no transport channel at all: PDCCH, PCFICH, and PHICH in the downlink, and PUCCH in the uplink. These carry pure physical-layer control — the DCI, the CFI, the HARQ indicator, and the UCI respectively — generated for and by the physical layer rather than passed down as a transport block.

🔀

LTE ↔ NR: the transport→physical mapping is broadly preserved (DL-SCHPDSCH, UL-SCHPUSCH, BCHPBCH, PCHPDSCH, RACHPRACH), but NR retires the MCH/PMCH broadcast pairing of early LTE, folds PBCH into the SSB (with PSS/SSS), and drops the standalone PCFICH and PHICH. NR's control channels are still PDCCH (carrying DCI, now Polar-coded) and PUCCH (carrying UCI), so the "control channels carry no transport channel" principle survives intact.

LTE transport → physical channel mapping Transport channels Physical channels DOWNLINK DL-SCH PCH BCH MCH PDSCH PBCH PMCH PDCCH / PCFICH / PHICH no transport channel — L1 control (DCI / CFI / HARQ indicator) UPLINK UL-SCH RACH PUSCH PRACH PUCCH no transport channel — carries UCI
Figure 2. Transport-to-physical channel mapping. Downlink: DL-SCH and PCH both map to PDSCH, BCH to PBCH, MCH to PMCH. Uplink: UL-SCH to PUSCH, RACH to PRACH. PDCCH/PCFICH/PHICH and PUCCH carry L1 control with no transport channel.

⚠ Common pitfalls / gotchas

  • Calling PDCCH/PUCCH "transport channels." They carry L1/L2 control (DCI/UCI) generated inside the physical layer — there is no MAC transport block behind them.
  • Forgetting that DL-SCH and PCH share PDSCH. The UE tells paging from user data only by the RNTI the PDCCH CRC is masked with (P-RNTI vs C-RNTI), not by the physical channel.
  • Confusing which link acknowledges what. Uplink PUSCH is ACKed on downlink PHICH; downlink PDSCH is ACKed on uplink PUCCH/PUSCH.
  • Assuming NR keeps the same channel set. NR has no PCFICH, no PHICH, and no always-on CRS — carrying LTE habits over leads to wrong answers.

Summary

LTE's air interface is a fixed roster you can hold in your head. On the downlink, six physical channels: PDSCH carries the data (plus paging and SIBs); PDCCH carries the DCI that schedules it; PCFICH tells you how big the control region is; PHICH acknowledges your uplink; PBCH carries the MIB; and PMCH carries MBMS. On the uplink, three: PUSCH for data, PUCCH for UCI, and PRACH for the access preamble. Everything else on the grid is a physical signalPSS/SSS to find the cell, CRS/DMRS/CSI-RS/PRS downlink and DMRS/SRS uplink — carrying no user bits.

Two facts do most of the heavy lifting in interviews: the read order in a subframe (PCFICHPDCCHPDSCH), and the transport-to-physical mapping with its two twists (DL-SCH and PCH both ride PDSCH; the four control channels carry no transport channel). Keep those straight and you can reason about almost any LTE downlink or uplink behaviour from first principles — and you will immediately see what NR kept, moved, or deleted.

Quick Q&A

Q&A Quick Q&A

Q. What does PCFICH tell the UE, and why must it be read first?

A. It carries the CFI (1, 2, or 3), which says how many OFDM symbols at the front of the subframe form the control region. Until the UE knows that boundary it cannot tell where PDCCH/PHICH end and PDSCH begins, so PCFICH is decoded before anything else in the subframe.

Q. Which channel carries HARQ ACK/NACK, and in which direction?

A. It depends on the link. For an uplink PUSCH transmission, the eNB acknowledges on the downlink PHICH. For a downlink PDSCH, the UE acknowledges on the uplink PUCCH (or on PUSCH if it happens to be transmitting data).

Q. Which physical channels carry no transport channel, and what do they carry instead?

A. PDCCH (carries DCI), PCFICH (carries the CFI), PHICH (carries the HARQ indicator), and PUCCH (carries UCI). All four carry pure physical-layer control generated for the L1/L2 scheduling process, not a MAC transport block.

Q. Two transport channels map to PDSCH — which, and how does the UE tell them apart?

A. DL-SCH (user/signalling data) and PCH (paging) both ride on PDSCH. The UE distinguishes them by the DCI on PDCCH: a paging DCI has its CRC masked by P-RNTI, whereas a normal assignment uses the UE's C-RNTI.

Q. What is PMCH for, and how is it transmitted differently from unicast PDSCH?

A. PMCH carries MBMS multicast/broadcast content (the MCH transport channel). It is sent in MBSFN subframes where several synchronised cells transmit identical waveforms, uses an extended cyclic prefix, and is demodulated with the MBSFN reference signal rather than CRS.

Where physical channels connect

The channels here are the surface; the interesting behaviour is in what rides on them — the control messages that schedule you, the data channel itself, and the sync signals that got you onto the cell.

PDCCH & DCI — how assignments and grants are encodedPDSCH — the downlink data channel in detailCell Search — PSS/SSS and acquiring the cell