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

Glossary term · Services

AR data

Augmented Reality Data

Services →

AR data is the data generated by the AR Runtime and accessible via API to AR/MR applications, including pose information, sensor outputs, and camera outputs, enabling immersive AR experiences.

Introduced
Rel-17
Where
Services › Codecs
Specifications
2 specs
AR data Description Purpose What changed Neighbours Specifications

Description

AR data, as defined in 3GPP specifications such as TS 26.264 and TS 26.998, refers to the data generated by the Augmented Reality (AR) Runtime that is made accessible to AR/MR applications through an API. This data includes a variety of information essential for AR experiences, such as pose information (the position and orientation of the device or user), sensor outputs (e.g., from accelerometers, gyroscopes, and magnetometers), and camera outputs (video frames from the device's cameras). The AR Runtime is a software layer that manages AR processing, including tracking, mapping, and rendering, and exposes this data to applications via standardized APIs.

The AR data concept is crucial for enabling AR applications to function correctly. For example, a pose provides the spatial relationship between the device and the environment, which is necessary for rendering virtual objects in the correct position. Sensor outputs provide motion and orientation data that can be used for tracking and stabilization. Camera outputs provide the visual context for the AR scene, which can be used for computer vision tasks such as plane detection and object recognition. By standardizing the API for accessing AR data, 3GPP enables interoperability between AR applications and AR runtimes from different vendors.

In the 3GPP context, AR data is relevant for services that involve AR communication over cellular networks. For instance, in an AR conference, the AR data from one user's device might be transmitted to another user's device to enable a shared AR experience. The AR data may also be processed by the AR Application Server to provide services such as AR content mixing or remote rendering.

The AR data is generated by the AR Runtime, which is typically implemented on the UE. The AR Runtime may use various sensors and cameras available on the device, as well as network-based information (e.g., from location services), to generate the AR data. The API for accessing AR data is defined in 3GPP specifications, ensuring that applications can rely on a consistent interface. This is particularly important for AR applications that need to work across different devices and networks.

AR data was introduced in Release 17 as part of the work on AR/MR media processing and delivery. The definition has remained unchanged through Release 19, indicating a stable concept. The AR data concept is foundational for the development of AR services in 3GPP networks, and it is expected to be further refined as AR technology evolves.

Purpose & Motivation

The AR data concept was created to standardize the way AR applications access the data generated by the AR Runtime. Before this, AR applications had to rely on proprietary APIs or platform-specific implementations, which hindered interoperability and portability. By defining AR data and its API in 3GPP specifications, the industry can ensure that AR applications can work across different devices and networks, fostering a vibrant AR ecosystem.

The AR data concept addresses the need for a clear separation between the AR Runtime (which handles low-level AR processing) and the AR application (which provides the user-facing experience). This separation allows AR Runtime vendors to innovate in tracking and rendering, while AR application developers can focus on creating compelling experiences. The standardized API ensures that applications can access essential data such as pose, sensors, and camera outputs without needing to understand the underlying hardware.

In the context of 3GPP networks, AR data is important for enabling AR communication services. For example, in a remote assistance scenario, the AR data from a field worker's device (including camera and pose) can be transmitted to a remote expert, who can then provide guidance. The IMS data channel provides a standardized transport for such data. The AR data concept thus supports the broader goal of integrating AR into 5G and beyond, enabling new immersive services.

What changed in its specifications

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

TS 26.264Rel-18 → Rel-19

Rel-19 added avatar representation format support, negotiation via reliable data channel, transport via second HTTP sub-protocol, and Base Avatar Repository management API.

Full comparison in TS 26.264 →

Release Timeline

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-17 Initial

Initial definition: 'Data generated by the AR Runtime that is accessible through API by an AR/MR application such as pose information, sensors outputs, and camera outputs.' This established the concept of AR data and its API.

Definition carried over unchanged from Rel-17.

Definition carried over unchanged from Rel-17.

Defining Specifications

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

SpecificationTitleRelease
TS 26.264 vj41 IMS Conversational Augmented Reality Services Rel-19 read
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19 read