UE Context Suspend Request is the NGAP message sent by the NG-RAN node to the AMF when the RAN requests suspension of an existing UE-associated NGAP context instead of full release.
NG-RAN decides that a UE-associated context should be suspended and preserved for possible later resume instead of being fully released.
Main purpose
Requests suspension of an existing UE-associated NGAP context, gives AMF the UE identity and suspend reason, preserves continuity for later resume handling, and separates suspend handling from full UE context release cleanup.
What is UE Context Suspend Request in simple terms?
UE Context Suspend Request is the NGAP message sent by the NG-RAN node to the AMF when the RAN requests suspension of an existing UE-associated NGAP context instead of full release.
Requests suspension of an existing UE-associated NGAP context, gives AMF the UE identity and suspend reason, preserves continuity for later resume handling, and separates suspend handling from full UE context release cleanup.
Why this message matters
UE Context Suspend Request is the gNB asking AMF to preserve an existing UE context in suspended handling. It is not the same as release, and AMF must still accept or reject the suspend request.
Where this message appears in the call flow
UE Context Suspend
Suspend branch: NG-RAN asks AMF to suspend an existing UE-associated context rather than fully release it.
Call flow position: NG-RAN sends this initiatingMessage when it asks AMF to suspend an existing UE-associated context.
Typical state: The context exists and is being moved toward suspend handling, pending AMF acceptance or rejection.
Preconditions:
AMF UE NGAP ID and RAN UE NGAP ID identify the active UE-associated NGAP context.
NG-RAN has a suspend reason available in the Cause IE.
Optional location, PDU session, or suspend transfer context may be available.
Next likely message: UE Context Suspend Response or UE Context Suspend Failure
Suspend accepted
Outcome branch: AMF either accepts the suspend request with Suspend Response or rejects it with Suspend Failure.
Call flow position: AMF accepts the suspend request and returns UE Context Suspend Response.
Typical state: The UE context can be preserved in suspended handling for a later resume branch.
Preconditions:
AMF can retain the necessary UE context state.
The request is valid for the current UE context.
Next likely message: Later UE Context Resume Request
Suspend rejected
Role comparison: suspend preserves continuity, release cleans up context, and resume brings a suspended context back.
Call flow position: AMF cannot accept the requested suspend state and returns UE Context Suspend Failure.
Typical state: Suspend continuity is not established; AMF and NG-RAN must handle the failure according to the returned reason and local policy.
Preconditions:
AMF determines the context cannot be suspended.
Failure handling is needed instead of assuming later resume is possible.
Next likely message: Failure handling, fallback, or release procedure
Transport / encapsulation: NGAP over SCTP/IP between NG-RAN and AMF
Security context: The message assumes an existing UE-associated NGAP context. It asks AMF to put the context into suspend handling rather than treating the event as immediate full release.
Message Structure Overview
UE Context Suspend Request is an NG-RAN-to-AMF initiatingMessage in UE Context Management.
It requests suspend handling for an existing UE-associated NGAP context instead of full release cleanup.
AMF UE NGAP ID and RAN UE NGAP ID identify the context.
Cause is mandatory and explains why NG-RAN requests suspension.
Optional User Location Information, PDU Session Resource List, and Suspend Request Transfer add context for AMF handling.
The normal AMF outcomes are UE Context Suspend Response or UE Context Suspend Failure.
ASN.1 for 5G NGAP - UE Context Suspend Request
UEContextSuspendRequest ::= SEQUENCE {
protocolIEs ProtocolIE-Container { {UEContextSuspendRequest-IEs} },
...
}
UEContextSuspendRequest-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-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } |
{ ID id-UserLocationInformation CRITICALITY ignore TYPE UserLocationInformation PRESENCE optional } |
{ ID id-PDUSessionResourceList CRITICALITY ignore TYPE PDUSessionResourceList PRESENCE optional } |
{ ID id-SuspendRequestTransfer CRITICALITY ignore TYPE SuspendRequestTransfer PRESENCE optional },
...
}
How to read this ASN.1
Decode the UE identity pair and Cause first. Optional location, PDU session, and suspend transfer fields explain the context AMF may need to preserve for later resume handling.
5G NGAP - UE Context Suspend Request - Example Dump
Treat this as a teaching example based on the expected message structure, not as a captured network trace.
The request asks AMF to suspend the context; it does not prove that suspend was accepted.
Look for UE Context Suspend Response or UE Context Suspend Failure after this request.
If the context is later resumed, correlate the Resume Request with the same UE context continuity.
Important Information Elements
IE
Required
Description
Message Type
Yes
Identifies the NGAP PDU as UE CONTEXT SUSPEND REQUEST.
AMF UE NGAP ID
Yes
Mandatory AMF-side UE identifier used to bind the suspend request to the correct UE-associated NGAP context.
RAN UE NGAP ID
Yes
Mandatory NG-RAN-side UE identifier used to identify the radio-side UE context being suspended.
Cause
Yes
Mandatory reason why NG-RAN is requesting suspension. This is the first field to inspect during troubleshooting.
User Location Information
Optional
Optional latest UE location when the suspend request is sent.
PDU Session Resource List
Optional
Optional list of PDU session resources associated with the UE context being suspended.
Suspend Request Transfer
Optional
Optional suspend-related transfer or context information used by AMF for suspend and later resume handling.
Detailed field explanation
Message Type
Identifies the NGAP PDU as UE CONTEXT SUSPEND REQUEST.
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 AMF-side UE identifier used to bind the suspend request to the correct UE-associated NGAP context.
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 NG-RAN-side UE identifier used to identify the radio-side UE context being suspended.
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.
Cause
Mandatory reason why NG-RAN is requesting suspension. This is the first field to inspect during troubleshooting.
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.
User Location Information
Optional latest UE location when the suspend request is sent.
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.
PDU Session Resource List
Optional list of PDU session resources associated with the UE context being suspended.
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.
Suspend Request Transfer
Optional suspend-related transfer or context information used by AMF for suspend and later resume handling.
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.
What to check in logs and traces
Confirm the message direction is NG-RAN node to AMF.
Match AMF UE NGAP ID and RAN UE NGAP ID to the active UE context.
Decode Cause before interpreting optional context.
Check User Location Information and PDU Session Resource List when present.
Inspect Suspend Request Transfer when present.
Verify AMF responds with UE Context Suspend Response or UE Context Suspend Failure.
If a later resume occurs, correlate UE Context Resume Request with the suspended context.
Common Issues and Troubleshooting
Suspend is treated as a full UE context release.
Likely cause: UE Context Suspend Request is being confused with UE Context Release Request.
What to inspect: Check the message name, procedure, and whether AMF returns Suspend Response or Suspend Failure rather than Release Command.
Next step: Analyze suspend continuity first; move to release analysis only if release signaling appears.
Later resume behavior is expected but never appears.
Likely cause: Suspend may not have been accepted, or the trace may be missing UE Context Suspend Response.
What to inspect: Find the AMF outcome after the request and confirm whether Suspend Response or Suspend Failure was sent.
Next step: Only expect resume continuity after a successful suspend branch.
The suspend reason is unclear.
Likely cause: Cause IE may have been skipped or mapped too broadly.
What to inspect: Decode Cause first and compare it with preceding radio, mobility, transport, or local RAN events.
Next step: Use the cause category to decide whether the issue is expected suspend behavior, a failure path, or a release candidate.
PDU session state looks inconsistent after suspend.
Likely cause: PDU Session Resource List or suspend transfer context may not have been decoded.
What to inspect: Check PDU Session Resource List and any Suspend Request Transfer content by PDU Session ID.
Next step: Correlate those sessions with later suspend response, resume request, or release handling.
Wrong UE context is associated during a busy suspend event.
Likely cause: AMF UE NGAP ID and RAN UE NGAP ID correlation may be stale or mixed with other UE context procedures.
What to inspect: Rebuild the UE identity timeline across the active context, suspend request, AMF outcome, and later resume or release.
Next step: Fix identity correlation before interpreting Cause or session impact.
LTE / 5G / Variant Comparison
Compared with UE Context Release Request
Release Request asks AMF to release the UE context. Suspend Request asks AMF to preserve the context in suspended handling.
Suspend Request moves an active context toward suspension. Resume Request brings a suspended context back.
FAQ
What is UE Context Suspend Request in NGAP?
It is the NG-RAN-to-AMF message used when NG-RAN asks AMF to suspend an existing UE-associated NGAP context instead of fully releasing it.
Who sends UE Context Suspend Request?
The NG-RAN node sends UE Context Suspend Request to the AMF.
When is UE Context Suspend Request used?
It is used when a UE context already exists and NG-RAN wants AMF to handle it as suspended so continuity may be preserved for later resume.
What is the response to UE Context Suspend Request?
AMF responds with UE Context Suspend Response if suspension is accepted, or UE Context Suspend Failure if it is rejected.
What is the difference between suspend and release?
Suspend preserves UE context continuity for possible resume. Release tears down the UE-associated context through the release procedure.
Can a suspended UE context be resumed later?
Yes. After a successful suspend branch, a later UE Context Resume Request can bring the suspended context back.
What does the Cause IE mean?
Cause explains why NG-RAN is requesting suspension and is the main troubleshooting field in the request.
How do you troubleshoot UE Context Suspend Request?
Match both UE NGAP IDs, decode Cause first, inspect optional location and PDU session context, verify Suspend Response or Suspend Failure, and correlate any later Resume 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.
