PDCCH — Physical downlink control channel — the assignment
Channels — what carries what
Where it sits
What it is
What it is. The channel that carries the DCI, and therefore the channel that must be decoded before PDSCH can be. TS 38.211 clause 7.3.2. Its content is described in PDSCH §8; this section is about how it is physically built.
Two units, both defined in clause 7.3.2:
REG — resource element group. "a resource-element group equals one resource block during one OFDM symbol" — twelve resource elements, of which three carry the PDCCH's own DM-RS and nine carry data.
CCE — control-channel element. "A control-channel element consists of 6 resource-element groups" — so one CCE is 72 resource elements, 54 of them payload.
Aggregation level is the code rate knob. A PDCCH occupies 1, 2, 4, 8 or 16 CCEs (Table 7.3.2.1-1). The DCI payload is fixed by its format, so more CCEs means a lower code rate and a more robust message:
| Aggregation level | CCEs | REGs | Payload REs | Bits at QPSK | Rate for a 68-bit DCI |
|---|---|---|---|---|---|
| 1 | 1 | 6 | 54 | 108 | 0.63 |
| 2 | 2 | 12 | 108 | 216 | 0.31 |
| 4 | 4 | 24 | 216 | 432 | 0.16 |
| 8 | 8 | 48 | 432 | 864 | 0.079 |
| 16 | 16 | 96 | 864 | 1728 | 0.039 |
PDCCH is always QPSK (clause 7.3.2.4) — there is no MCS field for control, because there is no channel report to base one on at the moment the control message is being sent. Robustness is bought with resources instead of with modulation, which is the whole difference between control and data.
Read on
This concept was first written up in ref-channels, which reads the whole group as one argument.
Before this concept, the hierarchy says to learn the following — the full chain, in order: