| Protocol | rrc | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 38.331 | Spec Section | 5.3.13, 6.2.2 |
| Direction | gNB -> UE | Message Type | Connection Resume |
| Full message name | 5G NR - RRC Resume |
|---|---|
| Protocol | RRC |
| Technology | 5G |
| Direction | gNB -> UE |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / DL-DCCH |
| Typical trigger | Used when the network accepts an RRC Resume Request and restores the UE's context. |
| Main purpose | Restores the UE's connected-mode context from an inactive or suspended state so protected signaling and data transfer 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 |
| Related timers | T380 |
RRC Resume is the downlink NR RRC message used by the network to resume a suspended or inactive context after a valid resume request.
Restores the UE's connected-mode context from an inactive or suspended state so protected signaling and data transfer can continue.
RRC Resume is the network's message for restoring an inactive or suspended RRC context.
Call flow position: Sent after the network accepts the resume attempt.
Typical state: UE is recovering from RRC_INACTIVE or suspended context.
Preconditions:
Next likely message: RRC Resume Complete
Previous message(s): RRC Resume Request, RRC Resume Request1
Next message(s): RRC Resume Complete
Security context: Sent when resuming an existing suspended or inactive context.
RRCResume ::= SEQUENCE {
criticalExtensions CHOICE {
rrcResume RRCResume-IEs,
...
}
}
The important practical question is what context was restored and whether the UE accepted it.
DL-DCCH-Message
message: rrcResume
radioBearerConfig: present
| IE | Required | Description |
|---|---|---|
radioBearerConfig | Optional | Restored or updated bearer configuration used during resume. |
masterCellGroup | Optional | Cell-group information the UE applies when resuming the connected context. |
radioBearerConfigRestored or updated bearer configuration used during resume.
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.
masterCellGroupCell-group information the UE applies when resuming the connected 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.
Likely cause: The restored context may not match the UE's inactive state.
What to inspect: Check the resume payload and the later complete or failure path.
Next step: Follow the exact state transition after the resume command.
The UE normally answers with RRC Resume Complete if the resume succeeds.
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.