IoT Day 2013 - Madrid

Technology

waltercolitti
  • 1.Open IP and Web Technologies forthe Internet of Things WALTER COLITTI (@waltercolitti)VRIJE UNIVERSITEIT BRUSSEL
  • 2. “Big” devicesThings on the Internet 2
  • 3. “Small” devicesIntranet of ThingsDifferent protocols = no interoperabilityGateways = architectural complexityGateways = no integration with the Web3
  • 4. Internet backgroundEnd-to-End principle InteroperabilityWhy not repeating the IP success in IoT? 4
  • 5. Embedded IPTechnologies
  • 6. Embedded IP – StandardsPromotes IP as network technology for embeddeddevices6LoWPAN Enables IPv6 over constrained networksRPL Routing protocol for Low-power Lossy Networks6
  • 7. 6LowPAN – AdvantageINTERNETWirelessSensor LANNetwork Application ApplicationTransport TransportInternetInternet Internet InternetInternet(IPv4/IPv6) (IPv4/IPv6)(IPv4/IPv6) (IPv6)(IPv6) 6LoWPAN 6LoWPAN LinkLink LinkLinkLink (802.15.4)(802.15.4)Application LAN/InternetInternet/WSNTCP/IP enabledborder router border routerSensor mote 7
  • 8. Embedded Web Technologies(Web of Things)
  • 9. Embedded Web - AdvantageThe Web is everywhereJSON REST URIXMLHTTP 9
  • 10. Embedded Web - ProblemREST/HTTP complex for tiny devicesRelies on TCPREST/HTTP not designed for IoT/M2M appsComplex observation mechanismsNo multicast supportLong-lived transactions10
  • 11. Constrained Application Protocol (CoAP)
  • 12. CoAP standardCoRE Working GroupConstrained Application Protocol HTTP functionalities for constrained devices Extra functionalities added12
  • 13. CoAP principleRequest/Response HTTPCoAPDual Layer TCP UDP TransactionIPIP Transaction layer for message exchange Request/Response layer for resource manipulation Small message overhead (4 bytes binary header)Features Client can observe resource status changes 13
  • 14. CoAP PerformanceResponse Time14
  • 15. CoAP Performance Energy consumption(server mote)15
  • 16. HTTP – CoAP ProxyClient Proxy Serverhttp:// sensor1.contikigh.com/readings http://193.226.5.150/readings GET /readings HTTP/1.1 Host: sensor1.contikigh.comcoap:// sensor1.contikigh.com/readingscoap:// [aaaa::c30c:0:0:365]/readingsCON GETURI -Path: readingsCON 2.00 {“sensor”:”212:7400:2:202”,”readings”:{“hum”:50,”temp”:26.8}} HTTP/1.1 200 OKHumidity: 50, Temperature: 26.8 16
  • 17. THANK YOUfor your attentionWALTER COLITTI (@waltercolitti) Email: wcolitti@gmail.com
    Please download to view
  • 1
    All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
    Description
    This presentation was given at the celebration of the international Internet of Things day in Madrid. It presents the use of IP and Web standard communication technologies for the IoT. In particular the 6LowPAN and CoAP protocols are briefly presented.
    Text
    • 1.Open IP and Web Technologies forthe Internet of Things WALTER COLITTI (@waltercolitti)VRIJE UNIVERSITEIT BRUSSEL
  • 2. “Big” devicesThings on the Internet 2
  • 3. “Small” devicesIntranet of ThingsDifferent protocols = no interoperabilityGateways = architectural complexityGateways = no integration with the Web3
  • 4. Internet backgroundEnd-to-End principle InteroperabilityWhy not repeating the IP success in IoT? 4
  • 5. Embedded IPTechnologies
  • 6. Embedded IP – StandardsPromotes IP as network technology for embeddeddevices6LoWPAN Enables IPv6 over constrained networksRPL Routing protocol for Low-power Lossy Networks6
  • 7. 6LowPAN – AdvantageINTERNETWirelessSensor LANNetwork Application ApplicationTransport TransportInternetInternet Internet InternetInternet(IPv4/IPv6) (IPv4/IPv6)(IPv4/IPv6) (IPv6)(IPv6) 6LoWPAN 6LoWPAN LinkLink LinkLinkLink (802.15.4)(802.15.4)Application LAN/InternetInternet/WSNTCP/IP enabledborder router border routerSensor mote 7
  • 8. Embedded Web Technologies(Web of Things)
  • 9. Embedded Web - AdvantageThe Web is everywhereJSON REST URIXMLHTTP 9
  • 10. Embedded Web - ProblemREST/HTTP complex for tiny devicesRelies on TCPREST/HTTP not designed for IoT/M2M appsComplex observation mechanismsNo multicast supportLong-lived transactions10
  • 11. Constrained Application Protocol (CoAP)
  • 12. CoAP standardCoRE Working GroupConstrained Application Protocol HTTP functionalities for constrained devices Extra functionalities added12
  • 13. CoAP principleRequest/Response HTTPCoAPDual Layer TCP UDP TransactionIPIP Transaction layer for message exchange Request/Response layer for resource manipulation Small message overhead (4 bytes binary header)Features Client can observe resource status changes 13
  • 14. CoAP PerformanceResponse Time14
  • 15. CoAP Performance Energy consumption(server mote)15
  • 16. HTTP – CoAP ProxyClient Proxy Serverhttp:// sensor1.contikigh.com/readings http://193.226.5.150/readings GET /readings HTTP/1.1 Host: sensor1.contikigh.comcoap:// sensor1.contikigh.com/readingscoap:// [aaaa::c30c:0:0:365]/readingsCON GETURI -Path: readingsCON 2.00 {“sensor”:”212:7400:2:202”,”readings”:{“hum”:50,”temp”:26.8}} HTTP/1.1 200 OKHumidity: 50, Temperature: 26.8 16
  • 17. THANK YOUfor your attentionWALTER COLITTI (@waltercolitti) Email: wcolitti@gmail.com
  • Comments
    Top