Description
The Home Node B Gateway (HNB-GW) is a critical aggregation and security gateway in the 3GPP UMTS femtocell (HNB) architecture. Its primary function is to serve as the network-side termination point for secure tunnels established from thousands of distributed Home Node Bs (HNBs) over untrusted IP networks (like the public internet). From the perspective of the core network elements – the Mobile Switching Center (MSC) for circuit-switched calls and the Serving GPRS Support Node (SGSN) for packet data – the HNB-GW appears as a standard Radio Network Controller (RNC), communicating via the Iu-CS and Iu-PS interfaces respectively.
Operationally, each HNB discovers and registers with an HNB-GW, establishing a secure IPsec tunnel for all control and user plane traffic. The HNB-GW authenticates the HNB, often using certificates, and manages the lifecycle of this secure association. It terminates the Iu-h interface from the HNB, which carries a modified version of the RANAP protocol, and translates it into the standard Iu interface signaling for the core network. This includes relaying location updates, call setup requests, and handover messages. For the user plane, the HNB-GW may perform concentration and lawful interception functions, forwarding voice and data packets between the secure tunnel and the core network's media gateways or GGSN.
The HNB-GW also plays a key role in mobility management. It handles handovers between HNBs under its control (intra-HNB-GW handover) and can facilitate handovers to and from the macro UMTS network. It maintains context for active UEs connected via HNBs. Furthermore, it interfaces with the HNB Management System (HMS) for provisioning and fault management of the HNBs. By concentrating traffic from many low-capacity HNBs, the HNB-GW provides a scalable architecture that protects the core network from being directly exposed to a vast number of consumer-grade devices.
Purpose & Motivation
The HNB-GW was created to solve the fundamental network integration and security challenges posed by mass deployment of consumer femtocells (HNBs). Without a gateway, each HNB would need to connect directly to the operator's core network nodes (MSC, SGSN), which was not scalable or secure over the public internet. The HNB-GW provides a necessary aggregation and trust boundary.
It addresses several key problems: Security, by terminating IPsec tunnels and authenticating HNBs before they can access core network resources; Scalability, by aggregating signaling and traffic from potentially millions of HNBs into a manageable number of interfaces towards the core; and Transparency, by hiding the femtocell-specific aspects (like the Iu-h interface and CSG management) from the legacy core network, allowing existing MSCs and SGSNs to operate without major upgrades.
The development of the HNB-GW in Release 8 was motivated by the need for a standardized, carrier-grade architecture that would enable operators to safely and efficiently deploy femtocells at scale. It provided the crucial piece of infrastructure that made the residential femtocell business model viable, ensuring network integrity, enabling efficient resource usage, and supporting essential functions like mobility and lawful interception.
What changed in its specifications
The latest release-to-release comparison of specifications that define HNB-GW. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 25.467: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 25.467 →Enhanced Home NodeB/eNodeB procedures and CSG membership status information element were added.
Full comparison in TS 25.468 →Technology family
Base stations and RAN nodes · Radio Access Network
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 sourcesDocumented 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.
HNB-GW is specified for the first time as the gateway concentrating HNB connections toward the CN over Iu, handling HNB/UE registration, access control and RANAP forwarding via HNBAP and RUA.
- “The HNB GW serves the purpose of a RNC presenting itself to the CN as a concentrator of HNB connections.” TS 25.467 v8.6.0
- “The purpose of the HNB Registration Procedure is to register the HNB with the HNB-GW to enable the HNB-GW to provide service and core network connectivity” TS 25.469 v8.5.0
- “The reception of the RUA CONNECT message at the HNB-GW triggers the setup of an SCCP connection by the HNB-GW towards the CN.” TS 25.467 v8.6.0
In Rel-9 the HNB-GW gained CSG-related access control and membership verification, CSG membership status signalling to the HNB, optional mux port de-multiplexing, and the ability to initiate RUA Connect for inbound relocation.
- “The HNB-GW shall initiate this procedure whenever it needs to indicate a change of a UE's CSG membership status to the HNB.” TS 25.469 v9.3.0
- “The HNB GW shall perform access control (in case of CSG cells) or membership verification (in case of Hybrid cells) for the UE.” TS 25.467 v9.6.0
- “If the HNB-GW is capable of de-multiplexing, then the MuxPortNumber IE may be included in the HNB REGISTER ACCEPT message.” TS 25.469 v9.3.0
HNB-GW behaviour was extended: it may include a mux port in HNB REGISTER ACCEPT, can supply Iurh TNL address lists, stores RAB/ciphering/trace parameters, and sends TNL UPDATE FAILURE on TNL resource failure.
- “If the HNB-GW has capability to de-multiplex, the HNB-GW may include a mux port in the HNB REGISTER ACCEPT message.” TS 25.467 v10.6.0
- “If the HNB-GW includes a list of Iurh signalling TNL addresses in the HNBAP HNB: CONFIGURATION TRANSFER RESPONSE message” TS 25.467 v10.6.0
- “If the HNB-GW fails to establish TNL resources for the RABs indicated within the TNL UPDATE REQUEST message the HNB-GW shall send the TNL UPDATE FAILURE message” TS 25.469 v10.4.0
HNB-GW gained new responsibilities in Rel-11: verifying CSG ID and cell access mode, acting as a single RNC concentrator towards macro RNCs, and using an S15 interface towards PCRF for fixed broadband interworking.
- “the HNB-GW uses a S15 interface towards PCRF for CS sessions as specified in TS 23.139 [36]” TS 25.467 v11.5.0
- “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
- “The HNB-GW acts as a single RNC towards the macro RNC (as it does towards the CN)” TS 25.467 v11.5.0
HNB-GW gained new responsibilities in Rel-12: assigning and keeping S-RNTI prefixes unique for CELL_FACH mobility, answering U-RNTI queries, and routing PCAP messages between HNBs and the SAS via PUA.
- “The HNB-GW ensures that the S-RNTI prefixes assigned to HNBs are unique within the URA Area/overlapping URA Areas.” TS 25.467 v12.3.0
- “If the CELL_FACH Mobility Support IE is included in the HNB REGISTER REQUEST message, the HNB-GW shall, if supported, include the S-RNTI Prefix IE” TS 25.469 v12.4.0
- “The HNB-GW then generates and routes the PCAP PDU within a connectionless SCCP message towards the SAS.” TS 25.467 v12.3.0
Defining Specifications
3GPP specifications that define or reference HNB-GW, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |
| TR 25.967 vj00 | Home NodeB RF Requirements Technical Report | Rel-19 read |
| TS 28.673 vj00 | HNS NRM IRP Solution Set Definitions | Rel-19 read |
| TS 31.104 vj00 | HPSIM Application Specification | Rel-19 read |
| TS 32.583 vj00 | HNB OAM&P Procedure Flows for Type 1 Interface | Rel-19 read |
| TS 32.821 v900 | SON OAM for Home NodeB (LTE/UMTS) | Rel-9 read |