Description
UAS Services, as defined in 3GPP Release 19 (TS 23.256 and TS 33.256), encompass the set of connectivity and communication services that a mobile network provides to Unmanned Aircraft Systems (UAS). These services are essential for enabling drones to operate beyond visual line of sight (BVLOS) and to comply with regulatory requirements. The core UAS Services include: establishment of connectivity for communication with the UAS Service Supplier (USS), establishment of Command and Control (C2) links between the UAV and its controller, support for Remote Identification (RID), and support for UAV location and tracking.
The first service, connectivity with the USS, allows the UAV and the network to exchange information with the USS, which is an external entity responsible for managing UAS operations, flight planning, and deconfliction. This connectivity is typically established via the NEF (Network Exposure Function) or directly through the UAS NF, using PDU sessions. The USS may provide authorization for the UAV to fly, and the network may enforce policies based on USS input.
The second service, C2 link establishment, is critical for drone control. The C2 link is a communication path between the UAV and the UAV controller, which may be direct (e.g., via radio) or indirect (e.g., via the mobile network). When provided by the mobile network, the C2 link is carried over a PDU session with specific QoS requirements (low latency, high reliability). The UAS NF authorizes the establishment of this session, ensuring that the UAV and controller are authenticated and authorized for the operation.
The third service, Remote Identification (RID), is a regulatory requirement in many jurisdictions. It enables the broadcasting or network-based transmission of identification and location data of a UAV to authorized parties such as law enforcement or air traffic control. The mobile network can support RID by providing location information and by facilitating the exchange of RID messages between the UAV and the USS or other entities.
The fourth service, UAV location and tracking, involves the network providing continuous or periodic location updates for the UAV. This can be based on network-based positioning (e.g., NR positioning) or on UAV-reported location. Tracking is essential for airspace management, collision avoidance, and compliance with geofencing rules.
UAS Services are not a single network function but rather a set of capabilities enabled by the interaction of the UAS NF, AMF, SMF, UPF, NEF, GMLC, and external USS. They are offered to UAS operators and can be tailored based on subscription and authorization. Security is a key aspect, with authentication and authorization procedures ensuring that only legitimate UAVs and controllers can access these services. The services are designed to be scalable and to support a wide range of drone operations, from small consumer drones to large commercial UAVs.
Purpose & Motivation
UAS Services were defined in 3GPP Release 19 to provide a standardized framework for delivering connectivity and communication capabilities to Unmanned Aircraft Systems over mobile networks. Prior to this, drones could connect to cellular networks as generic devices, but there was no standardized way to ensure that the connectivity met the specific needs of drone operations, such as low-latency C2 links, remote identification, and integration with USS/UTM systems. This lack of standardization hindered the widespread adoption of cellular-connected drones and made it difficult for operators to offer value-added services.
The purpose of UAS Services is to address these gaps by defining a set of services that the network can provide to UAS, ensuring interoperability, security, and regulatory compliance. By standardizing these services, 3GPP enables mobile operators to offer UAS connectivity as a service, and allows UAS operators to rely on cellular networks for safe and reliable drone operations. The services also facilitate coordination with aviation authorities through Remote Identification and tracking, which are mandatory in many regions.
Furthermore, UAS Services enable new business opportunities for operators, such as providing C2 links, RID, and tracking as part of a service-level agreement. They also support the scalability needed for future mass drone operations, such as drone delivery and urban air mobility. The definition in Release 19 provides a foundation that can be extended in future releases to support more advanced features like autonomous operations and advanced traffic management.
What changed in its specifications
The latest release-to-release comparison of specifications that define UAS Services. Each summary describes the whole specification, not only this term.
Rel-19 adds NEF-assisted pre-flight planning, USS changeover, and network-assisted detect-and-avoid to TS 23.256. It also adds no-transmit zone enforcement for UAV UEs and altitude reporting.
Full comparison in TS 23.256 →Uncrewed Aerial System Phase 3 adds USS changeover and UUAA procedures between UAV and USS 2, with checks against authorized USS lists.
Full comparison in TS 33.256 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference UAS Services, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.256 vj50 | UAS Support Architecture Enhancements | Rel-19 read |
| TS 33.256 vj20 | Security for Uncrewed Aerial Systems (UAS) | Rel-19 read |