Description
A Home Node B (HNB) is a low-power, user-deployed cellular base station defined by 3GPP for UMTS (WCDMA/HSPA) networks. It is a type of femtocell designed for residential or small business environments. Physically, it is a small device that plugs into a user's existing broadband internet connection (like DSL or cable). The HNB creates a licensed 3G radio cell, typically covering an area of a few hundred to a few thousand square feet, allowing standard 3G User Equipment (UE) to connect to the mobile network through this localized access point.
Architecturally, the HNB contains the essential functions of a Node B (the UMTS base station) and a simplified Radio Network Controller (RNC). It handles radio transmission/reception, modulation/demodulation, channel coding, and power control. For network connectivity, it establishes a secure IPsec tunnel over the public internet to a dedicated gateway in the operator's network, known as the HNB Gateway (HNB-GW). This tunnel carries both user plane traffic (voice and data) and control plane signaling (RANAP over Iu-h interface). The HNB-GW then interfaces with the core network's Mobile Switching Center (MSC) for circuit-switched services and Serving GPRS Support Node (SGSN) for packet-switched services, making the femtocell appear as a standard RNC to the core.
The HNB operates with sophisticated self-configuration and self-optimization capabilities. It scans the radio environment to select a suitable UMTS carrier and scrambling code, minimizing interference with the macro network and neighboring HNBs. It also implements access control, typically allowing only a closed subscriber group (CSG) – a pre-defined list of subscribers – to connect, turning it into a 'femtozone' for the home or business. Management and provisioning are handled via a separate interface to an HNB Management System (HMS), which is part of the operator's network management infrastructure.
Purpose & Motivation
The HNB was created to solve the persistent problem of poor indoor cellular coverage, particularly for 3G services which operate at higher frequencies more susceptible to building penetration loss. It allows operators to extend high-quality voice and data coverage into homes and offices without the massive capital expenditure of deploying additional macro cell sites. It offloads traffic from the macro network, improving overall capacity and user experience.
Prior to femtocells, solutions for indoor coverage included picocells (operator-installed) or Wi-Fi, but these had limitations. Picocells were expensive to deploy and manage at scale for residential use. Wi-Fi required dual-mode handsets and did not offer seamless cellular service continuity. The HNB concept leveraged the user's own broadband backhaul, dramatically reducing deployment costs for the operator while providing a transparent cellular experience for the subscriber using their standard 3G phone.
The introduction of HNB in 3GPP Release 8 was motivated by the commercial need to improve 3G service penetration and compete with fixed-line voice services. It addressed operator concerns about backhaul security, network integration, interference management, and scalable management for millions of deployed units. The HNB ecosystem enabled new business models, such as 'home zone' tariffs, and laid the groundwork for future small cell technologies in 4G and 5G.
Key Features
- Low-power UMTS/WCDMA/HSPA radio access for indoor coverage
- Utilizes consumer broadband (DSL, cable, fiber) for backhaul via secure IPsec tunnels
- Supports Closed Subscriber Group (CSG) for restricted access
- Implements autonomous radio configuration and interference management
- Integrates with operator core network via the standardized Iu-h interface to an HNB-GW
- Remote management and provisioning via TR-069 or similar protocols
Evolution Across Releases
Initial introduction of the HNB architecture. Defined the HNB as a femtocell for UMTS, specifying the Iu-h interface to the new HNB Gateway (HNB-GW), the HNB Management System (HMS), and core network integration for both CS and PS domains. Established foundational procedures for discovery, registration, and CSG management.
Defining Specifications
| Specification | Title |
|---|---|
| TS 22.220 | 3GPP TS 22.220 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.830 | 3GPP TS 23.830 |
| TS 24.008 | 3GPP TS 24.008 |
| TS 24.285 | 3GPP TS 24.285 |
| TS 25.367 | 3GPP TS 25.367 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 25.444 | 3GPP TS 25.444 |
| TS 25.467 | 3GPP TS 25.467 |
| TS 25.468 | 3GPP TS 25.468 |
| TS 25.469 | 3GPP TS 25.469 |
| TS 25.470 | 3GPP TS 25.470 |
| TS 25.471 | 3GPP TS 25.471 |
| TS 25.820 | 3GPP TS 25.820 |
| TS 25.866 | 3GPP TS 25.866 |
| TS 25.967 | 3GPP TS 25.967 |
| TS 28.671 | 3GPP TS 28.671 |
| TS 28.672 | 3GPP TS 28.672 |
| TS 28.673 | 3GPP TS 28.673 |
| TS 28.702 | 3GPP TS 28.702 |
| TS 31.102 | 3GPP TR 31.102 |
| TS 31.104 | 3GPP TR 31.104 |
| TS 31.121 | 3GPP TR 31.121 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.571 | 3GPP TR 32.571 |
| TS 32.572 | 3GPP TR 32.572 |
| TS 32.581 | 3GPP TR 32.581 |
| TS 32.582 | 3GPP TR 32.582 |
| TS 32.583 | 3GPP TR 32.583 |
| TS 32.584 | 3GPP TR 32.584 |
| TS 32.592 | 3GPP TR 32.592 |
| TS 32.593 | 3GPP TR 32.593 |
| TS 32.594 | 3GPP TR 32.594 |
| TS 32.632 | 3GPP TR 32.632 |
| TS 32.633 | 3GPP TR 32.633 |
| TS 32.635 | 3GPP TR 32.635 |
| TS 32.771 | 3GPP TR 32.771 |
| TS 32.772 | 3GPP TR 32.772 |
| TS 32.821 | 3GPP TR 32.821 |
| TS 33.106 | 3GPP TR 33.106 |
| TS 33.107 | 3GPP TR 33.107 |
| TS 33.126 | 3GPP TR 33.126 |
| TS 33.320 | 3GPP TR 33.320 |
| TS 33.545 | 3GPP TR 33.545 |
| TS 33.820 | 3GPP TR 33.820 |
| TS 36.921 | 3GPP TR 36.921 |
| TS 36.922 | 3GPP TR 36.922 |