Human Readable Network Name

Description

The Human Readable Network Name (HRNN) is a network identifier defined in 3GPP specifications for user-friendly network discovery and selection. It is a UTF-8 encoded character string that represents the name of a network, such as a public operator's brand (e.g., 'Operator A 5G') or a private/corporate network (e.g., 'Factory Campus Network'). The HRNN is broadcast by the network in system information blocks (SIBs) over the radio interface and is used by the UE to present available networks to the user in a comprehensible way. From an architectural perspective, the HRNN is associated with a PLMN ID (MCC+MNC) or a Network Identifier (NID) for an SNPN (Standalone Non-Public Network). It operates within the Non-Access Stratum (NAS) and Access Stratum (AS) procedures for network selection and registration.

The mechanism works as follows: The network (gNB in 5G NR or eNB in LTE) includes the HRNN within specific system information messages, such as SIB1. When a UE performs initial cell selection or scans for available networks, it reads these broadcast messages. The UE's NAS layer receives the HRNN along with the PLMN ID/NID. The device's management layer (MM) or user interface then uses this HRNN to populate the list of available networks shown to the user. For automatic network selection, the UE may use the PLMN ID from its list of preferred networks, but the HRNN enhances the manual selection experience. In the case of Non-Public Networks (NPNs), the HRNN is particularly crucial because these networks may not have a globally unique PLMN ID and are intended for private use; a recognizable name is essential for users to identify and connect to the correct private network in environments where multiple such networks may be present.

The HRNN is defined across multiple 3GPP specifications, covering core network aspects (TS 23.003), UE management commands (TS 27.007), and radio access network procedures (TS 38.300, 38.304, 38.331). Its introduction formalizes a practice that existed in a vendor-specific manner, ensuring interoperability. The UE behavior for handling HRNN is specified, including scenarios where an HRNN is not provided (the UE may display the PLMN ID) or where multiple HRNNs for different languages are broadcast (the UE selects the most appropriate based on its settings). This identifier plays a key role in improving user experience, especially in the context of network slicing and private networks, where clear identification is necessary for both consumers and enterprise users.

Purpose & Motivation

HRNN was introduced to solve the user experience problem of identifying networks solely by their numeric PLMN codes (MCC+MNC), which are meaningless to end-users. While PLMN IDs are essential for network routing and core network functions, they provide a poor interface for human interaction. Prior to standardization, some devices and networks used proprietary methods to display network names, leading to inconsistencies. The proliferation of new network types in 5G, particularly Non-Public Networks (NPNs) and network slices presented as virtual networks, created an urgent need for a standardized, human-friendly identifier.

The primary motivation was to support the 5G vision of vertical industries and private networks. In a factory, airport, or campus setting, multiple private networks from different vendors or for different purposes might coexist. A technician or IoT device needs to easily identify and connect to 'Logistics 5G' versus 'Security Camera Network.' Relying on obscure numeric codes would be error-prone and inefficient. HRNN standardizes this naming capability, ensuring that any compliant UE can correctly display the network name provided by any compliant RAN. It also future-proofs the system for more complex network selection scenarios involving slice-specific network names or user-specific network subscriptions, enhancing usability in the increasingly heterogeneous 5G ecosystem.