5G NR System Information: MIB, SIB1, and the SIB Catalog

Overview

NR system information is broadcast on the radio interface so that any UE in the cell can read the common configuration without dedicated signaling. The practical sequence is straightforward: the UE decodes MIB, then SIB1, and then any additional SIBs the cell schedules.

In traces, the important question is not just whether the decode succeeded, but whether the broadcast content matches the deployment, the PLMN, and the feature set the UE is trying to use.

Reading order

MIB -> SIB1 -> SystemInformation -> feature SIBs

That is the sequence most engineers use in the field. MIB gives the first anchor, SIB1 gives access and cell context, and SystemInformation carries the additional blocks that explain mobility, paging, feature support, or deployment-specific behavior.

MIB

Master Information Block (MIB) is the first essential broadcast anchor after PBCH decode. It gives the UE the minimum context needed to continue toward SIB1.

• It is broadcast on the PBCH path as part of the earliest access sequence.
• It helps the UE locate SIB1 and understand the most basic common cell information.
• It is the first place to check when the UE sees the cell but does not move forward.

Key fields engineers usually inspect include the common timing context, common subcarrier spacing, the SIB1 scheduling pointer, and access-related flags such as cell barred or reselection permission.

Open the detailed reference page: 5G NR - Master Information Block (MIB).

SIB1

System Information Block 1 (SIB1) is the essential broadcast block that tells the UE how to use the cell. If MIB is the first anchor, SIB1 is the first operational decision point.

• It carries access, PLMN, and cell-identity context.
• It carries access barring and reservation behavior when configured.
• It carries common serving-cell configuration and the scheduling hint for later SI.

For field work, SIB1 is often the fastest way to answer whether the UE should camp, attempt access, wait for paging, or move on to other broadcast blocks.

Open the detailed reference page: 5G NR - System Information Block 1 (SIB1).

SystemInformation

SystemInformation is the broadcast container that carries one or more SIBs with the same periodicity. It is not a single feature block. It is the envelope that delivers the additional SI the cell wants the UE to read after MIB and SIB1.

• The container matters because of which SIBs it carries.
• All included SIBs in one SystemInformation message share the same periodicity.
• If the expected SIB is missing from the container, the UE may never get the context it needs.

Open the detailed reference page: 5G NR - System Information.

SIB catalog

Not every cell broadcasts every SIB. Which ones appear depends on the release, the deployment, and the features the operator enables. The table below gives you a practical way to map the block to the thing it is usually used for.

For positioning-related context, check SIB23 and UE Positioning Assistance Info. That is where most of the practical positioning reference in this section lives.

Trace workflow

When broadcast information looks wrong, the fastest debug path is simple: start at the last good decode and move forward in the same order the UE does.

1. Check MIB decode and confirm the UE can locate SIB1.
2. Check SIB1 for PLMN, barring, serving-cell, and SI scheduling context.
3. Check the SystemInformation container for the expected follow-up SIB.
4. Move into the feature-specific SIB only after the broadcast path is correct.

If the UE still fails after that, continue into RRC connection setup or RRC SystemInfo Request, depending on whether the UE is trying to access the cell or asking for missing SI.

Paging and idle use

System information is not just for initial access. It also drives idle and inactive behavior. SIB1 contains the basic paging and scheduling context, and the later SIBs shape how the UE behaves in idle mobility, feature discovery, and release-specific operation.

• Paging starts to matter once the UE is idle or inactive.
• Idle mobility depends heavily on the SIB2 to SIB5 family.
• Feature-specific systems such as slicing, NTN, MBS, and sidelink rely on later SIBs.

If you are correlating this with a live flow, keep 5G Paging Procedure and 5G Idle Mode Mobility open next to this page.

How it connects

MIB -> SIB1 -> SystemInformation -> trace context -> setup / paging / mobility

This is the quickest way to think about the broadcast side of RRC. If the broadcast path is wrong, the UE may never get cleanly to setup, resume, or mobility. If the broadcast path is right, you can usually move on to the dedicated procedure with much more confidence.

FAQ

Reusable excerpt

5G NR system information starts with MIB and SIB1, then expands through the SystemInformation container and feature-specific SIBs. Use this page to map broadcast context to the right message page, trace step, or troubleshooting path.