jan. 2005rich presence1 rich presence and privacy henning schulzrinne (with xiaotao wu and ron...
Post on 22-Dec-2015
218 views
TRANSCRIPT
Jan. 2005 Rich presence 1
Rich Presence and Rich Presence and PrivacyPrivacy
Henning Schulzrinne(with Xiaotao Wu and Ron Shacham)
Columbia UniversitySIP 2005 (Paris)
January 26, 2005
Jan. 2005 Rich presence 2
OverviewOverview
Context-aware communications Presence data model Rich presence in SIP Privacy user control of
information dissemination Creating context-based services
Service creation in end systems Service and session mobility
Jan. 2005 Rich presence 3
Basic presenceBasic presence Role of presence
initially: “can I send an instant message and expect a response?”
now: “should I use voice or IM? is my call going to interrupt a meeting?”
Yahoo, MSN, Skype presence services: on-line & off-line
useful in modem days – but many people are (technically) on-line 24x7
thus, need to provide more context + simple status (“not at my desk”)
entered manually rarely correct does not provide enough context for directing
interactive communications
Jan. 2005 Rich presence 4
Context-aware Context-aware communicationcommunication
context = “the interrelated conditions in which something exists or occurs”
anything known about the participants in the (potential) communication relationship
both at caller and calleetime CPL
capabilities caller preferences
location location-based call routinglocation events
activity/availability presence
sensor data (mood, bio)
privacy issues similar to location data
Jan. 2005 Rich presence 5
Presence and event Presence and event notificationnotification Presence = special case
of event notification “user Alice is available for
communication” Human users:
multiple contacts per presentity device (cell, PDA, phone, …) service (“audio”)
activities, current and planned
surroundings (noise, privacy, vehicle, …)
contact information composing (typing,
recording audio/video IM, …)
Events in multimedia systems: REFER (call transfer) message waiting
indication conference floor control conference membership push-to-talk system configuration
General events: emergency alert
(“reverse 911”) industrial sensors (“boiler
pressure too high”) business events (“more
than 20 people waiting for service”)
Jan. 2005 Rich presence 6
IETF effortsIETF efforts SIP, SIPPING and SIMPLE working groups
but also XCON (conferencing) Define SIP methods PUBLISH, SUBSCRIBE,
NOTIFY GEOPRIV:
geospatial privacy location determination via DHCP information delivery via SIP, HTTP, … privacy policies
SIMPLE: architecture for events and rich presence configuration (XCAP) session-oriented IM (↔ page mode) filtering, rate limiting and authorization
Jan. 2005 Rich presence 7
Presence data modelPresence data model
“calendar” “cell” “manual”
[email protected], video, text
person(presentity)
(views)
services
devices
Jan. 2005 Rich presence 8
Presence data architecturePresence data architecture
rawpresencedocument
createview
(compose)
privacyfiltering
draft-ietf-simple-presence-data-model
compositionpolicy
privacypolicy
presence sources
XCAP XCAP
(not defined yet)
depends on watcherselect best sourceresolve contradictions
PUBLISH
Jan. 2005 Rich presence 9
Presence data architecturePresence data architecture
candidatepresencedocument
watcherfilter
rawpresencedocument
post-processingcomposition(merging)
finalpresencedocument
differenceto previous notification
SUBSCRIBE
NOTIFY
remove data not of interest
watcher
Jan. 2005 Rich presence 10
CompositionComposition
union oftuples
rule-based:most recent;
source quality
program:complex conditionsand transformations
com
ple
xit
y
capability
Jan. 2005 Rich presence 11
Future work: sourcesFuture work: sources Composition may need to resolve conflicts
calendar says meeting, but user is driving Composition relies on source information:
information gathering: sensor, manual, calendar relative trustworthiness (sensor vs. manual) how recently updated? does place and time make activity likely?
Will likely add source information to presence data already started for geo data
Jan. 2005 Rich presence 12
GEOPRIV and SIMPLE GEOPRIV and SIMPLE architecturesarchitectures
targetlocationserver
locationrecipient
rulemaker
presentity
caller
presenceagent
watcher
callee
GEOPRIV
SIPpresence
SIPcall
PUBLISHNOTIFY
SUBSCRIBE
INVITE
publicationinterface
notificationinterface
XCAP(rules)
INVITE
DHCP
Jan. 2005 Rich presence 13
RPID = rich presenceRPID = rich presence Provide watchers with better information about
the what, where, how of presentities facilitate appropriate communications:
“wait until end of meeting” “use text messaging instead of phone call” “make quick call before flight takes off”
designed to be derivable from calendar information or provided by sensors in the environment
allow filtering by “sphere” – the parts of our life don’t show recreation details to colleagues
Jan. 2005 Rich presence 14
The role of presence for call The role of presence for call routingrouting Two modes:
watcher uses presence information to select suitable contacts
advisory – caller may not adhere to suggestions and still call when you’re in a meeting
user call routing policy informed by presence
likely less flexible – machine intelligence
“if activities indicate meeting, route to tuple indicating assistant”
“try most-recently-active contact first” (seq. forking)
LESS
translateRPID
CPL
PA
PUBLISH
NOTIFY
INVITE
Jan. 2005 Rich presence 15
RPID: rich presenceRPID: rich presence<person>
<tuple>
<device>
<activities>
<class>
<mood>
<place-is>
<place-type>
<privacy>
<relationship>
<service-class>
<sphere>
<status-icon>
<time-offset>
<user-input>
Jan. 2005 Rich presence 16
Rich presence – describing Rich presence – describing presentitypresentity
class: label elements for grouping and selection
i-belong-to: AOR contact in tuple belongs to proposed element
status-icon icon URL with hint for
watcher user interface
Jan. 2005 Rich presence 17
Rich presence – describing Rich presence – describing serviceservice relationship
a communication service offered by a family member associate (colleague) assistant supervisor
service-class: type of service offered electronic delivery (courier) postal in-person
Jan. 2005 Rich presence 18
Rich presence – describing Rich presence – describing statestate mood of presentity
afraid, amazed, angry, annoyed, anxious, ashamed, bored, brave, calm, cold, confused, contented, cranky, curious, depressed, disappointed, disgusted, distracted, embarrassed, excited, flirtatious, frustrated, grumpy, guilty, happy, hot, humbled, humiliated, hungry, hurt, impressed, in_awe, in_love, indignant, interested, invincible, jealous, lonely, mean, moody, nervous, neutral, offended, playful, proud, relieved, remorseful, restless, sad, sarcastic, serious, shocked, shy, sick, sleepy, stressed, surprised, thirsty, worried
likely derived from game state manual input lie detector + fMRI (later)
Jan. 2005 Rich presence 19
Rich presence – describing Rich presence – describing activitiesactivities sphere
current state and role free text e.g., “work”, “home”,
“soccer club”, “PTA” activities: what is the
person doing away, appointment,
busy, holiday, in-transit, meal, meeting, on-the-phone, performance, permanent-absence, sleeping, steering, travel, vacation
Jan. 2005 Rich presence 20
Rich presence – describing Rich presence – describing place and surroundingsplace and surroundings place-type: type of surroundings
aircraft, airport, bus, car, home, hotel, industrial, library, mall, office, outdoors, public, public-transport, restaurant, school, ship, station, street, theater, train, truck
place-is: communication properties video: bright, dark audio: noisy, quiet
privacy: communication that is private audio, video, text
time-offset: minutes from UTC for avoiding middle-of-the-night calls
Jan. 2005 Rich presence 21
Rich presence – describing Rich presence – describing user—device interactionsuser—device interactions
How long has the user not provided input to the device? e.g., microphone input, keyboard,
mouse
idle active
idle-threshold
activity
Jan. 2005 Rich presence 22
CIPID: Contact InformationCIPID: Contact Information
More long-term identification of contacts
Elements: card – contact Information home page icon – to represent user map – pointer to map for user sound – presentity is available
Jan. 2005 Rich presence 23
Rich presence: time Rich presence: time informationinformation Presence is currently about here and now but often only have (recent) past – e.g., calendar or future
“will be traveling in two hours” “will be back shortly”
allows watcher to plan communication
timed-status timed-status
time
RPIDfrom until
now
Jan. 2005 Rich presence 24
PrivacyPrivacy All presence data,
particularly location, is highly sensitive
Basic location object (PIDF-LO) describes
distribution (binary) retention duration
Policy rules for more detailed access control
who can subscribe to my presence
who can see what when
<tuple id="sg89ae">
<status>
<gp:geopriv>
<gp:location-info>
<gml:location>
<gml:Point gml:id="point1“
srsName="epsg:4326">
<gml:coordinates>37:46:30N 122:25:10W
</gml:coordinates>
</gml:Point>
</gml:location>
</gp:location-info>
<gp:usage-rules>
<gp:retransmission-allowed>no
</gp:retransmission-allowed>
<gp:retention-expiry>2003-06-23T04:57:29Z
</gp:retention-expiry>
</gp:usage-rules>
</gp:geopriv>
</status>
<timestamp>2003-06-22T20:57:29Z</timestamp>
</tuple>
Jan. 2005 Rich presence 25
Privacy policy Privacy policy relationshipsrelationships
geopriv-specific presence-specific
common policy
RPID CIPID
future
Jan. 2005 Rich presence 26
Privacy rulesPrivacy rules Conditions
identity, sphere time of day current location identity as <uri> or
<domain> + <except>
Actions watcher confirmation
Transformations include information reduced accuracy
User gets maximum of permissions across all matching rules privacy-safe
composition: removal of a rule can only reduce privileges
Extendable to new presence data rich presence biological sensors mood sensors
Jan. 2005 Rich presence 27
Example rules documentExample rules document
<identity><id>[email protected]</id></identity>
<sub-handling>allow</sub-handling>
<provide-services> <service-uri-scheme>sip</service-uri-scheme> <service-uri-scheme>mailto</service-uri-scheme></provide-services><provide-person>true</provide-person><provide-activities>true</provide-activities><provide-user-input>bare</provide-user-input>
<ru
lese
t>
<rule id=1>
<co
ndit
ions>
<tr
ansf
orm
ati
on
s>
<act
ions>
Jan. 2005 Rich presence 28
Creating and manipulating Creating and manipulating rulesrules
Uploaded in whole or part via XCAP XML not user-visible Web or application UI, similar to
mail filtering Can also be location-dependent
“if at home, colleagues don’t get presence information”
Possibly implementation-defined “privacy levels”
Jan. 2005 Rich presence 29
Program location-based Program location-based servicesservices
Jan. 2005 Rich presence 30
ConclusionConclusion
Rich presence human-centered information about presentities
Rich presence more appropriate communication + substitute for voice & IM communications
Privacy through simple rule sets