IEEE 802 Emergency Services (ES) Call for Interest (CFI)

1. IEEE 802 Emergency Services (ES) Call for Interest (CFI) Date: 2007-11-13 Stephen McCann stephen.mccann@roke.co.uk Stephen McCann, NSN

2. Abstract The purpose of this presentation is to determine interest in the formation of an IEEE 802 Study Group about Emergency Service (ES) provision Stephen McCann, NSN

3. IEEE 802 ES Background • Maturing IEEE 802 technologies carry VoIP traffic and it’s only a matter of time before regulations insist they support emergency services. (FCC & EU commission proposals) • IEEE 802 technologies by themselves cannot ensure that all factors are compatible for Emergency Service sessions to actually take place. • Therefore, it’s essential to distinguish between the minimum level of support provided by IEEE 802 emergency services, and support of emergency services at higher layers. • By “IEEE 802 Emergency Services” we refer to the direct support in IEEE 802 of such services, independently of what solutions are adopted at higher protocol layers. • Under all circumstances, changes to IEEE 802 should be kept to the minimum necessary. Stephen McCann, NSN

4. Do What? • To initiate a Study Group • WGSG: Technology specific, 802.1, 802.21? • ECSG: Harmonized approach to ES in all 802 groups • This study will take into account regulatory issues and the architecture requirements of NENA i2 & i3, IETF ECRIT and 3GPP/3GPP2 architecture requirements on radio access technologies. • Attempt to pre-empt upcoming regulatory issues • Determine what aspects of ES would benefit from a harmonized approach across all IEEE 802. • Prepare a PAR for ES provision enhancements, if study shows there is a need. Stephen McCann, NSN

5. Relevant Requirements • Ability to support ES calls • (various media types) • Support for callback • Unauthenticated calls (no credentials in terminal) • Roaming and non roaming • Emergency Alert System (EAS) service • Authority – authority communications • Citizen – citizen communications • Location (Automatic Location Identifier) • Common Approach • Note: This is not a location provisioning study group Stephen McCann, NSN

6. ES Interest • Initial interest in ES within 802.11 • Other interest from 802.1 • LLDP-MED is a adopted wired solution with location support. • Subsequent interest from 802.21 (802 handover) • Provision of ES Information Server • Some interest from 802.15 (15.4) and 802.16 • ZigBee and 802.16d (fixed) community • Additional Information • IEEE 802 Tutorials at March and July 2007 plenary meetings. Attendance ~150 • Liaisons between IEEE 802.11u, NENA and IETF ECRIT • e.g. <draft-tschofenig-ecrit-unauthenticated-access-00.txt> Stephen McCann, NSN

7. ES Study Group • Future work • Study group will consider • existing work in this area • industry input • network and service provider input • what do regulators require • Defined Goals and Timeframe • To determine what work, if any, is necessary to enable an 802 harmonized approach to emergency service provision • Timeframe • 2 plenary cycles, to investigate PAR definition Stephen McCann, NSN

8. Background/Relevant AspectsIEEE 802.1 • LLDP-MED currently supports automatic physical location discovery suitable for wired 802 networks • 802.1AB-Rev work in process could allow location discovery to be leveraged across all 802 technologies Stephen McCann, NSN

9. IEEE 802.11p • Supports Intelligent Transportation Systems (ITS) applications. This includes data exchange between high-speed vehicles and between the vehicles and the roadside infrastructure in the licensed ITS band of 5.9 GHz. • ES from vehicles to authority (eCALL blackbox) • Authority – authority vehicle comms Stephen McCann, NSN

10. IEEE 802.11u • New QoS features • expedited bandwidth request • QoS mapping • Generic Advertising Service (GAS) • Emergency services recommendations (informative) • Use case #1: open network • Use case #2: public credentials Stephen McCann, NSN

11. IEEE 802.11v • Reliable Location Determination • Capability information includes • Format (Civic, Geo – shapes not points, Location by Reference…etc) • Encoding and Resolution • Capable of providing • self-location • remote-location Stephen McCann, NSN

12. IEEE 802.21 • Information Server • logical place to support a comprehensive list of all ES support options. • Mobility support • assisting handovers during an ES session • Location • Service providers need flexibility on how location services are offered in their network • Provides help in determining or provide the location to the clients at various layers • Link layer specific ones (Layer 2) • Link layer agnostic ones (Layer 3+) Stephen McCann, NSN

13. Other Requirements? • 802.16/20/22 • Location Determination • NG911 • Support for non-voice ES connections (e.g. text messaging, email, video) Stephen McCann, NSN

14. Summary • Study group • ECSG/WGSG • Scope • Provision of Emergency Service Capability throughout 802 • Purpose • To determine what work, if any, is necessary to enable an 802 harmonized approach to emergency service provision • Timeframe • 2 plenary cycles, to investigate PAR definition Stephen McCann, NSN

15. Call for Interest Polls (115 in room) • Support formation of a study group • Yes/No/Abstain 41/4/26 • Formation of an EC study group • Yes/No/Abstain 23/13/28 • Formation of an WG study group • 802.1 Yes/No/Abstain 11/15.25 • 802.21 Yes/No/Abstain 17/16/27 • Other, than .1,.21 Yes/No/Abstain 17/14/30 • How many people intend to participate? • 24 • How many companies intend to participate? • 16 Stephen McCann, NSN