Home Node B Application Part

Description

The Home Node B Application Part (HNBAP) is a critical control plane protocol defined within the 3GPP Iuh interface specification. It operates between the Home Node B (HNB), which is a consumer-grade femtocell, and the HNB Gateway (HNB-GW), which aggregates traffic from multiple HNBs and connects them to the core network. HNBAP is responsible for the management and control functions necessary to bring an HNB into service and maintain its operation. It is analogous to the Node B Application Part (NBAP) used in macrocell networks but is adapted for the specific requirements of the femtocell architecture, including security and scalability for potentially millions of deployed units.

The protocol operates over Stream Control Transmission Protocol (SCTP) associations, providing reliable message delivery. Its primary functions are divided into two main categories: HNB Registration and HNB Configuration. The Registration procedures allow an HNB to authenticate itself with the HNB-GW and the core network, verifying its identity, location, and authorized service area. This process involves mutual authentication and the establishment of security contexts. The Configuration procedures are used to manage the HNB's operational parameters, such as radio frequency (RF) settings, neighbor cell lists, and system information blocks (SIBs). The HNB-GW uses HNBAP to push configuration updates and control the HNB's radio resource management to minimize interference with the macro network.

Key architectural components involved with HNBAP include the HNB itself, the HNB-GW, and the Security Gateway (SeGW). The SeGW establishes an IPsec tunnel with the HNB for secure transport before any HNBAP signaling occurs. HNBAP messages are then carried within this secure tunnel. The protocol defines numerous elementary procedures (EPs) for specific tasks, such as HNB Register, HNB De-register, HNB Configuration Update, and Error Indication. It also handles UE registration procedures for user equipment connecting through the HNB. HNBAP's role is foundational; it enables the HNB subsystem to appear as a standard Radio Network Controller (RNC) from the core network's perspective, thereby allowing reuse of existing core network interfaces and functions for femtocell traffic.

Purpose & Motivation

HNBAP was created to address the specific control and management challenges introduced by the mass deployment of femtocells (Home Node Bs) in 3GPP Release 8. Prior to femtocells, cellular networks were built solely on operator-deployed macrocell infrastructure. The introduction of consumer-deployed small cells required a new architecture that could scale to millions of units, ensure robust security to prevent network intrusion, and manage radio resources to avoid interference with the existing macro network. Existing macrocell control protocols like NBAP were not designed for this insecure, residential IP-backhaul environment.

The primary problem HNBAP solves is the secure and scalable integration of untrusted, consumer-owned access points into the trusted operator network. It provides the standardized signaling necessary for an HNB to bootstrap itself, authenticate its location and identity, receive its operating configuration from the network, and manage the lifecycle of connected UEs. This allows operators to offer improved indoor coverage and capacity using customer-premises equipment without compromising network security or stability. The protocol's design motivations included enabling plug-and-play installation for consumers, centralized control for operators, and efficient use of licensed spectrum by managing femtocell power levels and frequencies through network-controlled configuration.

Key Features

• Manages HNB registration and authentication with the core network
• Transports configuration data (RF parameters, neighbor lists) from HNB-GW to HNB
• Controls the setup and release of signaling connections for UEs
• Supports error reporting and fault management procedures
• Operates over SCTP for reliable transport within a secure IPsec tunnel
• Defines procedures for HNB deregistration and configuration updates

Evolution Across Releases

Defining Specifications