1. IMS Emergency Call Requirements & Emergency Call number support
Month Year
doc.: IEEE yy/xxxxr0
January 2007
IMS Emergency Call Requirements & Emergency Call number support
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
Donghee Shim
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
January 2007
Abstract
This presentation provides an analysis on the IMS emergency call requirements relevant to
Some pending issues are identified based on analysis.
At the end of the presentation, there will be a motion to include proposed normative text in the 11u draft.
Donghee Shim
John Doe, Some Company

3. 3GPP TS 23.167 - IMS Emergency Call
January 2007
3GPP TS IMS Emergency Call
TS – IP Multimedia Subsystem (IMS) emergency sessions
Defines the stage-2 service description for emergency services in IMS, including the elements necessary to support IP Multimedia emergency services
This document covers also the Access Network aspects that are crucial for the provisioning of IMS emergency services including fixed broadband access aspects, GPRS and 3GPP/WLAN Interworking.
Donghee Shim

4. IMS Emergency Architectural Principles
January 2007
IMS Emergency Architectural Principles
Emergency services are independent from the IP-CAN with respect to the detection and routing of emergency sessions. The emergency services shall be possible over at least a cellular access network, a fixed broadband access, I-WLAN access and a nomadic access.
Any kind of emergency numbers, and emergency SIP and TEL URIs as specified in TS 22.101, and special indications for emergency sessions within the SIP signalling shall be supported.
Emergency sessions should be prioritized over non-emergency sessions by the system.
The primary solution shall be that the UE can detect an emergency session (e.g. by evaluating the SIP-URI or the dialled number) by itself and indicates the emergency session to the network. The cases where the UE can't detect an emergency session shall also be supported.
The solution shall work in case the UE has sufficient credentials to authenticate with the IMS and is registered to the IMS or is not registered with the IMS. The case where the UE does not have sufficient credentials to authenticate with the IMS shall also be supported where regulations allow.
Donghee Shim

5. January 2007
Discussion
The primary solution shall be that the UE can detect an emergency session (e.g. by evaluating the SIP-URI or the dialled number) by itself and indicates the emergency session to the network
The terminal should be able to use the well-known emergency numbers (e.g. 911) as well as the emergency numbers that are valid based on current user’s location in the Visited SSPN
However, the terminal cannot store all possible emergency number in every available SSPN since this requires us to know all possible emergency numbers and emergency numbers in one country may be a non-emergency numbers in another country
Donghee Shim

6. January 2007
Discussion
The terminal can be configured with one or more ‘DEFAULT’ emergency numbers (e.g. 911)
In case of overlap between the ‘DEFAULT’ emergency numbers and the local emergency numbers take precedence.
In addition, if the terminal uses the emergency numbers of Home SSPN instead of the local emergency numbers, then local ones take precedence.
Once the terminal has local emergency call numbers, the terminal is able to determine if the call made by the user is an emergency call or not.
Then, when a user makes an emergency call, the terminal can recognize the call as an emergency call.
Then universal emergency indication, e.g. SERVICES:SOS, can be added in the SIP INVITE message to indicate the emegency call to the call manager
Donghee Shim

7. January 2007
Proposal
Local emergency call numbers shall be downloaded in the Beacon, Probe Response and Association Response frame
Put local emergency call numbers in Beacon
Put local emergency call numbers in Probe Response
Put local emergency call numbers in Association Response
Donghee Shim

8. Example Message Sequence Chart
January 2007
Example Message Sequence Chart
Donghee Shim

9. January 2007
Motion
Move to have authors draft normative text for potential inclusion into TGu draft
Mover:
Seconder:
Donghee Shim