1. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 1 Emergency Services for 802 Date: 2007-03-13 Authors:

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

3. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 3 Content Scope & Motive Introduction Requirements 802 technologies Other SDOs What next?

4. doc.: IEEE 802.11-07/0505r0 Tutorial March 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.

5. doc.: IEEE 802.11-07/0505r0 Tutorial March 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

6. doc.: IEEE 802.11-07/0505r0 Tutorial March 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

7. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 7 Requirements

8. doc.: IEEE 802.11-07/0505r0 Tutorial March 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 11-2691111 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 161.300 MHz.Rega http://en.wikipedia.org/wiki/Emergency_telephone_number#Emergency_number s_by_countryhttp://en.wikipedia.org/wiki/Emergency_telephone_number#Emergency_number s_by_country

9. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 9 Emergency Alert System (EAS) http://wonkette.com/politics/television/emergency-alert-system-actually-used-183830.php

10. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 10 IEEE 802 technologies

11. doc.: IEEE 802.11-07/0505r0 Tutorial March 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

12. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 12 Issues to be solved for IEEE 802 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) Unauthenticated Network Access (e.g. IEEE 802.11) Admission Control –QoS – dedicated bandwidth –preemption

13. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 13 IEEE 802.1

14. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 14 IEEE 802.1AB Link Layer Discovery Protocol (LLDP) A standard and extensible multi-vendor protocol and management elements to support network topology discovery and exchange device configuration and capabilities Developed and maintained by IEEE 802.1, planned for revision (for wireless purposes)

15. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 15 IEEE 802.11

16. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 16 Introduction Why does IEEE 802.11 need to address Emergency Services provision at all? –Emergency Service Identification –Location –Unauthenticated Network Access –Vehicular Emergency Communications –Network Push Alert IEEE 802.11 must be able to open an 802.1X port to proceed, if 802.1X is the required authentication procedure (i.e. not open authentication)

17. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 17 AP (11u-capable) STA (11u-capable) Configured by Hotspot owner / administrator Beacon (Emergency Service Realm) Association request (SSID : emergency_network) Association Response (…) EAP Success (include PMK) delay IEEE 802.11 Emergency Call Setup EAPOL/EAP-Response/Identity (e.g. anonymous@ESR) EAPOL/EAP-Request/Identity 4-Way Handshake

18. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 18 IEEE 802.11 Emergency Call Setup

19. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 19 Location Location information is being developed by IEEE 802.11k (Geospatial) and IEEE 802.11v (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

20. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 20 Unauthenticated Network Access (unique to IEEE 802.11) 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 along with the credentials in order enable this operation. 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. How to reach these network elements (e.g., a Call Manager) and which protocol to use (e.g., SIP) are outside the scope of IEEE 802.11.

21. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 21 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.

22. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 22 IEEE 802.15

23. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 23 IEEE 802.15 IEEE802.15.4a has built in a position measurement capability (<1m), but it appears that they are not dealing with emergency services.

24. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 24 IEEE 802.16

25. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 25 IEEE 802.16 In IEEE 802.16g there are several elements for Device Localization and Location Based Services (LBS) - which may be used for Emergency Services. Examples in location sensitized applications, emergency call origination tracking, equipment tracking etc. IEEE 802.16e utilises RFC 3825 Is it useful consider civic location issues, when cell/hotspot sizes are so high.

26. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 26 IEEE 802.20

27. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 27 IEEE 802.20 There is no distinct description within current draft for emergency service. However the draft indicates that the system can get the terminal location, and obviously the system can support QoS classes, that might be used as emergency service location identification and provide preferential resource for emergency call. The SectorParameters message is used to convey sector specific information from the serving sector to the access terminals, including the Latitude, Longitude, RegistrationRadius, etc. The terminal may possibly initialize a emergency call in "connected" states with an open session using ConnectionOpenRequest ?

28. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 28 IEEE 802.21

29. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 29 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 802.21 Information Server AAA DHCP SSID #5

30. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 30 Emergency Call with 802.21 IS

31. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 31 IEEE 802.21 Information Server 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 802.21 provides a logical place to support a comprehensive list of all support options using IS

32. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 32 IEEE 802.22

33. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 33 IEEE 802.22 IEEE 802.22 has defined a Location Configuration Measurement Report A Location Configuration report as described in IETF RFC 3825 (“Dynamic Host Configuration Protocol Option for Coordinate- based Location Configuration Information”), includes latitude, longitude and altitude. The report format shall be as described in RFC 3825, and the length shall be 16 octets.

34. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 34 Vehicular Communications

35. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 35 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 806.16e, IEEE 802.20 –DSRC : IEEE 1609 continues work on application layer standards for IEEE 802.11p

36. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 36 Vehicular Communications DSRC/WAVE. Dedicated short-range communications (DSRC) at 5.9 GHz using an IEEE 802.11p 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.

37. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 37 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.

38. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 38 2 nd SDO emergency services coordination workshop 2nd SDO Emergency Services Workshop hosted by the U.S. Department of Transportation (DOT). The workshop will be held April 10, 11 & 12, 2007, from 8:30 am - 6:00 pm., in the Jefferson Building of the Library of Congress, located at 101 Independence Avenue SE in Washington, D.C. Please find updated information at this webpage: http://www.emergency-services-coordination.info/2007/

39. doc.: IEEE 802.11-07/0505r0 Tutorial March 2007 S. McCann et alSlide 39 Concluding Issues Don’t assume that IEEE 802 technologies can already support all ES requirements: –call back facilities ? –terminal location ? geospatial or civic? –does Civic location, make sense, for large scale systems? How far do we want to pre-empt upcoming regulations? –2 years? –10 years? What does the market require? –Similar issues to Legal Intercept? Do we want closer liaisons with other SDOs Comments welcome