Device-Aware Mobile Service Discovery with Ranking

Eyhab Al-Masri

Contents

Architecture1

Click to add Title2

Click to add Title3

Click to add Title4

Experimental Environment

Server

Database (registry)

Simulators

General Overview

Server has to be able to handle requests and sends responses

Server Internet Mobile Device

HTTPrequest

response

1. Identify Requesting Device (Capabilities)

i.e. Browser, Markup Language,Image Capabilities

2. Locate Mobile Page (.aspx) – use sessions

3. Perform search process and prepare

an appropriateresponse message

URLUser AgentHeader Info

sessions

Database Registry

In order to simulate this discovery model, it is important to have a working database that contains at least: serviceName, serviceKey serviceDescription businessName Actual service implementation (i.e. WSDL)

Database Registry

We used XMethods.net to collect services

100 services were collected

Information was stored into a local database (*.mdb)

Services were picked based on functionality

Mobile Device Supported Attributes

Although there are defined mobile device capabilities (i.e. CC/PP), service providers have no way of including recommended device capabilities (i.e. WSDL file, etc…)

Supported Device Attributes

For each service collected (from XMethods.net or services table), generate random device attributes.

Simulators

Simulators can be devices, computer programs, or systems that: operates or behaves like a given system

Mobile Device Profile/Capabilities

In order to enhance service discovery based on mobile device capabilities, we need:

Collect device capabilities Process device capabilities Perform service matching Perform service ranking

Collect Device Capabilities

Browser based: Collect information via browser, Send device profile via HTTP request (user

agent)

Native Create a client application that handles

collection of device profile offline

Collect Device Capabilities

Browser-Based Why?

• Less overhead,

• Can take advantage of server session objects to store device profile capabilities (no space required on mobile device)

• Compatible through any browser (HTML or WAP)

• No need for any client applications to be installed (less work and processing for clients)

Collect Device Capabilities

Clients access a webpage “detect.aspx”

Identify device

capabilities

Sto

re e

nti

re p

rofi

le o

n

serv

er(u

sin

g s

essi

on

ob

ject

)

ran

ked

res

ult

s

search,aspx

Service Matching

Look for services that match a given

keyword(s)

Matching

Prepare a list of services to

be ranked

Service Ranking

Detect.aspx collects device capabilities and stores them in a session

Search.aspx performs a keyword matching for serviceName

For each matching service, retrieve service capabilities (from DB)

Load device capabilities from session For each matching service, compare

retrieved service capabilities with device capabilities

A scoring function is used to determine the “relevance” of a matching service

Service Matching Example

Demo

Demonstration

Microsoft Mobile Profile vs. CC/PP

Microsoft’s version of CC/PP is Mobile Profile

NumberOfSoftkeys MobileDeviceManufacturer MobileDeviceModel PreferredRenderingMime PreferredImageMime ScreenCharactersWidth ScreenCharactersHeightScreenPixelsHeight ScreenPixelsWidthSupportsCss MaximumHrefLengthCanInitiateVoiceCallIsColorInputTypeSupportsBold

NumberOfSoftKeysVendorModelPush-Accept (text + images)

ScreenSizeChar (width+height)

ScreenSize

SupportsCSSURLRequestLengthVoiceInputCapableColorCapableKeyboardTextFormatBoldSupported

Summary

Search and Discover

HTTP Web Server

Mobile Service Directory

Mobile Device

Wireless Carrier

(5) send relevant results string

(1) cl

ient

invo

kes

GUI an

d

perf

orm

s se

arch

req

uest

(2) request is

forwarded to server

to d

irecto

ry

(3) connect

(4) e

xecu

te s

earc

h

Search and Discover

HTTP Web Server

Mobile Service Directory

Mobile Device

Wireless Carrier

(5) send relevant results string

(1) cl

ient

invo

kes

GUI an

d

perf

orm

s se

arch

req

uest

(2) request is

forwarded to server

to d

irecto

ry

(3) connect

(4) e

xecu

te s

earc

h

Technologies

JAVA

ASP.NET

VB.NET (Mobile Controls)

IIS 6.0

Regular or WAP Browser

Conclusion

1Device capabilities can play major role in enhancing service discovery

2

It is essential to include device capabilities into the service matching process

3

A ranking mechanism can significantly improve search results and output desired or compatible services within top results

Q & A

Thank you