5G NAS - PDU Session Release Complete

Message Fact Sheet

Protocol	nas	Network	5g
Spec	3GPP TS 24.501	Spec Section	8.3.15
Direction	UE to SMF via AMF	Message Type	5GSM signaling

Full message name	5G NAS - PDU Session Release Complete
Protocol	NAS
Technology	5G
Direction	UE to SMF via AMF
Interface	N1
Signaling bearer / channel	NAS signaling / Usually carried inside UL NAS Transport on the access side
Typical trigger	The UE received a PDU Session Release Command and is confirming that the session is now considered released.
Main purpose	Confirms that the UE accepted the network's release instruction so the SMF can finish the release procedure and clear the session state.
Main specification	3GPP TS 24.501, 8.3.15
Release added	Release 15
Procedures where used	Network-requested PDU Session Release, UE-requested PDU Session Release, Reactivation requested handling
Related timers	T3592, T3582

What is PDU Session Release Complete in simple terms?

PDU Session Release Complete is the 5GSM message the UE sends after it receives a release command and considers the active PDU session released.

Confirms that the UE accepted the network's release instruction so the SMF can finish the release procedure and clear the session state.

Why this message matters

PDU Session Release Complete is the UE's confirmation that the PDU session has been released.

Where this message appears in the call flow

Network-requested PDU Session Release

Call flow position: UE acknowledgement that the release command was received and the session is now considered released.

Typical state: The UE has received the release command and is telling the network the release is complete.

Preconditions:

A release command was received.
The UE has accepted the release instruction.

Next likely message: The session becomes inactive and any new service requires a fresh establishment request

UE-requested PDU Session Release

Call flow position: UE completion step after the network accepted the release request and sent the release command.

Typical state: The UE is completing the release procedure after the network's downlink instruction.

Preconditions:

The UE previously sent PDU Session Release Request.
The network responded with PDU Session Release Command.

Next likely message: The session becomes inactive

Call flow position

Previous message(s): PDU Session Release Command, UL NAS Transport, UE considered session released

Next message(s): Session becomes inactive, New PDU Session Establishment Request if reactivation or new service is needed

Message direction and transport

Sender and receiver: UE to SMF via AMF

Interface: N1

Domain: Core-side session management completion with access-side NAS delivery dependency

Signaling bearer: NAS signaling

Logical channel: Usually carried inside UL NAS Transport on the access side

Transport / encapsulation: 5GSM NAS message transported end-to-end from the UE to the SMF through AMF mediation

Security context: Normally delivered while NAS security is already active, so engineers usually expect protected uplink NAS handling.

ASN.1 Message Syntax for 5G NAS - PDU Session Release Complete

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 is a 5GSM NAS message defined by ordered information elements in 3GPP TS 24.501 rather than ASN.1 syntax.

5G NAS - PDU Session Release Complete - Example Dump

PDU Session Release Complete
  Extended Protocol Discriminator: 5G Session Management
  PDU Session ID: 10
  PTI: 6
  Message Type: PDU Session Release Complete
  Extended Protocol Configuration Options:
    No additional data

How to read this dump

Start with PDU Session ID to confirm which session the UE is acknowledging as released.
Check PTI to correlate the completion with the right release transaction.
A minimal completion message is normal because the UE often just confirms the session is released.

Important Information Elements

IE	Required	Description
`PDU Session ID`	Yes	Identifies the PDU session that is now considered released.
`PTI`	Yes	Correlates the completion with the release transaction when one exists.
`Extended protocol configuration options`	Optional	May carry additional protocol data from the UE back to the SMF during release completion.

Detailed field explanation

`PDU Session ID`

Identifies the PDU session that is now considered released.

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.

`PTI`

Correlates the completion with the release transaction when one exists.

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.

`Extended protocol configuration options`

May carry additional protocol data from the UE back to the SMF during release completion.

Presence: Optional

In practice: This is where DNS and other operational configuration can hide. When the session is accepted but applications still fail, EPCO is often one of the first optional fields worth validating.

What to check in logs and traces

Confirm the completion follows a visible PDU Session Release Command.
Verify `PDU Session ID` and `PTI` first so the completion matches the right release procedure.
Check whether `T3592` stopped on the network side after the completion arrived.
If the release was UE-requested, verify that `T3582` also stopped on the UE side.
Correlate the completion with the session state transition to inactive.

Common Issues and Troubleshooting

The UE does not send release complete.

Likely cause: The UE may not have received the release command, or the release command may not have been accepted.

What to inspect: Check the release command, the downlink NAS path, and the UE state machine.

Next step: Confirm whether the issue is transport, sequencing, or command parsing.

The network still shows the session as pending release.

Likely cause: The completion may have been lost, delayed, or not correlated with the correct PTI.

What to inspect: Check T3592, PTI correlation, and SMF logs.

Next step: Validate that the UE sent the completion and that the SMF received it in time.

The session remains active after completion.

Likely cause: The network may not have processed the completion correctly, or another procedure may still be holding the session context.

What to inspect: Check SMF release handling and any concurrent modification or reactivation procedure.

Next step: Confirm the session state transition in the core network.

FAQ

What does PDU Session Release Complete do?

It confirms that the UE accepted the release command and considers the PDU session released.

Who sends PDU Session Release Complete?

The UE sends it to the SMF via the AMF.

When is PDU Session Release Complete sent?

It is sent after the UE receives a PDU Session Release Command.

What are the important IEs in PDU Session Release Complete?

Start with PDU Session ID and PTI, then inspect any Extended Protocol Configuration Options field.

What happens after PDU Session Release Complete?

The network stops waiting for the release procedure and the session becomes inactive.

Is ASN.1 used for PDU Session Release Complete?

No. It is a 5GSM NAS message defined by structured information elements in 3GPP TS 24.501.

Can this message carry configuration data?

Yes. It can include extended protocol configuration options.

What timer is related to this message?

T3592 is the main network-side timer that should stop when the completion is received.

Related message pages

Related Procedures

Related Tools

Use This Reference in Practice

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.