1、 ETSI ES 203 283 V1.1.1 (2017-11) Protocol specifications for Emergency Service Caller Location determination and transport ETSI STANDARD ETSI ETSI ES 203 283 V1.1.1 (2017-11) 2 Reference DES/NTECH-00025-M493-protocols Keywords emergency, location, VoIP ETSI 650 Route des Lucioles F-06921 Sophia Ant
2、ipolis 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 The present document can be downloaded from: http:/www.etsi.org/standards-search The present
3、document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions
4、and/or in print, the only prevailing document is the print of the Portable Document Format (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 curren
5、t status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part
6、 may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoi
7、ng restriction extend to reproduction in all media. ETSI 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizat
8、ional Partners. oneM2M logo is protected for the benefit of its Members. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI ES 203 283 V1.1.1 (2017-11) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References
9、6g32.1 Normative references . 6g32.2 Informative references 8g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 10g34 Descriptions and assumptions 11g34.1 Introduction 11g35 Protocol specifications for the interfaces of the functional architecture in ETSI ES 203 178 . 12g3
10、5.1 Interface ia 12g35.2 Interface ib 12g35.2.1 Protocol specifications 12g35.2.2 IMS/NGN implementation considerations 12g35.3 Interface ic 13g35.3.1 Protocol specifications 13g35.3.1.1 General 13g35.3.1.2 Location request without pre-established relationship between VSP and ANP 13g35.3.1.3 Locatio
11、n request in the case of pre-established relationship between VSP and ANP . 15g35.3.1.4 Location request to a gateway mobile location centre 17g35.3.2 IMS implementation considerations . 17g35.4 Interface id 18g35.4.1 Protocol specifications 18g35.4.2 IMS implementation considerations . 18g35.5 Inte
12、rface ie 18g35.5.1 Protocol specifications 18g35.5.2 IMS implementation considerations . 21g35.6 Interface if 22g35.6.1 Protocol specifications 22g35.6.2 IMS/NGN implementation considerations 24g35.7 Interface ig 24g35.7.1 Protocol specifications 24g35.7.2 IMS implementation considerations . 24g35.8
13、 Interface ih 25g35.8.1 Protocol specifications 25g35.8.2 IMS implementation considerations . 27g35.9 Interface ii 28g35.9.1 Protocol specifications 28g35.9.2 IMS implementation considerations . 28g35.10 Interface ij 28g35.10.1 Protocol specifications 28g35.10.2 IMS/NGN implementation considerations
14、 30g35.11 Interface ik 30g35.11.1 Protocol specifications 30g35.11.2 IMS/NGN implementation considerations 31g35.12 Interface il 32g35.12.1 Protocol specifications 32g35.12.2 IMS implementation considerations . 32g35.13 Interface im 33g35.13.1 Protocol specifications 33g35.13.2 IMS implementation co
15、nsiderations . 33g3ETSI ETSI ES 203 283 V1.1.1 (2017-11) 4 5.14 Interface in 34g35.14.1 Protocol specifications 34g35.14.2 IMS implementation considerations . 34g36 Functional entities 34g36.1 UE 34g36.2 Location Server 34g36.3 LS Discovery 35g36.4 VSP Call Control 35g36.5 Emergency Service Routing
16、Function (ESRF) . 35g36.5.1 Retrieval of the PSAP URI . 35g36.5.2 Additional functionalities of the ESRF . 36g36.5.3 Privacy considerations 36g36.6 LS Proxy . 36g36.7 Emergency Service Routing Proxy (ESRP) . 37g36.8 Route Server . 37g36.9 IP-PSAP . 37g36.10 PSTN-PSAP . 37g37 Protocol registration re
17、quirements . 37g37.1 General . 37g37.2 ProviderIDseries . 37g37.3 ProviderID 38g3History 39g3ETSI ETSI ES 203 283 V1.1.1 (2017-11) 5 Intellectual Property Rights Essential patents IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaini
18、ng 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 Secretaria
19、t. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). 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
20、 ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the p
21、roperty of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This ETSI Standard (ES) has been
22、produced by ETSI Technical Committee Network Technologies (NTECH). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verb
23、al forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI ES 203 283 V1.1.1 (2017-11) 6 1 Scope The present document describes the protocol specifications for emergency service caller location determination a
24、nd transport architecture as specified in ETSI ES 203 178 1. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific ref
25、erences, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at th
26、e time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI ES 203 178: “Functional architecture to support European requirements on emergency caller location determination and transport“.
27、 2 OMA-TS-MLP-V3_5: “Mobile Location Protocol Version 3.5“. NOTE: Available at http:/www.openmobilealliance.org/release/MLS/V1_4-20150224-C/OMA-TS-MLP-V3_5-20150224-C.pdf. 3 IETF RFC 3261: “SIP: Session Initiation Protocol“. 4 IETF RFC 4320: “Actions Addressing Identified Issues with the Session Ini
28、tiation Protocols (SIP) Non-INVITE Transaction“. 5 IETF RFC 5393: “Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies“. 6 IETF RFC 5954: “Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261“. 7 IETF RFC 6442: “Location Conveyance for the Sess
29、ion Initiation Protocol“. 8 IETF RFC 4566: “SDP: Session Description Protocol“. 9 IETF RFC 3264: “An Offer/Answer Model with the Session Description Protocol (SDP)“. 10 ETSI TS 124 229: “Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); L
30、TE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229)“. 11 ETSI TS 129 165: “Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Inter-IMS Ne
31、twork to Network Interface (NNI) (3GPP TS 29.165)“. 12 ETSI TS 123 167: “Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) emergency sessions (3GPP TS 23.167)“. 13 ETSI ES 283 035: “Network Technologies (NTECH); Network Attachment; e2 interface based on the DIAMET
32、ER protocol“. ETSI ETSI ES 203 283 V1.1.1 (2017-11) 7 14 ETSI TS 129 163: “Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (
33、3GPP TS 29.163)“. 15 IETF RFC 4119: “A Presence-based GEOPRIV Location Object Format“. 16 IETF RFC 5139: “Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)“. 17 IETF RFC 5491: “GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarifi
34、cation, Considerations, and Recommendations“. 18 IETF RFC 6848: “Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)“. 19 IETF RFC 7216: “Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS“. 20 IETF RFC 5985: “HTTP-Enabled
35、 Location Delivery (HELD)“. 21 IETF RFC 5986: “Discovering the Local Location Information Server (LIS)“. 22 IETF RFC 6155: “Use of Device Identity in HTTP-Enabled Location Delivery (HELD)“. 23 IETF RFC 6915: “Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)“. 24 IETF RFC 7840: “A Ro
36、uting Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol“. 25 IETF RFC 6753: “A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)“. 26 IETF RFC 5031: “A Uniform Resource Name (URN) for Emergency and Other Well-Known Services“. 27 IETF RFC 6881: “Best Cur
37、rent Practice for Communications Services in Support of Emergency Calling“. 28 IETF RFC 3325: “Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks“. 29 IETF RFC 7852: “Additional Data Related to an Emergency Call“. 30 IETF RFC 3323: “A Privacy Me
38、chanism for the Session Initiation Protocol (SIP)“. 31 IETF RFC 5079: “Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)“. 32 Recommendation ITU-T Q.850 (1998) Amd. 1 (07/2001): “Usage of cause and location in the Digital Subscriber Signalling System No. 1 (DSS1) and the Signalli
39、ng System No. 7 ISDN user part (ISUP), Amendment 1“. 33 ETSI TS 124 525: “Universal Mobile Telecommunications System (UMTS); LTE; Business trunking; Architecture and functional description (3GPP TS 24.525)“. 34 ETSI EN 300 899-1 (V1.1.2) (09-1998): “Integrated Services Digital Network (ISDN); Signal
40、ling System No.7; Interworking between ISDN User Part (ISUP) version 2 and Digital Subscriber Signalling System No. one (DSS1); Part 1: Protocol specification ITU-T Recommendation Q.699, modified“. 35 IETF RFC 7163: “URN for Country-Specific Emergency Services“. 36 draft-winterbottom-sipcore-locpara
41、m-01 (May 2017): “Location Source Parameter for the SIP Geolocation Header Field“. ETSI ETSI ES 203 283 V1.1.1 (2017-11) 8 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, o
42、nly the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following refere
43、nced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI ES 282 001: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture“. i.2 I
44、ETF RFC 3825: “Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information“. i.3 IETF RFC 6225: “Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information“. i.4 ETSI TS 123 228: “Digital cellular telecommunications syst
45、em (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228)“. i.5 ETSI TS 123 032: “Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Universal Geographical Area Des
46、cription (GAD) (3GPP TS 23.032)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: access network: portion of the telecommunications network that provides access to the switching function and terminates the user acce
47、ss signalling Access Network Provider (ANP): service provider that provides physical and IP connectivity to a user equipment (UE) via a fixed or mobile access NOTE: The access network may be provided by a single organization or it may be provided by a number of different organizations, BUT the inter
48、faces between these organizations are not relevant to the scope of the present document as it is matter of contractual relations between the parties. default PSAP: PSAP that is routed to when insufficient information exists to route to a specific PSAP, based on either location or emergency category
49、emergency: urgent need for assistance or relief emergency call: call from a user to an emergency call centre, PSAP or similar agency charged with routeing calls to the relevant emergency response organization emergency call facilities: mechanisms provided by public or private communications networks, emergency telephone stanchions/boxes, fire alarms, etc. the use of which enables emergency calls to be made Emergency Call Service Provider (ECSP): service provider that acts as a mediator bet
