1、 ETSI TR 102 476 V1.1.1 (2008-07)Technical Report Emergency Communications (EMTEL);Emergency calls and VoIP: possible short andlong term solutions and standardization activitiesETSI ETSI TR 102 476 V1.1.1 (2008-07) 2 Reference DTR/EMTEL-00006 Keywords emergency, VoIP ETSI 650 Route des Lucioles F-06
2、921 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.ets
3、i.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
4、 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.
5、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 fore
6、going restriction extend to reproduction in all media. European Telecommunications Standards Institute 2008. 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
7、 registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 476 V1.1.1 (2008-07) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 2.1 Normative references .6 2.2 Informative references7 3 Definitions and abbreviations.8 3.1 Definit
8、ions8 3.2 Abbreviations .8 4 Purpose of the present document8 4.1 The network evolution8 4.1.1 Summary.9 4.2 Broadband subscribers .9 4.2.1 Summary.9 5 General on Access to Emergency Services 9 5.1 Service types 10 5.2 The PSAP interface 11 5.3 Network capabilities.11 6 Emergency Calls and VoIP 11 6
9、.1 Description of VoIP scenarios11 6.1.1 IP-based telephony from fixed terminal12 6.1.2 Internet telephony from fixed terminal .12 6.1.3 IP-based telephony from nomadic terminal 12 6.1.4 Internet telephony from nomadic terminal13 6.1.5 IP-based telephony from mobile terminal.13 6.1.6 Internet teleph
10、ony from mobile terminal 13 6.2 Emergency Calls 14 6.2.1 IP-based telephony from fixed terminal14 6.2.1.1 Routing14 6.2.1.2 Identification .14 6.2.1.3 Location 14 6.2.2 Internet telephony from fixed terminal .15 6.2.3 IP-based telephony from nomadic terminal 15 6.2.3.1 Routing .15 6.2.3.2 Identifica
11、tion .16 6.2.3.3 Location 16 6.2.4 Internet telephony from nomadic terminal17 6.2.5 IP-based telephony from mobile terminal.17 6.2.5.1 Routing17 6.2.5.2 Identification .18 6.2.5.3 Location 18 6.2.6 Internet telephony from mobile terminal 19 7 Standardization activities .19 7.1 IETF/ECRIT.19 7.1.1 Re
12、quirements for Emergency Context Resolution with Internet Technologies19 7.1.2 A Uniform Resource Name (URN) for Emergency and Other Well-Known Services.19 7.1.3 Security Threats and Requirements for Emergency Call Marking and Mapping .20 7.1.4 LoST: A Location-to-Service Translation Protocol20 7.1.
13、5 Location-to-URL Mapping Architecture and Framework 20 7.1.6 Best Current Practice for Communications Services in support of Emergency Calling.20 7.1.7 Framework for Emergency Calling using Internet Multimedia 20 ETSI ETSI TR 102 476 V1.1.1 (2008-07) 4 7.1.8 A Dynamic Host Configuration Protocol (D
14、HCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure 20 7.2 ETSI .21 7.2.1 Requirements of the NGN network to support Emergency Communication from Citizen to Authority (TISPAN)21 7.2.2 NGN Architecture to support emergency communication from citizen to authority21 7.2.3 Eme
15、rgency Location Protocol.21 7.2.4 Requirements in Emergency Communications in NGN .21 7.2.5 Architecture to support of Emergency Communications21 7.2.6 Revision of TS 102 164 on the Endorsement of the OMA MLP v 3.2.021 7.3 3GPP 22 7.3.1 IP Multimedia Subsystems (IMS) emergency sessions 22 7.3.2 Othe
16、r organizations working with Emergency Call Standardization22 Annex A: Bibliography23 History 24 ETSI ETSI TR 102 476 V1.1.1 (2008-07) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these es
17、sential 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 upda
18、tes 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 ETI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the
19、ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Special Committee Emergency Communications(EMTEL). The present document is one of several deliverables covering the communication needs of individual
20、s and authorities in emergency situations, as identified below: TR 102 180: “Basis of requirements for communication of individuals with authorities/organizations in case of distress (Emergency call handling)“; TS 102 181: “Requirements for communication between authorities/organizations during emer
21、gencies“; TS 102 182: “Requirements for communications from authorities/organizations to individuals, groups or the general public during emergencies“; TR 102 410: “Basis of requirements for communications between individuals and between individuals and authorities whilst emergencies are in progress
22、“. ETSI ETSI TR 102 476 V1.1.1 (2008-07) 6 1 Scope The present document gives an overview of standardisation activities and summarises different methods for VoIP providers to deliver emergency communication services. VoIP is growing quickly, especially in countries with a high broadband penetration.
23、 Therefore the use of this technology for the provision of emergency communication services will be considered. For this, specific features can be introduced such as location and routing facilities. The present document is applicable to ETSI technical bodies for the defining of services and specifyi
24、ng technical solutions. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part there
25、of and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location m
26、ight be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should
27、, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clau
28、se were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the l
29、atest edition of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TR 102 476 V1.1.1 (2008-07) 7 2.2 Informative references The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular
30、 subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 ETSI TR 102 180: “Basis of Requirements for communication of Individuals with authorities/organizations in case of distress (emergency call handling)“. i.2 ETSI TS 102 42
31、4 (V1.1.1): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Requirements on the NGN network to support Emergency Communication from Citizen to Authority“. i.3 ETSI TS 123 167: “Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsys
32、tem (IMS) emergency sessions (Release 7)“. i.4 IETF RFC 5012: “Requirements for Emergency Context Resolution with Internet Technologies“. i.5 IETF RFC 5031: “A Uniform Resource Name (URN) for Emergency and Other Well-Known Services“. i.6 IETF RFC 5069: “Security Threats and Requirements for Emergenc
33、y Call Marking and Mapping“. i.7 Draft-ietf-ecrit-mapping-arch-03: “Location-to-URL Mapping Architecture and Framework“ by H. Schulzrinne. NOTE: This reference can is available at http:/www.ietf.org/internet-drafts/draft-ietf-ecrit-mapping-arch-03.txt. i.8 Draft-ietf-ecrit-lost-10: “LoST: A Location
34、-to-Service Translation Protocol“, by T. Hardie, A. Newton, H. Schulzrinne and H. Tschofenig. NOTE: This reference can is available at http:/www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-10.txt. i.9 Draft-ietf-ecrit-phonebcp: “Best Current Practice for Communications Services in support of Emer
35、gency Calling“, by B. Rosen and J. Polk. NOTE: This reference can is available at http:/www.ietf.org/internet-drafts/draft-ietf-ecrit-phonebcp-04.txt. i.10 Draft-ietf-ecrit-framework-05: “Framework for Emergency Calling using Internet Multimedia“, by B. Rosen, H. Schulzrinne, A. Newton and J. Polk.
36、NOTE: This reference can is available at http:/www.ietf.org/internet-drafts/draft-ietf-ecrit-framework-05.txt. i.11 Draft-ietf-ecrit-dhc-lost-discovery: “A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure“, by H. Schulzrinne, H. Tsc
37、hofenig and J. Polk. NOTE: This reference can is available at http:/www.ietf.org/internet-drafts/draft-ietf-ecrit-dhc-lost-discovery-03.txt. i.12 ETSI TS 182 009: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Architecture to support emergency
38、 communication from citizen to authority; Endorsed document 3GPP TS 23.167, Release 7“. i.13 ETSI TS 102 164 (V2.1.1): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Emergency Location Protocols; OMA-TS-MLP-V3_2-20051124-C“. i.14 ETSI EG 202 339:
39、“Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Definition of requirements on the functional architecture for supporting Emergency and Priority user services“. i.15 ITU Recommendation E.164: “List of ITU Recommendation E.164 assigned country codes“
40、. ETSI ETSI TR 102 476 V1.1.1 (2008-07) 8 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: IP network: packet transport network deploying the IP protocol Voice over Internet Protocol (VoIP): is the generic name, whic
41、h defines the transportation of voice traffic by means of transmission in packets using Internet Protocol (IP) NOTE: VoIP traffic can be routed on a controlled private network or the internet, which is a public network, or a combination of the two. Internet telephony and managed IP-based telephony a
42、re sub elements of VoIP. IP-based telephony (or managed IP-based telephony): specific VoIP service, where the voice traffic is carried by data packets fully or partially on managed IP network, in which case the management of network means management of quality, reliability and security of calls inte
43、rnet telephony (or Voice over Internet (VoIT): a specific VoIP service using transmission in packets on the Internet public network which is by definition open and noncontrollable 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Par
44、tnership Project DNS Domain Name System EGEA Expert Group on Emergency Access ETSI European Telecommunications Standards Institute IETF Internet Engineering Task Force NTP Network Termination Point PATS Publicly Available Telephony Services PIDF-LO Presence Information Data Format Location Object PS
45、AP Public Safety Answering Point PSTN Public Switched Telephone Network RPC Remote Procedure Call SIM Subscriber Identification Module for GSM VoIP Voice over Internet Protocol URI Uniform Resource Identifier USIM Subscriber Identification Module for UMTS 4 Purpose of the present document 4.1 The ne
46、twork evolution New communications networks are IP-based. The number of broadband telephones is increasing quickly and more and more calls no longer reach a circuit switched network. Emergency calls traditionally reach the PSAP through the PSTN. Actors offering VoIP services without a PSTN network,
47、e.g. municipality networks, need to transfer emergency calls through a circuit switched network, typically the old PSTN. Since IP allows for transfer of more information related to the call and the caller, it could be beneficial to allow for direct IP-interconnect to PSAPs. It is also foreseeable th
48、at the days of the circuit switched networks are coming to an end. That means that the requirements for IP-interconnections of PSAPs are developed. It can also be argued why new IP-based public communications operators would not have the possibility to connect directly to PSAPs over IP. ETSI ETSI TR
49、 102 476 V1.1.1 (2008-07) 9 Apart from the above mentioned reasons for EMTEL to work on IP-interconnection of PSAPs, it is likely to be an advantage to try and define a PSAP IP interface. It could lead to easier reaching common functionality meeting requirements on Emergency Services which in turn could lead to a possibility to utilize common platforms and easier exchange of experiences. This is done with the knowledge that other standardization bodies are working on different aspects of the problem. 4.1.1 Summary - The circuit swit
