5G NR - Master Information Block (MIB) Explained

The Master Information Block (MIB) is the first essential broadcast RRC information a UE decodes in 5G NR after synchronization. It is carried through PBCH and gives the UE the minimum cell context needed to continue toward SIB1 and later initial access.

For beginners, the simple meaning is: MIB is the first small package of cell information that helps the UE move beyond basic synchronization.
For experienced engineers, MIB is the first operational checkpoint in the broadcast-information chain, and it often explains why a UE sees a cell but fails to progress toward SIB1, PRACH, or setup.

What is MIB in simple terms?

MIB is a compact broadcast RRC message in the BCCH-BCH family. It does not carry the full cell configuration. Instead, it gives the UE just enough information to continue the next stage of system-information acquisition.

In practical terms, MIB helps answer:

  • is the cell barred?
  • what basic common timing and configuration context applies?
  • how does the UE move from PBCH into SIB1 acquisition?

Why this message matters

MIB matters because it sits at the first real handoff between:

  • cell detection and synchronization
  • usable broadcast-system-information acquisition

If the UE fails here, the problem may look like a PRACH or RRC setup issue, but the real problem is earlier:

  • PBCH decode quality
  • MIB interpretation
  • inability to continue toward SIB1
  • cell-barred context

Where MIB appears in the call flow

The early access path is typically:

  1. UE detects SSB.
  2. UE synchronizes to the cell.
  3. UE decodes PBCH and obtains MIB.
  4. UE uses MIB to locate and interpret SIB1 acquisition.
  5. UE continues toward initial access and RRCSetupRequest.

Mini sequence:

UE                          gNB
|                            |
|<-- SSB --------------------|
|<-- PBCH / MIB -------------|
|<-- SIB1 -------------------|
|--- PRACH / access -------->|
|--- RRCSetupRequest ------->|

So MIB is not a dedicated per-UE message. It is the first broadcast control anchor that makes the next access steps possible.

Message direction and transport

For engineering traces, the key transport facts are:

  • Direction: gNB to UE
  • Message family: RRC broadcast system information
  • Logical message path: BCCH-BCH
  • Physical transport context: carried on PBCH inside the SSB
  • Security context: broadcast and not UE-specific

This means MIB should be analyzed together with SSB and PBCH, not as a dedicated SRB-based control message.

Structure overview

At a practical level, engineers usually inspect:

  • systemFrameNumber
  • subCarrierSpacingCommon
  • ssb-SubcarrierOffset
  • dmrs-TypeA-Position
  • pdcch-ConfigSIB1
  • cellBarred
  • intraFreqReselection

The most operationally important field is often pdcch-ConfigSIB1, because it controls how the UE moves from MIB toward SIB1 scheduling and acquisition.

Important information elements

1. systemFrameNumber

This gives the UE the initial broadcast frame-number context.

Why it matters:
It helps anchor the timing context used in the earliest access stage.

2. subCarrierSpacingCommon

This indicates the common broadcast subcarrier-spacing context used by the UE for early interpretation.

Why it matters:
It ties the MIB into the cell’s early timing and access behavior.

3. ssb-SubcarrierOffset

This gives offset information associated with SSB-based early access interpretation.

Why it matters:
It helps the UE relate the SSB/PBCH context to the broader carrier configuration.

4. dmrs-TypeA-Position

This carries a common DMRS-related broadcast setting used in the early configuration context.

Why it matters:
It is part of the common serving-cell baseline the UE uses before dedicated configuration arrives later.

5. pdcch-ConfigSIB1

This is the field engineers often care about most.

Why it matters:
It tells the UE how to find the scheduling information needed to obtain SIB1. If this path breaks, the UE may never move forward even when the cell is clearly visible.

6. cellBarred

This indicates whether the cell is barred for access.

Why it matters:
It directly explains why a UE may not continue toward normal access even if radio detection is healthy.

Example decoded dump

BCCH-BCH-Message
  message: mib
    systemFrameNumber: 42
    subCarrierSpacingCommon: scs30or120
    ssb-SubcarrierOffset: 8
    dmrs-TypeA-Position: pos2
    pdcch-ConfigSIB1: 96
    cellBarred: notBarred
    intraFreqReselection: allowed

How to read this dump

  • systemFrameNumber gives the UE its initial timing anchor.
  • subCarrierSpacingCommon and ssb-SubcarrierOffset help define the early common interpretation context.
  • pdcch-ConfigSIB1 is the handoff point from MIB into SIB1 acquisition.
  • cellBarred: notBarred means the cell is not barred in this example.

What to check in logs and traces

  • Did the UE successfully detect SSB and decode PBCH first?
  • Are the decoded MIB values stable across repeated observations?
  • Does pdcch-ConfigSIB1 lead to successful SIB1 acquisition?
  • Is cellBarred consistent with observed camping and access behavior?
  • Does the later SIB1 decode line up with the same serving-cell context?

Common failures and troubleshooting

The UE sees the cell but never gets to SIB1

This is often a PBCH / MIB path issue, not yet a PRACH problem.

Check:

  • PBCH quality
  • MIB decode consistency
  • pdcch-ConfigSIB1

Access never starts even though synchronization works

The problem may be rooted in broadcast-system-information processing rather than random access itself.

Check:

  • whether MIB was decoded cleanly
  • whether the cell is barred
  • whether the UE progressed from MIB to SIB1

Engineers blame PRACH or RRC setup too early

If the UE never had a clean MIB and SIB1 chain, later access stages were never on solid ground.

Check:

  • SSB -> PBCH / MIB -> SIB1 -> PRACH

as one continuous workflow.

Beginner takeaway

MIB is the first small but essential 5G broadcast message that lets the UE move from synchronization into real cell information and access preparation.

Advanced engineer notes

  • MIB problems often hide underneath symptoms that later appear as access or RRC failures.
  • A “valid MIB decode” is only useful if it also leads to a correct SIB1 acquisition path.
  • Always correlate SSB, PBCH, MIB, and SIB1 together.

Decoder CTA

Use the 3GPP Decoder to inspect broadcast RRC payloads, then compare MIB, SIB1, and the later access path as one continuous early-cell-access workflow.

FAQ

What is MIB in 5G NR?

MIB is the Master Information Block, the first essential broadcast RRC information the UE decodes from PBCH after synchronization.

Who sends the 5G NR MIB?

The gNB broadcasts MIB to all UEs through PBCH.

On which channel is MIB sent?

MIB is carried in the BCCH-BCH message and transmitted on PBCH.

What comes after MIB?

The UE uses MIB to continue toward SIB1 acquisition and then initial access behavior.

Why is pdcch-ConfigSIB1 important?

Because it tells the UE how to find the scheduling information needed to decode SIB1.

Can MIB explain why access never starts?

Yes. If MIB or PBCH processing fails, or if the cell is barred, the UE may never proceed toward SIB1, PRACH, or RRC setup.

Summary

The NR Master Information Block (MIB) is the first essential broadcast RRC information a UE decodes from PBCH after synchronization. It gives the UE the minimal system information needed to continue toward SIB1 acquisition and initial access.