March 2007 Emergency Services for IEEE 802
Date: 2007-03-13
Authors:
Name
Stephen McCann
Dave Stephenson
Vivek Gupta
Gabor Bajko
Srinivas
Sreemanthula
Company Address Phone email
Siemens Roke Manor Roke Manor Research Ltd
Old Salisbury Lane, Romsey
Hampshire, SO51 0ZN, UK
Cisco
Intel
170 W Tasman Dr. San Jose,
CA 95134
Mailstop JF3-206,
Nokia
2111, NE 25th Avenue,
Hillsboro, OR 97124
Palo Alto, CA
+44 1794 833341 stephen.mccann@roke.co.
uk
+1 408 527 7991 daves@cisco.com
+1 503 712 1754 vivek.g.gupta@intel.com
+1 972 894 5000 Gabor.Bajko@nokia.com
Nokia Irving, TX +1 972 894 5000 Srinivas.Sreemanthula@n okia.com
Tutorial Slide 1 S. McCann, D. Stephenson and V. Gupta

March 2007
•
Scope & Motive
• Introduction
• Regulations
• Media types
• 802 technologies
•
Other SDOs
•
What next?
Emergency Services for IEEE 802
Tutorial Slide 2 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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 Emergency Services for IEEE 802
•
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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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
Tutorial Slide 5 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
Tutorial Slide 7 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
Wireless Enhanced 911 (E911) rules seek to improve the effectiveness and reliability of wireless 911 service by providing 911 dispatchers with additional information on wireless 911 calls.
• The wireless E911 program is divided into two parts - Phase I and Phase
II. Phase I requires carriers, upon valid request by a local Public Safety
Answering Point (PSAP), to report the telephone number of a wireless
911 caller and the location of the antenna that received the call. Phase II requires wireless carriers to provide far more precise location information, within 50 to 300 meters in most cases.
•
The deployment of E911 requires the development of new technologies and upgrades to local 911 PSAPs, as well as coordination among public safety agencies, wireless carriers, technology vendors, equipment manufacturers, and local wireline carriers.
• http://www.fcc.gov/911/enhanced/
Tutorial Slide 8 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
Tutorial
• 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
Slide 9 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• Emergency call (“notification”) regulation is being discussed in Ministry of Internal Affairs and Communications. In operation from 1 st April
2007.
•
For analog telecommunication facilities or equivalent analog fixed telecommunication facilities
1. Emergency call must connect to the local emergency center
2. User device sends its number and location to the emergency center that is nearest the user device.
3. Emergency call maintains a circuit connection or callback function (or equivalent functions)
•
For other voice transmission facilities
– 1 and 2
– Emergency call maintains a circuit connection unless the call termination signal is transmitted from the emergency center
•
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
Tutorial Slide 10 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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_number s_by_country
Tutorial Slide 11 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
http://wonkette.com/politics/television/emergency-alert-system-actually-used-183830.php
Tutorial Slide 12 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
Tutorial Slide 13 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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.
• ...and others as defined in http://tools.ietf.org/wg/ecrit/draft-ietf-ecrit-framework/draft-ietfecrit-framework-00.txt section 12 .
Tutorial Slide 14 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
Tutorial Slide 15 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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
Tutorial Slide 16 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
•
– 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)
•
•
– QoS – dedicated bandwidth
– preemption
Tutorial Slide 17 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
•
– 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)
•
•
– QoS – dedicated bandwidth
– preemption
Tutorial Slide 18 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
IEEE 802.1
Tutorial Slide 19 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
IEEE 802.11
Tutorial Slide 21 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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 S. McCann, D. Stephenson and V. Gupta

March 2007
STA
(11u-capable)
Emergency Services for IEEE 802
AP
(11u-capable)
Configured by Hotspot owner / administrator
Beacon (ESN)
Association request (SSID : Foo)
Association Response (…)
EAPOL/EAP-Request/Identity
EAPOL/EAP-Response/Identity (e.g. anonymous@ESN)
EAP Success (include PMK)
4-Way Handshake
Tutorial Slide 23 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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
• it’s own location
• the location of the access point
• GeoPriv (RFC 4119) used to wrap location information
– Location standard formats supported include GEO and CIVIC
• Control and Measurement mechanisms to enable tracking continuously
Tutorial Slide 24 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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.
• 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.
Tutorial Slide 25 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
In 2003, the FCC allocated 50 MHz of spectrum in the 4.9 GHz band to public safety services. Public safety agencies can use this
4.9 GHz band to implement wireless networks such as IEEE
802.11 for the transmission of mission-critical information such as streaming video, data access, maps, and missing person images.
•
IEEE 802.11 has now been amended to operate within this band and is able to provide emergency facilitator communications such as: police, fire and rescue, disaster relief.
Tutorial Slide 27 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
IEEE 802.15
Tutorial Slide 28 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
IEEE 802.16
Tutorial Slide 30 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
IEEE 802.20
Tutorial Slide 32 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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 Emergency Services for IEEE 802
IEEE 802.21
Tutorial Slide 34 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
AAA
Carrier Network
IEEE 802.21
Information Server
Tutorial
STA
(11u-capable)
AP
(11u-capable)
VLAN #5
Note: There does NOT need to be a 1-to-1 mapping between this and SSID #5.
DHCP
SSID
#5
Slide 35 Matthew Gast, Dave Stephenson

March 2007 Emergency Services for IEEE 802
802.11u STA
802.11u AP
802.21 IS
(MIH-aware)
Pre-config
Beacon (GAS: MIH)
Advertising protocol =
IS (APID)
Length limitation req from 11u to 21
Out of scope
Probe REQ
802.11
802.21
Probe RSP (GAS: MIH)
GAS init req (MIH IE: e911 req)
MIH frame (e911 req)
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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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
Tutorial Slide 37 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
IEEE 802.22
Tutorial Slide 38 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
Vehicular Communications
Tutorial Slide 40 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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 Emergency Services for IEEE 802
•
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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
Standard Development Organizations
Tutorial Slide 44 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
ES in IEEE 802 technologies do not provide the whole solution.
•
What do we expect from other SDOs
– signaling protocol SIP (new variant – USIP)
• Note: SIP requires an IP address of an SIP agent. This can not be used by 802.11 in state 1, unless a SIP agent discovery protocol exists?)
– codec (e.g. G711)
– network connection (authentication at layer 2)
– application authentication (e.g. https)
– internationalization of emergency dialing codes
Tutorial Slide 45 S. McCann, D. Stephenson and V. Gupta

March 2007
•
3GPP & 3GPP2
• TIA TR-45
• IETF ECRIT
•
NENA
• OMA
•
ITU-T
• ETSI EMTEL
• OCG
•
EU Commission
• ComCare
•
ESIF NGES
• ANSI HSSP
•
US DoT
Tutorial
Emergency Services for IEEE 802
Slide 46 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
– Service requirements from 3GPP TS 22.101
http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/Service_requirements-
ESW06.ppt
– Architecture = IMS (centralised) http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/3GPP IP Based
Emergency Calls.pdf
– Protocol Details from 3GPP TS 24.229
http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/ 3GPP-
Protocol_details.ppt
Tutorial Slide 47 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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 TR-
45.pdf
Tutorial Slide 48 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
– 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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
– Sets standards (among many other things) for emergency calls in
U.S./Canada
– Next Generation 9-1-1 project (NG911)
• Complete overhaul of the entire 9-1-1 system
• Based on IP
• Includes changes to processes, funding, training, etc, etc
• The initial version of the technical standards part is known as “i3”
– Architecture and solutions based on IETF protocols http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/NENA
NG911 arch for SDO workshop.ppt
Tutorial
– NENA sent an liaison to IEEE 802, regarding location issues.
IEEE 802.11u are currently addressing this liaison.
Slide 50 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• 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.
– http://www.ietf-ecrit.org/EmergencyWorkshop2006/slides/2006
OGC GML Info for October SDO Coordination Meeting.ppt
Tutorial Slide 52 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
•
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/EU-
Commission.ppt
• COMCARE
– US Organization Overview and pointers to OASIS standards for authority-to-authority communication.
http://www.ietf-ecrit.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 Emergency Services for IEEE 802
• 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 NENA’s 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
Tutorial Slide 54 S. McCann, D. Stephenson and V. Gupta

March 2007
• US DoT
– Report about NG911 projects
Emergency Services for IEEE 802 http://www.ietfecrit.org/EmergencyWorkshop2006/slides/ USDOT.ppt
•
Emergency Services Project in Austria
– Emergency service project based on IETF protocols http://www.ietfecrit.org/EmergencyWorkshop2006/slides/
AT_PROTOTYP_FIELDTEST.ppt
Tutorial Slide 55 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
nd
• 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 S. McCann, D. Stephenson and V. Gupta

March 2007 Emergency Services for IEEE 802
• Don’t 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?
• 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
Tutorial Slide 57 S. McCann, D. Stephenson and V. Gupta