5G Core Course  /  Course home  /  Module 3 — PDU Sessions End-to-End
3GPP Release 19
MODULE M3 · ~45 MIN · FLAGSHIP

PDU Sessions,
End to End.

Open the pipe that carries every byte — message by message. PDU session anatomy and SSC modes, the full 21-step Establishment flow, CreateSMContext on the wire, how the SMF programs the UPF over N4/PFCP, modification and release, and multi-anchor edge topologies — narrated and fully animated, explained like an expert.

~45minanimated video
21 stepsEstablishment
PDR·FAR·QER·URRthe N4 rules
SSC1·2·3continuity modes
EN·فاkaraoke subs
TS 23.501 §5.6 · TS 23.502 §4.3 · TS 24.501 §8.3 · TS 29.502 · TS 29.244
▶ VIDEO · MODULE 3 · ~45 MIN

PDU Sessions End-to-End — opening the pipe, message by message

The player screen is a live animation stage — scenes fire exactly as the narration reaches them, step by step. Karaoke subtitles in English, two subtitle modes, and fullscreen.

Module 3 · 5G Core Masterclass · the 21-step PDU session
PDU Sessions End-to-End
0:00 / 0:00
REFERENCE · THE IEs & CAUSES IN THIS MODULE
The M3 IE catalogue →
Every information element the video opens — SmContextCreateData, the PDU Session Establishment Request/Accept, the N4 rules, and the 5GSM cause codes — with clause and presence, searchable.
REFERENCE · THE M3 IE CATALOGUE

Every information element in the module

Each message and structured data type the video opens — its interface, direction, purpose and clause. Click any row to open its full Information-Element breakdown. Filter to find any of them.

MessageInterfaceDirWhat it doesClause
TS 23.502 V19 §4.2 · TS 24.501 §8.2 · TS 38.413 (NGAP) · TS 33.501 §6.1
REFERENCE · PDU ANATOMY · SSC · N4 RULES · THE 21 STEPS · TOPOLOGIES

The PDU session, at protocol depth

Everything the video draws, as reference you can scan in a trace: what a session is made of, the four N4 rules that run the user plane, the twenty-one steps grouped into four acts, and the multi-anchor topologies. All spec-cited.

PDU session type — the promise about the traffic (TS 23.501 §5.6.10)

IPv4

  • value 1
  • one IPv4 address

IPv6

  • value 2
  • prefix + SLAAC

IPv4v6

  • value 3
  • both families in one session

Ethernet

  • value 5
  • raw L2 frames · factories, FWA

Unstructured

  • value 4
  • no IP · machine data
SSC mode — what happens to your anchor UPF when you move (TS 23.501 §5.6.9.2)

SSC mode 1 — preserve

  • Anchor UPF never changes; IP address preserved for the life of the session.
  • For voice, VPN — anything that dies if the address changes.

SSC mode 2 — break before make

  • Network releases the old session, then builds a new one.
  • New IP address; stateless apps reconnect.

SSC mode 3 — make before break

  • New anchor built before the old one is removed.
  • Two paths briefly → nothing is lost. The edge-mobility mode.
The four N4 rules — the entire user plane, in four letters each (TS 29.244 §7.5.2)

PDR · eyes

  • How to recognize a packet
  • PDI: interface, F-TEID, UE IP, SDF filters
  • points to FAR / QER / URR
  • §7.5.2.2

FAR · hands

  • What to do: FORW · DROP · BUFF · DUPL
  • Outer Header Creation (GTP-U tunnel)
  • §7.5.2.3 · Apply Action §8.2.26

QER · traffic cop

  • Enforce bit rate: MBR / GBR
  • Gate open/closed · stamp the QFI
  • §7.5.2.5

URR · accountant

  • Count volume / time / events
  • Reporting triggers → SMF → CHF
  • §7.5.2.4
PDU Session Establishment — 21 steps, four acts (TS 23.502 §4.3.2.2.1)
ActStepsWhat happensKey message
1 · request1–5UE asks; AMF selects & calls the SMF; SMF fetches subscription and is born as session ownerNsmf_PDUSession_CreateSMContext
2 · build6–10optional secondary auth; PCF policy; UPF + SSC mode selected; IP assigned; UPF programmed over N4N4 Session Establishment (PDR/FAR/QER/URR)
3 · radio11–16one transfer splits into N2 (radio) + N1 (UE); RRC builds DRBs; radio reports back; N4 modified for downlink; UECM registerNamf_Comm_N1N2MessageTransfer · UpdateSMContext
4 · flow17–21UpdateSMContext ack; status notify; IPv6 Router Advertisement; final policy update; unsubscribe — user data flowsN3 user-plane data
UP path management — one session, many anchors (TS 23.501 §5.6.4)

ULCL — Uplink Classifier

  • UPF inserted in the path; sorts uplink traffic by destination.
  • Edge traffic → local anchor; internet → central anchor. UE sees one IP.
  • §5.6.4.2

Branching Point (IPv6)

  • UE has two IPv6 prefixes; BP UPF steers by source prefix.
  • Same goal, multi-homing flavour. §5.6.4.3

N9 & local PSA

  • N9 tunnels user plane UPF↔UPF (anchor to anchor).
  • A local PSA at the edge serves game/cache/factory apps at low latency.
5GSM cause codes — read these first when a session fails (TS 24.501 §9.11.4.2)
CauseMeaningWhere to look
#26insufficient resourcesUPF / RAN capacity
#27missing or unknown DNNsubscription / DNN config
#28unknown PDU session typeUE request vs support
#29user authentication or authorization failedDN-AAA secondary auth
#43invalid PDU session identityUE / AMF state mismatch
#54PDU session does not existstale session reference

The rule to remember: the SMF is the brain, the UPF is the muscle, and N4 is the nerve between them. The SMF never touches a user packet — it only writes the four rules and ships them over PFCP. Everything else in this module is a variation on that one idea.

TS 23.501 §5.6 · TS 23.502 §4.3 · TS 24.501 §8.3 & §9.11.4 · TS 29.502 · TS 29.244
QUIZ · 10 QUESTIONS

PDU session mastery check

Questions and answers reshuffle every load. 70%+ to consider Module 3 done.