| Protocol | rrc | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 38.331 | Spec Section | 5.3.5, 6.2.2 |
| Direction | UE -> gNB | Message Type | Connection Control |
| Full message name | 5G NR - RRC Reconfiguration Complete |
|---|---|
| Protocol | RRC |
| Technology | 5G |
| Direction | UE -> gNB |
| Interface | Uu |
| Signaling bearer / channel | SRB1 / UL-DCCH |
| Typical trigger | Used when the UE successfully applies an RRC Reconfiguration. |
| Main purpose | Closes the reconfiguration loop by telling the network that the UE applied the new configuration. |
| Main specification | 3GPP TS 38.331, 5.3.5, 6.2.2 |
| Release added | Release 15 |
| Procedures where used | RRC Reconfiguration, Measurement Configuration, Mobility Preparation |
| Related timers | None highlighted |
RRC Reconfiguration Complete is the UE-to-network NR RRC message confirming that the UE successfully applied the received RRC Reconfiguration.
Closes the reconfiguration loop by telling the network that the UE applied the new configuration.
RRC Reconfiguration Complete tells the network that the UE applied the new RRC settings.
Call flow position: UE confirmation at the end of the reconfiguration path.
Typical state: UE is in connected mode and has applied the new settings.
Preconditions:
Next likely message: Normal signaling that uses the new configuration
Previous message(s): RRC Reconfiguration
Next message(s): Normal connected signaling, Measurement Report, Handover continuation
Security context: Sent as protected connected-mode signaling after the UE processes the reconfiguration.
RRCReconfigurationComplete ::= SEQUENCE {
criticalExtensions CHOICE {
rrcReconfigurationComplete RRCReconfigurationComplete-IEs,
...
}
}
The main question is whether the UE acknowledged the reconfiguration at all, and if so, what happened after that point.
UL-DCCH-Message
message: rrcReconfigurationComplete
| IE | Required | Description |
|---|---|---|
lateNonCriticalExtension | Optional | Extension field for later releases. |
lateNonCriticalExtensionExtension field for later releases.
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 have failed to apply the new configuration.
What to inspect: Check lower-layer delivery, configuration validity, and whether another failure message follows.
Next step: Correlate the missing complete with radio or security issues.
The connection continues using the new configuration.
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.