Skip to content

Mobility & QoS

All Callflows / Sequence diagrams from Level 3

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.

Paging

Diagram 1 — Procedure — Call Flow

Original explanation, assumptions and specification references

This is the heart of this page. The main steps of Network Triggered Paging, starting from the arrival of DL data, are shown in a Mermaid sequenceDiagram. The basis is 3GPP TS 23.502 Clause 4.2.3.3 (Network Triggered Service Request) and TS 38.413 (NGAP Paging) (the fine-grained section numbers are to be confirmed).

Prerequisite: the UE is registered and in CM-IDLE

The UE is assumed to be 5GMM-REGISTERED and in CM-IDLE. If it were CM-CONNECTED, a connection already exists, so Paging is unnecessary and DL data can be delivered directly.

sequenceDiagram
    autonumber
    participant UE as UE (CM-IDLE)
    participant RAN as (R)AN / group of gNBs
    participant AMF
    participant SMF
    participant UPF

    Note over UPF: DL data for the destination UE arrives (DL path not established)
    UPF->>SMF: PFCP Session Report Request<br/>Downlink Data Report
    Note right of UPF: N4 / TS 29.244. The UPF buffers the DL data
    SMF-->>UPF: PFCP Session Report Response
    SMF->>AMF: Namf_Communication_N1N2MessageTransfer<br/>POST /namf-comm/v1/ue-contexts/{ueContextId}/n1-n2-messages
    AMF-->>SMF: Namf_Communication_N1N2MessageTransfer<br/>HTTP 202 Accepted

    Note over AMF: Judges the UE to be in CM-IDLE → decides on Paging
    AMF->>RAN: NGAP Paging<br/>TAI List for Paging
    Note right of AMF: TS 38.413. UE Paging Identity=5G-S-TMSI, TAI List, etc.
    RAN-->>UE: RRC Paging

    Note over UE: Receives the Paging → starts responding
    UE->>RAN: RRC RRCSetupComplete<br/>NAS: Service Request
    RAN->>AMF: NGAP Initial UE Message<br/>NAS: Service Request
    Note over UE,AMF: Service Request details are in a separate chapter (this chapter gives an outline)

    Note over UE,AMF: Establish UE context / AS security and re-establish DL path
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK, N2 SM Information
    AMF->>RAN: NGAP Initial Context Setup Request<br/>NAS: Service Accept, if required
    RAN->>UE: RRC SecurityModeCommand
    UE-->>RAN: RRC SecurityModeComplete
    RAN->>UE: RRC RRCReconfiguration
    UE-->>RAN: RRC RRCReconfigurationComplete
    opt Service Accept is sent
        RAN->>UE: RRC DLInformationTransfer<br/>NAS: Service Accept
    end
    RAN-->>AMF: NGAP Initial Context Setup Response<br/>RAN N3 tunnel
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request<br/>RAN N3 tunnel
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    UPF-->>RAN: GTP-U G-PDU<br/>Buffered downlink data
    Note over RAN,UE: User data delivered over the radio
    Note over UE: Transitions to CM-CONNECTED and receives

Step-by-step explanation (numbers correspond to the diagram above)

The steps below group related messages by procedure (TS 23.502 Clause 4.2.3.3, TS 29.518 Clause 5.2.2.3.1).

  1. UPF→SMF: DL data arrives for the destination UE, but because the UE is in CM-IDLE and the DL path (N3 tunnel) is not established, the UPF buffers the data and notifies the SMF via a PFCP Session Report Request (Downlink Data Report / DLDR) (N4 / TS 29.244). The IE name "Downlink Data Report" is a representative notation; the details are to be confirmed.
  2. SMF→AMF: the SMF invokes Namf_Communication_N1N2MessageTransfer. In this CM-IDLE example the AMF starts paging and returns HTTP 202 (TS 23.502 Clause 4.2.3.3, TS 29.518 Clause 5.2.2.3.1).
  3. AMF decision: the AMF checks the UE context, and when it judges it to be in CM-IDLE, it decides on Paging. If CM-CONNECTED, Paging is unnecessary.
  4. AMF→(R)AN: the AMF sends NGAP Paging to the group of gNBs covering the UE's Registration Area (TAI list) (N2 / TS 38.413). Key IEs include UE Paging Identity (5G-S-TMSI), TAI List for Paging, Paging DRX, etc. (the IE names are to be confirmed, see Packet Analysis).
  5. (R)AN→UE: each gNB transmits Paging (RRC) over the air. The UE receives it at the DRX Paging occasion (the radio-side details are out of scope).
  6. UE→response: the UE that received the Paging initiates the Service Request procedure and carries the NAS to the AMF via Initial UE Message, etc. (N2). The details of the Service Request procedure are covered in a separate chapter (this chapter gives an outline).
  7. Connection establishment / DL path re-establishment: the UE context and AS security are established, and the DL path is re-activated via AMF→SMF→UPF (N4). The UPF delivers the buffered DL data, and the UE receives it in CM-CONNECTED.

Parts of the procedure are situation/implementation dependent

The above is the typical case of Network Triggered (starting from DL data). For NW-initiated signaling (e.g. a page for AMF/NW convenience), steps 1-2 differ. Also, the number of Paging retransmissions, timers, and whether the entire Registration Area is paged at once or in stages (e.g. paging only the last-known TA first) vary with operator policy and implementation (implementation-dependent, some to be confirmed).

Reference: TS 23.502 Clause 4.2.3.3 (Network Triggered Service Request, section number to be confirmed), TS 38.413 (NGAP Paging), TS 29.244 (PFCP Session Report).

Service Request

Diagram 1 — UE-triggered Service Request (main axis)

Original explanation, assumptions and specification references

sequenceDiagram
    autonumber
    participant UE as UE (CM-IDLE)
    participant RAN as (R)AN / gNB
    participant AMF
    participant SMF
    participant UPF

    Note over UE,RAN: The need to originate / send UL data arises
    Note over UE,RAN: RRC connection establishment/resume (radio side, outline/out of scope)
    UE->>RAN: RRC RRCSetupComplete<br/>NAS: Service Request
    Note right of UE: TS 24.501 Clause 5.6.1. Service type (mo-signalling/mo-data, etc.)
    RAN->>AMF: NGAP Initial UE Message<br/>NAS: Service Request
    Note right of RAN: N2 / TS 38.413

    opt Security re-establishment/re-authentication (conditional, situation dependent)
        Note over UE,AMF: Verify the existing security context. Re-authenticate only when needed (details in a separate chapter)
    end

    Note over AMF: Determine which PDU Session(s) to re-activate
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request (N4)
    Note right of SMF: Reconfigure N3/FAR (reflecting the gNB-side N3 TEID may be finalized later)
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK, N2 SM Information

    AMF->>RAN: Initial Context Setup Request (NGAP)<br/>NAS: Service Accept, if required
    Note right of AMF: Set the UE context / AS security / PDU Session N3 information
    RAN->>UE: RRC SecurityModeCommand
    UE-->>RAN: RRC SecurityModeComplete
    RAN->>UE: RRC RRCReconfiguration
    UE-->>RAN: RRC RRCReconfigurationComplete
    opt Service Accept is sent
        RAN->>UE: RRC DLInformationTransfer<br/>NAS: Service Accept
    end
    RAN-->>AMF: Initial Context Setup Response (NGAP)
    Note right of RAN: Notify the gNB-side N3 TEID

    opt Reflect the gNB-side N3 TEID into the UPF (implementation/procedure dependent)
        AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
        SMF->>UPF: PFCP Session Modification Request<br/>RAN N3 tunnel
        UPF-->>SMF: PFCP Session Modification Response
        SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    end

    Note over UE,UPF: N3 (GTP-U) re-established → uplink/downlink data flowing
    Note over UE: Transition to CM-CONNECTED

Diagram 2 — The difference from Network-triggered (Paging precedes it)

Original explanation, assumptions and specification references

In the Network-triggered case, the biggest difference is that Paging is inserted before the diagram above. The UPF buffers and notifies of the DL data arrival, this passes through SMF→AMF, the AMF sends NGAP Paging, and the paged UE starts the Service Request of the diagram above.

sequenceDiagram
    autonumber
    participant UE as UE (CM-IDLE)
    participant RAN as (R)AN / gNB
    participant AMF
    participant SMF
    participant UPF

    Note over UPF: DL data for the target UE arrives (N3 not active) → buffer
    UPF->>SMF: PFCP Session Report Request<br/>Downlink Data Report
    SMF-->>UPF: PFCP Session Report Response
    SMF->>AMF: Namf_Communication_N1N2MessageTransfer<br/>POST /namf-comm/v1/ue-contexts/{ueContextId}/n1-n2-messages
    AMF-->>SMF: Namf_Communication_N1N2MessageTransfer<br/>HTTP 202 Accepted
    Note right of SMF: For details, see the Paging chapter (paging.md)
    AMF->>RAN: NGAP Paging
    RAN-->>UE: RRC Paging
    Note over UE: From here, start the same Service Request as "UE-triggered" above
    UE->>RAN: RRC RRCSetupComplete<br/>NAS: Service Request
    RAN->>AMF: NGAP Initial UE Message<br/>NAS: Service Request
    Note over UE,UPF: Connection re-establishment / U-Plane re-activation (common with the diagram above)
    Note over UPF,UE: After re-establishment, deliver the buffered DL data

Step-by-step explanation (numbers correspond to the UE-triggered diagram)

The steps below group related messages by procedure (TS 23.502 Clause 4.2.3.2, TS 38.331 Clause 5.3.3–Clause 5.3.5).

  1. UE→(R)AN: the need to originate, send UL data, etc. arises; the UE (on the radio side) establishes/resumes the RRC connection (outline/out of scope) and carries the Service Request (NAS). The NAS may include a Service type (e.g. mo-signalling / mo-data, etc.; values to be confirmed) and information on the PDU Session(s) to be re-activated. Reference: TS 24.501 Clause 5.6.1 (section number to be confirmed).
  2. (R)AN→AMF: the gNB puts the NAS onto an Initial UE Message (NGAP) and sends it to the AMF (N2 / TS 38.413).
  3. (Conditional) security/re-authentication: the AMF verifies the existing security context. It re-authenticates and runs Security Mode only when needed (situation dependent; the details are the subject of the Security/Authentication chapter).
  4. AMF's determination: the AMF determines which PDU Session(s) to re-activate, and notifies the SMF of the targets.
  5. AMF→SMF: requests U-Plane activation via Nsmf_PDUSession_UpdateSMContext (TS 29.502 Clause 5.2.2.3.2).
  6. SMF→UPF: reconfigures the UPF's N3/FAR via a PFCP Session Modification Request (N4). The gNB N3 TEID is obtained in the subsequent RAN response and applied when required.
  7. SMF→AMF: returns U-Plane information (the UPF-side N3 TEID, etc.) in the UpdateSMContext Response.
  8. AMF→(R)AN: sets the UE context, AS security, and PDU Session N3 information in the gNB via an Initial Context Setup Request (NGAP).
  9. (R)AN⇔UE: the gNB sends SecurityModeCommand and RRCReconfiguration, and the UE acknowledges each. Service Accept is also relayed when required.
  10. (R)AN→AMF: notifies the gNB-side N3 TEID, etc. via an Initial Context Setup Response (NGAP).
  11. (Implementation/procedure dependent) reflecting the gNB N3 TEID: to reflect the gNB-side N3 TEID into the UPF's downlink FAR, an N4 update via AMF→SMF→UPF may be performed again (procedure/implementation-dependent; some implementations integrate this with step 6 above = to be confirmed).
  12. Data flow / state transition: N3 (GTP-U) is re-established, and uplink/downlink data flows. The UE transitions to CM-CONNECTED. In the Network-triggered case, the DL data buffered in the UPF is delivered.

Parts of the procedure are situation/implementation dependent

The number and order of the N4 updates accompanying U-Plane re-activation (when to reflect the gNB-side N3 TEID into the UPF) differ between the spec's description and implementations. The diagram above is a representative flow for understanding; whether there is one N4 Modification or two, and in which message the gNB N3 TEID is fixed, etc. are implementation-dependent and partly to be confirmed. Whether re-authentication occurs (step 3) is also situation dependent.

Reference: TS 23.502 Clause 4.2.3 series (UE Triggered / Network Triggered Service Request, section number to be confirmed), TS 24.501 Clause 5.6 series (NAS Service Request), TS 38.413 (NGAP), TS 29.244 (PFCP).

RRC Resume / Small Data Transmission — Lightweight Return from RRC Inactive

Diagram 1 — Procedure — Call Flow

Original explanation, assumptions and specification references

sequenceDiagram
  participant UE as UE
  participant GC as gNB (current)
  participant GL as gNB (last serving)
  participant AMF as AMF
  participant SMF as SMF
  participant UPF as UPF

  Note over UE,GC: UE is RRC_INACTIVE / core is CM-CONNECTED
  UE->>GC: RRC RRCResumeRequest<br/>I-RNTI
  Note right of GC: TS 38.331 Clause 5.3.13
  alt UE context held by current gNB
    Note over GC: Restore context locally
  else Return at a different gNB
    GC->>GL: XnAP Retrieve UE Context Request
    Note right of GL: TS 38.423 Clause 8.2.4.2
    GL-->>GC: XnAP Retrieve UE Context Response
  end
  GC->>UE: RRC RRCResume
  UE->>GC: RRC RRCResumeComplete
  opt Xn response contains UE Context Reference at the S-NG-RAN node IE
    GC->>GL: XnAP Retrieve UE Context Confirm
    Note right of GL: TS 38.423 Clause 8.2.4.2 / Clause 8.2.12
  end
  opt U-Plane path update only when necessary
    GC->>AMF: NGAP Path Switch Request
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request<br/>Target N3 tunnel
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK, N2 SM Information
    AMF-->>GC: NGAP Path Switch Request Acknowledge
  end
  Note over UE,GC: UE moves to RRC_CONNECTED

Step-by-step explanation

  1. RRC Resume Request: the UE requests return from RRC_INACTIVE and presents its I-RNTI to let itself be identified against its context.
  2. UE context restoration: if the current gNB holds it, restore locally. If not, obtain it from the last serving gNB via Xn: Retrieve UE Context. If the response contains the UE Context Reference at the S-NG-RAN node IE, send Confirm after successful resume (TS 38.423 Clause 8.2.4.2 / Clause 8.2.12).
  3. RRC Resume: the gNB accepts the return and returns the information needed to resume the AS (radio led; details to be confirmed).
  4. RRC Resume Complete: the UE notifies of return completion. At this point it is RRC_CONNECTED.
  5. Path Switch (only when necessary): the AMF requests an SMF update, and the SMF updates the UPF's N3 path over PFCP (TS 23.502 Clause 4.8.2.2 step 4a / Clause 4.9.1.2.2, TS 29.502 Clause 5.2.2.3.3).

Warning

Whether Xn-based retrieval occurs and whether/how many times Path Switch occurs depend on the RAN deployment and implementation = to be confirmed. If it completes within a single gNB, core updates may not occur.

SDT (concept only, small flow)

Diagram 2 — Procedure — Call Flow

Original explanation, assumptions and specification references

sequenceDiagram
  participant UE as UE
  participant GC as gNB
  Note over UE,GC: UE remains in RRC_INACTIVE (to be confirmed)
  UE->>GC: RRC RRCResumeRequest<br/>SDT
  alt CG-SDT
    Note over UE,GC: User data on Configured Grant (procedure outline)
  else RA-SDT
    Note over UE,GC: User data on Random Access (procedure outline)
  end
  Note over UE,GC: Response and further exchange depend on the scheme and conditions

Both CG-SDT and RA-SDT initiate resume with RRCResumeRequest or RRCResumeRequest1 (TS 38.331 Clause 5.3.13.1b–Clause 5.3.13.3). The diagram selects the former and outlines user data and subsequent processing.

Mobility Registration Update

Diagram 1 — Procedure — Call Flow

Original explanation, assumptions and specification references

This is the heart of this page. The main steps of Mobility Registration Update are shown in a Mermaid sequenceDiagram. The basis is 3GPP TS 23.502 Clause 4.2.2.2 series (Registration procedures), TS 24.501 Clause 5.5.1 series (NAS Registration procedure), and TS 38.413 (NGAP) (the fine details of the section numbers are to be confirmed). It emphasizes the point that the authentication and subscriber-retrieval steps present in Initial Registration are conditional / can be simplified in this procedure.

Prerequisite: the UE is registered (5GMM-REGISTERED) and holds a valid 5G-GUTI

Assume the UE is 5GMM-REGISTERED and holds the 5G-GUTI and security context obtained at its most recent registration. It detects that its serving TA has fallen outside the assigned TAI list and starts this procedure. For the whole of Initial Registration, see Initial Registration (duplication is handled by directing).

sequenceDiagram
    autonumber
    participant UE as UE (REGISTERED)
    participant RAN as (R)AN / gNB
    participant AMF
    participant OLD as Old AMF
    participant UDM

    Note over UE: Serving TA outside the assigned TAI list → start registration update
    Note over UE,RAN: Example establishing RRC from CM-IDLE
    UE->>RAN: RRC RRCSetupComplete<br/>NAS: Registration Request (mobility registration updating)
    Note right of UE: TS 24.501 Clause 5.5.1. 5GS registration type=mobility (to be confirmed)
    RAN->>AMF: NGAP Initial UE Message<br/>NAS: Registration Request
    Note right of RAN: N2 / TS 38.413. May perform AMF selection

    Note over AMF: Check the existing UE context (resolved by 5G-GUTI)

    opt On AMF change (AMF re-selection, Rel/config dependent, conceptual)
        AMF->>OLD: Namf_Communication_UEContextTransfer<br/>POST /namf-comm/v1/ue-contexts/{ueContextId}/transfer
        OLD-->>AMF: Namf_Communication_UEContextTransfer<br/>HTTP 200 OK
    end

    opt Conditional: re-authentication (situation dependent)
        Note over UE,AMF: Re-authentication details are in a separate chapter
    end

    opt UDM registration on AMF change
        AMF->>UDM: Nudm_UECM_Registration<br/>PUT /nudm-uecm/v1/{ueId}/registrations/amf-3gpp-access
        UDM-->>AMF: Nudm_UECM_Registration<br/>HTTP 201 Created / 200 OK / 204 No Content
    end

    opt Conditional: subscription-info lookup / AMF registration update (situation dependent)
        AMF->>UDM: Nudm_SDM_Get<br/>GET /nudm-sdm/v2/{supi}/am-data
        UDM-->>AMF: Nudm_SDM_Get<br/>HTTP 200 OK, Access and Mobility Subscription Data
    end

    Note over AMF: Determine the new Registration Area (TAI list)
    AMF->>RAN: NGAP Downlink NAS Transport<br/>NAS: Registration Accept
    RAN->>UE: RRC DLInformationTransfer<br/>NAS: Registration Accept
    Note right of AMF: TS 24.501 Clause 5.5.1. registration result, etc.

    opt On 5G-GUTI reassignment
        UE->>RAN: RRC ULInformationTransfer<br/>NAS: Registration Complete
        RAN->>AMF: NGAP Uplink NAS Transport<br/>NAS: Registration Complete
        Note right of UE: ACK on new 5G-GUTI assignment, etc.
    end
    Note over UE,AMF: Registration Area update complete while maintaining 5GMM-REGISTERED

Step-by-step explanation (numbers correspond to the diagram above)

Related messages are grouped by procedure. Connected NAS transport uses NGAP and RRC (TS 23.502 Clause 4.2.2.2.2, TS 38.331 Clause 5.3.3 / Clause 5.7.1–Clause 5.7.2, TS 38.413 Clause 8.6.1–Clause 8.6.3).

  1. UE→(R)AN: the UE detects that its serving TA has fallen outside the assigned TAI list, establishes/resumes an RRC connection (on the radio side) (outline / out of scope), and carries the Registration Request (NAS) with Registration type = mobility registration updating. Typically a valid 5G-GUTI is placed in the 5GS mobile identity (the IE name / type value are to be confirmed). Reference: TS 24.501 Clause 5.5.1 (section number to be confirmed).
  2. (R)AN→AMF: the gNB puts the NAS onto an Initial UE Message (NGAP) and sends it to the AMF (N2 / TS 38.413). At the same time it may perform AMF selection.
  3. AMF's decision (context check): the AMF resolves the existing UE context from the 5G-GUTI and starts the update processing. Unlike Initial Registration, being able to reuse the existing security and subscription info here is the basic case.
  4. (Conditional / on AMF change) context transfer: the new AMF invokes Namf_Communication_UEContextTransfer at the old AMF (TS 23.502 Clause 4.2.2.2.2, TS 29.518 Clause 5.2.2.2.1).
  5. (Conditional) re-authentication: only when the existing security context cannot be reused, etc., the AMF→AUSF re-authentication (5G-AKA, N12) is performed. It can be omitted (situation dependent; the details are the subject of the Security/Authentication chapter).
  6. (Conditional) subscription-info lookup / AMF registration update: only when the subscription info changed, the AMF changed, etc., the AMF→UDM (Nudm_UECM_Registration / Nudm_SDM_Get, N8) is performed. It can be omitted (situation dependent).
  7. Determine the new Registration Area: the AMF determines a new Registration Area (TAI list). It assigns the group of TAs that covers the UE's current location.
  8. Accept: with AMF→UE Registration Accept (NAS), it notifies the new TAI list and (if needed) a new 5G-GUTI, registration result, etc.
  9. (On 5G-GUTI reassignment) complete: when a new 5G-GUTI has been assigned, etc., the UE→AMF Registration Complete (NAS) is returned. This is a completion confirmation, and the UE maintains 5GMM-REGISTERED throughout the procedure (it is not a new transition from DEREGISTERED).

The conditional branches are situation/implementation dependent

Re-authentication (step 5), the UDM lookup (step 6), the context transfer on AMF change (step 4), and 5G-GUTI reassignment (steps 8-9) are omitted or changed depending on the validity of the existing context, the configuration, operator policy, and whether the AMF changed. Because 3GPP TS 23.502 Clause 4.2.2 series contains many optional/conditional steps, the specific omission conditions must be checked against the spec individually (some of the detailed branching conditions are to be confirmed). In particular, the details of context transfer on AMF re-selection are out of scope of this chapter and kept at the conceptual level.

Reference: TS 23.502 Clause 4.2.2.2 series (Registration procedures, section number to be confirmed), TS 24.501 Clause 5.5.1 series (the NAS-side Registration procedure), TS 38.413 (NGAP).

Periodic Registration Update

Diagram 1 — Procedure — Call Flow

Original explanation, assumptions and specification references

This is the heart of this page. The main steps of Periodic Registration Update are shown in a Mermaid sequenceDiagram. The basis is 3GPP TS 23.502 Clause 4.2.2.2 series (Registration procedures), TS 24.501 Clause 5.5.1 series (NAS Registration procedure), and TS 38.413 (NGAP) (the details of the section numbers are to be confirmed). The skeleton is common with Mobility Registration Update, but we emphasize that authentication, subscriber retrieval, and TAI list reassignment usually do not occur, making it more lightweight.

Prerequisite: the UE is registered (5GMM-REGISTERED) and the periodic timer has expired

The UE is assumed to be in 5GMM-REGISTERED, holding the 5G-GUTI and security context obtained in its most recent registration. Even without having moved, it fires this procedure triggered by the expiry of the periodic registration update timer. For the whole of Initial Registration, see Initial Registration.

sequenceDiagram
    autonumber
    participant UE as UE (REGISTERED)
    participant RAN as (R)AN / gNB
    participant AMF
    participant UDM

    Note over UE: Periodic registration update timer expiry (no movement needed)
    Note over UE,RAN: Example establishing RRC from CM-IDLE
    UE->>RAN: RRC RRCSetupComplete<br/>NAS: Registration Request (periodic registration updating)
    Note right of UE: TS 24.501 Clause 5.5.1. 5GS registration type=periodic (to be confirmed)
    RAN->>AMF: NGAP Initial UE Message<br/>NAS: Registration Request
    Note right of RAN: N2 / TS 38.413

    Note over AMF: Check the existing UE context (resolved by 5G-GUTI)
    Note over AMF: Update the UE's liveness record (regard as in the serving area)

    opt Only in exceptional cases: re-authentication / subscription query (usually does not occur)
        AMF->>UDM: Nudm_SDM_Get<br/>GET /nudm-sdm/v2/{supi}/am-data
        UDM-->>AMF: Nudm_SDM_Get<br/>HTTP 200 OK, Access and Mobility Subscription Data
    end

    AMF->>RAN: NGAP Downlink NAS Transport<br/>NAS: Registration Accept
    RAN->>UE: RRC DLInformationTransfer<br/>NAS: Registration Accept
    Note right of AMF: TS 24.501 Clause 5.5.1. Usually no TAI list reassignment

    opt On 5G-GUTI reassignment
        UE->>RAN: RRC ULInformationTransfer<br/>NAS: Registration Complete
        RAN->>AMF: NGAP Uplink NAS Transport<br/>NAS: Registration Complete
    end
    Note over UE,AMF: The UE restarts the periodic timer. It maintains 5GMM-REGISTERED

Step-by-step explanation (numbers correspond to the diagram above)

Related messages are grouped by procedure. Connected NAS transport uses NGAP and RRC (TS 23.502 Clause 4.2.2.2.2, TS 38.331 Clause 5.3.3 / Clause 5.7.1–Clause 5.7.2, TS 38.413 Clause 8.6.1–Clause 8.6.3).

  1. UE→(R)AN: triggered by the expiry of the periodic registration update timer, the UE establishes/resumes an RRC connection (on the radio side) (outline / out of scope) and carries the Registration Request (NAS) with Registration type = periodic registration updating. Typically a valid 5G-GUTI is placed in the 5GS mobile identity (the IE name / type value are to be confirmed). Reference: TS 24.501 Clause 5.5.1 (section number to be confirmed).
  2. (R)AN→AMF: the gNB puts the NAS onto an Initial UE Message (NGAP) and sends it to the AMF (N2 / TS 38.413).
  3. The AMF's judgment (context check): the AMF resolves the existing UE context from the 5G-GUTI. In a periodic update the base case is that the existing security and subscription information can be reused, making it even more lightweight than Mobility.
  4. Liveness record update: the AMF records that the UE is in the serving area (maintaining reachability) and updates the periodic timer supervision. This is the essence of this procedure.
  5. (Only in exceptional cases) re-authentication / subscription query: only in the exceptional case where re-authentication is needed or the subscription information has changed, etc., the AMF may perform AMF→AUSF (N12) / AMF→UDM (N8). In a periodic update it usually does not occur (situation dependent).
  6. Accept: the AMF responds with AMF→UE Registration Accept (NAS). Usually there is no TAI list reassignment (within the same area). If necessary, it may notify the next periodic timer value, the registration result, etc. (the IE name / handling are to be confirmed).
  7. (When necessary) Complete: in this example the UE returns Registration Complete (NAS) when a 5G-GUTI is reassigned. A timer value alone does not require Complete. The UE restarts the periodic timer and maintains 5GMM-REGISTERED (TS 24.501 Clause 5.5.1.3.4).

Conditional branches are situation/implementation dependent. Periodic update is 'lightweight by default' but this is not asserted

Re-authentication / UDM query (step 5), the notification of the next timer value / 5G-GUTI reassignment (steps 6-7) may be omitted or changed depending on the validity of the existing context, the configuration, and operator policy. A periodic update is a lightweight procedure in which these usually do not occur, but one cannot assert that "they never occur" (situation dependent). Because TS 23.502 Clause 4.2.2 series contains many optional/conditional steps, the concrete conditions must be checked against the spec individually (some are to be confirmed).

Reference: TS 23.502 Clause 4.2.2.2 series (Registration procedures, section number to be confirmed), TS 24.501 Clause 5.5.1 series (the NAS-side Registration procedure), TS 38.413 (NGAP).

UE Configuration Update — Updating a Registered UE

Diagram 1 — Procedure — UE Configuration Update

Original explanation, assumptions and specification references

The UE is registered and CM-CONNECTED. The diagram isolates the N1 exchange over 3GPP access and shows a case without a re-registration request. Updating 5G-GUTI or TAI List requires the AMF to request an acknowledgement from the UE (TS 23.502 Clause 4.2.4.2).

sequenceDiagram
    participant UE
    participant RAN as NG-RAN
    participant AMF
    Note over AMF: Decide to update 5G-GUTI / TAI List
    AMF->>RAN: NGAP Downlink NAS Transport<br/>NAS: Configuration Update Command (5G-GUTI, TAI List, ACK requested)
    RAN->>UE: RRC DLInformationTransfer<br/>NAS: Configuration Update Command
    Note over UE: Validate NAS message and<br/>apply accepted configuration
    UE->>RAN: RRC ULInformationTransfer<br/>NAS: Configuration Update Complete
    RAN->>AMF: NGAP Uplink NAS Transport<br/>NAS: Configuration Update Complete
    Note over AMF: Receive UE acknowledgement
    Note over UE,AMF: No new Registration in this example

Step-by-step explanation

  1. The AMF decides to update: Changes to subscription data, policy or network configuration can trigger an update. Specific operational triggers and configuration methods are implementation-dependent.
  2. Send information and instructions in the Command: Updating information, requesting an acknowledgement and requesting re-registration are distinct aspects. The actual NAS message name is Configuration Update Command (TS 24.501 Clause 5.4.4.2).
  3. The UE applies the configuration: It accepts a valid message and updates the specified information. IEs other than 5G-GUTI/TAI List have their own processing conditions (TS 24.501 Clause 5.4.4.3).
  4. Return the requested ACK: Here the UE returns Configuration Update Complete. Not every Command requests a Complete (TS 24.501 Clause 5.4.4.3 / Clause 5.4.4.4).

On an established connection NAS is relayed in NGAP Downlink/Uplink NAS Transport and RRC DLInformationTransfer/ULInformationTransfer (TS 38.413 Clause 8.6.2–Clause 8.6.3, TS 38.331 Clause 5.7.1–Clause 5.7.2).

Omitted updates to NG-RAN and UE lower layers

When 5G-GUTI is updated over 3GPP access, the AMF notifies NG-RAN of the new UE Identity Index Value after receiving the UE's ACK, and the UE passes the new 5G-GUTI to the lower layers of 3GPP access. These are not optional implementation details merely because they are absent from the diagram. Conditional rules also apply to multiple accesses (TS 23.502 Clause 4.2.4.2 steps 2c–2d).

First reach the UE if it is CM-IDLE

The AMF can wait until the UE becomes CM-CONNECTED or initiate a Network Triggered Service Request. The choice depends on the network implementation (TS 23.502 Clause 4.2.4.2 step 0). This preceding stage is omitted from the diagram.

Acknowledgement and re-registration are different instructions

When re-registration is requested, the updated information determines whether it occurs in CM-CONNECTED or starts in CM-IDLE after AN Release. Emergency sessions introduce additional conditions. It is therefore incorrect to always draw Complete → Release → Registration (TS 23.502 Clause 4.2.4.2 steps 3–4).

Handover

Diagram 1 — Xn-based Handover

Original explanation, assumptions and specification references

The case where there is an Xn between the Source and Target gNB and the gNBs coordinate directly. The core's involvement centers on the post-execution Path Switch (N3 downlink path switch).

sequenceDiagram
    autonumber
    participant UE
    participant S as Source gNB
    participant T as Target gNB
    participant AMF
    participant SMF
    participant UPF

    Note over UE,S: radio quality degradation → HO decision (Measurement Report, etc. / radio-side / out of scope)
    S->>T: Handover Request (XnAP)
    Note right of S: TS 38.423 (XnAP)
    T-->>S: Handover Request Acknowledge (XnAP)
    Note over S,T: Target prepares UE context/resources
    S->>UE: RRC RRCReconfiguration<br/>Handover to target NR
    Note over UE,T: UE radio-syncs and switches to the Target gNB
    UE->>T: RRC RRCReconfigurationComplete
    opt Data forwarding (optional)
        S-->>T: GTP-U G-PDU<br/>Forwarded user data
    end

    Note over T,AMF: from here, the core's Path Switch (N3 downlink path switch)
    T->>AMF: Path Switch Request (NGAP)
    Note right of T: notify the new gNB's N3 TEID/address
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request<br/>Target N3 tunnel
    UPF-->>SMF: PFCP Session Modification Response
    Note over T,UPF: downlink N3 (GTP-U) switched to the new gNB
    opt End Marker (a marker for the end of the old path)
        UPF-->>S: GTP-U End Marker
    end
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK, N2 SM Information
    AMF-->>T: Path Switch Request Acknowledge (NGAP)
    T->>S: UE Context Release (XnAP)
    Note over UE,UPF: switch complete / communication continues

Diagram 2 — N2-based Handover

Original explanation, assumptions and specification references

The case where there is no Xn, or AMF/UPF relocation is required. The AMF mediates preparation/execution over N2.

sequenceDiagram
    autonumber
    participant UE
    participant S as Source gNB
    participant AMF
    participant SMF
    participant UPF
    participant T as Target gNB

    Note over UE,S: radio quality degradation → HO decision (radio-side / out of scope)
    S->>AMF: Handover Required (NGAP)
    Note right of S: specify the Target gNB / TS 23.502 Clause 4.9.1.3

    Note over AMF,SMF: preparation phase (SMF judges UPF relocation if needed)
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    opt UPF update required
        SMF->>UPF: PFCP Session Modification Request<br/>Handover preparation
        UPF-->>SMF: PFCP Session Modification Response
    end
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK

    AMF->>T: Handover Request (NGAP)
    T-->>AMF: Handover Request Acknowledge (NGAP)
    Note over AMF,T: Target prepares accept resources / N3 TEID
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content

    AMF->>S: Handover Command (NGAP)
    S->>UE: RRC RRCReconfiguration<br/>Handover to target NR
    Note over UE,T: UE switches to the Target gNB
    UE->>T: RRC RRCReconfigurationComplete
    T->>AMF: Handover Notify (NGAP)

    Note over AMF,UPF: execution phase (finalize the N3 downlink path to the new gNB)
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request<br/>Target N3 tunnel
    UPF-->>SMF: PFCP Session Modification Response
    opt End Marker
        UPF-->>S: GTP-U End Marker
    end
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    Note over AMF,S: release the old resources
    AMF->>S: UE Context Release Command (NGAP)
    S-->>AMF: UE Context Release Complete (NGAP)
    Note over UE,UPF: switch complete / communication continues

Step-by-step explanation (numbers correspond to each diagram)

The explanation groups related messages by procedure rather than packet number.

Xn-based (upper diagram)

  1. S→T: Handover Request (XnAP). The Source gNB directly asks the Target gNB "please accept this UE" (TS 38.423).
  2. T→S: Handover Request Acknowledge (XnAP). The Target prepares the UE context/radio resources and consents. 3-5. Radio-side HO execution (outline / out of scope): the Source instructs the UE to execute over RRC, and the UE syncs and switches to the Target gNB and completes. (Data forwarding is optional, forwarding undelivered data S→T.)
  3. T→AMF: Path Switch Request (NGAP). The Target gNB requests the AMF "point the downlink path to me." It notifies the new gNB's N3 TEID/address.
  4. AMF→SMF: conveys the new gNB's N3 info via Nsmf_PDUSession_UpdateSMContext and receives N2 SM information on success (TS 29.502 Clause 5.2.2.3.3).
  5. SMF→UPF: updates the destination of the downlink FAR to the new gNB's N3 TEID via N4 Session Modification (PFCP). → the downlink N3 (GTP-U) is switched to the new gNB (an End Marker may be sent as a marker for the end of the old path).
  6. AMF→T: Path Switch Request Acknowledge (NGAP).
  7. T→S: UE Context Release (XnAP). Releases that UE's resources on the old gNB.

N2-based (lower diagram)

  1. S→AMF: Handover Required (NGAP). Since Xn cannot be used, it asks the AMF to mediate. Specifies the Target gNB.
  2. Preparation phase: AMF→SMF UpdateSMContext, and when required SMF→UPF PFCP Session Modification. This diagram illustrates an existing UPF update.
  3. AMF→T: Handover Request (NGAP) / T→AMF Handover Request Acknowledge (NGAP). The Target prepares resources and the N3 TEID, and the AMF forwards the result to the SMF.
  4. AMF→S: Handover Command (NGAP). Instructs the Source "you may execute."
  5. Radio-side HO execution: NR RRCReconfiguration and RRCReconfigurationComplete move the UE to the Target (TS 38.331 Clause 5.3.5).
  6. T→AMF: Handover Notify (NGAP). Notifies that the switch is complete on the Target side.
  7. Execution phase: AMF→SMF UpdateSMContext (HO complete) → SMF→UPF N4 Modification to update the downlink FAR to the new gNB N3 TEID (an End Marker may be sent).
  8. Release the old resources: AMF→S UE Context Release Command (NGAP) and response.

Message names and ordering have spec/implementation-dependent parts

The names Handover Required / Handover Request / Handover Command / Handover Notify (N2-based, NGAP), Handover Request / Handover Request Acknowledge (Xn-based, XnAP), and Path Switch Request / Acknowledge (NGAP) are based on TS 23.502 Clause 4.9.1, TS 38.413 (NGAP), and TS 38.423 (XnAP). However, the fine step-division of the preparation/execution phases, the exact operation names for the SMF/UPF coordination (UpdateSMContext, etc.) / their counts / optional steps, the presence and timing of UPF relocation, and the handling of data forwarding and End Markers differ by version, configuration, and implementation, and some are to be confirmed. In particular, the internal sequence of N2-based preparation/execution is a simplification of the multiple steps of TS 23.502 Clause 4.9.1.3.

Reference: TS 23.502 Clause 4.9.1 (Handover procedures. Xn-based around Clause 4.9.1.2, N2-based around Clause 4.9.1.3. The fine-grained section numbers are to be confirmed), TS 38.413 (NGAP: Handover-family / Path Switch), TS 38.423 (XnAP: Handover-family).

Inter-AMF Handover — N2 Handover with an AMF Change

Diagram 1 — Procedure — Preparation

Original explanation, assumptions and specification references

The UE is connected and has PDU Sessions to hand over. The Source RAN requests N2 handover, and the Source AMF determines that a Target AMF change is needed (TS 23.502 Clause 4.9.1.3.2).

sequenceDiagram
    participant S as Source NG-RAN
    participant SA as Source AMF
    participant TA as Target AMF
    participant SMF
    participant T as Target NG-RAN
    S->>SA: NGAP Handover Required<br/>Target ID, PDU Session IDs, N2 information
    Note over SA: Select Target AMF
    SA->>TA: Namf_Communication_CreateUEContext<br/>PUT /namf-comm/v1/ue-contexts/{ueContextId}
    TA->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    Note over SMF: Check conditions for retaining the existing UPF
    SMF-->>TA: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK, N2 SM Information
    TA->>T: NGAP Handover Request
    T-->>TA: NGAP Handover Request Acknowledge<br/>Target N3 information
    TA->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    Note over SMF: Store Target N3 information
    SMF-->>TA: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    TA-->>SA: Namf_Communication_CreateUEContext<br/>HTTP 201 Created, N2 information

Step-by-step explanation

  1. The Source RAN requests handover: It sends Target ID, target PDU Sessions, Source-to-Target information and other applicable information to the Source AMF.
  2. The Source AMF hands processing to the Target AMF: CreateUEContext transfers the UE context and preparation information. This differs from reallocation using N1MessageNotify during Registration.
  3. The Target AMF coordinates with the SMF: It contacts the SMF for each target PDU Session. Conditions such as an S-NSSAI unavailable at the target have separate handling.
  4. Prepare Target RAN resources: Handover Request/Acknowledge provides admitted PDU Sessions and target tunnel information. Not every session is necessarily admitted.
  5. Return the results to the SMF: With no UPF change, as in this example, the SMF stores Target N3 information. Preparation completion and downlink-path switching are not the same event.
  6. Respond to the Source AMF: The Target AMF returns the information needed for Handover Command. Check rejection and partial-admission handling separately.

Omitted preparation branches

UPF changes, data-forwarding tunnels and monitoring responses from multiple SMFs require additional processing. This example does not make an N4 update during preparation an unconditional step. See TS 23.502 Clause 4.9.1.3.2 steps 5–8 and 11.

Diagram 2 — Procedure — Execution

Original explanation, assumptions and specification references

Preparation above has succeeded, and the downlink path from the existing PSA UPF is switched to the Target RAN. Radio operations, PDCP status transfer and detailed data forwarding are omitted (TS 23.502 Clause 4.9.1.3.3).

sequenceDiagram
    participant UE
    participant S as Source NG-RAN
    participant SA as Source AMF
    participant TA as Target AMF
    participant T as Target NG-RAN
    participant SMF
    participant UPF as PSA UPF
    SA->>S: NGAP Handover Command
    S->>UE: RRC RRCReconfiguration<br/>Handover to target NR
    UE->>T: RRC RRCReconfigurationComplete
    T->>TA: NGAP Handover Notify
    TA->>SA: Namf_Communication_N2InfoNotify<br/>POST {n2NotifyUri}
    Note over SA: On receiving N2InfoNotify,<br/>start the source RAN resource-release timer
    SA-->>TA: Namf_Communication_N2InfoNotify<br/>HTTP 204 No Content
    TA->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request<br/>Target N3 tunnel
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>TA: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    UE->>T: RRC ULInformationTransfer<br/>NAS: Registration Request (mobility registration updating)
    T->>TA: NGAP Uplink NAS Transport<br/>NAS: Registration Request
    Note over UE,TA: Use context already obtained during HO
    Note over SA: Release timer expires
    SA->>S: NGAP UE Context Release Command
    S-->>SA: NGAP UE Context Release Complete

Step-by-step explanation

  1. Instruct execution from the source side: After receiving preparation results, the Source AMF sends Handover Command to the Source RAN, and the UE moves to the Target RAN.
  2. Notify the Source AMF of target-side completion: The Target AMF sends N2InfoNotify. This example returns HTTP 204 when there is no Secondary RAT usage data to return. If such data is buffered, HTTP 200 carries it (TS 29.518 Clause 5.2.2.3.6.2).
  3. The SMF switches the downlink path: Based on Handover Complete from the Target AMF, the SMF updates the UPF. The AMF does not control N4 directly.
  4. Update registration information: The connected UE sends Registration Request over RRC and NGAP; subsequent registration steps are omitted (TS 23.502 Clause 4.9.1.3.3 step 12, TS 38.331 Clause 5.7.2, TS 38.413 Clause 8.6.3).
  5. Release source RAN resources: Perform UE Context Release at the Source RAN according to the Source AMF's timer. Do not assume a universal timer value.

Successful handover does not mean every session succeeded

Partial PDU Session admission or delayed responses can require release and other handling. Serving-AMF registration with the UDM and conditional release of old UPF/forwarding resources are also omitted. An AMF change does not necessarily delete every existing PDU Session (TS 23.502 Clause 4.9.1.3.3).

4G-5G Interworking — How UEs Move Across EPC and 5GC (N26 / Single-/Dual-Registration)

Diagram 1 — Procedure — Idle mode and Handover

Original explanation, assumptions and specification references

The "way of moving" in Interworking is divided into two families by the UE's state (idle or communicating).

sequenceDiagram
    participant UE
    participant RAN as NG-RAN(5G)
    participant AMF
    participant MME as MME(4G)
    participant ENB as eNB(4G/LTE)
    participant SMFC as SMF+PGW-C

    Note over UE,SMFC: (A) Idle mode mobility (moving while idle)
    UE->>ENB: LTE RRC RRCConnectionSetupComplete<br/>NAS: Tracking Area Update Request
    ENB->>MME: S1AP Initial UE Message<br/>NAS: Tracking Area Update Request
    opt With N26
        MME->>AMF: GTPv2-C Context Request
        AMF-->>MME: GTPv2-C Context Response
        MME->>AMF: GTPv2-C Context Acknowledge
    end
    Note over MME,SMFC: PDN transition details omitted
    Note over UE,ENB: Communication continues on 4G (IP retained)

    Note over UE,SMFC: (B) Handover (connected mode, with N26)
    RAN->>AMF: NGAP Handover Required<br/>Target E-UTRAN
    AMF->>MME: GTPv2-C Forward Relocation Request
    MME->>ENB: S1AP Handover Request
    ENB-->>MME: S1AP Handover Request Acknowledge
    MME-->>AMF: GTPv2-C Forward Relocation Response
    AMF->>RAN: NGAP Handover Command
    RAN->>UE: NR RRC MobilityFromNRCommand<br/>LTE RRC: RRCConnectionReconfiguration
    UE->>ENB: LTE RRC RRCConnectionReconfigurationComplete
    ENB->>MME: S1AP Handover Notify
    Note over UE,ENB: Communication continues on LTE

Explanation of the procedure:

  1. (A) Idle mode mobility — the UE, while idle, camps on the destination radio (e.g. LTE) and performs TAU (4G) / Registration (5G). If there is N26, the destination node (MME/AMF) retrieves the UE context from the counterpart over N26, and continues the session (PDN/PDU session). The shared nodes (SMF+PGW-C, etc.) allow the IP address to be retained. For the details of the 5G-side registration update, see Mobility Registration Update; the 4G side is TAU.
  2. (B) Handover (connected mode) — in 5G→4G with N26, NGAP Handover Required is followed by GTPv2-C Forward Relocation and S1AP preparation, then NR MobilityFromNRCommand and LTE RRCConnectionReconfigurationComplete. Uninterrupted traffic is not guaranteed (TS 23.502 Clause 4.11.1.2.1, TS 38.331 Clause 5.4.3, TS 36.331 Clause 5.3.5).

Check preparation and follow-up separately for each direction

The diagram above mainly outlines 5G→4G. Separate Connected Handover from Idle Mobility as well as separating the directions. Connected handover uses Forward Relocation, while the idle examples use Context Request from the destination core; TAU and Registration also play different roles. See the four N26 Mobility cases for separate diagrams and step explanations (TS 23.502 Clause 4.11.1.2 / Clause 4.11.1.3).

N26 Mobility — Connected / Idle in Both Directions

Diagram 1 — Procedure — 5GS to EPS Handover

Original explanation, assumptions and specification references

This is the Connected procedure. It shows a successful PDU Session transfer with usable EPS bearer information and no direct or indirect data forwarding. The target is an E-UTRAN eNB, and the N26 peer is the MME (TS 23.502 Clause 4.11.1.2.1).

sequenceDiagram
    participant UE
    participant G as Source NG-RAN
    participant AMF
    participant MME
    participant E as Target eNB
    participant SGW as S-GW
    participant SMF as SMF + PGW-C
    participant UPF as UPF + PGW-U
    G->>AMF: NGAP Handover Required<br/>Target eNB
    AMF->>SMF: Nsmf_PDUSession_ContextRequest<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/retrieve
    opt EPS-side CN tunnel preparation is required
        SMF->>UPF: PFCP Session Modification Request
        UPF-->>SMF: PFCP Session Modification Response
    end
    SMF-->>AMF: Nsmf_PDUSession_ContextRequest<br/>HTTP 200 OK, EPS PDN connection
    AMF->>MME: GTPv2-C Forward Relocation Request
    MME->>SGW: GTPv2-C Create Session Request
    SGW-->>MME: GTPv2-C Create Session Response
    MME->>E: S1AP Handover Request
    E-->>MME: S1AP Handover Request Acknowledge
    MME-->>AMF: GTPv2-C Forward Relocation Response
    AMF->>G: NGAP Handover Command
    G->>UE: NR RRC MobilityFromNRCommand<br/>LTE RRC: RRCConnectionReconfiguration
    UE->>E: LTE RRC RRCConnectionReconfigurationComplete
    E->>MME: S1AP Handover Notify
    MME->>AMF: GTPv2-C Forward Relocation Complete Notification
    AMF-->>MME: GTPv2-C Forward Relocation Complete Acknowledge
    MME->>SGW: GTPv2-C Modify Bearer Request
    SGW->>SMF: GTPv2-C Modify Bearer Request
    SMF->>UPF: PFCP Session Modification Request<br/>EPS downlink tunnel
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>SGW: GTPv2-C Modify Bearer Response
    SGW-->>MME: GTPv2-C Modify Bearer Response
    UE->>E: LTE RRC ULInformationTransfer<br/>NAS: Tracking Area Update Request
    E->>MME: S1AP Uplink NAS Transport<br/>NAS: Tracking Area Update Request
    Note over AMF: Source RAN resource-release timer expires
    AMF->>G: NGAP UE Context Release Command
    G-->>AMF: NGAP UE Context Release Complete

Step-by-step explanation

  1. Collect information usable in EPS: The AMF obtains mapped EPS PDN Connection information and related context from the SMF+PGW-C. Exclusion conditions apply to EBIs and PDU Sessions that cannot transfer.
  2. The MME prepares the EPS side: After Forward Relocation Request, it prepares S-GW and Target eNB resources.
  3. Move the UE after preparation: Without data forwarding, this diagram proceeds from Forward Relocation Response to Handover Command. If data forwarding, including direct forwarding, is used, additional processing such as UpdateSMContext with the SMF is required first (TS 23.502 Clause 4.11.1.2.1 steps 10a / 10c). Do not reuse the illustrated order unchanged.
  4. Coordinate completion over N26: After notification from the Target eNB, the MME notifies the AMF of completion.
  5. Switch the downlink user plane: Modify Bearer along MME → S-GW → SMF+PGW-C, together with N4 updates, switches the path to EPS.
  6. Check TAU and cleanup: The UE performs TAU. Cleanup of the old AMF's 3GPP-access registration and conditional handling of dedicated bearers and forwarding resources must also be considered. Source NG-RAN resources are released according to the AMF-side timer.

Reference: TS 23.502 Clause 4.11.1.2.1. The referenced EPC-side procedure is TS 23.401 Clause 5.5.1.2.2.

Not every QoS Flow is carried over unchanged

Retained sessions/flows depend on EBI allocation, transfer eligibility and the flow associated with the default QoS rule. Do not assume arbitrary one-to-one mappings between 5QI and QCI; inspect the mapped EPS bearer context actually transferred (TS 23.502 Clause 4.11.1.2.1 steps 2, 11 and 14–19).

Diagram 2 — Procedure — EPS to 5GS Handover

Original explanation, assumptions and specification references

This is the Connected procedure. It shows successful transfer of a PDN Connection at the shared anchor to 5GS. The initially selected AMF remains the Target AMF, and neither direct nor indirect data forwarding is used (TS 23.502 Clause 4.11.1.2.2).

sequenceDiagram
    participant UE
    participant E as Source eNB
    participant MME
    participant AMF as Target AMF
    participant G as Target NG-RAN
    participant SMF as SMF + PGW-C
    participant UPF as UPF + PGW-U
    participant SGW as Source S-GW
    E->>MME: S1AP Handover Required
    MME->>AMF: GTPv2-C Forward Relocation Request
    AMF->>SMF: Nsmf_PDUSession_CreateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts
    SMF->>UPF: PFCP Session Modification Request<br/>5GS CN tunnel
    UPF-->>SMF: PFCP Session Modification Response<br/>CN tunnel information
    SMF-->>AMF: Nsmf_PDUSession_CreateSMContext<br/>HTTP 201 Created, N2 SM information
    AMF->>G: NGAP Handover Request
    G-->>AMF: NGAP Handover Request Acknowledge<br/>Target N3 tunnel
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request<br/>Handover preparation
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    AMF-->>MME: GTPv2-C Forward Relocation Response
    MME->>E: S1AP Handover Command
    E->>UE: LTE RRC MobilityFromEUTRACommand<br/>NR RRC: RRCReconfiguration
    UE->>G: NR RRC RRCReconfigurationComplete
    G->>AMF: NGAP Handover Notify
    AMF->>MME: GTPv2-C Forward Relocation Complete Notification
    MME-->>AMF: GTPv2-C Forward Relocation Complete Acknowledge
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF->>UPF: PFCP Session Modification Request<br/>Target N3 tunnel
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    UE->>G: NR RRC ULInformationTransfer<br/>NAS: Registration Request (mobility registration updating)
    G->>AMF: NGAP Uplink NAS Transport<br/>NAS: Registration Request
    Note over E,SGW: MME cleans up old EPS resources according to conditions / timers (outline)

Step-by-step explanation

  1. Transfer EPS context to the AMF: Forward Relocation Request over N26 is the entry point. The AMF converts EPS MM context into 5GS information.
  2. Prepare the 5GS SM context: The AMF requests CreateSMContext from the SMF+PGW-C associated with the existing PDN Connection. It indicates HO Preparation so that the downlink path is not switched during preparation.
  3. Apply Target RAN admission results: Prepare the Target RAN using S-NSSAI, EBI/QFI mappings and N2 SM information, then apply the returned N3 information at the SMF/UPF.
  4. Move the UE and notify completion over N26: After preparation, the UE moves, and the Target AMF notifies the MME of completion.
  5. Switch the downlink path to 5GS: On Handover Complete, the SMF+PGW-C updates N4. Conditional End Marker handling and PCF updates are omitted.
  6. Perform Mobility Registration and old-resource cleanup: The UE proceeds with EPS-to-5GS Mobility Registration, and the MME cleans up old EPS resources. PDN Connections that cannot transfer to 5GS require separate handling.

References: TS 23.502 Clause 4.11.1.2.2.2 / Clause 4.11.1.2.2.3, TS 36.331 Clause 5.4.3, TS 38.331 Clause 5.3.5.

Distinguish N26/no-N26 and Handover/Idle mobility

This diagram is a handover using N26. Do not mix it with Idle Context Request/Response or movement without N26. RelocateUEContext for AMF reselection during EPS-to-5GS handover is also omitted. It is not the same operation as Registration rerouting (TS 23.502 Clause 4.11.1.2.2.2 step 8a / Clause 4.11.1.3 / Clause 4.11.2).

Diagram 3 — Procedure — 5GS to EPS Idle Mobility

Original explanation, assumptions and specification references

This is the Idle procedure. The UE moves from 5GS CM-IDLE to E-UTRA/EPS and starts TAU. There are transferable PDU Sessions, but no user-plane activation is requested using the TAU active flag, nor triggered by downlink data or similar events. TAU integrity verification succeeds, and the MME allocates a new GUTI (TS 23.502 Clause 4.11.1.3.2 / Clause 4.11.1.5.3; TS 23.401 Clause 5.3.3.1).

sequenceDiagram
    participant UE
    participant E as eNB
    participant MME
    participant AMF as Old AMF
    participant SGW as S-GW
    participant SMF as SMF + PGW-C
    participant UPF as UPF + PGW-U
    participant HSS as HSS + UDM
    Note over UE: Camp on EPS from CM-IDLE<br/>No source RAN handover preparation
    UE->>E: LTE RRC RRCConnectionSetupComplete<br/>NAS: Tracking Area Update Request
    E->>MME: S1AP Initial UE Message<br/>NAS: Tracking Area Update Request
    MME->>AMF: GTPv2-C Context Request<br/>TAU Request
    Note over AMF: Verify TAU Request integrity
    AMF->>SMF: Nsmf_PDUSession_ContextRequest<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/retrieve
    opt CN tunnel information for EPS bearers needs allocation
        SMF->>UPF: PFCP Session Modification Request
        UPF-->>SMF: PFCP Session Modification Response
    end
    SMF-->>AMF: Nsmf_PDUSession_ContextRequest<br/>HTTP 200 OK, EPS PDN connection
    AMF-->>MME: GTPv2-C Context Response<br/>Mapped MM / security context, EPS bearer contexts
    opt Additional authentication / security processing is required
        Note over UE,MME: Authentication and security details omitted
    end
    MME->>AMF: GTPv2-C Context Acknowledge
    MME->>SGW: GTPv2-C Create Session Request
    SGW->>SMF: GTPv2-C Modify Bearer Request
    SMF->>UPF: PFCP Session Modification Request<br/>SGW-U tunnel information
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>SGW: GTPv2-C Modify Bearer Response
    SGW-->>MME: GTPv2-C Create Session Response
    MME->>HSS: Diameter Update Location Request
    HSS->>AMF: Nudm_UECM_DeregistrationNotification<br/>POST {deregCallbackUri}
    AMF-->>HSS: Nudm_UECM_DeregistrationNotification<br/>HTTP 204 No Content
    Note over AMF,HSS: Clean up old 3GPP registration / subscriptions / policy, etc. (outline)
    HSS-->>MME: Diameter Update Location Answer
    MME->>E: S1AP Downlink NAS Transport<br/>NAS: Tracking Area Update Accept
    E->>UE: LTE RRC DLInformationTransfer<br/>NAS: Tracking Area Update Accept
    UE->>E: LTE RRC ULInformationTransfer<br/>NAS: Tracking Area Update Complete
    E->>MME: S1AP Uplink NAS Transport<br/>NAS: Tracking Area Update Complete
    Note over UE,MME: No radio / S1 user-plane activation in this example

Step-by-step explanation

  1. The UE starts TAU from the target: The source RAN does not send Handover Required. The UE uses an EPS GUTI mapped from its 5G-GUTI and indicates movement from 5GC. The TAU Request is integrity protected with the 5G security context (TS 23.502 Clause 4.11.1.5.3).
  2. The MME retrieves information from the AMF: It sends Context Request over N26, and the AMF verifies the included TAU Request. This diagram assumes successful verification; it does not imply that authentication can always be omitted when verification fails.
  3. The AMF collects transferable session information: It sends ContextRequest to the SMF+PGW-C and obtains EPS bearer contexts. If needed, the UPF+PGW-U prepares EPS-side CN tunnel information.
  4. Acknowledge context retrieval and update EPS path information: Following conditional authentication/security processing, the MME returns Context Acknowledge. S-GW Create Session, Modify Bearer toward SMF+PGW-C and N4 updates are distinct from advance RAN preparation in Connected Handover.
  5. Update the serving registration: On the MME's Update Location, HSS+UDM notifies the old AMF of 5GS-to-EPS mobility. Distinguish release of non-transferable PDU Sessions from continuity of transferable sessions. Non-3GPP-access registration is not unconditionally deleted (TS 23.502 Clause 4.11.1.3.2 steps 15–15c).
  6. Accept TAU: Here the UE returns Complete for an Accept containing a new GUTI. Do not treat TAU Complete as an unconditional response in every TAU (TS 23.401 Clause 5.3.3.1 step 21).

User-plane activation is a separate decision during Idle mobility

The active flag, downlink data or downlink signalling can trigger radio/S1 bearer activation during TAU. Do not infer that the UE must remain idle throughout, or that successful TAU always means data can already flow. NAS forwarding and individual unsubscribe responses are omitted from the latter part of the diagram (TS 23.401 Clause 5.3.3.1; TS 23.502 Clause 4.11.1.3.2).

When Initial Attach replaces TAU

This diagram uses TAU because transferable PDU Sessions exist. If none exist and either the UE or EPC does not support attach without PDN connectivity, Initial Attach is used. Do not assume every 5GS-to-EPS Idle move uses TAU (TS 23.502 Clause 4.11.1.3.1).

Diagram 4 — Procedure — EPS to 5GS Idle Mobility

Original explanation, assumptions and specification references

This is the Idle procedure. The UE moves from EPS ECM-IDLE to NG-RAN and starts Mobility Registration Update. N26 context retrieval succeeds, and PDN Connections at the shared anchor can transfer to 5GS. Retrieval of native 5G context from an old AMF, AMF reselection, user-plane reactivation requests and pending downlink data are excluded (TS 23.502 Clause 4.11.1.3.3).

sequenceDiagram
    participant UE
    participant RAN as NG-RAN
    participant AMF
    participant MME as Old MME
    participant SMF as SMF + PGW-C
    participant UPF as UPF + PGW-U
    participant HSS as HSS + UDM
    participant SGW as Old S-GW
    Note over UE: Camp on NG-RAN from ECM-IDLE<br/>Not an MME-issued Handover Command
    UE->>RAN: NR RRC RRCSetupComplete<br/>NAS: Registration Request (mobility registration updating)
    RAN->>AMF: NGAP Initial UE Message<br/>NAS: Registration Request
    AMF->>MME: GTPv2-C Context Request<br/>EPS GUTI, TAU Request
    Note over MME: Verify the embedded TAU Request
    MME-->>AMF: GTPv2-C Context Response<br/>EPS MM / bearer contexts
    Note over AMF: Convert EPS MM Context to 5GS MM Context
    opt New authentication or related processing is required
        Note over UE,AMF: Authentication and security details omitted
    end
    AMF->>MME: GTPv2-C Context Acknowledge
    AMF->>HSS: Nudm_UECM_Registration<br/>PUT /nudm-uecm/v1/{ueId}/registrations/amf-3gpp-access
    HSS-->>AMF: Nudm_UECM_Registration<br/>HTTP 201 Created / 200 OK / 204 No Content
    AMF->>HSS: Nudm_SDM_Get<br/>GET /nudm-sdm/v2/{supi}/am-data
    HSS-->>AMF: Nudm_SDM_Get<br/>HTTP 200 OK
    AMF->>SMF: Nsmf_PDUSession_CreateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts
    SMF->>UPF: PFCP Session Modification Request<br/>PDU Session CN tunnel
    UPF-->>SMF: PFCP Session Modification Response
    SMF-->>AMF: Nsmf_PDUSession_CreateSMContext<br/>HTTP 201 Created
    HSS->>MME: Diameter Cancel Location Request
    MME-->>HSS: Diameter Cancel Location Answer
    opt Old-resource release conditions / timer expiry
        MME->>SGW: GTPv2-C Delete Session Request<br/>Operation Indication not set
        SGW-->>MME: GTPv2-C Delete Session Response
    end
    AMF->>RAN: NGAP Downlink NAS Transport<br/>NAS: Registration Accept
    RAN->>UE: NR RRC DLInformationTransfer<br/>NAS: Registration Accept
    UE->>RAN: NR RRC ULInformationTransfer<br/>NAS: Registration Complete
    RAN->>AMF: NGAP Uplink NAS Transport<br/>NAS: Registration Complete
    Note over UE,AMF: Check session transfer and N3 reactivation completion separately

Step-by-step explanation

  1. Start with Registration: The UE sets registration type to Mobility Registration Update and supplies a 5G-GUTI mapped from EPS GUTI and information indicating movement from EPC. For Idle mobility, Registration Request also contains a TAU Request protected with the EPS security context for the MME to verify (TS 23.502 Clause 4.11.1.3.3 step 2).
  2. The AMF contacts the old MME: It derives the MME and EPS GUTI from the mapped GUTI and sends Context Request over N26. The MME verifies TAU Request and returns EPS MM/bearer contexts.
  3. Decide security handling and acceptance: The AMF converts the received EPS information for 5GS. Without an available native 5G security context, derivation of a mapped context or new authentication is required. On acceptance, it returns Context Acknowledge (TS 23.502 Clause 4.11.1.3.3 steps 5–8).
  4. Create the SM context corresponding to the existing PDN Connection: The AMF requests CreateSMContext from SMF+PGW-C, which correlates it with the existing PDN Connection and updates N4. This is not unconditional creation of a completely new PDU Session from scratch.
  5. Clean up the old EPS side: HSS+UDM cancels the MME registration, and old S-GW resources are released according to conditions and timers. Here Delete Session Request does not set the Operation Indication, avoiding deletion at the shared PGW. Do not assume a fixed ordering of release relative to Registration Accept (TS 23.502 Clause 4.11.1.3.3 steps 15–16a; TS 23.401 Clause 5.3.3.1).
  6. Check registration results and session state: Accept carries updated 5G-GUTI, Allowed NSSAI, EPS bearer status and other information; the UE updates the corresponding state. Reactivation would require N2 SM information and RAN processing, but this example does not request it. Conditional SMF registration with the UDM and PCF updates are omitted (TS 23.502 Clause 4.11.1.3.3 steps 14–18).

Do not add Context Request to post-handover Registration

TS 23.502 Clause 4.11.1.3.3 also applies to Mobility Registration following EPS-to-5GS handover, not only to Idle mobility. However, when performed as part of handover, the N26 Context Request/Response/Acknowledge in steps 5 and 8 is not performed. Do not use the same diagram for registration updates after Connected Handover and those starting from Idle.

Idle mobility with data forwarding is a separate branch

Forwarding buffered downlink data adds the procedures in TS 23.502 Clause 4.11.1.3.2A / Clause 4.11.1.3.3A. Idle does not inherently rule out data forwarding; these examples explicitly choose the no-forwarding case.

QoS — The 5G QoS Model

Diagram 1 — Procedure — Call Flow

Original explanation, assumptions and specification references

This is the heart of this page. The control flow accompanying the establishment/modification of a QoS Flow is shown as a Mermaid sequenceDiagram. The basis is TS 23.502 (QoS configuration within the PDU Session establishment/modification procedures), TS 23.501 Clause 5.7 (the QoS model, section number to be confirmed), TS 29.512 (Npcf_SMPolicyControl), TS 29.244 (PFCP QER), and TS 38.413 (NGAP QoS profile). Since a QoS Flow is in many cases established as part of PDU Session Establishment, here we focus on the distribution of the QoS configuration (for the overall PDU Session establishment procedure, see pdu-session).

Precondition: QoS is configured in the context of PDU Session establishment/modification

The establishment of a QoS Flow is not an independent procedure; it happens within PDU Session Establishment or PDU Session Modification. This diagram extracts the QoS decision → distribution to the UPF/NG-RAN/UE part of it. The operation names and ordering conform to TS 23.502, but the details are version/implementation-dependent, and some are to be confirmed.

sequenceDiagram
    autonumber
    participant UE
    participant RAN as NG-RAN / gNB
    participant AMF
    participant SMF
    participant PCF
    participant UPF

    Note over SMF,PCF: A QoS decision becomes necessary on the trigger of PDU Session establishment/modification
    opt Dynamic PCC policy association creation (may precede modification)
        SMF->>PCF: Npcf_SMPolicyControl_Create<br/>POST /npcf-smpolicycontrol/v1/sm-policies
        PCF-->>SMF: Npcf_SMPolicyControl_Create<br/>HTTP 201 Created, PCC rules
        Note right of PCF: N7 / TS 29.512
    end
    Note over SMF: Decide the QoS per QoS Flow<br/>(QFI assignment, 5QI, GBR/AMBR)

    SMF->>UPF: PFCP Session Modification Request<br/>QER, PDR
    Note right of SMF: N4 / TS 29.244. Instructs rate control and DL QFI marking
    UPF-->>SMF: PFCP Session Modification Response

    SMF->>AMF: Namf_Communication_N1N2MessageTransfer<br/>POST /namf-comm/v1/ue-contexts/{ueContextId}/n1-n2-messages
    AMF-->>SMF: Namf_Communication_N1N2MessageTransfer<br/>HTTP 200 OK
    AMF->>RAN: NGAP PDU Session Resource Modify Request<br/>N2 SM information, NAS: DL NAS Transport
    Note right of AMF: N2 / TS 38.413
    Note over RAN: Decide QoS Flow(QFI) ↔ DRB mapping
    RAN->>UE: RRC RRCReconfiguration<br/>NAS: DL NAS Transport (PDU Session Modification Command)
    UE-->>RAN: RRC RRCReconfigurationComplete
    RAN-->>AMF: NGAP PDU Session Resource Modify Response<br/>N2 SM information
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    UE->>RAN: RRC ULInformationTransfer<br/>NAS: UL NAS Transport (PDU Session Modification Complete)
    RAN->>AMF: NGAP Uplink NAS Transport<br/>NAS: UL NAS Transport
    AMF->>SMF: Nsmf_PDUSession_UpdateSMContext<br/>POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify
    SMF-->>AMF: Nsmf_PDUSession_UpdateSMContext<br/>HTTP 200 OK / 204 No Content
    Note over RAN,UE: Radio-side DRB setup (outline/out of scope)

    Note over UE,UPF: Subsequent data: QFI marking over N3<br/>DL: the UPF sets it on N3<br/>UL: the UE classifies via QoS rules (sets the QFI if a SDAP header is configured), the gNB sets it on N3

Step-by-step explanation (numbers correspond to the diagram above)

The diagram illustrates modification of an existing session; related messages are grouped by procedure (TS 23.502 Clause 4.3.3.2, TS 29.512 Clause 4.2.2).

1-2. (conditional) SMF↔PCF: In a dynamic-PCC configuration, the SMF fetches the PCC Rule with Npcf_SMPolicyControl (N7). The PCC Rule includes QoS parameters such as 5QI, the GBR/Non-GBR distinction, and AMBR (TS 29.512). In a PCF-less (static PCC) configuration, the SMF's default QoS is used (configuration-dependent). 3. (inside the SMF) QoS decision: The SMF assigns a QFI per QoS Flow and finalizes the 5QI and GBR/AMBR. 4-5. SMF→UPF: With PFCP Session Establishment/Modification (N4), it sets the QER (QoS Enforcement Rule) and PDR on the UPF. The QER instructs rate control (caps such as Session-AMBR) and DL-side QFI marking (TS 29.244). For the PFCP rule details, see N4. 6-7. SMF→AMF→NG-RAN: The SMF distributes the N2 SM info containing the QoS profile and the QoS rules for the UE (N1) via the AMF. The AMF carries the QoS profile in NGAP to the NG-RAN (N2 transport relay, TS 38.413). 8. NG-RAN's DRB mapping: The NG-RAN decides the (QoS Flow, QFI) ↔ DRB correspondence. Multiple QoS Flows may be bundled onto one DRB (radio side, implementation-dependent). 9. NG-RAN⇔UE (radio side, outline/out of scope): The NG-RAN sets up the DRB via RRC and delivers the bundled QoS rules to the UE. 10. QFI marking during data transfer: For subsequent real data, the UPF marks the QFI over N3 (GTP-U) for DL according to the QoS Flow, and the NG-RAN carries it onto the corresponding DRB. For UL, the UE classifies traffic into QoS Flows based on the QoS rules and, on DRBs for which a UL SDAP header is configured by RRC, sends it with the QFI in the radio-side SDAP header (TS 37.324 Clause 6.2.2.3, TS 38.331 sdap-HeaderUL; to be confirmed). It is the gNB that sets the UL QFI in the PDU Session Container on N3 (GTP-U) (TS 38.415; clause numbers to be confirmed).

The procedure is embedded within PDU Session establishment/modification

The diagram above extracts the skeleton of QoS distribution. In practice, it is woven into the Call Flow of PDU Session Establishment and integrated with the two N4 stages of Establishment→Modification and the N2 resource setup. The message ordering, operation names, and some IEs are version/implementation-dependent and to be confirmed.

References: TS 23.501 Clause 5.7 (the QoS model, section number to be confirmed), TS 23.502 (PDU Session procedures with QoS configuration), TS 29.512 (Npcf_SMPolicyControl), TS 29.244 (PFCP QER), TS 38.413 (NGAP QoS profile).