EPS Mobility Management Context

Description

The EPS Mobility Management (EMM) context is a fundamental data structure in the Evolved Packet System (EPS) that represents the mobility management state of a User Equipment (UE). It is created in both the UE and the Mobility Management Entity (MME) upon the successful completion of the initial Attach procedure. This context enables the network to track the UE's location at the Tracking Area level and to manage the UE's reachability for services such as paging and downlink data notification.

The EMM context contains a variety of parameters essential for mobility and session management. These include the Globally Unique Temporary Identity (GUTI), the Tracking Area Identity (TAI) list, the EPS Bearer Contexts, security parameters (such as the Key Set Identifier and the non-access stratum (NAS) keys), the UE's EMM state (EMM-IDLE or EMM-CONNECTED), and various capability and configuration flags. The GUTI, in particular, allows the network to identify the UE without transmitting the International Mobile Subscriber Identity (IMSI) over the radio interface, enhancing privacy and security.

The context is maintained as long as the UE remains registered with the network. It is updated during procedures such as Tracking Area Update (TAU), GUTI reallocation, authentication, and security mode control. When the UE detaches from the network, the EMM context is deleted in both the UE and the MME. The context also plays a critical role during handovers, where it is transferred from the source MME to the target MME to ensure seamless service continuity.

In the UE, the EMM context is stored in the Universal Subscriber Identity Module (USIM) and the mobile equipment's non-volatile memory, allowing the UE to retain its registration state across power cycles. The MME stores the context in its subscriber database, which may be co-located with a Home Subscriber Server (HSS) or accessed via the S6a interface. The EMM context is distinct from the EPS Session Management (ESM) context, which handles bearer and IP address management.

The EMM context is defined in 3GPP TS 24.301 for the NAS protocol and in TS 24.801 for the overall architecture. It is also referenced in TS 23.401, which describes the EPS architecture. The context's structure and procedures are essential for interoperability between different vendors' equipment and for ensuring consistent mobility management across the network.

Purpose & Motivation

The EMM context exists to provide a persistent and synchronized state for mobility management between the UE and the core network. Before its introduction, mobility management in earlier technologies like GPRS relied on separate GMM (GPRS Mobility Management) contexts, which were limited to packet-switched services and did not support the always-on connectivity and higher data rates required by LTE. The EMM context was designed to address the need for a unified mobility management framework that supports both voice and data, integrates security from the start, and enables efficient tracking of UEs in a flat, all-IP network architecture.

The context solves several critical problems: it allows the network to know the UE's location for paging and downlink data delivery, it stores security keys for ciphering and integrity protection of NAS signaling, and it maintains the list of EPS bearers for QoS and session management. Without the EMM context, the network would have to re-authenticate and re-establish sessions each time the UE moved or became active, leading to significant signaling overhead and delays.

Historically, the EMM context was introduced in 3GPP Release 8 as part of the System Architecture Evolution (SAE) that defined the EPS. It replaced the GMM context in 2G/3G networks and was later extended to support features like interworking with non-3GPP accesses, circuit-switched fallback, and narrowband IoT optimizations. Its design has proven robust and has been carried forward into 5G with the 5GMM context, ensuring backward compatibility and smooth evolution.