| Protocol | nas | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 24.501 | Spec Section | 8.2.30 |
| Direction | AMF to UE | Message Type | 5GMM signaling |
| Full message name | 5G NAS - DL NAS Transport |
|---|---|
| Protocol | NAS |
| Technology | 5G |
| Direction | AMF to UE |
| Interface | N1 |
| Signaling bearer / channel | NAS signaling / Dedicated NAS message, commonly transported via DL Information Transfer on the access side |
| Typical trigger | Sent when the network needs to deliver a payload to the UE through NAS transport handling instead of using a dedicated top-level 5GMM message. |
| Main purpose | Transports a contained payload from the network to the UE through NAS signaling without defining a separate standalone top-level message for every use case. |
| Main specification | 3GPP TS 24.501, 8.2.30 |
| Release added | Release 15 |
| Procedures where used | Payload delivery over NAS, Protected 5GMM signaling, Core-to-UE transport of embedded information |
DL NAS Transport is the NAS wrapper message the network uses to deliver a payload downward to the UE when the procedure needs to carry additional content transparently through NAS.
Transports a contained payload from the network to the UE through NAS signaling without defining a separate standalone top-level message for every use case.
DL NAS Transport is the network using NAS as a wrapper to send another piece of information down to the UE.
Call flow position: Network-to-UE transport step used when an inner payload must be delivered through NAS signaling.
Typical state: The UE already has a valid NAS relationship and the network is using DL NAS Transport as a wrapper rather than opening a new standalone outer procedure.
Preconditions:
Next likely message: UL NAS Transport or procedure-specific UE handling
Call flow position: Supplementary downlink transport step inside a broader mobility-management or session-related exchange.
Typical state: The outer NAS exchange is stable, but the operational meaning depends mainly on the transported payload.
Preconditions:
Next likely message: Payload-specific response or transport continuation
Previous message(s): UL NAS Transport, Protected NAS procedure state, Procedure-specific core handling
Next message(s): UL NAS Transport, Procedure-specific UE response, 5GMM Status
Security context: Often appears in an already established NAS security context, so engineers should inspect both the outer wrapper and the embedded payload meaning.
This message is not typically analyzed as ASN.1 on the wire. It is usually read as a NAS or protocol field structure instead.
DL NAS Transport follows NAS 24.501 IE structure and is not an ASN.1 message.
DL NAS Transport
Extended Protocol Discriminator: 5G Mobility Management
Security Header Type: Integrity protected and ciphered
Message Type: DL NAS Transport
Payload Container Type: N1 SM information
Payload Container: 2e0101c211...
PDU Session ID: 10
| IE | Required | Description |
|---|---|---|
Payload container type | Yes | Tells you what kind of embedded content the message carries and therefore how the inner payload should be interpreted. |
Payload container | Yes | Carries the actual transported downlink content, which usually matters more than the outer DL NAS Transport wrapper. |
PDU Session ID | Optional | May be present when the transported content is tied to a specific session context. |
Additional information | Optional | Scenario-dependent container extensions that refine how the payload should be handled. |
Payload container typeTells you what kind of embedded content the message carries and therefore how the inner payload should be interpreted.
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.
Payload containerCarries the actual transported downlink content, which usually matters more than the outer DL NAS Transport wrapper.
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.
PDU Session IDMay be present when the transported content is tied to a specific session context.
Presence: Optional
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.
Additional informationScenario-dependent container extensions that refine how the payload should be handled.
Presence: Optional
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: The wrapper may be correct while the embedded payload is malformed, unsupported, or interpreted differently by the UE.
What to inspect: Decode the payload container type and the inner payload before concluding that the NAS downlink transport itself failed.
Next step: Correlate with the matching UL NAS Transport or later UE behavior to see whether the inner content was understood.
Likely cause: DL NAS Transport is a transport wrapper, so reading only the outer message hides the real procedure semantics.
What to inspect: Focus on the payload container type, the payload container contents, and any session identifiers.
Next step: Map the inner payload to its actual procedure instead of treating DL NAS Transport as the whole story.
It carries an embedded payload from the network down to the UE using NAS transport handling.
Usually no. It is often a wrapper, and the real procedure meaning comes from the transported payload.
Start with the payload container type and then decode the inner payload.
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.