Deployment view

The deployment view is based on the mobile terminal realisation platform as introduced in Section 5.1. Also called an allocation structure, the deployment view assigns the software components of the UIAF to hardware-processing and communication elements. Allocation structures are a common way to describe this relation [17]. Especially in distributed systems, like the UIAF, this is of particular interest. Further it defines the technical basis for the scenario walkthrough.

Figure 84 shows the deployment view for the Multimedia Infotainer scenario. The four main devices in this illustration are the portal device (equipped by Mike), two user interface devices hosting several Device Agents (for the car and home locations) and a virtual server machine running the Multimedia Infotainer server side components. Their respective communication channels are indicated by the named associations (TCP sockets, UPnP discovery, HTTP / SOAP).

dep lo y m en t UIAF m obile term inal platform

« d e v i c e »

Virtual M achine - Linux

/ /

« e x e c u t i o n e n v i r o n m e n t »

Tom cat w e b s e r v e r - Infotainer

i n f o t a i n e r - s e r v e r . j a r ^ 1 « m a n i f e s t »

V

a

M ultim edia infotainer s e r v e r

T

H T T P / S O A P

1

« d e v i c e » portal d e v ic e « e x e c u t i o n e n v i r o n m e n t » J a v a ME JVM (e.g. CrE-ME U l A F . j a r i g T C P s o c k e t s / U P n P d i s c o v ^ v i n f o t a i n e r . i a r l à_m • m a n i f e s t » • m a n i f e s t » s

UIAF M ultim edia infotainer clien t

• • d e v i c e »

c a r u s e r in terface d e v ic e s (UMPC - WinXP)

• • e x e c u t i o n e n v i r o n m e n t » J a v a SE JVM - c a r u p n p - s e r v e r . j a r ^ 1--- r e m o t e - i n p u t . j a r g i I r e m o t e - a g e n t . j a n a i • • m a n i f e s t » _______________________^ « m a n i f e s t » < • • m a n i f e s t » '

a

a

a

U PnP au d io d e v ic e input d e v ic e s e r v e r - c a r a g e n t a g e n t T C P s o c k e t s / U P n P d i s c o v e r y K ^ • • d e v i c e »

hom e u s e r in terface d e v ic e s (high definition TV)

« e x e c u t i o n e n v i r o n m e n t » J a v a SE JVM - hom e u p n p - s e r v e r . j a r g !--- r e m o t e - a g e n t . j a r j « m a n i f e s t » / « m a n i f e s t » m a n i f e s t » ' £ V

a

a

a

U PnP w e b c o n te n t d e v ic e d e v ic e a g e n t a g e n t

Figure 55: UIAF mobile terminal platform scenario deployment view

The following list incorporates the detailed information necessary to understand the purpose of the different devices for the evaluation scenario:

Java SE JVM execution environment - The virtual server machine (Linux) and both user interface devices (car, home) are running a Java Virtual Machine (JVM) based on Java SE. This provides the execution environment for all assigned components as seen in the deployment view illustration. Details about the components on each of the devices are provided in the respective bullet points.

Virtual server machine (Linux) - The virtual machine provides the execution environment for all Multimedia Infotainer server side components involved in the scenario. Using a database, information about the current available media items is held available for the Multimedia Infotainer client residing on the portal device. Media items are either pre-stored or fetched from internet RSS feeds. The Multimedia Infotainer server is realised on top of an Apache tomcat Web server. Therefore the packed component

performed in the EU-IST MobiLife project, further details are not given as part of this thesis. Communication as already indicated with the Multimedia Infotainer client is assured through the HTTP / SOAP protocol.

Portal device - The portal device hosts the Multimedia Infotainer client arid the UIAF mobile terminal implementation package. For the selection of personalised multimedia content choices the Multimedia Infotainer client resides on the portal device. It communicates via the HTTP / SOAP interface with the Multimedia Infotainer server. The UIAF component packaged into the UlAF.jar inherits the functionalities of the DeaMon, DeGan and local Device Agents (e.g. text, xhtml and audio output). The DeaMon connects through a local interfacing mechanism with the Multimedia Infotainer and provides its mobile multimodality functionalities to it. The DeGan in this scenario provides an UPnP discovery adapter, allowing for environment situation detection of user interface devices. All components are executed inside the Java ME JVM. Through a Wireless LAN interface the portal device can perform its UPnP discovery and delivery or receive media items and user input via TCP sockets.

Car user interface devices - The car environment in this scenario is simulated by an ultra mobile PC (UMPC) allowing for touch screen input. Mentioned earlier it runs a Java SE JVM in order to host an UPnP server, audio Device Agent, and input Device Agent. The UPnP server packaged as upnp-server.jar essentially provides the capability of the device to announce its Device Agent descriptions to the network. During the scenario the user can select (news) media items using predefined navigation buttons or gestures. This functionality is provided by the input Device Agent packaged as remote-input.jar. Further in order to retrieve the news content, the UIAF being aware that the user is in the car, audio output is provided by the audio Device Agent packaged as remote-agent.jar. The communication channels used are the same as described for the portal device (TCP

sockets/UPnP discovery).

Home user interface devices - The home environment in this scenario is simulated by a normal mobile PC, providing a higher screen resolution as a mobile device. It therefore can be treated as a high definition TV set, including video and audio output. Similar to the car user interface device, it runs a Java SE JVM hosting an UPnP server packages as

upnp-server.jar, also providing same functionality. Additionally, a video and Web

content Device Agent is provided. During the scenario a user arrives at home, wanting to resume an earlier played video. With detection of the TV set and the user invoking the same video item the video is delivery to the video Device Agent. Further some Web content (e.g. on-line picture portal, such as flickr.com could provide previous stored pictures) can be selected in the Multimedia Infotainer application and delivered to the

Web content deivce agent. Both agents are packaged as remote-agent.jar, similar to the car user interface devices.

This concludes the deployment view. It is shown how the UIAF implementation and additional components are deployed in order to achieve the selected mobile terminal platform scenario. The scenario walk through of the next section demonstrates how the deployed UIAF behaviour during the scenario progress.

In document Mobile Multimodal User Interfaces. (Page 151-154)