Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

MME

Mobility Management Entity

Core Network →

MME is the key control-plane node in the 4G LTE Evolved Packet Core that manages UE mobility, session establishment, authentication, and handover signaling.

Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
85 specs
Also in
Radio Access Network, Management, Security
MME Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Mobility Management Entity (MME) is a fundamental control-plane entity within the 4G LTE Evolved Packet Core (EPC) architecture. It does not handle user data traffic but is exclusively responsible for signaling and control functions related to UE mobility and session management. The MME interacts with several other network elements via standardized interfaces. Key interfaces include the S1-MME interface to the eNodeB (eNB) for control signaling, the S6a interface to the Home Subscriber Server (HSS) for subscriber authentication and authorization, the S11 interface to the Serving Gateway (SGW) for session management, and the S3 interface to the SGSN for inter-system mobility with 2G/3G networks.

Architecturally, the MME operates as a state machine for each attached UE, maintaining the UE's mobility management context (e.g., tracking area, connection state) and session management context (bearer information). Its core functions include: managing the attach/detach procedures and authentication via the HSS; initiating the establishment, modification, and release of default and dedicated bearers by coordinating with the SGW and PGW; managing tracking area updates and paging procedures to locate UEs for incoming sessions; and controlling handover signaling, including selection of target eNBs and SGWs. It also plays a role in lawful interception and supports features like CS Fallback for voice services.

In the network ecosystem, the MME acts as the central brain for control-plane mobility. It ensures the UE is reachable, authenticated, and has the appropriate bearers established for data services. Its decisions directly impact signaling efficiency, handover success rates, and overall network reliability. While its functions are largely subsumed by the Access and Mobility Management Function (AMF) in the 5G Core (5GC), the MME remains critical for LTE networks and interworking scenarios with 5G.

Purpose & Motivation

The MME was created as part of the LTE/EPC architecture in 3GPP Release 8 to address limitations of previous 2G/3G architectures, specifically the separation of control and user plane. In pre-4G systems like UMTS, the SGSN handled both control signaling and user data forwarding, which could lead to scalability bottlenecks and complex upgrades. The EPC introduced a clear split between the control plane (MME) and user plane (SGW/PGW), enabling independent scaling, optimized signaling paths, and more efficient mobility management.

The primary problems the MME solves are streamlined UE attachment, secure authentication, efficient tracking and paging of mobile devices, and seamless mobility management. It centralizes the control logic, reducing signaling load on user-plane gateways and allowing for more sophisticated mobility features like optimized handovers and idle mode mobility. Its creation was motivated by the need for a flatter, all-IP network architecture capable of supporting higher data rates, lower latency, and a massive increase in connected devices, which the integrated design of earlier systems struggled to accommodate efficiently.

What changed in its specifications

The latest release-to-release comparison of specifications that define MME. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 23.009Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.009: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.009 →

Architecture

Where it sits in the network

Evolution Lineage

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
  • MME counterpart in another generation: 3G-SGSN (not stated verbatim in the specifications)
  • MME counterpart in another generation: SGSN
    “3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol"” TS 23.002
  • MME counterpart in another generation: AMF
    “At inter-system handover, the AMF selects target MME based on 2 octet TAC format used in the Target ID as specified in TS 38.413 [34].” TS 23.501

Security functions and anchors · Security

  1. Phase 1 AuC
  2. R99 HLR/AuC
  3. Rel-5 HSS
  4. Rel-6 3GPP AAA Server, BSF
  5. Rel-8 ASME, MME
  6. Rel-9 HSS-FE
  7. Rel-15 AMF, ARPF, AUSF, SEAF, SEPP, SIDF
  8. Rel-16 AAnF
  • MME counterpart in another generation: AMF
    “When a UE is CM-CONNECTED in 5GC and a handover to EPS occur, the AMF selects the target MME based on the source AMF Region ID, AMF Set ID and target location information.” TS 23.501

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 sources

Documented 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.

Rel-8 introduced

The MME is specified for the first time in Rel-8 as the LTE control-plane node: it handles load balancing, overload control, RFSP Index handling, NAS security, and the S11/S10/S6a procedures.

  • “The MME shall contain mechanisms for avoiding and handling overload situations.” TS 23.401 v8.18.0
  • “The MME shall make use of this procedure to update the MME identity stored in the HSS” TS 29.272 v8.14.0
  • “the MME shall generate a KSISGSN, create a nonceMME and generate the K'ASME using the created nonceMME” TS 24.301 v8.10.0
Rel-9 specification text

MME handling changed: it chooses the RFSP Index in use per operator configuration, sets EIA0/EEA0 with a locally generated K'ASME for emergency handover, and moves emergency attached UEs to EMM-DEREGISTERED after a mobile reachable timer expires.

  • “Any time after expiry of this timer the MME may change the EMM state of an emergency attached UE to EMM-DEREGISTERED.” TS 23.401 v9.16.0
  • “the MME shall set EIA0 and EEA0 as the selected NAS security algorithms in the NAS security transparent container for handover to E-UTRAN” TS 24.301 v9.11.0
Rel-10 specification text

In Rel-10 the MME gained new behaviours: overload restriction via S1 OVERLOAD START with traffic load reduction, throttling of low-priority Downlink Data Notifications, NAS level congestion control, and long periodic TAU timer allocation.

  • “The MME may optionally include a Traffic Load Reduction Indication in the OVERLOAD START message.” TS 23.401 v10.13.0
  • “the MME can request the SGWs to selectively reduce the number of Downlink Data Notification requests it sends for downlink low priority traffic” TS 23.401 v10.13.0
  • “The MME may allocate long periodic TAU timer value to the UE according to clause 4.3.17.3.” TS 23.401 v10.13.0
Rel-11 1 CR

In Rel-11 the MME gained new behaviour: it signals homogeneous IMS voice over PS support to the HSS, registers for SMS in MME, and handles overload back-off with low access priority.

  • “if "IMS Voice over PS Sessions" is supported homogeneously in all TAs in the serving MME for the UE, the MME shall include the” TS 23.401 v11.11.0
  • “If the MME supports the "SMS in MME" feature and the UE has requested a combined EPS/IMSI attach” TS 29.272 v11.14.0
  • Registration of MME for SMS TS 23.272CR0839
Rel-12 specification text

MME behaviour changed in Rel-12: it uses Load Information for GW selection, runs a mobile reachable timer based on PSM Active Time, handles SIPTO relocation, and registers for SMS in MME.

  • “If MME has allocated an Active Time to the UE, then the MME starts the mobile reachable timer with the value of Active Time.” TS 23.401 v12.11.0
  • “When the MME supports the GTP-C Load Control feature, it takes into account the Load Information received from the PDN GW” TS 23.401 v12.11.0
  • “the MME shall set the mobile reachable timer to a value equal to the value of timer T3324.” TS 24.301 v12.13.0
Rel-13 1 CR

MME behaviour was extended in Rel-13, including CIoT optimisation support, active-time/reachability handling, CSG membership verification for dual connectivity, SMS without combined attach, and attach without PDN connection.

  • “If the MME indicates support of User Plane CIoT EPS optimisation then it shall also indicate support of S1-U data transfer.” TS 23.401 v13.14.0
  • “If MME has allocated an Active Time to the UE, then the MME starts the Active timer with the value of Active Time” TS 23.401 v13.14.0
  • Correction on MME overload control for CIOT TS 23.401CR3035
Rel-14 specification text

MME behaviour was extended in Rel-14: Control Plane data back-off timer handling, DCN-based load balancing and congestion control, TAI list restrictions for NB-IoT, and HASH_MME inclusion in security mode command.

  • “Under overload conditions the MME may restrict requests from UEs for data transmission via Control Plane CIoT EPS Optimisation.” TS 23.401 v14.11.0
  • “the MME shall not allocate a Tracking Area Identity list that contains both NB-IoT and WB-E-UTRAN Tracking Areas.” TS 23.401 v14.11.0
  • “if the MME initiates a security mode control procedure, the MME shall include a HASHMME IE in the SECURITY MODE COMMAND message” TS 24.301 v14.10.0
Rel-15 specification text

MME behaviour was extended in Rel-15: it signals NR access restrictions to E-UTRAN and UE, enforces the Service Gap timer with back-off timers, and supports 15 EPS bearers per UE.

  • “If the MME has an Access Restriction for NR for a UE” TS 23.401 v15.13.0
  • “The MME may enforce the Service Gap timer by rejecting connection request for MO user plane data, MO control plane data, or MO SMS” TS 23.401 v15.13.0
  • “the MME shall allocate a Tracking Area Identity list that provides homogenous support for 15 EPS bearers per UE” TS 23.401 v15.13.0
Rel-16 1 CR

MME behaviour was extended in Rel-16: it now chooses and forwards the ARPI to the eNodeB alongside the RFSP Index, and it handles NR access restrictions and eKSI-based security for 5GC interworking.

  • “the MME may provide the parameter 'Additional RRM Policy Index' (ARPI) to an eNodeB across S1.” TS 23.401 v16.14.0
  • “The MME shall store the mapped EPS NAS security context with the uplink and downlink NAS COUNT counters associated with the derived K'ASME key” TS 24.301 v16.9.0
  • MME Functionality to Control Emergency Call Bearer Support Indicator TS 23.401CR3539
Rel-17 specification text

MME behaviour was extended in Rel-17: it determines RAT type for satellite access, handles Multi-USIM paging features (IMSI offset, paging restriction), and gives Voice Service Indication in paging.

  • “a supporting MME provides an Accepted IMSI Offset value to the UE in the Attach Accept or Tracking Area Update Accept message” TS 23.401 v17.11.0
  • “The MME may accept or reject the Paging Restriction Information requested by the UE.” TS 23.401 v17.11.0
  • “WB-E-UTRAN or NB-IoT RAT types for satellite access, based on the Tracking Area indicated in the INITIAL UE MESSAGE by the eNodeB” TS 23.401 v17.11.0
Rel-18 specification text

MME behaviour was extended in Rel-18: it determines and applies unavailability period values for satellite discontinuous coverage, requests coarse location from the UE, and remaps QCI at inter-PLMN mobility.

  • “the MME shall store the determined unavailability period duration and, optionally, the start of the unavailability period, and provide them to the UE” TS 24.301 v18.9.0
  • “the UE and the MME may support reporting of Coarse Location Information (with the format defined in TS 24.301 [46]) from the UE to MME” TS 23.401 v18.8.0
  • “At inter-PLMN mobility the source MME shall provide the EPS bearer QoS parameters used in the source MME to the target MME.” TS 23.401 v18.8.0
Rel-19 specification text

Rel-19 changes MME behaviour: disaster roaming TAI list allocation restricted to disaster-condition areas, S&F satellite operation handling by the MME, and CIoT control plane overhead reduction with back-off timer handling.

  • “the MME shall only consider TAIs covering the area with the Disaster Condition.” TS 23.401 v19.6.0
  • “it shall reject the NAS procedure. In this case, the MME shall include a reject cause indicating the NAS rejection is due to Store and Forward Satellite operation.” TS 23.401 v19.6.0
  • “the MME shall deactivate all non-emergency EPS bearer contexts by initiating an EPS bearer context deactivation procedure.” TS 24.301 v19.8.0
Rel-20 specification text

MME behaviour changed in Rel-20: it now handles Inter/Intra-Country Inter-PLMN HO restrictions, may indicate emergency bearer services and IMS voice support over NB-IoT (GEO), and signals UHRR support.

  • “the MME shall neither send EPLMN IDs with a MCC corresponding to a country different to that of the UE's current TAI” TS 23.401 v20.1.0
  • “If the MME determines the PDN connection is used for IMS voice over NB-IoT(GEO) and the MME supports UHRR, the MME shall include a UHRR support Indication” TS 23.401 v20.1.0
  • “the MME may set the EMC BS bit to "emergency bearer services in S1 mode supported" in the EPS network feature support IE” TS 24.301 v20.1.0

Defining Specifications

3GPP specifications that define or reference MME, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.009 vj00 Handover Procedures in PLMNs Rel-19 read
TS 23.139 vj00 3GPP-Fixed Broadband Interworking Stage 2 Rel-19 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.251 vj00 Network Sharing Stage 2 Specification Rel-19 read
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 23.402 vj00 EPC for Non-3GPP Access (PMIP) Rel-19 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 23.839 vc00 BBF Access Interworking Architecture Study Rel-12 read
TS 23.857 vb00 EPC Node Failure and Restoration Study Rel-11 read
TS 23.896 vc00 PCC for Fixed Broadband Convergence Rel-12 read
TS 24.161 vj00 Network-Based IP Flow Mobility (NBIFOM) Rel-19 read
TS 24.171 vj00 NAS Protocol for LCS in E-UTRAN Rel-19 read
TS 24.301 vk10 EPS NAS Mobility and Session Management Rel-20 read
TS 24.801 v810 CT1 SAE NAS Aspects for EPC Rel-8 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TS 28.707 vj00 EPC NRM IRP Requirements Rel-19 read
TS 28.708 vj00 EPC NRM Integration Reference Point Information Service Rel-19 read
TS 28.709 vj00 EPC NRM IRP Solution Set Definitions Rel-19 read
TS 28.874 vj10 Study on Management Aspects of NTN Phase 2 Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.118 vj10 MME-VLR Interface for CS Fallback & SMS Rel-19 read
TS 29.168 vj00 SBc-AP Protocol Specification Rel-19 read
TS 29.171 vj10 LCS-AP between MME and E-SMLC (SLs) Rel-19 read
TS 29.172 vj00 EPC LCS Protocol (ELP) specification Rel-19 read
TS 29.272 vj60 MME and SGSN Diameter interfaces to HSS/CSS/EIR Rel-19 read
TS 29.276 vj00 EPS S101/S121/S103 Interfaces Stage 3 Rel-19 read
TS 29.277 vj00 S102 Interface Protocol Specification Rel-19 read
TS 29.281 vj20 GTPv1-U Protocol Specification Rel-19 read
TS 29.507 vk10 Access and Mobility Policy Control Rel-20 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.673 vk00 3GPP TS 29673 vk00: Nucmf Service Based Interface Rel-20 read
TS 29.674 vj00 UE Radio Capability Management Protocol (URCMP) Rel-19 read
TS 29.805 v800 IWF for MAP-Diameter Interworking Rel-8 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read
TS 31.104 vj00 HPSIM Application Specification Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.273 vj00 MBMS Charging Management Rel-19 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.426 vj00 EPC Performance Measurements Specification Rel-19 read
TS 32.582 vj00 HNB Management Information Model for Type 1 Interface Rel-19 read
TS 32.584 vj00 HNB OAM&P XML Definitions for Type 1 Interface Rel-19 read
TS 32.592 vj00 HeNB OAM&P Information Model Rel-19 read
TS 32.593 vj00 HeNB OAM&P Procedure Flows for Type 1 Interface Rel-19 read
TS 32.594 vj00 Data definitions for HeNB to HeMS Type 1 interface Rel-19 read
TS 32.751 vb00 EPC NRM IRP Requirements Rel-11 read
TS 32.752 vb01 EPC Network Resource Model Information Service Rel-11 read
TS 32.753 v920 EPC NRM IRP CORBA Solution Set Rel-9 read
TS 32.756 vb00 EPC NRM IRP Solution Set Definitions Rel-11 read
TS 32.816 v800 E-UTRAN and EPC Management Principles Rel-8 read
TS 32.820 v801 Study on Evolved 3GPP Charging Architecture Rel-8 read
TS 32.821 v900 SON OAM for Home NodeB (LTE/UMTS) Rel-9 read
TS 32.833 vb00 Fixed-Mobile Convergence Management Study Rel-11 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.320 vj00 H(e)NB Subsystem Security Architecture Rel-19 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.402 vj00 Security for non-3GPP access to EPS Rel-19 read
TS 33.820 v830 H(e)NB Security Threats and Countermeasures Rel-8 read
TS 33.821 v900 LTE/SAE Security Threat Analysis and Countermeasures Rel-9 read
TS 33.835 vg10 Study on authentication and key management for apps Rel-16 read
TS 33.859 vb10 UTRAN Key Hierarchy Study Rel-11 read
TS 33.863 ve20 Security for Battery-Efficient IoT Device to Enterprise Rel-14 read
TR 33.916 vk00 Security Assurance Methodology (SECAM) Evaluation Process Rel-20 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19 read
TS 36.410 vj00 S1 Interface: General Aspects and Principles Rel-19 read
TS 36.412 vj00 S1 Signalling Transport Specification Rel-19 read
TS 36.413 vj20 S1 Application Protocol (S1AP) for E-UTRAN Rel-19 read
TS 36.414 vj00 S1 Interface User Plane Transport Rel-19 read
TS 36.423 vj10 X2 Application Protocol (X2AP) Specification Rel-19 read
TS 36.424 vj00 X2 Interface User Plane Transport Protocols Rel-19 read
TS 36.440 vj00 E-UTRAN MBMS Architecture Description Rel-19 read
TS 36.442 vj00 Signalling transport for M2 and M3 interfaces Rel-19 read
TS 36.444 vj00 M3AP Protocol Specification for M3 Interface Rel-19 read
TS 36.455 vj00 LTE Positioning Protocol Annex (LPPa) Rel-19 read
TS 36.456 vj00 SLm Interface Introduction Rel-19 read
TS 36.458 vj00 SLm Interface Signalling Transport Rel-19 read
TS 36.876 vd00 LTE Small Cell High-Layer Enhancements Rel-13 read
TS 36.896 ve00 Study on Flexible eNB-ID and Cell-ID in E-UTRAN Rel-14 read
TS 43.129 vj00 PS Handover in GERAN A/Gb and GAN Modes Rel-19 read
TS 44.060 vj00 GERAN RLC/MAC Protocol Specification Rel-19 read
TS 48.018 vj00 BSS-SGSN Interface for GPRS Control Rel-19 read