Skip to content

Inter-AMF Handover — N2 Handover with an AMF Change

Why — One AMF box hides important coordination

This chapter expands the N2-based overview in Handover for different Source and Target AMFs. Target RAN preparation is not handled entirely by the Source AMF: the Target AMF coordinates with the SMF and Target RAN (TS 23.502 Clause 4.9.1.3).

The example is non-roaming within one PLMN, retaining the existing SMF and PSA UPF. Intermediate UPF insertion/change, DAPS and indirect data forwarding are excluded. Explanation numbers group actions and do not match every specification message number.

Procedure — Preparation

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.

Procedure — Execution

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).

Packet Analysis

Keep Source and Target AMFs separate when tracing CreateUEContext, UpdateSMContext to the SMF, Handover Notify, N2InfoNotify and source RAN release. Track PDU Session ID and NGAP IDs as distinct identifiers. Correlation methods and available log information are implementation-dependent.

Knowledge check

  • Which AMF prepares the Target RAN? → The Target AMF in this example.
  • Does Handover Request Acknowledge alone mean the downlink N3 path has switched? → No. Check preparation and execution separately.

3GPP Specification

Next Step

Handover Overview / AMF Reallocation / N26 Mobility (Connected / Idle) / Mobility Registration Update