| 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 Complete |
|---|---|
| Protocol | RRC |
| Technology | 5G |
| Direction | UE -> gNB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / UL-DCCH |
| Typical trigger | Used when the UE successfully applies RRC Resume. |
| Main purpose | Closes the resume procedure by telling the network that the UE applied the restored context and normal connected-mode behavior can continue. |
| 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 |
RRC Resume Complete is the UE-to-network NR RRC message confirming that the suspended or inactive context was resumed successfully.
Closes the resume procedure by telling the network that the UE applied the restored context and normal connected-mode behavior can continue.
RRC Resume Complete tells the network that the UE successfully resumed the prior context.
Call flow position: Final UE confirmation at the end of the resume path.
Typical state: UE has resumed the connected context.
Preconditions:
Next likely message: Normal connected-mode operation
Previous message(s): RRC Resume
Next message(s): Normal connected signaling
Security context: Sent after the UE accepts the resumed context.
RRCResumeComplete ::= SEQUENCE {
criticalExtensions CHOICE {
rrcResumeComplete RRCResumeComplete-IEs,
...
}
}
The main value is confirmation that the resume path really completed.
UL-DCCH-Message
message: rrcResumeComplete
| IE | Required | Description |
|---|---|---|
lateNonCriticalExtension | Optional | Extension field for later release handling. |
lateNonCriticalExtensionExtension field for later release 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.
Likely cause: The UE may not have accepted or applied the resumed context.
What to inspect: Check lower layers, state alignment, and any later setup fallback.
Next step: Compare missing completion with later fresh setup or release.
It means the UE successfully completed the resume procedure.
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.