1 / 5

Contextual Multi-Device Delivery

This document explores the intricacies of multi-device content delivery, focusing on its benefits and limitations. Key advantages include device-specific downscaling, version selection, and content transcoding tailored to individual devices. However, challenges like diminished user experience and loss of engagement persist. As users navigate through diverse computing environments, content delivery must prioritize user preferences and dynamic resource availability. This comprehensive overview outlines essential considerations for optimizing service architecture and maximizing effectiveness across various devices.

raoul
Télécharger la présentation

Contextual Multi-Device Delivery

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. Contextual Multi-Device Delivery Venu Vasudevan Motorola Labs venuv@labs.mot.com

  2. Single-Device Contextual Delivery : Benefits and Limitations • Benefits: Device-specific downscaling of content • Select device-specific content version • Device-specific content transcoding • Limitations: loss of “wow” factor • Even the cleverest miniaturization makes the service less compelling • The multi-device delivery option • User travels thru computing islands with multiple devices • Users have multi-device ‘toolbelts’ • Service architecture treats computing island as single logical device

  3. Components of multi-device orchestration • axioms • All-IP network, multiple access networks • Peer-to-peer (not c/s), not necessarily HTTP • Proxy (“edge box”) in the path • Devices as containers of downloadable plug-ins • aggregate capabilities of a device neighborhood • inherent capabilities (model#, o/s) • resource availability (e.g. sound card) • environmental device attributes (e.g. device orientation) • user and content provider orchestration preferences • Content provider - content re-targeting hints • User preferences - demultiplexing vs. transcoding, choice of access network • allowable device plug-ins

  4. CC/PP based Personal Mobility Solution Internet RTP multimedia Stream (video+audio) Transcoder Cloud Service Orchestrator Neighborhood Topology User Preferences Web Services Collage Composer Operator Discovery User Activation CC/PP (over SIP) – neighborhood capabilities and availability SIPLets- dynamic device personalities Office Parking Lot Car

  5. CC/PP Perspective • CC/PP model needs to include “pluggable” proxies • Current proxies assume fixed operator set • Express capabilities of groups of devices • Support delivery to a user, not a device • Metadata with shorter lifespans • Resource availability (e.g. availability of audio card) can change rapidly • Expressing non-conventional device metadata • e.g. device orientation • Support model of devices as containers

More Related