LocByRef Use Cases

About This Presentation

Title:

Description:

Number of Views:13

Avg rating:3.0/5.0

Slides: 8

Provided by: roh55

Learn more at: http://www.cs.columbia.edu

Category:

Tags: locbyref | cases | fetch | use

Transcript and Presenter's Notes

Title: LocByRef Use Cases

1
LocByRef Use Cases

2
Definition

LIS combination of an LG (Location Generator)
and an LS (Location Server)
pawn ticket URL reference with random
component. possession authorization.
authenticated URL reference which requires
authentication from specific user or group or
users.

3
Presence Server

Presence server uses LbyR to subscribe to
location from LIS
watcher 1 subscribes to loc/pres value from pres
server
watcher 2 clicks find out where I am right now
on targets web page. web page fetches location
from pres server using a reference to an
authenticated URL

my web page
watcher 2
LIS
fetch
subscribe
watcher 1
pres server
subscribe
target
4
Emergency

If target isnt mobile, it should provide LbyV
If target is mobile, it should provide LbyR.
PSAP should subscribe to the location using a
pawn ticket URL
going directly to the LG eliminates extra
machinery
does the proxy need to fetch the current location
too? Or is an initial value good enough?

subscription
LIS
PSAP
fetch ?
proxy / SR
target
5
Pizza

Two ways to provide a ref to Pizza Place
ref resolving to LIS
ref resolving to PS
Looks like this would always be a fetch. So,
LbyR does not look compelling for Pizza delivery
(use LbyV instead)

LIS
pizza place
pres server
target
6
Navigation

My navigation server probably has special
relationship with me. Often target (me) will
point its nav server directly at LIS. (Most
likely subscription but could be fetch)
I visit a city and go on a tour. I do not want
to offer direct LIS access to the tourism nav
server, so I provide a pawn ticket URL from my
presence server. (Could be either but more
likely a fetch)

target/ watcher
subscribe or fetch
my nav server
LIS
subscribe
pres server
tourismnav server
subscribe or fetch
target
7
Tracking

Tracking Server wants to keep track of all
resources all the time. Needs to subscribe to
location (probably from LIS). Tracker 1 can
subscribe or fetch current location
Tracking app/web page just fetches location
whenever tracker 2 asks for current location of a
resource