| Protocol | rrc | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 38.331 | Spec Section | 5.3.8, 6.2.2 |
| Direction | gNB -> UE | Message Type | Connection Release |
| Full message name | 5G NR - RRC Release |
|---|---|
| Protocol | RRC |
| Technology | 5G |
| Direction | gNB -> UE |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / DL-DCCH |
| Typical trigger | Used when the network decides to release the active RRC connection. |
| Main purpose | Ends the current connected RRC context while optionally providing information relevant to idle, inactive, redirection, or release handling. |
| Main specification | 3GPP TS 38.331, 5.3.8, 6.2.2 |
| Release added | Release 15 |
| Procedures where used | RRC Release, Connected-to-Idle Transition, Connected-to-Inactive Transition |
| Related timers | T320 when redirection or priority context applies |
RRC Release is the downlink NR RRC message used by the network to release the connected-mode context and move the UE out of active connected signaling.
Ends the current connected RRC context while optionally providing information relevant to idle, inactive, redirection, or release handling.
RRC Release tells the UE to leave the current connected RRC state.
Call flow position: Network command that ends the connected RRC context.
Typical state: UE is in RRC_CONNECTED.
Preconditions:
Next likely message: Idle or inactive behavior, or later access signaling
Previous message(s): RRC Reconfiguration, Paging response path
Next message(s): RRC_IDLE, RRC_INACTIVE, Redirection or later access
Security context: Sent as protected connected-mode signaling before the UE leaves the connected state.
RRCRelease ::= SEQUENCE {
criticalExtensions CHOICE {
rrcRelease RRCRelease-IEs,
...
}
}
The main engineering checks are whether the release is a plain release, an inactive-style release, or a redirection release.
DL-DCCH-Message
message: rrcRelease
suspendConfig: present
| IE | Required | Description |
|---|---|---|
redirectedCarrierInfo | Optional | Provides redirection information if the UE should move to another carrier or system. |
suspendConfig | Optional | Provides suspend or inactive-related information when that path is used. |
redirectedCarrierInfoProvides redirection information if the UE should move to another carrier or system.
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.
suspendConfigProvides suspend or inactive-related information when that path is used.
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 release context may indicate a different next-state path than expected.
What to inspect: Check suspendConfig, redirection information, and the next UE action.
Next step: Follow whether the UE resumed, reselected, or started a fresh setup.
Not always. It can also lead to inactive behavior or redirection depending on the included context.
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.