ETSI TS 103 479 V1.1.1 (2019-12)

Emergency Communications (EMTEL); Core elements for network independent access to emergency services

DTS/EMTEL-00037

General Information

• Status: Published
• Publication Date: 15-Dec-2019
• Technical Committee: EMTEL - Emergency Communications
• Current Stage: 12 - Completion
• Due Date: 18-Dec-2019
• Completion Date: 16-Dec-2019

Standards Content (Sample)

TECHNICAL SPECIFICATION
Emergency Communications (EMTEL);
Core elements for network independent access
to emergency services
2 ETSI TS 103 479 V1.1.1 (2019-12)

Reference
DTS/EMTEL-00037
Keywords
emergency services, location, multimedia
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
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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
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 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.

© ETSI 2019.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI TS 103 479 V1.1.1 (2019-12)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
Executive summary . 7
Introduction . 7
1 Scope . 9
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 12
3 Definition of terms, symbols and abbreviations . 12
3.1 Terms . 12
3.2 Symbols . 12
3.3 Abbreviations . 12
4 General . 14
4.1 Overview . 14
4.2 Architecture . 15
4.3 Mandatory Interfaces . 16
4.4 Optional Interfaces . 17
5 Entities . 18
5.1 Border Control Function (BCF) . 18
5.1.1 Overview . 18
5.1.2 Mandatory Interfaces . 18
5.1.3 Optional Interfaces . 18
5.2 Emergency Service Routing Proxy (ESRP) . 19
5.2.1 Overview . 19
5.2.2 Mandatory Interfaces . 19
5.2.3 Optional Interfaces . 20
5.2.4 Call Queueing . 20
5.2.5 Policy Routing . 21
5.3 Emergency Call Routing Function (ECRF) . 22
5.3.1 Overview . 22
5.3.2 Mandatory Interfaces . 22
5.3.3 Optional Interfaces . 23
5.3.4 Routing Query . 23
5.3.5 Service Boundary . 23
5.4 Public Safety Answering Point (PSAP). 24
5.4.1 Overview . 24
5.4.2 Mandatory Interfaces . 24
5.4.3 Optional Interfaces . 25
5.5 Location Information Server (LIS) . 26
5.5.1 Overview . 26
5.5.2 Mandatory Interfaces . 27
5.5.3 Optional Interfaces . 27
5.5.4 Location Representation . 27
5.6 Call Transfer Bridge (BRIDGE) . 28
5.6.1 Overview . 28
5.6.2 Mandatory Interfaces . 28
5.6.3 Optional Interfaces . 28
6 Interfaces . 29
6.1 Signalling . 29
6.1.1 SIP Transport (SIP-1) . 29
6.1.2 SIP Session (SIP-2) . 29
ETSI
4 ETSI TS 103 479 V1.1.1 (2019-12)
6.1.2.1 Overview . 29
6.1.2.2 SIP Methods . 30
6.1.2.3 Required SIP Headers . 33
6.1.2.4 Accepted SIP Headers . 34
6.1.2.5 Resource Priority . 34
6.1.2.6 History-Info and Reason . 35
6.1.2.7 Call-Info . 35
6.1.2.8 SIP Message Bodies . 36
6.1.2.9 SIP Element Overload . 36
6.1.2.10 Test Call . 36
6.1.3 SIP Registration (SIP-3) . 37
6.1.3.1 Overview . 37
6.1.3.2 SIP Methods . 37
6.1.3.3 Required SIP Headers . 37
6.2 Web Services . 37
6.2.1 Dequeue Registration (HTTP-1) . 37
6.2.1.1 Overview . 37
6.2.1.2 Parameter . 38
6.2.2 Bad Actor (HTTP-2) . 38
6.2.2.1 Overview . 38
6.2.2.2 Parameter . 38
6.3 Event Notification . 39
6.3.1 Queue State (SIP-E1) . 39
6.3.1.1 Overview . 39
6.3.1.2 Parameter . 40
6.3.2 Abandoned Call (SIP-E2) . 40
6.3.2.1 Overview . 40
6.3.2.2 Parameter . 41
6.3.3 Security Posture (SIP-E3) . 41
6.3.3.1 Overview . 41
6.3.3.2 Parameter . 42
6.3.4 Element State (SIP-E4) . 42
6.3.4.1 Overview . 42
6.3.4.2 Parameter . 43
6.3.5 Service State (SIP-E5) . 43
6.3.5.1 Overview . 43
6.3.5.2 Parameter . 44
6.4 Mapping Services . 45
6.4.1 Find Service (LOST-1) . 45
6.4.1.1 Overview . 45
6.4.1.2 findService Request . 45
6.4.1.3 findService Response . 46
6.4.2 Service Boundary (LOST-2) . 47
6.4.2.1 Overview . 47
6.4.2.2 getServiceBoundary Request . 47
6.4.2.3 getServiceBoundary Response . 47
6.4.3 List Services (LOST-3) . 47
6.4.3.1 Overview . 47
6.4.3.2 listServices Request . 47
6.4.3.3 listServices Response . 47
6.4.4 List Services by Location (LOST-4) . 47
6.4.4.1 Overview . 47
6.4.4.2 listServicesByLocation Request . 48
6.4.4.3 listServicesByLocation Response . 48
6.4.5 Error Responses . 48
6.5 Location Services . 49
6.5.1 HTTP Enabled Location Delivery (HELD-1) . 49
6.5.1.1 Overview . 49
6.5.1.2 Location Request . 49
6.5.1.3 Location Response . 49
6.5.1.4 Error Responses . 49
6.5.2 Location Dereference (HELD-2) . 49
ETSI
5 ETSI TS 103 479 V1.1.1 (2019-12)
6.5.3 Location URI (HELD-3) . 49
6.5.3.1 Overview . 49
6.5.3.2 Subscription . 49
6.5.3.3 Notification . 49
6.6 Media . 50
6.6.1 RTP Transport (RTP-1) . 50
6.6.2 RTP Types (RTP-2) . 50
6.6.2.1 General . 50
6.6.2.2 Audio . 50
6.6.2.3 Video . 50
6.6.2.4 Real-time Text . 50
6.7 Instant Messaging (IM-1) . 50
6.8 Common Alerting Protocol (CAP-1) . 51
Annex A (normative): JSON Schema . 52
A.1 QueueState . 52
A.2 AbandonedCall . 52
A.3 SecurityPosture . 53
A.4 ElementState . 53
A.5 ServiceState . 53
A.6 Dequeue Registration Request . 54
A.7 Dequeue Registration Response . 55
A.8 BadActor Request . 55
A.9 BadActor Response . 55
Annex B (informative): Organizational Descriptions . 56
B.0 General . 56
B.1 Certificate Authority. 56
B.2 National, and Regional Authorities . 56
B.3 Public Safety Computer Emergency Response Team (CERT) . 56
B.4 ETSI Protocol Naming and Numbering Service (PNNS) . 56
B.5 Emergency Call Service Authorities . 56
Annex C (informative): Parameter Registries . 58
C.0 General . 58
C.1 queueState Registry . 58
C.1.1 General . 58
C.1.2 Name . 58
C.1.3 Information required to create a new value . 58
C.1.4 Management Policy . 58
C.1.5 Content . 58
C.1.6 Initial Values . 58
C.2 securityPosture Registry . 59
C.2.0 General . 59
C.2.1 Name . 59
C.2.2 Information required to create a new value . 59
C.2.3 Management Policy . 59
C.2.4 Content . 59
C.2.5 Initial Values . 59
C.3 elementState Registry . 59
ETSI
6 ETSI TS 103 479 V1.1.1 (2019-12)
C.3.0 General . 59
C.3.1 Name . 59
C.3.2 Information required to create a new value . 59
C.3.3 Management Policy . 60
C.3.4 Content . 60
C.3.5 Initial Values . 60
C.4 serviceState Registry . 60
C.4.0 General . 60
C.4.1 Name . 60
C.4.2 Information required to create a new value . 60
C.4.3 Management Policy . 60
C.4.4 Content . 60
C.4.5 Initial Values . 60
Annex D (informative): Change History . 61
History . 62

ETSI
7 ETSI TS 103 479 V1.1.1 (2019-12)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (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 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 property 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 Technical Specification (TS) has been produced by ETSI Special Committee Emergency Communications
(EMTEL).
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 (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Executive summary
The core elements for network independent access to emergency services provide facilities that support centralized
mapping and routing functions for current and future emergency communications and operational requirements. The
baseline is a network with the functional elements that comprise security measures and the routing capabilities being
necessary to forward a call received at any concentration point based on the caller's location to the responsible
emergency call centre. In addition, other functional elements and necessary protocols and procedures enabling
interoperable and secure implementations are specified to allow multimedia communications as they evolve.
Introduction
At present, an emergency services infrastructure is based on straightforward technical building blocks and a few
legal/regulatory aspects. Technical elements, typically part of an incumbent telephone service provider, ensure that
emergency calls are routed to the most appropriate PSAP. Such routing is based on static information at the local
telephone exchange that provides a mapping between the location of a calling line and the PSAP, or for a mobile call,
between the location of the mobile network cell coverage and the PSAP. The mapping information itself is most often
managed by the national regulator, and typically, mapping information is represented by dialling code/area code/cell
identifier and a table that maps those codes to PSAPs, which are identified by unlisted and often un-dialable numbers.
ETSI
8 ETSI TS 103 479 V1.1.1 (2019-12)
However, the existing, legacy emergency services infrastructure is not designed in a way that enables interaction with
enhanced services, or that current and future communications and operational requirements will be met. Simply put, the
emergency services infrastructure has not kept up with technology, thus, is not able to provide the level of service that
citizens expect. Hence, new technologies with a new architecture are introduced as core elements for network
independent access to emergency services. These elements enable citizens/individuals to contact emergency services in
different ways, using the same types of technology as those they use to communicate every day. It also makes possible
that PSAPs receive more and better information about emergencies of all magnitudes and improves interoperability
between emergency services.
ETSI
9 ETSI TS 103 479 V1.1.1 (2019-12)
1 Scope
The purpose of the present document is to describe the architecture, the core elements and corresponding technical
interfaces for network independent access to emergency services. Elements are: Border Control Function (BCF),
Emergency Service Routing Proxy (ESRP), Emergency Call Routing Function (ECRF), Public Safety Answering Point
(PSAP), the Location Information Server (LIS), and the Call Transfer Bridge (BRIDGE).
The described architecture is currently named Next Generation 112 architecture.
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 references, 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
https://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.
[1] ETSI ES 203 178: "Functional architecture to support European requirements on emergency caller
location determination and transport".
[2] ETSI ES 203 283: "Protocol specifications for Emergency Service Caller Location determination
and transport".
[3] ETSI TS 103 625: "Emergency Communications (EMTEL); Transporting Handset Location to
PSAPs for Emergency Calls - Advanced Mobile Location".
[4] IETF RFC 2046 (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part
Two: Media Types", N. Freed and N. Borenstein.
[5] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol", J. Rosenberg, H. Schulzrinne,
G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley and E. Schooler.
[6] IETF RFC 3262 (June 2002): "Reliability of Provisional Responses in Session Initiation Protocol
(SIP)", J. Rosenberg and H. Schulzrinne.
[7] IETF RFC 3264 (June 2002): "An Offer/Answer Model with Session Description Protocol (SDP)",
J. Rosenberg and H. Schulzrinne.
[8] IETF RFC 3311 (September 2002): "The Session Initiation Protocol (SIP) UPDATE Method",
J. Rosenberg.
[9] IETF RFC 3325 (November 2002): "Private Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity Within Trusted Networks", C. Jennings, J. Peterson and M. Watson.
[10] IETF RFC 3326 (December 2002): "The Reason Header Field for the Session Initiation Protocol
(SIP)", D. Oran and G. Camarillo.
[11] IETF RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant
Messaging", B. Campbell, J. Rosenberg, H. Schulzrinne, C. Huitema and D. Gurle.
[12] IETF RFC 3515 (April 2003): "The Session Initiation Protocol (SIP) Refer Method", R. Sparks.
ETSI
10 ETSI TS 103 479 V1.1.1 (2019-12)
[13] IETF RFC 3550 (July 2003): "RTP: A Transport Protocol for Real-Time Applications",
H. Schulzrinne, S. Casner, R. Frederick and V. Jacobson.
[14] IETF RFC 3558 (July 2003): "RTP Payload Format for Enhanced Variable Rate Codecs (EVRC)
and Selectable Mode Vocoders (SMV)", A. Li.
[15] IETF RFC 3711 (March 2004): "The Secure Real-time Transport Protocol (SRTP)", M. Baugher,
D. McGrew, M. Naslund, E. Carrara and K. Norrman.
[16] IETF RFC 3841 (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)",
J. Rosenberg, H. Schulzrinne and P. Kyzivat.
[17] IETF RFC 3856 (August 2004): "A Presence Event Package for the Session Initiation Protocol
(SIP)", J. Rosenberg.
[18] IETF RFC 3891 (September 2004): "The Session Initiation Protocol (SIP) "Replaces" Header",
R. Mahy, B. Biggs, and R. Dean.
[19] IETF RFC 3911 (October 2004): "The Session Initiation Protocol (SIP) "Join" Header", R. Mahy
and D. Petrie.
[20] IETF RFC 3994 (January 2005): "Indication of Message Composition for Instant Messaging",
H. Schulzrinne.
[21] IETF RFC 4103 (June 2005): "RTP Payload for Text Conversation", G. Hellstrom and P. Jones.
[22] IETF RFC 4119 (December 2005): "A Presence-Based GEOPRIV Location Object Format",
J. Peterson.
[23] IETF RFC 7044 (February 2014)): "An Extension to the Session Initiation Protocol (SIP) for
Request History Information", M. Barnes, F. Audet, S. Schubert, J. van Elburg, C. Holmberg.
[24] IETF RFC 4412 (February 2006): "Communications Resource Priority for the Session Initiation
Protocol (SIP)", H. Schulzrinne and J. Polk.
[25] IETF RFC 4566 (July 2006): "SDP: Session Description Protocol", M. Handley, V. Jacobson and
C. Perkins.
[26] IETF RFC 4568 (July 2006): "Session Description Protocol (SDP) Security Descriptions for
Media Streams", F. Andreasen, M. Baugher and D. Wing.
[27] IETF RFC 4579 (August 2006): "Session Initiation Protocol (SIP) Call Control - Conferencing for
User Agents", A. Johnston and O. Levin.
[28] IETF RFC 4585 (July 2006): "Extended RTP Profile for Real-time Transport Control Protocol
(RTCP)-Based Feedback (RTP/AVPF)", J. Ott, S. Wenger, N. Sato, C. Burmeister and J. Rey.
[29] IETF RFC 4660 (September 2006): "Functional Description of Event Notification Filtering",
H. Khartabil, E. Leppanen, M. Lonnfors and J. Costa-Requena.
[30] IETF RFC 4661 (September 2006): "An Extensible Markup Language (XML)-Based Format for
Event Notification Filtering", H. Khartabil, E. Leppanen, M. Lonnfors and J. Costa-Requena.
[31] IETF RFC 4788 (January 2007): "Enhancements to RTP Payload Formats for EVRC Family
Codecs", Q. Xie, and R. Kapoor.
[32] IETF RFC 4975 (September 2007): "The Message Session Relay Protocol (MSRP)", B. Campbell,
R. Mahy and C. Jennings.
[33] IETF RFC 4976 (September 2007): "Relay Extensions for the Message Session Relay Protocol
(MSRP)", C. Jennings, R. Mahy and A. B. Roach.
[34] IETF RFC 5031 (January 2008): "A Uniform Resource Name (URN) for Emergency and Other
Well-Known Services", H. Schulzrinne.
ETSI
11 ETSI TS 103 479 V1.1.1 (2019-12)
[35] IETF RFC 5104 (February 2008): "Codec Control Messages in the RTP Audio-Visual Profile with
Feedback (AVPF)", S. Wenger, U. Chandra, M. Westerlund and B. Burman.
[36] IETF RFC 5168 (March 2008): "XML Schema for Media Control", O. Levin, R. Even and
P. Hagendorf.
[37] IETF RFC 5188 (February 2008): "RTP Payload Format for the Enhanced Variable Rate
Wideband Codec (EVRC-WB) and the Media Subtype Updates for EVRC-B Codec", H Desineni
and Q. Xie.
[38] IETF RFC 5194 (June 2008): "Framework for Real-Time Text Over IP Using the Session
Initiation Protocol (SIP)", A. vanWijk and G. Gybels.
[39] IETF RFC 5222 (August 2008): "LoST: A Location-to-Service Translation Protocol", T. Hardie,
A. Newton and H. Schulzrinne and H. Tschofenig.
[40] IETF RFC 5223 (August 2008): "Discovering Location-to-Service Translation (LoST) Servers
Using the Dynamic Host Configuration Protocol (DHCP)", H. Schulzrinne, J. Polk and
H. Tschofenig.
[41] IETF RFC 5411 (February 2009): "A Hitchhiker's Guide to the Session Initiation Protocol (SIP)",
J. Rosenberg.
[42] IETF RFC 5621 (September 2009): "Message Body Handling in the Session Initiation Protocol
(SIP)", G. Camarillo.
[43] IETF RFC 5627 (October 2009): "Obtaining and Using Globally Routable User Agent URIs
(GRUUs) in the Session Initiation Protocol (SIP)", J. Rosenberg.
[44] IETF RFC 5808 (May 2010): "Requirements for a Location-by-Reference Mechanism",
R. Marshall.
[45] IETF RFC 5985 (September 2010): "HTTP-Enabled Location Delivery (HELD)", M. Barnes.
[46] IETF RFC 6086 (January 2011): "Session Initiation Protocol (SIP) INFO Method and Package
Framework", C. Holmberg, E. Burger and H. Kaplan.
[47] IETF RFC 6155 (March 2011): "Use of Device Identity in HTTP-Enabled Location Delivery
(HELD)", J. Winterbottom, H. Tschofenig and R. Barnes.
[48] IETF RFC 6442 (December 2011): "Location Conveyance for the Session Initiation Protocol",
J. Polk, B. Rosen and J. Peterson.
[49] IETF RFC 6446 (January 2012): "Session Initiation Protocol (SIP) Event Notification Extension
for Notification Rate Control", A. Niemi, K. Kiss and S. Loreto.
[50] IETF RFC 6447 (January 2012): "Filtering Location Notifications in the Session Initiation
Protocol (SIP)", R. Mahy, B. Rosen and H. Tschofenig.
[51] IETF RFC 6665 (July 2012): "SIP-Specific Event Notification", A. B. Roach.
[52] IETF RFC 6753 (October 2012): "A Location Dereference Protocol Using HTTP-Enabled
Location Delivery (HELD)", J. Winterbottom, H. Tschofenig, H. Schulzrinne and M. Thomson.
[53] IETF RFC 6849 (February 2013): "An Extension to the Session Description Protocol (SDP) and
Real-time Transport Protocol (RTP) for Media Loopback", H. Kaplan, K. Hedayat, N. Venna,
P. Jones and N. Stratton.
[54] IETF RFC 6881 (March 2013): "Best Current Practice for Communications Services in Support of
Emergency Calling", B. Rosen and J. Polk.
[55] IETF RFC 6884 (March 2013): "RTP Payload Format for the En
...