1 / 15

From data delivery to control: rich presence and multimedia

From data delivery to control: rich presence and multimedia. Henning Schulzrinne, Ron Shacham, Xiaotao Wu Columbia University, New York Wolfgang Kellerer, Srisakul Thakolsri DoCoMo Euro-Labs, Munich. Old problems and approaches: efficient codecs ubiquitous reachability

jesusi
Télécharger la présentation

From data delivery to control: rich presence and multimedia

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. From data delivery to control: rich presence and multimedia Henning Schulzrinne, Ron Shacham, Xiaotao Wu Columbia University, New York Wolfgang Kellerer, Srisakul Thakolsri DoCoMo Euro-Labs, Munich

  2. Old problems and approaches: efficient codecs ubiquitous reachability audio/video synchronization network-layer mobility quality-of-service APIs and middleware New problems: controlled reachability spam cell phone ringing in lecture service availability information privacy service & personal mobility service creation by non-experts Multimedia systems problems

  3. Columbia CINEMA project • Multimedia system • standards-based (IETF): SIP, GEOPRIV • inter-domain (security, naming, …) • Rich presence  control reachability • Location-based services • integration of multiple indoor & outdoor location sensors • user-controlled privacy • Using presence and events as system glue • integrates service location (SLP, RDF) • Mobility: terminal, personal, service, session

  4. Rendezvous protocol lets users find each other by only knowing a permanent identifier Mobility enabler: personal mobility one person, multiple terminals terminal mobility one terminal, multiple IP addresses session mobility one user, multiple terminals in sequence or in parallel service mobility services move with user SIP as service enabler

  5. Context-aware communication • context = “the interrelated conditions in which something exists or occurs” • anything known about the participants in the (potential) communication relationship • both at caller and callee:

  6. GEOPRIV and SIMPLE architectures rule maker rule interface target location server location recipient notification interface publication interface GEOPRIV SUBSCRIBE presentity presence agent watcher SIP presence PUBLISH NOTIFY caller callee SIP call INVITE INVITE

  7. RPIDS: rich presence data • Basic IETF presence (CPIM) only gives you • contact information (SIP, tel URI) • priority • “open” or “closed” • Want to use presence to guide communications watcher everything PA PUA watcher "vague" PUBLISH watcher NOTIFY CPL <activity> <place-type> <privacy> <mood> <sphere> INVITE

  8. Policy relationships common policy geopriv-specific presence-specific future RPID CIPID

  9. Location-based services in CINEMA • Initial proof-of-concept implementation • Integrate devices: • lava lamp via X10 controller  set personalized light mood setting • Pingtel phone  add outgoing line to phone and register user • painful: needs to be done via HTTP POST request • stereo  change to audio CD track based on user • Sense user presence and identity: • GPS • passive infrared (PIR) occupancy sensor • magnetic swipe card • ibutton • BlueTooth equipped PDA • IR+RF badge (in progress) • RFID (in progress) • UWB (future) • biometrics (future)

  10. Location-based IM & presence

  11. Service (profile) mobility • In the future, people will use many communication devices, both personal (PDA, desk phone) and public (e.g., workplace, hotel), that may be personalized • Examples of personalization: • Application configuration: SIP proxy and authorization settings • Address books & speed dial numbers • Call logs • Emergency numbers • Move from explicit synchronization (syncML, Palm) to automated profile & data migration • We built a SIP event-based architecture that configures and de-configures devices based on a user’s location and other context information

  12. Room Room SLP Service Agent SLP Service Agent SrvReg SrvReg SLP Directory Agent SrvReq SrvRply TFTP HTTP Device Controller (DC) REGISTER (Room Presence Updates) REGISTER (Room Presence Updates) Scripts Room SUB/NOTIFY/Updates Soft phone SUB/NOTIFY/Updates SIP Proxy/ Registrar Room Presence User Profiles Service Mobility Architecture

  13. Service creation • Tailor a shared infrastructure to individual users • traditionally, only vendors (and sometimes carriers) • learn from web models

  14. Service creation environment for CPL and LESS

  15. Conclusion • Old model: communication as end • reachability as supreme goal • New model: user-controlled, context-sensitive • Getting close to having tool set that allows building such services

More Related