ETSI ES 203 178-2015 Functional architecture to support European requirements on emergency caller location determination and transport (V1 1 1)《用于支持紧急呼叫位置确定和传输的欧洲要求的功能架构 (V1 1 1)》.pdf

《ETSI ES 203 178-2015 Functional architecture to support European requirements on emergency caller location determination and transport (V1 1 1)《用于支持紧急呼叫位置确定和传输的欧洲要求的功能架构 (V1 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI ES 203 178-2015 Functional architecture to support European requirements on emergency caller location determination and transport (V1 1 1)《用于支持紧急呼叫位置确定和传输的欧洲要求的功能架构 (V1 1 1)》.pdf（48页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI ES 203 178 V1.1.1 (2015-02) Functional architecture to support European requirements on emergency caller location determination and transport ETSI STANDARD ETSI ETSI ES 203 178 V1.1.1 (2015-02) 2Reference DES/E2NA-00001-M493-stage2 Keywords emergency, location, VoIP ETSI 650 Route des Lucioles

2、 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-

3、search The present 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 bet

4、ween such versions 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. Inform

5、ation 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: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notificatio

6、n No part 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 th

7、e foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered fo

8、r 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 ETSI ES 203 178 V1.1.1 (2015-02) 3Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g3

9、2.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 9g34 Descriptions and assumptions 9g34.1 Introduction 9g34.2 Location information descriptions 10g34.2.1 General 10g34.2.2 Location value 10g34.2.3 Location identif

10、ier. 10g34.2.4 Location reference 11g35 Functional architecture to support European requirements on emergency caller location determination and transport 11g35.1 Overview 11g35.2 Architectural requirements . 12g35.2.1 General 12g35.2.2 ANP - Access Network Provider 13g35.2.3 VSP - Voice Service Prov

11、ider. 13g35.2.4 ECSP - Emergency Call Service Provider 13g35.2.5 PSP - PSAP Service Provider . 14g35.3 Interfaces 14g35.3.1 Interface definitions 14g35.3.2 Information flows . 16g35.3.2.1 ia interface. 16g35.3.2.2 ib interface. 17g35.3.2.3 ic interface . 17g35.3.2.4 id interface. 18g35.3.2.5 ie inte

12、rface . 18g35.3.2.6 if interface . 18g35.3.2.7 ig interface. 19g35.3.2.8 ih interface. 19g35.3.2.9 ii interface . 20g35.3.2.10 ij interface . 21g35.3.2.11 ik interface. 22g35.3.2.12 il interface . 22g35.3.2.13 im interface . 23g35.3.2.14 in interface. 23g35.4 Functional entities 24g35.4.1 ANP 24g35.

13、4.1.1 Location Server (LS) . 24g35.4.2 VSP . 25g35.4.2.1 VSP Call Control 25g35.4.3 ECSP . 26g35.4.3.1 ESRF . 26g35.4.3.2 LS Proxy . 26g35.4.3.3 Other entities . 26g35.4.4 PSAP Service Provider . 27g3ETSI ETSI ES 203 178 V1.1.1 (2015-02) 45.4.4.1 Emergency Service Routeing Proxy 27g35.4.4.2 Route Se

14、rver 27g35.4.4.3 Other entities . 27g35.4.5 other functional entities 28g35.4.5.1 Location Server Discovery Function . 28g35.4.5.2 User Equipment . 28g35.4.5.3 IP-PSAP 28g35.4.5.4 PSTN-PSAP 28g35.5 Information flow diagrams . 29g35.5.1 Introduction. 29g35.5.2 ANP provides a location value . 29g35.5.

15、3 ANP provides location reference to the VSP and the ECSP pulls location value . 31g35.5.4 ANP provides to the VSP a location identifier . 32g35.5.5 ANP provides location identifier to the VSP and the PSAP pulls location value . 34g35.6 Extension of the Functional Architecture for Networks with VPN,

16、 NAT/PAT and other components which change Packet Flow Identity 35g35.7 Extension of the Functional Architecture to support VSP Aggregation Providers . 35g36 Protocol and other requirements . 36g36.1 Generic requirements . 36g36.2 Trust relationships 36g3Annex A (normative): Extension of the Functio

17、nal Architecture for Networks with VPN, NAT/PAT and other components which change Packet Flow Identity 37g3A.1 General . 37g3A.2 LS chaining solution . 37g3A.2.1 Location chaining interface impacts . 39g3A.3 HOST_ID solution . 39g3Annex B (informative): M/493 Scope . 43g3Annex C (normative): Extensi

18、on of the Functional Architecture to support an aggregating VSP 44g3C.1 General . 44g3C.2 Architectual requirements for VSP Aggregation Provider (VAP) . 44g3C.3 Extended Interface definition . 45g3C.4 VSP Aggregating Entity . 45g3Annex D (informative): Avoiding authentication between the VSP and the

19、 ANP 46g3History 48g3ETSI ETSI ES 203 178 V1.1.1 (2015-02) 5Intellectual 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,

20、 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:/ipr.etsi.org). Pursuant to th

21、e 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. For

22、eword This ETSI Standard (ES) has been produced by ETSI Project End-to-End Network Architectures (E2NA). 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 claus

23、e 3.2 of the ETSI Drafting Rules (Verbal 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 178 V1.1.1 (2015-02) 61 Scope The present document describes the unified functional architecture to suppo

24、rt requirements as outlined in European Commission (EC) mandate M/493 i.4 on emergency caller location determination and transport, in particular for the case where the VoIP service provider and one or several network operators - all serving the customer in the establishment of an emergency call - a

25、re independent enterprises needing to co-operate to determine the location of the (nomadic) caller. The architecture identifies all necessary interfaces, which are needed to fulfil the requirements outlined in EC Mandate M/493 i.4, and provides a basis for the specification of the protocols to be us

26、ed on those interfaces. The present document is applicable to both NGN and pre-NGN IP-based networks. The architecture defined in the present document is intended to be compatible with IMS-based deployments but does not require compliance to IMS specifications. This architecture does not intend to r

27、eplace existing deployed solutions. It should enable operators and undertakings providing services to realize transmission of location information to the Public Safety Answering Point. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edit

28、ion number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected loca

29、tion might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. Not applicab

30、le. 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, only the cited version applies. For non-specific references, the latest version of the reference document (including any

31、 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 referenced documents are not necessary for the application of the present document but they assist the user with regard to a p

32、articular subject area. i.1 ETSI TS 123 167: “Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) emergency sessions (3GPP TS 23.167)“. i.2 IETF RFC 6967: “Analysis of Potential Solutions for Revealing a Host Identifier (HOST-ID) in Shared Address Deployments“. i.3

33、Draft-boucadair-intarea-host-identifier-scenarios-03 (March 2013): “Host Identification: Use Cases“. i.4 M/493: “Standardisation Mandate to the European Standards Organisations (ESO) in support of the location enhanced emergency call service“. ETSI ETSI ES 203 178 V1.1.1 (2015-02) 7i.5 IETF RFC 6753

34、: “A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)“. i.6 ETSI TS 102 181: “Emergency Communications (EMTEL); Requirements for communication between authorities/organizations during emergencies“. i.7 ETSI TS 102 650: “Telecommunications and Internet converged Services and

35、Protocols for Advanced Networking (TISPAN); Analysis of Location Information Standards produced by various SDOs“. i.8 Directive 2002/22/EC of the European Parliament and of the Council of 7 March 2002 on universal service and users rights relating to electronic communications networks and services (

36、Universal Service Directive). i.9 Commission Recommendation 2003/558/EC of 25 July 2003 on the processing of caller location information in electronic communication networks for the purpose of location-enhanced emergency call services (notified under document number C(2003)2657). i.10 IETF RFC 5222:

37、 “LoST: A Location-to-Service Translation Protocol“. i.11 IETF RFC 4848: “Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and defin

38、itions apply: access network: portion of the telecommunications network that provides access to the switching function and terminates the user access signalling Access Network Provider (ANP): service provider that provides physical and IP connectivity to a user equipment (UE) via a fixed or mobile a

39、ccess NOTE: The access network may be provided by a single organization or it may be provided by a number of different organizations, BUT the interfaces between these organizations are not relevant to the scope of the present document as it is matter of contractual relations between the parties. eme

40、rgency: 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, e

41、mergency 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 between the voice service providers and the public safety answering point service providers emergency caller: in

42、dividual placing an emergency call to reach the suitable PSAP emergency response organization: local or national force established to provide assistance to citizens in the event of their being involved in an emergency situation and requiring specialized help, for example, the police, fire service an

43、d emergency medical services emergency service: service that provides immediate and rapid assistance in situations where there is a direct risk to life or limb, individual or public health or safety, to private or public property, or the environment but not necessarily limited to these situations em

44、ergency situation: abnormal situation of serious nature that develops suddenly and unexpectedly, of which the evolution is uncertain and which may turn into a crisis or cause damage and casualties ETSI ETSI ES 203 178 V1.1.1 (2015-02) 8FlowChanger: device in an IP flow, which changes the packet flow

45、 identity, for example changing the IP address and/or port, so the UE can no longer be identified in the original access network location identifier: public network identifier, which provides a location value EXAMPLE: A cell ID or line ID (see ETSI TS 123 167 i.1). NOTE: A location value can be obta

46、ined from a location identifier by applying a static mapping or the location identifier may be encoded in such a way that it contains a location value (e.g. a ZIP code). location information: location value, and/or a location identifier and/or a location reference location reference: identifies a lo

47、cation server and provides sufficient information to allow the location server to provide the location value for the UE EXAMPLE: https:/:49152/uri/w3g61nf5n66p0, IETF RFC 6753 i.5. location value: civic or geodetic position network-provided location information: any location information pertaining t

48、o the calling device that is determined, provided or verified by the ANP Next Generation Network (NGN): packet-based network able to provide telecommunication services and able to make use of multiple broadband, QoS-enabled transport technologies and in which service-related functions are independen

49、t from underlying transport-related technologies nomadic: having the ability to move across network access points NOTE: A nomadic user can make calls from different locations. However, unlike a mobile user, the location of a nomadic user cannot change during a specific call. originating network: access network in which the emergency call was placed packet flow identity: all network parameters, which unambiguously identify a IP flow PSAP address: URI or an E.164 number identifying a PSAP or a group of PSAPs PSAP Service Provider: s