From data delivery to control: rich presence and multimedia

Henning Schulzrinne, Ron Shacham, Xiaotao WuColumbia University, New York

Wolfgang Kellerer, Srisakul ThakolsriDoCoMo Euro-Labs, Munich

Multimedia systems problems

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

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

SIP as service enabler

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

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:

time CPL

capabilities caller preferences

location location-based call routing

location events

activity/availability “rich” presence

sensor data (mood, bio) not yet, but similar in many aspects to location data

GEOPRIV and SIMPLE architectures

targetlocationserver

locationrecipient

rulemaker

presentity

caller

presenceagent

watcher

callee

GEOPRIV

SIPpresence

SIPcall

PUBLISHNOTIFY

SUBSCRIBE

INVITE

publicationinterface

notificationinterface

ruleinterface

INVITE

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

PA

watcher

PUA watcher

watcher

PUBLISH

NOTIFY

everything

"vague"

CPL

INVITE

<activity><place-type><privacy><mood><sphere>

Policy relationships

geopriv-specific presence-specific

common policy

RPID CIPID

future

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)

Location-based IM & presence

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

Service Mobility Architecture

RoomPresence

SLP DirectoryAgent

Device Controller

(DC)

Scripts

SIP Proxy/Registrar

SLP ServiceAgent

SLP ServiceAgent

REGISTER(Room Presence Updates)

REGISTER(Room Presence Updates)

SrvReg SrvReg

SrvReq SrvRplyTFTP HTTP

Room Room

UserProfiles

Soft phone

SUB/NOTIFY/Updates

RoomSUB/NOTIFY/Updates

Service creation

programmer, carrier

end user

network servers

SIP servlets, sip-cgi

CPL

end system VoiceXML

SMIL

VoiceXML (voice),

LESS

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

Service creation environment for CPL and LESS

Conclusion

Old model: communication as endreachability as supreme goal

New model: user-controlled, context-sensitive

Getting close to having tool set that allows building such services