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.
Key Features
- Aggregates control and user plane connections from a large number of HNBs
- Terminates secure IPsec tunnels from HNBs over untrusted IP networks
- Acts as a concentrator, presenting a standard Iu interface to the core network (MSC, SGSN)
- Translates between the HNB-specific Iu-h interface protocol and standard Iu RANAP
- Manages HNB registration, authentication, and security context
- Handles mobility, including handovers between HNBs and to/from the macro network
Evolution Across Releases
Initial specification of the HNB-GW as part of the UMTS femtocell architecture. Defined its role in aggregating HNB connections via the Iu-h interface, establishing security with IPsec, and interfacing with the core network via standard Iu-CS and Iu-PS. Specified procedures for HNB discovery, registration, and UE mobility management through the gateway.
Defining Specifications
| Specification | Title |
|---|---|
| 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.967 | 3GPP TS 25.967 |
| TS 28.673 | 3GPP TS 28.673 |
| TS 31.104 | 3GPP TR 31.104 |
| TS 32.583 | 3GPP TR 32.583 |
| TS 32.821 | 3GPP TR 32.821 |