Non-3GPP device

Description

A Non-3GPP device is a concept introduced in 3GPP Release 19 to describe devices that connect to a Mission Critical (MC) gateway User Equipment (UE) using access technologies not specified by 3GPP. This term is defined in specifications TS 23.280 and TS 24.501, which cover mission-critical services and non-3GPP access, respectively. The primary purpose is to allow devices that do not natively support 3GPP radio access (such as Wi-Fi-only devices, wired devices, or proprietary radio systems) to participate in mission-critical communication services by leveraging a 3GPP UE as a gateway. This extends the reach of MC services beyond traditional cellular coverage, enhancing interoperability and flexibility in critical communications.

The architecture involves a Non-3GPP device connecting to an MC gateway UE via a non-3GPP access method. The MC gateway UE acts as a bridge, relaying traffic between the Non-3GPP device and the 3GPP network (e.g., 5G core). A subset of Non-3GPP devices can host an MC client as specified by 3GPP, meaning they can run the application-layer protocols required for mission-critical services like MCPTT (Mission Critical Push-to-Talk), MCVideo, and MCData. This allows users on non-3GPP devices to communicate seamlessly with users on 3GPP devices, using the same service enablers and quality of service mechanisms. The MC gateway UE handles the 3GPP-specific procedures, such as registration, authentication, and QoS management, on behalf of the Non-3GPP device.

The key components include the Non-3GPP device itself, which may be a smartphone, laptop, or specialized communication device; the MC gateway UE, which is a 3GPP-compliant device with gateway capabilities; and the 3GPP network, which provides the MC services. The Non-3GPP device connects to the gateway via a local access technology, such as Wi-Fi, Bluetooth, or Ethernet. The gateway then establishes a connection to the 3GPP network, potentially using a PDU session or similar mechanism, and relays the MC traffic. The 3GPP network treats the gateway as the endpoint for the Non-3GPP device, applying security and policy controls as needed.

This concept is particularly relevant for scenarios where 3GPP coverage is unavailable or unreliable, such as indoor environments, remote areas, or during disasters. By allowing non-3GPP devices to access MC services through a gateway, organizations can ensure continuous communication for first responders and critical personnel. It also enables the integration of legacy or specialized equipment into modern MC systems, protecting investments and facilitating gradual migration. The specification ensures that such integration maintains the required security, reliability, and performance standards of mission-critical services.

In summary, the Non-3GPP device term formalizes the inclusion of non-cellular devices in the 3GPP mission-critical ecosystem. It leverages the concept of a gateway UE to bridge disparate access technologies, providing a standardized way to extend MC services. This innovation, introduced in Rel-19, reflects the evolving needs of critical communications, where seamless connectivity across heterogeneous networks is paramount.

Purpose & Motivation

The Non-3GPP device concept was created to address the growing need for mission-critical communication services to be accessible from a wide range of devices, not just those with 3GPP cellular modems. In many critical scenarios, such as emergency response, users may have devices that only support Wi-Fi or other non-3GPP access technologies. Previously, these devices could not directly participate in 3GPP MC services, limiting the reach and effectiveness of critical communications. The introduction of this term in Rel-19 provides a standardized framework for integrating such devices via a gateway UE, ensuring they can benefit from the reliability, security, and features of 3GPP MC services.

Historically, mission-critical services were confined to 3GPP access, which restricted their use to devices with cellular connectivity. This was a limitation in environments where cellular coverage is poor or where devices are not equipped with cellular modems. The Non-3GPP device concept solves this by allowing a 3GPP UE to act as a gateway, relaying traffic between non-3GPP devices and the 3GPP network. This approach leverages the ubiquity of non-3GPP access technologies like Wi-Fi and the widespread availability of 3GPP UEs, creating a flexible and cost-effective solution.

The motivation also includes the desire to support a diverse ecosystem of devices in MC communications, from smartphones to specialized equipment. By enabling a subset of Non-3GPP devices to host an MC client, the specification ensures that these devices can fully participate in MC services, including push-to-talk, video, and data, with the same user experience as 3GPP devices. This fosters interoperability and allows organizations to leverage existing devices, reducing costs and simplifying deployment. Overall, the Non-3GPP device term exemplifies 3GPP's commitment to evolving mission-critical communications to meet real-world operational needs.