Skip to content

AMF Reallocation — Rerouting Registration to the Appropriate AMF

Why — The first AMF is not necessarily the final serving AMF

The Initial AMF receiving a Registration Request may reroute registration to a Target AMF, considering factors such as the requested slices. This reroutes a NAS request during Registration; it is separate from Inter-AMF Handover during connected operation (TS 23.502 Clause 4.2.2.2.3).

Read Registration, GUAMI and Network Slicing first to distinguish candidate AMF selection from request forwarding.

What — Separate selection information from the forwarding path

  • UDM: Supplies subscription information for slice selection when needed.
  • NSSF: Supplies information such as Allowed NSSAI and AMF Set when slice selection is required.
  • NRF: Discovers candidate AMF addresses and capabilities when needed.
  • Initial / Target AMF: The AMF receiving the registration request and the AMF continuing registration after rerouting.

Not every query is performed every time. The diagrams show representative normal 3GPP-access cases, omitting old-AMF information retrieval, detailed authentication and branches such as disaster roaming (TS 23.502 Clause 4.2.2.2.3 steps 1–6).

Procedure — Direct AMF Reroute

The Initial AMF forwards the NAS request directly to the Target AMF. If a security association has already been established between the UE and Initial AMF, this direct path is used rather than rerouting via the RAN (TS 23.502 Clause 4.2.2.2.3 steps 6–7(A)).

sequenceDiagram
    participant RAN as NG-RAN
    participant I as Initial AMF
    participant NSSF
    participant NRF
    participant T as Target AMF
    alt From CM-IDLE
        RAN->>I: Initial UE Message (NAS-PDU: Registration Request)
    else From CM-CONNECTED
        RAN->>I: Uplink NAS Transport (NAS-PDU: Registration Request)
    end
    Note over I: Obtain needed identity / subscription data and decide on reallocation
    opt Slice selection is required
        I->>NSSF: Nnssf_NSSelection_Get<br/>GET /nnssf-nsselection/v2/network-slice-information
        NSSF-->>I: Nnssf_NSSelection_Get response<br/>HTTP 200 OK (Allowed NSSAI, AMF Set, etc.)
    end
    opt Target AMF discovery is required
        I->>NRF: Nnrf_NFDiscovery_Request<br/>GET /nnrf-disc/v1/nf-instances
        NRF-->>I: Nnrf_NFDiscovery_Request response<br/>HTTP 200 OK (candidate AMF addresses / capabilities, etc.)
    end
    I->>T: Namf_Communication_N1MessageNotify<br/>POST {n1NotifyCallbackUri} (Registration Request, AN information, available SUPI / MM Context, etc.)
    T-->>I: Namf_Communication_N1MessageNotify response<br/>HTTP 204 No Content
    Note over T: Continue Registration using transferred information
    Note over RAN,T: The first subsequent N2 message updates the UE's termination<br/>Its type depends on the subsequent procedure

The notification uses the callback URI registered with the NRF (TS 29.518 Clause 5.2.2.3.5.2); selection and discovery are specified in TS 29.531 Clause 5.2.2.2.2 and TS 29.510 Clause 5.3.2.2.

Step-by-step explanation

  1. Receive the registration request: The entry point is Initial UE Message from CM-IDLE, or Uplink NAS Transport for registration while CM-CONNECTED.
  2. Determine the target: Use available subscription and slice information. NRF discovery can be omitted under conditions such as addresses being locally available.
  3. Transfer the request and context directly: Namf_Communication_N1MessageNotify carries not only the NAS request but also AN access information, available SUPI/MM Context and other applicable information. Unavailable information is not assumed to be included.
  4. The Target AMF continues registration: This is not merely an instruction for the UE to start registration again from scratch. The specification also defines preferential use of a 5G security context received from the Initial AMF.
  5. Update the NG-RAN termination: The Target AMF's first N2 message supplies the Initial AMF name and Target AMF-side UE NGAP ID, among other information. The complete exchange through Registration Accept/Complete is omitted.

Reference: TS 23.502 Clause 4.2.2.2.3 steps 1, 6, 7(A) and 8.

Procedure — Reroute via NG-RAN

This path applies when the UE registers from CM-IDLE without an established security association with the Initial AMF, and the specification's RAN-assisted rerouting conditions are met. Do not fold cases such as receiving a candidate AMF list from the NSSF into the same branch (TS 23.502 Clause 4.2.2.2.3 step 7(B)).

sequenceDiagram
    participant RAN as NG-RAN
    participant I as Initial AMF
    participant T as Target AMF
    RAN->>I: Initial UE Message (Registration Request)
    Note over I: Choose RAN-assisted rerouting based on slice information, etc.
    I-->>RAN: REROUTE NAS REQUEST<br/>(AMF Set ID, Registration Request, Allowed NSSAI, etc.)
    Note over RAN: Select Target AMF using supplied information
    RAN->>T: INITIAL UE MESSAGE<br/>(rerouted Registration Request, etc.)
    Note over T: Continue Registration

Step-by-step explanation

  1. Receive Initial UE Message: This path covers entry from CM-IDLE.
  2. The Initial AMF asks the RAN to reroute: The formal NGAP procedure is Reroute NAS Request. The request includes information such as AMF Set ID needed to select the next AMF.
  3. NG-RAN forwards to the Target AMF: If supported, NG-RAN reroutes Initial UE Message according to the specified AMF Set and other supplied information. Transfer of Allowed NSSAI and related information is also conditional (TS 38.413 Clause 8.6.5).
  4. The Target AMF continues registration: The RAN-assisted path does not transfer the Initial AMF's security context to the Target AMF, so it is not equivalent to direct forwarding.

The paths are not freely interchangeable

Step 7(B) cannot be used for a registration request received in CM-CONNECTED. An established security association with the Initial AMF also requires direct forwarding. RAN-assisted rerouting is not an unconditional fallback whenever N14 is unreachable (TS 23.502 Clause 4.2.2.2.3 steps 6–8).

Packet Analysis

For the same UE, line up the Initial AMF, selected AMF Set, direct N1MessageNotify or REROUTE NAS REQUEST, and the Target AMF's first N2 message. SBI visibility and log correlation depend on the implementation and analysis environment.

Knowledge check

  • Are the Initial AMF and the previously serving AMF the same role? → Not necessarily. Distinguish the first receiver of the registration request from the AMF holding the previous context.
  • Can the flow freely switch to the RAN path after authentication and NAS security establishment? → No. Check the security-association conditions.

3GPP Specification

Next Step

Registration / Inter-AMF Handover / GUAMI / Callflow