Home eNodeB Profile Interface

Description

The Interface HeNBProfile is a managed object class defined within the GenericNetworkResourcesNRMDefs::ManagedFunction hierarchy of the 3GPP Generic Network Resource Model (NRM). It represents a profile—a collection of configuration parameters—that can be applied to one or more Home eNodeBs (HeNBs). Profiles are a common management concept that allows operators to define a template of settings (such as radio parameters, access control lists, or mobility settings) and then associate that template with multiple network elements. The HeNBProfile serves this purpose for the Home eNodeB Subsystem (HeNS), enabling efficient bulk configuration and reducing the risk of inconsistencies across a large number of femtocells.

The managed function is specified in 3GPP TS 28.676, which defines the Home eNodeB Subsystem NRM, and is referenced in TS 32.786, the Home eNodeB Subsystem management IRP. In the NRM, the HeNBProfile inherits from the ManagedFunction class and is typically contained within a SubNetwork or a ManagedElement that represents a management system or a profile repository. The profile object contains attributes that define the actual configuration values, as well as relationships to the HeNBFunction objects that reference it. When a HeNB is provisioned, the management system can assign a profile to it, and the HeNB's configuration is derived from that profile. This indirection allows operators to update many HeNBs at once by modifying the profile, rather than reconfiguring each HeNB individually.

Architecturally, the HeNBProfile is part of the management plane, not the user or control plane. It does not directly participate in call processing or data forwarding. Instead, it is used by the Element Manager (EM) or Network Manager (NM) to push configuration to HeNBs via the HeNB Management System (HeMS), which is defined in the Broadband Forum's TR-069 family of specifications and adapted by 3GPP for femtocell management. The HeNBProfile object in the 3GPP NRM is often mapped to a corresponding profile in the HeMS data model, ensuring end-to-end consistency from the OSS down to the HeNB.

The profile concept is particularly important for self-organizing networks (SON). With SON, HeNBs can automatically configure themselves based on profiles that include policies for radio parameter selection, neighbour relations, and interference management. The HeNBProfile managed object provides a standardized way to define these policies and to monitor their application. It may also include attributes for closed subscriber group (CSG) configuration, allowing operators to define which users are allowed to access a particular HeNB or group of HeNBs.

Since its introduction in Release 10, the HeNBProfile has been a stable part of the 3GPP management specifications. Its definition has not changed in the quoted text across releases, indicating that the fundamental concept of a profile-based configuration for HeNBs has remained consistent. This stability is beneficial for multi-vendor interoperability, as it ensures that management systems from different vendors can interpret and apply HeNB profiles in a standardized manner.

Purpose & Motivation

The HeNBProfile managed object exists to solve the operational challenge of configuring and maintaining a large number of Home eNodeBs in a consistent and scalable way. In early femtocell deployments, each HeNB had to be configured individually, which was impractical for deployments involving thousands or millions of devices. Manual configuration was error-prone, time-consuming, and expensive. The profile concept addresses this by allowing operators to define a set of configuration parameters once and apply them to many HeNBs, ensuring uniformity and reducing operational costs.

Moreover, profiles support the dynamic nature of small cell deployments. HeNBs can be installed, moved, or replaced frequently, and they need to be configured quickly and correctly. With a profile-based approach, a new HeNB can automatically retrieve its configuration from the management system by referencing a profile, enabling plug-and-play operation. This is essential for consumer femtocells, which are often installed by non-technical users.

The HeNBProfile also facilitates policy-based management. Operators can define different profiles for different types of deployments—for example, a profile for residential HeNBs with open access, another for enterprise HeNBs with closed subscriber groups, and another for public hotspots with specific QoS settings. By associating HeNBs with the appropriate profile, operators can enforce policies consistently across the network. The standardization of the HeNBProfile in 3GPP ensures that these capabilities are available in a multi-vendor environment, which was not possible with proprietary solutions.