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

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
• Technical Committee: EMTEL - Emergency Communications
• Current Stage: 12 - Completion
• Due Date: 17-Jul-2019
• Completion Date: 01-Jul-2019

Standards Content (Sample)

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

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.: [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.
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
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
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
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 . 74
6.8.3 Actors . 74
6.8.4 Pre-conditions . 75
6.8.5 Triggers . 75
6.8.6 Normal Flow . 75
ETSI
6 ETSI TR 103 582 V1.1.1 (2019-07)
6.8.7 Alternative flow . 75
6.8.8 Post-conditions . 75
6.8.9 High Level Illustration . 76
6.8.10 Potential points of failure putting safety at risk . 76
6.8.11 Potential means to prevent points of failure . 76
6.9 AE2: IoT-based action following public warning system message reception . 77
6.9.1 Emergency Domain . 77
6.9.2 Description . 77
6.9.3 Actors . 77
6.9.4 Pre-conditions . 77
6.9.5 Triggers . 78
6.9.6 Normal Flow . 78
6.9.7 Alternative flow . 78
6.9.8 Post-conditions . 78
6.9.9 High Level Illustration . 79
6.9.10 Potential points of failure putting safety at risk . 79
6.9.11 Potential means to prevent points of failure . 79
6.10 Conclusions . 80
7 Impact of use cases on specifications . 80
7.1 Introduction . 80
7.2 Recommendations of requirements for existing domains . 80
7.2.1 Emergency Calling domain. 80
7.2.1.1 Usage & Maintenance . 80
7.2.1.2 Interoperability . 81
7.2.1.3 Networks and connectivity . 81
7.2.1.4 Data Exchange at service and application level . 81
7.2.1.5 Security . 81
7.2.2 Mission Critical Communications domain . 82
7.2.2.1 Usage & Maintenance . 82
7.2.2.2 Interoperability . 82
7.2.2.3 Networks and connectivity . 82
7.2.2.4 Data Exchange at service and application level . 83
7.2.2.5 Security . 84
7.2.3 PWS domain . 84
7.2.3.1 Usage & Maintenance . 84
7.2.3.2 Interoperability . 84
7.2.3.3 Networks and connectivity . 84
7.2.3.4 Data Exchange at service and application level . 85
7.2.3.5 Security . 85
7.3 Recommendations of requirements for new domains. 85
7.3.1 Automated Emergency response domain . 85
7.3.1.1 Usage & Maintenance . 85
7.3.1.2 Interoperability . 86
7.3.1.3 Networks and connectivity . 86
7.3.1.4 Data Exchange at service and application level . 86
7.3.1.5 Security . 86
7.4 Concluding recommendations . 87
7.4.1 SC EMTEL recommendations . 87
7.4.2 Recommendations for IoT service platform specification groups . 87
7.4.3 Recommendations for network specification groups . 88
Annex A: Use case MC2: MCI logistics and management in detail . 89
Annex B: Bibliography . 93
Annex C: Change History . 94
History . 95

ETSI
7 ETSI TR 103 582 V1.1.1 (2019-07)
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 Report (TR) has been produced by ETSI Special Committee Emergency Communications (EMTEL).
Modal verbs terminology
In the present document "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.
Introduction
Since the Internet has matured, society has become more interconnected, as have the devices used to enhance everyday
lives. This has led to the emergence of the so-called "Internet of Things" (IoT), in which autonomous devices as well as
people act as connected endpoints in a massive network of networks.
The purpose of the present document is to consider communications involving IoT devices in all types of emergency
situations, such as emergency calling, mission critical communications, Public Warning System communications and a
new domain identified as automated emergency response, and to prepare the potential standardization requirements
enabling a safe operation of these communications.
The reader will find in clause 4 a general overview of the topic.
Clause 5 provides a comprehensive state of the art at the date of the present document, covering IoT in emergency
communications, as well as emergency handling in IoT communications. It analyses existing standards,
communications networks, previous studies and solutions being already deployed.
A set of eight exemplary use cases, presenting different types of communications and applications involving IoT
devices for emergency services, is presented in clause 6. The use cases are analysed from the point of view of potential
failures putting safety at risk. Potential means to prevent these points of failure are also identified.
ETSI
8 ETSI TR 103 582 V1.1.1 (2019-07)
Finally, the impact of these use cases on existing or future standards is assessed. A set of potential requirements is
proposed in clause 7, for each emergency domain under study, leading to recommendations for the different
standardization groups targeted by this study, including SC EMTEL, IoT service platform specification groups and
network specification groups.
ETSI
9 ETSI TR 103 582 V1.1.1 (2019-07)
1 Scope
The present document considers communications involving IoT devices in all types of emergency situations. This
includes the use of IoT devices to enhance:
• Emergency calling, e.g. between individuals and emergency authorities/organizations, between emergency
authorities/organizations, and between individuals.
• Mission critical communications within emergency services/public safety organizations, e.g. between public
safety officers and control centres, between the control centres of different public safety organizations, and
between individual public safety officers.
• Public Warning System type communications from authorities to the general public.
• Automated emergency response (new IoT domain) between two IoT devices.
The current state of the art for IoT device communications, especially when relevant to emergency situations, is
described and use cases illustrate how such communications can be used to provide additional/enhanced information for
communicating parties involved in emergency situations.
The impact of the use cases on the existing emergency, public warning, and mission critical communications is then
considered, and recommendations for requirements to existing specifications for each domain are provided.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
2.2 Informative 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.
NOTE: While any hyperlinks included in this clause were valid at t
...