Registration — How a device becomes known to the core

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

The device — identity, state, mobility

Where it sits

Sits atLevel 11 of the hierarchy · The device — identity, state, mobility · explained
Learn first5G AKA · Initial access · RM state — 31 concepts in the full chain, see the paths
UnlocksUE capability
Primary clauseTS 24.501 §5.5.1, TS 23.502 §4.2.2.2
Used inref-ue-state 14 · ref-ue-mobility 4 · index 3 · ref-core 3 · ref-ue-identity 2
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 procedure by which a device becomes known to the core: authenticated, authorised, located, and given a temporary identity. TS 24.501 §5.5.1 for the protocol, TS 23.502 §4.2.2.2 for the system procedure. Nothing else can happen until it has succeeded — no PDU session, no data, no reachability.

The chain, from radio silence to registered:

  1. Cell selection — find a suitable cell of a PLMN the device may use, and camp on it.
  2. Initial access — SSB, PBCH, system information, PRACH, and an RRC connection.
  3. Registration Request — a NAS message carrying a SUCI or a 5G-GUTI, the Requested NSSAI, and the device's capabilities.
  4. AMF selection — the RAN picks an AMF; the NSSF may decide a different one must serve the requested slices, and the registration is re-routed.
  5. Authentication — 5G AKA via the AUSF and UDM, which de-conceals the SUCI.
  6. Subscription retrieval — the AMF fetches subscription data from the UDM and registers itself there as the serving AMF.
  7. Registration Accept — carrying the Allowed NSSAI, a TAI list, and normally a fresh 5G-GUTI.

Step 6 is the one that is easy to skip past and hard to do without. The UDM is not only asked who is this subscriber — it is told which AMF is now serving them (TS 23.501 §6.2.7: "UE's Serving NF Registration Management"). That reverse index is how anything arriving from outside finds the device later. Registration is as much about the network learning where to find you as about you being admitted.

Three reasons to do it again, per TS 23.501 §5.3.2.1: periodically, "in order to remain reachable"; upon mobility, when the device leaves its TAI list; and "to update its capabilities or re-negotiate protocol parameters".

Periodic registration is a liveness check with a real cost. Every registered device must check in on a timer, whether or not it has anything to say, or the AMF cannot distinguish a device that left from one that is quietly camped. Set the timer short and a network of millions of idle devices generates continuous signalling for nothing; set it long and the AMF holds stale contexts. It is the same trade as the TAI list size, on the time axis rather than the space one.

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 Registration (level 11) you first need 31 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 Registration: RM state, Initial access, 5G AKA.
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 · Registration Top · Concept map · Hub