80 likes | 229 Vues
Service requirements from 3GPP TS 22.101. SDO Emergency Services Coordination Workshop (ESW06) Columbia University, New York October 5-6, 2006. Atle Monrad, Ericsson Mobile Platform (atle.monrad@ericsson.com). Topics. 3GPP specifications General requirements
E N D
Service requirements from 3GPP TS 22.101 SDO Emergency Services Coordination Workshop (ESW06) Columbia University, New York October 5-6, 2006 Atle Monrad, Ericsson Mobile Platform (atle.monrad@ericsson.com)
Topics • 3GPP specifications • General requirements • Identification of emergency calls • Interaction with cellular protocols • Location of emergency calls
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 and alignments 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
General requirements • Protocol support for emergency services is needed • The speech service is 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 with as well as 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
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 detect emergency calls, but no specific requirements have been made on how this should happen
Interaction with the cellular protocol • 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 • The handling of dialled numbers versus dial-string may need further clarifications.
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