LHN

Local Home Network Identifier

Identifier →
Introduced in Rel-12

LHN is an identifier used in LTE and 5G NR to distinguish a specific Local Home Network for RAN access control, mobility management, and policy application.

Category
Identifier
Introduced
Rel-12
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
4 specs
LHN Description Purpose Related Classification Specifications

Description

The Local Home Network Identifier (LHN ID) is a network identifier used within the 3GPP Radio Access Network (RAN) architecture, particularly in the context of small cells deployed in homes or enterprises (HeNBs, HNGs). It serves as a unique label for a specific Local Home Network, which is a logical grouping of one or more Home eNodeBs (HeNBs) or Home gNBs that belong to the same administrative domain, such as a particular enterprise campus, a residential subscriber's network, or a neutral host infrastructure.

Technically, the LHN ID is configured in the Home eNodeB/gNB and is communicated to the core network (MME/AMF) and neighboring macro cells during network interface establishment and handover procedures. It is carried in RAN Application Part (RANAP) and X2 Application Protocol (X2AP) messages. The primary function of the LHN ID is to enable the RAN and core network to identify the 'home' network of a UE when it is connected via a small cell. This identification is crucial for several operational procedures.

For mobility management, the LHN ID allows the network to optimize handovers. For example, a handover between two HeNBs sharing the same LHN ID can be treated as an 'intra-LHN' handover, potentially using simplified procedures compared to a handover to a cell in a different LHN or the macro network. For access control and policy, the core network can use the LHN ID to verify if a UE is authorized to access that specific local network. Furthermore, it enables the application of network-specific policies, such as dedicated charging rules or allowed services, based on the local network context. In scenarios like Closed Subscriber Group (CSG) cells or hybrid access cells, the LHN ID helps manage the hybrid membership and resource partitioning between home network subscribers and visiting macro users.

Purpose & Motivation

The LHN ID was introduced to solve the management and operational complexities arising from the large-scale deployment of consumer and enterprise small cells (femtocells). Early femtocell deployments lacked a standardized way for the macro network to logically group and identify clusters of these cells belonging to the same owner or location. This made efficient mobility management, coordinated radio resource management, and application of localized policies difficult.

Its creation was motivated by the need for enhanced RAN support for Local IP Access (LIPA) and Selected IP Traffic Offload (SIPTO) at the local network. To efficiently route traffic and manage mobility for UEs accessing local services, the network required a clear identifier for the local domain. The LHN ID provided this, enabling features like SIPTO continuity during mobility within the same local network. It addressed the limitation of treating every HeNB as an isolated entity, allowing operators to manage groups of small cells as a cohesive local network for operational and service delivery purposes, improving both network efficiency and the user experience for localized services.

Classification

Part ofSIPTO

Evolution Across Releases

Rel-12 Initial

Introduced the LHN ID to enhance support for small cells and local networks. Defined its encoding and inclusion in RANAP and X2AP signaling to enable identification of a UE's local home network for improved mobility management (e.g., handover between HeNBs of the same LHN) and support of LIPA/SIPTO continuity.

Explore further

Broader topics and technologies where LHN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.413 vj10 S1 Application Protocol (S1AP) Rel-19
TS 36.875 vd10 Dual Connectivity Extension Requirements Rel-13
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.