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

Glossary term · Other

GCS

Global Coordinate System

Other →

GCS is a standardized 3GPP spatial reference framework that consistently defines the locations and orientations of network elements, UEs, and objects to support positioning, location-based services, and spatial consistency in applications such as NR positioning and UAV tracking.

Introduced
Rel-12
Where
Services › Codecs
Specifications
28 specs
Also in
Radio Access Network, Core Network
GCS Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Global Coordinate System (GCS) in 3GPP refers to a common coordinate framework used to represent geographical positions and orientations of entities such as user equipment (UE), base stations (gNB), and other objects. It is essential for location-based services, positioning enhancements, and spatial consistency in various 3GPP features, including NR positioning, UAV identification and tracking, and cooperative intelligent transport systems (C-ITS). The GCS provides a unified way to express coordinates, typically based on the World Geodetic System 1984 (WGS 84) for latitude, longitude, and altitude, and may also include local Cartesian coordinates for relative positioning.

In 3GPP specifications, the GCS is used across multiple releases and working groups. For example, in NR positioning (Rel-16 and beyond), the GCS is the reference for reporting UE location estimates. The Location Management Function (LMF) uses the GCS to provide positioning results to external clients via the Gateway Mobile Location Centre (GMLC). The GCS also appears in the UAV specifications (e.g., TS 23.179, TS 23.280) for reporting UAV position and in the V2X specifications for vehicle location. The coordinate system ensures that all network elements interpret location data consistently, which is critical for applications like autonomous driving, drone delivery, and emergency services.

The GCS is not a single protocol but a conceptual framework that is referenced in many 3GPP specifications. It defines how coordinates are encoded, the reference ellipsoid, and the units of measurement. For example, TS 23.032 defines the universal geographical area description (GAD) which includes latitude, longitude, and altitude with specified accuracy. The GCS may also include orientation parameters (e.g., heading, pitch, roll) for UAVs, as defined in TS 23.280 for UAV tracking. In addition, the GCS can be extended to local coordinate systems for indoor positioning, where a local origin and orientation are defined relative to the global system.

The implementation of GCS in 3GPP networks involves several interfaces and protocols. The LMF communicates with the UE and gNB using the LTE Positioning Protocol (LPP) and NR Positioning Protocol A (NRPPa), which carry GCS-based location information. The GMLC exposes location to external clients via the Le interface, using the GCS. For UAVs, the UAV controller and USS (UAS Service Supplier) exchange position data using GCS coordinates over the Uu or PC5 interfaces. The GCS is also used in the 5G Service-Based Architecture (SBA) for location services, where the Nlmf and Ngmlc services provide location information in GCS format.

The GCS is crucial for interoperability and accuracy. Without a common coordinate system, location data from different sources would be incompatible, leading to errors in positioning and tracking. The GCS ensures that a location reported by one network element can be understood by another, regardless of vendor or technology. It also facilitates the integration of 3GPP networks with external systems, such as air traffic control or intelligent transportation systems, which rely on standardized geospatial data.

As 3GPP evolves, the GCS continues to be refined to support new use cases. For instance, Rel-17 introduced enhancements for UAVs, including more precise altitude reporting and orientation. Rel-18 and beyond are expected to further improve positioning accuracy and support for new coordinate systems, such as those for indoor and industrial environments. The GCS remains a foundational element for any location-aware service in 5G and beyond.

Purpose & Motivation

The Global Coordinate System (GCS) exists to provide a common language for expressing location and orientation across all 3GPP specifications and network elements. Before its standardization, different systems used proprietary or incompatible coordinate formats, making it difficult to share location data between networks, devices, and applications. The GCS solves this by defining a universal reference framework based on internationally recognized geodetic standards, ensuring that a location reported by one entity is unambiguously understood by another.

The GCS is motivated by the growing demand for location-based services, emergency call positioning (e.g., E911), and new use cases like UAV traffic management and autonomous vehicles. These applications require high accuracy and reliability, which can only be achieved if all components—UEs, base stations, core network functions, and external servers—use the same coordinate system. The GCS also enables interoperability between 3GPP networks and external systems, such as air traffic control or intelligent transport systems, which rely on standardized geospatial data.

Historically, 3GPP has used the GCS since early releases for location services (LCS) in GSM and UMTS. As networks evolved to LTE and 5G, the GCS was extended to support new positioning methods (e.g., OTDOA, NR positioning) and new use cases (e.g., UAVs). The GCS continues to evolve to meet the demands of emerging applications, ensuring that 3GPP remains at the forefront of location technology.

What changed in its specifications

The latest release-to-release comparison of specifications that define GCS. 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 →
TS 23.281Rel-18 → Rel-19

Enhanced Mission Critical Architecture adds MCVideo procedures for ad hoc group call release, leave, and criteria modification, plus call handling during group regroup.

Full comparison in TS 23.281 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change
  • MB2 improvements for GCS AS to be able to request application of FEC and/or RoHC to a MBMS bearer TS 23.468CR0081

Defining Specifications

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

SpecificationTitleRelease
TS 23.179 vd50 MCPTT Functional Architecture Rel-13 read
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 23.281 vk51 Mission Critical Video Service Rel-20 read
TS 23.379 vk40 Mission Critical Push-to-Talk Architecture Rel-20 read
TS 23.468 vj00 Group Communication System Enablers for LTE Rel-19 read
TS 23.795 vg10 V2X Application Architecture Study Rel-16 read
TS 24.380 vk10 MCPTT Media Plane Control Protocols Rel-20 read
TS 24.581 vj30 MCVideo Media Plane Control Rel-19 read
TS 26.281 vj00 MCVideo Codecs and Media Handling Rel-19 read
TS 26.346 vj30 MBMS User Services Specification Rel-19 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TS 26.880 ve00 MBMS Enhancements for Mission Critical Video Rel-14 read
TS 26.881 vf00 MBMS FEC for Mission Critical Services Study Rel-15 read
TR 26.989 vj00 MCPTT Enhancement Analysis Rel-19 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.468 vj00 MB2 Reference Point Protocol Definition Rel-19 read
TS 32.273 vj00 MBMS Charging Management Rel-19 read
TS 33.185 vj00 V2X Security in LTE Rel-19 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read
TS 36.873 vc70 3D Channel Model for LTE Beamforming and FD-MIMO Rel-12 read
TS 38.305 vj30 NG-RAN UE Positioning Stage 2 Rel-19 read
TS 38.355 vj20 Sidelink Positioning Protocol (SLPP) Specification Rel-19 read
TS 38.753 vj00 Spatial Channel Model Study for NR Demodulation Rel-19 read
TS 38.843 vj00 Study on AI/ML for NR Air Interface Rel-19 read
TR 38.900 vf00 Channel Model Study for >6 GHz Rel-15 read
TS 38.901 vj50 5G NR Channel Model Rel-19 read