NR-MIB

NR-Master Information Block

Physical Layer →
Introduced in Rel-15

NR-MIB is the minimal set of essential system information broadcast by a gNB on the NR-PBCH, providing fundamental parameters like system frame number to enable initial cell search, synchronization, and network entry in 5G.

Category
Physical Layer
Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
NR-MIB Description Purpose Related Classification Detected Changes Specifications

Description

The NR-Master Information Block (NR-MIB) is a fundamental broadcast channel message transmitted by the Next Generation NodeB (gNB) on the Physical Broadcast Channel (NR-PBCH). It is a core component of the 5G New Radio (NR) system information (SI) framework, designed to be extremely robust and frequently transmitted to facilitate rapid cell discovery and initial access by User Equipment (UE). The NR-MIB is mapped to specific resource elements within the SS/PBCH block (SSB), which is transmitted with a defined periodicity, typically 20 ms. Its transmission is beamformed, and multiple SSBs can be transmitted in different spatial directions to support beam management and initial beam selection for UEs.

The content of the NR-MIB is deliberately minimal and static to ensure reliable decoding under poor radio conditions. It carries the most critical parameters a UE needs to begin communicating with the cell. These include the System Frame Number (SFN), specifically the 6 most significant bits of the 10-bit SFN, with the remaining bits derived from the PBCH payload scrambling. It also indicates the subcarrier spacing (SCS) common for the SSB and the initial downlink bandwidth part (BPD). Furthermore, it signals the configuration of the Control Resource Set (CORESET) for Type0-PDCCH common search space, which is the gateway for the UE to find and decode the remaining system information blocks (SIBs) like SIB1. The MIB also contains a field indicating whether cell-barred information is present in SIB1.

From an architectural perspective, the NR-MIB is generated by the Radio Resource Control (RRC) layer at the gNB. The RRC layer packages the MIB information into an RRC message, which is then passed down through the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) layers. At the physical layer, the MIB bits are channel coded, scrambled, modulated (using QPSK), and mapped to the resource elements of the PBCH within the SSB. The entire SSB, including the PSS, SSS, and PBCH (carrying the MIB), is a self-contained block that a UE can detect and decode to obtain initial timing, frequency synchronization, and these essential system parameters. The successful decoding of the NR-MIB is a prerequisite for all subsequent steps in the random-access procedure and network attachment.

Purpose & Motivation

The NR-MIB was created to address the need for a highly reliable and efficient mechanism to broadcast the most critical system information in 5G NR networks. Unlike LTE's MIB, which was relatively simple, the NR-MIB had to support a much wider range of deployment scenarios, including millimeter-wave (mmWave) frequencies with beamforming. The primary problem it solves is enabling a UE to quickly and reliably acquire the absolute timing of the cell (via the SFN) and the necessary configuration to locate the control channels that carry the rest of the system information. Without the MIB, a UE would be unable to determine the cell's timing structure or know where to look for the PDCCH that schedules SIB1.

Historically, system information broadcast in previous generations (like the MIB in LTE) provided similar functions but were not designed for the flexible numerology and beam-centric operation of 5G. The NR-MIB's design motivations include minimizing the time-to-sync for UEs, which is crucial for reducing connection latency—a key 5G performance indicator. It also had to be decodable from a single SSB burst to support initial beam sweeping, where a UE might only reliably receive one beam at a time during cell search. By packing essential information into a small, robust payload and transmitting it within the SSB, the NR-MIB ensures that UEs can begin the access procedure with minimal delay, even in challenging radio environments or when using high-frequency bands with directional beams.

Classification

Part ofSIB1
Related approachesCORESET

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-15, normative work from Rel-16.

Rel-16 1 change

In Release 16, the primary new introduction for the NR-MIB function was the specification of its management over the F1 interface for the ng-eNB, as indicated by the Stage-2 CR on system information message over F1. Based on the grounding context, this involved clarifying the functional split where the ng-eNB-DU is responsible for the encoding of the ng-eNB-MIB and for transmitting all system information according to its scheduling, while the ng-eNB-CU is responsible for assembling certain other system information blocks.

  • Stage-2 CR on system information message over F1 (Rel-16) TS 38.470CR0075
Rel-17 2 changes

In Release 17, the NR-MIB function itself did not receive direct updates according to the provided materials. The specified changes introduced new system information capabilities for disaster roaming and positioning system information corrections. The technical grounding context details the existing architecture where the ng-eNB-DU remains responsible for encoding and broadcasting the MIB and other system information, with no new procedures or interfaces indicated for the MIB specifically from these updates.

  • Supporting the disaster roaming information [MINT] TS 38.470CR0097
  • Correction to 38.470 on Positioning System Information TS 38.470CR0107
Rel-19 1 change

In Release 19, the primary update for the NR-MIB function was a correction to the overall system information management function. Based on the specified architecture, this involved clarifying the responsibilities between network nodes, where the ng-eNB-DU remains responsible for encoding and transmitting the ng-eNB-MIB and other core system information blocks. The release did not introduce new procedures or interfaces for the MIB itself but focused on refining the existing management framework.

  • Correction of system information management function TS 38.470CR0166

Explore further

Broader topics and technologies where NR-MIB plays a role.

Defining Specifications

3GPP specifications that define or reference NR-MIB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 37.470 vj00 W1 Interface Introduction for ng-eNB Rel-19
TS 38.470 vj10 F1 Interface Introduction Rel-19