What does Deregistration Accept (UE Originating) do?
It confirms that the network accepted the UE's deregistration request.
| Protocol | nas | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 24.501 | Spec Section | 8.2.12 |
| Direction | AMF to UE | Message Type | 5GMM signaling |
| Full message name | 5G NAS - Deregistration Accept (UE Originating) |
|---|---|
| Protocol | NAS |
| Technology | 5G |
| Direction | AMF to UE |
| Interface | N1 |
| Signaling bearer / channel | NAS signaling / Dedicated NAS message, commonly transported through DL Information Transfer |
| Typical trigger | Sent after a valid UE-originated Deregistration Request. |
| Main purpose | Confirms that the network processed the UE-originated deregistration and that the UE can treat the deregistration exchange as complete. |
| Main specification | 3GPP TS 24.501, 8.2.12 |
| Release added | Release 15 |
| Procedures where used | UE-Originated Deregistration |
Deregistration Accept (UE Originating) is the AMF response confirming that the UE-originated deregistration request was accepted.
Confirms that the network processed the UE-originated deregistration and that the UE can treat the deregistration exchange as complete.
This is the network confirming that the UE-originated deregistration is complete.
Call flow position: Network confirmation at the end of a successful UE-originated deregistration exchange.
Typical state: UE is leaving a previously registered state.
Preconditions:
Next likely message: No immediate follow-on NAS message is required in the successful basic path
Previous message(s): Deregistration Request (UE Originating)
Next message(s): UE leaves registered state
Security context: Commonly protected if valid NAS security still exists during the deregistration exchange.
This message is not typically analyzed as ASN.1 on the wire. It is usually read as a NAS or protocol field structure instead.
This message follows NAS 24.501 formatting rather than ASN.1.
Deregistration Accept (UE Originating)
Extended Protocol Discriminator: 5G Mobility Management
Security Header Type: Integrity protected and ciphered
Message Type: Deregistration Accept (UE Originating)
Likely cause: The network may not have received or processed the request, or the trace may be incomplete.
What to inspect: Check uplink delivery, DL Information Transfer, and AMF-side state.
Next step: Correlate with later paging or residual registered behavior.
It confirms that the network accepted the UE's deregistration request.
Decode this message with the 3GPP Decoder, inspect the related message database, or open the matching call flow to see where this signaling step fits in the full procedure.