www.mobilevce.com © 2007 mobile vce. © 2007 mobile vce core 5: user interactions service...

9
www.mobilevce.co m © 2007 Mobile VCE

Upload: sophie-stanley

Post on 05-Jan-2016

227 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

Page 2: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

Core 5: User Interactions

Service Architecture

Eamonn O’NeillAcademic Coordinator

Jim GrimmettResearch Officer

Page 3: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

Page 4: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

What is the Architecture For?

Many apps and services available – how do consumers know about them?

How do companies get their apps and services into the hands of consumers?

How do consumers find appropriate apps and services for ad hoc tasks?

The answers to these questions are twofold:1. Better enable service/app discovery2. Better describe services/apps so we can filter

them appropriately

Page 5: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

Architecture Requirements

Architecture must• Better enable service/app discovery• Enable detailed service descriptions• Be usable by a variety of companies who may

wish to configure it in different ways• Interoperate with many technologies• Scalable• Reliable• Easy to use (zero conf?)

Page 6: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

How do we meet these Requirements?

Use open, cross-platform standards

Use peer-to-peer technologies to provide scaling and robustness

Introduce common, well defined service descriptions using semantic technologies

Integrate WAN and LAN networks to bridge existing service discovery technologies

Develop flexible software that can be configured in many different ways – e.g. authenticated vs open, walled garden vs internet, consumer driven content vs company content

Page 7: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

Architecture Overview

P2P Network

The Internet

Local Network

Local Network

Local Network

ServiceDirectory

UPnPBridge

TCP/IPConnection

UPnPConnection

Page 8: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

Business Models

Key features of the architecture are the Control Points it makes available

Control points allow a variety of stakeholders to decide how parts of the architecture are used (and by whom). This can result in very different business platforms

e.g. the end-to-end control of the Apple App Store vs the more open Android Marketplace are very different platforms operating across what is essentially a similar architecture

Page 9: Www.mobilevce.com © 2007 Mobile VCE.  © 2007 Mobile VCE Core 5: User Interactions Service Architecture Eamonn O’Neill Academic Coordinator

www.mobilevce.com

© 2007 Mobile VCE

Thank you !

For further information please contact:

Dr Walter TuttlebeeE-mail: [email protected]: +44 1256 338604WWW: www.mobilevce.com