Emergency Services Over IEEE 802 Tutorial V1.3
Emergency Services Over IEEE 802 Tutorial V1.3
Emergency Services Over IEEE 802 Tutorial V1.3
Cisco Intel
Nokia Nokia
Tutorial
Slide 1
March 2007
Content
Scope & Motive Introduction Regulations Media types 802 technologies Other SDOs What next?
Tutorial
Slide 2
March 2007
Introduction
This tutorial 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.
Tutorial Slide 3 S. McCann, D. Stephenson and V. Gupta
March 2007
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)
Tutorial
Slide 4
March 2007
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.
Tutorial
Slide 5
March 2007
Motive
Organizations, within the US, such as the National Emergency Number Association (NENA), the ATIS Emergency Service Interconnection Forum (ESIF) and the FCC's Network Reliability and Interoperability Council (NRIC) have created considerable documentation identifying requirements and technical needs that must be addressed to support emergency services (i.e. E911) through emerging access technologies. Should IEEE 802 working groups consider including in their standards whatever is needed for the generation and delivery of location identification and callback capability for individuals trying to gain access to emergency services ??
Tutorial
Slide 6
March 2007
Regulations
(I am not a lawyer)
Tutorial
Slide 7
March 2007
Tutorial
Slide 8
March 2007
112 in the EU
Member States shall ensure that, in addition to any other national emergency call numbers specified by the national regulatory authorities, all end-users of publicly available telephone services, including users of public pay telephones, are able to call the emergency services free of charge, by using the single European emergency call number "112". Member States shall ensure that calls to the single European emergency call number "112" are appropriately answered and handled in a manner best suited to the national organisation of emergency systems and within the technological possibilities of the networks. Member States shall ensure that undertakings which operate public telephone networks make caller location information available to authorities handling emergencies, to the extent technically feasible, for all calls to the single European emergency call number "112". http://www.eena.org/view/en/citizen/112_in_eu.html
Tutorial
Slide 9
March 2007
Tutorial
Location information (one or more of ZIP, Address Code, Address, Subscriber ID etc) of user must be provided to the emergency center.
11-06-0460-01-000u-japanese-emergency-call-regulation.ppt
Slide 10 S. McCann, D. Stephenson and V. Gupta
March 2007
Tutorial
March 2007
http://wonkette.com/politics/television/emergency-alert-system-actually-used-183830.php
Tutorial Slide 12 S. McCann, D. Stephenson and V. Gupta
March 2007
Media Types
(I am not a journalist)
Tutorial
Slide 13
March 2007
Media Types
One Way
VoIP SMS/Text/IM Video TTY/TDD (speech impaired)
Interactive
Instant messaging and video could improve the ability to communicate and evaluate the situation and to provide appropriate instruction prior to arrival of emergency crews.
Tutorial
Slide 14
March 2007
Tutorial
Slide 15
March 2007
Tutorial
Slide 16
March 2007
March 2007
March 2007
IEEE 802.1
Tutorial
Slide 19
March 2007
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)
Tutorial
Slide 20
March 2007
IEEE 802.11
Tutorial
Slide 21
March 2007
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)
Tutorial
Slide 22
March 2007
AP
(11u-capable)
EAPOL/EAP-Request/Identity
delay
Tutorial
Slide 23
March 2007
Location
Location information is being developed by IEEE 802.11k and IEEE 802.11v (RFC 3825) Request/Response paradigm
Client may request from the access point
its own location the location of the access point
Tutorial
Slide 24
March 2007
Tutorial
Slide 25
March 2007
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.
Tutorial
Slide 26
March 2007
Tutorial
Slide 27
March 2007
IEEE 802.15
Tutorial
Slide 28
March 2007
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.
Tutorial
Slide 29
March 2007
IEEE 802.16
Tutorial
Slide 30
March 2007
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.
Tutorial
Slide 31
March 2007
IEEE 802.20
Tutorial
Slide 32
March 2007
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 ?
Tutorial Slide 33 S. McCann, D. Stephenson and V. Gupta
March 2007
IEEE 802.21
Tutorial
Slide 34
March 2007
Architecture
AAA
Carrier Network
IEEE 802.21 Information Server
VLAN #5 Note: There does NOT need to be a 1-to-1 mapping between this and SSID #5.
DHCP AP
(11u-capable)
STA
(11u-capable)
SSID #5
Tutorial
Slide 35
March 2007
802.11u AP (MIH-aware)
Beacon (GAS: MIH) Probe REQ Probe RSP (GAS: MIH) GAS init req (MIH IE: e911 req)
comeback_delay
GAS init resp (Query ID, comeback_delay) GAS comeback req (Query ID) GAS comeback rsp (Query ID, e911 accepted) MIH frame rsp (e911 accepted + IS Location)
Tutorial
Slide 36
March 2007
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
Tutorial
Slide 37
March 2007
IEEE 802.22
Tutorial
Slide 38
March 2007
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 Coordinatebased 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.
Tutorial
Slide 39
March 2007
Vehicular Communications
Tutorial
Slide 40
March 2007
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
Tutorial Slide 41 S. McCann, D. Stephenson and V. Gupta
March 2007
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 vehicledata network separate from the cellular network.
Tutorial
Slide 42
March 2007
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.
Tutorial
Slide 43
March 2007
Tutorial
Slide 44
March 2007
codec (e.g. G711) network connection (authentication at layer 2) application authentication (e.g. https) internationalization of emergency dialing codes
Tutorial
Slide 45
March 2007
Other SDOs
3GPP & 3GPP2 TIA TR-45 IETF ECRIT NENA OMA ITU-T ETSI EMTEL OCG EU Commission ComCare
ESIF NGES ANSI HSSP US DoT
Tutorial
Slide 46
March 2007
3GPP
Service requirements from 3GPP TS 22.101
http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/Service_requirementsESW06.ppt
Tutorial
Slide 47
March 2007
3GPP2 S.R0115 All IP-Network Emergency Call Support Stage 1 requirements, produced by TSG-S; recommended for publication on Sept. 14, 2006
http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/3GPP2 IP Based Emergency Calls.ppt
TIA TR-45
Develops performance, compatibility, interoperability and service standards for mobile and personal communications systems Joint effort between TIA TR-45.2 AHES and ATIS WTSC (formerly T1P1) to develop Emergency Services Standards Requirements http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/TIA TR45.pdf
Tutorial
Slide 48
March 2007
IETF ECRIT
ECRIT working since 2004 Building off of the GEOPRIV work and architecture And the sipping-emergency design team of SIPPING Initial focus on using location information to learn how to direct emergency calls on the Internet
architecture = localised
IETF ECRIT Architecture http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/IETF-Overview.ppt SIP Location Conveyance: http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/SIP_Location_Conveyance.ppt Emergency Services Identifiers http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/ESW06-service-urn.ppt LoST and LoST Architecture http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/ESW06-LoST.ppt DHCP Civic & Geo http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/ESW06-civic.ppt http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/Geo DHCP Option 123 for LCI.ppt Geopriv L7 LCP http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/L7LCP-ESW06.ppt
Tutorial
Slide 49
March 2007
Architecture and solutions based on IETF protocols http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/NENA NG911 arch for SDO workshop.ppt NENA sent an liaison to IEEE 802, regarding location issues. IEEE 802.11u are currently addressing this liaison.
Tutorial Slide 50 S. McCann, D. Stephenson and V. Gupta
March 2007
OMA Mentioning of Mobile Location Services, Secure User Plane for Location, Mobile Location Protocol, Roaming Location Protocol, Privacy Control Protocol
http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/OMA-LOC ES Coordination WorkshopR01.ppt
ITU-T Work focused on Telecommunications for Disaster Relief and Early Warning
http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/TDR in ITU-T Oct 06.ppt
Tutorial
Slide 51
March 2007
ETSI EMTEL
Special Committee on Emergency Communications Act as a key coordinator in getting requirements on Emergency Communications, outside ETSI (i.e. from different stakeholders) and inside ETSI (i.e. ETSI Bodies). Provide requirements on issues of network security, network integrity, network behaviour in emergency situations, and emergency telecommunications needs in networks http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/ EMTEL Presentation_ECRIT 200.ppt
OCG
The Open Geospatial Consortium, Inc. (OGC) is a non-profit, international voluntary consensus standards organization that is leading the development of standards for geospatial and location based services.
Tutorial
Slide 52
March 2007
EU Commission Presentation on the EU Regulatory Framework Discussion on establishment of document outlining responsibilities of different market players http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/EUCommission.ppt COMCARE US Organization Overview and pointers to OASIS standards for authority-to-authority communication. http://www.ietfecrit.org/EmergencyWorkshop2006/slides/Emergency Services SDO Workshop Architecture.ppt Agency Locator Service Prototype http://www.ietfecrit.org/EmergencyWorkshop2006/slides/Emergency Services SDO Workshop Agency Locator Services.ppt
Tutorial Slide 53 S. McCann, D. Stephenson and V. Gupta
March 2007
ESIF NGES Next Generation Emergency Services (NGES) Subcommittee created at ESIF 17 in Las Vegas Provide liaison with global SDOs for the standards development coordination Plans to develop stage 2/3 standards based on NENAs i3 requirements and to would like to act as SDO coordinator on emergency services The goal is to ensure other Standards are aware of NG9-1-1 work being done at NENA and ESIF http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/ESIF NGES Update.ppt
ANSI HSSP The ANSI Homeland Security Standards Panel (HSSP) Plans to offer a forum for standards and coordination Aims to produce a white paper to outline key issues, emergency communications standards, identified gaps, and resources for further information/possible partnerships http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/ANSI-HSSP SDO Emergency Services Coordination Workshop.ppt
Slide 54 S. McCann, D. Stephenson and V. Gupta
Tutorial
March 2007
Tutorial
Slide 55
Washington DC, USA, on the 10, 11 and 12 April 2007. More details about the workshop via this webpage:
http://www.emergency-services-coordination.info/
Tutorial
Slide 56
March 2007
Concluding Issues
Dont assume that IEEE 802 technologies can already support all ES requirements:
callback facility ? terminal location ? geospatial or civic? does Civic location, make sense, for large scale systems?