CoAP, Copper, and Embedded Web Resources

9,718 views
9,396 views

Published on

Presentation at the Internet of Things Zurich Meetup, Zurich, Switzerland.
http://www.meetup.com/IoT-Zurich/events/55029792/

Published in: Technology, Business
0 Comments
11 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
9,718
On SlideShare
0
From Embeds
0
Number of Embeds
70
Actions
Shares
0
Downloads
369
Comments
0
Likes
11
Embeds 0
No embeds

No notes for slide

CoAP, Copper, and Embedded Web Resources

  1. 1. CoAP, Copper, and Embedded Web ResourcesMatthias Kovatschkovatsch@inf.ethz.chTuesday, 03 Apr 2012 Internet of Things Zurich Meetup, Zurich, Switzerland
  2. 2. What About Really Cheap Platforms? Smart DustMatthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 2
  3. 3. Outcome Wireless Sensor NetworksMatthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 3
  4. 4. IP Connectivity through 6LoWPAN IP router Web serverMatthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 4
  5. 5. Constrained Application Protocol (CoAP) A new Web-like protocol based on REST GET, PUT, POST, DELETE URIs Internet Media Types Interoperability Extensible option headers Common programming modelMatthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 5
  6. 6. The CoAP Universe IETF working group «Constrained RESTful Environments»  RESTful Web services for mote-class devices  Transparent mapping to HTTP Observing Resources publish/subscribe Group communication IP multicast CoRE Link Format Web linking RFC, discovery Caching proxies RESTful caching Resource directories sleepy nodes Blockwise transfers bulky data …Matthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 6
  7. 7. CoAP is Optimized, Binary…Matthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 7
  8. 8. Copper (Cu) CoAP user-agentMatthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 8
  9. 9. Embedded Web Resources /actuators/leds /config/date /consumption /debug/channel /config/mode /consumption/consumed /debug/neighbors /config/time /consumption/generated /debug/observers /debug/… /debug/… /debug/routes /sensors/battery /max/power /sensors/batter /sensors/temp /max/current y /sensors/button /sensors/user /max/voltage /sensors/humidity /set/valve /meter/power /sensors/light /set/target /meter/current /sensors/temperature /meter/voltage /meter/frequency /meter/phase /meter/reactive /reset /switchMatthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 9
  10. 10. Profiles for Embedded Web Resources IPSO Profile Smart Energy Profile 2.0  Pure RESTful design  SOAP-like service design  Treats CoAP and HTTP equally over REST  Currently still cryptic identifiers  Currently only defined for due to size optimizations HTTP, CoAP in the draft (e.g., /lt for light)Matthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 10
  11. 11. CoAP Open Source Implementations* Erbium for Contiki Californium in Java Copper for Firefox  REST Engine  CoAP framework  CoAP user-agent  For embedded devices  For the back-end  For user interaction  Enables thin server  Clients, servers,  Integration and testing architecture and proxies tool* Available on GitHub:athttps://github.com/mkovatsc Paris, France, Mar 2012: http://www.etsi.org/plugtests/coap/coap.htm Successfully tested the ETSI IoT CoAP Plugtests,Matthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 11
  12. 12. THANK YOUQuestions?Matthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 12
  13. 13. Protocol Stack Layer Protocol Application CoAP Transport UDP Network IPv6 / RPL Adaption 6LoWPAN MAC CSMA / link-layer bursts Radio Duty Cycling IEEE 802.15.4e / ContikiMAC Physical IEEE 802.15.4Matthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 13
  14. 14. CoAP Message Format 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Ver| T | OC | Code | Message ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Options (if any) ... | (Terminator) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Payload (if any) ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Matthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 14
  15. 15. CoAP Option Encoding 0 1 2 3 4 5 6 7 +---+---+---+---+---+---+---+---+ | Option Delta | Length | for 0..14 +---+---+---+---+---+---+---+---+ | Option Value ... +---+---+---+---+---+---+---+---+ for 15..270 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | Option Delta | 1 1 1 1 | Length - 15 | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | Option Value ... +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+Matthias Kovatsch – ETH Zürich CoAP, Copper, and Embedded Web Resources 15

×