Description
Evolved Mobility Management (EMM) is a core protocol and state management entity defined for the Evolved Packet System (EPS) and continued into the 5G System (5GS). It operates in the control plane between the User Equipment (UE) and the core network's Mobility Management Entity (MME) in 4G or the Access and Mobility Management Function (AMF) in 5G. EMM is responsible for establishing, maintaining, and releasing the mobility management context of a UE, which is essential for the network to know the UE's location (at the tracking/routing area level) and its connection state (EMM-REGISTERED or EMM-DEREGISTERED). This context is crucial for enabling the network to page the UE for incoming sessions and to authenticate the device for network access.
The protocol defines specific EMM procedures, which are initiated by either the network or the UE. Key UE-initiated procedures include the initial Attach, which registers the UE with the network and establishes a default bearer, and the Tracking Area Update (TAU), which updates the network when the UE moves into a new tracking area. Network-initiated procedures include Authentication and Security Mode Control to establish ciphering and integrity protection, and Detach to gracefully remove the UE's context. EMM works in conjunction with the ESM (EPS Session Management) protocol, which handles bearer management; EMM procedures often carry ESM messages as payload.
EMM states are central to its operation. The primary states are EMM-DEREGISTERED, where the UE is not known to the MME/AMF, and EMM-REGISTERED, where a context exists. Within the EMM-REGISTERED state, sub-states like EMM-IDLE and EMM-CONNECTED indicate whether a signaling connection to the radio access network is active. Transitions between these states are triggered by specific events, such as successful attach (deregistered to registered) or connection release (connected to idle). The protocol ensures that security keys are established during registration and are used to protect all subsequent NAS (Non-Access Stratum) signaling messages, providing a secure foundation for mobility management.
Purpose & Motivation
EMM was created as part of the System Architecture Evolution (SAE) in 3GPP Release 8 to provide a unified, IP-based mobility management framework for the new Evolved Packet Core (EPC). Previous 3GPP systems like GPRS and UMTS had mobility management (GMM) that was more tightly coupled with the circuit-switched domain and the legacy network architecture. The purpose of EMM was to design a cleaner, more efficient protocol optimized for all-IP networks, supporting seamless mobility between 3GPP and non-3GPP access networks (like Wi-Fi).
It solved the problem of managing mobility in a flatter network architecture where the control plane (handled by the MME) was separated from the user plane. EMM provides a standardized way for the UE and network to negotiate capabilities, establish security, and maintain location information without the overhead of the older circuit-switched paradigms. Its creation was motivated by the need for higher data rates, lower latency, and simplified network architecture required for LTE, and it laid the groundwork for the mobility management in 5G, where it evolved into the NAS protocol for Registration and Connection Management handled by the AMF.
What changed in its specifications
The latest release-to-release comparison of specifications that define EMM. Each summary describes the whole specification, not only this term.
Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.
Full comparison in TS 23.401 →Rel-19 adds store-and-forward satellite operation for NTN, control plane CIoT data overhead reduction via EMM TRANSPORT and Data container IE, and RAT utilization control. It also adds disaster roaming indications and MINT-EPS support, plus MPS priority for messaging paging.
Full comparison in TS 24.301 →Technology family
NAS mobility and session protocols · User Equipment › Protocol Layers (NAS)
- EMM counterpart in another generation: GMM
“The same list is used by 5GMM, EMM, GMM and MM (see 3GPP TS 24.501 [167] and 3GPP TS 24.301 [120])” TS 24.008
- EMM counterpart in another generation: 5GMM
“The same list is used by 5GMM, EMM, GMM and MM” TS 24.501
- EMM counterpart in another generation: MM
“The same list is used by 5GMM, EMM, GMM and MM (see 3GPP TS 24.501 [167] and 3GPP TS 24.301 [120])” TS 24.008
- EMM used together with ESM
“the ESM entity provides services to the Bearer Control (BC) entity and uses services of the MM sublayer. The ESMS entity is an extension of the SMS entity for non-EPS services. For message transfer, it uses the services from the EMM entity of the MM sublayer;” TS 24.007
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 13 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
EMM is specified for the first time in Rel-8: TS 24.301 defines the EPS Mobility Management protocol for mobility and NAS security control, and TS 23.401 defines the EMM states.
- “The EPS Mobility Management (EMM) protocol defined in the present document provides procedures for the control of mobility when the User Equipment (UE) is using” TS 24.301 v8.10.0
- “The EPS Mobility Management (EMM) states describe the Mobility Management states that result from the mobility management procedures” TS 23.401 v8.18.0
- “An EMM context is established in the UE and the MME when an attach procedure is successfully completed.” TS 24.301 v8.10.0
EMM procedures were extended in Rel-9 for emergency attach (emergency EMM context, reject causes, EMM-DEREGISTERED.NO-IMSI), CSG-related detach cause handling, and EMM state handling for emergency attached UEs.
- “Upon receiving the ATTACH REJECT message including EMM cause #5, the UE shall enter the state EMM-DEREGISTERED.NO-IMSI.” TS 24.301 v9.11.0
- “to attach the IMSI or IMEI for emergency bearer services, and to establish an EMM context and a default bearer” TS 24.301 v9.11.0
- “the MME changes the EMM state of the UE to EMM-DEREGISTERED” TS 23.401 v9.16.0
EMM procedures changed in Rel-10: NAS-level mobility management congestion control with back-off timer T3346 was added, and network-initiated detach handling and EMM-DEREGISTERED state behaviour were revised, including new EMM cause handling.
- “the network shall set the EMM cause value to #22 "congestion" and assign a back-off timer T3346.” TS 24.301 v10.15.0
- “The network may detect EMM signalling congestion and perform NAS level mobility management congestion control.” TS 24.301 v10.15.0
- “the network shall enter state EMM-DEREGISTERED. If the Detach type IE indicates "IMSI detach", the network shall not change the current EMM state.” TS 24.301 v10.15.0
MME handling of a SERVICE REQUEST or EXTENDED SERVICE REQUEST failing integrity check is specified: reject with EMM cause #9 if only non-emergency PDN connections exist, and may skip authentication only if an emergency PDN connection exists.
- “stop any of the timers T3410, T3417, T3430, T3418 or T3420 (if they were running)” TS 24.301 v11.14.0
EMM behaviour in TS 24.301 changed: PSM handling in EMM-REGISTERED substates, E-UTRA disabling for EMM cause #15, new T3440 start conditions, and SERVICE REJECT with EMM cause #9 on integrity failure.
- “If PSM is active, the UE can deactivate PSM at any time by activating the AS layer when the UE needs to send mobile originated signalling or user data.” TS 24.301 v12.13.0
- “The UE may support "E-UTRA Disabling for EMM cause #15" and implement the following behaviour:” TS 24.301 v12.13.0
- “shall start the timer T3440 if the UE receives any of the EMM cause values #11, #12, #13, #14” TS 24.301 v12.13.0
EMM behaviour now covers resuming a NAS signalling connection for RRC cause selection, exempts UE-initiated user data transport via control plane from ESM suspension, and makes default bearer establishment at attach optional.
- “or when EMM requests the lower layers to resume a NAS signalling connection, the RRC establishment cause used by the UE shall be selected” TS 24.301 v13.12.0
- “Except for the attach procedure and the service request procedure for UE initiated transport of user data via the control plane” TS 24.301 v13.12.0
EMM behaviour in TS 24.301 changed: eCall over IMS and test-call handling in EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH, PSM deactivation allowing EMM procedures, and revised EMM substate and shared-network PLMN handling.
- “if the UE receives a request from upper layers to establish an eCall over IMS, the UE enters state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH.” TS 24.301 v14.10.0
- “Upon deactivating PSM, the UE may initiate EMM procedures (e.g. for the transfer of mobile originated signalling or user data).” TS 24.301 v14.10.0
- Keep forbidden PLMN after receiving integrity protected EMM #11,14,35 TS 24.301CR2909
EMM procedures in TS 24.301 gained service gap control, an Extended EMM cause for NB-IoT not allowed, and a revised AUTHENTICATION REJECT timer list, and 5GMM/EMM coordination for interworking was specified.
- “If the network supports service gap control (SGC) feature and the service gap time value is available in the EMM context of the UE, the MME shall consider SGC as active for the UE.” TS 24.301 v15.8.0
- “if the UE is in NB-S1 mode and the Extended EMM cause IE with value "NB-IoT not allowed" is included in the ATTACH REJECT message” TS 24.301 v15.8.0
- Extended EMM cause for NB-IoT TS 24.301CR3035
EMM procedures and cause handling were changed in Rel-16, including RLOS attach with EMM substates, EMM cause #31 redirection to 5GCN, and corrected EMM cause handling for service reject and authentication reject.
- “The network redirects the UE to 5GCN by rejecting the attach request, or tracking area update request, or service request with the EMM cause #31” TS 24.301 v16.9.0
- Adding the stage 3 detail on EMM substates for attaching for access to RLOS. TS 24.301CR3179
- “the UE shall abort any EMM signalling procedure, stop any of the retransmission timers that are running” TS 24.301 v16.9.0
EMM behaviour changed in Rel-17: new EMM cause #78 for satellite E-UTRAN access with a stored PLMN list, and a UE timer-based remain-camped behaviour in EMM-REGISTERED.LIMITED-SERVICE.
- “The UE may be rejected with EMM cause #78 in ATTACH REJECT message, TRACKING AREA UPDATE REJECT message or DETACH REQUEST message.” TS 24.301 v17.12.0
- “may then start an implementation-specific timer and enter the state EMM-REGISTERED.LIMITED-SERVICE” TS 24.301 v17.12.0
- Handling of reject cause #78 in EMM procedures TS 24.301CR3620
EMM behaviour in TS 24.301 changed: EMM state handling for discontinuous coverage, new EMM cause #78 reject handling, and 5GMM/EMM coordination in single-registration mode.
- “E-UTRAN coverage has been lost, PSM is active in the UE or the access stratum is de-activated due to discontinuous coverage” TS 24.301 v18.9.0
- EMM state for discontinuous coverage TS 24.301CR3903
- Handling of a reject message including EMM cause value #78 without integrity protection TS 24.301CR3945
EMM procedures in TS 24.301 changed: a new EMM TRANSPORT message supports reduced-overhead control plane CIoT data transfer, with its own security protection, integrity check and ciphering rules.
- “Control plane CIoT EPS optimization using EMM messages with reduced protocol overhead.” TS 24.301 v19.8.0
- “The UE shall cipher the EMM TRANSPORT message including the Data container IE by ciphering the part of the message consisting of octet 7 and all subsequent octets” TS 24.301 v19.8.0
- NAS overhead reduction for CP CIoT data transport, EMM data transport procedure TS 24.301CR4464
The UE may re-enable satellite E-UTRAN capability for the current PLMN after NAS connection release when access technology utilization control information says satellite E-UTRAN is not restricted.
- “the UE receives an access technology utilization control information indicating that satellite E-UTRAN is not restricted, the UE may enable the satellite E-UTRAN capability” TS 24.301 v20.1.0
Defining Specifications
3GPP specifications that define or reference EMM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 read |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 read |
| TS 26.851 vb20 | MBMS Multimedia Service Enhancements | Rel-11 read |
| TS 31.121 vj00 | UICC Application Test Specification | Rel-19 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.401 vj00 | E-UTRAN Overall Architecture Description | Rel-19 read |
| TS 36.509 vi00 | UE Conformance Test Loop Functions | Rel-18 read |