ETSI TS 123 167 V7.11.0 (2009-01) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) emergency sessions (3GPP TS 23.167 version 7.11.0 Release 7) 3GPP TS 23.167 version 7.11.0 Release 7 1 ETSI TS 123 167 V7.11.0 (2009-01) Reference RTS/TSGS-0223167v7b0 Keywords UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI 3GPP TS 23.167 version 7.11.0 Release 7 2 ETSI TS 123 167 V7.11.0 (2009-01) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp. ETSI 3GPP TS 23.167 version 7.11.0 Release 7 3 ETSI TS 123 167 V7.11.0 (2009-01) Contents Intellectual Property Rights................................................................................................................................2 Foreword.............................................................................................................................................................2 Foreword.............................................................................................................................................................5 1 Scope........................................................................................................................................................6 2 References................................................................................................................................................6 3 Definitions, symbols and abbreviations...................................................................................................7 3.1 Definitions..........................................................................................................................................................7 3.2 Abbreviations.....................................................................................................................................................8 4 High level Principles................................................................................................................................8 4.1 Architectural Principles......................................................................................................................................8 4.2 Naming and Addressing...................................................................................................................................10 4.3 Location information for Emergency Sessions.................................................................................................10 4.3.1 General Location Information Principles....................................................................................................10 4.3.2 Void............................................................................................................................................................11 4.4 IP-CAN............................................................................................................................................................11 5 Architecture model and reference points................................................................................................11 5.1 Reference architecture......................................................................................................................................11 5.2 Reference points...............................................................................................................................................12 6 Functional description............................................................................................................................12 6.1 UE....................................................................................................................................................................12 6.2 IMS Functional entities....................................................................................................................................13 6.2.1 Proxy-CSCF................................................................................................................................................13 6.2.2 Emergency-CSCF.......................................................................................................................................14 6.2.3 Location Retrieval Function.......................................................................................................................14 6.2.4 Serving CSCF.............................................................................................................................................15 7 Procedures related to establishment of IMS emergency session............................................................15 7.1 High Level Procedures for IMS Emergency Services......................................................................................15 7.1.1 UE Detectable Emergency Session.............................................................................................................15 7.1.2 Non UE detectable Emergency Session......................................................................................................16 7.1.3 Emergency Session Establishment using LRF/RDF...................................................................................17 7.2 IMS Registration for Emergency Session........................................................................................................17 7.3 Emergency Session Establishment in the Serving IMS network......................................................................18 7.4 IMS Emergency Session Establishment without Registration.........................................................................19 7.5 Interworking with PSAP..................................................................................................................................20 7.5.1 PSAP/Emergency centre located at the GSTN...........................................................................................20 7.5.2 PSAP/Emergency centre connected via IP using SIP.................................................................................20 7.5.3 PSAP/Emergency centre connected via ECS..............................................................................................20 7.6 Retrieving Location information for Emergency Session................................................................................20 7.6.1 Acquiring location information from the UE or the network......................................................................20 7.6.2 Void............................................................................................................................................................22 7.6.3 Void............................................................................................................................................................22 Annex A (informative): Void.................................................................................................................23 Annex B (informative): IMS emergency sessions over 3GPP/WLAN Interworking (I-WLAN)....24 B.1 Void........................................................................................................................................................24 B.2 Void........................................................................................................................................................24 B.3 Location handling for I-WLAN.............................................................................................................24 Annex C (normative): IMS emergency services using Fixed Broadband Access...........................25 ETSI 3GPP TS 23.167 version 7.11.0 Release 7 4 ETSI TS 123 167 V7.11.0 (2009-01) C.1 Location Retrieval for emergency services over fixed broadband access........................................................25 C.1.1 High Level Principles for Emergency location information for fixed broadband access...........................25 C.1.2 Retrieval of location information for emergency services over fixed broadband access............................25 Annex D (informative): Examples of call flows according to NENA I2 recommendations.............27 D.1 ECS redirecting IMS emergency call.....................................................................................................27 D.2 ECS routes the emergency call to the gateway with record route..........................................................29 Annex E (Informative): Emergency support in different IP-CANs...................................................31 Annex F (Informative): TEL-URI provisioning considerations for IMS emergency call back.......32 Annex G (informative): Change history...............................................................................................33 History..............................................................................................................................................................35 ETSI 3GPP TS 23.167 version 7.11.0 Release 7 5 ETSI TS 123 167 V7.11.0 (2009-01) Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI 3GPP TS 23.167 version 7.11.0 Release 7 6 ETSI TS 123 167 V7.11.0 (2009-01) 1 Scope This document defines the stage 2 service description for emergency services in the IP Multimedia Core Network Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services. ITU-T Recommendation I.130 [4] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [3] defines stage 2 of the method. This document covers also the Access Network aspects that are crucial for the provisioning of IMS emergency services. Other 3GPP specifications that are related to the IMS emergency services are TS 23.228 [1] on IMS in general, including fixed broadband access aspects, and TS 23.234 [7] describing 3GPP/WLAN Interworking and TS 23.271 [5] that covers location services. TS 25.301 [6] contains an overall description of the UMTS Terrestrial Radio Access Network. GPRS functions for support of IMS emergency services are not defined in this version of the specification. The emergency support in different IP-CANs is described in the Informative Annex E. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPP TS 23.228: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS); Stage 2". [2] 3GPP TS 23.060: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; General Packet Radio Service (GPRS); Service description; Stage 2". [3] CCITT Recommendation Q.65: "Methodology – Stage 2 of the method for the characterisation of services supported by an ISDN". [4] ITU Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN". [5] 3GPP TS 23.271: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Functional stage 2 description of LCS". [6] 3GPP TS 25.301: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture". [7] 3GPP TS 23.234: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; 3GPP system to Wireless Local Area Network (WLAN) interworking; System description". [8] 3GPP TS 22.101: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Service aspects; Service principles". [9] IETF RFC 3825: "Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information". [10] IETF Internet-Draft: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information ", draft-ietf-geopriv-dhcp-civil-06 (May 30, 2005). ETSI 3GPP TS 23.167 version 7.11.0 Release 7 7 ETSI TS 123 167 V7.11.0 (2009-01) [11] 3GPP TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications". [12] 3GPP TS 23.002: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Network architecture". [13] 3GPP TS 24.008: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". [14] IETF RFC 4119: "A Presence-based GEOPRIV Location Object Format". [15] OMA AD SUPL: "Secure User Plane Location Architecture", http://www.openmobilealliance.org. [16] OMA TS ULP: "User Plane Location Protocol", http://www.openmobilealliance.org. [17] NENA I2 architecture: "Interim VoIP Architecture for Enhanced 9-1-1 Services (i2)". [18] ETSI ES 282 004: "Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [19] 3GPP TS 24.229: "IP multimedia call control protocol based on SIP and SDP; stage 3". [20] 3GPP TS 23.203: "Policy and Charging Control architecture". [21] 3GPP TS 23.003: "Numbering, addressing and identification". [22] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)". 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [11] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [11]. Connectivity Session Location and Repository Function (CLF): As per ETSI ES 282 004 [18], the Connectivity Session Location and Repository Function (CLF) registers the association between the IP address allocated to the UE and related network location information, i.e.: access transport equipment characteristics, line identifier (Logical Access ID), IP Edge identity. Emergency Call Server (ECS): The functional entity consists of a Location Retrieval Function (LRF) and either a routing proxy or a redirect server, e.g. an ECS contains a VPC and a Routing Proxy or Redirect Server in NENA I2 architecture [17]. Emergency-CSCF: The Emergency-CSCF handles certain aspects of emergency sessions, e.g. routing of emergency requests to the correct emergency centre or PSAP. Emergency Service Query Key (ESQK): A 10-digit North American Numbering Plan number used to identify a particular emergency call instance. It is used by the LRF as a key to look up for the location information and callback information associated with the emergency call instance and is also used by the PSAP to query location information from the LRF. Emergency Service Routing Key (ESRK): see TS 23.271 [5]. Emergency Service Routing Number (ESRN): North American Numbering Plan number used for routing of an emergency call to the appropriate gateway for an eventual delivery towards a CS-based PSAP. Geographical Location Information: Location indicated in geographical terms, for example geographical coordinates or street address (e.g. as supported by IETF RFC 4119 [14]). ETSI 3GPP TS 23.167 version 7.11.0 Release 7 8 ETSI TS 123 167 V7.11.0 (2009-01) IP-Connectivity Access Network (IP-CAN): The collection of network entities and interfaces that provides the underlying IP transport connectivity between the UE and the IMS entities. An example of an "IP-Connectivity Access Network" is I-WLAN. Location Identifier: Information about the current location of the UE in the network. Location is indicated in network terms, for example using the global cell id in cellular networks, line-id in fixed broadband networks, (OMA-Location also uses this term, but OMA so far defines the Location Identifier only for cellular access.) Location Information: The location information may consist of the Location Identifier, and/or the Geographical location information. Location Retrieval Function (LRF): This functional entity handles the retrieval of location information for the UE including, where required, interim location information, initial location information and updated location information. The LRF may interact with a separate RDF or contain an integrated RDF in order to obtain routing information. The LRF may interact with a separate GMLC or contain an integrated GMLC in order to obtain location information. The LRF may interact with or contain other types of location server functions in order to obtain location information. Last Routing Option (LRO): A number, which may be used in the event of network failure towards a specific location based PSAP or a number that can be associated to a national or default PSAP/Emergency centre. Public Safety Answering Point (PSAP): A physical location, where emergency calls from the public are received. Routing Determination Function (RDF): The functional entity, which may be integrated in a Location Server (e.g. GMLC) or in an LRF, provides the proper PSAP destination address to the E-CSCF for routing the emergency request. It can interact with a location functional entity (e.g. GMLC) to manage ESQK allocation and management, and deliver location information to the PSAP. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CLF Connectivity session Location and repository Function E-CSCF Emergency-CSCF ECS Emergency Call Server ESQK Emergency Service Query Key ESRK Emergency Service Routing Key ESRN Emergency Service Routing Number LRF Location Retrieval Function LRO Last Routing Option PSAP Public Safety Answering Point RDF Routing Determination Function 4 High level Principles 4.1 Architectural Principles The solution for emergency sessions in the IMS fulfils the emergency principles and requirements of TS 22.101 [8] and the following architectural requirements: 1. Void. 2. 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. 3. Any kind of emergency numbers, and emergency SIP and TEL-URIs as specified in TS 22.101 [8], and special indications for emergency sessions within the SIP signalling shall be supported. 4. Emergency sessions should be prioritized over non-emergency sessions by the system. ETSI 3GPP TS 23.167 version 7.11.0 Release 7 9 ETSI TS 123 167 V7.11.0 (2009-01) 5. The establishment of IMS emergency sessions shall be possible for users with a barred public user identity. 6. 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. 7. 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. In the case that UE is not already IMS registered, it shall perform a registration for the support of emergency services (emergency registration). In the case a UE is already IMS registered, the UE may skip the additional emergency registration if the UE is aware that it is in its home network (e.g. including IP-CANs where roaming outside the home network is not supported). If the UE does not have sufficient credentials to authenticate with the IMS it shall be possible to perform session establishment without an existing security association between UE and P-CSCF, and the UE shall include an equipment identifier (the specific details of the equipment identifier to use may depend upon the IP-CAN) in the request to establish an emergency session. 8. It shall be possible to reject emergency service requests from an UE, without sufficient credentials to authenticate with the IMS in networks where emergency services from UEs with sufficient credentials to authenticate with the IMS are required. 9. Emergency Service is not a subscription service and therefore will mainly be supported in the roamed-to network. In the case that a UE has sufficient credentials, it shall initiate an emergency registration with the network (requiring the involvement of the home network). The CSCFs providing service for emergency sessions may be different from the CSCFs involved in the other IMS services. In the case that the registration fails, the UE may attempt an anonymous emergency call. 10. If an emergency session establishment request is routed to a P-CSCF located in the home network, the home network should be able to detect that the session is for emergency service (whether indicated as such or not) and respond to the UE indicating that the UE should initiate an emergency session in the visited network (e.g. via the CS domain of the visited network). 11. Emergency centres and PSAPs may be connected to the PSTN, CS domain, PS domain or any other packet network. 12. Emergency centres and PSAPs shall be able to call back the user for an emergency session from a UE that has registered (i.e. containing valid credentials). 13. The IMS core network shall be able to transport information on the location of the subscriber. 14. Void. 15. The network shall be able to retrieve the caller's location; 16. As a regional option, the network shall be capable of assigning a routable location key (i.e. Emergency Services Query Key, a.k.a. ESQK, which has the same properties as the existing ESRK in wireless 911 services) to an IMS emergency session, and releasing the ESQK when the emergency session is terminated. 17. The network shall provide the caller's location information to the PSAP upon query from the PSAP. 18. The network shall provide the possibility to route to a default answering point given the scenario where the local PSAP can not be determined. 19. The network may provide a capability to enable a UE to obtain local emergency numbers. 20 A UE should support a capability to obtain local emergency numbers from the network once such a capability has been defined and agreed. 21. It shall be possible to prevent the sending of the information of the users, such as public user identifiers and the location information to the PSAP when explicitly requested by the user, i.e. request on session by session basis. ETSI