UE Context Resume Request is the NGAP message sent by the NG-RAN node to the AMF when the RAN requests resumption of a previously suspended UE-associated NGAP context.
NG-RAN detects UE activity or signaling that requires a previously suspended UE context to be restored.
Main purpose
Requests resumption of a suspended UE-associated NGAP context, avoids full UE context re-establishment, gives AMF the UE identity and resume context, supports faster reconnection, and preserves PDU session continuity where possible.
UE Context Resume, UE Context Suspend, UE Context Management, Suspend/resume mobility optimization, Fast reconnection and context continuity
What is UE Context Resume Request in simple terms?
UE Context Resume Request is the NGAP message sent by the NG-RAN node to the AMF when the RAN requests resumption of a previously suspended UE-associated NGAP context.
Requests resumption of a suspended UE-associated NGAP context, avoids full UE context re-establishment, gives AMF the UE identity and resume context, supports faster reconnection, and preserves PDU session continuity where possible.
Why this message matters
UE Context Resume Request is the gNB asking AMF to bring back a previously suspended UE context. It is faster than a fresh setup when the suspended context is still valid.
Where this message appears in the call flow
UE Context Resume
Resume branch: NG-RAN asks AMF to restore a previously suspended UE-associated context.
Call flow position: NG-RAN sends this initiatingMessage when it wants AMF to restore a previously suspended UE-associated context.
Typical state: The UE context should already be suspended and is being moved back toward active handling, pending AMF validation.
Preconditions:
A successful UE Context Suspend branch previously created suspended context state.
AMF UE NGAP ID and RAN UE NGAP ID identify the suspended UE context.
NG-RAN has a resume trigger available in the Cause IE.
Next likely message: UE Context Resume Response or UE Context Resume Failure
Fast reconnection optimization
Outcome branch: AMF either resumes the suspended context or rejects the attempt with Resume Failure.
Call flow position: Resume Request avoids creating a brand-new UE context when a valid suspended context can be restored.
Typical state: AMF can reuse retained UE context and PDU session state instead of taking the full setup path.
Preconditions:
Suspended context has not expired or been released.
Security and UE identity correlation still match.
Next likely message: UE Context Resume Response
Resume failure and fallback
Optimization branch: resume reuses retained state, while setup creates a new context path.
Call flow position: If AMF cannot find, validate, or restore the suspended context, it rejects the resume attempt.
Typical state: NG-RAN may need fallback handling, such as a new setup path or release/recovery procedure.
Preconditions:
Suspended context is missing, expired, mismatched, or inconsistent.
Transport / encapsulation: NGAP over SCTP/IP between NG-RAN and AMF
Security context: The message assumes a previously suspended UE-associated NGAP context. AMF must validate that the suspended context can be resumed before treating the UE context as active again.
Message Structure Overview
UE Context Resume Request is an NG-RAN-to-AMF initiatingMessage in UE Context Management.
It requests restoration of a previously suspended UE-associated NGAP context.
AMF UE NGAP ID and RAN UE NGAP ID locate the suspended context.
Cause is mandatory and explains why NG-RAN is requesting resume.
Optional location, PDU session resume list, and resume transfer fields help AMF validate and restore state.
AMF answers with UE Context Resume Response or UE Context Resume Failure.
ASN.1 for 5G NGAP - UE Context Resume Request
UEContextResumeRequest ::= SEQUENCE {
protocolIEs ProtocolIE-Container { {UEContextResumeRequest-IEs} },
...
}
UEContextResumeRequest-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-PDUSessionResourceResumeList CRITICALITY ignore TYPE PDUSessionResourceResumeList PRESENCE optional } |
{ ID id-ResumeRequestTransfer CRITICALITY ignore TYPE ResumeRequestTransfer PRESENCE optional },
...
}
How to read this ASN.1
Decode the UE identity pair first and confirm the same context had a successful suspend branch. Cause explains the resume trigger; optional session and transfer fields support state restoration.
5G NGAP - UE Context Resume Request - Example Dump
Treat this as a teaching example based on the expected message structure, not as a captured network trace.
Resume Request requires a valid suspended context; do not analyze it like a fresh setup request.
AMF must answer with UE Context Resume Response or UE Context Resume Failure.
PDU sessions are expected to continue from retained state where resume succeeds, not be recreated from scratch.
Important Information Elements
IE
Required
Description
Message Type
Yes
Identifies the NGAP PDU as UE CONTEXT RESUME REQUEST.
AMF UE NGAP ID
Yes
Mandatory AMF-side UE identifier used to locate and correlate the suspended UE context.
RAN UE NGAP ID
Yes
Mandatory NG-RAN-side UE identifier used to bind the resume request to the radio-side UE context.
Cause
Yes
Mandatory reason or trigger for requesting resume. This is important when troubleshooting why resume was attempted.
User Location Information
Optional
Optional UE location at resume time, useful for validating serving area and mobility context.
PDU Session Resource Resume List
Optional
Optional list of PDU session resources associated with the resume attempt.
Resume Request Transfer
Optional
Optional resume-specific transfer or context information needed by AMF to restore UE state.
Detailed field explanation
Message Type
Identifies the NGAP PDU as UE CONTEXT RESUME 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 locate and correlate the suspended UE 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 bind the resume request to the radio-side UE 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.
Cause
Mandatory reason or trigger for requesting resume. This is important when troubleshooting why resume was attempted.
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 UE location at resume time, useful for validating serving area and mobility 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.
PDU Session Resource Resume List
Optional list of PDU session resources associated with the resume attempt.
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.
Resume Request Transfer
Optional resume-specific transfer or context information needed by AMF to restore UE state.
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 UE context was previously suspended with UE Context Suspend Response.
Match AMF UE NGAP ID and RAN UE NGAP ID to the suspended context.
Decode Cause and confirm the resume trigger makes sense.
Inspect User Location Information when mobility or serving-area validation matters.
Check PDU Session Resource Resume List and Resume Request Transfer when present.
Verify AMF responds with UE Context Resume Response or UE Context Resume Failure.
Check PDU session continuity after a successful resume.
Common Issues and Troubleshooting
Resume Request is sent but AMF rejects it.
Likely cause: The suspended context may be missing, expired, released, or security/state validation may fail.
What to inspect: Look backward for UE Context Suspend Response and any later release, expiry, or identity change before the resume attempt.
Next step: If the suspended context is invalid, fall back to setup or recovery rather than retrying resume blindly.
Resume is confused with fresh UE context setup.
Likely cause: Trace analysis is ignoring the prior suspend state.
What to inspect: Compare Resume Request with Initial UE Message or setup signaling and confirm whether retained UE IDs are used.
Next step: Analyze this path as context restoration, not new context creation.
PDU sessions appear to restart from scratch.
Likely cause: Session continuity may be misread, or resume failed and fallback setup occurred.
What to inspect: Check UE Context Resume Response versus Failure, then correlate PDU Session Resource Resume List with later PDU session messages.
Next step: Separate successful resume continuity from fallback setup after resume failure.
Wrong UE context is resumed.
Likely cause: AMF UE NGAP ID and RAN UE NGAP ID mapping may be stale or mixed across suspend, resume, release, or new setup branches.
What to inspect: Rebuild the UE ID timeline from suspend request/response through resume request and AMF outcome.
Next step: Fix identity correlation before interpreting Cause or PDU session behavior.
Resume succeeds but service still fails.
Likely cause: Context restoration may have succeeded while PDU session, location, or radio state synchronization remains inconsistent.
What to inspect: Check optional location, PDU Session Resource Resume List, and later session or radio messages.
Next step: Troubleshoot continuity by PDU Session ID and serving-cell context after the resume response.
LTE / 5G / Variant Comparison
Compared with UE Context Suspend Response
Suspend Response establishes successful suspended state. Resume Request attempts to restore that suspended context.
Compared with Initial UE Message or setup
Resume restores retained context. Initial setup creates a new context path when no valid suspended state can be reused.
It is the NG-RAN-to-AMF message used to request restoration of a previously suspended UE-associated NGAP context.
Who sends UE Context Resume Request?
The NG-RAN node sends UE Context Resume Request to the AMF.
When is UE Context Resume Request used?
It is used when NG-RAN detects that a suspended UE context needs to become active again.
What is the difference between resume and setup?
Resume restores a retained suspended context. Setup creates a new UE context path when no valid retained context is reused.
What happens if resume fails?
AMF sends UE Context Resume Failure, and NG-RAN may need fallback handling such as a new setup or recovery procedure.
Are PDU sessions recreated during resume?
Not in the normal successful resume branch. The goal is PDU session continuity from retained context rather than recreation.
What does the Cause IE indicate?
Cause indicates why NG-RAN is requesting resume, such as UE activity, signaling need, or another resume trigger.
How do you troubleshoot resume failures?
Confirm a successful prior suspend, match both UE NGAP IDs, decode Cause, inspect optional resume/session context, and check whether AMF returned Resume Response or Resume Failure.
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.
