Emergency Services Tutorial


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page AP - Access Point SSID - Service Set Identifier
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Page
  • Emergency Services Tutorial

    1. 1. IEEE 802 Emergency Services Tutorial <ul><li>Date: 2007-07-16 </li></ul>Authors: Scott Henderson Manfred Arndt Richard Paine Allan Thomson Matthew Gast Chair: Stephen McCann : stephen.mccann@roke.co.uk
    2. 2. Abstract <ul><li>This submission has been formed from the individual presentations made during the IEEE 802 Emergency Services Tutorial on 16 th July 2007, San Francisco, California, USA. </li></ul>
    3. 3. IEEE 802 Emergency Services Tutorial <ul><ul><li>20:00 : Introduction [Stephen McCann] </li></ul></ul><ul><ul><li>20:05 : Regulations (An Engineer’s Viewpoint) [Scott Henderson] </li></ul></ul><ul><ul><li>20:20 : 802.1AB Location [Manfred Arndt] </li></ul></ul><ul><ul><ul><li>LLDP-REV </li></ul></ul></ul><ul><ul><li>20:35 : 802.11v Location [Dave Stephenson] </li></ul></ul><ul><ul><li>20:50 : 802.11u [Matthew Gast] </li></ul></ul><ul><ul><li>21:20 : Authority – Authority [Richard Paine] </li></ul></ul><ul><ul><li>Questions/Next Steps [Stephen McCann] </li></ul></ul>
    4. 4. <ul><li>Emergency Services Regulations (An Engineer’s Viewpoint) </li></ul><ul><li>G. Scott Henderson </li></ul><ul><li>Research In Motion </li></ul>
    5. 5. Emergency Services Organizations <ul><li>Government </li></ul><ul><ul><li>FCC </li></ul></ul><ul><ul><li>UE Commission (Expert Group on Emergency Access (EGEA) ) </li></ul></ul><ul><ul><li>ATIS ESIF NGES </li></ul></ul><ul><ul><li>ANSI HSSP </li></ul></ul><ul><ul><li>US DoT </li></ul></ul><ul><ul><li>Emergency Services Project in Austria </li></ul></ul><ul><ul><li>Canadian Radio-television and Telecommunications Commission ( CRTC ) </li></ul></ul><ul><li>ES </li></ul><ul><ul><li>NENA = National Emergency Number Assoc. </li></ul></ul><ul><ul><li>APCO = Assoc. of Public Safety Communications Officials </li></ul></ul><ul><li>Standards </li></ul><ul><ul><li>IETF ECRIT </li></ul></ul><ul><ul><li>IETF GEOPRIV / LoST </li></ul></ul><ul><ul><li>WiMAX Forum </li></ul></ul><ul><ul><li>WiFi Alliance </li></ul></ul><ul><ul><li>ETSI EMTEL </li></ul></ul><ul><ul><li>ETSI TISPAN </li></ul></ul><ul><ul><li>3GPP (IMS) </li></ul></ul><ul><ul><li>3GPP2 </li></ul></ul><ul><ul><li>IEEE 802.1AB </li></ul></ul><ul><ul><li>IEEE 802.11 u, v </li></ul></ul><ul><ul><li>IEEE 802.16 </li></ul></ul><ul><ul><li>TIA LLDP-MED </li></ul></ul><ul><ul><li>TIA TR-45 </li></ul></ul><ul><ul><li>OMA </li></ul></ul><ul><ul><li>ITU-T </li></ul></ul><ul><ul><li>OCG </li></ul></ul><ul><ul><li>CTIA </li></ul></ul>
    6. 6. Some of the Regulations/Standards <ul><li>Wireless Communications and Public Safety Act of 1999, Pub. L. No. 106-81, 113 Stat. 1286, § 2(b) (1999) (911 Act). </li></ul><ul><ul><li>U.S. Senate Bill 2007 S428 (amends The Wireless Communications and Public Safety Act of 1999 (47 U.S.C. 615 et seq.) to include IP services) </li></ul></ul><ul><li>FCC </li></ul><ul><ul><li>FCC 05-116 FIRST REPORT AND ORDER AND NOTICE OF PROPOSED RULEMAKING </li></ul></ul><ul><ul><li>FCC 94-102 Docket no 94-102 including order numbers 96-264, 99-96, 99-245 </li></ul></ul><ul><ul><li>FCC DA 05-2945 November 28, 2005 Interconnected VoIP 911 Compliance Letters </li></ul></ul><ul><li>EIA/J-STD-034-1997, Wireless Enhanced Emergency Services </li></ul><ul><li>TIA-J-STD-036-B Enhanced Wireless 9-1-1 Phase 2, 06/2005 </li></ul><ul><li>NENA Interim VoIP Architecture for Enhanced 9-1-1 Services (i2) </li></ul><ul><li>EU Requirements (ETSI EMTEL, TISPAN, EGEA) </li></ul><ul><li>ROW requirements </li></ul>
    7. 7. Distillation: Requirements as they affect IEEE 802 Now <ul><li>Location (Automatic Location Identifier) </li></ul><ul><ul><li>Initial with MS ES request </li></ul></ul><ul><ul><li>Enhanced upon NSAP request </li></ul></ul><ul><ul><li>Most regulatory domains require, some are opt in only </li></ul></ul><ul><li>Support for callback </li></ul><ul><li>Unauthenticated calls </li></ul><ul><ul><li>Roaming and non roaming </li></ul></ul><ul><li>Multi level priority for calls (not universal) </li></ul><ul><li>Multi level priority for LBS (location based services) flows (not universal) </li></ul>
    8. 8. Future Requirements <ul><li>ECALL </li></ul><ul><ul><li>Automated emergency calls </li></ul></ul><ul><li>NG911 </li></ul><ul><ul><li>Support for non voice ES connections </li></ul></ul>
    9. 9. Location Issues <ul><li>FCC 05-116 indicated multiple times that MS assisted location was OK for a start but long term “must include a method for determining a user’s location without assistance from the user” </li></ul><ul><li>Further, wireless VoIP should eventually be equivalent to cellular for 9-1-1 services </li></ul><ul><li>NENA has indicated that current cellular performance is inadequate and are requesting requirements be tightened </li></ul><ul><li>Handover after initiation could affect enhanced location requests, callback </li></ul>
    10. 10. Current Location Requirements <ul><li>Carriers are required to have the capability to identify the latitude and longitude of the mobile units making 911 calls - For network-based solutions: 100 meters for 67% of calls, and 300 meters for 95% of calls; For handset-based solutions: 50 meters for 67% of calls, and 150 meters for 95% of calls </li></ul>
    11. 11. Other Location Interests <ul><li>Lawful Intercept (CALEA, RIPA, etc.) </li></ul><ul><ul><li>Communications Asssistance for Law Enforcement Act, Pub. L. No. 103-414, 108 Stat. 4279 (1994) (codified as amended in sections of 18 U.S.C. and 47 U.S.C.) </li></ul></ul><ul><ul><li>Communications Assistance for Law Enforcement Act, Report and Order, CC Docket No. 97-213, released March 15, 1999 (“First Report and Order”) </li></ul></ul><ul><ul><li>Communications Assistance for Law Enforcement Act, Report and Order, CC Docket No. 97-213, released August 31, 1999 (“Second Report and Order”) </li></ul></ul><ul><ul><li>Communications Assistance for Law Enforcement Act, Report and Order, CC Docket No. 97-213, released August 31, 1999 (“Third Report and Order”) </li></ul></ul><ul><ul><li>Communications Assistance for Law Enforcement Act and Broadband Access and Services, ET Doc. 04-295, 19 FCC Rcd 15676 (Aug. 9, 2004) (“CALEA and Broadband Notice of Proposed Rulemaking and Declaratory Ruling”) </li></ul></ul><ul><ul><li>Communications Assistance for Law Enforcement Act and Broadband Access and Services, ET Doc. 04-295, released September 23, 2005 (“CALEA and Broadband First Report and Order”) </li></ul></ul><ul><ul><li>FCC regulations: 47 C.F.R (Subpart U) § 64.100 et seq. </li></ul></ul><ul><ul><li>J-STD 025B (TIA/ANSI) </li></ul></ul><ul><li>Location Based Commercial Services </li></ul><ul><li>DFS </li></ul><ul><ul><li>Prevent erroneous AP setup </li></ul></ul><ul><ul><li>Loss of spectrum in Canada, possibly France </li></ul></ul>
    12. 12. 802.1AB-Rev Proposal for Device Specific Location Delivery over Wireless LANs Manfred Arndt - manfred.r.arndt@hp.com
    13. 13. Key Emergency Service Location Steps 1 <ul><li>Determination - process used to calculate or measure the physical location. For wireless, this involves measurement methods (signal strength triangulation, time of arrival, etc) </li></ul><ul><li>Acquisition - protocol mechanism used to deliver location info to clients </li></ul><ul><li>Conveyance - protocol mechanism use by clients to deliver location to routing elements and Public Service Access Point (PSAP). This will be PIDF-LO 2 elements in the SIP header as defined by IETF Geopriv WG </li></ul>1. NENA VoIP Location Working Group: Background - Location Requirements 2. Presence Information Data Format (PIDF) for Location Objects (LO)
    14. 14. Wireless Location Determination <ul><li>Let access network interact with drivers and physical layer to determine enhanced location accuracy </li></ul><ul><ul><li>Softphone application are user space programs that do not need to be involved with location determination and must not require driver specific knowledge for every access technology on a given device (e.g. GPRS, 802.11, 802.16, etc.) </li></ul></ul><ul><ul><li>Use simple low level frames to exchange signal level, channel, etc. </li></ul></ul><ul><ul><li>Multiple mechanisms are required, to support clients without 11v capabilities, proprietary vendor specific solutions, etc. </li></ul></ul><ul><ul><li>Must keep unnecessary complexity out of driver, since this exposes too many security and buffer-over run vulnerabilities </li></ul></ul>
    15. 15. Location Acquisition <ul><li>Define a mechanism applicable across all IEEE 802 networking technologies for the access network to deliver location info to clients </li></ul><ul><ul><li>Must not require softphone application to use a unique interfaces for every technology supported on a given device (e.g. GPRS, 802.11, 802.16, etc.) </li></ul></ul><ul><ul><li>This is a management protocol that does not belong in a kernel space </li></ul></ul><ul><ul><li>Very low interest in 11v & 11k from several radio chipset manufacturers </li></ul></ul><ul><ul><li>Must not require any driver modifications </li></ul></ul><ul><ul><ul><li>Must be able to support some level of client location, via user mode SW only </li></ul></ul></ul><ul><ul><ul><li>Drivers updates for embedded devices is challenging and in practice rarely done </li></ul></ul></ul><ul><ul><ul><li>New location formats, if defined, must not require a new rev of driver (past experience has shown that new formats are likely) </li></ul></ul></ul><ul><ul><li>Must align with IETF ECRIT Emergency Call Service architecture and IETF Geopriv location-based services </li></ul></ul>
    16. 16. 802.1AB-Rev Applicability to 802.11 <ul><li>802.1AB benefits </li></ul><ul><ul><li>802.1AB operates above the MAC service layer, and as such can be easily implemented, without requiring any driver modifications </li></ul></ul><ul><ul><li>Reduced complexity with high interoperability potential </li></ul></ul><ul><ul><li>Added benefit of supporting any type of location based service (not just ECS) </li></ul></ul><ul><ul><li>Applicable to all IEEE 802 networks and would provide common interface across many networking technologies for ECS capable software applications </li></ul></ul><ul><li>802.1AB (LLDP) and ANSI/TIA-1057 (LLDP-MED) applicability </li></ul><ul><ul><li>Industry accepted solution, already deployed in many wired IP phones and Ethernet bridges </li></ul></ul><ul><ul><li>Believed all interfaces required for ECS location delivery are defined today </li></ul></ul><ul><ul><li>Draft IETF Emergency Services Best Practices - all telephone and mobile devices MUST support LLDP-MED location (DHCP and yet to be defined L7 method must also be supported) </li></ul></ul><ul><ul><ul><li>DHCP snooping and L7 mechanism not well suited for fine-grain location delivery, since no interface for interaction with access points and servers are defined </li></ul></ul></ul><ul><li>802.1AB-Rev applicability </li></ul><ul><ul><li>In the May 2007 Interim, it was decided to allow sending LLDP to unicast addresses specifically to support 802.11 stations </li></ul></ul><ul><ul><li>As such, LLDP-MED can provide physical location delivery of the AP (via multicast) as well as station specific location (via unicast) </li></ul></ul>
    17. 17. VoWLAN Location Overview <ul><li>AP can auto-discover it’s physical location via LLDP-MED from wired bridge </li></ul><ul><ul><li>Bridges must support LLDP-MED location delivery anyway, for wired IP phones </li></ul></ul><ul><li>Wireless stations would quickly discover new physical location on roaming </li></ul><ul><ul><li>802.1AB-Rev “fast-start” provides timely location discovery on roaming </li></ul></ul><ul><ul><li>802.1AB-Rev “rapid transmission” provides timely updates for moving stations with low overhead for stationary devices (e.g. eliminates client “where am I?” polling) </li></ul></ul><ul><li>Device location reference point </li></ul><ul><ul><li>All APs must advertise ‘AP specific location’ using LLDP multicast (suitable for many cases) </li></ul></ul><ul><ul><li>APs capable of higher accuracy can optionally advertise ‘client specific location’ via 802.1AB-Rev unicast mode </li></ul></ul>
    18. 18. Summary <ul><li>802.1AB provides several advantages for physical location delivery </li></ul><ul><ul><li>MAC independent , well defined standard, that can run in user space </li></ul></ul><ul><ul><li>Simple and effective with high interoperability potential </li></ul></ul><ul><ul><li>Existing industry accepted solution, already deployed on wired Ethernet </li></ul></ul><ul><ul><li>Supports both client specific location (&quot;where am I?&quot;) and network specific location (&quot;where are you?&quot;) to align with 802.11 requirements </li></ul></ul><ul><ul><li>Can provide common ECS interface across all 802 networking technologies </li></ul></ul><ul><li>Already agreed on 802.1AB-Rev changes beneficial to this proposal </li></ul><ul><ul><li>Fast-start supports timely location discovery on roaming </li></ul></ul><ul><ul><li>Rapid transmission well suited for timely updates of moving stations and low overhead for stationary devices (e.g. station doesn’t have to continuously poll AP) </li></ul></ul><ul><ul><li>Unicast address mode for client specific location </li></ul></ul>Recommend decoupling location determination from acquisition in wireless and use LLDP-MED
    19. 19. <ul><li>Enables Physical Location Services, including Emergency Call Service (ECS) </li></ul><ul><ul><li>Supports NENA E911 and other location services (for example NENA TID 07-501) </li></ul></ul><ul><li>Multiple Location Formats Supported, and easily extensible </li></ul><ul><ul><li>Coordinate-based LCI (Location Configuration Information) subtype as defined by IETF RFC 3825 </li></ul></ul><ul><ul><li>Civic Address LCI subtype defined by IETF RFC 4676 </li></ul></ul><ul><ul><li>ELIN (Emergency Location Identification Number) subtype, for traditional PSAP Emergency Calls </li></ul></ul><ul><ul><li>One or more formats may be used simultaneously for different endpoint requirements </li></ul></ul><ul><li>Two ECS methods supported (End-device & Notification based) </li></ul><ul><ul><li>Bridge advertises periodic location info for endpoint to use </li></ul></ul><ul><ul><li>Bridge sends notification whenever a new endpoint is detected or an endpoint moves </li></ul></ul>ANSI/TIA-1057 Location TLV
    20. 20. <ul><li>Wireless location </li></ul><ul><li>Allan Thomson, Cisco </li></ul>
    21. 21. 3 Important Presence Requirements <ul><li>Capability Advertisement </li></ul><ul><ul><li>The ability for the infrastructure and STAs to advertisement their capabilities </li></ul></ul><ul><li>Location determination </li></ul><ul><ul><li>The ability to control and manage location determination features of wireless devices </li></ul></ul><ul><ul><li>Location determination is necessary for reliable and accurate location to be distributed </li></ul></ul><ul><li>Location distribution </li></ul><ul><ul><li>The ability to distribute location information between wireless infrastructure and wireless STAs </li></ul></ul>
    22. 22. Capability Advertisement <ul><li>Requirement to provide unique capability exchange per STA </li></ul><ul><ul><li>Not all STAs will require the same information format…etc </li></ul></ul><ul><li>AP must respond to location requests if AP advertises capability </li></ul><ul><li>STAs advertise their location capabilities in Beacons, Probe Responses, (Re)Association Requests </li></ul><ul><li>Capability information includes </li></ul><ul><ul><li>Format (CIVIC, Geo, Location by Reference…etc) </li></ul></ul><ul><ul><li>Encoding (Binary, XML…etc) </li></ul></ul><ul><ul><li>Resolution </li></ul></ul><ul><ul><li>Capable of providing </li></ul></ul><ul><ul><ul><li>self-location </li></ul></ul></ul><ul><ul><ul><li>remote-location </li></ul></ul></ul>
    23. 23. Location Determination Requires… <ul><li>Reliable and timely communication of frames from a STA </li></ul><ul><li>STA frames must be detected close-in-time by multiple APs </li></ul><ul><li>Appropriate presence policy applied by APs for all associated STAs </li></ul><ul><li>Goal: To provide measurements necessary for high accuracy above “associated AP” accuracy </li></ul>
    24. 24. Typical Location Determination Messages
    25. 25. Floor Level Accuracy Requirement <ul><li>Determining correct floor is required for in-building presence and emergency services </li></ul><ul><li>Within buildings devices (e.g. phones) can associate to any AP on any floor </li></ul><ul><ul><li>Depends on RF Coverage </li></ul></ul><ul><li>Phone presence announcements seen on multiple floors </li></ul><ul><li>Location determination resolves appropriate floor based on all measurements </li></ul>
    26. 26. Building Accuracy Requirement <ul><li>Determining correct building is required for presence and emergency services </li></ul><ul><li>Across buildings: devices (phones) can associate to any AP in any building within RF coverage </li></ul>
    27. 27. Location Determination Requirements <ul><li>AP Responsibilities </li></ul><ul><li>Manages setup of STA presence messages for </li></ul><ul><ul><li>Frequency </li></ul></ul><ul><ul><ul><li>Stationary and In Motion parameters </li></ul></ul></ul><ul><ul><li>Interframe Interval </li></ul></ul><ul><ul><li>Timing Measurements </li></ul></ul><ul><ul><li>Channel set </li></ul></ul><ul><ul><ul><li>Channel Numbers and Regulatory Class </li></ul></ul></ul><ul><li>Policy administration </li></ul><ul><ul><li>AP can ensure all STAs in BSS conform to presence reporting policies </li></ul></ul><ul><ul><li>Can disassociate STA if failure to comply </li></ul></ul><ul><li>Additional measurements in 11k such as Measurement Request/Response help location determination </li></ul><ul><li>STA Responsibilities </li></ul><ul><li>Sends presence messages based on AP control </li></ul><ul><li>Presence Messages include: </li></ul><ul><li>Radio information including </li></ul><ul><ul><li>Antenna gain, Transmit Power, Received RSNI, Antenna ID for Rx and Tx </li></ul></ul><ul><li>Timing Measurements </li></ul><ul><li>Motion Indication </li></ul>
    28. 28. Location Distribution Requirements <ul><li>Secure </li></ul><ul><ul><li>Complies with privacy rules around location </li></ul></ul><ul><li>Scalable </li></ul><ul><ul><li>Enables network to provide accurate location for large number of clients </li></ul></ul><ul><li>Timely </li></ul><ul><ul><li>Enables network to provide location very close-in-time to emergency events or other location events </li></ul></ul><ul><li>Specific </li></ul><ul><ul><li>Enables network to provide location specific for a device in the format and options it requires </li></ul></ul>
    29. 29. Location Distribution: Request Based <ul><li>Meets all requirements </li></ul><ul><li>Secure </li></ul><ul><ul><li>Sent by either AP or non-AP STA in unicast frame with 802.11w encryption </li></ul></ul><ul><li>Timely </li></ul><ul><ul><li>Options for one-shot “On Demand” or event-based “subscription” </li></ul></ul><ul><li>Specific </li></ul><ul><ul><li>STA can request its own location with options </li></ul></ul><ul><ul><ul><li>Format (CIVIC, Geo…etc) </li></ul></ul></ul><ul><ul><ul><li>Encoding (Binary, ASCII) </li></ul></ul></ul><ul><ul><ul><li>Resolution (AP, XY, Building…etc) </li></ul></ul></ul><ul><ul><ul><li>Accuracy Estimate </li></ul></ul></ul><ul><ul><li>STA can request the AP’s location </li></ul></ul><ul><ul><li>STA can provide it’s own location if capable of self-determination </li></ul></ul><ul><li>Scalable </li></ul><ul><ul><li>Single message when required </li></ul></ul><ul><ul><li>Avoids continuous transmission of broadcasts or unicasts </li></ul></ul>
    30. 30. Location Distribution: Broadcast <ul><li>Sent by APs in beacon or probe response </li></ul><ul><li>Does not meet all requirements </li></ul><ul><li>Not secure </li></ul><ul><ul><li>Can be seen by any non-associated STAs, security risk? </li></ul></ul><ul><ul><li>For general location distribution, privacy is required </li></ul></ul><ul><ul><li>For Emergency Services location distribution, no privacy may be acceptable </li></ul></ul><ul><li>Not timely </li></ul><ul><ul><li>Broadcast has to be scheduled very infrequently </li></ul></ul><ul><li>Not scalable </li></ul><ul><ul><li>No way of knowing which clients are using location or not </li></ul></ul><ul><ul><li>Adds load to the infrastructure to provide location when unclear who and what is using it </li></ul></ul><ul><ul><li>Wastes Over-The-Air bandwidth </li></ul></ul><ul><li>Not specific </li></ul><ul><ul><li>Broadcast relates to AP position not STAs </li></ul></ul>
    31. 31. TGv Meets Requirements 1 : ANSI/TIA-1057 LLDP-MED Provides broadcast Provides Secure, Timely, Scalable, Specific Location Distribution None Provides control and high accuracy Location Determination None Provides per STA capability advertisement Capability Advertisement LLDP-MED 1 TGv Requirement
    32. 32. Final Thoughts <ul><li>Location object format is common across TGv and other protocols </li></ul><ul><li>Wireless location requires a protocol that fits a dynamic physical environment </li></ul><ul><li>Supporting one protocol for location determination and another for distribution complicates the infrastructure and the client </li></ul><ul><li>Location requirements for wireless MAN systems are equally, if not more, challenging </li></ul><ul><li>Location security and privacy critical issues </li></ul><ul><li>TGv meets all requirements for wireless location and emergency services </li></ul>
    33. 33. <ul><li>802.11u and Emergency Services </li></ul><ul><li>Matthew Gast </li></ul><ul><li>Trapeze Networks </li></ul><ul><li>Note: This presentation is based on 802.11u-D1.0 and subject to change by future standards activity </li></ul>
    34. 34. Major Features of 802.11u <ul><li>External network (“SSPN”) interface for extended authorization </li></ul><ul><li>New QoS features </li></ul><ul><li>Generic Advertising Service (GAS) </li></ul><ul><li>Emergency services recommendations (informative) </li></ul><ul><ul><li>Use case #1: open network </li></ul></ul><ul><ul><li>Use case #2: public credentials </li></ul></ul>
    35. 35. External Network (SSPN) Interface <ul><li>SSPN = Subscription Service Provider Network </li></ul><ul><ul><li>SSP holds user credentials </li></ul></ul><ul><ul><li>May build or partner with 802.11 access networks </li></ul></ul><ul><li>The SSPN may direct the STA-AN, for example by: </li></ul><ul><ul><li>Requiring that a certain encryption type is used (e.g. CCMP only) </li></ul></ul><ul><ul><li>Setting allowed access rates for different types of traffic (e.g. 80 kbps voice, no video, and up to 500 kbps best effort) </li></ul></ul><ul><ul><li>Specifying a minimum delay bound on transmitted frames </li></ul></ul><ul><li>Admission Control </li></ul><ul><ul><li>TSPEC processing is subject to authorized data rates as specified by SSPN </li></ul></ul>
    36. 36. QoS Signaling in 802.11u <ul><li>Expedited Bandwidth Request </li></ul><ul><ul><li>802.11 has only four categories (voice, video, best effort, and background) </li></ul></ul><ul><ul><li>Many STAs may request high-priority voice service </li></ul></ul><ul><ul><li>EBR allows a STA to describe the reason that it is requesting service and the network can act accordingly </li></ul></ul><ul><ul><li>Example: emergency calls and first-responder traffic can pre-empt “normal” voice traffic </li></ul></ul><ul><li>QoS Map </li></ul><ul><ul><li>802.11 QoS settings only affect last-hop access; QoS Map allows APs and STAs to extend higher-layer QoS settings </li></ul></ul><ul><ul><li>Ensures correct QoS treatment of frames even if destination networks use DSCP differently </li></ul></ul>
    37. 37. Generic Advertising Services (GAS) <ul><li>Interface to external information sources </li></ul><ul><ul><li>Example: Carrier of 802.21 data </li></ul></ul><ul><ul><li>Extensible for types beyond 802.21 </li></ul></ul><ul><li>“ Native” query mode </li></ul><ul><ul><li>Assists STA with information stored in the 802.11 access network </li></ul></ul><ul><ul><li>Example: enhances scan for multi-SSID use, so that a secondary SSID can be used for emergency services </li></ul></ul><ul><li>Operational details (in brief) </li></ul><ul><ul><li>Multicast/unicast operation </li></ul></ul><ul><ul><li>Query size limits: administrators can configure response limit size </li></ul></ul><ul><ul><li>Emergency Services native query: type of authentication </li></ul></ul>
    38. 38. Emergency Services Use Case #1: Dedicated SSID <ul><li>Uses “emergency services only” (ESO) bit to signal that the SSID can support emergency services without any 802.11-level security </li></ul><ul><li>Network must enforce appropriate security (out of scope for 802.11) </li></ul><ul><ul><li>Network is “locked down” to emergency calls only </li></ul></ul><ul><ul><li>e.g. dedicated VLAN, IP firewall </li></ul></ul>AP (11u-capable) STA (11u-capable) Beacon (w/ESO bit) Association Request Association Response Initiate higher-layer call (e.g. SIP) GAS Native Query (SSID list + ES info) GAS Native Query Response Restricted Network e.g. dedicated VLAN, IP filtering, etc. Note: SSID list is optional; used in multi-SSID deployments ADDTS Request (w/Expedited BW Req.) ADDTS Response
    39. 39. Emergency Services Use Case #2: Public Credentials <ul><li>ESO calls have no cryptographic protection (tampering, injection, forgery) </li></ul><ul><li>To provide cryptography, 802.11i security must be used </li></ul><ul><ul><li>Pre-shared key for all emergency networks is not feasible </li></ul></ul><ul><ul><li>802.11u provides a way for a network to set up an “emergency public credential” to use EAP methods </li></ul></ul><ul><li>EAP method needs clarification </li></ul>AP (11u-capable) STA (11u-capable) Association Request Association Response Initiate higher-layer call (e.g. SIP) GAS Native Query (emergency public credentials) GAS Native Query Response (credentials) EAPOL/EAP-Identity-Response (credentials) EAPOL/EAP-Identity-Request EAP method authentication 4-Way Handshake ADDTS Request (w/Expedited BW Request) ADDTS Response
    40. 40. <ul><li>Authority and Emergency Services </li></ul><ul><li>Richard Paine </li></ul><ul><li>Boeing </li></ul>
    41. 41. Authorities <ul><li>Police </li></ul><ul><li>Fire </li></ul><ul><li>Rescue </li></ul><ul><li>Emergency Services </li></ul><ul><li>Government Organization </li></ul><ul><li>Non-Governmental Organization (NGO) </li></ul><ul><li>Military </li></ul><ul><li>Airport </li></ul><ul><li>Airplane </li></ul><ul><li>Ship </li></ul><ul><li>Bus </li></ul>
    42. 42. Definitions <ul><li>http://psc.wi.gov/apps%5Cvia%5Cdocument%5C5TI1076%5CUSC%20Cellular-PCS%20E911%20Emer%20Svcs%20011504.pdf </li></ul><ul><li>“ E911 Authority&quot; means a municipality or other State or Local government unit, or an authorized agent of one or more municipalities or other State or Local government units to whom authority has been lawfully as the administrative entity to manage a public emergency telephone system for emergency police, fire, and emergency medical services through the use of one telephone number, 911. </li></ul>
    43. 43. PSTN Provider 911 <ul><li>PSTN Wireless Service Providers offer physical locations </li></ul><ul><li>PSTN Providers have agreements with 911 authorities </li></ul>
    44. 44. Ethernet Provider 911 <ul><li>Ethernet (802.3) Wired Service Providers offer physical locations </li></ul><ul><li>Ethernet (802.3) Wired Service Providers have agreements with 911 authorities </li></ul>
    45. 45. Cellular Service Provider E911 <ul><li>Cellular Wireless Service Providers offer GPS and Cellular location </li></ul><ul><li>GPS location not generally avbl in-building </li></ul><ul><li>Cellular location accuracy must be within 100m </li></ul><ul><li>Providers have agreements with FCC </li></ul>
    46. 46. 802.11 Service Provider E911 <ul><li>802.11 Service Providers need to have 11k location (any source) </li></ul><ul><li>802.11 VOIP providers will have 11k or 11v location </li></ul><ul><li>GPS location not generally avbl in-building </li></ul><ul><li>WLAN RTLS location accuracy will be within 10m </li></ul><ul><li>Enterprises with 802.11 have agreements with E911 authorities </li></ul>
    47. 47. Large Enterprise E911 <ul><li>Boeing has ~60,000 seats of VOIP </li></ul><ul><li>Awarded contract to supply E911 services via GW </li></ul><ul><li>Future is VOIP over the WLAN </li></ul><ul><li>Need to provide E911 locations via WLAN </li></ul><ul><ul><li>Labels on portable and mobile computing devices </li></ul></ul>
    48. 48. IEEE 802.11 E911 Issues <ul><li>Guns and hoses security </li></ul><ul><li>Business Locations (mobile equipment and people) </li></ul><ul><li>Assurances that identities are authentic </li></ul><ul><li>Dumbing down technology to fit switched telephony </li></ul>
    49. 49. Enterprise VOIP E911 <ul><li>Caution:911 service using this device may be limited or unavailable. </li></ul>
    50. 50. Use Case: Boeing 1 MP Sensor MP Sensor MP Sensor MP Sensor MP Sensor MP Sensor MP Sensor MAP MAP MPP MP Sensor MP Sensor MP Sensor MP Sensor Primary Route Secondary Route Infrastructure Network
    51. 51. Use Case: Boeing 2
    52. 52. Use Case: Boeing 3 – Guns and Hoses Offices Mesh Points Mesh Points
    53. 53. Use Case: Boeing 4 – Guns and Hoses Factory Mesh Points Access Points N
    54. 54. Large Enterprise E911
    55. 55. Authority Issues <ul><li>Authority </li></ul><ul><li>Policy </li></ul><ul><li>Control </li></ul>
    56. 56. Authority <ul><li>Governmental Organizations (GOs) </li></ul><ul><li>Non-governmental Organizations (NGOs) </li></ul><ul><li>Legitimacy and Establishment of ES Organizations </li></ul><ul><li>Management of Authorities </li></ul>
    57. 57. Policy <ul><li>Policy Creation </li></ul><ul><li>Policy Decision </li></ul><ul><li>Policy Enforcement </li></ul>
    58. 58. 802.11 Emergency Services Objectives <ul><li>Why have this tutorial? </li></ul><ul><li>What is the problem? </li></ul><ul><li>What do we want to achieve in 802.11? </li></ul>
    59. 59. What does 802.11 Want to Achieve? <ul><li>11k Location - Measurement Request/Response </li></ul><ul><li>11u Interworking – E911 using either RRM or NM (non-AP uses AP location if available to SSPN) </li></ul><ul><li>11v Location - Management Request/Response </li></ul>
    60. 60. Next Generation 802.11 Wireless Security <ul><li>Policy Development </li></ul><ul><li>Policy Decision Points </li></ul><ul><li>Policy Enforcement Points </li></ul><ul><li>Privacy </li></ul><ul><li>Security </li></ul>
    61. 61. Policy – Wiki Definition <ul><li>A policy is a deliberate plan of action to guide decisions and achieve rationale outcome(s). The term may apply to government, private sector organizations and groups, and individuals. Examples of policies include presidential executive orders , corporate privacy policies , or even Wikipedia's policies . </li></ul><ul><li>Policy may also refer to the process of making important organizational decisions, including the identification of different alternatives such as programs or spending priorities, and choosing among them on the basis of the impact they will have. Policies can be understood as political, management, financial, and administrative mechanisms arranged to reach explicit goals. </li></ul>
    62. 62. Conclusions <ul><li>11k and 11v providing E911 location for WLAN devices and 11u their interworking </li></ul><ul><li>Future Requirements </li></ul><ul><ul><li>Policy </li></ul></ul><ul><ul><li>Next generation of WLAN security </li></ul></ul><ul><ul><ul><li>Identity </li></ul></ul></ul><ul><ul><ul><li>IEEE 802.11 Device Security </li></ul></ul></ul>
    63. 63. SMA Elements: PKI Badge cert Temp cert Client RA SSL/TLS Tunnel 1 2 Boeing PKI SLDAP <ul><li>Badge used for Client Auth; TempCert request sent to RA </li></ul><ul><li>RA issues TempCert </li></ul><ul><li>Client has TempCert available for up to 8 hours </li></ul>TempCert Provisioning Process
    64. 64. SMA Elements: NDS <ul><li>Support for real-time endpoint mobility & location data </li></ul><ul><li>Future integration with Boeing DNS and directory (CED, NAMS-ng) infrastructure </li></ul>Enterprise DNS Proxy Security Perimeter Virtual Directory SLDAP Client Policy Decision Daemon Middleboxes Client DNS DDNS Location Server Directory Information Flow
    65. 65. Concluding Straw Poll <ul><li>Would you like to see these issues discussed more in November 2007? </li></ul><ul><li>802 Ad Hoc (32) </li></ul><ul><li>802 Architecture Group (8) </li></ul><ul><li>Something Else (4) </li></ul><ul><li>Nothing (0) </li></ul>