Home eNodeB Gateway Function Interface

Description

The Interface HeNBGWFunction is a managed object class defined within the GenericNetworkResourcesNRMDefs::ManagedFunction hierarchy of the 3GPP Generic Network Resource Model (NRM). It represents the Home eNodeB Gateway (HeNB GW), a network element introduced to support femtocell deployments in LTE and LTE-Advanced networks. The HeNB GW sits between a potentially very large number of Home eNodeBs (HeNBs) and the Evolved Packet Core (EPC), acting as a concentrator and a single point of contact for the core network. From a management perspective, the HeNBGWFunction object exposes attributes, operations, and notifications that allow an Operations Support System (OSS) or Element Manager (EM) to configure, monitor, and control the gateway.

The managed function is defined in 3GPP TS 28.676, which specifies the Home eNodeB Subsystem (HeNS) Network Resource Model, and referenced in TS 32.786, which covers the Home eNodeB Subsystem management integration reference point (IRP). The NRM follows the generic NRM framework of TS 28.622, where managed functions inherit from the ManagedFunction class and are contained within a SubNetwork or ManagedElement. The HeNBGWFunction object therefore participates in the standard configuration management (CM) and fault management (FM) workflows: it can be created, modified, and deleted by the network manager, and it can emit alarms and notifications related to its operational state.

Architecturally, the HeNB GW provides several critical functions. First, it aggregates the S1 interface from many HeNBs into a smaller number of S1 connections toward the Mobility Management Entity (MME) and Serving Gateway (S-GW). This aggregation reduces the signalling load on the core network and simplifies scaling. Second, it supports the S1-flex concept, allowing a HeNB to be connected to multiple MMEs through the gateway. Third, it can perform closed subscriber group (CSG) related functions, such as access control and paging optimisation, in coordination with the HeNB and the core network. The HeNBGWFunction managed object models the gateway's identity, its supported capabilities, and its relationships to the HeNBs it serves and the core network nodes it connects to.

In terms of the management model, the HeNBGWFunction is typically contained within a ManagedElement that represents the physical or logical HeNB GW. It has associations with other managed objects, such as the HeNBFunction objects representing individual Home eNodeBs, and with core network managed objects representing the MME and S-GW. The object's attributes may include the gateway's identifier, its operational and administrative states, and configuration parameters for S1 aggregation and CSG handling. These attributes are accessible via the Itf-N interface (northbound interface) using protocols such as NETCONF or CORBA, depending on the IRP solution set.

The HeNBGWFunction has been part of the 3GPP management specifications since Release 10, when femtocell support was enhanced in LTE. Its definition has remained stable across releases, reflecting the maturity of the HeNB architecture. Although the term is specific to the management domain, it is closely tied to the radio access network and core network interfaces that the HeNB GW implements, making it a bridge between management and operational aspects of small cell deployments.

Purpose & Motivation

The HeNBGWFunction managed object exists to provide a standardized, vendor-independent way to manage Home eNodeB Gateways within 3GPP networks. Before its introduction, femtocell deployments faced significant management challenges because each vendor implemented proprietary management interfaces for their gateways. This made multi-vendor integration difficult and increased operational costs for mobile network operators. The HeNB GW itself was introduced to solve the scalability problem of connecting potentially millions of residential and enterprise femtocells directly to the core network, which would overwhelm the MME and S-GW with signalling and user plane traffic.

By defining the HeNBGWFunction as a managed function in the generic NRM, 3GPP enabled operators to configure, monitor, and troubleshoot HeNB gateways using standardized operations. This includes the ability to set parameters for S1 aggregation, manage CSG access lists, and receive alarms when the gateway experiences failures or performance degradation. The standardized model also supports automated provisioning and integration with higher-level management systems, such as a Network Management System (NMS) or an OSS, reducing manual effort and the risk of configuration errors.

The creation of this managed function was motivated by the need to support the massive scale of small cell deployments envisioned for LTE and beyond. Unlike macro base stations, which are relatively few and managed individually, HeNBs are deployed in large numbers and often in unmanaged environments. The HeNB GW abstracts this complexity from the core network, and the HeNBGWFunction managed object abstracts the gateway's management from the OSS. Together, they make large-scale femtocell deployments operationally feasible.