1. ES Access Date: 2008-05-09 Authors: May, 2008 November 2005
doc.: IEEE /0499r1
May, 2008
ES Access
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
Gabor Bajko

2. November 2005
doc.: IEEE /0499r1
May, 2008
Role of an AP in ES
The role of an AP in an unauthenticated ES call is limited to providing the required access
Open access
Access requiring public credentials
If public credentials are needed, those are downloaded (shouldn’t matter where from), and the AP only performs its usual tasks. Authentication is done by the AS, port is opened as in any other case
Gabor Bajko

3. November 2005
doc.: IEEE /0499r1
May, 2008
Proposal -1-
Do not store public credentials in the AP, but in a server in the backend (eg, IS)
Use so-called GAS to download the public credentials for ES access, similarly to any generic IE ( using MIH IS protocol ID)
Remove from Table 43x the “Emergency Public Network Access” Native Query protocol Info ID
Define 2 bits in Network Types:
ESO
ES with public credentials
Gabor Bajko

4. ESO and ES with Public credentials
November 2005
doc.: IEEE /0499r1
May, 2008
ESO and ES with Public credentials
Make recommendations for the AP to support ESO for ES support in case the AP does not have access to an IS
Make recommendations for the AP to support ES with Public Credentials when there is access to an IS from the AP
Gabor Bajko

5. Emergency Call Number Information
November 2005
doc.: IEEE /0499r1
May, 2008
Emergency Call Number Information
Is this similar to the Local Emergency Dialstring?
A client having access to a LoST database may download the Local Emergency Dialstring from there, using the LoST protocol
Using GAS for this requires to have an Advertisement ID for LoST
The information may also be stored in an IS
The string is not AP specific, shouldn’t be stored there
Gabor Bajko

6. November 2005
doc.: IEEE /0499r1
May, 2008
Proposal -2-
Do not store local emergency dialstrings in the AP, but in a server in the backend (eg, IS)
Use so-called GAS to download the local emergency dialstrings, similarly to any generic IE from
Alternatively define a new Advertisement ID for LoST and let the STA query a LoST server (which is a PSAP populated database)
Remove from Table 43x the “Emergency Call Number Information” Native Query protocol Info ID
Gabor Bajko

7. November 2005
doc.: IEEE /0499r1
May, 2008
Proposal 3
The MIH term (Media Independent Handover) in the MIH IS Advertisement ID might need to be renamed.
MIH is handover specific term
Emergency Service support is anything but not handover
Gabor Bajko