ETSI TR 103 201 V1.1.1 (2016-03)

Emergency Communications (EMTEL); Total Conversation for emergency communications; implementation guidelines

DTR/EMTEL-00029

General Information

• Status: Published
• Publication Date: 13-Mar-2016
• Technical Committee: EMTEL - Emergency Communications
• Current Stage: 12 - Completion
• Due Date: 15-Mar-2016
• Completion Date: 14-Mar-2016

Standards Content (Sample)

ETSI TR 103 201 V1.1.1 (2016-03)






TECHNICAL REPORT
Emergency Communications (EMTEL);
Total Conversation for emergency communications;
implementation guidelines

---------------------- Page: 1 ----------------------
2 ETSI TR 103 201 V1.1.1 (2016-03)



Reference
DTR/EMTEL-00029
Keywords
accessibility, disability, emergency, IMS, IP, real-
time text, SIP, total conversation

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 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
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.

© European Telecommunications Standards Institute 2016.
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.
TM
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: 2 ----------------------
3 ETSI TR 103 201 V1.1.1 (2016-03)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
Introduction . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 8
3 Definitions and abbreviations . 12
3.1 Definitions . 12
3.2 Abbreviations . 13
4 Background . 14
5 Existing requirements, recommendations, and assumptions . 15
5.1 General . 15
5.2 Summary of existing requirements . 15
5.3 Study and Analysis Assumptions . 16
5.3.1 General . 16
5.3.2 Assumptions related to Total Conversation for Emergency Communication . 16
5.3.3 Assumptions about the PSAP and Relay node networks . 17
5.3.4 Assumptions about the Total Conversation user terminal and access network . 17
5.3.5 Assumptions on the routing of Total Conversation for emergency communication calls . 17
6 Architecture principles . 17
6.1 General . 17
6.2 Functional Architecture . 17
6.3 Call scenarios . 19
6.3.1 General . 19
6.3.2 Baseline session (without any assisting service) . 19
6.3.3 Routing based on media capability of PSAP . 19
6.3.4 Routing based on language / modality . 19
6.3.5 Routing via an assisting service . 20
6.3.6 Conferencing with third party including assisting relay services. 20
6.3.7 Transfer of session from PSAP . 20
6.3.8 Transfer of session to more appropriate Total Conversation user terminal . 21
6.3.9 Call-back . 21
6.4 Implementation technologies. 22
6.4.1 General . 22
6.4.2 IETF SIP . 22
6.4.3 IMS . 22
6.4.4 Web based technologies . 22
6.4.5 PSTN . 22
6.5 Supported functions in Total Conversation for Emergency Communications . 22
6.5.1 General . 22
6.5.2 Identification of the Total Conversation emergency session . 23
6.5.3 Naming and addressing . 23
6.5.3.1 Caller / Originator Identity . 23
6.5.3.2 Relay Service identification and addressing . 23
6.5.4 Language considerations . 24
6.5.5 Location and routing . 24
6.5.5.1 Location information . 24
6.5.5.2 Routing information . 25
6.5.6 Assisting services . 25
6.5.7 Security and Privacy . 26
6.5.8 Transfer of session to another Total Conversation user terminal . 27
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TR 103 201 V1.1.1 (2016-03)
6.5.9 Testing . 27
6.5.10 Media . 27
7 Key Issues for implementing Total Conversation for Emergency services . 28
7.1 General . 28
7.2 Identification and invocation of assisting relay service . 28
7.2.1 General . 28
7.2.2 Issue #1: Invoking the conference for inclusion of an assisting relay service . 28
7.2.2.1 General . 28
7.2.2.2 Solution #1: Conference invocation by the Total Conversation terminal . 29
7.2.2.2.1 Description . 29
7.2.2.2.2 Evaluation . 29
7.2.2.3 Solution #2: Conference invocation initiated in the Access Network . 30
7.2.2.3.1 Description . 30
7.2.2.3.2 Evaluation . 31
7.2.2.4 Solution #3: Conference invocation in the ESInet . 32
7.2.2.4.1 Description . 32
7.2.2.4.2 Evaluation . 32
7.2.3 Issue #2: Indicating/identifying the communication needs of the Total Conversation user. 33
7.2.3.1 General . 33
7.2.3.2 Solution #1: Preferred Language / Modality indicated by Total Conversation terminal in Accept-
Contact header . 33
7.2.3.2.1 Description . 33
7.2.3.2.2 Evaluation . 34
7.2.3.3 Solution #2: Preferred Language / Modality indicated by Total Conversation terminal in SDP
language attribute . 34
7.2.3.3.1 Description . 34
7.2.3.3.2 Evaluation . 35
7.2.3.4 Solution #3: Preferred Language / Modality tag added by Application Service Provider . 35
7.2.3.4.1 Description . 35
7.2.3.4.2 Evaluation . 36
7.2.3.5 Solution #4: Use of Additional Data to indicate communication needs and / or a specific relay
service . 36
7.2.4 Issue #3: Emergency session handling at the assisting relay service . 37
7.2.4.1 General . 37
7.2.4.2 Solution #1: Use of "SIP PSAP callback indicator" . 37
7.2.4.2.1 Description . 37
7.2.4.2.2 Evaluation . 37
7.2.4.3 Solution #2: Use of assisting relay service emergency specific URI . 38
7.2.4.3.1 Description . 38
7.2.4.3.2 Evaluation . 38
7.2.4.4 Solution #3: Trusted relay services recognizing PSAP specific originating URIs . 38
7.2.4.4.1 Description . 38
7.2.4.4.2 Evaluation . 38
7.2.4.5 Solution #4: include a SIP field in the call to use for assisting relay service invocation . 38
7.2.4.5.1 Description . 38
7.2.4.5.2 Evaluation . 38
7.2.4.6 Solution #5: include a SIP priority tag in the call to the assisting relay service to indicate its
emergency status . 39
7.2.4.6.1 Description . 39
7.2.4.6.2 Evaluation . 39
7.2.5 Issue #4: Obtaining the identity of a specific assisting service . 39
7.2.5.1 General . 39
7.2.5.2 Solution #1: PSAP interrogation of a database . 39
7.2.5.2.1 Description . 39
7.2.5.2.2 Evaluation . 40
7.2.5.3 Solution #2: Identity communicated by the Total Conversation user terminal . 40
7.2.5.3.1 Description . 40
7.2.5.3.2 Evaluation . 41
7.2.6 Issue #5: Total Conversation user default behaviour . 41
7.3 Automatic translation . 42
7.3.1 General . 42
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TR 103 201 V1.1.1 (2016-03)
7.3.2 Solution #1: Automatic translation at the PSAP . 42
7.3.2.1 Description . 42
7.3.2.2 Evaluation . 43
7.3.3 Solution #2: Automatic translation at the Total Conversation user terminal . 43
7.3.3.1 Description . 43
7.3.3.2 Evaluation . 44
7.4 Media . 44
7.4.1 General . 44
7.4.2 Video . 45
7.4.3 Audio . 45
7.4.4 Real-time text . 45
7.4.4.1 General . 45
7.4.4.2 Multi-party handling of real-time text . 46
8 Recommendations . 46
8.1 General . 46
8.2 Assisting services . 46
8.3 Roaming sessions routed via the home network. 48
8.4 Media . 48
8.5 Security . 50
9 Recommended updates and new specification work . 50
9.1 Gap analysis and remedial actions . 50
9.1.1 Use of terms GTT and RTT in 3GPP specifications . 50
9.1.1.1 Description of issue . 50
9.1.1.2 Remedial action . 50
9.1.1.3 Status . 50
9.1.2 Order of payload types for real-time text in 3GPP specifications . 50
9.1.2.1 Description of issue . 50
9.1.2.2 Remedial action . 51
9.1.2.3 Status . 51
9.1.3 Provision of feedback and comments on draft version ETSI ES 202 975 . 51
9.1.3.1 Description of issue . 51
9.1.3.2 Remedial action . 51
9.1.3.3 Status . 51
9.1.4 Inclusion of Total Conversation for emergency services as a regional requirement. 51
9.1.4.1 Description of issue . 51
9.1.4.2 Remedial action . 52
9.1.4.3 Status . 52
9.2 New and revised specifications . 52
9.2.1 General . 52
9.2.2 3GPP/ETSI specifications . 52
9.2.2.1 Relay service interface for emergency communications . 52
9.2.2.2 Test Specifications for Total Conversation . 52
9.2.2.3 AT commands . 52
9.2.2.4 ETSI TS 101 470 . 52
9.2.3 IETF specifications . 52
9.2.3.1 Best practices in real-time text . 52
9.2.4 EENA Specifications . 53
9.2.4.1 SDP based routing . 53
9.3 Open issues . 53
9.3.1 Use of non-usual terminals . 53
9.3.2 Configuration of Total Conversation settings . 53
9.3.2.1 General . 53
9.3.2.2 Setting by Application Service Provider . 53
9.3.2.3 Setting of the Total Conversation Terminal . 53
9.3.3 Rapid captioning of speech . 54
10 Conclusions . 54
Annex A: Alternative solution for relay service identification and invocation . 55
A.1 General . 55
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TR 103 201 V1.1.1 (2016-03)
A.2 Hybrid solution rationale . 55
A.2.1 Sessions where the Total Conversation user terminal is IETF or IMS SIP registered . 55
A.2.1.1 Sessions where the Total Conversation user terminal is not roaming . 55
A.2.1.2 Sessions where the
...