Skip to content

Deregistration — Registration and Session Cleanup

Why — Disconnecting is not the same as deregistering

If Registration is the entry point, Deregistration ends the registration. Unlike AN Release, which releases radio and N2 connections after inactivity, deregistration handles registration and PDU Session cleanup for the target access (TS 23.502 Clause 4.2.2.3 / Clause 4.2.6).

This chapter uses a non-roaming UE registered over 3GPP access only, using normal services. Emergency services, multiple accesses and ordering changes due to Secondary RAT usage reporting are outside the diagrams' scope. Step numbers group related actions.

What — Identify the initiator and response direction

  • UE-initiated: The UE sends a Deregistration Request, and the AMF returns a Deregistration Accept unless the request indicates switch-off (TS 23.502 Clause 4.2.2.3.2).
  • Network-initiated, explicit: The AMF sends the Request, and the receiving UE returns the Accept (TS 23.502 Clause 4.2.2.3.3).
  • Implicit deregistration: The AMF processes deregistration without sending a Request to the UE. It does not wait for an Accept from the UE (TS 23.502 Clause 4.2.2.3.3).

Procedure — UE-initiated Deregistration

This example uses a valid NAS security context. PDU Session release is performed for each session on the target access (TS 23.502 Clause 4.2.2.3.2). {smContextRef} identifies the SM context. HTTP 204 is one successful ReleaseSMContext response (TS 29.502 Clause 5.2.2.4).

sequenceDiagram
    participant UE
    participant AMF
    participant SMF
    participant UPF
    participant UDM
    participant PCF
    participant RAN as NG-RAN
    UE->>RAN: ULInformationTransfer<br/>(RRC#59; NAS: Deregistration Request (UE originating), Access Type, Switch-off)
    RAN->>AMF: Uplink NAS Transport<br/>(NGAP#59; NAS-PDU: Deregistration Request (UE originating))
    opt PDU Sessions exist on the target access
        AMF->>SMF: Nsmf_PDUSession_ReleaseSMContext<br/>(HTTP POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/release)
        SMF->>UPF: PFCP Session Deletion Request<br/>(PFCP)
        UPF-->>SMF: PFCP Session Deletion Response<br/>(PFCP)
        SMF-->>AMF: 204 No Content<br/>(HTTP)
        opt Dynamic PCC is used
            Note over SMF,PCF: Terminate SM Policy Association (outline)
        end
        opt UDM cleanup conditions are met
            Note over SMF,UDM: Remove subscription and SMF registration (outline)
        end
    end
    opt No registration on another access and PCF associations exist
        Note over AMF,PCF: Terminate AM / UE Policy Associations (outline)
    end
    alt Not switch-off
        AMF-->>RAN: Downlink NAS Transport<br/>(NGAP#59; NAS-PDU: Deregistration Accept (UE originating))
        RAN-->>UE: DLInformationTransfer<br/>(RRC#59; NAS: Deregistration Accept (UE originating))
    else Switch-off
        Note over UE,AMF: No Deregistration Accept is sent
    end
    opt An N2 signalling connection remains
        AMF->>RAN: UE Context Release Command<br/>(NGAP)
        RAN->>UE: RRCRelease<br/>(RRC)
        RAN-->>AMF: UE Context Release Complete<br/>(NGAP)
    end

Step-by-step explanation

  1. Specify the target: The UE indicates the access to deregister using Access Type. The Switch-off indication helps explain cases where no Accept is returned.
  2. Release sessions: The AMF requests release from the SMF, which deletes the PFCP Session at the UPF. This stage is absent when there is no PDU Session.
  3. Clean up associations: Terminate the SM Policy Association used for dynamic PCC. The SMF unsubscribes from UDM data subject to conditions such as this being the last PDU Session for the relevant DNN and S-NSSAI, and deregisters its SMF registration. AM/UE Policy termination at the AMF also depends on registration over other accesses.
  4. Return an Accept only when required: A missing Accept during switch-off is not a response failure.
  5. Release remaining signalling connections: If an N2 connection remains, perform NGAP UE Context Release and radio RRCRelease.

References: TS 23.502 Clause 4.2.2.3.2 / Clause 4.2.6; formal PFCP message names are specified in TS 29.244 Clause 7.5.6 / Clause 7.5.7.

Not an unconditional deletion of all sessions and registrations

Cleanup depends on the target access and any remaining access. When Secondary RAT usage reporting is required, a branch performs the Accept and connection release earlier. Do not apply the illustrated serial order to every case (TS 23.502 Clause 4.2.2.3.2).

Procedure — Network-initiated Deregistration

The AMF itself initiates explicit deregistration, and the UE is CM-CONNECTED. Cases with a PDU Session associated with emergency services are excluded (TS 23.502 Clause 4.2.2.3.3).

sequenceDiagram
    participant UE
    participant AMF
    participant SMF
    participant UPF
    participant RAN as NG-RAN
    AMF->>RAN: Downlink NAS Transport<br/>(NGAP#59; NAS-PDU: Deregistration Request (UE terminated))
    RAN->>UE: DLInformationTransfer<br/>(RRC#59; NAS: Deregistration Request (UE terminated), Access Type, re-registration required)
    Note over UE,AMF: Accept can follow reception of Request<br/>Shown before session release in this example
    UE-->>RAN: ULInformationTransfer<br/>(RRC#59; NAS: Deregistration Accept (UE terminated))
    RAN-->>AMF: Uplink NAS Transport<br/>(NGAP#59; NAS-PDU: Deregistration Accept (UE terminated))
    opt PDU Sessions exist on the target access
        AMF->>SMF: Nsmf_PDUSession_ReleaseSMContext<br/>(HTTP POST /nsmf-pdusession/v1/sm-contexts/{smContextRef}/release)
        SMF->>UPF: PFCP Session Deletion Request<br/>(PFCP)
        UPF-->>SMF: PFCP Session Deletion Response<br/>(PFCP)
        SMF-->>AMF: 204 No Content<br/>(HTTP)
        Note over AMF,SMF: UDM / PCF cleanup is conditional
    end
    AMF->>RAN: UE Context Release Command<br/>(NGAP)
    RAN->>UE: RRCRelease<br/>(RRC)
    RAN-->>AMF: UE Context Release Complete<br/>(NGAP)
    opt Re-registration is required
        Note over UE,AMF: Re-registration starts as a separate procedure
    end

Step-by-step explanation

  1. The network sends the Request: The direction is reversed compared with UE-initiated deregistration. Check whether re-registration is required.
  2. The UE returns the Accept: The UE can return it after receiving the Request. Its ordering relative to SMF/UPF release completion is not fixed.
  3. Perform network-side cleanup: Apply conditional processing to the target PDU Sessions, UDM subscriptions and registrations, and PCF associations.
  4. Release the connection and follow the instruction: Subsequent UE behavior depends on whether re-registration is required. Deregistration does not always mean immediate re-registration.

UDM-initiated, idle and implicit cases

The UDM can request deregistration using Nudm_UECM_DeregistrationNotification, which the AMF acknowledges. Explicit deregistration of a CM-IDLE UE requires Paging to reach it. Implicit deregistration, however, omits the UE-facing Request/Accept exchange. Do not treat all these cases as the assumptions of the diagram above (TS 23.502 Clause 4.2.2.3.3).

Packet Analysis

  • First check the NAS Request/Accept direction, Access Type, Switch-off indication and re-registration requirement.
  • Correlate the release request on N11 and Session Deletion on N4 with the target PDU Session. How correlation keys are logged or obtained is implementation-dependent.
  • Do not diagnose a failure from the absence of an Accept alone; distinguish switch-off and implicit deregistration.

Knowledge check

  • Is a missing Accept abnormal for UE-initiated switch-off deregistration? → Not necessarily. The AMF does not send it in this case.
  • Is this the same as AN Release? → No. Distinguish deregistration from connection release.

3GPP Specification

Next Step

Registration / PDU Session Release / CM State / Callflow