Skip to content

Advanced Procedures

All Callflows / Sequence diagrams from Level 5

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.

Charging — 5GC Charging (Converged Charging)

Diagram 1 — Procedure — The Call Flow of charging

Original explanation, assumptions and specification references

This is the typical flow of online charging (Quota-based).

sequenceDiagram
    participant UPF
    participant SMF
    participant CHF
    Note over SMF,CHF: (1) At PDU Session establishment: initial charging request
    SMF->>CHF: Nchf_ConvergedCharging_Create<br/>HTTP POST /chargingdata (initial quota request)
    CHF-->>SMF: HTTP 201 Created (ChargingDataResponse, granted quota)
    SMF->>UPF: PFCP Session Modification Request (install URR threshold)
    UPF-->>SMF: PFCP Session Modification Response
    Note over UPF: (2) During communication: metering
    UPF->>SMF: PFCP Session Report Request (Usage Report: quota threshold reached)
    SMF-->>UPF: PFCP Session Report Response
    Note over SMF,CHF: (3) Before Quota exhaustion: additional request
    SMF->>CHF: Nchf_ConvergedCharging_Update<br/>HTTP POST /chargingdata/{ChargingDataRef}/update
    CHF-->>SMF: HTTP 200 OK (ChargingDataResponse, next quota)
    Note over SMF,CHF: (4) At session termination
    SMF->>CHF: Nchf_ConvergedCharging_Release<br/>HTTP POST /chargingdata/{ChargingDataRef}/release
    CHF-->>SMF: HTTP 204 No Content
    Note over CHF: Balance checks and CDR processing are internal CHF actions

Signal Flow (key messages)

# Message Segment Meaning
1 Nchf_ConvergedCharging_Create (HTTP POST /chargingdata) SMF→CHF Charging start. Initial quota request
2 HTTP 201 Created CHF→SMF ChargingDataResponse with initial quota
3 PFCP Session Modification Request/Response SMF⇔UPF Install the URR metering rule
4 PFCP Session Report Request/Response UPF⇔SMF Report usage threshold reached
5 Nchf_ConvergedCharging_Update (HTTP POST /chargingdata/{ChargingDataRef}/update) SMF→CHF Usage report and next-quota request
6 HTTP 200 OK CHF→SMF ChargingDataResponse with next quota
7 Nchf_ConvergedCharging_Release (HTTP POST /chargingdata/{ChargingDataRef}/release) SMF→CHF Session termination and final report
8 HTTP 204 No Content CHF→SMF Release request completed

On credit rejection (insufficient balance)

If, in online charging, the CHF rejects the next Quota (e.g., insufficient balance), the SMF either releases the PDU Session or applies specific handling (e.g., redirection to a payment page). This behavior is operator-policy- and implementation-dependent. The diagram shows one successful response path.


Policy — Policy Control in the 5GC (PCF)

Diagram 1 — (A) Policy application at PDU Session establishment (SMF-originated)

Original explanation, assumptions and specification references

The flow in which, behind PDU Session establishment, the SMF requests policy from the PCF and receives a PCC Rule.

sequenceDiagram
    participant SMF
    participant PCF
    participant UDR
    participant UPF
    Note over SMF,PCF: Part of PDU Session establishment
    SMF->>PCF: Npcf_SMPolicyControl_Create<br/>HTTP POST /sm-policies
    PCF->>UDR: Nudr_DM_Query<br/>HTTP GET /policy-data/ues/{ueId}/sm-data
    UDR-->>PCF: HTTP 200 OK (SessionManagementPolicyData)
    Note over PCF: Generate PCC Rules (internal processing)
    PCF-->>SMF: HTTP 201 Created (SmPolicyDecision)
    Note over SMF: QoS Flow selection is local SMF processing
    SMF->>UPF: PFCP Session Modification Request (PCC/QoS rules)
    UPF-->>SMF: PFCP Session Modification Response

Diagram 2 — (B) AF-originated QoS request (N5)

Original explanation, assumptions and specification references

The flow in which an AF (e.g. IMS's P-CSCF) requests the QoS of a specific service such as voice from the network. This is also behind the voice QoS establishment of VoNR.

sequenceDiagram
    participant AF
    participant PCF
    participant SMF
    participant UPF
    AF->>PCF: Npcf_PolicyAuthorization_Create<br/>HTTP POST /app-sessions (media component)
    PCF-->>AF: HTTP 201 Created (AppSessionContext)
    PCF->>SMF: Npcf_SMPolicyControl_UpdateNotify<br/>HTTP POST {notificationUri}/update
    SMF-->>PCF: HTTP 204 No Content
    SMF->>UPF: PFCP Session Modification Request (updated PCC/QoS rules)
    UPF-->>SMF: PFCP Session Modification Response
    Note over SMF: N1/N2 application of the QoS change is outside this focused policy flow

Signal Flow (main messages)

# Message Segment Meaning
1 Npcf_SMPolicyControl_Create (HTTP POST /sm-policies; HTTP 201 Created, TS 29.512 Clause 4.2.2) SMF→PCF Policy request at PDU Session establishment
2 Nudr_DM_Query (HTTP GET /policy-data/ues/{ueId}/sm-data; HTTP 200 OK, TS 29.504 Clause 5.2.2.2) PCF→UDR Retrieval of subscriber policy data (N36)
3 HTTP 201 Created PCF→SMF Returns the SmPolicyDecision
4 Npcf_PolicyAuthorization_Create (HTTP POST /app-sessions) AF→PCF AF-originated QoS request (N5)
5 Npcf_SMPolicyControl_UpdateNotify (HTTP POST {notificationUri}/update; HTTP 204 No Content, TS 29.512 Clause 4.2.3.2) PCF→SMF Policy notification reflecting the AF request (TS 23.502 Clause 4.16.5.2; see AF / N5)
6 UE Configuration Update (separate procedure) PCF→UE Example of URSP delivery, not included in the two call flows above

An AF request does not necessarily pass as-is

An AF's QoS request is a "request," and the PCF approves/modifies/rejects it in light of subscriber policy and operator policy. Note that the requested QoS is not always granted (implementation/policy dependent).


Roaming — Roaming in 5GC (SEPP / N32)

Diagram 1 — Procedure — Call Flow of roaming Registration

Original explanation, assumptions and specification references

This is a representative flow for VPLMN registration authentication and subscription retrieval. The home AUSF provides authentication, the home UDM provides subscriber data, and SEPPs protect-forward inter-PLMN SBI requests and responses over N32-f.

sequenceDiagram
    participant UE
    participant RAN as NG-RAN
    participant AMF_V as VPLMN AMF
    participant SEPP_V as V-SEPP
    participant SEPP_H as H-SEPP
    participant AUSF_H as HPLMN AUSF
    participant UDM_H as HPLMN UDM
    UE->>RAN: RRCSetupRequest
    RAN-->>UE: RRCSetup
    UE->>RAN: RRCSetupComplete (dedicatedNAS-Message: Registration Request)
    RAN->>AMF_V: NGAP Initial UE Message (NAS Registration Request, SUCI/GUTI)

    Note over AMF_V,UDM_H: (2) HPLMN authentication data and authentication context
    AMF_V->>SEPP_V: Nausf_UEAuthentication HTTP POST /ue-authentications
    SEPP_V->>SEPP_H: N32-f protected forwarding of the SBI request
    SEPP_H->>AUSF_H: Nausf_UEAuthentication HTTP POST /ue-authentications
    AUSF_H->>UDM_H: Nudm_UEAU_GenerateAuthData<br/>HTTP POST /{supiOrSuci}/security-information/generate-auth-data
    UDM_H-->>AUSF_H: HTTP 200 OK (AuthenticationInfo)
    AUSF_H-->>SEPP_H: HTTP 201 Created (UEAuthenticationCtx)
    SEPP_H-->>SEPP_V: N32-f protected forwarding of the SBI response
    SEPP_V-->>AMF_V: HTTP 201 Created (UEAuthenticationCtx)

    Note over AMF_V,UE: (3) UE authentication challenge and response
    AMF_V->>RAN: NGAP Downlink NAS Transport (NAS Authentication Request)
    RAN->>UE: RRC DLInformationTransfer (NAS Authentication Request)
    UE->>RAN: RRC ULInformationTransfer (NAS Authentication Response)
    RAN->>AMF_V: NGAP Uplink NAS Transport (NAS Authentication Response)
    AMF_V->>SEPP_V: Nausf_UEAuthentication HTTP PUT /ue-authentications/{authCtxId}/5g-aka-confirmation
    SEPP_V->>SEPP_H: N32-f protected forwarding of the SBI request
    SEPP_H->>AUSF_H: Nausf_UEAuthentication HTTP PUT /ue-authentications/{authCtxId}/5g-aka-confirmation
    AUSF_H-->>SEPP_H: HTTP 200 OK (authentication result)
    SEPP_H-->>SEPP_V: N32-f protected forwarding of the SBI response
    SEPP_V-->>AMF_V: HTTP 200 OK (authentication result)

    Note over AMF_V,UDM_H: (4) HPLMN access and mobility subscription data
    AMF_V->>SEPP_V: Nudm_SDM_GetAmData<br/>HTTP GET /{supi}/am-data
    SEPP_V->>SEPP_H: N32-f protected forwarding of the SBI request
    SEPP_H->>UDM_H: Nudm_SDM_GetAmData<br/>HTTP GET /{supi}/am-data
    UDM_H-->>SEPP_H: HTTP 200 OK (AccessAndMobilitySubscriptionData)
    SEPP_H-->>SEPP_V: N32-f protected forwarding of the SBI response
    SEPP_V-->>AMF_V: HTTP 200 OK (AccessAndMobilitySubscriptionData)
    AMF_V->>RAN: NGAP Downlink NAS Transport (NAS Registration Accept)
    RAN-->>UE: RRC DLInformationTransfer (NAS Registration Accept)
    UE->>RAN: RRC ULInformationTransfer (NAS Registration Complete)
    RAN->>AMF_V: NGAP Uplink NAS Transport (NAS Registration Complete)

Signal Flow (key Messages)

# Message Segment Meaning
1 Registration Request / Registration Accept UE⇔VPLMN AMF (RRC/NGAP) Registration request and acceptance
2 Nausf_UEAuthentication (HTTP POST /ue-authentications; HTTP 201 Created) VPLMN AMF⇔HPLMN AUSF via SEPP/N32-f Create the authentication context
3 Nudm_UEAU_GenerateAuthData (HTTP POST /{supiOrSuci}/security-information/generate-auth-data; HTTP 200 OK) HPLMN AUSF⇔UDM Request authentication data
4 NAS Authentication Request/Response (RRC/NGAP) VPLMN AMF⇔UE Authentication exchange with the UE
5 Nausf_UEAuthentication 5g-aka-confirmation (HTTP PUT /ue-authentications/{authCtxId}/5g-aka-confirmation; HTTP 200 OK) VPLMN AMF⇔HPLMN AUSF via SEPP/N32-f Confirm the authentication result
6 Nudm_SDM_GetAmData (HTTP GET /{supi}/am-data; HTTP 200 OK) VPLMN AMF⇔HPLMN UDM via SEPP/N32-f Retrieve Access and Mobility Subscription Data

The N32 handshake is a prerequisite

For (2) onward above to hold, V-SEPP and H-SEPP must have established the connection over N32-c and negotiated the protection method (PRINS/TLS) in advance. If N32-c is not up, inter-operator signaling will not pass.

PDU Session structure of Home Routed

In Home Routed, the user plane is routed back to the HPLMN.

graph LR
    UE[UE] --- RAN[NG-RAN]
    RAN --- UPF_V[V-UPF]
    UPF_V -->|N9| UPF_H[H-UPF]
    UPF_H --> DN[Data Network<br/>Breaks out to the external network on the HPLMN side]
    SMF_V[V-SMF] -.control.- UPF_V
    SMF_H[H-SMF] -.control.- UPF_H
    SMF_V -.via N16 SEPP/N32.- SMF_H

Location Service (LCS) — positioning services via GMLC and LMF

Diagram 1 — Procedure — Call Flow (MT-LR)

Original explanation, assumptions and specification references

We understand the representative procedure MT-LR (Mobile Terminated Location Request) in four stages: (A) external request reception → (B) relay to AMF → (C) positioning at LMF → (D) response.

sequenceDiagram
    participant EXT as External LCS client
    participant GMLC
    participant AMF
    participant LMF
    participant UE
    participant RAN as NG-RAN

    Note over EXT,GMLC: (A) External Le request/response protocol details are outside scope#59; no standardized URI is assumed
    Note over GMLC: Requester authorization / privacy check / serving AMF discovery

    Note over GMLC,AMF: (B) Relay to AMF
    GMLC->>AMF: Namf_Location_ProvidePositioningInfo<br/>HTTP POST /{ueContextId}/provide-pos-info
    opt UE is CM-IDLE
        AMF->>RAN: NGAP Paging
        RAN-->>UE: RRC Paging
        UE->>RAN: RRCSetupRequest
        RAN-->>UE: RRCSetup
        UE->>RAN: RRCSetupComplete (dedicatedNAS-Message: Service Request)
        RAN->>AMF: NGAP Initial UE Message (NAS Service Request)
    end
    Note over AMF,LMF: (C) Positioning using Nlmf_Location
    AMF->>LMF: Nlmf_Location_DetermineLocation<br/>HTTP POST /determine-location
    LMF->>AMF: Namf_Communication_N1N2MessageSubscribe<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages/subscriptions
    AMF-->>LMF: HTTP 201 Created (N1N2 subscription)
    LMF->>AMF: Namf_Communication_N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages (N1: LPP RequestLocationInformation)
    AMF-->>LMF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
    AMF->>RAN: NGAP Downlink NAS Transport (NAS DL NAS Transport: LPP RequestLocationInformation)
    RAN->>UE: RRC DLInformationTransfer (NAS message)
    UE->>RAN: RRC ULInformationTransfer (NAS UL NAS Transport: LPP ProvideLocationInformation)
    RAN->>AMF: NGAP Uplink NAS Transport (same NAS message)
    AMF->>LMF: Namf_Communication_N1MessageNotify<br/>HTTP POST {n1NotifyCallbackUri}
    LMF-->>AMF: HTTP 204 No Content
    LMF->>AMF: Namf_Communication_N1N2MessageTransfer<br/>HTTP POST /ue-contexts/{ueContextId}/n1-n2-messages (N2: NRPPa Measurement Request)
    AMF-->>LMF: HTTP 200 OK (cause: N1_N2_TRANSFER_INITIATED)
    AMF->>RAN: NGAP Downlink UE Associated NRPPa Transport (NRPPa MEASUREMENT REQUEST)
    RAN->>AMF: NGAP Uplink UE Associated NRPPa Transport (NRPPa MEASUREMENT RESPONSE)
    AMF->>LMF: Namf_Communication_N2InfoNotify<br/>HTTP POST {n2NotifyCallbackUri}
    LMF-->>AMF: HTTP 204 No Content
    LMF-->>AMF: HTTP 200 OK (Nlmf_Location_DetermineLocation result)
    AMF-->>GMLC: HTTP 200 OK (Namf_Location_ProvidePositioningInfo result)

Explanation of the procedure:

  1. (A) External request reception — the Le protocol/URI between an external client and GMLC is not asserted as a specific standardized API in this diagram. GMLC authorization, privacy checks, and AMF discovery are shown as Notes.
  2. (B) Relay to AMF — the GMLC invokes Namf_Location_ProvidePositioningInfo (HTTP POST /{ueContextId}/provide-pos-info) and receives the location result in an HTTP 200 response.
  3. (C) Positioning at LMF — the AMF invokes Nlmf_Location_DetermineLocation (HTTP POST /determine-location). The LMF uses Namf_Communication N1/N2 subscription and message transfer. For the connected UE, N1N2MessageTransfer returns HTTP 200 OK with N1_N2_TRANSFER_INITIATED. LPP RequestLocationInformation/ProvideLocationInformation is carried in NAS→NGAP→RRC, and UE-associated NRPPa MEASUREMENT REQUEST/RESPONSE is carried in NGAP Downlink/Uplink UE Associated NRPPa Transport (TS 38.413 Clause 8.10.2.1 / Clause 8.10.2.2, TS 38.455 Clause 8.5.1.2 / Clause 9.1.4.1–Clause 9.1.4.2). The AMF returns the N1MessageNotify/N2InfoNotify callbacks to the LMF.
  4. (D) Response — the positioning result returns to AMF in the Nlmf_Location HTTP response and to GMLC in the Namf_Location HTTP response. The external Le response format/transport is outside this diagram.

MO-LR / NI-LR as other patterns

The subject of this chapter is the externally-initiated MT-LR, but there are also MO-LR (Mobile Originated), in which the UE itself requests its own location, and NI-LR (Network Induced, emergency calls, etc.), triggered by the network itself. The skeleton (AMF as hub, LMF for positioning, LPP/NRPPa) is common; the originator and request path differ. The details and conditions of each pattern are to be confirmed in TS 23.273.