Sharing and Controlling the IoT
0 likes282 views
The document outlines various technological components and protocols related to the Internet of Things (IoT), focusing on their identification, communication, integration, and security aspects. It introduces platforms like Senz for sharing and controlling IoT data while emphasizing the importance of privacy and end-to-end security in IoT applications. Additionally, it discusses the challenges of addressing and securing IoT devices, as well as the complexities involved in machine-to-machine communications.
Sharing and Controlling the IoT
- 1. Sharing and Controlling the Internet of Things (IoT) Kasun De ZoysaKasun De Zoysa score.ucsc.lk University of Colombo School of Computing Sri Lanka
- 2. Technological Components Identification (“sensing”): ● (passive, active) RFID tags ● sensor networks Communication: ● interface object/network ● embed the TCP/IP stack into the devices (TinyTCP, mIP)? Integration: ● object and service discovery ● object and service cataloging ● service composition Intelligence and Collaboration: Security and Privacy:
- 3. Identification Ultimate goal: unique/universal Id for naming and addressing individual objects Naming is difficult! ● DNS: Domain Name Service ● ONS: Object Name Service, ● basically, RFID tag/EPC code → URI of a description file (Object Code Mapping Service-Direct Search (OCMS-DS) Addressing is difficult! stupid but tricky issue: RFID addresses are different from IPv6 addresses (64-96 bits vs 128 bits) Addressing moving objects is even more difficult
- 4. Communication From host2host to object2object TCP is not adapted designed for long-lasting connections while objects (like tags or sensors) exchange small pieces of data => handshake + congestion control/retransmit/recovery + flow control + buffering procedures too complex Very heterogeneous networks and traffic Scalability? Quality of service?
- 6. 6LoWPAN • IPv6 over Low-Power wireless Area Networks • Defined by IETF standards (RFC 4919, 4944) • Stateless header compression • Enables a standard socket API • Minimal use of code and memory • Direct end-to-end Internet integration • Multiple topology options
- 7. CoAP The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained networks in the Internet of Things. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.
- 8. UpnP Universal Plug and Play (UPnP) is a set of networking protocols that permits networked devices, such as personal computers, printers, Internet gateways, Wi-Fi access points and mobile devices to seamlessly discover each other's presence on the network and establish functional network services for data sharing, communications, and entertainment. UPnP is intended primarily for residential networks without enterprise-class devices.
- 9. LWM2M Lightweight M2M is a protocol from the Open Mobile Alliance for M2M or IoT device management. Lightweight M2M enabler defines the application layer communication protocol between a LWM2M Server and a LWM2M Client, which is located in a LWM2M Device.
- 10. MQTT MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.
- 11. REST REST stands for Representational State Transfer. (It is sometimes spelled "ReST".) It relies on a stateless, client-server, cacheable communications protocol -- and in virtually all cases, the HTTP protocol is used. REST is an architecture style for designing networked applications.
- 12. WebSocket WebSocketis a web technology providing full-duplex communications channels over a single TCP connection The WebSocket API is being standardized by the W3C, and the WebSocket protocol has been standardized by the IETF as RFC 6455. WebSocket is designed to be implemented in web browsers and web servers, but it can be used by any client or server application.
- 16. IoT Security is Hard Complex, distributed systems ● Many languages, and networks ● Specialized hardware Just developing applications is hard Securing them is even harder ● Enormous attack surface ● Reasoning across hardware, software, languages, devices, etc. ● What are the threats and attack models? Valuable data: personal, location, presence • Rush to development + hard ➔ avoid, deal later
- 17. Security Protocols Standard IT security solutions are the core security mechanisms for most of these protocols which offer security. These security approaches are based on: ● TLS ● IPSec / VPN ● SSH ● SFTP ● Encryption and decryption ● DTLS (for UDP only security)
- 18. Data Security What do IoT applications need to do? ● Generate data samples ● Process/filter these samples ● Analytics on streams of data, combined with historical data ● Produce results for end applications to view Goal: end-to-end security ● Embedded devices generate encrypted data ● Only end applications can fully decrypt and view data ● Gateways and cloud operate on data without knowing what it is
- 19. Homomorphic Encryption Can we compute statistics on secrets? ● You’re in the 85th percentile for saving water today! ● Your house consumed 120% of its average energy today Can we securely compute complex analytics? Need new cryptographic computation models
- 25. PubNub
- 26. Azure IoT Hub
- 27. AWS IoT Hub
- 28. Can we do better? ● Keep data on IoT device and share it if necessary ● Secure communication directly from each device ● Secure computation on the trusted device ● Can do that for small set of devices belong to a person. Claim: many IoT cloud computations can be done as a distributed protocol among clients!
- 29. SenZ PlatformSenZ Platform ➢ Introduction of low cost devices such as Android mobile phones and Raspberry-pi have made Internet of Things (IoT) a bit closer to life. ➢ We developed a social network like platform called SenZ (www.mysensors.info) to share and control IoT. ➢ SenZ platform strengthens the protection of the user's privacy with its cryptographic protocol and new Senz language. ➢ SenZ: Human to Machine (H2M) and M2M Protocol
- 30. Senze Language – Simple Example 1 The device D1 which belongs to Kasun says SHARE #tp @kasun SenZ delivers to the senze to Kasun as: SHARE #tp @kasun #time <t1> ^D1 <Digital Signature> Then Kasun sends a message GET #tp @D1 FOR 5day SAMPLE 5s The device receives the message and execute the Senze GET #tp @D1 FOR 5day SAMPLE 5s #time <t2> ^kasun <Digital Signature> Then device D sends the data to Kasun for 5 days in very 5 seconds DATA #tp 30 @kasun So that Kasun receives DATA #tp 30 #time <t2> ^DA <Digital Signature>
- 31. Senze Language – Simple Example 2 The Raspberry-pi device (rpi) belongs to kasun says SHARE #gpio1 @kasun Kasun receives the message: SHARE #gpio1 @kasun #time <t1> ^rpi <Signature> Then Kasun sends a message PUT #gpio1 ON @rpi OR PUT #gpio1 OFF @kasun.rpi The device receives the message PUT #gpio1 ON #time <t2> ^kasun <Signature> OR PUT #gpio1 OFF #time <t2> ^kasun <Signature> It turns on/off the switch The device sends the data DATA #gpio1 ON @kasun OR DATA #gpio1 OFF @kasun So that Kasun receives DATA #gpio1 ON #time <t3> ^rpi <Signature> OR DATA #gpio1 OFF #time <t3> ^rpi <Signature>
- 32. Senze Language – Simple Example 3 The Kasun would like to share his location with his wife (Shanika). So Kasun's smart phone says: SHARE #lat #lon @shanika Shanika receives the message: SHARE #lat #lan @kasun #time <t1> ^kasun <Signature> Then Shanika sends a message GET $lat $lon @kasun The Kasun receives the message GET $lat $lon @kasun $key <encrypted key> #time <t1> ^shanika <Signature> The Kasun's smart phone sends the data DATA $lat <encrypted data> $lon <encrypted data> @shanika Shanika receives the data, decrypts it and displays on the map.
- 34. Human Elephant Conflict Infrasonic Localization Smart Electric Fence
- 35. HomeZ: Smart Home Application
- 36. Rahasak: Social Network AppRahasak: Social Network App (www.rahasak.com)(www.rahasak.com) ➢ Typical social network applications saves data at central servers/clouds ➢ Users may not have the total control of their data. ➢ Therefore, present mobile applications with location sharing create serious privacy issues. ➢ An application which use SenZ platform to securely share secrets information such as location and camera among friends. ➢ Can be installed in your android phone freely. ➢ Share your secrets only with people you trust. ➢ Even SenZ platform or anyone else cannot see it.