EMTEL; Study of use cases and communications involving IoT devices in provision of emergency situations

DTR/EMTEL-00041

General Information

Status
Published
Publication Date
30-Jun-2019
Current Stage
12 - Completion
Due Date
17-Jul-2019
Completion Date
01-Jul-2019
Ref Project

Buy Standard

Standard
ETSI TR 103 582 V1.1.1 (2019-07) - EMTEL; Study of use cases and communications involving IoT devices in provision of emergency situations
English language
95 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TR 103 582 V1.1.1 (2019-07)






TECHNICAL REPORT
EMTEL;
Study of use cases and communications involving
IoT devices in provision of emergency situations

---------------------- Page: 1 ----------------------
2 ETSI TR 103 582 V1.1.1 (2019-07)



Reference
DTR/EMTEL-00041
Keywords
emergency, emergency services, IoT, public
safety, security
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 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.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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

---------------------- Page: 2 ----------------------
3 ETSI TR 103 582 V1.1.1 (2019-07)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
Introduction . 7
1 Scope . 9
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 14
3.1 Terms . 14
3.2 Symbols . 14
3.3 Abbreviations . 14
4 General Overview. 17
5 State of the art for communications relevant to emergency situations involving IoT devices . 18
5.1 General overview . 18
5.2 Emergency-related standardization state of the art . 19
5.2.1 ETSI SC EMTEL standardization . 19
5.2.1.1 General . 19
5.2.1.2 Summary of ETSI SC EMTEL Requirements . 19
5.2.1.3 Advanced Mobile Location for emergency calls. 21
5.2.1.4 Conclusion . 21
5.2.2 ETSI SES/SatEC standardization . 22
5.2.3 ETSI TCCE standardization . 22
5.2.4 3GPP standardization . 23
5.2.4.1 General . 23
5.2.4.2 Conclusion . 24
5.2.5 IETF standardization. 24
5.2.6 ITU standardization . 25
5.2.7 CEN and 3GPP standardization for the eCall . 25
5.3 IoT-related standardization state of the art . 26
5.3.1 3GPP Standardization . 26
5.3.1.1 General . 26
5.3.1.2 Conclusion . 26
5.3.2 IETF standardization. 27
5.3.2.1 General . 27
5.3.2.2 Conclusion . 27
5.3.3 ITU-T standardization . 28
5.3.3.1 General . 28
5.3.3.2 Conclusion . 29
5.3.4 IEEE standardization . 29
5.3.4.1 General . 29
5.3.4.2 IEEE 802.15.1 Bluetooth® . 29
5.3.4.3 IEEE 802.15.3 High Rate WPAN . 30
5.3.4.4 IEEE 802.15.4 Low Rate WPAN . 30
5.3.4.5 IEEE 802.15.7 Visible Light Communication . 30
5.3.5 oneM2M standardization . 30
5.3.5.1 General . 30
5.3.5.2 Conclusion . 30
5.4 Communication networks deployed . 31
5.4.1 Networks related to emergency communications domains . 31
5.4.1.1 Emergency Calling . 31
5.4.1.2 Mission critical communications . 31
5.4.1.3 Public Warning System . 34
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TR 103 582 V1.1.1 (2019-07)
5.4.1.4 Conclusion . 34
5.4.2 IoT networks from mobile telecom operators . 34
5.4.2.1 General . 34
5.4.2.2 LTE-M (Long Term Evolution for Machines) . 35
5.4.2.3 NB-IoT (Narrowband Internet of Things) . 35
5.4.2.4 Conclusion . 35
5.4.3 Additional long-range IoT networks . 35
5.4.3.1 General . 35
5.4.3.2 Sigfox . 35
5.4.3.3 LoRaWAN . 36
5.4.4 Other IoT short range networks . 36
5.4.4.1 General . 36
5.4.4.2 ZigBee . 36
5.4.4.3 Z-Wave . 37
5.4.4.4 EnOcean . 37
5.4.4.5 ANT/ANT+ . 37
5.5 Support of emergency by IoT sensors and platforms . 37
5.5.1 Overview of IoT landscape . 37
5.5.2 Overview of IoT service platforms . 39
5.5.3 Drones as special IoT devices . 40
5.5.4 Existing implementations and trials using IoT sensors for emergency situations . 41
5.5.4.1 Emergency calling . 41
5.5.4.2 Mission critical communications . 41
5.5.4.2.1 Based on PMR systems . 41
5.5.4.2.2 Proprietary solutions . 41
5.5.4.2.3 Research and trials . 41
5.5.4.3 Public Warning System . 42
5.6 Selection of use cases and existing requirements . 43
5.6.1 Emergency situation handling in oneM2M standard . 43
5.6.1.1 General . 43
5.6.1.2 oneM2M use case: Traffic Accident Information Collection . 43
5.6.1.3 oneM2M use case: Information Delivery Service in The Devastated Area . 44
5.6.1.4 Conclusion . 44
5.6.2 ETSI PPDR 2016 workshop . 45
5.7 Previous studies on IoT in emergency situations . 45
5.7.1 EENA . 45
5.7.2 White paper on technologies for mission critical IoT . 46
5.7.2.1 General . 46
5.7.2.2 Conclusion . 48
5.7.3 Experiments and Simulations . 48
5.7.3.1 NIST disaster simulation (Philadelphia, USA) . 48
5.7.3.2 Disaster-ready communication infrastructure (Coral Gables, Florida, USA) . 48
6 Use cases for emergency services involving communications with IoT devices . 48
6.1 Introduction . 48
6.2 EC1: Automatic direct emergency call from IoT device . 53
6.2.1 Emergency Domain . 53
6.2.2 Description . 53
6.2.3 Actors . 53
6.2.4 Pre-conditions . 53
6.2.5 Triggers . 53
6.2.6 Normal Flow . 54
6.2.7 Alternative flow . 54
6.2.8 Post-conditions . 54
6.2.9 High Level Illustration . 55
6.2.10 Potential points of failure putting safety at risk . 55
6.2.11 Potential means to prevent points of failure . 56
6.3 EC2: IoT device provides additional information to an emergency call . 56
6.3.1 Emergency Domain . 56
6.3.2 Description . 56
6.3.3 Actors . 57
6.3.4 Pre-conditions . 57
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TR 103 582 V1.1.1 (2019-07)
6.3.5 Triggers . 57
6.3.6 Normal Flow . 58
6.3.7 Alternative flow . 58
6.3.8 Post-conditions . 58
6.3.9 High Level Illustration . 59
6.3.10 Potential points of failure putting safety at risk . 59
6.3.11 Potential means to prevent points of failure . 59
6.4 MC1: IoT-based mission critical communications . 60
6.4.1 Emergency Domain . 60
6.4.2 Description . 60
6.4.3 Actors . 60
6.4.4 Pre-conditions . 61
6.4.5 Triggers . 61
6.4.6 Normal Flow . 61
6.4.7 Alternative flow . 61
6.4.8 Post-conditions . 62
6.4.9 High Level Illustration . 62
6.4.10 Potential points of failure putting safety at risk . 62
6.4.11 Potential means to prevent points of failure . 63
6.5 MC2: Mission critical logistics support . 63
6.5.1 Emergency Domain . 63
6.5.2 Description . 63
6.5.3 Actors . 64
6.5.4 Pre-conditions . 65
6.5.5 Triggers . 65
6.5.6 Normal Flow . 65
6.5.7 Alternative flow . 65
6.5.8 Post-conditions . 65
6.5.9 High Level Illustration . 66
6.5.10 Potential points of failure putting safety at risk . 66
6.5.11 Potential means to prevent points of failure . 67
6.6 MC3: Emergency services teams accessing pre-deployed IoT devices . 68
6.6.1 Emergency Domain . 68
6.6.2 Description . 68
6.6.3 Actors . 69
6.6.4 Pre-conditions . 69
6.6.5 Triggers . 69
6.6.6 Normal Flow . 69
6.6.7 Alternative flow . 69
6.6.8 Post-conditions . 69
6.6.9 High Level Illustration . 70
6.6.10 Potential points of failure putting safety at risk . 70
6.6.11 Potential means to prevent points of failure . 70
6.7 PWS1: warning sent via IoT device to citizens . 71
6.7.1 Emergency Domain . 71
6.7.2 Description . 71
6.7.3 Actors . 71
6.7.4 Pre-conditions . 72
6.7.5 Triggers . 72
6.7.6 Normal Flow . 72
6.7.7 Alternative flow . 72
6.7.8 Post-conditions . 72
6.7.9 High Level Illustration . 73
6.7.10 Potential points of failure putting safety at risk . 73
6.7.11 Potential means to prevent points of failure . 73
6.8 AE1: IoT communication with priority handling to prevent emergency situation . 74
6.8.1 Emergency Domain . 74
6.8.2 Description .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.