geopriv LbyR Nov28

Download Report

Transcript geopriv LbyR Nov28

LocByRef Use Cases
Rohan Mahy
November 28, 2006
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.
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
target’s web page. web
page fetches location
from pres server using a
reference to an
authenticated URL
my web
page
LIS
fetch
pres
server
target
watcher 2
watcher 1
subscribe
Emergency
• If target isn’t 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?
LIS
subscription
proxy /
SR
target
PSAP
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
pres
server
target
pizza
place
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
pres
server
target
subscribe
or
fetch
tourism
nav server
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
tracking app/
web page
fetch
tracker 2
LIS
tracking
server
target
tracker 1
subscribe
or
fetch