update abstract and teaser
This commit is contained in:
parent
822920ae70
commit
f87bca98c1
File diff suppressed because one or more lines are too long
Before Width: | Height: | Size: 299 KiB After Width: | Height: | Size: 295 KiB |
30
main.tex
30
main.tex
@ -1,7 +1,7 @@
|
||||
% $Id: template.tex 11 2007-04-03 22:25:53Z jpeltier $
|
||||
|
||||
%\documentclass{vgtc} % final (conference style)
|
||||
\documentclass[review]{vgtc} % review
|
||||
\documentclass{vgtc} % final (conference style)
|
||||
%\documentclass[review]{vgtc} % review
|
||||
%\documentclass[widereview]{vgtc} % wide-spaced review
|
||||
%\documentclass[preprint]{vgtc} % preprint
|
||||
%\documentclass[electronic]{vgtc} % electronic version
|
||||
@ -115,15 +115,17 @@
|
||||
\teaser{
|
||||
\centering
|
||||
\includesvg[inkscapelatex=false, width=\linewidth]{figures/teaser.drawio.svg}
|
||||
\caption{AURA workflow overview.}
|
||||
\caption{Overview of AURA's role during multi-application deployment.
|
||||
a) An AURA-based system scans the room, and independently launched applications submit their spatial and behavioural requirements through AURA manifests.
|
||||
b) The AURA-powered Head-Mounted Display (HMD) identifies suitable components in the environment and, with user input, assigns them to each application by creating dedicated ambients (e.g., $\alpha_1$, $\alpha_2$). This allows Application 1 and 2 to coexist within the same room.}
|
||||
\label{fig:teaser}
|
||||
}
|
||||
|
||||
%% Abstract section.
|
||||
\abstract{
|
||||
Augmented Reality (AR) enables digital content to be integrated with the physical world across diverse platforms, including projection systems, head-mounted displays, and mobile devices. However, current AR frameworks lack a standardized, platform-independent model for describing spatial structure, interaction logic, and shared resource usage. This fragmentation limits interoperability, complicates cross-platform deployment, and hinders the coexistence of multiple AR applications within the same environment.
|
||||
|
||||
We introduce AURA {-} the \textit{\textbf{A}ugmented Reality \textbf{U}nified \textbf{R}epresentation \textbf{A}rchitecture}, centered on a JSON-LD-based manifest for defining how AR applications declare their spatial and behavioural models {-} including components, agents, and event-driven logic {-} it enables independent applications to coexist within scoped spatial containers (\textit{ambients} and \textit{worlds}), relying on system-managed shared memory for safe data exchange. It also supports heuristic-based modelling for dynamic states and interactions, paving the way for adaptive AR systems. Through examples, we demonstrate how AURA facilitates modular development, scalable coordination, and cross-platform interoperability.
|
||||
Augmented Reality (AR) integrates digital content into physical space across diverse platforms, including projection systems, head-mounted displays, and mobile devices. However, current AR frameworks lack a standardized, platform-independent method for applications to declare their spatial and system-level requirements. This fragmentation complicates cross-platform development, and hinders the coexistence of multiple AR applications within the same environment.
|
||||
|
||||
We introduce AURA {-} the \textbf{A}ugmented Reality \textbf{U}nified \textbf{R}epresentation \textbf{A}rchitecture {-}, which defines a manifest format through which applications specify their spatial components, interactive elements, participating agents, and required system resource needs. AURA enables multiple applications to run concurrently by assigning them to scoped containers and managing their access to shared physical surfaces, regions and devices. AURA also supports dynamic, context-aware behaviour via event-driven triggers and system-mediated data exchange at runtime. Through examples, we demonstrate how AURA facilitates cross-platform development and application interoperability.
|
||||
} % end of abstract
|
||||
|
||||
%% Keywords that describe your work. Will show as 'Index Terms' in journal
|
||||
@ -153,19 +155,17 @@ Augmented Reality (AR) integrates digital content with real-world environments t
|
||||
|
||||
Most existing AR development platforms, such as Unity's XR Interaction Toolkit and Unreal Engine's AR APIs, are geared toward building single-application experiences. These tools provide abstractions for tracking, rendering, and input, but lack a standardized model for representing application structure, coordinating access to physical components, or supporting interaction logic across applications. This gap limits scalability, complicates cross-platform deployment, and hinders the development of multi-application AR environments.
|
||||
|
||||
We introduce AURA {-} the \textit{\textbf{A}ugmented Reality \textbf{U}nified \textbf{R}epresentation \textbf{A}rchitecture} {-} a conceptual and declarative approach to structuring AR applications and coordinating their behaviour within shared spatial environments. At its core, AURA introduces a manifest format that allows applications to formally declare their spatial and behavioural requirements, including entities, components, agents, and interaction logic. The system, in turn, defines the runtime context: available physical components, spatial subdivisions (\textit{ambients} and \textit{worlds}), and device mappings.
|
||||
We introduce AURA {-} the \textbf{A}ugmented Reality \textbf{U}nified \textbf{R}epresentation \textbf{A}rchitecture {-} a different approach to structuring AR applications and coordinating their behaviour within shared spatial environments. At its core, AURA introduces a manifest format that allows applications to formally declare their spatial and behavioural requirements, including entities, components, agents, and interaction logic. The system, in turn, defines the runtime context: available physical components, spatial subdivisions (\textit{ambients} and \textit{worlds}), and mappings between devices and applications.
|
||||
|
||||
AURA adopts terminology and structuring principles inspired by the Entity-Component-System (ECS) architecture, widely used in interactive software. In this model, entities are abstract units composed of components (which represent tracked surfaces, spatial areas, or physical devices), while the system observes and governs their runtime states and transitions. This model promotes modularity, reusability, and a clear separation between application logic and physical deployment.
|
||||
AURA adopts terminology and structuring principles inspired by the Entity-Component-System (ECS) architecture, widely used in interactive software. In AURA architecture, entities are logical sets of components (which represent tracked surfaces, spatial areas, or physical devices), while the system observes the physical space and mediates application runtime and agents' interactions. This model promotes modularity, reusability, and a clear separation between application logic and physical deployment.
|
||||
|
||||
Importantly, AURA does not enforce a single global spatial model. Instead, each application is bound to an \textit{ambient}-scoped view, enabling coexistence through a layered abstraction of space. The \textit{unified} nature of AURA refers to its consistent runtime contract: all applications interface with the system using a common schema, while the system tracks shared state and coordinates access to components without requiring direct inter-application communication.
|
||||
Importantly, AURA does not enforce a single global spatial model. Instead, each application is bound to an ambient-scoped view, enabling coexistence through a layered abstraction of space. The \textit{unified} nature of AURA refers to its consistent runtime contract: all applications interface with the system using a common schema, while the system tracks general interaction and coordinates access to components without requiring direct inter-application communication.
|
||||
|
||||
To ground this model, \cref{fig:teaser} presents a conceptual overview of the application onboarding workflow in AURA. Applications independently submit their manifests to the system, which identifies compatible spatial components. Users then map applications to the environment through the system interface, establishing shared state and surface mappings while preserving modular execution.
|
||||
|
||||
AURA enables:
|
||||
To ground the architecture in a tangible scenario, \cref{fig:teaser} illustrates how AURA supports runtime coordination across multiple independent AR applications. In (a), two applications submit their manifests to an AURA-based system, which parses their spatial and behavioural requirements. In (b), the system creates an ambient for each application, which maps them within the physical space {-} ensuring non-conflicting use of shared surfaces {-} while enabling the user to intervene in the mapping and then to interact with both applications in the same room. AURA enables:
|
||||
\begin{itemize}
|
||||
\item Standardized application structure definitions, including components, entities, interaction logic, and resource constraints;
|
||||
\item Concurrent execution of multiple AR applications in shared physical environments without conflict;
|
||||
\item Event- and request-driven data exchange via structured, system-managed memory tied to spatial components.
|
||||
\item Standardized application structure definitions, including components, entities, interaction logic, devices, and performance requirements;
|
||||
\item Concurrent execution of multiple AR applications in shared physical environments without conflict, enabling coexistence;
|
||||
\item Event- and request-driven data exchange via structured, system-managed memory tied to spatial components, enabling interoperability.
|
||||
\end{itemize}
|
||||
|
||||
In this paper, we present the core AURA specification and demonstrate how it enables scalable, interoperable, and modular AR systems. We focus on its support for application isolation, declarative interaction modelling, and conflict-free coordination of shared resources. Future work will explore runtime extensions such as probabilistic reasoning, formal validation, and distributed orchestration across heterogeneous AR platforms.
|
||||
|
Loading…
x
Reference in New Issue
Block a user