Non-3GPP Device Identifier

Description

The Non-3GPP Device Identifier is a key concept introduced in 3GPP Release 19 to enable fine-grained Quality of Service (QoS) differentiation for non-3GPP devices that connect to the 5G network through a User Equipment (UE) or a 5G Residential Gateway (5G-RG). Such devices may include Wi-Fi-only gadgets, IoT sensors, or legacy equipment that do not support 3GPP radio interfaces. The identifier is a generic string that is bound to the non-3GPP device, allowing the 5G Core Network (5GC) to recognize and treat traffic originating from or destined to that device differently from other traffic traversing the same UE or 5G-RG.

In the 5G architecture, a UE or 5G-RG can act as a gateway for multiple non-3GPP devices, aggregating their traffic over the 3GPP access link. Without a mechanism to distinguish individual devices, all traffic would receive the same QoS treatment, which is inefficient for scenarios where different devices have different requirements (e.g., a video streaming device versus a temperature sensor). The Non-3GPP Device Identifier solves this by providing a unique label that the 5GC can use to map traffic to specific QoS flows or policies.

The identifier is defined in 3GPP TS 23.501 (System Architecture for the 5G System) and TS 33.700 (Study on Security Aspects of Enhancement for Support of Non-3GPP Devices). It is a string that can be assigned by the network or derived from device information, and it is bound to the device during registration or session establishment. The binding process involves the UE or 5G-RG reporting the identifier to the network, which then associates it with the device's traffic. This allows the Session Management Function (SMF) and Policy Control Function (PCF) to apply specific QoS rules, such as guaranteed bit rate or priority handling, for that device's traffic.

The identifier operates at the application or transport layer, as it is not a 3GPP-specific hardware identifier like the IMEI or SUPI. It is a logical identifier that can be provisioned by the network operator or generated dynamically. The 5GC uses it to enforce QoS policies in the User Plane Function (UPF) and to ensure that the correct treatment is applied to packets belonging to the non-3GPP device. This is particularly important in fixed-mobile convergence scenarios, where a 5G-RG serves as a broadband gateway for home devices, and the operator wants to offer differentiated services such as low-latency gaming or high-priority video conferencing.

From a security perspective, the identifier must be protected against spoofing and unauthorized modification. TS 33.700 outlines security requirements for the binding and usage of the identifier, ensuring that only authorized entities can assign or modify it. The identifier is typically transmitted over secure channels, such as the N1 interface between the UE and AMF, or the N2 interface between the 5G-RG and the network, and is subject to integrity protection.

The introduction of the Non-3GPP Device Identifier reflects the growing importance of non-3GPP access in 5G, as operators seek to integrate Wi-Fi and other technologies into their service offerings. It enables a more granular and efficient use of network resources, improving user experience and enabling new business models.

Purpose & Motivation

The Non-3GPP Device Identifier was created to address the lack of granularity in QoS enforcement for non-3GPP devices connected behind a UE or 5G-RG. In earlier 5G releases, all traffic from such devices was treated as a single flow, making it impossible to differentiate services based on the specific device. This limitation hindered the ability to offer tailored QoS for different applications and devices, especially in home and enterprise environments where a single gateway serves multiple endpoints.

The identifier solves this by providing a standardized way to label and distinguish individual non-3GPP devices, allowing the 5GC to apply per-device QoS policies. This is essential for supporting use cases such as smart home automation, where a security camera might require higher uplink priority than a smart bulb, or enterprise networks where different departments need different service levels.

Historically, the need for such an identifier arose from the convergence of fixed and mobile networks, driven by the proliferation of non-3GPP devices and the desire to integrate them seamlessly into 5G. The 3GPP Release 19 study on non-3GPP devices (TS 33.700) highlighted the security and architectural challenges, leading to the definition of this identifier in TS 23.501. It represents a step forward in making 5G a truly converged network that can serve any device, regardless of its access technology.