Uploaded on

 

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
24
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Aquí podrías hablar de todo lo que sabemos, que la AR y la MR están creciendo por la utilización de teléfonos. Explica también la diferencia entre AR y MR y que la usarás indistintamente por facilidad -ya no se necesitan aparatos caros -está casi pervasiva y está extendiendose a muchos escenarios Ej. THOFU Aquí puedes hablar este párrafo: Today, applications such as Wikitude, Layar and WordLens, offer an efficient and proven AR experience to end users. Despite this, their proprietary and close nature can slow down their adaptation time to customized business processes and communication systems. Furthermore, taking into consideration future IoS scenarios, these stand-alone applications will hardly integrate with service policies (concerning privacy, accountability, QoS and so on) the users could impose to the mobile device. On the other hand, the IoT stands for ubiquitous sensorised environments, so users may wish to invoke actions across different and unrecognized devices, networks, and services. Thus, current stand-alone applications will not be sufficient to deliver the desired experience future IoS platforms envisage
  • Aqui puedes hablar de la motivación de integrar tanto contenido que sea creado externamente como contenido que ya yo tenga. Además de esto que se puedan consumir todo el contenido a mi alrededor (QUIZÁS ddentro de una PAN) fácilmente a través de una arquitectura abierta de servicios. Como hay hoy en día con los webservices (tipo mashup) El segundo punto es que la OMA está definiendo una arquitectura de referencia pero aún no está lista. Este párrafo te ayudaría: Content standardization is one of the main issues in AR environments. Currently, there are many languages, such as KLM and ARML, for representing Point of Interest (POI), superposed images, geo-location information and so on. Thus, AR delivery platforms need to process information arriving from different sources and data formats. Current AR stand-alone applications indeed handle these processes, but at the same time introduce a tight integration with the mobile platform. On the other hand, factors concerning scalability, fragmentation between different mobile platforms and slow application development, can limit flexibility of services expected by future IoS scenarios. In conclusion, there are still requirements current AR technologies have not addressed yet in order to deploy MR platforms and MR-aware services connected to the future Web of Things
  • Aquí puedes definir a grandes rasgos qué necesita la realidad mixta para ser tratada como un servicio… creo que aquí vas sobrado, porque puedes hablar de todo lo de mio, de que se necesita definir el servicio, enlazarlo en tiempo de ejecución, abstraerlo etc… y que no hay una arquitectura de referencia..
  • Aquí están los requisitos específicos, y vamos mucho más al grano que la slide anterior, si te parece bien puedes fusionar la anterior con esta, y la que sigue ya es casi lo mismo… pero es importante decir que estos requisitos los definimos nosotros y que nadie lo había hecho, o sea que es una contribución por si sola
  • Aquí puedes definir a grandes rasgos qué necesita la realidad mixta para ser tratada como un servicio… creo que aquí vas sobrado, porque puedes hablar de todo lo de mio, de que se necesita definir el servicio, enlazarlo en tiempo de ejecución, abstraerlo etc… y que no hay una arquitectura de referencia..
  • Aquí describes las partes del sdl, Y EXPplicas que está en XML y por qué lo hicimos así… The SDL consists of three service views or main subsections. Each view represents a set of parameters that define the service in response to certain criteria. The SDL syntax is based on XML, which is currently suitable for processing in most of the mobile devices and provides modularity and standard mechanisms for modifying the document. Thus, each view is described as a parent tag, and they enclose all the required information for being processed by the mobile device or the supporting infrastructure.
  • Aquí explicar qué hace cada cosa… a grandes rasgos, no es muy distinto a mio! Ni al paper del ucamii
  • Aquí explicas el prototipo… qué librerías se utilizaron etc… el proceso de bajar la textura meterla en .h compilarla usando el NDK de android etc… mencionas la dificultad para la parte gráfica y que actualmente es un poco difícil Concerniente a la gráfica es ilustrativa y puedes decir que la arquitectura no tiene por qué sobrecargar el sistema aún cuando hayan muchas actividades, eso sí puedes hablar de la dificultad que requeriría hacer un motor bpel…
  • Las conclusiones son básicamente descriptivas, y creo que le puedes meter chicha en la ejecución de servicios distribuidos…

Transcript

  • 1. Mixed Reality-aware ServiceArchitecture for MobileEnvironmentsRamon Alcarria, Augusto Morales, Tomas Robles, Edwin CedeñoTechnical 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) andAugmented reality (AR) havebeen emerging as novelty trendsas they allow more naturalinterfaces between individualsand their real lifeenvironments Trends:- In the near future, more real lifeenvironments will be shaped by IoT.- MR has become an alternatives forcreating user interfaces that fit specificinteraction requirements of the IoT
  • 4. MOTIVATION Currently, AR/MR is beingconsumed using staticapplications (Layar, Wikitude)Problem:- External content integration- Users’ content integration MobAR is the future referencearchitecture for AR. However,There are no referenceimplementation
  • 5. Mixed Reality as a Service As we stated, using MR-aware services for interacting withubiquitous computing offers advantages over stand-aloneapplications. 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 ServiceSpecific MR-aware service requirements MR services should describe human and machine eventsas well as the actions they trigger in other real worldservices.Instantiation Requirements for these sort of services it is essential from a MR-aware service perspective toensure space, time and process decoupling betweeninformation producers and consumers. the mobile terminal architecture has to accurately bindresources by analyzing which functionalities can be fulfilledwith tangible hardware or software resources.
  • 7. Mixed Reality as a ServiceSpecific MR-aware service requirements MR-aware services have to match and support contentusing standard web-technologies such as: XML and JSON The execution platform has to be capable of adjusting theservice workflow depending on these new data and triggerMR or non-MR events in the own execution platform oreven in the infrastructure.
  • 8. SDL PROPOSALMetadata: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. IMPLEMENTATIONIn order to validate the architecture, we have developed a prototype that has beentested using a Samsung Nexus S, running OS Android 2.3.7 version and a SamsungGalaxy Tab running Android 3.1. We used the Qualcomm AR libraries forrecognizing image patters
  • 11. SUMMARY AND CONCLUSIONS MR capabilities, which do exist in current mobile devices viastand-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 forsupporting them. We validated and tested our architecture using a realexecution environment In future research, we will evaluate the adaptation of theproposed SDL to existing SDL languages such as BPEL orBPMN. We will also face the problem of distributed MRservice scenarios