doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 1 Emergency Services for 802 Date: Authors:

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 2 Note This presentation was originally produced for an IEEE 802 tutorial on 13 th March This version has been re-formatted and shortened for: –2 nd SDO Emergency Workshop, Washington D.C. 2007

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 3 Content Scope & Motive Introduction Requirements IEEE Use Case with IEEE IS Vehicular Communications Concluding Issues

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 4 Introduction This presentation reflects work in progress. Its intention is to inform members about ongoing efforts to standardise emergency services within IEEE 802. It does not attempt to provide definitive solutions to all problems. It hopefully will encourage all projects and members to consider whether their technology will meet the future requirements of regulatory bodies for emergency service provision.

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 5 Scope Within this tutorial we define Emergency Services as: –Suitable for IEEE 802 Wireless technologies –Emergency voice calls –Network push alerts (e.g. Emergency Alert System – EAS) –Vehicle communication –non-VoIP calls (e.g. multi-media) Three types of Emergency Service (ES) –citizen-to-authority –authority-to-citizen –authority-to-authority

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 6 Motive There is an overarching concern for a consistent approach by standards development organizations (SDOs – see later) to address social policy expectations, such as full Emergency Service capability, in relation to emerging access technologies. Location identification and callback capability represent baseline requirements for emergency service. Call integrity is of prime concern

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 7 Requirements

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 8 Emergency Calls in Random Countries Philippines: 112 or 911; police 117 Singapore: fire and medical 995; police 999; 112 and 911 can be dialed from mobile phones South Korea: police 112; fire and medical 119 Sri Lanka: police emergency 119 accident service Lithuania: 112; fire 01, 101, or 011; police 02, 102, or 022; medical 03, 103, or 033. Note: the non-112 numbers are for separate emergency services differ in distinct telecommunications networks, whereas 112 available on all networks. Vietnam: 115; police 113; fire 114 Switzerland: fire 118; police 117; medical 144; poison 145; road emergency 140; psychological support (free and anonymous) 143; psychological support for teens and children (free and anonymous) 147; helicopter air-rescue (Rega) 1414 or by radio on MHz.Rega s_by_countryhttp://en.wikipedia.org/wiki/Emergency_telephone_number#Emergency_number s_by_country

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 9 Emergency Alert System (EAS)

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 10 IEEE

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 11 Generalized Emergency Call procedure Location determination ( in cellular networks, this might be done by the network on behalf of the mobile phone) with Location Configuration Protocols (LCP) Location representation (geo, civic: cell-id for cellular) Mapping database discovery Location to Service Translation (LoST) Location conveyance

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 12 Issues to be solved for IEEE ES identification Location information –Some procedure to fetch the location information by higher layers when initializing the call may be required. –Mobile terminal –Network edge device (e.g. Access Point, Base Station) –Possible interaction with LLDP-MED Unauthenticated Network Access (e.g. IEEE ) Admission Control –QoS – dedicated bandwidth –preemption

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 13 IEEE Emergency Call Setup

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 14 Location Location information is being developed by IEEE k (Geospatial) and IEEE v (Geospatial & Civic) Request/Response paradigm –Client may request from the access point it’s own location the location of the access point GeoPriv used to wrap location information –Location standard formats supported include GEO and CIVIC Control and Measurement mechanisms to enable tracking continuously Correct use of RFC 3825 & RFC 4119 ??

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 15 Unauthenticated Network Access Public user credentials. In this situation, a client uses the defined network selection method to query candidate networks to determine which one (or several) supports VoIP, end-to-end QoS and emergency services. Once this has been determined, the client associates to the SSID corresponding to the chosen network using public user credentials. It may be necessary to define a default EAP method (e.g. EAP-e911) Use an SSID configured for Open Authentication, that is only suitable for obtaining emergency service (i.e., and not suited for obtaining other hotspot services such as internet access). Network elements necessary to complete an emergency call are reachable via this SSID.

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 16 Admission Control A QoS enabled client requests bandwidth using a TSPEC Request in an action frame. Currently a TSPEC Request includes parameters describing the characteristics of the traffic stream, but no information on the actual use of the traffic stream. To indicate emergency call initiation, it is proposed that a new “Expedited Bandwidth Request” element is used. It is the responsibility of the client to transmit this element.

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 17 Use Case using an IEEE Information Server (IS)

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 18 AP (11u-capable) STA (11u-capable) Carrier Network VLAN #5 Note: There does NOT need to be a 1-to-1 mapping between this and SSID #5. Architecture IEEE Information Server AAA DHCP SSID #5

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 19 IEEE Information Server (IS) Networks may support means to determine, help in determining or provide the location to the clients at various layers –Link layer specific ones: LLDP[-MED], U-TDoA, D-TDoA –Link layer agnostic ones: DHCP, OMA SUPL, RELO, HELD (HTTP based) –Other SDOs defined different LCPs Service providers need flexibility on how location services are offered in their network IEEE provides a logical place to support a comprehensive list of all support options using IS

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 20 Emergency Call with IS

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 21 Vehicular Communications

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 22 Vehicular Communications Emergency communications is a major focus of ITS (Intelligent Transport Systems) activity, and it was a significant topic at the March 2005 ITU Workshop. Project MESA is also helping to call attention to this area and providing high-level direction. Two distinct areas for wireless communications: –MBW: New work item in ISO/TC204/WG16: “Specific Mobile Broadband Wireless Access Communications Systems”, e.g. IEEE e, IEEE –DSRC : IEEE 1609 continues work on application layer standards for IEEE p

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 23 Vehicular Communications DSRC/WAVE. Dedicated short-range communications (DSRC) at 5.9 GHz using an IEEE p base is now called WAVE (Wireless Access in Vehicular Environments). The U.S. FCC has allocated 75 MHz of bandwidth for ITS applications in this band, with emphasis on public safety and, in the U.S., WAVE may become a U.S. federally funded vehicle- data network separate from the cellular network.

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 24 Vehicular Communications Mobile wireless broadband (MWB) represents an important part of a public sector (particularly public safety) solution. MWB can provide a consistent and robust capacity that can serve routine operations, but provide priority for emergencies. MWB is useful for commercial applications of ITS as well as to support public agency and public safety applications, due to its ability to function well over large distances and at high travel speeds. It is vitally important for commercial and public uses of MWB to remain consistent with one another, including the ability to prioritise messages, especially in case of emergencies.

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 25 Concluding Issues

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 26 Concluding Issues I Don’t assume that IEEE technologies can already support all ES requirements: –call back facilities ? –terminal location ? geospatial or civic? –does Civic location, make sense, for large scale systems? IEEE needs to conform to both the IETF/NENA and the 3GPP IMS architectures to satisfy all potential interworking scenarios.

doc.: IEEE /0505r2 Tutorial April 2007 S. McCann et alSlide 27 Concluding Issues II How far do we want to pre-empt upcoming regulations? –2 years? –10 years? What does the market require from WLAN technology? –Will WLAN (and hence other IEEE 802 technologies) be exempt from emergency service regulation? –Similar issues to Legal Intercept? Does IEEE want closer liaisons with other SDOs Comments welcome