Physical layer — Layer 1 — what turns a transport block into radio

5G Systems Notes · Concept map · Physical layer Route · Hierarchy · Index · All concepts · Hub

The protocol stack

Where it sits

Sits atLevel 4 of the hierarchy · The protocol stack · explained
Learn firstResource element — 4 concepts in the full chain, see the paths
UnlocksTransport block
Primary clauseTS 38.202 §4
Used innr-pdsch 10 · index 5 · ref-stack 4 · nr-frame-structure 1 · nr-srs 1 · ref-system 1
Scanned from the notes at page load and joined with terms.json; nothing on this card is typed by hand.

What it is

What it is. Layer 1 — everything that turns a transport block into radio and back. TS 38.202 is the short specification that defines it as a service rather than as machinery: clause 4.1 says the physical layer offers data transport to higher layers, accessed through transport channels via the MAC sublayer.

The functions, from TS 38.202 clause 4.2 — this is the whole job, in eleven lines:

Error detection on the transport channel and indication to higher layers · FEC encoding/decoding · hybrid ARQ soft-combining · rate matching of the coded transport channel to physical channels · mapping onto physical channels · power weighting · modulation and demodulation · frequency and time synchronisation · radio characteristics measurements and indication to higher layers · MIMO antenna processing · RF processing.

Every one of those is a section of another note in this folder. Error detection is PDSCH §4.1; FEC and rate matching are §4.2–§5; modulation is ref-modulation §1; soft-combining is PDSCH §12; synchronisation is the SSB story in frame structure §9.1.

The boundary is the interesting part. The physical layer never learns what a transport block contains — see PDSCH §2.2. Add a new service above and layer 1 needs no change, because it never looked inside. That opacity is what makes the whole stack extensible, and it is why this reference note can describe five sublayers without any of them re-describing the radio.

Read on

This concept was first written up in ref-stack, which reads the whole group as one argument.

Widget not found: sim_status

Before this concept, the hierarchy says to learn the following — the full chain, in order:

To understand Physical layer (level 4) you first need 4 other concepts. Read them in this order — everything on one line can be read in any order, but no line before the one above it:
Immediately before Physical layer: Resource element.
Keep going — where this sits on the route
The route is every concept in the folder ordered by level, so nothing here needs anything after it. Computed at page load from terms.json; the same numbering as the route page.
5G Systems Notes · Concept map · Physical layer Top · Concept map · Hub