250 likes | 263 Views
Learn about ongoing efforts to standardize emergency services within IEEE 802.11 wireless technologies, including emergency voice calls, network push alerts, and vehicle communication.
E N D
Emergency Services for 802.11 Date: 2007-04-11 Authors: S. McCann et al
Note • This presentation was originally produced for an IEEE 802 tutorial on 13th March 2007. This version has been re-formatted and shortened for: • 2nd SDO Emergency Workshop, Washington D.C. 2007 S. McCann et al
Content • Scope & Motive • Introduction • Requirements • IEEE 802.11 • Vehicular Communications • Concluding Issues S. McCann et al
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. S. McCann et al
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 S. McCann et al
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 S. McCann et al
Requirements S. McCann et al
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. • http://en.wikipedia.org/wiki/Emergency_telephone_number#Emergency_numbers_by_country S. McCann et al
Emergency Alert System (EAS) http://wonkette.com/politics/television/emergency-alert-system-actually-used-183830.php S. McCann et al
IEEE 802.11 S. McCann et al
IEEE 802.11 Working Group U V N Interworking with External Networks Wireless Network Management 5 GHz High Throughput I Enhanced Security Mechanisms S SC K ESS Mesh Wireless Next Generation Radio Resource Measurements E MAC QoS Enhancements Y P J Wireless Access Vehicular Environment 3650-3700 MHz Operations Japan Extensions MAC W R H Management Frame Security Fast BSS Transition 5 GHz Spectrum Managed G PHY M T 2.4GHz High Rate >20Mbps Maintenance Wireless Performance Prediction SC D B Regulatory Updates A 2.4 GHz 802.11b 5.5 Mbps 11 Mbps 5 GHz 802.11a 6, 12, 24 Mbps 9-54 Mbps (opt) Infra-Red 1 Mbps 2 Mbps (opt) 2.4 GHz Frequency Hopped Spread Spectrum 1 Mbps 2 Mbps (optional) 2.4 GHz Direct Sequence Spread Spectrum 1 Mbps 2 Mbps C Reaffirmed 802.11 2003 Completed work in yellow Active 2005 work in red Active 2007 work in Blue International Standard 1999 ISO/IEC 8802-11: 1999 Completed additions in Green Published as IEEE Standard 1997 IEEE Std. 802.11-1997 Initial capabilities in White S. McCann et al
Task Group k - Migrating Current MIBs… NETWORK • 802.11 • Configuration for STA and very limited proprietray RF measurements • Widely implemented in APs, but not standardized • Very simple monitoring of global AP statistics (proprietary implementations only) • 802.1x • Detailed auth state for individual 1x ports • Also some per port statistics • Not widely implemented in access points today • Bridge MIB • Possible to get some info on which STAs are associated with an AP • Implemented in some APs • Not 802.11 specific, little MAC, and no PHY statistics LINK/MAC PHY To… • Standardized RF Measurements and Methods • Basic measurements available to upper layers from AP and Client • Neighbor lists for AP’s - Client association to AP lists • Noise histograms - Channel Loading • Station Statistics - Link Measurement • Location Configuration Information • Transmit stream measurement • Accurate power level measurements in dBm referenced at the antenna • Better diagnostics • Obtaining information in a standard form from all equipment • Enable better frequency planning and network optimization and performance • Automated signal/interference surveys • Enable new services • Location awareness capabilities for AP’s and Clients S. McCann et al
Task Group v - Migrating Present Mechanisms… • Radio Resource Management via CSMA and backoff • Disorganized Reuse • No Coordination (except proprietary methods) • Interference growing • Channels likely to be too noisy for QoS NETWORK LINK/MAC PHY To… • Disciplined Wireless Network Management • Reuse via space, time, frequency • AP’s synchronized from common backbone • AP’s/clients communicate across RF channel • Discovery process, followed by self-organizing • Enable auto-configuration processes • Enable Cognitive Radio interference avoidance S. McCann et al
GSM Association Task Group u • Objectives: • To be an integral part in the production of a generically applicable interworking standard for WWAN and other public networks. • To be a point of resolution for external netowrk SDO’s • Convergence of WLAN, WWAN, Networks • Multiple Standards • Internet • Service Providers • QoS • Security • Authentication MMAC } 3GPP IETF IEEE 802.11 WIEN Wireless internetworking w/external networks 3GPP2 Wi-Fi Alliance S. McCann et al
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 S. McCann et al
Issues to be solved for IEEE 802.11 • 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 • Admission Control • QoS – dedicated bandwidth • preemption S. McCann et al
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 • Correct use of RFC 3825 & RFC 4119 ?? S. McCann et al
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. S. McCann et al
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. S. McCann et al
Vehicular Communications S. McCann et al
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 S. McCann et al
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. S. McCann et al
Concluding Issues S. McCann et al
Concluding Issues I • Don’t assume that IEEE 802.11 technologies can already support all ES requirements: • call back facilities ? • terminal location ? geospatial or civic? • IEEE 802.11 needs to conform to both the IETF/NENA and the 3GPP IMS architectures to satisfy all potential interworking scenarios. S. McCann et al
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 802.11 want closer liaisons with other SDOs • Comments welcome S. McCann et al