UAS Service Supplier

Description

A UAS Service Supplier (USS) is a service entity in 3GPP UAS architectures that supplies capabilities to UAS operators, UAS users, and UAS vehicles. In the standardized UAS framework, the USS is not necessarily a mobile network node; it may be an external service provider, a platform, or a network-exposed service enabler that supports the provisioning, registration, authentication, and operation of unmanned aerial systems. The USS can expose network capabilities, coordinate with 5G core functions, and provide application-level services such as remote identification, command-and-control link support, airspace integration, or fleet management. The USS interacts with several actors. The UAS operator is responsible for managing one or more UAS vehicles and may subscribe to USS services. The UAS user or pilot controls the vehicle and may receive service through the USS. The UAS vehicle itself may contain a UAS application client and communicate over the mobile network. The network, particularly the 5G core, may expose authentication, authorization, location, QoS, and communication capabilities through network exposure functions or UAS-specific functions. The USS may also interact with external authorities or service providers for regulatory compliance, such as remote ID or airspace authorization. Operationally, a USS may support UAS registration by validating the UAS identity, operator identity, and service subscription. It may assist authentication and authorization flows, enabling the network to distinguish legitimate UAS traffic and apply appropriate policies. It may help establish or maintain communication links, including command-and-control links, data links for telemetry, and video or sensor payloads. The USS can also provide service enablers, such as connectivity monitoring, network slicing coordination, quality of service management, and event reporting. From a protocol perspective, the USS may use application-layer interfaces toward the UAS operator or user, and network interfaces toward 3GPP functions. In 5G, these interactions can be supported by network exposure, policy control, and session management. The USS may be involved in procedures that bind a UAS application identifier to a UE or device, request specific QoS profiles, or report UAS state. The architecture is designed to allow different business models: a mobile network operator may act as a USS, a third-party cloud provider may act as a USS, or multiple suppliers may cooperate. Security and trust are central to the USS role. A USS may help establish the identity of a UAS operator, validate subscriptions, and support authorization for network resources. It may also coordinate with security functions to protect command-and-control traffic, telemetry, and application data. Because UAS operations can have public safety implications, the USS may need to support traceability, fraud prevention, privacy, and compliance with regulatory requirements. The term is used across service, architecture, security, and network exposure specifications. The provided release list indicates that the abbreviation appears in many releases, but the concrete UAS Service Supplier role is most closely associated with the UAS architecture work that matured in Rel-16 and later. In earlier releases, the term may have been referenced in preparatory or service-level contexts without the full UAS network architecture being specified. The definition itself remains stable: a supplier of UAS services.

Purpose & Motivation

UAS Service Supplier exists because unmanned aerial systems require more than ordinary mobile data connectivity. A UAS may need reliable command-and-control links, low-latency telemetry, remote identification, airspace authorization, and integration with network services. Without a standardized supplier concept, each UAS deployment would require bespoke integration between aircraft, network operators, cloud platforms, and regulators. The USS provides a reusable service layer that can mediate between UAS applications and mobile network capabilities. Previous approaches used vertical silos: an aircraft manufacturer, a network operator, and an application provider each implemented proprietary interfaces. This created interoperability problems, inconsistent security, and difficulty in scaling. The USS concept addresses these limitations by defining a service supplier role that can expose network capabilities to UAS operators and users while preserving the mobile network's control over authentication, policy, and QoS. The motivation also includes regulatory and safety requirements. Authorities may require remote ID, operator registration, and traceability. A USS can support these functions by coordinating with network nodes and external services. The concept also supports commercial models where connectivity and UAS services are bundled, enabling managed drone fleets, public safety operations, and delivery services.