Transcript Location Configuration

March, 2007
doc.: IEEE 802.11-07/0xxxr0
Joint TGu-802.21: Location Configuration
for Emergency Services
Date: 2007-03-13
Authors:
Name
Company
Address
Phone
email
Gabor Bajko
Nokia
+1 972 894
5000
[email protected]
Srinivas
Sreemanthula
Nokia
Palo Alto,
CA
Irving, TX
+1 972 894
5000
Srinivas.Sreemanthula@nokia.
com
Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in
this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE
Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit
others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11.
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement
"IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents
essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is
essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair
<[email protected]> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being
developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <[email protected]>.
Submission
Slide 1
Gabor/Srini
March, 2007
doc.: IEEE 802.11-07/0xxxr0
Abstract
• This presentation gives an overview of the components
of an Emergency Service and addresses an information
framework to provide location configuration protocol
capabilities to the requesting nodes
Submission
Slide 2
Gabor/Srini
March, 2007
doc.: IEEE 802.11-07/0xxxr0
Emergency Services - background
• Enhanced 911 (E911) was defined to be a system that
automatically associates a physical address with the calling party's
telephone number
• Wireless E911 allows the mobile phone to be located
geographically using radiolocation (relative loc), or alternatively it
mandated the mobile phone to determine its own location with
GPS (absolute loc)
• Nowadays not only a mobile phone, but any device capable of
networking and having a VoIP application might be able to place
an Emergency Call, and the access network providing IP access to
the device might be mandated to support such a call
Submission
Slide 3
Gabor/Srini
March, 2007
doc.: IEEE 802.11-07/0xxxr0
(Location related) Procedures required for
placing an Emergency Call
•
Placement of an Emergency Call is a complex procedure for the device, it
involves:
– Location Configuration Protocol (LCP) selection
– Location determination ( in cellular networks, this might be done by the network on
behalf of the mobile phone)
– Location representation (geo, civic)
– Mapping database discovery
– Location to Service Translation (LoST)
– Location conveyance
– Placing Emergency calls
•
IETF is defining the pieces of this puzzle
•
Other SDOs defined different LCPs
Submission
Slide 4
Gabor/Srini
March, 2007
doc.: IEEE 802.11-07/0xxxr0
Location Determination for Emergency
Service purposes
• Currently, in PSTN and Cellular Networks, before the call is
delivered to the PSAP, it must have location information included
• Location can be:
– determined by the network (using radiolocation techniques, like TDoA)
and provided to the psap (and not to the device)
– determined by the device itself (e.g. GPS) and provided to psap
– determined by the network and provided to the device upon request
(before the Emergency Call is made)
– Configured in the network and downloaded by the device (before the
Emergency Call is made)
• Networks may support multiple protocols to determine, help in
determining or provide the location to the device
Submission
Slide 5
Gabor/Srini
March, 2007
doc.: IEEE 802.11-07/0xxxr0
Location Configuration Protocols (LCP)
• Protocols which determine or provide the location of the device to
the device are called Location Configuration Protocols
• There are many standardized LCPs currently available
• Some of them are link layer specific, others are link layer agnostic
• Example of (network based) LCPs:
– Link layer specific ones: LLDP[-MED], U-TDoA, D-TDoA
– Link layer agnostic ones: DHCP, OMA SUPL, RELO, HELD (HTTP
based)
• (Access) network operators may implement none, one or many
LCPs
• Devices will need to implement at least one, preferably many LCPs
Submission
Slide 6
Gabor/Srini
March, 2007
doc.: IEEE 802.11-07/0xxxr0
Location
• Location Information is needed for placing an
Emergency Call
• Location Information may be needed in other cases too
• The accuracy the location is determined may be
relevant for some services
• This presentation only addresses Location from
Emergency Services point of view
Submission
Slide 7
Gabor/Srini
March, 2007
doc.: IEEE 802.11-07/0xxxr0
Proposal
• It is proposed that 802.21 defines a new Information Element, called e.g.
LCP Information Element, and that would list all the LCPs a given
network supports
• a device would query the network to find out about the supported LCPs
which helps in
–
–
–
–
Run the supported LCP to determine location quickly
Network selection depending on the client need and support for LCP for location
Flexibility for clients to choose any of supported LCP in network
Cuts down on location discovery mechanisms in serving network
• The IE could also contain the accuracy that specific network is providing
the location of the device (per LCP)
• LCP request is envisioned to be used in same scenarios as the MIH IS
– Obtaining serving link location protocol capabilities
– Using serving link to obtain about target links
– Queries in pre-association states in 802.11 and 802.16
Submission
Slide 8
Gabor/Srini
March, 2007
doc.: IEEE 802.11-07/0xxxr0
Simple State-1 Query: For emergency use
STA
802.21
IS
AP
Get Information Req
(Request for LCP)
State-1 Query Mechanisms
Get Information Resp
(LCP IE )
Determine local
LCP support
Associate/Authenticate
Determine Location Information
(may be after IP addressing info)
Place an Emergency Call
Submission
Slide 9
Gabor/Srini