ETSI SR 002 777 V1.1.1 (2010-07)

Emergency Communications (EMTEL); Test/verification procedure for emergency calls

DSR/EMTEL-00014

General Information

• Status: Published
• Publication Date: 01-Jul-2010
• Technical Committee: EMTEL - Emergency Communications
• Current Stage: 12 - Completion
• Due Date: 10-Jul-2010
• Completion Date: 02-Jul-2010

Standards Content (Sample)

Special Report
Emergency Communications (EMTEL);
Test/verification procedure for emergency calls

2 ETSI SR 002 777 V1.1.1 (2010-07)

Reference
DSR/EMTEL-00014
Keywords
conformance, CTS, emergency, location, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP 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
3 ETSI SR 002 777 V1.1.1 (2010-07)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 Testing functionality. 8
4.1 Emergency Calls/Sessions in Packet (IP) based Networks . 8
4.2 Emergency Calls in Circuit Switched Networks . 11
4.2.1 PSTN/ISDN . 11
4.2.2 Mobile Phone (3GPP) . 11
History . 13

ETSI
4 ETSI SR 002 777 V1.1.1 (2010-07)
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 Special Report (SR) has been produced by ETSI Special Committee Emergency Communications (EMTEL).
ETSI
5 ETSI SR 002 777 V1.1.1 (2010-07)
1 Scope
The present document outlines a test procedures for emergency calls from individuals (citizens) to authorities.
In order to test (in a given environment) the emergency call/messaging capability of the current operator it would be
favourable to have a test procedure, i.e. to be able to call a "test" address not invoking a real emergency call. Such a test
could be initiated either manually or automatically (e.g. with a given periodicity). It is advised to observe the threats in
security vulnerability and of network overload. Such a procedure should work both for calls from CS and PS networks
(wired or wireless). The testing functionality may also be utilized in order to facilitate other location based/dependent
services as described in TS 123 271 [i.8]. As for emergency services, both CS and PS PSAPs should be catered for.
The aim of the present documents is to make a contribution to an overall functional architecture and specification for
such a test service.
2 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.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
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] ETSI TR 102 180: "Emergency Communications (EMTEL); Basis of requirements for
communication of individuals with authorities/organizations in case of distress (Emergency call
handling)".
[i.3] ETSI TR 102 476: "Emergency Communications (EMTEL); Emergency calls and VoIP: possible
short and long term solutions and standardization activities".
[i.4] IETF [draft-ietf-ecrit-phone-bcp]: "Best Current Practice for Communications Services in support
of Emergency Calling".
NOTE: For the status of work items within the IETF ECRIT working group please see:
http://tools.ietf.org/wg/ecrit/
[i.5] IETF [draft-ietf-ecrit-framework]: "Framework for Emergency Calling using Internet
Multimedia".
[i.6] IETF [draft-schulzrinne-ecrit-unauthenticated-access]: "Extensions for Unauthenticated &
Unauthorized Devices".
ETSI
6 ETSI SR 002 777 V1.1.1 (2010-07)
[i.7] IETF RFC 5222: "LoST: A Location-to-Service Translation Protocol".
[i.8] ETSI TS 123 271: "Digital cellular telecommunications system (Phase 2+); Universal
Mobile Telecommunications System (UMTS); LTE; Functional stage 2 description of Location
Services (LCS) (3GPP TS 23.271)".
[i.9] ETSI TS 136 305: "LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN);
Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN
(3GPP TS 36.305)".
[i.10] ETSI TS 125 305: "Universal Mobile Telecommunications System (UMTS); Stage 2 functional
specification of User Equipment (UE) positioning in UTRAN (3GPP TS 25.305)".
[i.11] ETSI TS 143 059: "Digital cellular telecommunications system (Phase 2+); Functional stage 2
description of Location Services (LCS) in GERAN (3GPP TS 43.059)".
[i.12] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for
Civic Addresses Configuration Information", November 2006.
[i.13] IETF RFC 3825: "Dynamic Host Configuration Protocol Option for Coordinate-based Location
Configuration Information", July 2004.
[i.14] IETF [draft-ietf-geopriv-http-location-delivery]: "HTTP Enabled Location Delivery (HELD)",
Barnes, M., Winterbottom, J., Thomson, M., and B. Stark.
NOTE: For the status of work items within the IETF GEOPRIV working group please see :
http://tools.ietf.org/wg/geopriv/
[i.15] IEEE 802.1AB: "Station and Media Access Control Connectivity Discovery", 2009.
[i.16] IETF [draft-ietf-geopriv-arch]: "An Architecture for Location and Location Privacy in Internet", R.
Barnes, M. Lepinskim, A. Cooper, J. Morris, H. Tschofenig, H. Schulzrinne.
[i.17] IETF RFC 3261: "SIP: Session Initiation Protocol", J. Rosenberg et al., June 2002.
[i.18] ETSI TS 122 101: "Universal Mobile Telecommunications System (UMTS); LTE; Service
aspects; Service principles (3GPP TS 22.101)".
[i.19] ETSI TR 121 905: "Universal Mobile Telecommunications System (UMTS); Vocabulary for
3GPP Specifications (3GPP TR 21.905)".
[i.20] Directive 2006/24/EC of the European Parliament and of the Council of 15 March 2006 on the
retention of data generated or processed in connection with the provision of publicly available
electronic communications services or of public communications networks and amending
Directive 2002/58/EC.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TS 123 167 [i.1], TR 102 180 [i.2],
TS 123 271 [i.8], TR 121 905 [i.19] and the following apply:
Access Network Provider (ANP): provides physical access to the network
dispatch location: location used for dispatching responders to the person in need of assistance
NOTE: According to [i.5] "the dispatch location must be sufficiently precise to easily locate the caller; it typically
needs to be more accurate than the routing location".
IP service Provider (ISP): provides access to the IP network, allocates IP addresses to users and route their traffic
location configuration: location configuration is the process in which an endpoint learns its physical location
ETSI
7 ETSI SR 002 777 V1.1.1 (2010-07)
Location Configuration Protocol (LCP): protocol used by an endpoint to learn its location
location conveyance: location conveyance delivers location information to another element
location determination: location determination finds where an endpoint is physically located
EXAMPLE: The endpoint may contain a GPS receiver used to measure its own location or the location may be
determined by a network administrator using a wiremap database.
Location Information Server (LIS): location Information Server that stores location information for retrieval by an
authorized entity
NOTE: The LIS maps network addresses or equipment IDs to physical locations.
No Access Authorization (NAA): current access network requires access authorization and the caller does not have
valid user credentials
NOTE: This includes the case where the access network allows pay-per-use, as is common for wireless hotspots,
but there is insufficient time to pay for access.
No Voice service Provider (NVP): caller does not have a Voice (over IP) Service Provider (VSP) at the time of the call
physical location: physical location, as used here is where a person or device is located in physical space, described by
a coordinate system or a civic address
NOTE: It is distinguished from the network location, described by a network address.
routing location: routing location of a device is used for routing an emergency call and may not be as precise as the
Dispatch Location
NOTE: These definitions are adopted from [i.5] - location, as referred to here, normally refer to physical location.
User Agent (UA): In SIP a user agent is a set of applications running in the UE (the user equipment)
NOTE: This set consists of two units:
1) a user agent client: a caller application that initiates and sends SIP requests; and
2) a user agent server: an application that receives and responds to SIP requests on behalf of clients,
accepts, redirects or refuses calls.
Voice Service Provider (VSP): provides a VoIP service
Zero-Balance voice service Provider (ZBP): caller has valid credentials with a VSP, but is not allowed to place calls,
e.g. because the user has a zero balance in a prepaid account
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TS 123 167 [i.1], TS 122 101 [i.18],
TR 121 905 [i.19] and the following apply:
ANP Access Network Provider
CS Circuit Switched
DHCP Dynic Host Confi
...