1. Emergency Services signalling for WLAN
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Emergency Services signalling for WLAN
Date:
Authors:
Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Michael Montemurro, Chantry Networks
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Overview
This is not a complete solution for Emergency Services; it just provide a mechanism to signal an emergency call using a QoS mechanism.
This presentation does not cover location.
Michael Montemurro, Chantry Networks
John Doe, Some Company

3. Emergency Services Signalling Description
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Emergency Services Signalling Description
IEEE e provides the ADDTS action frame for admission control and power-save mechanisms.
A client can use the ADDTS action frame to indicate parameters and request bandwidth for a traffic stream.
The traffic stream parameters are included in the TSPEC element.
Reserved bits in the TSINFO field of the TSPEC element could be used to indicate that the traffic stream is for an emergency service.
This mechanism preserves the existing protocol message content with a minor change to the TSPEC element.
Michael Montemurro, Chantry Networks
John Doe, Some Company

4. Use of ADDTS for Emergency Services
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Use of ADDTS for Emergency Services
The ADDTS frame seems to be the most reasonable frame to piggyback emergency signalling.
ADDTS could be used at any time (no state changes associated with the message)
ADDTS frames are passed to the SME where the signalling could be handled.
TSPEC signalling
Involves minimal changes with little impact on existing standards.
TSPEC are already used for CAC, this approach is consistent with normal QoS handling.
TSPEC’s are generally built above the WLAN driver – minimal driver changes required
Michael Montemurro, Chantry Networks
John Doe, Some Company

5. Emergency Services for WLAN TSPEC element description
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Emergency Services for WLAN TSPEC element description
Modified TS Info field in the TSPEC element, based on IEEE e is shown below. Bit 17 of the TS Info element will indicate that the TSPEC refers to an emergency request. 23 18 17 16 15 14 10 9
8 7 6 5 4 1
Reserved
Emergency
Service
ACK
Policy
User
Priority
APSD
Aggregation
Access
Direction
TSID
Traffic
Type
Michael Montemurro, Chantry Networks
John Doe, Some Company

6. Emergency Services for WLAN Message Flow during Call Initiation
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Emergency Services for WLAN Message Flow during Call Initiation
Michael Montemurro, Chantry Networks
John Doe, Some Company

7. Emergency Services for WLAN Information Element
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Emergency Services for WLAN Information Element
Could add an additional information element to the ADDTS to indicate that there is an emergency call pending.
The information element could potentially provide additional information to the infrastructure.
Michael Montemurro, Chantry Networks
John Doe, Some Company

8. Emergency Services for WLAN Location
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Emergency Services for WLAN Location
The Call Server/PBX needs the location of the terminal to:
Route the call to the correct Public Safety Answering Point (PSAP)
Indicate the location of the caller to Emergency Services personnel.
Two mechanism to provide location:
Infrastructure determines the location.
Terminal reports its location.
If the infrastructure is used, the location of the terminal has to be known proactively (track terminal movement)
If the terminal knows its location, it can report the information through the application layer to the Call Server/PBX.
IETF provides mechanisms to do this.
Michael Montemurro, Chantry Networks
John Doe, Some Company

9. Issues How to address cases where Admission Control is not enabled?
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
Issues
How to address cases where Admission Control is not enabled?
How does the ADDTS signalling interleave with the “call control” messaging?
Michael Montemurro, Chantry Networks
John Doe, Some Company

10. doc.: IEEE 802.11-yy/xxxxr0 Questions? Comments?
Month Year
doc.: IEEE yy/xxxxr0
Month YearJanuary 2006
The End!
Questions?
Comments?
Michael Montemurro, Chantry Networks
John Doe, Some Company