External Serving Gateway Function (Interface ExternalServingGWFunction)

Description

The Interface ExternalServingGWFunction is a managed object defined in the 3GPP Generic Network Resources NRM, specifically as a GenericNetworkResourcesNRMDefs::ManagedFunction. It represents a Serving Gateway (SGW) 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 user-plane data forwarding and mobility anchoring. The SGW is a key element of the Evolved Packet Core (EPC), responsible for routing and forwarding user data packets, acting as the mobility anchor for inter-eNodeB handovers, and serving as the gateway to the PDN Gateway (PGW) for external data networks.

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 ExternalServingGWFunction' indicates that this is an interface-level definition within the IRP framework, specifying the attributes, operations, and notifications for managing external SGW functions. As a ManagedFunction, it inherits common managed object behaviour such as state management, containment, and notification support.

Architecturally, ExternalServingGWFunction resides in the management plane and provides a standardized way to model external SGWs that the managed network's elements (e.g., MME, eNodeB, PGW) need to reference. Key attributes typically include the SGW's identity (such as the FQDN or IP address used for S1-U, S5/S8, and S11 interfaces), 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 SGWs, which is essential for roaming, inter-PLMN handover, and S5/S8 interface management.

In operation, when a UE moves from one network to another, the source and target SGWs may need to exchange user-plane data or signalling over the S5/S8 interface (inter-SGW) or S1-U interface (eNodeB-SGW). The ExternalServingGWFunction MO provides the management representation of the peer SGW, enabling the operator to configure roaming agreements, manage inter-PLMN user-plane policies, and troubleshoot inter-operator data forwarding issues. It also supports SON and self-configuration functions, where the management system can automatically discover and model external SGWs 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 user-plane management grew in importance. It has been maintained across Releases 10 through 19, reflecting the continued relevance of EPC and SGW functions even in the 5G era, where interworking between 5G core (UPF) and EPC (SGW) remains necessary. The definition text has remained stable, indicating a mature and stable information model element.

Purpose & Motivation

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

By defining a standardized representation of external SGW functions in the NRM, 3GPP enabled interoperable management interfaces. An operator can now use a single, standardized model to describe all relevant SGWs — internal and external — across different PLMNs and administrative domains. This is essential for roaming, where the visited network must know the home network's SGW identity and capabilities, and for inter-PLMN handover, where the source and target SGWs must exchange user-plane 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 user-plane management remains a critical operational requirement, and that standardized management of external SGWs continues to be necessary even as networks evolve toward 5G.