MME

NPC MME Network Product Class

Core Network →
Introduced in Rel-5 Also in: Radio Access Network, Management, Security

MME is a 3GPP network product class that categorizes Mobility Management Entities by their performance benchmarks, feature sets, and capacity for consistent operator evaluation and procurement.

Category
Core Network
Introduced
Rel-5
Where
Core Network › 5G Core
Also touches
3 segments
Specifications
85 specs
MME Description Purpose Related Classification Detected Changes Specifications

Description

The NPC MME (Network Product Class for the Mobility Management Entity) is a detailed specification within 3GPP that categorizes MME implementations according to a standardized set of performance and capability criteria. The MME itself is a core network node in the Evolved Packet Core (EPC) for LTE and the 5G Core (5GC) where it evolved into the Access and Mobility Management Function (AMF). The NPC framework, however, focuses on defining what constitutes a particular 'class' of MME product in terms of its capacity to handle subscribers, sessions, signaling transactions, and supported features.

Architecturally, the NPC definitions do not alter the MME's standard interfaces or protocols but provide a rigorous testing and classification methodology. An MME's class is determined by its performance against benchmarks defined in specifications like TS 36.413 (S1-AP) and TS 29.272 (S6a). Key metrics include maximum supported number of attached subscribers, busy hour call attempts (BHCA), packet data network (PDN) connections, tracking area updates (TAU) per second, and handover rates. The classification also mandates support for specific 3GPP features, such as emergency services, lawful interception, and various mobility and session management procedures.

How it works is that vendors design their MME hardware or software to target a specific NPC (e.g., a high-capacity class). They then perform conformance and load tests, often referencing the test suites in specifications like TS 36.523, to verify the product meets all the requirements for that class. This provides network operators with an apples-to-apples comparison when issuing requests for proposal (RFPs). The NPC ensures that an MME advertised as a certain class will deliver a guaranteed level of performance and functionality, which is critical for network dimensioning, capacity planning, and ensuring service level agreements (SLAs). Its role is therefore one of standardization and quality assurance in the network equipment market, ensuring interoperability and predictable performance across different vendor implementations.

Purpose & Motivation

The purpose of defining Network Product Classes for the MME was to bring clarity, fairness, and reliability to the telecommunications equipment procurement process. Before such classification, vendors could use proprietary or non-standard metrics to describe the capacity of their MME nodes, making direct comparison difficult for operators. This led to risks of under-provisioning (if a product did not perform as expected) or inefficient capital expenditure (if over-specified products were purchased).

The creation of the MME NPC, with roots in earlier work on network product classes for other nodes, was motivated by the commercial rollout of LTE (EPS) starting in 3GPP Release 8. As a brand new, all-IP core network, operators needed confidence that the critical signaling node (the MME) from any vendor could handle the projected subscriber growth and signaling load. The NPC framework solved this by providing a common language and a rigorous set of benchmarks defined by the standards body itself.

It addresses the fundamental problem of vendor lock-in and performance ambiguity. By standardizing the performance classes, it fosters a more competitive multi-vendor environment, as operators can mix and match nodes from different suppliers with confidence in their interworking and capacity. Furthermore, it aids in the evolution of networks, as the NPC definitions are updated across releases to include new features (e.g., support for VoLTE, IoT devices, network slicing precursors), ensuring that product classifications remain relevant to contemporary service demands. It is a key enabler for predictable network scaling and cost-effective evolution from 4G to 5G.

Architecture

In the Network Map

Evolution Lineage

Classification

Part ofEPC

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (49 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 11 changes

In Release 15, several specific enhancements were introduced for the MME function, including support for a dual registration indicator and refined handling for unsupported APNs. The release also defined procedures for storing CE Mode B UE capability, requesting UE Radio Capabilities, and aligning with eNodeB procedures for CP Relocation Indication. Furthermore, it extended the usage of HASH_MME and clarified MME behaviors for specific Diameter error responses and rate control timing.

  • Dual registration supported indicator from MME TS 23.401CR3365
  • MME handling of unsupported APN TS 23.401CR3392
  • Alignment CR for storing CE mode B UE capability in MME TS 23.401CR3378
  • MME request for UE Radio Capabilities TS 23.401CR3440
  • Storing CE Mode B in MME TS 24.301CR2953
  • Starting time of Serving PLMN rate control at the MME TS 24.301CR3146

+ 5 more changes

Rel-16 7 changes

In Release 16, the MME saw enhancements for emergency services, secondary RAT data reporting clarification, and S1-U data capability handling corrections. It also received updates for security procedures during 5GC interworking in idle mode and refinements to UE status information usage. Furthermore, the release included editorial clarifications on inter-PLMN mobility and the formalization of supported features for combined MME/SGSN network nodes.

  • MME Functionality to Control Emergency Call Bearer Support Indicator TS 23.401CR3539
  • Clarification of MME handling for secondary RAT data reporting TS 23.401CR3581
  • Correction on S1-U data capability indication and handling in the MME TS 24.301CR3190
  • MME not using EMM registration status in UE status IE TS 24.301CR3402
  • Correction on MME security handling for 5GC interworking in idle mode TS 24.301CR3409
  • Removal of Editor's note on inter PLMN mobility under same MME TS 24.301CR3414

+ 1 more changes

Rel-17 7 changes

In Release 17, the MME function was enhanced with several specific updates. These included ensuring the MME is used in the UE's located country for IoT NTN, applying ARP per local configuration, and correcting EPS bearer QoS handling. Other additions were support for an Alternative IMSI in the MM context, clarifications on UE radio capability handling during paging, the ability to send forbidden TAIs to the UE, and defined procedures for retransmitting TAU requests during certain inter-system changes.

  • IoT NTN: Ensure use of MME in the country where UE is located TS 23.401CR3668
  • ARP PL applied by MME per local configruation TS 23.401CR3648
  • Correction to MME handling EPS bearer QoS TS 23.401CR3670
  • Adding Alternative IMSI to the MM Context in the MME TS 23.401CR3677
  • Clarification on handling of UE radio capability for paging when MME changes TS 23.401CR3687
  • MME sends forbidden TAI(s) to UE TS 23.401CR3708

+ 1 more changes

Rel-18 7 changes

In Release 18, the MME function was enhanced with specific capabilities for reporting Coarse UE Location Information to the eNB for NB-IoT UEs, including necessary S1AP impacts. Furthermore, it introduced clarifications and handling procedures for ePCO support during inter-MME handovers and for transferred PDNs when moving to an MME that does not support ePCO. The release also defined mechanisms for Lawful Interception identifier availability during Inter-MME and MME-5GS handovers, and refined timer adjustment logic based on UP duration and start time.

  • Identifier availability for Lawful Interception during Inter-MME/ MME-5GS handover TS 23.401CR3720
  • Applying MME determined unavailability values TS 23.401CR3814
  • When MME does not support ePCO for non-IP/ethernet/UAS services TS 24.301CR3914
  • Clarification that the MME adjusts different timers based on UP duration and start time. TS 24.301CR3997
  • ePCO support handling for a transferred PDN when change to an MME not supporting ePCO TS 24.301CR4041
  • Coarse UE Location Information Reporting from MME to eNB for NB-IoT UEs TS 36.300CR1415

+ 1 more changes

Rel-19 17 changes

In Release 19, the primary new feature for the MME was the introduction of a split MME architecture, which required new procedures like Attach with PDN connection and Path Switch Requests to resume UE connections specifically for this design. The release also included significant clarifications and enhancements for handling Disaster Roaming Services and satellite operations, including MME behavior when a disaster condition ends and reject handling for UEs not supporting satellite functionality. Additionally, it provided corrections and clarifications on existing procedures such as SGs LAU updates, MME/SGSN registration for SMS, and the use of the S&F Monitoring List within the new split architecture.

  • Introduction to Split MME architecture TS 23.401CR3800
  • Support of Attach with PDN connection for split MME architecture TS 23.401CR3854
  • MME behaviour when the disaster condition has ended and the UE maintains a PDN connection for emergency bearer services TS 24.301CR4572
  • Clarify MME and HSS behavior on authentication in disaster roaming service TS 29.272CR0888
  • Clarification related to terminology and on MME providing list in detach procedure TS 23.401CR3897
  • Clarification that the S&F Wait Timer may need to take into account the time to synchronize the UE context between MME-ground and MME-onboard(s) TS 23.401CR3928

+ 11 more changes

Explore further

Broader topics and technologies where MME plays a role.

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

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.