Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

MC gateway UE

Mission Critical Gateway User Equipment

Services →

MC gateway UE is a user equipment that can be shared between multiple MC service clients or provides access to MC services for non-3GPP devices, extending MC services to devices without direct 3GPP connectivity.

Introduced
Rel-18
Where
Services › IMS
Specifications
2 specs
MC gateway UE Description Purpose What changed Neighbours Detected Changes Specifications

Description

The MC gateway UE is a specialized User Equipment defined in 3GPP TS 23.280 that serves as a bridge between Mission Critical (MC) services and devices that may not have direct 3GPP connectivity. Its definition has evolved from focusing on UE sharing among multiple MC service clients to emphasizing its role in providing access for non-3GPP devices. This evolution reflects the growing need to extend MC services to a wider range of devices, such as those connected via non-3GPP access networks (e.g., Wi-Fi, Ethernet) or devices that lack native MC capabilities.

In its original Rel-18 definition, the MC gateway UE was described as 'A UE that can be simultaneously shared between multiple MC service clients using the same or different MC services.' This addressed scenarios where a single physical device (e.g., a vehicle-mounted terminal or a ruggedized handheld) might need to support multiple MC service clients, possibly from different agencies or for different services (MCPTT, MCVideo, MCData). The gateway UE would manage the sharing of underlying resources, such as network connections, security contexts, and location data, among these clients.

In Rel-19, the definition was revised to 'A UE with functionality that enables access to the MC service for non-3GPP devices.' This shift in wording broadens the concept significantly. The MC gateway UE now acts as an access point for devices that are not directly connected to a 3GPP network but need to use MC services. For example, a police officer's body-worn camera (which may only have Wi-Fi) could connect to the officer's MC gateway UE (e.g., a smartphone with 3GPP connectivity), which then relays the MC service traffic to the network. This enables a wider ecosystem of MC devices without requiring each device to have its own 3GPP modem and MC client.

Architecturally, the MC gateway UE implements a relay function at the application layer. It terminates the MC service protocols from the non-3GPP devices and re-originates them towards the MC system. It must handle authentication and authorization of the connected devices, ensure security (e.g., encryption) for the relayed traffic, and manage QoS and priority appropriately. The gateway UE may also perform protocol conversion if the non-3GPP devices use different protocols (e.g., HTTP-based vs. SIP-based).

The MC gateway UE is particularly relevant for scenarios involving wearables, sensors, and other IoT devices in public safety. It allows these devices to participate in MC services without the cost and power consumption of a 3GPP modem. It also simplifies device management, as the gateway UE can aggregate and manage multiple devices. However, it introduces challenges such as ensuring that the gateway UE does not become a single point of failure, and that security is maintained end-to-end.

The evolution of the MC gateway UE definition from Rel-18 to Rel-19 reflects the 3GPP's responsiveness to market needs. As MC services expand beyond traditional handheld radios to include body-worn cameras, drones, and sensors, the gateway UE concept provides a flexible way to integrate these devices into the MC ecosystem. Future releases may further refine the gateway UE's capabilities, such as supporting more device types or enhancing security and management features.

Purpose & Motivation

The MC gateway UE was introduced to solve two related problems: enabling a single UE to support multiple MC service clients, and extending MC services to non-3GPP devices. In the early MC architecture, each MC service client was expected to run on a UE with its own 3GPP connection. However, in practice, users often carry multiple devices (e.g., a radio, a smartphone, a body-worn camera) and need them all to access MC services. The gateway UE allows a single 3GPP-connected device to act as a hub for other devices, reducing the number of 3GPP subscriptions and simplifying connectivity.

The Rel-19 redefinition explicitly targets non-3GPP devices, which are increasingly common in public safety (e.g., Wi-Fi-enabled cameras, sensors). These devices often lack the ability to connect directly to 3GPP networks due to cost, power, or form factor constraints. The MC gateway UE provides a way to bring them into the MC system without requiring custom network interfaces. This is analogous to a mobile hotspot but with MC-specific functionality such as priority handling, security, and group communication.

The gateway UE also addresses the need for flexibility in device deployment. For example, a command vehicle might have a powerful MC gateway UE that provides connectivity for several tablets and cameras used by first responders. This reduces the complexity of managing multiple 3GPP subscriptions and ensures that all devices can communicate seamlessly. The gateway UE thus plays a crucial role in the broader MC ecosystem, enabling a diverse range of devices to participate in mission-critical communications.

What changed in its specifications

The latest release-to-release comparison of specifications that define MC gateway UE. Each summary describes the whole specification, not only this term.

TS 23.280Rel-18 → Rel-19

Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.

Full comparison in TS 23.280 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (19 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-18 12 changes
  • Addition of definitions of terms and introduction related to MC gateway UE function TS 23.280CR0298
  • Introduction of subclauses to capture MC gateway UE function details TS 23.280CR0299
  • Using identities behind the MC gateway UE TS 23.280CR0309
  • MC gateway UE routing capabilties TS 23.280CR0310
  • MC gateway UE – MC client disconnection procedure TS 23.280CR0311
  • Clarification of MC gateway UE selection TS 23.280CR0318

+ 6 more changes

Rel-19 6 changes
  • Clarification on MC gateway UE routing capabilities TS 23.280CR0590
  • MC gateway UE fixes TS 23.280CR0624
  • Adding MC gateway UE related architectural requirements TS 23.280CR0664
  • Adding MBMS delivery function to MC gateway UE in clause 11.1 TS 23.280CR0665
  • MC gateway UE updates for security alignment TS 23.280CR0551
  • Clarification on MC gateway UE definition TS 23.280CR0558
Rel-20 1 change
  • MC gateway UE migration support TS 23.280CR0724

Defining Specifications

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

SpecificationTitleRelease
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read