Description
A Heterogeneous Network (HetNet) in 3GPP terminology refers to a radio access network that consists of multiple cells with different characteristics, typically a mix of macro cells and small cells (e.g., pico, femto, relay nodes). The definition in 21.905 specifies that for E-UTRA, this includes a variety of eNodeBs, Home eNodeBs (HeNBs), and e-UTRA Relays. The primary goal of a HetNet is to enhance coverage and capacity in areas with high traffic demand or poor macro coverage, by overlaying smaller cells onto the macro network. These small cells can be deployed indoors or outdoors, and they may operate on the same or different frequency carriers as the macro layer.
Architecturally, a HetNet introduces additional nodes into the radio access network. Macro eNodeBs provide wide-area coverage and handle high-mobility users. Home eNodeBs (also known as femtocells) are low-power base stations typically deployed in homes or small businesses, providing dedicated coverage to a closed subscriber group (CSG) or open access. e-UTRA Relays are nodes that wirelessly backhaul traffic to the macro eNodeB, extending coverage without the need for wired backhaul. These different node types have varying transmit powers, coverage areas, and capabilities, leading to a multi-tier network structure. The 3GPP specifications define the interworking and mobility procedures to ensure seamless operation across these tiers.
Key technical challenges in HetNets include interference management, mobility robustness, and load balancing. Interference can occur between macro and small cells, especially when they share the same frequency. Techniques such as enhanced Inter-Cell Interference Coordination (eICIC) and Further Enhanced ICIC (FeICIC) were introduced in Rel-10 and Rel-11 to mitigate cross-tier interference. These include almost blank subframes (ABS) and cell range expansion (CRE) with reduced power subframes. Mobility management must handle fast-moving users passing through small cells, avoiding frequent handovers and radio link failures. Load balancing algorithms distribute traffic across tiers to optimize resource utilization.
In terms of deployment, HetNets can be deployed in various configurations: co-channel (same frequency), dedicated frequency, or carrier aggregation across tiers. The backhaul for small cells can be wired (fiber, DSL) or wireless (relay). The core network sees these nodes as regular eNodeBs, but with additional parameters for CSG and hybrid access. The X2 interface is used for inter-node coordination, enabling handover and interference coordination. The S1 interface connects to the EPC. In 5G, the concept of HetNet continues with the deployment of gNBs and small cells, often referred to as a multi-layer network.
The evolution of HetNets has been driven by the exponential growth in mobile data traffic. The specifications 36.104, 36.141, and 36.808 define the RF requirements for base stations, including those for heterogeneous deployments. 37.104 and 37.141 cover multi-standard radio (MSR) base stations. In 5G, 38.104 and 38.141 specify NR base station requirements, and 38.174 covers integrated access and backhaul (IAB) nodes, which are a form of relay for 5G. The HetNet concept is fundamental to modern network densification strategies, enabling operators to meet capacity demands cost-effectively.
Purpose & Motivation
The Heterogeneous Network concept was introduced to address the limitations of traditional homogeneous macro-only networks in meeting the ever-increasing demand for mobile broadband data. Macro networks alone struggle to provide sufficient capacity in dense urban areas and indoor environments due to physical constraints, high path loss, and limited spectrum. HetNets solve this by adding small cells that offload traffic from the macro layer, improve indoor coverage, and provide targeted capacity where needed. This approach is more cost-effective than continuously adding macro sites, which are expensive and often face deployment challenges such as site acquisition and zoning.
Before HetNets, networks were primarily planned with a regular grid of macro base stations, which led to uneven capacity distribution and poor indoor penetration. The introduction of Home eNodeBs in Rel-8 and Rel-9 allowed users to deploy their own small cells, but these were initially isolated and not fully integrated into the macro network. Rel-10 marked a significant step by formally defining HetNet and introducing interference coordination techniques to enable co-channel deployment. This allowed operators to leverage the same spectrum across tiers, improving spectral efficiency.
The motivation also included the need to support high-speed data services and the growing number of connected devices. HetNets enable a more flexible and scalable network architecture, where capacity can be added incrementally through small cells. They also facilitate the deployment of new services such as fixed wireless access and IoT, by providing localized coverage. The concept has evolved with 5G, where ultra-dense networks and millimeter-wave small cells are key enablers for enhanced mobile broadband and ultra-reliable low-latency communications.
What changed in its specifications
The latest release-to-release comparison of specifications that define Heterogeneous Network. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →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.
Initial definition introduced: 'a 3GPP access network consisting of multiple cells with different characteristics (e.g., for the case of E-UTRA: a variety of e-NodeBs, Home e-NodeBs, e-UTRA Relays).' This release also introduced eICIC to manage interference in co-channel HetNets.
Defining Specifications
3GPP specifications that define or reference Heterogeneous Network, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |