Network Mode of Operation

Description

Network Mode of Operation (NMO) is a fundamental configuration parameter for a mobile network, defining the high-level operational paradigm of the Core Network (CN) with respect to the services it provides and how it interacts with User Equipment (UE). It specifically governs the relationship and availability of the Circuit-Switched (CS) domain (for traditional voice and SMS) and the Packet-Switched (PS) domain (for IP-based data) within the network infrastructure. The NMO setting instructs UEs on how to attach to the network and which domains to register with, directly influencing service accessibility and handover procedures.

Technically, NMO is broadcast by the network in system information (e.g., in LTE's SIB1) and is a critical parameter during UE attachment and tracking area update procedures. The UE reads this parameter and behaves accordingly. For instance, in an NMO-I network, the UE performs a Combined EPS/IMSI Attach, registering simultaneously with both the EPS (PS) and CS domains. This allows the Mobility Management Entity (MME) to act as a proxy for CS signaling, enabling functionalities like SMS over SGs interface without a full CS radio connection. The NMO dictates the network's strategy for delivering voice services: whether it relies on the legacy CS domain (via CS Fallback or Single Radio Voice Call Continuity), uses the PS domain exclusively (IMS-based VoLTE/VoNR), or uses a combination.

The NMO has profound architectural implications. It determines whether the network needs to maintain a functional CS Core (MSC) alongside the PS Core (EPC/5GC). In modes like NMO-II or III, the CS domain might be absent or not supported for certain access technologies, pushing all services to the PS domain and the IP Multimedia Subsystem (IMS). This is central to the evolution towards all-IP networks. The choice of NMO affects mobility management, paging strategies, and service continuity during handovers between different radio access technologies (e.g., LTE to 2G/3G). It is a key decision for network operators migrating their voice services from legacy CS to modern VoIP solutions.

Purpose & Motivation

NMO was introduced to manage the complex transition from 2G/3G networks, which were built around a robust Circuit-Switched core for voice, to 4G LTE and beyond, which are inherently all-Packet-Switched. LTE was designed as a data-only technology from the radio perspective, lacking native CS bearers. This created a challenge for providing ubiquitous voice service, a critical revenue stream and user expectation. The NMO concept provided a standardized framework to define how a network would bridge this gap during the transition period.

It solved the problem of service continuity and device interoperability. Without a defined NMO, UEs would not know how to behave in a mixed-network environment. NMO provides clear signaling to the UE about what services are available and through which domain, ensuring predictable user experience. It addressed the limitations of previous "always-on-CS" models by allowing networks to gradually phase out the CS core, first by using it as a fallback (CSFB), then as a signaling proxy for SMS, and eventually retiring it completely for a full IMS-based voice solution (VoLTE/VoNR).

Historically, as operators deployed LTE, they needed a path to maintain voice service while building out their IMS capabilities. NMO provided the blueprint for this migration. For example, starting with NMO-I (CSFB for voice) allowed immediate LTE data deployment, then moving to NMO-II/III with VoLTE represented the target all-IP architecture. This structured approach prevented fragmentation and ensured devices from different manufacturers would work consistently on networks worldwide, which was essential for global LTE adoption.

Key Features

• Defines CS and PS domain availability and interworking
• Determines UE attachment procedure (Combined vs. EPS-only attach)
• Governs voice service delivery method (CSFB, VoLTE, VoNR)
• Impacts SMS delivery mechanism (over SGs, over IMS)
• Influences network architecture and core element requirements
• Controls mobility and handover behavior between LTE and 2G/3G

Evolution Across Releases

Defining Specifications