doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 1 Location Reference for Emergency Services in WLAN Domain Notice: This document has been prepared to assist IEEE 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 Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. Date: Authors:

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 2 Abstract The Public Safety community, globally, is gearing up to take advantage of the IP proliferation to upgrade their network systems, wire-line and wireless, in order to provide next generation of Emergency Services (ES). In this regard, NENA has developed and published VoIP-based (interim) i2 architecture for deployment of next generation of emergency services in North America. In parallel, the FCC is working to create appropriate regulation in support of ES for newer wireless technologies such as WiMAX. Location (positioning of an end-user) is fundamental to facilitating ES in fixed as well as mobile networks. And, as a byproduct, location also enables the network to provide many commercial Location Based Services (LBS). The current k draft (D5.0) does specify the Location Configuration Information (LCI) Report and its format, in line with that standardized by IETF/Geopriv in IETF RFC 3825; however, this facilitates only conveyance of location information (lat-long-altitude). On the other hand, the i2 approach dictates the STA to acquire authentic location information from the LIS (Location Information Server) in the access network, and it also requires that the network, in addition, facilitate conveyance of location parameters that enable the LIS to calculate and determine the most relevant location of the STA/end-user. Thus, the purpose of this presentation is to show the need to add location referencing aspects in support of the i2 approach by incorporation of mechanisms so that the LIS can retrieve necessary network parameters and end-user associated data for determination of location.

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 3 Background Information Subsequent to FCC E-911 mandate for Emergency Services (ES) deployment in existing cellular networks, similar rules are in works at the Commission for other newer wireless systems (such as WiMAX). Stakeholders in public safety applications foresee the advantages of and are preparing to deploy the Next Generation (NextGen) of IP-based ES networks. The National Emergency Number Association (NENA) has, in December 2005, published its (interim) i2 architecture standard for IP-based ES deployment in North America. Location or positioning of the end-user (SOS caller) is a core requirement for most emergency services.

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 4 Families of Location-Based Services (LBS) Emergency Services such as: SOS caller location, ES vehicle/personnel tracking and dispatch, real-time route-guidance and navigation in ES vehicles, etc. Intelligent Transportation Systems (ITS) services such as: commercial vehicle tracking, route-guidance & navigation, traffic management, en-route driver assistance Other LBS: such as yellow pages, locating people, maps and determination of destinations Network Management: for example, long-term and near-term people/vehicle mobility trends, real-time network configuration, congestion control, etc.

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 5 NENA defined (i2) migratory architecture Note boundaries of responsibility! ALI Local National PAM CAMA IP ISUP Call Server LIS VPC – VoIP Position Centre LIS – Location Identification Server Selective Router VPC E2+ ESGW VSP ISP Global ESZ boundary data Call Handling Call routing and location delivery Location determination Geodetic & Civil loc,n locn call Civic addr MSAG validation VDB ERDB Emergency network 911

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 6 PSAP1 VPC PSAP2 PSAP1 ESZ1 ESZ2 ESRN = X ESN = Y ES-Nums = n1, n2, n3… ELT = s1, s2, s3… ESZ3 ESZ4 ESZ5 ESZ6 ERD B Call Server ESGW Selective Router ALI a LIS CallbackNum LO|LK LO request LO LO identified with applicable ESZ ESRN ESN ES-Nums ELT… ESRN ESQK ESQK Location CallbackNum ES-Nums ELT etc… ESGW chosen based on ESRN SR chosen on ESRN and trunk selection rules specified by SR operator PSAP route selected based on ESQK from SRDB VPC selected based on ESQK 911 LO sig Call setup, routing and query routing V0 V1 V2 V3 V4 E2

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 7 LIS and IEEE WLAN Today, WLAN is ; and, IEEE is a matured standard WLANs are at the smallest location granularity under the wider (interworking) wireless network expanse. Some WLAN location applications at BSS/ESS level, include: locating needed personnel (such as doctors) in a hospital environment, or experts (technicians or managers) in a factory or office setting. However, the current IEEE802.11k. D5.0 draft standard facilitates only the delivery of actual location data per the Location Configuration Information (LCI) Report mechanism. The NENA i2 architecture requires a Location Information Server (LIS), from which the STA, via IP, will acquire location: –Using an application protocol that works above the IP layer (application layer) –LIS will also be used to authenticate the E-911 caller location –Depending on the network characteristics, a LIS will cover a few BSS/ESS as well as portions of fixed and wide-area wireless access networks –LIS will also have capability to manage location measurement, compute location from raw data, and provide updated location for mobile users. Thus, location parameter conveyance is also required to be supported, in addition, so as to enable the LIS function fully and as intended. This same (LIS) approach is being adopted by IETF/Geopriv/ECRIT fora as well. The LIS functionality is also being carried over in its totality to NENA’s i3 (end-to-end IP) architecture that is under development.

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide WG Support for i2 Archr Location determination process and parameters will vary with access network technology (e.g., for WiMAX vs. DSL); however, global consistency for location acquisition method is required. Therefore, a generic mechanism in k specs is desired to facilitate delivery of certain information to LIS that would aid in determination of required location, such as: –Some measurement data --- e.g., received signal strength and timing measurement data for the client STA that will enable LIS to select location method appropriate to the access network –Certain network parameters that correlate with the MAC address and/or IP address of the client device (an STA, or an AP); IP address correlation at LIS eventually is always required –Data necessary for the LIS to authenticate location associated with an STA (or AP) --- such as channel information –Mobility condition of an STA, for obtaining location updates. WG help is also requested in identification of PHY & MAC parameters that may be useful for location determination and its refinement.

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 9 In Conclusion, We request A generic mechanism– e.g. Location Parameter Conveyance Report, be established in the k specs that will support LIS to obtain end-user (by MAC address) specific network parameters and other information. Support from WG help to identify radio link parameters that would aid location determination and refinement. IEEE WG be the first to produce enabler location specs for ES and LBS. Naturally, then, the location related specification (messages and structure, information exchange, storage, and process-segments) would be ‘primitives’ that could be carried over to larger-sized networks such as WiMAX and cellular. Such an approach will facilitate global consistency for end-user devices in that: –Location information acquisition is in the same manner, irrespective of the type of access network the dev ice is attached to, and –Location acquisition is independent of the access network technology.

doc.: IEEE /0051r0 Submission Jan 2007 Vijay Patel, Andrew CorporationSlide 10 References Interim VoIP Architecture for Enhanced Services (i2), NENA , Issue 1, December 06, 2005