NAS — The protocol between the device and the core, which the RAN only carries

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

The device — identity, state, mobility

Where it sits

Sits atLevel 8 of the hierarchy · The device — identity, state, mobility · explained
Also writtenNon-Access Stratum · non-access stratum
Learn firstAMF · RRC — 13 concepts in the full chain, see the paths
Unlocks5GMM · 5GSM
Primary clauseTS 24.501 §4
Used inref-ue-state 15 · ref-core 6 · index 4 · ref-session 3 · ref-ue-identity 1 · ref-ue-mobility 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. The Non-Access Stratum — the protocol between the device and the AMF, which the radio network carries and is required not to understand. TS 24.501. The name is the definition: everything not in the access stratum, the access stratum being RRC and everything below it.

The split, stated plainly:

Access stratum Non-access stratum
Between device and base station device and AMF
Protocol RRC (TS 38.331) NAS (TS 24.501)
About the radio — measurements, bearers, BWPs the subscription — registration, sessions, mobility
Changes when you change cell yes, constantly no
Ciphered by PDCP the AMF itself

NAS is carried inside RRC over the air, and inside N2 beyond it — and neither leg reads it. That is why N1 is drawn as a reference point between the device and the AMF even though no such link physically exists. The base station relays an opaque blob.

And it is separately ciphered. TS 23.501 §6.2.1 gives the AMF "NAS ciphering and integrity protection" — so NAS is protected between the device and the core, independently of the PDCP ciphering protecting it over the radio. A compromised base station sees neither.

Why the layering pays. A device changing cell renegotiates the entire access stratum and changes nothing about NAS: it stays registered, its sessions stay up, its security context stands. Mobility becomes a radio-layer event that the subscription layer never sees.

Two protocols inside it, and they behave differently — TS 24.501 defines both:

5GMM, mobility management, which the AMF does read; and 5GSM, session management, which the AMF forwards without reading to the SMF. One protocol family, two state machines, two audiences.

Read on

This concept is read as part of one argument in ref-ue-state, alongside the rest of its group.

Widget not found: sim_status

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

To understand NAS (level 8) you first need 13 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 NAS: RRC, AMF.
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 · NAS Top · Concept map · Hub