Description
Mobility in 3GPP networks refers to the ability of a User Equipment (UE) to maintain communication services while moving geographically, without manual intervention. This capability is fundamental to cellular systems and is achieved through a combination of radio access procedures, core network functions, and standardized interfaces. The architecture supporting mobility spans the Radio Access Network (RAN) and the Core Network (CN), with specific protocols and procedures defined across multiple 3GPP specifications.
In the RAN, mobility is managed through cell selection, cell reselection, and handover procedures. When a UE is in idle mode, it performs cell reselection based on signal strength and quality measurements, ensuring it camps on the best available cell. In connected mode, the network controls handovers, which can be intra-frequency, inter-frequency, or inter-RAT (Radio Access Technology). Handovers are triggered by measurement reports from the UE, and the network decides when to transfer the connection to a target cell. Key protocols involved include RRC (Radio Resource Control) for signaling and X2 (or Xn in 5G) for inter-base station coordination.
In the Core Network, mobility is managed by entities such as the Mobility Management Entity (MME) in 4G and the Access and Mobility Management Function (AMF) in 5G. These functions handle UE registration, tracking area updates, paging, and bearer management. They maintain the UE's location at the tracking area level and ensure that downlink data can be delivered when the UE is idle. The core network also manages mobility between different access technologies, such as between 4G and 5G, through interworking procedures.
Mobility also encompasses session continuity, ensuring that ongoing sessions (e.g., voice calls, data transfers) are not interrupted during movement. This is achieved through mechanisms like bearer switching and path updates in the core network. In 5G, the Session Management Function (SMF) and User Plane Function (UPF) collaborate to maintain session continuity, with the UPF anchoring the user plane and the SMF updating the session context as the UE moves.
Overall, mobility is a complex, multi-layered capability that relies on tight coordination between the UE, RAN, and CN. It is continuously evolving to support new use cases such as high-speed trains, drones, and massive IoT, where seamless connectivity is critical.
Purpose & Motivation
Mobility exists to enable users to stay connected while on the move, which is the core value proposition of cellular networks. Before cellular systems, mobile communication was limited to short-range or fixed-line services. The introduction of cellular networks allowed seamless handover between base stations, but early systems (1G/2G) had limited mobility support, often dropping calls when moving between cells. 3GPP standardized mobility procedures to ensure service continuity across technologies and generations.
The purpose of mobility is to provide ubiquitous connectivity, allowing users to make calls, access data, and use applications without being tethered to a specific location. It solves the problem of maintaining session state and routing data to a moving user. This is achieved by tracking the user's location at various granularities (cell, tracking area) and updating the network as the user moves. Mobility also enables load balancing and network optimization by allowing the network to steer users to different cells or frequencies.
Historically, mobility was primarily about voice call continuity. With the advent of mobile broadband, mobility now supports high-speed data, low-latency applications, and diverse devices. The evolution from 2G to 5G has seen mobility become more granular, with features like dual connectivity, carrier aggregation, and network slicing requiring sophisticated mobility management. The ongoing development in Rel-18 and beyond focuses on enhancing mobility for new scenarios like non-terrestrial networks and industrial IoT.
What changed in its specifications
The latest release-to-release comparison of specifications that define Mobility. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-17 added support for Multi-USIM devices, emergency call handling, and definitions for MUSIM UEs.
Full comparison in TS 22.101 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Mobility, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.101 vl00 | 3GPP Service Principles for PLMNs | Rel-21 read |