Description
The H(e)NB Subsystem is an architectural concept in 3GPP specifications that defines the functional grouping of a Home NodeB (HNB) or Home eNodeB (HeNB) together with its optional gateway. It is specified in 3GPP TS 22.220 (Service requirements for Home NodeB and Home eNodeB) and TS 23.830 (Architecture aspects of Home NodeB and Home eNodeB). The subsystem represents the complete set of network elements that provide residential or enterprise femtocell coverage and connect to the mobile core network through a fixed broadband access network. The H(e)NB itself is a low-power base station that provides 3G or LTE coverage to a small area, typically a home or small business, and connects to the operator's core network via the public internet or a dedicated broadband connection.
The H(e)NB Subsystem architecture includes the H(e)NB, which terminates the air interface (Uu for 3G, LTE-Uu for LTE) and provides the radio resource management functions for the small cell. Optionally, the subsystem includes an H(e)NB Gateway, which aggregates traffic from multiple H(e)NBs and provides a concentrator function toward the core network. The gateway is particularly useful in deployments where a large number of home base stations need to connect to the core network, as it reduces the number of interfaces and simplifies scaling. The H(e)NB Subsystem connects to the core network via the Iuh interface (for HNB) or S1 interface (for HeNB), and to the H(e)NB Management System (HMS) for configuration and management. Security is provided by the Security Gateway (SeGW), which establishes IPsec tunnels between the H(e)NB and the core network.
The subsystem concept is important because it defines the boundary of what constitutes a complete home base station deployment from a functional perspective. It allows operators to deploy H(e)NBs with or without a gateway, depending on the scale and architecture of their network. For example, a small operator with a few hundred H(e)NBs might connect them directly to the core network, while a large operator with millions of H(e)NBs would use a gateway to aggregate traffic and reduce signaling load. The subsystem also defines the interfaces and protocols used between the H(e)NB and the gateway, and between the gateway and the core network, ensuring interoperability between equipment from different vendors.
The H(e)NB Subsystem supports a range of services including voice, data, and emergency calls, and provides features such as local IP access (LIPA) and selected IP traffic offload (SIPTO) in later releases. It also supports closed subscriber group (CSG) functionality, allowing operators to restrict access to authorized users. The subsystem is designed to be self-configuring and self-optimizing, with the H(e)NB automatically establishing connectivity to the core network and downloading configuration parameters from the HMS. This plug-and-play capability is essential for consumer deployments where the user installs the H(e)NB without technical expertise.
The definition of the H(e)NB Subsystem has evolved slightly over time. In Release 9, the definition stated that the subsystem consists of the H(e)NB and, optionally, the H(e)NB Gateway belonging to it. In Release 10, the wording changed to state that the subsystem consists of the H(e)NB and the H(e)NB Gateway, removing the 'optionally' qualifier. This change may reflect a shift in emphasis toward deployments that include a gateway, or it may be an editorial simplification. From Release 10 onward, the definition has remained unchanged through Release 19, indicating stability in the architectural concept.
Purpose & Motivation
The H(e)NB Subsystem concept was created to provide a standardized architectural framework for home base station deployments in 3GPP networks. Prior to the introduction of H(e)NB specifications in Release 8 and 9, there was no standardized way to deploy low-power residential base stations that connect to the core network over fixed broadband. Early femtocell solutions were proprietary and lacked interoperability, which limited their adoption and increased costs for operators.
The subsystem concept solves several problems. First, it defines the functional boundary between the home base station and the core network, clarifying which functions reside in the H(e)NB and which reside in the gateway or core network. This separation of functions is essential for interoperability and for enabling multi-vendor deployments. Second, it provides a scalable architecture by allowing the optional inclusion of an H(e)NB Gateway, which can aggregate traffic from many H(e)NBs and reduce the load on the core network. Third, it supports the plug-and-play model by defining the management interfaces and procedures that allow the H(e)NB to automatically configure itself and establish connectivity.
Historically, the H(e)NB Subsystem was introduced in Release 9 as part of the work on Home NodeB and Home eNodeB specifications. It built upon earlier work in Release 8 on HeNB architecture and was refined in subsequent releases. The change in wording from Release 9 to Release 10, which removed the 'optionally' qualifier for the gateway, may reflect a growing recognition that gateway-based deployments are the norm for large-scale femtocell rollouts. The subsystem concept has remained stable since Release 10, demonstrating its enduring relevance for small cell deployments, including in the 5G era where home base stations continue to play a role in coverage and capacity enhancement.
What changed in its specifications
The latest release-to-release comparison of specifications that define H(e)NB Subsystem. Each summary describes the whole specification, not only this term.
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 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference H(e)NB Subsystem, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.220 vj00 | Home NodeB/Home eNodeB Service Requirements | Rel-19 read |
| TS 23.830 v900 | Home NodeB/HeNB Architecture and CSG Study | Rel-9 read |