Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

EENA2019: Track2 session4 _Study of use cases and communications involving IoT devices in emergency solutions_Michelle Wetterwald

1,171 views

Published on

Cities and emergency services need to better understand emerging technologies, which represent a novel way to tackle potential threats and incidents in urban spaces. This session will highlight concrete examples of how strengthened resilience of public spaces could be enabled.

Chair: Mladen Vratonjic, Vice President, EENA

  • Be the first to comment

  • Be the first to like this

EENA2019: Track2 session4 _Study of use cases and communications involving IoT devices in emergency solutions_Michelle Wetterwald

  1. 1. Presented by: For: © ETSI 2019 11.04.2019 ETSI Technical Report 103 582 (STF 555) Study of use cases and communications involving IoT devices in emergency situations Michelle Wetterwald, STF Leader EENA Conference, April 11, 2019
  2. 2. © ETSI 2019 2 Content Motivation for the work - IoT in emergency situations Objective & presentation of the project (STF 555) Use cases Recommendation for requirements Conclusion EENA Conference, 11/04/2019
  3. 3. © ETSI 2019 3 Motivation The 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 systems. integration and interoperability infrastructure deployment devices and sensor technologies security and privacy. IoT technologies invading all application domains including services relevant to emergency situations, but… No requirements yet for communications involving IoT devices in emergency situations! EENA Conference, 11/04/2019
  4. 4. © ETSI 2019 4 ETSI STF 555 - Objectives The purpose of this standardisation project (STF 555) is to deliver a Technical Report to prepare the requirements for communications involving IoT devices in all types of emergency situations. This includes the use of IoT devices to enhance: Emergency calling Mission critical communications Public Warning System Leverage from benefits of IoT Data gathering without human interaction Objectivity of IoT data Fast and fail-safe information sharing No translation of human languages required Real-time data transmission Operation in dangerous environments EENA Conference, 11/04/2019 * STF : Specialists Task Force
  5. 5. © ETSI 2019 5 ETSI STF 555 - Project Description Deliverable (Technical Report): ETSI TR 103 582: Study of use cases and communications involving IoT devices in provision of emergency situations Steering Committee ETSI SC EMTEL (Emergency Communications) Schedule The work started on 1st of July 2018 The stable draft of the Technical Report is under review, Publication of the Report is planned mid-June 2019 EENA Conference, 11/04/2019
  6. 6. © ETSI 2019 6 List of use cases An exemplary set of use cases has been derived from the state of the art analysis 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 reception EENA Conference, 11/04/2019 AE: Automated Emergency EC: Emergency Calling MC: Mission Critical PWS: Public Warning System
  7. 7. © ETSI 2019 7 Actors involved in the different use cases EENA Conference, 11/04/2019 Actors Citizens Local Emergency Management Authority (LEMA) IoT Device(s) Sensors Processors Actuators Connectivity IoT Platform IoT Server(s) IoT Gateway IoT Application(s) Man-Machine-Interface(s) Machine-Machine-Interface(s) Communication Network(s) / Service Provider(s) IoT Network(s) Public Telecommunications Network(s) Emergency Service Network (for PSAP, ECC, LEMA etc.) Mission Critical Communications Network Public Safety Answering Point(s) (PSAP) PSAP Operator(s) Emergency Control Centre(s) (ECC) Off-site Incident Area (Field Emergency Control Centre) Emergency Service(s) (incident area) Emergency Service(s) Decision Maker(s) Emergency Service(s) Team(s) Member(s) Fire Brigade Health / Medical Technical Rescue Surface Water Rescue Police
  8. 8. © ETSI 2019 8 Example Use Case: EC1: Automatic direct emergency call from IoT device Example in a smart city : 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 EENA Conference, 11/04/2019
  9. 9. © ETSI 2019 9 Example Use Case: MC1: IoT-based mission critical communications Example in a smart city : smart clothing, equipped with sensors, can report in real time vital signs and temperature of firefighters involved in hazardous situations. EENA Conference, 11/04/2019 IoT Server IoT Gateway 55° 42° 15° Common Operating Picture Vict1: Adult male Vict2: Adult female IoT :: Temp. Sensor IoT :: Smart Glasses Emergency Service Decision Maker Alternative flow On-site Emergency Service Decision Maker Emergency Control Center Critical Communications Network(s) Emergency Communication Network(s)
  10. 10. © ETSI 2019 10 Example Use Case: AE2: IoT-based action following PWS message reception Example in a smart city : an earthquake occurs at sea, may be followed by a tsunami in coastal regions , the IoT device may turn off a gas tap or prevent a subway to further progress towards the coast EENA Conference, 11/04/2019
  11. 11. © ETSI 2019 11 Impact of the use cases : recommendations of requirements to be included in new / revised standards Four emergency communication domains were analyzed: Emergency calling Mission critical communications Public warning system (PWS) Automated emergency 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 Security EENA Conference, 11/04/2019
  12. 12. © ETSI 2019 12 Recommendations of requirements (extracted examples) Usage and maintenance Emergency Calling domain Emergency data received from an IoT device should be clear and unambiguous Mission Critical Communication domain Software updates of IoT entities should be subject to a certification process Public Warning System domain The configuration of the IoT device supporting PWS should be properly tested before the start of its operation, and then regularly Automated Emergency Response domain A supporting IoT service platform should monitor the status of an IoT device supporting automated emergency response EENA Conference, 11/04/2019
  13. 13. © ETSI 2019 13 Recommendations of requirements (extracted examples) Data exchange at service and application level Emergency Calling domain IoT devices should support the sending of an emergency data message Mission Critical Communication domain IoT devices should be able to trigger other IoT devices (e.g., smoke detector turns on a camera). Public Warning System domain The IoT service platform and the IoT device should identify PWS message duplication and suppress them. Automated Emergency Response domain An IoT service platform involved in automated emergency response should ensure data interoperability between the emergency control centre and the IoT devices EENA Conference, 11/04/2019
  14. 14. © ETSI 2019 14 Conclusion STF 555 has performed 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 as Recommendations for ETSI SC EMTEL 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) System deployment stakeholders are impacted as well !!! EENA Conference, 11/04/2019
  15. 15. © ETSI 2019 15 Contact details Thank you for your attention. Questions? Michelle Wetterwald STF 555 leader Email: michelle.wetterwald@netellany.fr michelle.wetterwald@gmail.com STF web page: https://portal.etsi.org//STF/STFs/STFHomePages/STF555 EENA Conference, 11/04/2019
  16. 16. © ETSI 2019 16 An ETSI Specialists Task Force (STF) project EENA Conference, 11/04/2019 Obsolete superseded standards Officially issue new or revised standards Elaborate new or revised standards Define scope and work plan Identify needs Inception Conception Drafting ApprovalObsolescence I : idem ipsium volverit . II : ibidem quaestio velim ad magnam... III : sicut ingenius hanc ..... I : idem ipsium volverit . II : ibidem quaestio velim ad magnam... III : sicut ingenius hanc ..... Funding approved by ETSI board for dedicated experts Picture from R. Bolla, Univ of Genoa, draft of "Understanding ICT Standardization: Principles and Practice", ETSI

×