Osaka University EE ES 2016 Talk series 2/3 21-JUN-2016

A part of Electrical Engineering Lecture Series 2016 at School of Engineering Science, Osaka University / 大阪大学基礎工学部電気工学特別講義2016 2/3

Transcript

1. oueees-201606 Part 2: IoT software and infrastructure Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 1
2. Kenji Rikitake 21-JUN-2016 School of Engineering Science Osaka University Toyonaka, Osaka, Japan @jj1bdx Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 2
3. Lecture notes on GitHub • https://github.com/jj1bdx/oueees-201606- public/ • Don't forget to check out the issues! Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 3
4. What Internet of Things is all about? Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 4
5. Things. Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 5
6. Internet (supposed to be) Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 6
7. Trivia: IoT is also called M2M (Machine to Machine) Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 7
8. M2M technology • Direct communication between devices • IoT is modern M2M • Links: PSTN, GSM/3G/LTE, internet, Wifi, bluetooth, LoRa (low-power WAN), etc. • Not necessarily centralized Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 8
9. Cyber-physical systems1 1 By Behrad3d/IMSCenter.net, http://imscenter.net/cyber-physical-platform Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 9
10. OTOH current IoT model: for telemetering = data collection Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 10
11. Telemetering Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 11
12. So, the reality is: • Mostly unidirectional (not really the true and genuine internet) • Sensors/devices gathering data through internet and feed them to the servers in the cloud computing platforms • The servers do the most of computation • Extremely centralized Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 12
13. Things need local servers Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 13
14. Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 14
15. Why local server nodes? • Microcontrollers do not speak internet • TCP/IP, HTTP, MQTT and other protocols are simply too complex • Local servers give more computing power • Devices to servers: serial over USB, SPI, I2C • Local servers to internet: HTTP, MQTT, UDP • ... with cryptographic security (TLS) Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 15
16. Reality: nobody wants to think about the security (and privacy) Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 16
17. Secure operation is hard • Access control: filesystems, networks, etc. • Authentication: identity management • Cryptography: computationally security consumes a lot of CPU power • Logging and backup • Physical tampering: TEMPEST (electromagnetic emission), wiretapping, device theft Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 17
18. More reality: security incidents may risk your business and trust Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 18
19. So what is "IoT security"? • Nothing special: no silver bullet exists • 20 years ago in 1995, it was called private network; and now it is called VPN (virtual private network) • How to connect non-intelligent devices without worrying much about security • Closed networks built over internet • Question: is it really secure? Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 19
20. Security with 3G/LTE example: SORACOM Canal • Device > 3G/LTE > SORACOM Virtual Private Cloud (VPC) > user's AWS VPC (no internet exposure) • SIM-based authentication and encryption • No need to configure VPN • Access to internet selectable via Virtual Private Gateways (VPGs) • Public Beta status as of June 2016 Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 20
21. Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 21
22. Other issues on IoT infrastructure systems • Very large scale database is hard • Massive connections/packets from devices • Concurrency/parallelism • Consistency .vs. availability • Distributed systems problem • Fault-tolerance .vs. simplicity Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 22
23. Inconsistency by concurrency/parallelism Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 23
24. Concurrency and timing Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 24
25. Inconsistency by netsplit Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 25
26. IoT device communication • Data link speed (bits/second) • Frequency per TCP/UDP/IP packets • Frequency per transmission events • Acceptable error rate • Acceptable power consumption • ... and many more things to consider Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 26
27. Question: what kind of link technologies will emerge for IoT? Think about the following points: • How much energy can a device consume? • How much bandwidth is required? • How reliable should the communication be? Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 27
28. Credits for photos and diagrams • https://pixabay.com/en/icons-symbols-signs-set-travel-41305/ [CC0 / public domain] • https://pixabay.com/en/network-iot-internet-of-things-782707/ [CC0 / public domain] • By Behrad3d/IMSCenter.net [CC BY-3.0], via Wikipedia https://en.wikipedia.org/wiki/File %3ACPS_for_Manufacturing.png • By Jackyknight (Own work) [CC BY-SA 3.0], via Wikimedia Commons https://commons.wikimedia.org/wiki/File%3AParallel-tasks.png • By b4283 (Own work) [CC0 / public domain], via Wikimedia Commons https://commons.wikimedia.org/wiki/File %3ANetsplit_split.svg Kenji Rikitake / oueees 201606 part 2 21-JUN-2016 28