1. Mixed Reality-aware Service
Architecture for Mobile
Environments
Ramon Alcarria, Augusto Morales, Tomas Robles, Edwin Cedeño
Technical University of Madrid, Spain

2. OUTLINE
Motivation
Mixed Reality as a Service
SDL Proposal
Architectural Proposal
Implementation
Summary and Conclusions

3. MOTIVATION
 Mixed Reality (MR) and
Augmented reality (AR) have
been emerging as novelty trends
as they allow more natural
interfaces between individuals
and their real life
environments
 Trends:
- In the near future, more real life
environments will be shaped by IoT.
- MR has become an alternatives for
creating user interfaces that fit specific
interaction requirements of the IoT

4. MOTIVATION
 Currently, AR/MR is being
consumed using static
applications (Layar, Wikitude)
Problem:
- External content integration
- Users’ content integration
 MobAR is the future reference
architecture for AR. However,
There are no reference
implementation

5. Mixed Reality as a Service
 As we stated, using MR-aware services for interacting with
ubiquitous computing offers advantages over stand-alone
applications.
 Instantiation Requirements for these sort of services
- Abstraction of actions
- Service instanciation and cooperation
- Service discovery
 We have to define a SDL or adapt a new one.
 A Reference architecture is needed!!!

6. Mixed Reality as a Service
Specific MR-aware service requirements
 MR services should describe human and machine events
as well as the actions they trigger in other real world
services.Instantiation Requirements for these sort of services
 it is essential from a MR-aware service perspective to
ensure space, time and process decoupling between
information producers and consumers.
 the mobile terminal architecture has to accurately bind
resources by analyzing which functionalities can be fulfilled
with tangible hardware or software resources.

7. Mixed Reality as a Service
Specific MR-aware service requirements
 MR-aware services have to match and support content
using standard web-technologies such as: XML and JSON
 The execution platform has to be capable of adjusting the
service workflow depending on these new data and trigger
MR or non-MR events in the own execution platform or
even in the infrastructure.

8. SDL PROPOSAL
Metadata:
Human Interface:
Logical Description:
<?xml version="1.0" encoding="UTF-8"?>
<view_master>
<view_metadata .../>
<view_human_interface>
<HIAC name="touchVirtualLamp" id="4323">
<mixreality>
<value name="InternalARlibrary" value=”virtualLamp.obj”
bind=”touchscreen” hwreq=”tscreen” defstate="true"/>
<value name="KLM/HTML" value=”” /> ...
<gest name="touchscreen" event=”touch” ...>
<cpoints>
<input event="patternDetected" value=""/>
<output event="touch" value=""/>
</cpoints>
...
<logical_description>
<task>
<Invoke activity="capturePattern"/>
<While condition="true">
<if capturePattern.output= "true">
<Invoke activity="readGPS"/>
<Invoke activity="invokeLight" /> ...
<activities>
<activity name = "readGPS" />
<invoke cmd= "getLastKnownLocation()"
type="externalmr" />
<output event="locationGPS" value="" />
</activity>
<activity name = "invokeLight">
...
<activity name ="capturePattern">
<invoke cmd="AugRealityCameraAPI()" type=internal />
<output event="patternDetected" value="" /> ...
</activities>
</task>
<cpoint>
<input name="touchVirtualLamp.touch"/> ...
<output name="capturePattern.patternDetected" /> …

9. ARQUITECTURE PROPOSAL

10. IMPLEMENTATION
In order to validate the architecture, we have developed a prototype that has been
tested using a Samsung Nexus S, running OS Android 2.3.7 version and a Samsung
Galaxy Tab running Android 3.1. We used the Qualcomm AR libraries for
recognizing image patters

11. SUMMARY AND CONCLUSIONS
 MR capabilities, which do exist in current mobile devices via
stand-alone applications, can be enriched through services.
 Hence, we have also proposed a SDL for these new MR-
aware services, and defined a mobile architecture for
supporting them.
 We validated and tested our architecture using a real
execution environment
 In future research, we will evaluate the adaptation of the
proposed SDL to existing SDL languages such as BPEL or
BPMN. We will also face the problem of distributed MR
service scenarios