NBM

Network Based Mobility Management

Mobility
Introduced in Rel-8
A mobility management architecture where the network controls and manages the mobility of user equipment (UE). It is a core concept in 3GPP Evolved Packet Core (EPC) and 5G Core (5GC), enabling seamless handovers and session continuity without requiring the UE to be heavily involved in the signaling process.

Description

Network Based Mobility Management (NBM) is a fundamental architectural paradigm in 3GPP systems, primarily defined for the Evolved Packet System (EPS) and continued into the 5G System (5GS). In this model, the network infrastructure is responsible for tracking the location of the User Equipment (UE) and managing the mobility-related signaling required to maintain IP connectivity as the UE moves. The UE's role is simplified; it performs access network attachment and may report its location, but the complex tasks of managing mobility contexts, bearer paths, and handover decisions are handled by network nodes. This contrasts with host-based mobility protocols like Mobile IP, where the UE is actively involved in managing its own mobility binding and tunnel establishment.

In the EPS, NBM is implemented through protocols like the GPRS Tunneling Protocol (GTP) and the Proxy Mobile IP (PMIP) variant. The key network functions are the Mobility Management Entity (MME) for control plane mobility and the Serving Gateway (S-GW) and Packet Data Network Gateway (P-GW) for user plane mobility. The MME tracks the UE's location at the Tracking Area level and manages the signaling for handovers and bearer establishment. The S-GW acts as the local mobility anchor, switching the user plane path as the UE moves between eNodeBs. The P-GW serves as the IP anchor point, providing a stable IP address for the UE's PDN connection regardless of its location within the network.

In the 5GS, the NBM principle continues with the Access and Mobility Management Function (AMF) and the Session Management Function (SMF) taking on the control plane roles. The User Plane Function (UPF) acts as the mobility anchor for the user plane, analogous to the S-GW and P-GW. The 5GC introduces enhanced flexibility, such as the ability to select different UPFs for different PDU Sessions (UL CL, BP) to optimize traffic routing. NBM enables features like seamless handover, idle mode mobility (tracking area updates), and session continuity. Its network-centric approach allows for optimized routing, efficient network resource utilization, and the implementation of advanced policies (e.g., QoS, charging) by the operator, which would be more complex if managed directly by the UE.

Purpose & Motivation

NBM was developed to provide a scalable, efficient, and operator-controlled method for managing user mobility in packet-switched cellular networks. Prior to 3GPP's adoption of a unified NBM approach for EPS in Release 8, mobility management was often tied to specific access technologies and could involve host-based schemes that placed significant processing and signaling burden on the mobile device. The primary motivation was to design a network architecture that could support seamless mobility for a massive number of devices with varying capabilities, from smartphones to IoT sensors, while maintaining session continuity for IP-based services.

The architecture solves several key problems. First, it centralizes intelligence in the network, allowing operators to optimize handover decisions based on network load, subscriber policies, and service requirements. Second, it simplifies the UE design and conserves its battery life by offloading complex signaling procedures. Third, it provides a stable anchor point for the user's IP session, ensuring that ongoing communications (like VoIP calls or video streams) are not interrupted during movement. This is critical for delivering a consistent quality of experience. Furthermore, NBM is essential for enabling core network features like lawful interception, detailed charging records, and the application of consistent policy and QoS enforcement regardless of the UE's point of attachment.

Historically, NBM in EPS (using GTP) was a natural evolution from the GPRS core network, providing a smooth migration path for operators. Its continuation and enhancement in 5GS demonstrate its foundational role in providing reliable mobility as a service, which is a prerequisite for enabling advanced use cases like massive IoT, ultra-reliable low-latency communications (URLLC), and network slicing, where predictable and managed mobility is paramount.

Key Features

  • Network-controlled mobility signaling and handover decisions
  • UE simplification with reduced signaling burden and power consumption
  • IP session continuity through stable network anchor points (S-GW/P-GW in EPS, UPF in 5GS)
  • Support for both GTP and PMIP based mobility protocols in the user plane
  • Enables idle mode mobility management via tracking/routing area updates
  • Foundation for policy enforcement, charging, and lawful interception across the network

Evolution Across Releases

Rel-8 Initial

Introduced as the foundational mobility architecture for the Evolved Packet System (EPS). Defined GTP-based NBM between the Serving Gateway (S-GW) and Packet Data Network Gateway (P-GW), and between eNodeBs and the S-GW. Also specified Proxy Mobile IPv6 (PMIPv6) as an alternative user plane protocol between S-GW and P-GW. Established the Mobility Management Entity (MME) as the key control plane node for tracking area management and handover signaling.

Enhanced NBM for emergency services and location services. Introduced optimizations for handovers between 3GPP and non-3GPP access networks (e.g., WLAN) connected via the S2a/S2b interfaces, maintaining the network-based mobility principle across heterogeneous access.

Introduced Dual Connectivity, where a UE can be connected to two eNodeBs. NBM was extended to manage the user plane aggregation and mobility for the secondary cell group, with the Master eNodeB and S-GW coordinating the bearer management.

Enhanced NBM for Machine-Type Communications (MTC), introducing features like extended idle mode DRX and new power saving modes that leveraged the network's control to optimize signaling for low-power devices.

Further enhancements for small cell and dual connectivity scenarios. Introduced network-based IP flow mobility (IFOM) and seamless WLAN offload, giving the network greater control over steering specific IP flows between 3GPP and WLAN access.

Extended NBM principles to support LTE-WLAN Aggregation (LWA) and LTE-WLAN Radio Level Integration (LWIP), where the network controls the aggregation and switching of data flows at the radio level.

Enhanced support for Vehicle-to-Everything (V2X) communications, where NBM mechanisms were adapted to handle high-mobility scenarios and proximity services with network-controlled authorization and mobility management.

Fundamentally redefined NBM for the 5G System (5GS). Replaced EPC nodes with Service-Based Architecture (SBA) functions: AMF for mobility management, SMF for session management, and UPF as the user plane anchor. Introduced service-based interfaces (e.g., N1, N2) and enhanced support for network slicing within the NBM framework.

Enhanced 5GS NBM for integrated access and backhaul (IAB), non-public networks (NPN), and access traffic steering, switching and splitting (ATSSS). The network's control was extended to manage mobility across these new deployment scenarios and multi-access PDU sessions.

Further enhanced NBM for 5GS to support reduced capability (RedCap) devices, satellite access, and edge computing. Introduced enhancements for network-controlled mobility in non-terrestrial networks and service continuity for edge applications.

Ongoing evolution for 5G-Advanced, focusing on network energy savings, enhanced network automation, and AI/ML-assisted mobility management, where NBM principles are applied to make more intelligent and predictive handover decisions.

Continued enhancements for 5G-Advanced, expected to further refine NBM for extreme mobility scenarios, AI-native air interface, and tighter integration with application-layer requirements for immersive services.

Defining Specifications

SpecificationTitle
TS 23.402 3GPP TS 23.402
TS 24.302 3GPP TS 24.302
TS 29.273 3GPP TS 29.273