Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

HNB

Home Node B

Radio Access Network →

HNB is a customer-premises equipment that provides 3G UMTS radio coverage for a small area and connects to the operator's core network via a residential broadband connection.

Introduced
Rel-8
Where
Management
Specifications
47 specs
Also in
Radio Access Network, Security, Core Network
HNB Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define HNB. Each summary describes the whole specification, not only this term.

TS 22.220Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 22.220: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 22.220 →
TS 23.060Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.060 →

Technology family

Base stations and RAN nodes · Radio Access Network

  1. Phase 1 BSC, BSS, BTS
  2. R99 Node B, RNC, RNS
  3. Rel-8 eNB, HeNB, HNB, HNB-GW
  4. Rel-10 DeNB, HeNB-GW, RN
  5. Rel-15 en-gNB, gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, ng-eNB
  6. Rel-16 IAB-donor, IAB-DU, IAB-MT, IAB-node
  7. Rel-18 Mobile IAB-node
  • HNB builds on Node B
    “The Home NodeB Subsystem (HNS) consists of a Home NodeB (HNB), a Home NodeB Gateway (HNB-GW) and optionally a Local GW (L-GW).” TS 23.002

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 5 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-8 introduced

Rel-8 first specifies the HNB architecture, the HNBAP registration and de-registration procedures over Iuh, and the HNB auto-configuration and management flows with the HMS.

  • “The present document specifies the UTRAN architecture for 3G Home NodeB (HNB).” TS 25.467 v8.6.0
  • “The HNB shall initiate this procedure by sending a HNB REGISTER REQUEST message whenever it needs to commence operations and requiring service from the HNB-GW.” TS 25.469 v8.5.0
  • “The HNB establishes a LAN connectivity to the Internet when it is initially powered up.” TS 32.583 v8.2.0
Rel-9 specification text

HNB registration, access control and CSG membership handling changed: HNB-GW may do membership verification, HNB provides CSG-ID and access mode in registration, and HNB handles membership changes and hybrid cells.

  • “If the HNB is CSG capable and operates in a Closed access mode as defined in [15], then it shall provide the CSG-ID IE” TS 25.469 v9.3.0
  • “If the UE is served by a Hybrid cell, the HNB may use the new membership information to perform differentiated treatment” TS 25.467 v9.6.0
  • “If the HNB operates in a Hybrid access mode as defined in [15], then it shall provide the CSG-ID IE and HNB Cell Access Mode IE” TS 25.469 v9.3.0
Rel-10 specification text

HNB behaviour was extended in Rel-10: it uses the Iuh secure interface for Gn/S5 when an L-GW is present, and gains Iurh connectivity, HNB-to-HNB relocation and configuration transfer procedures.

  • “If the L-GW is present within the HNB, the HNB shall use for Gn/S5 connectivity the same secure interface established by the HNB for Iuh signalling” TS 25.467 v10.6.0
  • “If the HNB supports direct Iurh connectivity it shall provide the Iurh signalling TNL Address IE to the HNB-GW within the HNB REGISTER REQUEST message.” TS 25.469 v10.4.0
  • “The HNB initiates this procedure by sending an HNB CONFIGURATION TRANSFER REQUEST message to the HNB-GW in order to retrieve the IP address” TS 25.469 v10.4.0
Rel-11 specification text

HNB registration now requires the HNB-GW to verify the HNB identity, cell access mode and CSG ID, and HNB behaviour was extended for Iurh connectivity, PWS and the Tunnel Information IE.

  • “The HNB-GW shall verify the HNB identity, the validity of the indicated cell access mode and, for CSG cells, the CSG ID” TS 25.467 v11.5.0
  • “If supported, the HNB may include the Tunnel Information IE in the HNB REGISTER REQUEST message.” TS 25.469 v11.3.0
  • “If the HNB is supporting PWS it shall provide the Service Area For Broadcast IE within the HNB REGISTER REQUEST message.” TS 25.469 v11.3.0
Rel-12 specification text

HNB gained CELL_FACH/CELL_PCH/URA_PCH mobility support, with S-RNTI prefix assignment by the HNB-GW, HNB-to-HNB mobility over Iurh, and L-GW co-location extended to SIPTO@LN mode.

  • “CELL_FACH mobility support, if the HNB supports mobility for CELL_FACH, CELL_PCH and URA_PCH.” TS 25.467 v12.3.0
  • “The HNB that supports S-RNTI prefix assignment shall include the S-RNTI prefix in the most significant bits of S-RNTI part” TS 25.467 v12.3.0
  • “The Local Gateway (L-GW) may be present only when the HNB operates in LIPA mode or when the HNB operates in SIPTO@LN mode.” TS 25.467 v12.3.0

Defining Specifications

3GPP specifications that define or reference HNB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.220 vj00 Home NodeB/Home eNodeB Service Requirements Rel-19 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.830 v900 Home NodeB/HeNB Architecture and CSG Study Rel-9 read
TS 24.008 vk10 NAS Call, Mobility and Session Procedures Rel-20 read
TS 24.285 vj00 Allowed CSG List Management Object Rel-19 read
TS 25.367 vj00 Home NodeB Mobility Procedures Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 25.444 vj00 HNB User Data Transport Protocols Rel-19 read
TS 25.467 vj00 UTRAN Architecture for 3G Home Node B Rel-19 read
TS 25.468 vj00 RANAP User Adaption (RUA) protocol specification Rel-19 read
TS 25.469 vj00 HNBAP Specification for HNB to HNB-GW Interface Rel-19 read
TS 25.470 vj00 PCAP User Adaption (PUA) protocol specification Rel-19 read
TS 25.471 vj00 RNSAP User Adaptation (RNA) for Iurh Rel-19 read
TS 25.820 v820 3G Home NodeB Study Report Rel-8 read
TS 25.866 v900 1.28Mcps TDD Home NodeB Study Item Rel-9 read
TR 25.967 vj00 Home NodeB RF Requirements Technical Report Rel-19 read
TS 28.671 vj00 HNS Network Resource Model Requirements Rel-19 read
TS 28.672 vj00 HNS NRM IRP Information Service Rel-19 read
TS 28.673 vj00 HNS NRM IRP Solution Set Definitions Rel-19 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 31.104 vj00 HPSIM Application Specification Rel-19 read
TS 31.121 vj00 UICC Application Test Specification Rel-19 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.571 vj00 HNB/HeNB Type 2 Interface Management Concepts Rel-19 read
TS 32.572 vj00 HNB/HeNB Type 2 Interface Concepts & Requirements Rel-19 read
TS 32.581 vj00 HNB OAM&P Concepts & Requirements Rel-19 read
TS 32.582 vj00 HNB Management Information Model for Type 1 Interface Rel-19 read
TS 32.583 vj00 HNB OAM&P Procedure Flows for Type 1 Interface Rel-19 read
TS 32.584 vj00 HNB OAM&P XML Definitions for Type 1 Interface Rel-19 read
TS 32.592 vj00 HeNB OAM&P Information Model Rel-19 read
TS 32.593 vj00 HeNB OAM&P Procedure Flows for Type 1 Interface Rel-19 read
TS 32.594 vj00 Data definitions for HeNB to HeMS Type 1 interface Rel-19 read
TS 32.632 vb00 Core Network Resources NRM Rel-11 read
TS 32.633 v920 Core Network Resources IRP CORBA Solution Set Rel-9 read
TS 32.635 v910 Core Network Resources IRP Bulk CM XML Format Rel-9 read
TS 32.771 vb00 HNS NRM IRP Requirements Rel-11 read
TS 32.772 vb00 HNS Network Resources NRM Rel-11 read
TS 32.821 v900 SON OAM for Home NodeB (LTE/UMTS) Rel-9 read
TS 33.106 vj00 Lawful Interception Requirements (Pre-Rel-15) Rel-19 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.126 vj30 Lawful Interception Requirements Rel-19 read
TS 33.320 vj00 H(e)NB Subsystem Security Architecture Rel-19 read
TS 33.545 vk10 NR Femto Security Architecture Rel-20 read
TS 33.820 v830 H(e)NB Security Threats and Countermeasures Rel-8 read
TR 36.921 vj00 FDD Home eNodeB RF Requirements Technical Report Rel-19 read
TR 36.922 vj00 LTE TDD Home eNodeB RF Requirements Rel-19 read