RSSI Measurement Timing Configuration

Description

The RSSI Measurement Timing Configuration (RMTC) is a crucial mechanism defined in 3GPP specifications for enabling Listen-Before-Talk (LBT) and channel occupancy measurements in unlicensed and shared spectrum. It is a configuration message sent by the network (via RRC signaling) to a User Equipment (UE), defining a specific measurement window for performing wideband RSSI measurements on one or more carrier frequencies. The primary goal is to sense the radio environment to determine if a channel is idle or busy before the network or UE transmits, which is a regulatory requirement in many unlicensed bands (e.g., 5 GHz).

An RMTC configuration includes several key parameters: the carrier frequency (or list of frequencies) to measure, the measurement bandwidth, the timing of the measurement window (specified as an offset and duration relative to a reference SFN), and the periodicity of these measurement occasions. The UE uses this configuration to activate its receiver at the specified times and frequencies, measures the total received power (RSSI) within the configured bandwidth, and processes the results. The measurement is typically an energy detection mechanism, not requiring synchronization to any specific signal. The UE then reports the measurement results back to the network, often in the form of channel occupancy statistics (e.g., the percentage of time the RSSI was above a certain threshold).

The network utilizes these reports for dynamic channel selection and channel access procedures. For example, in License-Assisted Access (LAA) and NR-U (NR in unlicensed spectrum), a gNB may configure UEs with RMTC to scout for clean channels in the unlicensed band. Based on collective reports from multiple UEs, the gNB can decide which carrier to use for secondary cell (SCell) activation, thereby improving overall system performance and coexistence with other systems like Wi-Fi. The RMTC mechanism allows the network to delegate the sensing task to UEs, providing a distributed view of the radio environment without requiring the base station itself to constantly monitor all potential channels.

Purpose & Motivation

RMTC was introduced in 3GPP Release 13 as part of the LTE-LAA (License-Assisted Access) work item to enable LTE operation in the unlicensed 5 GHz spectrum. The core problem it solved was how to efficiently meet regulatory Listen-Before-Talk (LBT) requirements while maintaining network control. Unlike Wi-Fi, which uses distributed contention (CSMA/CA), LAA adopted a more centralized approach where the network (eNodeB) coordinates channel access. RMTC provided the tool for this coordination by allowing the network to instruct UEs—devices already equipped with receivers—to perform the necessary channel sensing on its behalf.

This approach addressed several limitations. First, it provided the network with a broader and more accurate view of interference conditions across different locations within a cell, which a single base station measurement could not achieve. Second, it enabled efficient use of UE resources by configuring measurements only when needed and on specific frequencies of interest. Third, it was essential for fair coexistence with other technologies like Wi-Fi, as it allowed the LTE/5G system to accurately assess channel occupancy before transmitting. The concept was later carried forward into 5G NR-U (Release 16 and beyond), where it remains a foundational element for operating NR in shared and unlicensed spectrum, supporting use cases like enhanced mobile broadband and private network deployments.

Key Features

• Configures UE-based RSSI measurement windows for channel sensing
• Includes parameters for carrier frequency, bandwidth, timing offset, duration, and periodicity
• Essential for meeting Listen-Before-Talk (LBT) regulatory requirements in unlicensed spectrum
• Enables network-coordinated channel selection for LAA and NR-U
• Supports measurement reporting for channel occupancy statistics
• Allows distributed environment sensing by leveraging multiple UEs

Evolution Across Releases

Defining Specifications