SMTC in 5G NR — Detailed Guide (SMTC1, SMTC2, SMTC-LP, SMTC3, SMTC4)
SMTC in 5G NR — Comprehensive Guide
What is SMTC?
SMTC stands for SS/PBCH Block Measurement Timing Configuration. It is a time-domain window that tells the UE when to expect SS/PBCH blocks (SSBs) from neighbour cells so it can perform measurements (SS-RSRP, SS-RSRQ, SS-SINR) for cell identification, mobility decisions, and RRM.
Why is SMTC needed?
In NR, SSBs are not transmitted continuously — they are burst-transmitted within an SS burst set periodicity (5, 10, 20, 40, 80, or 160 ms). A UE measuring neighbour cells needs to know exactly when to look for those SSBs so it doesn't waste power or miss them. The SMTC window solves this by defining:
| Parameter | Description | Values |
|---|---|---|
| Periodicity | How often the measurement window repeats | 5, 10, 20, 40, 80, 160 ms |
| Offset | Slot offset from SFN=0 where the window starts | 0 to (periodicity - 1) slots |
| Duration | How long the measurement window stays open | 1, 2, 3, 4, or 5 ms |
The effective measurement window = intersection of the SMTC window and the measurement gap occasion (for inter-frequency measurements).
Spec References: TS 38.331 clause 5.5.2.10, TS 38.133 clause 9, TS 38.215 clause 4
SMTC Types — Full Breakdown
1. SMTC1 (smtc1 / SSB-MTC)
Introduced: Rel-15 (baseline NR)
Configured in: MeasObjectNR (TS 38.331 clause 5.5.2.2)
Purpose: Primary SMTC for inter-frequency and intra-frequency SSB-based neighbour cell measurements.
- This is the original and most fundamental SMTC.
- Configured per
MeasObjectNR(i.e., per target carrier frequency). - The UE uses this window to search for and measure SSBs from neighbour cells on that carrier.
- For intra-frequency measurements, SMTC1 defines when the UE measures serving-frequency neighbour cells.
- For inter-frequency measurements, the UE aligns measurement gap occasions with the SMTC1 window.
Key parameters:
SSB-MTC ::= SEQUENCE {
periodicity ENUMERATED {sf5, sf10, sf20, sf40, sf80, sf160},
offset INTEGER (0..maxSFN-1),
duration ENUMERATED {sf1, sf2, sf3, sf4, sf5}
}
When the UE measures: Only during the SMTC1 window. Outside it, the UE assumes no SSBs are present on the target frequency and does not attempt measurements.
2. SMTC2 (smtc2 / SSB-MTC2)
Introduced: Rel-15
Configured in: MeasObjectNR (TS 38.331 clause 5.5.2.2)
Purpose: Secondary SMTC for measuring SSBs with different periodicities on the same carrier, or for specific PCIs.
SMTC2 provides a second measurement window on the same carrier frequency, used when:
- Some cells on the target frequency transmit SSBs with a different periodicity than the cells covered by SMTC1.
- The network wants the UE to measure a specific set of PCIs with a different timing window.
- Neighbour cells deployed by a different operator or with different SSB configurations share the same carrier.
Key differences from SMTC1:
| Aspect | SMTC1 | SMTC2 |
|---|---|---|
| Mandatory? | Yes (per MeasObjectNR) | Optional |
| PCI filtering | Measures all cells | Can be associated with a specific PCI list (pci-List) |
| Typical use | Default neighbour cell measurements | Cells with different SSB periodicity |
| Duration | Configurable (1–5 ms) | Typically inherits or has independent duration |
Example scenario: Carrier frequency f2 has macro cells transmitting SSBs with 20 ms periodicity (covered by SMTC1) and small cells transmitting SSBs with 40 ms periodicity (covered by SMTC2 with a PCI list for those small cells).
3. SMTC3 (smtc3)
Introduced: Rel-16/17 (NTN and IAB enhancements)
Configured in: MeasObjectNR / SSB-MTC3List
Purpose: Additional SMTCs for NTN (Non-Terrestrial Networks) where multiple satellites on the same frequency have different SSB timing due to different propagation delays.
In NTN, the challenge is:
- Satellite A at 600 km altitude and satellite B at a different orbital position both serve the same carrier frequency.
- Their SSBs arrive at the UE at vastly different times due to different propagation delays (up to ~40 ms for LEO).
- A single SMTC window cannot capture SSBs from both satellites.
Solution: Configure multiple SMTC windows per carrier — one per satellite or satellite group.
Key characteristics:
- Up to 7 SMTCs can be configured per carrier for NTN (idle/inactive mode).
- Each SMTC3 entry has its own periodicity, offset, and duration.
- The UE may down-select SMTC windows based on GNSS position and ephemeris data — only measuring satellites above the minimum elevation angle.
- Dynamic update: As satellites move, the network updates SMTC3 timing via RRC reconfiguration. The UE may also use ephemeris to autonomously refine timing within the configured window.
SMTC3 parameters (per entry):
SSB-MTC3 ::= SEQUENCE {
periodicity ENUMERATED {sf5, sf10, sf20, sf40, sf80, sf160},
offset INTEGER (0..maxOffset),
duration ENUMERATED {sf1, sf2, sf3, sf4, sf5},
associatedSSB SEQUENCE { ... } -- optional, links to specific SSB config
}
4. SMTC4 (smtc4)
Introduced: Rel-17 (MeasObjectNR enhancements)
Configured in: MeasObjectNR
Purpose: SMTC for serving cell SSB measurements when the serving cell SSB periodicity differs from what is assumed by default, or for Scell SSB measurement timing.
SMTC4 addresses scenarios where:
- The serving cell (PCell or PSCell) SSB timing needs to be explicitly configured for intra-frequency measurements.
- In CA/DC setups, an SCell's SSB periodicity may differ from the PCell's, requiring a separate SMTC.
- Used for L3 measurements on the serving frequency when the SSB config deviates from default assumptions.
5. SMTC-LP (Low Power SMTC / smtc-LP)
Introduced: Rel-19 (RedCap evolution / eRedCap)
Configured in: MeasObjectNR
Purpose: Power-saving SMTC for low-power / low-complexity UEs that enables relaxed measurements with extended periodicities.
SMTC-LP targets RedCap (Reduced Capability) and eRedCap UEs that prioritize battery life:
- Extended periodicities: SMTC-LP supports periodicities beyond 160 ms — up to 320 ms, 640 ms, or even longer — allowing the UE to wake up far less frequently for SSB measurements.
- Relaxed measurement requirements: UEs using SMTC-LP have longer cell identification times and measurement periods (TS 38.133 relaxed requirements).
- Tied to LP-RSRP / LP-RSRQ: TS 38.215 defines Low Power measurement quantities (LP-RSRP, LP-RSRQ) specifically measured within SMTC-LP windows.
- Applicable in low-mobility / stationary scenarios: The network configures SMTC-LP when the UE reports low mobility or the cell determines relaxed measurements are acceptable.
Key differences from SMTC1:
| Aspect | SMTC1 | SMTC-LP |
|---|---|---|
| Target UE | All NR UEs | RedCap / eRedCap / low-power UEs |
| Periodicity range | 5–160 ms | Extended (up to 640+ ms) |
| Measurement quantities | SS-RSRP, SS-RSRQ, SS-SINR | LP-RSRP, LP-RSRQ |
| Power impact | Standard | Significantly reduced wake-ups |
| Cell ID time | Standard (TS 38.133 clause 9) | Relaxed / extended |
| Mobility assumption | Any | Low mobility / stationary |
Complete Comparison Table
| SMTC Type | Release | Primary Use Case | Periodicity | Scope |
|---|---|---|---|---|
| SMTC1 | Rel-15 | Standard inter/intra-freq neighbour cell measurement | 5–160 ms | Per MeasObjectNR (mandatory) |
| SMTC2 | Rel-15 | Cells with different SSB periodicity / specific PCI list | 5–160 ms | Per MeasObjectNR (optional) |
| SMTC3 | Rel-16/17 | NTN multi-satellite per-carrier timing | 5–160 ms | Multiple per carrier (up to 7) |
| SMTC4 | Rel-17 | Serving cell / SCell SSB measurement timing | 5–160 ms | Per serving/SCell |
| SMTC-LP | Rel-19 | Low-power relaxed measurements (RedCap/eRedCap) | Extended (320+ ms) | Per MeasObjectNR |
How SMTC Interacts with Measurement Gaps
SMTC and Measurement Gap Timeline
(MG ∩ SMTC)
- Intra-frequency: UE measures within SMTC window without needing gaps (gap-free if capable).
- Inter-frequency: UE needs a measurement gap; the effective measurement window is the intersection of the gap occasion and the SMTC window.
- RRM impact: Cell identification time =
max(T_SSB, ceil(N × T_SMTC_period))where N depends on SNR conditions (TS 38.133). - Measurement period:
T_measure_NR = max(200 ms, ceil(5 × T_SMTC))for intra-frequency without DRX.
Source Specifications
| Spec | Clause | Content |
|---|---|---|
| TS 38.331 | clause 5.5.2.2 | MeasObjectNR — SMTC1, SMTC2, SMTC-LP configuration |
| TS 38.331 | clause 5.5.2.10 | SS/PBCH block measurement timing configuration procedures |
| TS 38.331 | clause 5.5.2.12 | Effective measurement window |
| TS 38.133 | clause 9 | RRM measurement timing requirements, cell ID time, measurement periods |
| TS 38.215 | clause 4, clause 5 | Physical layer measurement definitions (SS-RSRP, LP-RSRP, etc.) |
| TS 38.300 | clause 9.2.3 | Connected mode mobility, measurement framework overview |
| TS 38.300 | clause 16.14 | NTN-specific measurement and SMTC extensions |
Related Articles
- Measurement Gaps Handling in 5G NR — Gap patterns, per-UE/per-FR gaps, gap sharing
- Where is SSB located in Time Domain? — SS/PBCH block structure, SS burst set
- Cell Defining SSB (CD-SSB) — Understanding the role of CD-SSB in cell search
- Measurement Report Event A3 — Overview of the measurement reporting framework
- SMTC Basics — Fundamentals of SMTC in 5G NR
WirelessBrew Team
Technical expert at WirelessBrew, specializing in 5G NR, LTE, and wireless system optimization. Committed to providing accurate, 3GPP-compliant engineering tools.
Up Next
More 5g nr Articles →