Upload
jeffry-brown
View
216
Download
0
Embed Size (px)
Citation preview
1 © 2006 Nokia IMS emergency reqs.ppt / 4-Jul-2006 / Hannu Hietalahti
Company Confidential
IMS emergency call requirements
Presentation for 3GPP – IETF joint workshop on SIP emergency calls
4th of July 2006 / Hannu Hietalahti
2 © 2006 Nokia IMS emergency reqs.ppt /4-Jul-2006 / Hannu Hietalahti3GPP – IETF emergency call workshop
Topics• 3GPP specifications
• General requirements
• Identification of emergency calls
• Interaction with cellular protocols
• Location of emergency calls
3 © 2006 Nokia IMS emergency reqs.ppt /4-Jul-2006 / Hannu Hietalahti3GPP – IETF emergency call workshop
3GPP specifications
• IMS emergency is a Rel-7 work item• Foreseen freezing early 2007
• Service requirements are specified in 3GPP TS 22.101• This presentation is an overview of IMS emergency call requirements in
22.101
• The service requirements TS is already frozen (i.e. the functionality is there)
• ...but corrections are still possible
• Architecture is specified in 3GPP TS 23.167• The TS is under version control, but new features are still possible
• Protocol details are in 3GPP TS 24.229• Work in progress
4 © 2006 Nokia IMS emergency reqs.ppt /4-Jul-2006 / Hannu Hietalahti3GPP – IETF emergency call workshop
General requirements
• Protocol support for emergency services is needed• At least speech services are required, multimedia is FFS (in later releases)
• Routing to the appropriate service point according to national regulations
• Emergency call without dialing a number must be possible• triggering e.g. by red “emergency” button or car airbag sensor
• Terminal supporting voice services shall also support emergency speech calls
• terminal must support emergency calls without SIM / USIM
• support of emergency calls without SIM / USIM in the network is subject to national regulations
• Push-to-talk is not considered a voice service in this respect
5 © 2006 Nokia IMS emergency reqs.ppt /4-Jul-2006 / Hannu Hietalahti3GPP – IETF emergency call workshop
Identification of emergency calls
• The terminal detects emergency number or “IMS emergency call identifier”
• global default numbers 112, 911 (even in terminal without SIM / USIM)
• global IMS emergency call identifier (even in terminal without SIM / USIM)
• HPLMN can define additional e-numbers (but no IMS identifiers) on SIM / USIM
• Serving network can download local e-numbers (but no IMS identifiers)• Currently only 3GPP cellular protocols (CS + PS domain) support this requirement
• Emergency call without dialing a number must be possible• triggering e.g. by red “emergency” button or car airbag sensor
• Different emergency services need to be identified• Police, ambulance, fire brigade, marine guard, mountain rescue
• Use of the subcategories is subject to national administration
• The network must be able to to detect emergency call, but no specific requirements have been made on how this should happen
6 © 2006 Nokia IMS emergency reqs.ppt /4-Jul-2006 / Hannu Hietalahti3GPP – IETF emergency call workshop
Interaction with the cellular protocols
• CS + PS (IMS) capable mobile should give priority to CS emergency call
• Local numbers downloaded by the serving network and HPLMN configured emergency numbers do apply also to IMS emergency call initiation
• Emergency categories (police, ambulance, etc) do apply also in IMS
• No means to configure local or HPLMN IMS emergency call identifiers is needed
7 © 2006 Nokia IMS emergency reqs.ppt /4-Jul-2006 / Hannu Hietalahti3GPP – IETF emergency call workshop
Location of emergency calls
• Location of emergency calls must be supported, applicability is subject to national regulations
• Locating emergency calls overrides subscribers privacy request
• Based on local regulation, the network controls this privacy override, as long as the PSAP and the emergency service authorities need it