Description
The Network Element Identifier (NEID) is a fundamental identifier defined within 3GPP specifications, particularly in the security context (TS 33.108). It serves as a globally unique or domain-unique name for a network element (NE) participating in 3GPP-defined security and management protocols. A network element can be any physical or logical node within the system, such as a Radio Access Network (RAN) component like a gNB or eNodeB, a Core Network (CN) function like an AMF or SMF, or an Operations and Maintenance (O&M) entity like an Element Manager (EM) or Network Manager (NM).
The NEID is used as a primary identifier in security mechanisms, most notably in the 3GPP Lawful Interception (LI) and Key Establishment (KE) architectures. In LI systems, the NEID is used to unambiguously identify the network element that is generating or mediating interception-related information (IRI) and content of communication (CC). This allows the Lawful Interception Administration Function (LIAF) and Mediation Functions to correctly attribute intercepted data to its source. In key establishment protocols for securing management interfaces (like the Key Establishment (KE) protocol defined in TS 33.310), the NEID forms part of the certificate subject name or is used in authentication exchanges to ensure that keys are established with the correct, intended network element.
From an operational perspective, the structure and assignment of NEIDs are critical for network management. They enable fault management systems to pinpoint the exact equipment reporting an alarm, performance management systems to correlate metrics from the correct source, and configuration management systems to target updates accurately. The NEID must be persistent and stable over the lifecycle of the element. Its format is often hierarchical, potentially incorporating elements like the Public Land Mobile Network (PLMN) ID, operator-assigned identifiers, and equipment type or instance numbers, ensuring uniqueness across potentially global deployments and facilitating automated discovery and inventory.
Purpose & Motivation
The NEID was created to address the critical need for unambiguous identification in large-scale, multi-vendor, and potentially interconnected telecommunications networks. Prior to standardized identifiers, operators and equipment vendors used proprietary naming schemes, which complicated interoperability, security, and centralized management, especially in networks composed of equipment from different suppliers.
Its primary purpose is to solve the identification problem in two key areas: security and manageability. For security, protocols like Lawful Interception and secure key exchange require a trusted, unforgeable identifier to bind security credentials (like digital certificates) and intercepted data to a specific physical or logical entity. Without a unique NEID, it would be impossible to reliably authenticate a network element requesting a secure connection or to audit the source of intercepted communications, compromising legal compliance and network integrity. For network management, the NEID provides a stable key for all O&M functions. It allows an operator's Network Management System (NMS) to uniquely identify and communicate with thousands of disparate elements, enabling automated provisioning, software updates, fault correlation, and performance monitoring across the entire network fabric, regardless of the underlying equipment vendor.
Key Features
- Globally or domain-unique identifier for a physical or logical network element
- Used as a subject identifier in security certificates (e.g., for TLS on management interfaces)
- Mandatory identifier in 3GPP Lawful Interception (LI) architectures for attributing intercepted data
- Enables precise targeting in network management protocols (fault, configuration, performance)
- Supports multi-vendor interoperability by providing a standardized naming scheme
- Persistent identifier that remains constant throughout the element's operational lifecycle
Evolution Across Releases
Formally defined the concept and requirements for the Network Element Identifier within the 3GPP security architecture, particularly in TS 33.108 for Lawful Interception. Established its role as a fundamental name used in security protocols and for identifying the source of Interception-Related Information (IRI).
Adapted and reaffirmed the use of NEID principles within the 5G security architecture. With the introduction of the Service-Based Architecture (SBA) and new network functions, the need for secure, unique identification of NFs (which can be considered logical network elements) remained, integrating with concepts like NF Instance IDs and security credential management.
Defining Specifications
| Specification | Title |
|---|---|
| TS 33.108 | 3GPP TR 33.108 |