Skip to content

PDU Session Reject — Rejection and Subsequent Behavior

Why — Registration success is not data-session success

A registered UE's requested PDU Session is not necessarily accepted. As a companion to PDU Session Establishment, this chapter follows an SMF-generated PDU Session Establishment Reject (TS 24.501 Clause 6.4.1.4.1).

The rejection reason is a 5GSM cause. Do not compare its number alone with the 5GMM causes used in Registration Reject.

Procedure — PDU Session Reject

The UE specifies a DNN, and the selected SMF rejects the request before creating an N4 Session. This example is limited to non-roaming normal services, with cause 26 "insufficient resources" and a non-zero, non-deactivated Back-off timer value (TS 24.501 Clause 6.4.1.4.1 / Clause 6.4.1.4.2). Assuming the SMF detects congestion for the requested DNN, this example illustrates HTTP 503 / DNN_CONGESTION on SBI and 5GSM cause 26 in N1. They belong to different layers: the example does not imply a fixed mapping from cause 26 to 503. The Release 18 OpenAPI for TS 29.502 Clause 5.2.2.2.1 / Clause 6.1.3.2.3.1 permits a 503 multipart response with SmContextCreateError and a binary N1 SM part; Clause 6.1.7.3 defines DNN_CONGESTION. Actual SBI errors depend on the failure and implementation.

sequenceDiagram
    participant UE
    participant RAN as NG-RAN
    participant AMF
    participant SMF
    UE->>RAN: ULInformationTransfer<br/>(RRC#59; UL NAS Transport: DNN, S-NSSAI#59; payload: PDU Session Establishment Request)
    RAN->>AMF: Uplink NAS Transport<br/>(NGAP#59; NAS-PDU: UL NAS Transport)
    Note over UE: Manage establishment with T3580
    AMF->>SMF: Nsmf_PDUSession_CreateSMContext<br/>(HTTP POST /nsmf-pdusession/v1/sm-contexts)
    Note over SMF: Reject due to insufficient resources<br/>No N4 Session created in this example
    SMF-->>AMF: 503 Service Unavailable<br/>(HTTP multipart#59; SmContextCreateError: error cause DNN_CONGESTION, n1SmMsg#59; binaryDataN1SmMessage: PDU Session Establishment Reject)
    AMF-->>RAN: Downlink NAS Transport<br/>(NGAP#59; NAS-PDU: DL NAS Transport / Reject, 5GSM cause 26, Back-off timer value)
    RAN-->>UE: DLInformationTransfer<br/>(RRC#59; DL NAS Transport / PDU Session Establishment Reject)
    Note over UE: Stop T3580 and release PTI<br/>PDU Session not established
    Note over UE: Start T3396 for the target DNN<br/>Restrict normal retries
    opt Retry becomes permitted, e.g. T3396 expires, and connectivity is needed
        UE->>RAN: ULInformationTransfer<br/>(RRC#59; UL NAS Transport / PDU Session Establishment Request)
        RAN->>AMF: Uplink NAS Transport<br/>(NGAP#59; NAS-PDU: UL NAS Transport)
    end

Step-by-step explanation

  1. Forward the 5GSM request: RRC and NGAP carry the request to the AMF, which POSTs it to the SMF. DNN and S-NSSAI are in the outer UL NAS Transport (TS 23.502 Clause 4.3.2.2.1, TS 24.501 Clause 8.2.10).
  2. The SMF generates the Reject: In this example's 503 multipart response, n1SmMsg in the JSON references a binary N1 SM part containing the cause 26 Reject. Check the HTTP status and 5GSM cause independently. No N4 Session exists here, so no deletion of a nonexistent PFCP Session is shown.
  3. The UE ends the establishment attempt: On receiving the Reject, it stops T3580, releases the allocated PTI and determines that this PDU Session was not established (TS 24.501 Clause 6.4.1.4.1).
  4. Restrict requests for the target DNN: Here the UE starts T3396 with the received value, restricting normal re-establishment requests and other applicable requests for that DNN. This timer does not indiscriminately stop all UE communication (TS 24.501 Clause 6.4.1.4.2).
  5. Treat a retry as a separate attempt: Backoff expiry does not guarantee resource availability. Follow the next request and response separately.

Keep different rejection paths separate

Distinguish a NAS Transport notification that the AMF cannot forward a 5GSM request from an SMF-generated 5GSM Reject. If failure occurs after resources such as N4 have been created, check cleanup of those resources separately. SBI response structure and detailed ordering depend on the failure point (TS 24.501 Clause 5.4.5 / Clause 6.4.1.4; TS 23.502 Clause 4.3.2.2.1).

What — Read the cause together with backoff

  • 26: insufficient resources. The diagram shows congestion control with a Back-off timer value.
  • 27: missing or unknown DNN. Start by checking DNN configuration, but do not assume this cause always means no timer is present.
  • 33: requested service option not subscribed. Check the requested service against subscription information.

These causes are specified in TS 24.501 Clause 6.4.1.4.1; congestion and non-congestion backoff are covered in Clause 6.4.1.4.2 / Clause 6.4.1.4.3. Zero or deactivated values, an unspecified DNN, slice-level control, and emergency or priority services involve conditions different from this diagram.

Packet Analysis

In nas-5gs, check PDU Session ID, PTI, 5GSM cause and Back-off timer value to correlate the request with the Reject. Also inspect the SMF response on N11 and whether N4 resources were created. Log correlation methods and display-field names are implementation-dependent.

Knowledge check

  • Does a PDU Session Reject always deregister the UE? → No. Registration and the establishment outcome of that session are separate.
  • Does every establishment rejection require PFCP Session Deletion? → No. It depends on which resources have already been created.

3GPP Specification

Next Step

Successful PDU Session Establishment / Modification and Release / Registration Reject / Cause Dictionary