SIST ES 203 178 V1.1.1:2015
(Main)Considering TS 102 650 and architectures from other standardisation organisations a single functional architecture to support European requirements on emergency caller location determination and transport needs to be developed in particular for the case where VoIP service provider and one or several network operators - all serving the customer in the establishment of an emergency call - are independent enterprises needing to co-operate to determine the location of the (nomadic) caller. The architecture shall identify all necessary interfaces, which are needed to fulfil the requirements outlined in EC Mandate M/493, and provide a basis for possible protocols to be used on those interfaces. Environmental aspect comments: 1) The establishment of emergency calls and the provision of location information about the caller shall not be hampered by high service or network loads or partial service or network outages. (2) The location information shall be provided to the PSAP in a manner that it is easily associated with the respective incoming voice call. (3) Location related information accurate enough to allow routing of the call must be constrained to those entities that require it in order to deliver the call to the correct PSAP. (4) Accurate location information shall be obtained from at least a trustworthy source. A CPE may not be considered trustworthy. User /Consumer Aspects comments: 1) The location should be determined as fast as possible. (2) Should the location determination fail for any reason, the emergency call is still to be setup without delay. (3) The access to and the provision of location information shall be strictly limited to emergency calls only. (4) The architecture shall not be based on location information provided by an entity controlled by the user. Security Aspects (1) The access to location information shall be strictly limited to cases of an emergency call. (2) Location information sufficiently detailed to dispatch personnel and resources shall only be provided to the PSAP handling the emergency call.
Funkcijska arhitektura evropskih določb za ugotavljanje kraja klicatelja v sili in za transport
Ob upoštevanju tehnične specifikacije TS 102 650 in arhitektur drugih organizacij za standardizacijo je treba oblikovati eno samo funkcijsko arhitekturo evropskih določb za ugotavljanje kraja klicatelja v sili in za transport, še posebej v primeru, da sta ponudnik storitev VoIP in eden ali več omrežnih operaterjev, pri čemer vsi sodelujejo pri vzpostavljanju klica v sili stranke, neodvisna podjetja, ki morajo sodelovati pri ugotavljanju kraja (nomadskega) klicatelja. Arhitektura mora določiti vse nujne vmesnike, potrebne za izpolnjevanje zahtev iz mandata M/493, ki ga je podelila Evropska komisija, ter zagotoviti podlago za možne protokole, ki se bodo uporabljali v okviru teh vmesnikov. Pripombe v zvezi z okoljskim vidikom: (1) Vzpostavljanja klicev v sili in zagotavljanja informacij o kraju klicatelja ne smejo ovirati visoke obremenitve storitve ali omrežja ali delni izpadi storitve ali omrežja. (2) Informacije o kraju je treba odzivni točki javne varnosti (PSAP) zagotoviti tako, da jih je mogoče enostavno povezati z ustreznim dohodnim glasovnim klicem. (3) Do informacij, ki se nanašajo na kraj in so dovolj točne, da omogočajo usmerjanje klica, lahko dostopajo samo tisti organi, ki to potrebujejo za usmeritev klica do ustrezne odzivne točke javne varnosti. (4) Točne informacije o kraju je treba pridobiti vsaj od zaupanja vrednega vira. Uporabniška oprema (CPE) se mogoče ne šteje za zaupanja vredno. Pripombe v zvezi z uporabniškimi/potrošniškimi vidiki: (1) Kraj je treba določiti čim hitreje. (2) Če je ugotavljanje kraja zaradi katerega koli razloga neuspešno, je vseeno treba takoj vzpostaviti klic v sili. (3) Dostop do informacij o kraju in njihovo zagotavljanje morata biti strogo omejena le na klice v sili. (4) Arhitektura ne sme temeljiti na informacijah o kraju, ki jih zagotavlja subjekt pod nadzorom uporabnika. Varnostni vidiki (1) Dostop do informacij o kraju mora biti strogo omejen na primere klicev v sili. (2) Informacije o kraju, ki so dovolj podrobne, da je mogoče tja poslati osebje in vire, je dovoljeno posredovati le odzivni točki javne varnosti, ki obravnava klic v sili.
General Information
Standards Content (sample)
SLOVENSKI STANDARD
SIST ES 203 178 V1.1.1:2015
01-oktober-2015
)XQNFLMVNDDUKLWHNWXUDHYURSVNLKGRORþE]DXJRWDYOMDQMHNUDMDNOLFDWHOMDYVLOLLQ]D
WUDQVSRUWFunctional architecture to support European requirements on emergency caller location
determination and transportTa slovenski standard je istoveten z: ES 203 178 V1.1.1
ICS:
33.030 Telekomunikacijske Telecommunication services.
uporabniške rešitve Applications
SIST ES 203 178 V1.1.1:2015 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------SIST ES 203 178 V1.1.1:2015
---------------------- Page: 2 ----------------------
SIST ES 203 178 V1.1.1:2015
ETSI ES 203 178 V1.1.1 (2015-02)
ETSI STANDARD
Functional architecture to support European requirements
on emergency caller location determination and transport
---------------------- Page: 3 ----------------------
SIST ES 203 178 V1.1.1:2015
2 ETSI ES 203 178 V1.1.1 (2015-02)
Reference
DES/E2NA-00001-M493-stage2
Keywords
emergency, location, VoIP
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
The present document can be downloaded from:
http://www.etsi.org/standards-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 between 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.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.aspIf you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspxCopyright Notification
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 the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
3GPP and LTE™ are Trade Marks of ETSI 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---------------------- Page: 4 ----------------------
SIST ES 203 178 V1.1.1:2015
3 ETSI ES 203 178 V1.1.1 (2015-02)
Contents
Intellectual Property Rights ................................................................................................................................ 5
Foreword ............................................................................................................................................................. 5
Modal verbs terminology .................................................................................................................................... 5
1 Scope ........................................................................................................................................................ 6
2 References ................................................................................................................................................ 6
2.1 Normative references ......................................................................................................................................... 6
2.2 Informative references ........................................................................................................................................ 6
3 Definitions and abbreviations ................................................................................................................... 7
3.1 Definitions .......................................................................................................................................................... 7
3.2 Abbreviations ..................................................................................................................................................... 9
4 Descriptions and assumptions .................................................................................................................. 9
4.1 Introduction ........................................................................................................................................................ 9
4.2 Location information descriptions .................................................................................................................... 10
4.2.1 General ........................................................................................................................................................ 10
4.2.2 Location value ............................................................................................................................................ 10
4.2.3 Location identifier....................................................................................................................................... 10
4.2.4 Location reference ...................................................................................................................................... 11
5 Functional architecture to support European requirements on emergency caller location
determination and transport .................................................................................................................... 11
5.1 Overview .......................................................................................................................................................... 11
5.2 Architectural requirements ............................................................................................................................... 12
5.2.1 General ........................................................................................................................................................ 12
5.2.2 ANP - Access Network Provider ................................................................................................................ 13
5.2.3 VSP - Voice Service Provider..................................................................................................................... 13
5.2.4 ECSP - Emergency Call Service Provider .................................................................................................. 13
5.2.5 PSP - PSAP Service Provider ..................................................................................................................... 14
5.3 Interfaces .......................................................................................................................................................... 14
5.3.1 Interface definitions .................................................................................................................................... 14
5.3.2 Information flows ....................................................................................................................................... 16
5.3.2.1 ia interface ............................................................................................................................................. 16
5.3.2.2 ib interface............................................................................................................................................. 17
5.3.2.3 ic interface ............................................................................................................................................. 17
5.3.2.4 id interface............................................................................................................................................. 18
5.3.2.5 ie interface ............................................................................................................................................. 18
5.3.2.6 if interface ............................................................................................................................................. 18
5.3.2.7 ig interface............................................................................................................................................. 19
5.3.2.8 ih interface............................................................................................................................................. 19
5.3.2.9 ii interface ............................................................................................................................................. 20
5.3.2.10 ij interface ............................................................................................................................................. 21
5.3.2.11 ik interface............................................................................................................................................. 22
5.3.2.12 il interface ............................................................................................................................................. 22
5.3.2.13 im interface ........................................................................................................................................... 23
5.3.2.14 in interface............................................................................................................................................. 23
5.4 Functional entities ............................................................................................................................................ 24
5.4.1 ANP ............................................................................................................................................................ 24
5.4.1.1 Location Server (LS) ............................................................................................................................. 24
5.4.2 VSP ............................................................................................................................................................. 25
5.4.2.1 VSP Call Control .................................................................................................................................. 25
5.4.3 ECSP ........................................................................................................................................................... 26
5.4.3.1 ESRF ..................................................................................................................................................... 26
5.4.3.2 LS Proxy ............................................................................................................................................... 26
5.4.3.3 Other entities ......................................................................................................................................... 26
5.4.4 PSAP Service Provider ............................................................................................................................... 27
ETSI---------------------- Page: 5 ----------------------
SIST ES 203 178 V1.1.1:2015
4 ETSI ES 203 178 V1.1.1 (2015-02)
5.4.4.1 Emergency Service Routeing Proxy...................................................................................................... 27
5.4.4.2 Route Server .......................................................................................................................................... 27
5.4.4.3 Other entities ......................................................................................................................................... 27
5.4.5 other functional entities .............................................................................................................................. 28
5.4.5.1 Location Server Discovery Function ..................................................................................................... 28
5.4.5.2 User Equipment ..................................................................................................................................... 28
5.4.5.3 IP-PSAP ................................................................................................................................................ 28
5.4.5.4 PSTN-PSAP .......................................................................................................................................... 28
5.5 Information flow diagrams ............................................................................................................................... 29
5.5.1 Introduction................................................................................................................................................. 29
5.5.2 ANP provides a location value ................................................................................................................... 29
5.5.3 ANP provides location reference to the VSP and the ECSP pulls location value ....................................... 31
5.5.4 ANP provides to the VSP a location identifier ........................................................................................... 32
5.5.5 ANP provides location identifier to the VSP and the PSAP pulls location value ....................................... 34
5.6 Extension of the Functional Architecture for Networks with VPN, NAT/PAT and other components
which change Packet Flow Identity .................................................................................................................. 35
5.7 Extension of the Functional Architecture to support VSP Aggregation Providers ........................................... 35
6 Protocol and other requirements ............................................................................................................. 36
6.1 Generic requirements ....................................................................................................................................... 36
6.2 Trust relationships ............................................................................................................................................ 36
Annex A (normative): Extension of the Functional Architecture for Networks with VPN,
NAT/PAT and other components which change Packet Flow Identity .... 37A.1 General ................................................................................................................................................... 37
A.2 LS chaining solution ............................................................................................................................... 37
A.2.1 Location chaining interface impacts ................................................................................................................. 39
A.3 HOST_ID solution ................................................................................................................................. 39
Annex B (informative): M/493 Scope ................................................................................................... 43
Annex C (normative): Extension of the Functional Architecture to support an aggregating
VSP .................................................................................................................. 44
C.1 General ................................................................................................................................................... 44
C.2 Architectual requirements for VSP Aggregation Provider (VAP) ......................................................... 44
C.3 Extended Interface definition ................................................................................................................. 45
C.4 VSP Aggregating Entity ......................................................................................................................... 45
Annex D (informative): Avoiding authentication between the VSP and the ANP............................ 46
History .............................................................................................................................................................. 48
ETSI---------------------- Page: 6 ----------------------
SIST ES 203 178 V1.1.1:2015
5 ETSI ES 203 178 V1.1.1 (2015-02)
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://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 ETSI Web
server) which are, or may be, or may become, essential to the present document.Foreword
This ETSI Standard (ES) has been produced by ETSI Project End-to-End Network Architectures (E2NA).
Modal verbs terminologyIn 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 (Verbal forms for the expression of
provisions)."must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI---------------------- Page: 7 ----------------------
SIST ES 203 178 V1.1.1:2015
6 ETSI ES 203 178 V1.1.1 (2015-02)
1 Scope
The present document describes the unified functional architecture to support 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 - are 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 used 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 replace existing deployed solutions. It should enable operators and undertakings
providing services to realize transmission of location information to the Public Safety Answering Point.
2 References2.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 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 location 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 applicable.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 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 particular 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] 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
---------------------- Page: 8 ----------------------
SIST ES 203 178 V1.1.1:2015
7 ETSI ES 203 178 V1.1.1 (2015-02)
[i.5] IETF RFC 6753: "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 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
(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: "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 definitions apply:
access network: portion of the telecommunications network that provides access to the switching function and
terminates the user access signallingAccess Network Provider (ANP): service provider that provides physical and IP connectivity to a user equipment
(UE) via a fixed or mobile accessNOTE: 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.
emergency: urgent need for assistance or reliefemergency call: call from a user to an emergency call centre, PSAP or similar agency charged with routeing calls to the
relevant emergency response organizationemergency 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 between the voice service
providers and the public safety answering point service providersemergency caller: individual 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 and
emergency medical servicesemergency 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 situationsemergency 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---------------------- Page: 9 ----------------------
SIST ES 203 178 V1.1.1:2015
8 ETSI ES 203 178 V1.1.1 (2015-02)
FlowChanger: device in an IP flow, which changes the packet flow 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 valueEXAMPLE: A cell ID or line ID (see ETSI TS 123 167 [i.1]).
NOTE: A location value can be obtained 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 location server and provides sufficient information to allow the location server to
provide the location value for the UEEXAMPLE: https://ls.example.com:49152/uri/w3g61nf5n66p0, IETF RFC 6753 [i.5].
location value: civic or geodetic position
network-provided location information: any location information pertaining to the calling device that is determined,
provided or verified by the ANPNext 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
independent from underlying transport-related technologiesnomadic: 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 PSAPsPSAP Service Provider: service provider that provides connectivity to Public Safety Answering Points (PSAPs) and
directs emergency calls from the ECSP to the PSAPPublic Safety Answering Point (PSAP): physical location where emergency calls are received under the responsibility
of a public authorityNOTE: See Commission Recommendation C(2003)2657 [i.9] and ETSI TS 102 181 [i.6].
regulatory domain: geographical area where a set of regulatory rules applies
telecommunication: any transmission, emission, or reception of signs, signals, writing, images, sounds or intelligence
of any nature, by wire, radio, optical fibre or other electromagnetic systemuser access: point of connection to a telecommunication network from which a call can be placed
NOTE: This includes public telephones and "emergency call facilities".user equipment: device allowing a user access to network services
user-provided location information: any location information originating from user-equipment that is not
independently verified by the ANPVoice Service Provider (VSP): specific type of application service provider that provides voice related services and
optionally text and video-related services, on IPVSP Aggregation Provider (VAP): provider that a VSP or group of VSPs can use to support call routing to remote
ECSPs and for the generation of related call data recordsETSI
---------------------- Page: 10 ----------------------
SIST ES 203 178 V1.1.1:2015
9 ETSI ES 203 178 V1.1.1 (2015-02)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ANP Access Network Provider
AP Access Point
CGN Carrier Grade NAT
DHCP Dynamic Host Configuration Protocol
DNS Domain Name Server
EC European Commission
ECSP Emergency Call Service Provider
ESO European Standards Organization
ESRF Emergency Service Routing Function
ESRP Emergency Service Routeing Proxy
ETSI European Telecommunications Standards Institute
FID Flow Identity
FID-N N Flow Identity
FQDN Fully Qualified Domain Name
IETF Internet Engineering Task Force
IMS IP Multimedia Subsystem
IP Internet Protocol
ISDN Integrated Services Digital Network
LS Location Server
LS-N N Location Server
NAPTR Naming Authority Pointer
NAT Network Address Translation
NGN Next Generation Network
PAT Port and Address Translation
PBX Private Branch Exchange
PCRF Policy and Charging Rules Function
PSAP Public Safety Answering Point
PSP PSAP Service Provider
PSTN Public Switched Telephone Network
RFC Request For Comment
SIP Session Initiation Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
UE User Equipment
URI Uniform Resource Identifier
VAE VSP Aggregating Entity
VAP VSP Aggegation Provider
VoIP Voice over Internet Protocol
VPN Virtual Private Network
VSP Voi
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.