Xiaotao Wu Henning Schulzrinne ([email protected]) with Ron Shacham, Kundan Singh, Matthew J. Mintz-habib (with slides from Ben Teitelbaum, Internet2)

Xiaotao WuHenning Schulzrinne ([email protected])

with Ron Shacham, Kundan Singh, Matthew J. Mintz-habib

(with slides from Ben Teitelbaum, Internet2)VON Fall 2004 (Boston, MA)

October 19, 2004

PALS: Presence and PALS: Presence and Location ServicesLocation Services

OverviewOverview

Goals of PIC groups and PALS effort Rich presence and context-based

communications Rich presence trials in Internet2 Location determination

Goal of Rich PresenceGoal of Rich Presence

Communication is enhanced through the inclusion of rich presence information, through which participants may see not only who is on-line, but also where they are and what they are doing, so that communications becomes planned and desired instead of disruptive and haphazard.

Presence Presence rich presence rich presence Presence

“Notification of events that facilitate communication”

“On-line”, “Away”, “Idle”, “On phone”, “Out to lunch”, ...

Back to the future? Remember BSD: finger, write, who, talk? Zephyr at MIT (1980s) Presence restores the sense of community that existed

on timesharing systems Forward to the future!

New standards for interoperability and scalability User-centric control of presence publication Richer state semantics and automatic triggers Addition of location information User-created services for rich presence and location

ContextContext

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) not yet, but similar in many aspects to location data

Indianapolis October, 2003Honolulu January, 2004Arlington April, 2004

Rich presence trials in Rich presence trials in Internet2Internet2

Determining locationDetermining location Two types of sensors:

end system determines location “handset-based” GPS, 802.11 triangulation

network conveys location to end system or other component

MAC backtracking AP-based 802.11 triangulation swipe cards, iButtons, active badges

Two modes: explicit user action: swipe card, touch iButton involuntary: network-based tracking

GPS may not be practical (cost, power, topology) Add location beacons

extrapolate based on distance moved odometer, pedometer, time-since-sighting

idea: meet other mobile location beacons estimate location based on third-party information

WiFi location trackingWiFi location tracking HP Labs Metro Project Signal Strength Location Tracking

Room-level accuracy Sniff client signal strength from multiple

monitors Triangulation difficult due to walls, multipath

effects Match signal strength signature of target locations Calibrate system by gathering signatures for each

location No client software required

But clients do have to transmit to be located

““Skiffs”Skiffs”

Standard access points No client software “Skiff” monitors

SA110 single board computer running Linux Report signal strength, MAC address of all

packets seen

ScannerWeb Server

InferenceEngine

AggregatorConsolidator

SIP LocationServiceScanner

Scanner

Database

Wireless

Client

MAC address locationsMAC address locations

ARPWatch and SIP registry map MAC addresses to SIP URIs

A simple exampleA simple example

Talk to Xiaotao

•Over the phone

•Go to his place andtalk face to face

•IM and meet himin conference room

PIC activitiesPIC activities Arlington, April 2004

Venue: Spring 2004 Internet2 Member Meeting, Arlington, VAPresence Elements: location (automatic); room session name; session end time; per-room internet weather

Honolulu, January 2004Venue: Winter 2004 Joint Techs Workshop, University of HawaiiPresence Elements: location (automatic); room session name; session end time; per-room internet weatherClients: sipc (Windows, Linux); presence portal

Indianapolis, October 2003Venue: Fall 2003 Internet2 Member Meeting, Indianapolis, INPresence Elements: location (manual); room session name; session end time; Clients: sipc (Windows, Linux); Session (Mac, Windows); presence portal

Technical detailsTechnical details

SUBSCRIBEto my location

PUBLISHpresence status

NOTIFYmyselfand others’ locations

by Jamey from HP

802.11 Signal Strength 802.11 Signal Strength Location TrackingLocation Tracking Room-level accuracy Unassociated 802.11 monitoring of all

channels in use Gathers signal strength measurements of each client Clients visible from multiple monitors

Triangulation difficult due to walls, multipath effects

Match signal strength signature of target locations Calibrate system by gathering signatures for each

location No client software required

But clients do have to transmit to be locatedby Jamey from HP

802.11 Location Tracking802.11 Location Tracking Standard access points No client software “Skiff” monitors

SA110 single board computer running Linux

Report signal strength, MAC address of all packets seen

by Jamey from HP

by Jamey from HP

Locating client devicesLocating client devices

ARP to correlate MAC to IP

by Jamey from HP

Locating SIP clientsLocating SIP clients

Correlate client IP addr to SIP registrar

SIPc: a context-aware SIP SIPc: a context-aware SIP UAUA

configuration

multimediasession setup presence

informationnetwork

appliance controlmulticasted session

emergencyhandling

SIPMultimediacall control

Real time streaming

Location sensing

Network appliance control

Floorcontrol

SIP for presence

SAP

Instantmessage

SIP CGIengine

LESS/CPLengine

Third party call control

Emergency handling

Service LocationDetection (SLP)

audio

video

whiteboard

desktopsharing

locationsensors

Web browsersEmail clients

RTP: RFC 1889SDP: RFC 2327RTSP: RFC 2326

SIP Event Notification: RFC 3265

SAP: RFC 2974SIP: RFC 3261

SLP: RFC 2608

Some IETF draftsCPL, SIP 3PCC,SIP Device ControlGEOPRIV location format, SIP for IM

Pinpoint user on a mapPinpoint user on a map

Internet2 WG PIC trialInternet2 WG PIC trial

PUBLISHpresence status

NOTIFYmyselfand others’ locations

SUBSCRIBEto my location

Actions for a locationActions for a location

Location switch for CPLLocation switch for CPL <?xml version="1.0"?> <cpl> <incoming> <location-switch type="civil"> <location loc=""> <time-switch> <time dtstart="20040224T200055Z"

dtend="20040224T210055Z"> <reject status="486" reason="Busy"/> </time> </time-switch> </location> </location-switch> </incoming> </cpl>

http://www.ietf.org/internet-drafts/draft-wu-iptel-locswitch-00.txt

LESS snapshotLESS snapshot<less> <incoming> <address-switch> <address is=“sip:[email protected]"> <device:turnoff device=“sip:[email protected]”/> <media media=“audio”> <accept/> </media> </address> </address-switch> </incoming></less>

incoming call

If the call from my boss

Turn off the stereo

Accept the call with only audio

trigger, switch, modifier, action

Internet2 Presence and Internet2 Presence and Integrated Communications WG Integrated Communications WG (PIC)(PIC)

Home page http://pic.internet2.edu/

Chair Jeremy George, Yale University

{email, im, sip}:[email protected]:203-436-4507

Charter Foster the deployment of SIP-based

communication that integrate multiple communications elements in the context of presence

ConclusionConclusion Internet2 experiments in location-based

services user location context services (“what’s happening”) proximity services location communications services

Use 802.11 to locate users indoors Closely related to emergency services (9-1-1) On-going related work at Columbia:

integration of many different location services integrate privacy policies (GEOPRIV) session mobility service mobility

Backup slidesBackup slides

sipc interactions with the sipc interactions with the world around itworld around it

SDP

SAP

RTP

RTP

RTP

RTSP

SIP

SIP

SIP

location

SLP3pccSIP DO

SLPSIP

NOTIFY

MESSAGE

DO

SIP

location

location

sipc for PIC trialsipc for PIC trial

PUBLISH and XCAP support Location-switch extension for CPL Display location information Pinpoint a user on a map

Convey civic or geo location & map address

Map URL can be in location notifications (in CIPID or pidf-lo document)

Location-based services in Location-based services in sipcsipc

Location-based device Location-based device controlcontrol

<notification> <geo-switch type="civil"> <geo LOC="7LW2"> <location url="sip:[email protected]"> <control action="poweron"/> </location> </geo> <otherwise> <location url="sip:[email protected]"> <control action="poweroff"/> </location> </otherwise> </geo-switch> </notification>

Service creation: location Service creation: location switch for CPLswitch for CPL

Sample SIP messageSample SIP messageINVITE sip:[email protected] SIP/2.0Expires: 3600To: <sip:[email protected]>Call-Info: <http://www.cs.columbia.edu/~xiaotaow>Call-ID: [email protected]: SIP/2.0/TCP 128.59.19.251:4226;rportPriority: emergencyContent-Type: multipart/mixed; boundary="----- =_Mjg4N2E5ZjcxOTJiMzU3ZTFlZjNhOTUxYmU4OGFlYTY="User-Agent: Columbia University sipc 2.45From: Xiaotao Wu <sip:[email protected]>; tag=335821192402.128.59.19.251Contact: <sip:[email protected]:5061>CSeq: 1 INVITEDate: Sun, 17 Oct 2004 18:52:30 GMTContent-Length: 1252

SIP message – SDPSIP message – SDP

------- =_Mjg4N2E5ZjcxOTJiMzU3ZTFlZjNhOTUxYmU4OGFlYTY=MIME-Version: 1.0Content-ID: <2620.1098039150.1@rer>Content-Type: application/sdpContent-Transfer-Encoding: 8bit

v=0o=xiaotaow 1098039150 1098039150 IN IP4 128.59.19.251s=SIPC Callc=IN IP4 128.59.19.251t=0 0m=audio 10000 RTP/AVP 3 0

SIP message – location SIP message – location contentcontent

------- =_Mjg4N2E5ZjcxOTJiMzU3ZTFlZjNhOTUxYmU4OGFlYTY=MIME-Version: 1.0Content-ID: <2620.1098039150.2@rer>Content-Type: application/pidf+xmlContent-Transfer-Encoding: 8bit

<?xml version="1.0" encoding="ISO-8859-1"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:cl=" urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc" xmlns:gml="urn:opengis:specification:gml:schema-xsd:feature:v3.0" entity="sip:[email protected]"> <tuple id="4404"> <contact priority="0.8">sip:[email protected]:5061</contact> <status> <gp:geopriv> <gp:location-info> <gml:location> <gml:Point> <gml:coordinates>41:04:32N 85:07:10W</gml:coordinates> </gml:Point> </gml:location> </gp:location-info> </gp:geopriv> </status> </tuple></presence>