Downlink UE Associated NRPPa Transport is the NGAP positioning transport message sent by the AMF to the NG-RAN node to carry UE-associated NRPPa signalling.
AMF receives or relays UE-associated NRPPa information that must be transported toward the NG-RAN for a specific UE positioning procedure.
Main purpose
Transports UE-associated NRPPa signalling toward NG-RAN, supports UE positioning procedures, preserves UE context with AMF UE NGAP ID and RAN UE NGAP ID, carries NRPPa-PDU as a transparent payload, and separates NGAP transport handling from NRPPa message interpretation.
Main specification
3GPP TS 38.413, Downlink UE Associated NRPPa Transport message
What is Downlink UE Associated NRPPa Transport in simple terms?
Downlink UE Associated NRPPa Transport is the NGAP positioning transport message sent by the AMF to the NG-RAN node to carry UE-associated NRPPa signalling.
Transports UE-associated NRPPa signalling toward NG-RAN, supports UE positioning procedures, preserves UE context with AMF UE NGAP ID and RAN UE NGAP ID, carries NRPPa-PDU as a transparent payload, and separates NGAP transport handling from NRPPa message interpretation.
Why this message matters
Downlink UE Associated NRPPa Transport is the AMF sending a UE-specific positioning payload to the gNB. NGAP carries the envelope; NRPPa explains the positioning content inside.
Where this message appears in the call flow
UE-associated NRPPa Transport
AMF uses NGAP to deliver a UE-associated NRPPa-PDU toward NG-RAN.
Call flow position: AMF sends this UE-associated initiatingMessage when NRPPa positioning signalling must be delivered toward NG-RAN for a specific UE.
Typical state: NG-RAN receives the transparent NRPPa-PDU and associates it with the UE context identified by the AMF and RAN UE NGAP IDs.
Preconditions:
A UE-associated NGAP context exists.
AMF UE NGAP ID and RAN UE NGAP ID identify the correct UE.
AMF has an encoded NRPPa-PDU to relay toward NG-RAN.
Next likely message: Uplink UE Associated NRPPa Transport
Transparent NRPPa payload handling
NGAP carries UE correlation and transport; NRPPa-PDU is decoded as NRPPa.
Call flow position: NGAP provides transport and UE correlation; the NRPPa content is decoded by NRPPa logic, not by NGAP.
Typical state: Trace analysis separates the NGAP envelope from the positioning message inside NRPPa-PDU.
Preconditions:
NRPPa-PDU is present and decodable by the analyzer.
The decoder supports the relevant NRPPa release and payload type.
Next likely message: NRPPa procedure continuation
UE-associated versus non-UE-associated positioning
Use the UE-associated branch when the positioning procedure belongs to a specific UE.
Call flow position: Use this message when the NRPPa signalling is tied to a specific UE context.
Typical state: UE identifiers are mandatory context for the transport branch, unlike non-UE-associated NRPPa transport.
Preconditions:
The positioning procedure relates to one UE.
UE ID correlation has not been lost through mobility or release.
Next likely message: Correct transport branch selection
Call flow position
Previous message(s): UE-associated positioning procedure is active, AMF has an NRPPa payload for downlink relay
Transport / encapsulation: NGAP over SCTP/IP between AMF and NG-RAN
Security context: Downlink UE Associated NRPPa Transport carries UE-specific positioning signalling. Correlate it with the authorized positioning procedure and handle the NRPPa payload according to operator privacy and regulatory policy.
Message Structure Overview
Downlink UE Associated NRPPa Transport is an AMF-to-NG-RAN UE-associated initiatingMessage.
AMF UE NGAP ID and RAN UE NGAP ID bind the transported positioning payload to the correct UE context.
NRPPa-PDU is the main payload and is interpreted using NRPPa, not NGAP.
Routing ID can support correct routing of positioning signalling when present or required by the deployment.
The likely reverse or follow-up path is Uplink UE Associated NRPPa Transport.
ASN.1 for Downlink UE Associated NRPPa Transport
DownlinkUEAssociatedNRPPaTransport ::= SEQUENCE {
protocolIEs ProtocolIE-Container { {DownlinkUEAssociatedNRPPaTransport-IEs} },
...
}
DownlinkUEAssociatedNRPPaTransport-IEs NGAP-PROTOCOL-IES ::= {
{ ID id-AMF-UE-NGAP-ID CRITICALITY reject TYPE AMF-UE-NGAP-ID PRESENCE mandatory } |
{ ID id-RAN-UE-NGAP-ID CRITICALITY reject TYPE RAN-UE-NGAP-ID PRESENCE mandatory } |
{ ID id-RoutingID CRITICALITY reject TYPE RoutingID PRESENCE optional } |
{ ID id-NRPPa-PDU CRITICALITY reject TYPE NRPPa-PDU PRESENCE mandatory },
...
}
How to read this ASN.1
Read this as an NGAP envelope around an encoded NRPPa payload. Decode UE identifiers and any Routing ID at NGAP level, then decode NRPPa-PDU with an NRPPa decoder.
Downlink UE Associated NRPPa Transport - Example Dump
Treat this as a teaching example based on the expected message structure, not as a captured network trace.
NRPPa-PDU is opaque to NGAP and must be decoded using NRPPa rules.
AMF UE NGAP ID and RAN UE NGAP ID decide which UE context receives the positioning payload.
Important Information Elements
IE
Required
Description
Message Type
Yes
Identifies the NGAP PDU as DOWNLINK UE ASSOCIATED NRPPA TRANSPORT.
AMF UE NGAP ID
Yes
Mandatory UE identity at the AMF.
RAN UE NGAP ID
Yes
Mandatory UE identity at the NG-RAN node.
Routing ID
Optional
Routing information for positioning transport when used by the involved positioning entities.
NRPPa-PDU
Yes
Encoded NRPPa payload carried transparently by NGAP.
Detailed field explanation
Message Type
Identifies the NGAP PDU as DOWNLINK UE ASSOCIATED NRPPA TRANSPORT.
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.
AMF UE NGAP ID
Mandatory UE identity at the AMF.
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.
RAN UE NGAP ID
Mandatory UE identity at the NG-RAN node.
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.
Routing ID
Routing information for positioning transport when used by the involved positioning entities.
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.
NRPPa-PDU
Encoded NRPPa payload carried transparently by NGAP.
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.
What to check in logs and traces
Confirm the direction is AMF to NG-RAN.
Verify AMF UE NGAP ID and RAN UE NGAP ID match an active UE context.
Check that NRPPa-PDU is present and not malformed.
Check Routing ID when it is present or expected by the deployment.
Look for Uplink UE Associated NRPPa Transport when a response or follow-up is expected.
Use an analyzer that can decode the NRPPa payload rather than only showing opaque bytes.
Separate NGAP transport issues from NRPPa procedure or payload issues.
Common Issues and Troubleshooting
The downlink transport appears but the positioning procedure does not continue.
Likely cause: The NRPPa-PDU may be malformed, unsupported by the decoder or node, or delivered to the wrong UE context.
What to inspect: Check UE IDs first, then decode NRPPa-PDU with NRPPa support enabled.
Next step: Separate N2 delivery and UE correlation from the inner NRPPa procedure failure.
NRPPa payload is shown only as opaque bytes.
Likely cause: The analyzer may decode NGAP but not the embedded NRPPa release or message type.
What to inspect: Verify analyzer NRPPa support, release settings, and payload handoff from NGAP to NRPPa decoding.
Next step: Use a decoder profile that supports the relevant NRPPa payload.
Message is associated with the wrong UE.
Likely cause: AMF UE NGAP ID or RAN UE NGAP ID correlation may be stale after mobility, context release, or trace window truncation.
What to inspect: Compare IDs with Initial Context Setup, handover, path switch, and release messages.
Next step: Rebuild the UE context timeline before interpreting positioning signalling.
Routing appears inconsistent across positioning messages.
Likely cause: Routing ID or positioning entity mapping may not match the expected transport path.
What to inspect: Compare Routing ID values across downlink and uplink NRPPa transport messages.
Next step: Validate routing configuration between positioning-related core functions, AMF, and NG-RAN.
A non-UE-associated transport is expected instead.
Likely cause: The procedure may be node-level or general positioning signalling rather than tied to a UE.
What to inspect: Check whether AMF UE NGAP ID and RAN UE NGAP ID are required for the procedure context.
Next step: Use UE-associated transport only for UE-specific positioning branches.
LTE / 5G / Variant Comparison
Compared with Uplink UE Associated NRPPa Transport
Downlink UE Associated NRPPa Transport carries UE-associated NRPPa from AMF to NG-RAN. Uplink UE Associated NRPPa Transport carries the reverse direction from NG-RAN to AMF.
Compared with non-UE-associated NRPPa transport
UE-associated transport includes AMF UE NGAP ID and RAN UE NGAP ID. Non-UE-associated transport is used for positioning signalling that is not tied to one UE context.
Compared with Location Reporting
Location Reporting messages are NGAP location reporting procedures. NRPPa Transport carries encoded NRPPa positioning signalling as a payload.
FAQ
What is Downlink UE Associated NRPPa Transport in NGAP?
It is the AMF-to-NG-RAN NGAP message used to carry UE-associated NRPPa positioning signalling for a specific UE.
Who sends this message?
The AMF sends Downlink UE Associated NRPPa Transport to the NG-RAN node.
What does NRPPa-PDU contain?
NRPPa-PDU contains the encoded NRPPa positioning message. NGAP transports it but does not interpret the positioning contents.
Is this message UE-associated?
Yes. It carries AMF UE NGAP ID and RAN UE NGAP ID so the transported NRPPa payload is tied to a specific UE context.
How is it different from non-UE-associated NRPPa transport?
UE-associated transport includes UE identifiers and is used for UE-specific positioning procedures. Non-UE-associated transport is used for node-level or general positioning signalling without a specific UE context.
Does NGAP decode the NRPPa payload?
No. NGAP carries NRPPa-PDU transparently. The payload must be decoded according to NRPPa specifications.
What is Routing ID used for?
Routing ID supports routing of NRPPa signalling between involved positioning entities and NG-RAN when that routing context is used.
How do you troubleshoot NRPPa transport issues?
Confirm AMF-to-NG-RAN direction, match UE IDs, verify NRPPa-PDU presence, check Routing ID if used, and decode the embedded payload with an NRPPa-aware analyzer.
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.
