RRC 5G UE -> gNB 3GPP TS 38.331

5G NR - RRC Resume Request1

RRC Resume Request1 is an alternate NR RRC resume request message variant used in the resume procedure.

Message Fact Sheet

Protocol	rrc	Network	5g
Spec	3GPP TS 38.331	Spec Section	5.3.13, 6.2.2
Direction	UE -> gNB	Message Type	Connection Resume

Full message name	5G NR - RRC Resume Request1
Protocol	RRC
Technology	5G
Direction	UE -> gNB
Interface	Uu
Signaling bearer / channel	SRB0 / UL-CCCH
Typical trigger	Used when the UE follows the RRCResumeRequest1 variant defined for the resume path.
Main purpose	Provides the UE with an alternate resume-request encoding path defined by the specification.
Main specification	3GPP TS 38.331, 5.3.13, 6.2.2
Release added	Release 15
Procedures where used	RRC Resume, Inactive-to-Connected Transition
Related timers	T380

What is RRC Resume Request1 in simple terms?

RRC Resume Request1 is an alternate NR RRC resume request message variant used in the resume procedure.

Provides the UE with an alternate resume-request encoding path defined by the specification.

Why this message matters

RRC Resume Request1 is an alternate resume-request message used by the UE in the resume procedure.

Where this message appears in the call flow

RRC Resume

Call flow position: Alternate first UE message in the resume path.

Typical state: UE is in inactive or suspended state and attempts resume.

Preconditions:

A valid inactive or suspended context exists.

Next likely message: RRC Resume or RRC Reject

Call flow position

Previous message(s): Paging, Resume trigger from upper layers

Next message(s): RRC Resume, RRC Reject

Message direction and transport

Sender and receiver: UE -> gNB

Interface: Uu

Domain: Access-side radio control

Signaling bearer: SRB0

Logical channel: UL-CCCH

Transport / encapsulation: Early resume signaling before restored dedicated context exists

Security context: Sent before full connected context is restored.

Message Structure Overview

The practical role is the same as Resume Request, but the exact encoded variant differs.

ASN.1 for 5G NR - RRC Resume Request1

RRCResumeRequest1 ::= SEQUENCE {
  criticalExtensions CHOICE {
    rrcResumeRequest1 RRCResumeRequest1-IEs,
    ...
  }
}

How to read this ASN.1

In practice, engineers treat this as an alternate resume request variant and correlate it with the same resume procedure outcome.

5G NR - RRC Resume Request1 - Example Dump

UL-CCCH-Message
  message: rrcResumeRequest1

How to read this dump

The main check is that the network recognizes and answers the alternate resume request correctly.

Important Information Elements

IE	Required	Description
`resumeIdentity / variant fields`	Yes	Carries the alternative resume-request content defined by the spec.

Detailed field explanation

`resumeIdentity / variant fields`

Carries the alternative resume-request content defined by the spec.

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

Check whether this variant appears instead of the base resume request.
Correlate it with the same resume acceptance or rejection path.

Common Issues and Troubleshooting

Resume works inconsistently across UE types.

Likely cause: Some traces may use the alternate Resume Request1 path.

What to inspect: Check whether the UE sent RRC Resume Request1 instead of the base resume request.

Next step: Compare the network response to both variants.

FAQ

How is RRC Resume Request1 different from RRC Resume Request?

It serves the same procedural role but represents an alternate resume-request encoding path defined by the spec.

Related message pages

Related Procedures

5G RRC Resume

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.