Architecture ▸loading the recorded archive…Slice scenario — subscription × requested NSSAI
Set two independent inputs: which slices the subscription (UDM/UDR) allows, and which slices the UE requests (standing in for URSP — the emulator has no URSP engine, so the Requested NSSAI is set directly here). The AMF then intersects the two: requested slices that are also subscribed get admitted (Allowed NSSAI); the rest are rejected (Rejected NSSAI, cause NOT_AVIALABLE_IN_PLMN). Registration itself never fails — it always falls back to the default slice. The result below is predicted from this logic, then confirmed on the wire by the tester. This is an archive: every combination was run once on the lab stack and recorded (fresh capture per run) — ▶ Show loads that recording.
Visited network supports
Subscription (UDM/UDR) — ● = default slice
UE Requested NSSAI
The guaranteed flow is triggered by the UE requesting the dedicated urllc-gbr DNN (with SST 2). The home PCF returns the GBR pcc_rule keyed on the S-NSSAI + DNN pair — a PCF policy is all-or-nothing per subscriber, so GBR lives on its own DNN (the plain urllc DNN stays non-GBR). The SMF then adds a dedicated QoS flow (QFI 2, 5QI 82) via a home-routed PDUSessionResourceModify — no AF. Available when SST 2 is both subscribed and requested (so it carries the PDU).
NRF directory
NF directory — how each consumer reaches a target: 🔄 mirrored via NRF subscription (Nnrf_NFManagement, intra-PLMN) · 🔎 discovered on demand (Nnrf_NFDiscovery) · 🌐 cross-PLMN via N32/SEPP. Each NF/SCP keeps its own cache — no single shared one.
SBI message ladder — one line per request→response