Technical 103 582 (STF of and communications IoT devices ... · When relevant, IoT devices should be able to trigger other IoT devices (e.g., smoke detector turns on a camera). The

Presented by: For:

© ETSI 2019

23.10.2019

ETSI Technical Report 103 582 (STF 555)Study of use cases and communications

involving IoT devices in emergency situations

Michelle Wetterwald, STF leader

ETSI IoT Week 2019

© ETSI 2019 2

Content

Motivation for the work ‐ IoT in emergency situations

Objective & presentation of the project (STF 555)

Methodology and Use cases

Recommendation for requirements

Conclusion

ETSI IoT Week, 23/10/2019

© ETSI 2019 3

MotivationThe Internet has matured ‐ “Internet of Things” (IoT) has emerged

Objects and people are now interconnected in and across private, public, and industrial spaces

IoT includes:devices in the physical world

sensors within or attached to these devices

smart services and applications.

Scope of IoT wider than connectivity and communication systemsintegration and interoperability

infrastructure deployment

devices and sensor technologies

security and privacy.

IoT technologies invading all application domains including services relevant to emergency situations

Requirements for the safety of communications involving IoT devices in emergency situations are necessary !


© ETSI 2019 4

Objectives of ETSI TR 103 582

A Technical Report to prepare the requirements for communications involving IoT devices in all types of emergency situations.

Leverage from benefits of IoTData gathering without human interactionObjectivity of IoT data Fast and fail‐safe information sharingNo translation of human languages requiredReal‐time data transmission Operation in dangerous environments


© ETSI 2019 5

ETSI STF 555 ‐ Project DescriptionDeliverable (Technical Report):

ETSI TR 103 582: Study of use cases and communications involving IoT devices in provision of emergency situations

Experts

Steering Committee ETSI SC EMTEL (Emergency Communications) / ETSI‐funded STF

Liaisons with : ETSI TC SmartM2M, ETSI TC SmartBAN, ETSI TC TCCE, 3GPP SA1, 3GPP SA3, 3GPP SA4, 3GPP SA6, oneM2M and GSMA

ScheduleThe work started on 1st of July 2018 and ended, as planned, end of June 2019

Publication of the TR early July 2019ETSI IoT Week, 23/10/2019

* STF : Specialists Task Force

© ETSI 2019 6

MethodologyIdentify all potential communication failures in an exemplary set of use cases derived from a thorough state of the art analysis and suggest mechanisms to prevent them

Four emergency communication domains were analyzed:Emergency Calling (EC)

Mission Critical (MC) communications

Public Warning System (PWS)

Automated Emergency (AE) response (new emergency communication domain)

For every emergency domain, 5 “knowledge areas” for potential requirements have been identified :

Usage & maintenance

Interoperability

Networks and connectivity

Data exchange at service and application level

SecurityETSI IoT Week, 23/10/2019

© ETSI 2019 7

List of use cases

EC1: Automatic direct emergency call from IoT device

EC2: IoT device provides additional information to an emergency call

MC1: IoT‐based mission critical communications

MC2: Mission critical logistics support

MC3: Emergency services teams accessing pre‐deployed IoT devices

PWS1: Warning sent by IoT device to citizens

AE1: IoT communication with priority handling to prevent emergency situation

AE2: IoT‐based action following public warning system message receptionETSI IoT Week, 23/10/2019

© ETSI 2019 8

Actors involved in the different use cases


© ETSI 2019 9

Example Use Case: EC1: Automatic direct emergency call from IoT device


A smoke detector in a trash container sends an emergency message in the event of a fire, or even provides in parallel a real‐time emergency video

The message is received by an IoT service provider where an operator asserts the existence of the fire and calls 112 [Preferred solution to avoid false alarms]

The PSAP dispatches the necessary emergency services

© ETSI 2019 10

Example Use Case: MC1: IoT‐based mission critical communications


Smart clothing, equipped with sensors or virtual reality headset, can report in real time vital signs and temperature of firefighters involved in hazardous situations.

IoT gateway, located in the truck, can analyse these data and share them with the relevant responders, locally or remotely

© ETSI 2019 11

Example Use Case: AE2: IoT‐based action following PWS message reception


An earthquake occurs at sea, maybe followed by a tsunami in coastal regions. A PWS message is broadcasted to the public

An IoT device receiving this message may turn off a gas tap autonomously or prevent a train to further progress towards the coast.

Another IoT device receiving the same message may trigger additional display on bus stops, road VMS, etc. to increase the level of dissemination of the warning (PWS1: Warning sent by IoT device to citizens)

© ETSI 2019 12

Recommendations of requirements (extracted examples)Usage and maintenance

An IoT device supporting emergency communications functionality should be remotely manageable

Software updates of IoT entities should be subject to a certification process

The configuration of the IoT device supporting PWS should be properly tested before the start of its operation, and then on a regular basis

An IoT service platform supporting Automated Emergency Response should monitor the status of an IoT device supporting automated emergency response

InteroperabilityEmergency data received from an IoT device should be clear and unambiguous

IoT entities involved in emergency communications should use interoperable protocols and data syntax

IoT service platform elements (e.g. IoT device, IoT gateway) should be interoperability tested inside and between different emergency services teams

Data exchange should be based on commonly accepted standards by all stakeholders (industry and users).


© ETSI 2019 13

Recommendations of requirements (extracted examples)Data exchange at service and application level

IoT devices involved in emergency calling should support the sending of an emergency data messageWhen relevant, IoT devices should be able to trigger other IoT devices (e.g., smoke detector turns on a camera).The IoT service platform and the IoT device should identify PWS message duplication and suppress them.An IoT service platform involved in automated emergency response should ensure data interoperability between the emergency control centre and the IoT devices (e.g. semantics)

SecurityRemote triggering of an emergency data message from an IoT device should be prevented other than via its sensor (e.g. prevent communication intrusion)IoT devices and IoT service platform should mutually authenticate each other before activationThe service provider should ensure the security, integrity and correctness of the data receivedIoT data confidentiality should be assured at any time.


© ETSI 2019 14

ConclusionTR 103 582 contains a technical study of impacts of IoT in emergency situations,

Analysis of the state of the art

Definition of exemplary use cases and analysis of potential failures and impact

Proposal of recommendations of potential requirements for revised / new standards

The proposed recommendations do not target specific specifications. Rather, they are organised by emergency communication domain and according to which knowledge area of that domain they apply

Concluding remarks give further indications asRecommendations for ETSI SC EMTEL

update of EMTEL TS to include these recommendations is ongoing

Recommendations for IoT service platform specification groups (e.g. oneM2M, OCF)

Recommendations for network specification groups (e.g. 3GPP, ETSI [TCCE, SES], IETF, ITU‐T, IEEE or some specific industrial alliances: ZigBee, Z‐Wave, LoRa)

AEF (Ag Equipment) was interested to leverage results for revision of the Machinery Directives (Safety)

System deployment stakeholders are impacted as well !!!ETSI IoT Week, 23/10/2019

© ETSI 2019 15

Contact details

Thank you for your attention. Questions?

Michelle Wetterwald

ex‐STF 555 leaderNETELLANY / FBConsulting

[email protected]

STF web page: https://portal.etsi.org//STF/STFs/STFHomePages/STF555


Documents

Technical 103 582 (STF of and communications IoT devices ... · When relevant, IoT devices should be able to trigger other IoT devices (e.g., smoke detector turns on a camera). The