 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| • |
Location
Applications are growing in IEEE 802.11 WLAN networks, as they are for
|
|
|
other
technologies
|
|
|
– |
Hotspot services,
Asset tracking, etc
|
|
|
– |
Wide variety of
indoor environments – office, warehouse, etc with multiple APs
|
|
| • |
Current IEEE
802.11 location specification:
|
|
|
|
– |
IEEE Std
802.11k-2008 defines a protocol for the exchange of location data, binary
encoding
|
|
of geospatial
format (needs to be updated)
|
|
|
– |
IEEE P802.11v
(Wireless network Management) Draft 6.0 adds civic and location by
|
|
|
reference,
referring to RFC4776; liaison approved 17 July
|
|
| • |
RFC 4776 does
not support full location description for a combination of civic and
|
|
|
shape
information
|
|
|
|
– |
Convey the
location of a WLAN entity that combines Building Address, Floor and a
|
|
|
determined/known
reference point and reference location as represented by a shape.
|
|
|
– |
A binary
representation that supports the Point, Polygon, Arc Band, Rectangle,
Circle,
|
|
|
Ellipse, Cube,
Cuboid, Sphere, and Ellipsoid shapes
|
|
|
– |
The binary
representation should extend or be combinable with civic information
already
|
|
|
defined in RFC
4776 so that a single payload message can Requesting extensions to the
|
|
|
CIVIC location
binary encoding specifications to support indoor location applications
|
|
|
| • |
Re-use IETF
defined formats for location data, to minimize specification duplication
|
|
|
and provide
common formats across layer 2 protocols and upper layer protocols.
|
|