IEEE 802 wide project on Emergency Services October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802 wide project on Emergency Services Date: 2007-10-31 Stephen McCann stephen.mccann@roke.co.uk Stephen McCann, NSN Stephen McCann, NSN

These are personal views of the Author October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 Abstract This submission has been produced for the 3rd SDO Emergency Services Workshop, Brussels, Belgium, 30th October – 1st November 2007. These are personal views of the Author Stephen McCann, NSN Stephen McCann, NSN

October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 Background Maturing IEEE 802 technologies carry VoIP traffic and its only a matter of time before service and network providers require that emergency services are supported. Access networks like IEEE 802 by themselves cannot ensure that all factors are compatible for Emergency Service sessions to actually take place. Therefore, it is essential to distinguish between the minimum level of support provided by IEEE 802 emergency services, and support of emergency services at higher layers. Under all circumstances, changes to IEEE 802 should be kept to the minimum necessary. Stephen McCann, NSN Stephen McCann, NSN

IEEE 802 wide ES project Do what? October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802 wide ES project Do what? Analysis of which requirements could affect the ability of RLANs to comply with IETF ECRIT and 3GPP/3GPP2 architecture requirements on radio access technologies. If necessary: initiate a cross IEEE 802 ES project to coordinate a harmonized approach to ES in all IEEE 802 technologies (802.1, .11, .15, .16, .20, .21, .22). Stephen McCann, NSN Stephen McCann, NSN

Relevant Requirements October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 Relevant Requirements Location (Automatic Location Identifier) Initial with MS ES request Most regulatory domains require, some are opt in only Support for callback Unauthenticated calls Multi level priority for calls Stephen McCann, NSN Stephen McCann, NSN

IEEE 802 wide interest Initial interest in ES within IEEE 802.11 October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802 wide interest Initial interest in ES within IEEE 802.11 Other interest from 802.1 (e.g. Manfred’s presentation) LLDP-MED Subsequent interest from 802.21 (802 handover) Provision of ES information server Some interest from 802.15 (15.4) and 802.16 ZigBee and Fixed 802.16 community Stephen McCann, NSN Stephen McCann, NSN

IEEE 802 wide ES project Current Status October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802 wide ES project Current Status IEEE 802 Tutorials at March and July 2007 plenary meetings. Attendance ~150 IEEE 802.11u liaisons with NENA and IETF ECRIT Stephen McCann, NSN Stephen McCann, NSN

IEEE 802.1 See Manfred’s presentation October 2007 October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802.1 See Manfred’s presentation Stephen McCann, NSN Stephen McCann, NSN

October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 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. Stephen McCann, NSN Stephen McCann, NSN

October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802.11u External network (“SSPN”) interface for extended authorization New QoS features Generic Advertising Service (GAS) Emergency services recommendations (informative) Use case #1: open network Use case #2: public credentials Stephen McCann, NSN Stephen McCann, NSN

October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802.11v Requirement to provide unique capability exchange per terminal Not all terminals will require the same information format…etc AP must respond to location requests if AP advertises capability Terminals advertise their location capabilities in Beacons, Probe Responses, etc. Capability information includes Format (CIVIC, Geo, Location by Reference…etc) Encoding (Binary, XML…etc) Resolution Capable of providing self-location remote-location Stephen McCann, NSN Stephen McCann, NSN

IEEE 802.21 October 2007 AAA Carrier Network IEEE 802.21 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802.21 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) SSID #5 STA (11u-capable) Stephen McCann, NSN Stephen McCann, NSN

IEEE 802.21 Information Server (IS) October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 IEEE 802.21 Information Server (IS) 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 Stephen McCann, NSN Stephen McCann, NSN

Other Requirements? eCALL NG911 October 2007 doc.: IEEE 802.11-07/2694r0 October 2007 Other Requirements? eCALL Automated emergency calls (e.g. EU proposal for car black boxes) NG911 Support for non-voice ES connections Stephen McCann, NSN Stephen McCann, NSN