| Protocol | nas | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 24.501 | Spec Section | 8.2.13 |
| Direction | AMF to UE | Message Type | 5GMM signaling |
| Full message name | 5G NAS - Deregistration Request (UE Terminated) |
|---|---|
| Protocol | NAS |
| Technology | 5G |
| Direction | AMF to UE |
| Interface | N1 |
| Signaling bearer / channel | NAS signaling / Dedicated NAS message, commonly via DL Information Transfer |
| Typical trigger | Network policy, subscription change, operator action, or AMF-side context removal requiring the UE to deregister. |
| Main purpose | Lets the network instruct the UE to leave registered state and release its mobility-management context. |
| Main specification | 3GPP TS 24.501, 8.2.13 |
| Release added | Release 15 |
| Procedures where used | Network-Initiated Deregistration |
Deregistration Request (UE Terminated) is the AMF-to-UE NAS message used when the network initiates deregistration.
Lets the network instruct the UE to leave registered state and release its mobility-management context.
This is the network telling the UE that it must leave registered 5G service.
Call flow position: Opening network command that tells the UE to leave registered state.
Typical state: UE is registered before the request is received.
Preconditions:
Next likely message: Deregistration Accept (UE Terminated)
Previous message(s): Registered-state NAS signaling
Next message(s): Deregistration Accept (UE Terminated)
Security context: Usually protected because it is sent while valid NAS security context still exists.
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 is defined in NAS 24.501, not ASN.1.
Deregistration Request (UE Terminated)
Extended Protocol Discriminator: 5G Mobility Management
Security Header Type: Integrity protected and ciphered
Message Type: Deregistration Request (UE Terminated)
Deregistration Type: Re-registration required, 3GPP access
| IE | Required | Description |
|---|---|---|
Deregistration type | Yes | Explains the scope and access context of the network-initiated deregistration. |
Deregistration typeExplains the scope and access context of the network-initiated deregistration.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
Likely cause: AMF policy, subscription state, mobility-management reset, or operator-triggered removal.
What to inspect: Check surrounding AMF-side decisions and the deregistration type.
Next step: Correlate with earlier configuration updates, rejects, or core-side state changes.
The AMF sends it when the network initiates deregistration.
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.