Mobility Management

Description

Mobility Management (MM) is a core network function that operates at the Non-Access Stratum (NAS) layer, managing the mobility of a User Equipment (UE) independent of the underlying radio access technology. The primary objective of MM is to maintain an accurate location of the UE so that the network can successfully deliver incoming calls, messages, and data sessions. It achieves this by managing different UE states, primarily the IDLE and CONNECTED states, and by handling procedures that transition the UE between these states. In the IDLE state, the UE is not actively transmitting user data but is registered with the network and listening for paging messages. The CONNECTED state (or ACTIVE state in some contexts) signifies that a signaling connection exists between the UE and the core network, allowing for active communication.

The MM function relies on a set of information known as the MM Context. This context is stored in both the UE and relevant core network nodes, such as the Serving GPRS Support Node (SGSN) in 2G/3G or the Access and Mobility Management Function (AMF) in 5G. The MM Context includes critical parameters like the UE's temporary identity (TMSI, GUTI), security keys, the UE's current registration area, and its current mobility management state. This shared context allows the network and UE to have a synchronized view of the UE's mobility status, enabling efficient procedures like periodic registration updates, handovers between cells or tracking areas, and service requests to re-establish user plane connections.

Key MM procedures include Attach/Registration, Detach/Deregistration, Tracking Area Update (TAU) or Routing Area Update (RAU), Periodic Registration Update, and Service Request. The Attach procedure establishes the UE's presence in the network and creates the initial MM context. Periodic updates and TAUs/RAUs keep the network informed of the UE's location as it moves, ensuring the network can page the UE within a specific area rather than across the entire network. The Service Request procedure is triggered by the UE or network to transition the UE from IDLE to CONNECTED state for user data transfer. These procedures are fundamental to the operation of any cellular network, ensuring that mobile devices remain reachable while optimizing the use of radio and network resources by minimizing signaling overhead when the device is stationary or inactive.

In the evolution from 2G/3G to 4G and 5G, the core principles of MM remain, but the specific network entities and protocol details have evolved. For instance, in 5G, the MM function is logically separated from Session Management (SM) and is housed within the AMF. The 5G MM introduces concepts like Registration Areas, which can be a list of Tracking Areas, and enhanced states for power saving (e.g., RRC_INACTIVE). Despite these architectural shifts, the fundamental role of MM—tracking UE location, managing reachability, and supporting session continuity—remains a cornerstone of 3GPP mobile network architecture.

Purpose & Motivation

Mobility Management exists to solve the fundamental challenge of providing seamless communication to a device that is free to move throughout a wide geographic area. In a fixed network, a device's point of attachment and address are static. In a mobile network, the point of attachment (the cell) changes constantly. Without MM, the network would have no way to locate a UE to deliver incoming services, rendering mobile communication impossible. The primary problems MM addresses are UE reachability, efficient resource usage, and session continuity during movement.

Historically, early cellular systems like GSM introduced basic MM concepts such as location areas and periodic updates. The limitations of earlier, simpler approaches included excessive paging load (if the location was too coarse) or excessive signaling traffic from frequent updates (if the location area was too small). 3GPP's MM protocols evolved to create a balanced, scalable system. It introduced hierarchical concepts like Routing Areas (for packet-switched domains) and Tracking Areas, and states like IDLE and CONNECTED to optimize signaling. The MM context allows the network to store just enough information to quickly re-establish a connection without needing a full re-authentication every time the UE moves or wakes up from a power-saving state.

The creation and continuous enhancement of MM protocols were motivated by the need to support an ever-growing number of mobile subscribers, diverse services (from voice to high-speed data), and new device types (IoT sensors with very different mobility patterns). It provides the foundational layer upon which all other services—voice calls, internet browsing, IoT messaging—are delivered reliably to a moving target. It is a critical enabler for the 'anywhere, anytime' connectivity promise of cellular networks.

Key Features

• Manages UE states (IDLE, CONNECTED, INACTIVE) to balance reachability and power efficiency
• Maintains a shared MM Context between UE and network nodes for synchronized mobility state
• Executes location update procedures (TAU, RAU, Periodic Registration) to track UE movement
• Handles Attach/Registration and Detach/Deregistration procedures for network entry and exit
• Initiates Service Request procedure to transition UE to connected state for data transfer
• Works in conjunction with paging to locate an IDLE UE within a specific area for incoming communication

Evolution Across Releases

Defining Specifications