Registration Reject / Retry¶
Why — Registration failure is more than retransmission¶
Failures in Registration include both explicit rejection and missing responses. This chapter covers the AMF returning Registration Reject, focusing on general NAS congestion control (TS 24.501 Clause 5.5.1.2.5).
The example uses cause 22 "congestion" with T3346. Do not apply the same retry rules to other causes, emergency or priority services, or SNPN-specific conditions.
Procedure — Registration Reject / Retry¶
In this example, a UE performing initial PLMN registration for normal services receives a Reject containing a valid, non-zero and non-deactivated T3346 value. A retry is not guaranteed to succeed (TS 24.501 Clause 5.5.1.2.5).
sequenceDiagram
participant UE
participant RAN as NG-RAN
participant AMF
UE->>RAN: RRCSetupRequest<br/>(RRC)
RAN->>UE: RRCSetup<br/>(RRC)
UE->>RAN: RRCSetupComplete<br/>(RRC#59; NAS: Registration Request)
RAN->>AMF: Initial UE Message<br/>(NGAP#59; NAS-PDU: Registration Request)
Note over AMF: Reject registration using general NAS congestion control
AMF-->>RAN: Downlink NAS Transport<br/>(NGAP#59; NAS-PDU: Registration Reject, cause 22, T3346 value)
RAN-->>UE: DLInformationTransfer<br/>(RRC#59; NAS: Registration Reject)
Note over UE: Abort registration and enter<br/>5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION
alt Reject is integrity protected
Note over UE: Start T3346 with the received value
else Not integrity protected
Note over UE: Start T3346 with a random value from the specified range
end
Note over UE: Wait before a normal registration retry
opt Retry is permitted and the RRC connection is still retained
UE->>RAN: ULInformationTransfer<br/>(RRC#59; NAS: Registration Request)
RAN->>AMF: Uplink NAS Transport<br/>(NGAP#59; NAS-PDU: Registration Request)
endStep-by-step explanation¶
- Request initial registration: NG-RAN forwards the UE's NAS request to the AMF.
- The AMF returns the rejection reason: General NAS congestion control uses 5GMM cause 22 and a T3346 value. Distinguish an explicit Reject from no response.
- The UE aborts the registration attempt: Under this cause's conditions, it sets the update status to
5U2 NOT UPDATED, resets the registration attempt counter and enters5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. - Determine the wait from the protection status: For a Reject without integrity protection, the UE does not simply use the received timer value. It stops any running T3346 before starting the new one.
- Retry when required: When T3346 expires or is stopped, the UE restarts initial registration if registration is still needed. Emergency and priority services follow separate conditions and are excluded here.
Reference: TS 24.501 Clause 5.5.1.2.5. See TS 24.501 Clause 5.1.3.2 for state definitions and Clause 5.2.2.3.3 for retry behavior in ATTEMPTING-REGISTRATION.
Not every Reject means waiting for T3346
This diagram covers specific conditions for cause 22. Check abnormal-case rules for a zero, deactivated or missing T3346 value. Other causes change PLMN/TA selection, registration information and retry conditions. Do not assume a fixed duration; check the received IE and protection status (TS 24.501 Clause 5.5.1.2.5 / Clause 5.5.1.2.7).
What — Four observations to collect¶
- 5GMM cause: The rejection reason's number and meaning.
- T3346 value: Distinguish absence, a valid value, zero and deactivated.
- NAS integrity protection: Even with the same IE value, this affects the timer value the UE actually starts.
- Retry trigger: Follow expiry, stopping the timer and upper-layer requests in time order.
In Wireshark, start with nas-5gs and ngap, and correlate the same UE's request, Reject and next request. Display-field names and logged timer values depend on the dissector and implementation.
Knowledge check¶
- Does the T3346 value in a Reject always tell you the wait duration? → No. Integrity-protection status also matters.
- Does registration succeed after backoff expires? → Permission to retry and success are separate outcomes.
3GPP Specification¶
- TS 24.501 V18.14.0 Clause 5.5.1.2.5 / Clause 5.5.1.2.7 / Clause 5.1.3.2 / Clause 5.2.2.3.3
- TS 38.413 V18.10.0 Clause 8.6.1 / Clause 8.6.2: NAS transport.
Next Step¶
Successful Registration / Authentication Failure / PDU Session Reject / Timer Dictionary