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.
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

Share

IoT Software Verification

Download to read offline

These slides were presented at the Iran University of Science and Technology. It was for Dependable Software Systems course in Spring 2019.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to like this

IoT Software Verification

  1. 1. IoT Software Verification Hita Barasm Mamagani Spring 2019 - Dependable Software Systems Course (By Dr. R. Entezari) Iran University of Science and Technology
  2. 2. Introduction  30 billion connected devices by 2020  46 billion connected devices by 2021  We are always facing problems like network failure, energy power down and other environmental defects. The challenge is how to do IoT software fault tolerable and secure.
  3. 3. A Simple IoT Example SmartHome  A motion sensor  Sensor hub  Program running on cloud  An smart bulb  Smart bulb hub
  4. 4. Traditional Approach for FT  Triple modular redundancy and majority consensus
  5. 5. Traditional App. Problems  Each SmartThings device only connects to one hub  Some systems support only one hub per home  Very difficult even for a skilled programmer to build a fault-tolerant application
  6. 6. A New Approach  One spare is enough for hardware fault- tolerance.  Use different type of each device for each functionality.  It is not necessary to use special-purpose hubs.  Use different types of WAN to have reliable connectivity.  IoT Smart apps are stateless event handlers, that they respond to events and take action at the time.
  7. 7. uSFI: Ultra-Lightweight Software Fault Isolation  Provides isolation between modules via MPU.  Only a single module is active at a time.  Inter-module calls are managed by the uSFI runtime.  Kernel is sandboxed then it only has access to memory regions assigned to it.  Forcing kernel to run at unprivileged and calling the trusted runtime for privileged operations.  But uSFI incurs less than a 10% code size overhead and roughly a 1% performance overhead.
  8. 8. uSFI System Architecture  uSFI Compiler and Verifier
  9. 9. Frama-C Platform  Static analysis on code via EVA plugin  Deductive verification using plugin WP  Dynamic (runtime) verification E-ACSL2C
  10. 10. Runtime Verification
  11. 11. Resources  Terry, Doug. "Toward a new approach to IoT fault tolerance." Computer 49, no. 8 (2016): 80-83.  Aweke, Zelalem Birhanu, and Todd Austin. "uSFI: Ultra-lightweight software fault isolation for IoT- class devices." In 2018 Design, Automation & Test in Europe Conference & Exhibition (DATE), pp. 1015-1020. IEEE, 2018.  Blanchard, Allan, Nikolai Kosmatov, and Frédéric Loulergue. "A Lesson on Verification of IoT Software with Frama-C." In 2018 International Conference on High Performance Computing & Simulation (HPCS), pp. 21-30. IEEE, 2018.
  12. 12. The END! Any Questions? Thanks for giving your time. 

These slides were presented at the Iran University of Science and Technology. It was for Dependable Software Systems course in Spring 2019.

Views

Total views

54

On Slideshare

0

From embeds

0

Number of embeds

1

Actions

Downloads

0

Shares

0

Comments

0

Likes

0

×