External Mobility Management Entity Function (Interface ExternalMMEFunction)

Description

The Interface ExternalMMEFunction is a managed object defined in the 3GPP Generic Network Resources NRM, specifically as a GenericNetworkResourcesNRMDefs::ManagedFunction. It represents a Mobility Management Entity (MME) that belongs to another network domain — for example, another PLMN, another operator, or a separate administrative domain — but which interacts with the managed network for mobility management purposes. The MME is the key control-plane element of the Evolved Packet Core (EPC), responsible for UE attach, authentication, bearer management, and tracking area management. When a UE roams or hands over between networks, the serving network must communicate with the external MME to exchange context and manage sessions.

The MO is defined in 3GPP TS 28.709 (Evolved Packet Core Network Resources NRM) and its associated IRP is described in TS 32.756 (Evolved Packet Core Network Resources IRP). The naming convention 'Interface ExternalMMEFunction' indicates that this is an interface-level definition within the IRP framework, specifying the attributes, operations, and notifications for managing external MME functions. As a ManagedFunction, it inherits common managed object behaviour such as state management, containment, and notification support.

Architecturally, ExternalMMEFunction resides in the management plane and provides a standardized way to model external MMEs that the managed network's elements (e.g., eNodeB, MME, SGW, PGW) need to reference. Key attributes typically include the MME's identity (such as the GUMMEI — Globally Unique MME Identifier, comprising MCC, MNC, and MME Identifier), the PLMN it belongs to, and possibly its supported features or interfaces. These attributes allow the management system to configure and maintain relationships between internal and external MMEs, which is essential for roaming, inter-PLMN handover, and S1-flex configurations.

In operation, when a UE moves from one network to another, the source and target MMEs exchange signalling over the S10 interface (inter-MME) or S6a interface (MME-HSS). The ExternalMMEFunction MO provides the management representation of the peer MME, enabling the operator to configure roaming agreements, manage inter-PLMN mobility policies, and troubleshoot inter-operator handover issues. It also supports SON and self-configuration functions, where the management system can automatically discover and model external MMEs based on network signalling and O&M data.

The term was introduced in Release 10, as LTE and EPC deployments became widespread and inter-operator mobility management grew in importance. It has been maintained across Releases 10 through 19, reflecting the continued relevance of EPC and MME functions even in the 5G era, where interworking between 5G core (AMF) and EPC (MME) remains necessary. The definition text has remained stable, indicating a mature and stable information model element.

Purpose & Motivation

The ExternalMMEFunction managed object exists to address the need for standardized management of external MMEs in multi-operator and multi-PLMN environments. In early LTE deployments, each vendor's management system used proprietary models to represent external MMEs, making it difficult to automate roaming configuration, inter-PLMN handover, and network integration. This lack of standardization led to operational complexity and increased risk of misconfiguration.

By defining a standardized representation of external MME functions in the NRM, 3GPP enabled interoperable management interfaces. An operator can now use a single, standardized model to describe all relevant MMEs — internal and external — across different PLMNs and administrative domains. This is essential for roaming, where the visited network must know the home network's MME identity and capabilities, and for inter-PLMN handover, where the source and target MMEs must exchange context.

The MO also supports regulatory and operational use cases such as roaming agreement management, inter-operator troubleshooting, and automated network configuration. Its long-standing presence from Rel-10 to Rel-19 demonstrates that inter-operator mobility management remains a critical operational requirement, and that standardized management of external MMEs continues to be necessary even as networks evolve toward 5G.