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

Glossary term · Services

Location agnostic service experience

Location Agnostic Service Experience

Services →

Location agnostic service experience is a service where the user's interaction and content are independent of their physical location, focusing instead on a distant or non-existent place.

Introduced
Rel-19
Where
Services
Specifications
2 specs
Location agnostic service experience Description Purpose Neighbours Specifications

Description

Location agnostic service experience is a concept introduced in 3GPP Rel-19 to categorize how users interact with services in relation to their physical location. It describes a scenario where the user interaction and the information provided by a service have little or no relation to the physical location in which the user accesses the service. Instead, the service delivers interaction and information concerning either a distant physical location or a non-existent (virtual) location. This definition is specified in 3GPP TS 22.156 and TS 22.856, which address service requirements and experiences for future 5G and beyond systems.

In practical terms, a location agnostic service experience occurs when a user consumes content or interacts with an application that is not tied to their immediate surroundings. Examples include watching a live stream of an event happening in another city, playing an online game set in a fictional world, participating in a video conference with participants from different countries, or browsing a social media feed with posts from around the globe. In all these cases, the user's physical location is irrelevant to the service experience; the service could be accessed from anywhere with sufficient connectivity, and the content remains the same.

The concept is important for 5G and future network design because it helps classify service requirements and optimize network resources accordingly. For location agnostic services, the network does not need to provide location-specific information or adapt the service based on the user's whereabouts. This simplifies service delivery and allows the network to focus on other quality parameters such as bandwidth, latency, and reliability. It also has implications for privacy, as the service does not require knowledge of the user's location, reducing the need for location data collection and associated privacy risks.

From an architectural perspective, location agnostic service experience is one end of a spectrum. The other end is location related service experience, where the service is highly dependent on the user's physical location (e.g., augmented reality navigation, local restaurant recommendations, or proximity-based social networking). Most services fall somewhere between these two extremes, but the classification helps standardize how networks and applications handle location information. The 3GPP specifications 22.156 and 22.856 define requirements and use cases for these service experiences, guiding how the 5G system should support them.

For network operators and service providers, understanding whether a service is location agnostic or location related affects decisions about edge computing, content caching, and network slicing. Location agnostic services can be hosted centrally or at any edge node without regard to user proximity, while location related services often benefit from multi-access edge computing (MEC) and localized content delivery. The concept also influences how quality of experience (QoE) is measured and reported, as location agnostic services may have different QoE metrics compared to location-dependent ones.

Purpose & Motivation

The concept of location agnostic service experience was introduced to provide a clear framework for classifying services based on their relationship to the user's physical location. Before Rel-19, 3GPP specifications primarily focused on technical capabilities such as data rate, latency, and reliability, without explicitly categorizing services by their location dependency. As 5G networks evolved to support a wide range of applications—from immersive VR to industrial IoT—it became clear that location plays a crucial role in determining service requirements and network resource allocation.

By defining location agnostic service experience, 3GPP addresses the need for a common vocabulary that helps operators, service providers, and application developers understand when location information is relevant and when it is not. This classification enables more efficient network design: for location agnostic services, the network can avoid unnecessary location tracking, reduce signaling overhead, and simplify service delivery. It also helps in privacy protection, as services that do not need location data can be designed to operate without it, minimizing the risk of location privacy breaches.

The motivation also stems from the growing diversity of 5G use cases. Some services, like augmented reality (AR) navigation or local emergency alerts, are inherently location related and require precise, real-time location data. Others, like streaming video or online gaming, are largely location agnostic and can be delivered without location awareness. By distinguishing these categories, 3GPP provides a foundation for optimizing network slicing, edge computing deployment, and QoE management. The specifications 22.156 and 22.856 capture these requirements, ensuring that the 5G system can flexibly support both types of service experiences.

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-19 Initial

Initial definition introduced in 3GPP TS 22.156 and TS 22.856. The concept classifies services based on their relationship to the user's physical location, distinguishing location agnostic from location related service experiences to guide network design and resource allocation.

Defining Specifications

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

SpecificationTitleRelease
TS 22.156 vj20 Service requirements for the mobile metaverse Rel-19 read
TR 22.856 vj20 Feasibility Study on Localized Mobile Metaverse Services Rel-19 read