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

Glossary term · Services

Location

Location

Services →

Location is the current position, velocity, and direction of a mission-critical user equipment, which enables location-aware services and emergency response coordination.

Introduced
Rel-8
Where
Services › IMS
Specifications
4 specs
Location Description Purpose What changed Neighbours Detected Changes Specifications

Description

In 3GPP terminology, Location refers to the current position of a Mission Critical (MCX) User Equipment (UE) and, when available, information about its instantaneous velocity and direction. It also encompasses other attributes such as a label indicating a geographic area in which the MCX UE is located. This definition is primarily used within the context of Mission Critical Services (MCX), including MCPTT (Mission Critical Push To Talk), MCVideo, and MCData, as specified in 3GPP TS 22.280 and TS 23.280. The concept is essential for enabling dispatchers and incident commanders to visualize the real-time positions of field personnel and assets during emergency operations.

The Location information is generated by the UE using various positioning methods, which may include GPS/GNSS, network-based positioning (e.g., Cell ID, OTDOA, E-CID), or hybrid techniques. The UE reports its location to the MCX server (e.g., MCPTT server) either periodically, on demand, or triggered by events such as entering or leaving a predefined geofence area. The MCX server then makes this information available to authorized users, such as dispatchers, through the MCX application. The location data is typically represented as a set of coordinates (latitude, longitude, altitude) along with a timestamp, accuracy estimate, and velocity vector. The geographic area label is a human-readable identifier (e.g., "Building A, Floor 3") that can be derived from the coordinates using a mapping database.

Architecturally, the Location functionality in MCX is supported by the Location Management (LM) function within the MCX server. The LM function is responsible for receiving location reports from UEs, storing them, and distributing them to authorized clients based on policy and access control rules. The interface between the UE and the MCX server for location reporting is typically the MCX-1 interface for signaling and the MCX-2 interface for media and data. The location information can also be integrated with other MCX features, such as group management (e.g., displaying all members of a group on a map) and emergency alerts (e.g., sending help to a specific location).

Key components involved in the Location ecosystem include the UE, which must support the necessary positioning capabilities; the MCX server, which hosts the LM function; and the location services (LCS) client, which may be internal or external to the MCX system. The location data is often consumed by dispatch consoles and command-and-control applications, which provide situational awareness to incident commanders. Security and privacy are critical: location information is sensitive and must be protected against unauthorized access. 3GPP TS 33.849 specifies security mechanisms for MCX, including authentication, authorization, and encryption of location data.

The evolution of the Location definition reflects the growing sophistication of mission-critical communications. Early definitions (Rel-8, Rel-9) were minimal, simply referring to a "specific set of coordinates." By Rel-12, the definition expanded to include geographical information such as GPS coordinates or local data like Cell ID or country. Rel-15 introduced a more concise wording, focusing on the physical location of the MC service UE. Rel-16 added velocity and direction, acknowledging the need for dynamic tracking. Rel-18 further enriched the definition with additional attributes like geographic area labels, enabling more context-aware services. This progression mirrors the increasing demands of public safety and critical communications for precise, real-time location awareness.

Purpose & Motivation

The Location concept exists to provide accurate, real-time positioning information for Mission Critical Services (MCX), enabling dispatchers and incident commanders to track and coordinate field personnel effectively. In emergency situations, knowing the exact location of first responders is vital for their safety and for the success of the operation. Without standardized location reporting, MCX systems would lack a common framework for exchanging location data, leading to interoperability issues and fragmented situational awareness.

Historically, location information in cellular networks was primarily used for emergency call routing (e.g., E911 in the US) and basic commercial services. However, the unique requirements of mission-critical communications—such as high reliability, low latency, and prioritization—demanded a dedicated approach. The Location definition in 3GPP TS 22.280 and TS 23.280 was created to address these needs, ensuring that location data is timely, accurate, and secure. It also supports advanced features like geofencing, which can trigger actions when a UE enters or leaves a designated area, and integration with dispatch applications for map-based tracking.

The evolution of the definition over releases reflects the changing capabilities of UEs and networks. Early releases focused on basic coordinates, while later releases incorporated velocity, direction, and area labels to support richer applications. This progression ensures that MCX systems can leverage the full potential of modern positioning technologies, such as GNSS and network-based positioning, to deliver enhanced situational awareness. Ultimately, the Location concept is a cornerstone of mission-critical communications, directly contributing to the safety and efficiency of emergency response operations.

What changed in its specifications

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

TS 22.280Rel-18 → Rel-19

Rel-19 adds FRMCS Phase 5 changes to TS 22.280 Annexes A, B and C. It adds general requirements and removes or replaces several MCPTT, MCVideo and MCData requirements.

Full comparison in TS 22.280 →
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 (57 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change
  • Location Server integration to PLMN TS 23.280CR0093
Rel-16 5 changes
  • Change to Location Subscription for notification immediate TS 23.280CR0196
  • Location information reporting based on functional alias TS 23.280CR0203
  • Add location management sever URI to initial MC service UE configuration TS 23.280CR0186
  • Corrections to clauses in 10.9 Location Management (on-network) TS 23.280CR0211
  • Correction of emergency location triggering criteria TS 23.280CR0180
Rel-17 20 changes
  • Support the location services related use cases while operating in off-network mode TS 22.280CR0131
  • Additional details to the Location information report TS 23.280CR0243
  • Additional details to the Location information notification TS 23.280CR0244
  • Additional details to the Location report response TS 23.280CR0245
  • Additional details to the Location reporting procedures TS 23.280CR0246
  • Configuration location history reporting TS 23.280CR0251

+ 14 more changes

Rel-18 12 changes
  • MCGWUE 3GPP access network related location information management TS 23.280CR0300
  • Sharing location information across MC systems (functional model) TS 23.280CR0322
  • Sharing location information across MC systems (on-demand) TS 23.280CR0323
  • Sharing location information across MC systems (triggered) TS 23.280CR0324
  • Sharing location information across MC systems (subscription) TS 23.280CR0325
  • Sharing location information across MC systems (configuration) TS 23.280CR0326

+ 6 more changes

Rel-19 17 changes
  • MC service group ID(s) usage for location information request TS 23.280CR0532
  • Location reporting information obtained from the PLMN operator (LTE) TS 23.280CR0569
  • Client-triggered location reporting cancel procedure TS 23.280CR0605
  • Requesting specific location information of MC service user on-demand or periodic TS 23.280CR0609
  • Amendments to location reporting configuration TS 23.280CR0610
  • Trigger override and cancel trigger override procedure for location reporting TS 23.280CR0617

+ 11 more changes

Rel-20 2 changes
  • Enhancing event triggered location reporting procedures TS 23.280CR0723
  • Corrections to location management TS 23.280CR0699

Defining Specifications

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

SpecificationTitleRelease
TS 22.280 vl00 Mission Critical Services Common Requirements Rel-21 read
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 29.199 3GPP TS 29.199 Rel-8 read
TS 33.849 ve00 3GPP Privacy Principles and Guidelines Rel-14 read