1、 ETSI TR 103 201 V1.1.1 (2016-03) Emergency Communications (EMTEL); Total Conversation for emergency communications; implementation guidelines TECHNICAL REPORT ETSI ETSI TR 103 201 V1.1.1 (2016-03) 2 Reference DTR/EMTEL-00029 Keywords accessibility, disability, emergency, IMS, IP, real-time text, SI
2、P, total conversation 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can
3、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
4、 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 b
5、e 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
6、.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 with
7、out 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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Me
8、mbers. 3GPPTM 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 ETSI TR 103 201 V1.1.1 (2016-03) 3 Contents Intellectual Property Rights 7g3Foreword
9、 . 7g3Modal verbs terminology 7g3Introduction 7g31 Scope 8g32 References 8g32.1 Normative references . 8g32.2 Informative references 8g33 Definitions and abbreviations . 12g33.1 Definitions 12g33.2 Abbreviations . 13g34 Background 14g35 Existing requirements, recommendations, and assumptions 15g35.1
10、 General . 15g35.2 Summary of existing requirements . 15g35.3 Study and Analysis Assumptions . 16g35.3.1 General 16g35.3.2 Assumptions related to Total Conversation for Emergency Communication . 16g35.3.3 Assumptions about the PSAP and Relay node networks 17g35.3.4 Assumptions about the Total Conver
11、sation user terminal and access network . 17g35.3.5 Assumptions on the routing of Total Conversation for emergency communication calls 17g36 Architecture principles . 17g36.1 General . 17g36.2 Functional Architecture 17g36.3 Call scenarios . 19g36.3.1 General 19g36.3.2 Baseline session (without any
12、assisting service) . 19g36.3.3 Routing based on media capability of PSAP 19g36.3.4 Routing based on language / modality 19g36.3.5 Routing via an assisting service 20g36.3.6 Conferencing with third party including assisting relay services 20g36.3.7 Transfer of session from PSAP . 20g36.3.8 Transfer o
13、f session to more appropriate Total Conversation user terminal 21g36.3.9 Call-back . 21g36.4 Implementation technologies 22g36.4.1 General 22g36.4.2 IETF SIP . 22g36.4.3 IMS . 22g36.4.4 Web based technologies 22g36.4.5 PSTN 22g36.5 Supported functions in Total Conversation for Emergency Communicatio
14、ns . 22g36.5.1 General 22g36.5.2 Identification of the Total Conversation emergency session 23g36.5.3 Naming and addressing . 23g36.5.3.1 Caller / Originator Identity 23g36.5.3.2 Relay Service identification and addressing . 23g36.5.4 Language considerations . 24g36.5.5 Location and routing . 24g36.
15、5.5.1 Location information . 24g36.5.5.2 Routing information 25g36.5.6 Assisting services 25g36.5.7 Security and Privacy . 26g36.5.8 Transfer of session to another Total Conversation user terminal 27g3ETSI ETSI TR 103 201 V1.1.1 (2016-03) 4 6.5.9 Testing 27g36.5.10 Media 27g37 Key Issues for impleme
16、nting Total Conversation for Emergency services . 28g37.1 General . 28g37.2 Identification and invocation of assisting relay service 28g37.2.1 General 28g37.2.2 Issue #1: Invoking the conference for inclusion of an assisting relay service 28g37.2.2.1 General 28g37.2.2.2 Solution #1: Conference invoc
17、ation by the Total Conversation terminal . 29g37.2.2.2.1 Description 29g37.2.2.2.2 Evaluation 29g37.2.2.3 Solution #2: Conference invocation initiated in the Access Network . 30g37.2.2.3.1 Description 30g37.2.2.3.2 Evaluation 31g37.2.2.4 Solution #3: Conference invocation in the ESInet 32g37.2.2.4.1
18、 Description 32g37.2.2.4.2 Evaluation 32g37.2.3 Issue #2: Indicating/identifying the communication needs of the Total Conversation user 33g37.2.3.1 General 33g37.2.3.2 Solution #1: Preferred Language / Modality indicated by Total Conversation terminal in Accept-Contact header . 33g37.2.3.2.1 Descrip
19、tion 33g37.2.3.2.2 Evaluation 34g37.2.3.3 Solution #2: Preferred Language / Modality indicated by Total Conversation terminal in SDP language attribute 34g37.2.3.3.1 Description 34g37.2.3.3.2 Evaluation 35g37.2.3.4 Solution #3: Preferred Language / Modality tag added by Application Service Provider
20、35g37.2.3.4.1 Description 35g37.2.3.4.2 Evaluation 36g37.2.3.5 Solution #4: Use of Additional Data to indicate communication needs and / or a specific relay service . 36g37.2.4 Issue #3: Emergency session handling at the assisting relay service 37g37.2.4.1 General 37g37.2.4.2 Solution #1: Use of “SI
21、P PSAP callback indicator“ 37g37.2.4.2.1 Description 37g37.2.4.2.2 Evaluation 37g37.2.4.3 Solution #2: Use of assisting relay service emergency specific URI 38g37.2.4.3.1 Description 38g37.2.4.3.2 Evaluation 38g37.2.4.4 Solution #3: Trusted relay services recognizing PSAP specific originating URIs 3
22、8g37.2.4.4.1 Description 38g37.2.4.4.2 Evaluation 38g37.2.4.5 Solution #4: include a SIP field in the call to use for assisting relay service invocation 38g37.2.4.5.1 Description 38g37.2.4.5.2 Evaluation 38g37.2.4.6 Solution #5: include a SIP priority tag in the call to the assisting relay service t
23、o indicate its emergency status . 39g37.2.4.6.1 Description 39g37.2.4.6.2 Evaluation 39g37.2.5 Issue #4: Obtaining the identity of a specific assisting service . 39g37.2.5.1 General 39g37.2.5.2 Solution #1: PSAP interrogation of a database . 39g37.2.5.2.1 Description 39g37.2.5.2.2 Evaluation 40g37.2
24、.5.3 Solution #2: Identity communicated by the Total Conversation user terminal . 40g37.2.5.3.1 Description 40g37.2.5.3.2 Evaluation 41g37.2.6 Issue #5: Total Conversation user default behaviour 41g37.3 Automatic translation . 42g37.3.1 General 42g3ETSI ETSI TR 103 201 V1.1.1 (2016-03) 5 7.3.2 Solut
25、ion #1: Automatic translation at the PSAP . 42g37.3.2.1 Description 42g37.3.2.2 Evaluation . 43g37.3.3 Solution #2: Automatic translation at the Total Conversation user terminal 43g37.3.3.1 Description 43g37.3.3.2 Evaluation . 44g37.4 Media 44g37.4.1 General 44g37.4.2 Video 45g37.4.3 Audio 45g37.4.4
26、 Real-time text 45g37.4.4.1 General 45g37.4.4.2 Multi-party handling of real-time text . 46g38 Recommendations 46g38.1 General . 46g38.2 Assisting services . 46g38.3 Roaming sessions routed via the home network. 48g38.4 Media 48g38.5 Security 50g39 Recommended updates and new specification work 50g3
27、9.1 Gap analysis and remedial actions . 50g39.1.1 Use of terms GTT and RTT in 3GPP specifications . 50g39.1.1.1 Description of issue . 50g39.1.1.2 Remedial action . 50g39.1.1.3 Status . 50g39.1.2 Order of payload types for real-time text in 3GPP specifications . 50g39.1.2.1 Description of issue . 50
28、g39.1.2.2 Remedial action . 51g39.1.2.3 Status . 51g39.1.3 Provision of feedback and comments on draft version ETSI ES 202 975 51g39.1.3.1 Description of issue . 51g39.1.3.2 Remedial action . 51g39.1.3.3 Status . 51g39.1.4 Inclusion of Total Conversation for emergency services as a regional requirem
29、ent. 51g39.1.4.1 Description of issue . 51g39.1.4.2 Remedial action . 52g39.1.4.3 Status . 52g39.2 New and revised specifications 52g39.2.1 General 52g39.2.2 3GPP/ETSI specifications . 52g39.2.2.1 Relay service interface for emergency communications . 52g39.2.2.2 Test Specifications for Total Conver
30、sation . 52g39.2.2.3 AT commands . 52g39.2.2.4 ETSI TS 101 470 . 52g39.2.3 IETF specifications . 52g39.2.3.1 Best practices in real-time text 52g39.2.4 EENA Specifications 53g39.2.4.1 SDP based routing . 53g39.3 Open issues . 53g39.3.1 Use of non-usual terminals . 53g39.3.2 Configuration of Total Co
31、nversation settings . 53g39.3.2.1 General 53g39.3.2.2 Setting by Application Service Provider . 53g39.3.2.3 Setting of the Total Conversation Terminal 53g39.3.3 Rapid captioning of speech . 54g310 Conclusions 54g3Annex A: Alternative solution for relay service identification and invocation 55g3A.1 G
32、eneral . 55g3ETSI ETSI TR 103 201 V1.1.1 (2016-03) 6 A.2 Hybrid solution rationale 55g3A.2.1 Sessions where the Total Conversation user terminal is IETF or IMS SIP registered . 55g3A.2.1.1 Sessions where the Total Conversation user terminal is not roaming . 55g3A.2.1.2 Sessions where the Total Conve
33、rsation user terminal is roaming . 55g3A.2.2 Sessions where the Total Conversation user terminal is IMS emergency registered . 56g3A.2.3 Example call-flow 56g3Annex B: Outstanding issues from ETSI TS 101 470 (V1.1.1) . 59g3B.1 General . 59g3B.2 Analysis of issues regarding ETSI TS 101 470 (V1.1.1) .
34、 59g3B.2.1 Text related to clause “5.4.2.1 Relay service“ 59g3B.2.2 Text related to clause “5.4.2.1.2 IMS support“ . 59g3B.2.3 Text related to clause “5.4.3 Multi-party multi-media call“ . 59g3B.2.4 Text related to clause “5.4.4 Transfer and Forward supplementary services“ 59g3B.2.5 Text related to
35、clause “5.11.1 Basic SIP support“ 59g3B.2.6 Text related to clause “5.17.1 Basic SIP support“ 60g3Annex C: Existing IMS requirements for support of Total Conversation 61g3C.1 General . 61g3C.2 Requirements from ETSI TS 122 101 61g3C.2.1 General . 61g3C.2.2 Requirements in clause 7.2 of ETSI TS 122 1
36、01 61g3C.2.3 Requirements in clause 7.2.4 of ETSI TS 122 101 . 61g3C.2.4 Requirements in clause 10.4 of ETSI TS 122 101 62g3C.3 Requirements from ETSI TS 122 173 63g3C.4 Requirements from ETSI TS 126 114 64g3C.5 Requirements from ETSI TS 122 228 64g3C.6 Requirements from ETSI TS 123 167 64g3Annex D:
37、 Current situation in Europe for Total Conversation and emergency service access for persons with disabilities 66g3D.1 General . 66g3D.2 Total Conversation, RTT and subsets for everyday use . 66g3D.3 Relay service availability . 66g3D.4 Emergency service access 66g3D.5 Conclusion 67g3History 68g3ETS
38、I ETSI TR 103 201 V1.1.1 (2016-03) 7 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 ET
39、SI 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
40、 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 Technical
41、Report (TR) 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 ET
42、SI 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. Introduction The present document contains recommendations and guidelines on the implementation of Total Conversation for emergency servi
43、ce access and provision. Total Conversation enables conversation in real-time text, video and audio. Subsets are also considered including the combination of real-time text and audio that forms the text telephony service. Total Conversation services and terminals are deployed in some European countr
44、ies, and have been adopted by people with disabilities who, for example, need video for sign language, or real-time text for a text based conversation or as complement to a voice conversation. The use of Total Conversation for Emergency Communications would enable and/or improve access to emergency
45、services by people with disabilities. However the few deployments of Total Conversation for Emergency Communications that exist, are implemented in different ways in different countries, and are not implemented according to the latest development of ETSI, IETF and 3GPP standards for Emergency Commun
46、ications. This non-harmonized deployment means that there are no interoperable solutions for emergency service access across the EU countries, which is contrary to EU policy. The present document is intended to assist ETSI SC EMTEL to coordinate with other standards bodies and relevant stakeholders
47、so that the recommendations of ETSI TS 101 470 i.2 and ETSI TR 103 170 i.3 can be implemented. It can also be used to assess if Total Conversation requirements are fulfilled by other necessary standards, and to ensure that there are no contradictions. ETSI ETSI TR 103 201 V1.1.1 (2016-03) 8 1 Scope
48、The present document: Assesses the support of Total Conversation for emergency communications by existing specifications, in particular those from 3GPP and IETF. Identifies any changes that might be needed to those specifications to support Total Conversation for emergency communications. Provides g
49、uidance for developers and PSAPs planning to implement Total Conversation for emergency communications, and for users of the Total Conversation service. The present document covers emergency calls with the full media set of Total Conversation as well as subsets of the media, except voice calls in which no assisting service is needed. Although the focus of the present document is Total Conversation for emergency communications, no Total Conversation user can be expected to use Total Conversation only for contacting emergency services. Therefore and where applicable, s
