For trace work, the key question is not just that the ASN.1 decodes, but whether the radioBearerConfig and masterCellGroup contents are internally consistent and appropriate for the UE and cell.
SRB1 creation is the first thing to confirm in a healthy RRC Setup.
masterCellGroup is where many real-world parsing or configuration failures show up.
The absence of DRBs in this message is normal.
Important Information Elements
IE
Required
Description
rrc-TransactionIdentifier
Yes
Transaction identifier used with the message type to correlate the RRC procedure.
criticalExtensions
Yes
Carries the versioned RRCSetup payload and enables forward compatibility.
radioBearerConfig
Yes
Bearer configuration delivered in RRC Setup. In this message, only SRB1 is configured.
masterCellGroup
Yes
CellGroupConfig container carrying the initial serving-cell, MAC, and physical cell-group configuration needed to bring up SRB1 and connected-mode operation.
lateNonCriticalExtension
Optional
Extension container used for backward and forward compatibility.
nonCriticalExtension
Optional
Release-specific extension branch for later feature additions.
Detailed field explanation
rrc-TransactionIdentifier
Transaction identifier used with the message type to correlate the RRC procedure.
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.
criticalExtensions
Carries the versioned RRCSetup payload and enables forward compatibility.
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.
radioBearerConfig
Bearer configuration delivered in RRC Setup. In this message, only SRB1 is configured.
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.
masterCellGroup
CellGroupConfig container carrying the initial serving-cell, MAC, and physical cell-group configuration needed to bring up SRB1 and connected-mode operation.
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.
lateNonCriticalExtension
Extension container used for backward and forward compatibility.
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.
nonCriticalExtension
Release-specific extension branch for later feature additions.
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.
What to check in logs and traces
Confirm the message follows RRCSetupRequest and not some unrelated fallback artifact.
Check that SRB1 is present in radioBearerConfig.
Inspect masterCellGroup for plausible and complete initial MAC / PHY / serving-cell configuration.
Verify the transaction identifier if correlating repeated setup attempts.
Confirm the next UE action is RRCSetupComplete and not an early failure.
Common Issues and Troubleshooting
RRC Setup arrives but the UE never sends RRCSetupComplete.
Likely cause: The UE may fail to parse or apply radioBearerConfig or masterCellGroup.
What to inspect: Check masterCellGroup completeness, SRB1 configuration, and any UE capability mismatch.
Next step: Compare the setup content with a successful UE trace and verify configuration support.
The network falls back to repeated setup attempts.
Likely cause: Earlier resume or re-establishment context recovery may have failed, forcing fresh setup repeatedly.
What to inspect: Look at the messages before RRCSetup and identify whether the path is a fallback case.
Next step: Troubleshoot the failed resume or re-establishment path, not only the fresh setup message.
Later SecurityModeCommand or RRC reconfiguration fails.
Likely cause: The issue may originate in early bearer or serving-cell setup delivered here.
What to inspect: Correlate RRCSetup with the first SRB1/DCCH messages and verify transport and state transition behavior.
Next step: Walk the procedure forward from setup to setup complete and security activation.
LTE / 5G / Variant Comparison
Compared with later RRCReconfiguration
RRC Setup handles the initial connected-mode control-plane bring-up, while RRCReconfiguration is the richer connected-state workhorse used later for DRBs, measurements, mobility, and feature changes.
FAQ
What is RRC Setup in 5G NR?
RRC Setup is the downlink RRC message that the gNB sends to establish SRB1 during RRC connection establishment.
What comes before RRC Setup?
The UE first sends RRCSetupRequest after initial access and random access preparation.
What comes after RRC Setup?
The UE applies the received configuration, enters connected mode, and responds with RRCSetupComplete. The network then typically proceeds with SecurityModeCommand.
Does RRC Setup configure DRBs?
No. In NR, RRC Setup is limited to the initial connected-mode configuration and only SRB1 can be configured here.
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.