MTC Wake Up Signal

Description

The MTC Wake Up Signal (MWUS) is a power-saving mechanism introduced for LTE-based Cellular Internet of Things (CIoT) technologies, specifically Narrowband IoT (NB-IoT) and LTE for Machine-Type Communications (LTE-M). It is a physical layer signal designed to enable extreme power saving for devices that are predominantly in a deep sleep state, known as Power Saving Mode (PSM) or extended Discontinuous Reception (eDRX). The core principle is to separate the low-power monitoring for network paging from the high-power operation of the device's main receiver. Architecturally, the MWUS is transmitted by the base station (eNB for LTE, gNB for NR in some contexts) in the downlink. It is a simple, robust, and very short signal that can be detected by an ultra-low-power receiver circuit (the Wake-Up Receiver - WUR) within the MTC device. This WUR consumes orders of magnitude less power than the device's primary LTE/NB-IoT receiver. The MWUS itself does not carry specific data; it is an on/off indicator. Its transmission is coordinated with the device's paging occasion. How it works: An MTC device configured with MWUS support enters a deep sleep state, powering down almost all circuitry except for the minimal WUR. The network, when it has downlink data or signaling (like a mobile-terminated request) for the device, first transmits the MWUS in a pre-defined resource, aligned with the device's calculated MWUS occasion. The device's WUR periodically wakes up for a very short duration to check for the presence of this signal. If the WUR detects the MWUS, it triggers the device's main application processor and primary LTE/NB-IoT receiver to fully power on. The device then proceeds to monitor its actual paging occasion (PO) in the usual way to receive the paging message containing the details of the downlink transaction. If no MWUS is detected, the WUR goes back to sleep, and the main receiver remains off, saving substantial energy. The configuration of MWUS, including its periodicity and radio resources, is signaled to the device via Radio Resource Control (RRC) messages or system information. This mechanism is a key enabler for battery lifetimes exceeding 10 years for certain IoT applications.

Purpose & Motivation

MWUS was created to address a critical challenge in massive Machine-Type Communications (mMTC): achieving ultra-long battery life, often a decade or more, for stationary or infrequently communicating sensors and meters. Prior to MWUS, power saving relied on PSM and eDRX, where devices sleep for long periods but still must periodically wake up their full, power-hungry LTE receiver to check for paging messages. This 'blind' waking incurs a significant energy cost, even when no data is waiting. MWUS solves this by introducing a two-step wake-up process. The problem it addresses is the energy wasted during these unnecessary full receiver activations. The motivation was driven by the stringent requirements of utilities (smart meters), agricultural sensors, and infrastructure monitoring devices, where battery replacement is costly or impossible. By allowing the device to remain in a very deep sleep and use a tiny, specialized circuit to listen for a simple 'wake-up' cue, the energy consumption during idle periods is drastically reduced. This innovation directly extends the operational lifetime of the device, making cellular IoT a viable and competitive technology for a wider range of low-power, wide-area (LPWA) applications. It was a key feature introduced in 3GPP Release 15 as part of the ongoing enhancements for CIoT, specifically to push the boundaries of power efficiency beyond what was possible with PSM and eDRX alone.

Key Features

• Ultra-low-power Wake-Up Receiver (WUR) for signal detection
• Physical layer signal (MWUS) transmitted before paging occasions
• Significantly reduces energy consumption during idle periods
• Applicable to both NB-IoT and LTE-M (eMTC) technologies
• Configurable via RRC signaling for flexible power saving profiles
• Enables battery life extension beyond 10 years for suitable IoT applications

Evolution Across Releases

Defining Specifications