Overview & Dictionary Diagrams¶
All Callflows / Sequence diagrams from Level 1 and the dictionary
Scope of the diagrams
These sequence diagrams and their surrounding explanations and caveats are reproduced from the existing lessons. They include simplified and conditional examples, not every specification branch. Read the original explanations for applicability, omitted steps, implementation-dependent details, TS and clause references, and any qualifications marked as requiring verification.
5GC Overview and SBA — The Concept of Service-Based Architecture¶
Diagram 1 — NF discovery via NRF¶
Original explanation, assumptions and specification references
For NFs to freely invoke one another under SBA, there needs to be a mechanism that manages "which NF provides what service, and where (at what address) it is." The NRF (Network Repository Function) fills this role. As the 5GC's NF phone book (registry), the NRF provides the following two things.
- NF Management (registration and management) — at startup, each NF registers with the NRF: "I am such-and-such NF, I provide these services, and I am here." It updates on state changes and removes its registration when it stops.
- NF Discovery — when one NF needs another, it queries the NRF, "tell me the NFs that provide service X," and discovers candidates (addresses, etc.) that match the criteria. From the candidates obtained, it selects the one to actually call.
sequenceDiagram
participant SMF as SMF
participant NRF as NRF (phone book)
participant UDM as UDM
UDM->>NRF: Nnrf_NFManagement_NFRegister<br/>PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID}
NRF-->>UDM: Nnrf_NFManagement_NFRegister response<br/>HTTP 201 Created
SMF->>NRF: Nnrf_NFDiscovery_Request<br/>GET /nnrf-disc/v1/nf-instances?target-nf-type=UDM&requester-nf-type=SMF
NRF-->>SMF: Nnrf_NFDiscovery_Request response<br/>HTTP 200 OK (SearchResult)
SMF->>UDM: Nudm_SDM_Get<br/>GET /nudm-sdm/v2/{supi}/sm-data
UDM-->>SMF: Nudm_SDM_Get response<br/>HTTP 200 OK (SM subscription data)The UDM registers with the NRF; the SMF queries the NRF and then retrieves SM subscription data directly from the UDM over SBI. Operation names are logical labels; HTTP method, URI and status correspond to packets (TS 29.510 Clause 5.2.2.2, Clause 6.2.3.2.3.1; TS 29.503 Clause 5.2.2.2.5).
For the NRF's role, APIs, and related topics, see the dedicated NRF page and the NF Dictionary.
Network Function (NF) Overview — The Design Philosophy of Splitting the 5GC into Functional Components¶
Diagram 1 — discovery — Finding one another via NRF¶
Original explanation, assumptions and specification references
NFs do not use fixed wiring; they dynamically look for their counterpart through the NRF (Network Repository Function). Let's grasp this flow intuitively.
sequenceDiagram
participant SMF as NF instance (e.g. SMF)
participant NRF as NRF
participant AMF as NF instance (e.g. AMF)
Note over AMF,NRF: At startup
AMF->>NRF: Nnrf_NFManagement_NFRegister<br/>PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID}
NRF-->>AMF: Nnrf_NFManagement_NFRegister response<br/>HTTP 201 Created
Note over SMF,NRF: When a counterpart is needed
SMF->>NRF: Nnrf_NFDiscovery_Request<br/>GET /nnrf-disc/v1/nf-instances?target-nf-type=AMF&requester-nf-type=SMF
NRF-->>SMF: Nnrf_NFDiscovery_Request response<br/>HTTP 200 OK (SearchResult)
SMF->>AMF: Namf_Communication_N1N2MessageTransfer<br/>POST /namf-comm/v1/ue-contexts/{ueContextId}/n1-n2-messages
AMF-->>SMF: Namf_Communication_N1N2MessageTransfer response<br/>HTTP 200 OK- Register — At startup, each NF instance registers its own information with the NRF as an NF profile
- Discovery — When an NF needs a counterpart, it queries the NRF specifying criteria (NF type, slice, region, etc.) and is told the matching instances
- Selection — From the returned candidates, select the instance to actually call
The service call is an example where a UE context exists. For the operation-to-HTTP method, URI and status mapping, see TS 29.510 Clause 5.2.2.2, Clause 6.2.3.2.3.1 and TS 29.518 Clause 5.2.2.3.1.
What is an NF profile
An NF profile is the "self-introduction card of that NF instance" registered with the NRF. It includes the NF type, NF Instance ID, the NF services provided, supported slices (S-NSSAI), the address to connect to, and so on. It is easy to understand if you grasp Discovery as the mechanism that narrows down these profiles by criteria. For details on the NRF and SBA themselves, see 5GC Overview and SBA.
Identifier Dictionary — Key Identifiers of 5GC¶
Diagram 1 — Diagram 2: the SUPI → SUCI → 5G-GUTI transformation flow¶
Original explanation, assumptions and specification references
This is the flow in which the identifiers pointing to the same UE change their form for each situation in order to protect privacy. The aim is to minimize exposure of the permanent ID (SUPI).
sequenceDiagram
autonumber
participant UE
participant AMF as AMF/SEAF
participant AUSF
participant UDM as UDM (SIDF)
Note over UE: Permanent ID = SUPI (public-key concealment example)
Note over UE: Conceal SUPI with the public key to generate SUCI
UE->>AMF: Registration Request<br/>(5GS mobile identity = SUCI)
AMF->>AUSF: Nausf_UEAuthentication_Authenticate<br/>POST /nausf-auth/v1/ue-authentications (SUCI)
AUSF->>UDM: Nudm_UEAuthentication_Get<br/>POST /nudm-ueau/v1/{supiOrSuci}/security-information/generate-auth-data
Note over UDM: SIDF deconceals SUCI using the private key
UDM-->>AUSF: Nudm_UEAuthentication_Get response<br/>HTTP 200 OK (SUPI, authentication data)
AUSF-->>AMF: Nausf_UEAuthentication_Authenticate response<br/>HTTP 201 Created (authentication challenge)
Note over UE,AMF: 5G-AKA challenge / response omitted
AMF->>AUSF: Nausf_UEAuthentication_Authenticate<br/>PUT /nausf-auth/v1/ue-authentications/{authCtxId}/5g-aka-confirmation
AUSF-->>AMF: Nausf_UEAuthentication_Authenticate response<br/>HTTP 200 OK (SUPI, authentication result)
Note over AMF: The AMF assigns a 5G-GUTI during registration
AMF-->>UE: Registration Accept<br/>(5G-GUTI)
Note over UE,AMF: Subsequent identification and paging use the 5G-GUTI<br/>(the SUPI is never exposed over the air)How to read the diagram
This example uses public-key concealment and 5G-AKA. The UDM's SIDF recovers the SUPI from SUCI, and the AUSF returns it to the AMF after successful authentication. The AMF assigns 5G-GUTI in Registration Accept. The diagram shows logical UE–AMF NAS messages; transfer via the RAN is omitted (TS 23.502 Clause 4.2.2.2.2; TS 29.509 Clause 5.2.2.2; TS 29.503 Clause 6.3.3.2.4.2). See the Authentication chapter / Security Dictionary.
Timer Dictionary — NAS (5GMM/5GSM) Main Timers and Peripheral Timers¶
Diagram 1 — Reachability / Congestion (Network/UE) Related Timers¶
Original explanation, assumptions and specification references
| Timer | Location | General Role | On Timeout / Expiry | Spec |
|---|---|---|---|---|
| Mobile reachable timer | AMF | Monitors the reachability of a registered UE (restarted on receiving a periodic registration update) | On expiry, considers the UE unreachable and transitions to the monitoring stage | TS 24.501 Clause 5.3.7 / TS 23.501 Clause 5.4.1.1 (to be confirmed) |
| Implicit de-registration timer | AMF | After the mobile reachable timer expires, monitors whether there is no further contact from the UE for an additional period | On expiry, implicit de-registration (implicit de-registration and resource release) | TS 24.501 Clause 5.3.7 / TS 23.501 Clause 5.4.1.1 (to be confirmed) |
| T3346 | UE (5GMM) | Backoff due to congestion control (backoff value attached to a Reject) | Refrains from retrying the relevant procedure until expiry | TS 24.501 Clause 10.2 (to be confirmed) |
Relationship between periodic registration update and implicit de-registration
When the UE sends a periodic registration update (triggered by T3512 expiry), the AMF-side mobile reachable timer is restarted. If the UE does not send an update and the timers expire in the order mobile reachable → implicit de-registration, the AMF implicitly de-registers the UE (releases resources). This is the flow of "update lapse → implicit de-registration." Details of each timer's values and relationships are to be confirmed (TS 24.501 Clause 5.3.7 / TS 23.501 Clause 5.4.1.1).
The figure below shows this T3512 → (update lapse) → mobile reachable → implicit de-registration timer chain in chronological order. The left is normal (the update arrives and restarts), and the right is a lapse (the timers expire in order and cause implicit de-registration).
sequenceDiagram
autonumber
participant UE
participant AMF
Note over UE,AMF: [Normal case] the UE periodically signals it is alive
Note over UE: Non-strictly-periodic example<br/>Start T3512 on entering 5GMM-IDLE
Note over UE: … T3512 expires …
UE->>AMF: Registration Request<br/>(5GS registration type = periodic registration updating)
Note over AMF: Stop the mobile reachable timer in CM-CONNECTED
AMF-->>UE: Registration Accept
Note over UE,AMF: Start the respective timers on return to CM-IDLE<br/>(conditions in TS 24.501 Clause 5.3.7)
Note over UE,AMF: [Loss-of-contact case] when updates stop arriving from the UE
Note over UE: (out of coverage, powered off, etc.)<br/>cannot send updates
Note over AMF: mobile reachable timer expires<br/>→ regard the UE as "unreachable"
Note over AMF: Then start the implicit de-registration timer
Note over AMF: implicit de-registration timer expires<br/>→ <b>implicit de-registration</b> (release resources)How to Read the Figure
In the normal case, expiry of the UE's T3512 triggers a Registration Request indicating periodic registration updating. The diagram shows logical UE–AMF NAS messages, omitting RAN forwarding, for the case where a strictly periodic registration timer is not indicated. In the lapse case, if the UE cannot send an update due to being out of coverage, etc., the two stages mobile reachable timer → implicit de-registration timer expire in order on the AMF side, and ultimately the AMF implicitly de-registers the UE and releases resources. For timer values and conditions, see TS 24.501 Clause 5.3.7.