SystemInformationBlockType1 (SIB1) is the key NR broadcast system information block that tells the UE how to access the cell, select PLMN context, and interpret important cell-level access restrictions and configuration.
Message Fact Sheet
Protocol
rrc
Network
5g
Spec
3GPP TS 38.331
Spec Section
5.2.1, 5.2.2, 5.4.3, 6.3.1
Direction
gNB -> UE
Message Type
Broadcast System Information
Full message name
5G NR - System Information Block 1 (SIB1)
Protocol
RRC
Technology
5G
Direction
gNB -> UE
Interface
Uu
Signaling bearer / channel
Broadcast transport / BCCH-DL-SCH
Typical trigger
Periodically broadcast by the cell so UEs can acquire essential system information before access, reselection, paging monitoring, and idle/inactive mobility decisions.
Main purpose
Provides the essential broadcast information the UE needs after MIB/PBCH decoding to camp on the cell correctly, decide whether access is allowed, and proceed toward random access and RRC connection establishment.
What is System Information Block 1 (SIB1) in simple terms?
SystemInformationBlockType1 (SIB1) is the key NR broadcast system information block that tells the UE how to access the cell, select PLMN context, and interpret important cell-level access restrictions and configuration.
Provides the essential broadcast information the UE needs after MIB/PBCH decoding to camp on the cell correctly, decide whether access is allowed, and proceed toward random access and RRC connection establishment.
Why this message matters
SIB1 is the most important broadcast system information block the UE reads before trying to access the cell. It tells the UE whether and how it should use the cell.
Where this message appears in the call flow
Initial Access
Call flow position: Read after successful synchronization and MIB acquisition, before the UE starts random access and sends RRCSetupRequest.
Typical state: UE is in idle-like access preparation and has not yet established an RRC connection.
Preconditions:
The UE has detected the cell and decoded MIB/PBCH.
The UE needs essential cell information before attempting access.
Next likely message: RRCSetupRequest
Cell Selection and Camping
Call flow position: Used while the UE evaluates whether the cell is suitable and how it should camp or select PLMN context.
Typical state: UE is performing cell selection, reselection, or camping checks.
Preconditions:
The UE has synchronized to the cell.
Next likely message: Continued camping, reselection evaluation, or access attempt
Paging and Idle / Inactive Mobility
Call flow position: Referenced after camping to understand paging-related and cell-level idle/inactive behavior.
Typical state: UE is already camped and monitoring cell broadcast information.
Preconditions:
The UE is on the cell and uses current broadcast configuration.
Next likely message: Paging, reselection action, or a new access attempt depending on UE state
Domain: Access-side radio control and broadcast system information
Signaling bearer: Broadcast transport
Logical channel: BCCH-DL-SCH
Transport / encapsulation: RRC BCCH-DL-SCH message carried over DL-SCH/PDSCH after the UE has acquired MIB and synchronization
Security context: Broadcast information. It is not UE-specific and is not carried under AS security.
Message Structure Overview
SIB1 is not a UE-specific dedicated message. It is the essential broadcast block that bridges early synchronization into real access behavior.
In practice, engineers focus on access barring, PLMN and tracking area context, servingCellConfigCommon, and any selection restrictions that can explain why the UE did or did not attempt access.
The message also tells the UE how to obtain additional system information, so SIB1 often explains why later SI-dependent behavior succeeds or fails.
ASN.1 for 5G NR - System Information Block 1 (SIB1)
For trace analysis, the important point is that SIB1 arrives as the systemInformationBlockType1 branch of BCCH-DL-SCH. Engineers usually care less about the wrapper and more about whether the access, PLMN, and serving-cell fields match the deployment and UE behavior.
5G NR - System Information Block 1 (SIB1) - Example Dump
The first engineering check is usually PLMN, TAC, and reservation/access context inside cellAccessRelatedInfo.
servingCellConfigCommon is the common baseline the UE uses before any dedicated reconfiguration arrives.
If SIB1 content does not match field deployment expectations, access, camping, paging, and even later setup behavior can all look wrong.
Important Information Elements
IE
Required
Description
cellSelectionInfo
Optional
Carries cell selection-related parameters such as q-RxLevMin and related restrictions that directly affect whether the UE treats the cell as suitable.
cellAccessRelatedInfo
Yes
Contains PLMN identity information, tracking area information, cell identity, and reservation/access context that engineers often inspect first in field traces.
connEstFailureControl
Optional
Provides configuration related to connection establishment failure control behavior, useful when repeated access attempts behave unexpectedly.
uac-BarringInfo
Optional
Unified access control and barring information that influences whether specific access categories or services are allowed.
servingCellConfigCommon
Yes
Broadcast common serving-cell configuration used as the baseline for access and early connected-mode operation.
si-SchedulingInfo
Optional
Tells the UE how additional system information is scheduled beyond SIB1.
tdd-UL-DL-ConfigurationCommon
Optional
Broadcast TDD pattern information when applicable, affecting uplink/downlink timing expectations.
ssb-PositionsInBurst
Optional
Provides SSB-related broadcast context used together with other synchronization and coverage interpretation.
Detailed field explanation
cellSelectionInfo
Carries cell selection-related parameters such as q-RxLevMin and related restrictions that directly affect whether the UE treats the cell as suitable.
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.
cellAccessRelatedInfo
Contains PLMN identity information, tracking area information, cell identity, and reservation/access context that engineers often inspect first in field traces.
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.
connEstFailureControl
Provides configuration related to connection establishment failure control behavior, useful when repeated access attempts behave unexpectedly.
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.
uac-BarringInfo
Unified access control and barring information that influences whether specific access categories or services are allowed.
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.
servingCellConfigCommon
Broadcast common serving-cell configuration used as the baseline for access and early 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.
si-SchedulingInfo
Tells the UE how additional system information is scheduled beyond SIB1.
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.
tdd-UL-DL-ConfigurationCommon
Broadcast TDD pattern information when applicable, affecting uplink/downlink timing expectations.
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.
ssb-PositionsInBurst
Provides SSB-related broadcast context used together with other synchronization and coverage interpretation.
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 UE decoded MIB/PBCH before attempting to process SIB1.
Verify the BCCH-DL-SCH decode is fresh for the serving cell and not stale or from a different frequency / PCI context.
Check PLMN, TAC, and cell identity values against the intended deployment.
Inspect access barring or reservation-related fields when the UE does not attempt access or receives early rejection.
Correlate servingCellConfigCommon with numerology, SSB configuration, and the expected random-access behavior.
If the UE sends RRCSetupRequest, verify the attempt is consistent with the broadcast access conditions carried in SIB1.
Common Issues and Troubleshooting
The UE does not start access even though the cell is detectable.
Likely cause: SIB1 may indicate barring, reservation, unsuitable cell conditions, or PLMN context that does not allow the intended access attempt.
What to inspect: Check cellSelectionInfo, cellAccessRelatedInfo, and any uac-BarringInfo or reservation-related fields.
Next step: Compare the broadcast values with a known-good cell and confirm the UE is using the expected PLMN and access category.
The UE sends RRCSetupRequest but later access behavior looks inconsistent.
Likely cause: SIB1 may have been decoded incorrectly, stale, or mismatched with the actual serving-cell configuration.
What to inspect: Verify servingCellConfigCommon, SSB-related context, and the exact cell/frequency on which SIB1 was read.
Next step: Correlate PBCH, SIB1, PRACH, and RRCSetupRequest in one continuous trace.
Repeated RRCReject or admission issues occur for specific service categories.
Likely cause: Broadcast barring or access-control information in SIB1 may be driving the observed behavior.
What to inspect: Check uac-BarringInfo and any operator/cell reservation indicators.
Next step: Validate whether the rejected access category is expected to be allowed on this cell.
PLMN or tracking-area interpretation is wrong in logs.
Likely cause: The UE may be selecting a different broadcast identity context than expected.
What to inspect: Check plmn-IdentityList, TAC, and later selectedPLMN-related behavior in RRCSetupComplete or NAS.
Next step: Compare SIB1 broadcast identities with later access and registration context.
LTE / 5G / Variant Comparison
SIB1 versus MIB
MIB gives the UE the first minimal broadcast anchor, while SIB1 provides the essential operational access and cell-selection information needed to proceed with real access behavior.
SIB1 versus later dedicated RRC
SIB1 is cell-broadcast common configuration. Later dedicated messages such as RRC Setup or RRC Reconfiguration provide UE-specific connected-mode configuration.
FAQ
What is SIB1 in 5G NR?
SIB1 is SystemInformationBlockType1, the essential broadcast system information block the UE reads before access and camping decisions.
Who sends SystemInformationBlockType1?
The gNB broadcasts SIB1 to all UEs in the cell.
On which channel is SIB1 sent?
SIB1 is carried as a BCCH-DL-SCH RRC message.
What comes before SIB1?
The UE first synchronizes to the cell and decodes MIB/PBCH.
What usually comes after SIB1?
If access is allowed and needed, the UE proceeds toward random access and then RRCSetupRequest.
Why is SIB1 important for troubleshooting?
Because it contains access, PLMN, and common serving-cell information that can explain why the UE camps, rejects a cell, or behaves unexpectedly during early access.
Does SIB1 contain UE-specific information?
No. SIB1 is broadcast cell-common information, not a dedicated UE-specific RRC message.
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.