1 / 22

Device-Aware Mobile Service Discovery with Ranking

Device-Aware Mobile Service Discovery with Ranking. Eyhab Al-Masri. 1. 2. 3. 4. Architecture. Click to add Title. Click to add Title. Click to add Title. Contents. Experimental Environment. Server Database (registry) Simulators. URL User Agent Header Info. General Overview.

Sharon_Dale
Download Presentation

Device-Aware Mobile Service Discovery with Ranking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Device-Aware Mobile Service Discovery with Ranking Eyhab Al-Masri

  2. 1 2 3 4 Architecture Click to add Title Click to add Title Click to add Title Contents

  3. Experimental Environment • Server • Database (registry) • Simulators

  4. URL User Agent Header Info General Overview • Server has to be able to handle requests and sends responses sessions 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 appropriate response message HTTP request response Server Internet Mobile Device

  5. 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)

  6. 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

  7. 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…)

  8. Supported Device Attributes • For each service collected (from XMethods.net or services table), generate random device attributes.

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

  10. 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

  11. 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

  12. 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)

  13. Collect Device Capabilities Store entire profile on server (using session object) search,aspx ranked results Clients access a web page “detect.aspx” Identify device capabilities

  14. Service Matching Matching Look for services that match a given keyword(s) Prepare a list of services to be ranked

  15. 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

  16. Service Matching Example

  17. Demo Demonstration

  18. Microsoft Mobile Profile vs. CC/PP • Microsoft’s version of CC/PP is Mobile Profile NumberOfSoftKeys Vendor Model Push-Accept (text + images) ScreenSizeChar (width+height) ScreenSize SupportsCSS URLRequestLength VoiceInputCapable ColorCapable Keyboard TextFormatBoldSupported NumberOfSoftkeys MobileDeviceManufacturer MobileDeviceModel PreferredRenderingMime PreferredImageMime ScreenCharactersWidth ScreenCharactersHeight ScreenPixelsHeight ScreenPixelsWidth SupportsCss MaximumHrefLength CanInitiateVoiceCall IsColor InputType SupportsBold

  19. Summary

  20. Technologies • JAVA • ASP.NET • VB.NET (Mobile Controls) • IIS 6.0 • Regular or WAP Browser

  21. 1 2 3 It is essential to include device capabilities into the service matching process A ranking mechanism can significantly improve search results and output desired or compatible services within top results Device capabilities can play major role in enhancing service discovery Conclusion

  22. Q & A Thank you

More Related