A physical channel in 5G NR is a set of resource elements that carries information handed down from the layers above. There are six: PBCH, PDCCH and PDSCH in the downlink, and PRACH, PUCCH and PUSCH in the uplink. PUSCH means Physical Uplink Shared Channel and carries the device's uplink data; PDSCH carries the downlink data; PDCCH carries the instructions that say where both of them are.
Around the channels sit the physical signals: DMRS, PT-RS, CSI-RS, SRS and the synchronization signals. They carry nothing from higher layers. They exist so the receiver can find, measure and demodulate the channels. Both are defined in TS 38.211, and the coding and mapping of data onto them is in TS 38.212.
The six channels at a glance
| Channel | Direction | Carries | Transport channel |
|---|
| PBCH (Physical Broadcast Channel) | Downlink | The MIB: frame number, subcarrier spacing, where to find SIB1 | BCH |
| PDCCH (Physical Downlink Control Channel) | Downlink | DCI: downlink assignments, uplink grants, power control, slot format | None (physical-layer control) |
| PDSCH (Physical Downlink Shared Channel) | Downlink | User data, SIBs, RRC and NAS messages, paging, random access responses | DL-SCH, PCH |
| PRACH (Physical Random Access Channel) | Uplink | The random access preamble | RACH |
| PUCCH (Physical Uplink Control Channel) | Uplink | UCI: HARQ-ACK, scheduling requests, CSI reports | None (physical-layer control) |
| PUSCH (Physical Uplink Shared Channel) | Uplink | User data, RRC and NAS messages, MAC CEs, and UCI when piggybacked | UL-SCH |
Two patterns make the table easier to remember. The shared channels carry transport blocks from MAC, coded with LDPC and protected by HARQ. The control channels carry physical-layer control information (DCI and UCI) with no transport channel above them, coded with polar codes (very small UCI payloads use repetition or Reed–Muller codes instead).
The second pattern: almost nothing moves on a shared channel until PDCCH has said so. Every dynamically scheduled PDSCH and PUSCH starts with a DCI. The exceptions are semi-persistent downlink, configured-grant uplink, and Msg3 of random access, which the random access response schedules.
PDCCH: the scheduler's instructions
PDCCH carries Downlink Control Information. DCI formats 1_0 and 1_1 assign PDSCH, formats 0_0 and 0_1 grant PUSCH, and the 2_x formats are group-common (2_0 for slot format, 2_1 for pre-emption, 2_2 and 2_3 for power control). Each DCI tells the device which PRBs, which symbols, which MCS and which HARQ process to use.
The device doesn't know in advance where its DCI is. It blind-decodes a limited set of candidates inside a CORESET, on a schedule set by a search space, at aggregation levels of 1, 2, 4, 8 or 16 CCEs. The CRC of each DCI is scrambled with an RNTI, so a candidate only decodes for the device it's meant for: C-RNTI for one device, SI-RNTI for system information, P-RNTI for paging, RA-RNTI for random access responses. Our CORESET and search spaces article covers this in detail.
PDCCH uses QPSK only, with its DMRS on three of every twelve subcarriers. When a device misses a PDCCH, it never knows a PDSCH was sent, so it sends no ACK or NACK at all. The gNB sees that as DTX, which is how missed grants show up in a trace.
PDSCH: downlink data, and a lot more than data
PDSCH carries the DL-SCH transport channel, and that means far more than user traffic. SIB1 and the other SIBs, RRC messages like RRCSetup and RRCReconfiguration (with NAS messages inside them), the random access response, and paging all travel on PDSCH.
Modulation goes from QPSK to 256QAM, with 1024QAM added in Release 17. A device can receive up to 8 layers; above 4 layers the transport data is split across two codewords. Time-domain mapping is either type A, which starts at the beginning of the slot with its first DMRS on symbol 2 or 3 (the MIB's dmrs-TypeA-Position), or type B, which can start anywhere and be as short as two symbols for low-latency traffic.
The slot and symbol structure underneath depends on numerology. If 30 kHz versus 120 kHz subcarrier spacing is still hazy, read NR numerology first.
PUSCH: the Physical Uplink Shared Channel
PUSCH is the uplink twin of PDSCH. It carries the UL-SCH: user data, RRC messages like RRCSetupComplete and MeasurementReport, and MAC control elements such as the buffer status report and power headroom report. Msg3 of random access is a PUSCH too.
PUSCH has two waveforms. CP-OFDM supports up to 4 layers. DFT-s-OFDM (transform precoding switched on) has a lower peak-to-average power ratio, so a power-limited device at the cell edge gets more useful power out of its amplifier; it's single-layer only, and it's the only case where π/2-BPSK is allowed. The rest of the modulation range is QPSK to 256QAM.
Scheduling comes in three kinds: a dynamic grant in DCI 0_0 or 0_1, a configured grant set up by RRC (type 1) or by RRC plus a DCI activation (type 2), and the grant inside the random access response for Msg3. When UCI is due in a slot where the device is already sending PUSCH, it's usually multiplexed onto the PUSCH instead of going out on a separate PUCCH.
The uplink is where coverage runs out first. A typical phone transmits at most 23 dBm (power class 3), against tens of watts from the gNB, so PUSCH power headroom and uplink BLER are among the first things to check when users at the edge complain.
PUCCH: feedback on its own channel
PUCCH carries Uplink Control Information when the device has no PUSCH to put it on. UCI is three things: HARQ-ACK for downlink transport blocks, scheduling requests asking for an uplink grant, and CSI reports (CQI, PMI, rank and, for beam management, L1-RSRP).
NR defines five PUCCH formats:
- Format 0: 1–2 symbols, up to 2 bits. Short, quick HARQ-ACK or SR.
- Format 1: 4–14 symbols, up to 2 bits. Same payload, more energy for coverage.
- Format 2: 1–2 symbols, more than 2 bits. Short CSI reports.
- Format 3: 4–14 symbols, more than 2 bits. Large CSI or multi-carrier HARQ-ACK.
- Format 4: 4–14 symbols, more than 2 bits, with several devices sharing the same PRB.
The short formats usually sit in the last symbols of a slot; the long ones spread over more symbols when the link is weak.
PRACH and PBCH: the channels used before a connection exists
PRACH carries a preamble, not data. The device picks one of 64 preambles in a RACH occasion and sends it so the gNB can notice it and measure its timing. Long preambles (839-sample sequences, formats 0–3) are FR1-only and suit large cells; short preambles (139 samples, formats A1–C2) work in FR1 and FR2 and fit inside a slot. The full procedure, Msg1 to Msg4, has its own article in this series.
PBCH travels inside the SS/PBCH block with the PSS and SSS. It carries the MIB, which is sent every 80 ms with repetitions inside that window. The MIB gives the device the system frame number, the subcarrier spacing for initial access, and pdcch-ConfigSIB1, the pointer to CORESET#0 where the DCI for SIB1 is found. Like PDCCH, PBCH is QPSK with polar coding.
The reference signals around them
- DMRS (Demodulation Reference Signal): sent with each channel so the receiver can estimate the channel and demodulate. PDSCH and PUSCH DMRS come in type 1 (up to 8 ports) and type 2 (up to 12), and extra DMRS symbols can be added for fast-moving devices.
- PT-RS (Phase Tracking Reference Signal): tracks phase noise, mostly an FR2 concern.
- CSI-RS (Channel State Information Reference Signal): downlink, up to 32 ports, used for CSI reports, beam management, time-frequency tracking (TRS) and mobility measurements.
- SRS (Sounding Reference Signal): uplink, lets the gNB measure the uplink channel. On TDD it's also how massive MIMO works out downlink beams, using reciprocity.
- PSS and SSS: the synchronization signals that, with PBCH, make up the SSB and give the device its physical cell ID.
Where you'll meet this
In a UE log. QXDM or a vendor trace shows each decoded DCI with its format, RNTI, PRBs and MCS, then the PDSCH or PUSCH result for that HARQ process. Reading a throughput problem usually means walking that chain: was the grant there (PDCCH), was it decoded (PDSCH BLER), and did the feedback come back (PUCCH HARQ-ACK)?
In counters. PRB utilization, BLER and MCS distributions are reported per channel and per direction. A cell with good downlink and poor uplink numbers points at PUSCH power, uplink interference or SRS configuration, not at the scheduler.
In layer 2 debugging. Transport channels are where MAC meets the physical layer. If a MAC CE or an RLC retransmission goes missing, the
PDCP, RLC and MAC walkthrough shows how to follow it down to the PUSCH or PDSCH that carried it.
In interviews. "Which channel carries RRCSetup?" PDSCH. "Where does a scheduling request go?" PUCCH. "Does PDCCH carry user data?" No, only DCI. "What does PUSCH mean?" Physical Uplink Shared Channel, and you now know what it carries.