Exposing M2M to the REST of us
26 likes•33,512 views
The document discusses the integration of machine-to-machine (M2M) communication and the Internet of Things (IoT) through a proposed solution called Qest, which utilizes MQTT and REST protocols for data exchange. It emphasizes the need for efficient data representation and communication security, as well as the significance of bridging traditional web development with IoT. The presentation aims to provide a Rails-like experience for developing M2M applications.
![if (!client.connected()) {
client.connect("arduino");
}
client.loop();
char s[10];
itoa(get_temperature(), s, 10);
client.publish("temp", s);
on Arduino: publishing](https://image.slidesharecdn.com/exposingm2mtotherestofus-130606035347-phpapp01/85/Exposing-M2M-to-the-REST-of-us-35-320.jpg)
![if (!client.connected()) {
client.connect("arduino");
}
client.loop();
char s[10];
itoa(get_temperature(), s, 10);
client.publish("temp", s);
This is called a topic,
and it is where we publish
data on MQTT.
on Arduino: publishing](https://image.slidesharecdn.com/exposingm2mtotherestofus-130606035347-phpapp01/85/Exposing-M2M-to-the-REST-of-us-36-320.jpg)
Exposing M2M to the REST of us
- 1. Exposing M2M to the REST of us @matteocollina
- 2. Matteo Collina Ph.D. Student @ University of Bologna @matteocollina matteocollina.com
- 6. Did you see it coming http://www.flickr.com/photos/12738000@N00/360231193/
- 10. We don’t #code for this phone anymore!
- 11. 7:11 PMiPad How do we #code an App?
- 12. 7:11 PMiPad We #code a response to some kind of user action
- 13. Pop-up Dialog OK This message come from the server! Cancel Web ServerTap We #code a remote web server
- 14. Web and Mobile apps are based on HTTP REST
- 15. REpresentational State Tranfer = REST
- 17. http://500px.com/photo/4766384 In the future, this chain will be connected to the Internet
- 18. http://500px.com/photo/26425201 We want to #code the (real) world.
- 19. Arduino is an open source microcontroller that you can use to hack things http://www.flickr.com/photos/mattrichardson/5029708468/
- 20. The Internet is our pillar
- 21. http://500px.com/photo/20050837 we want to monitor the seating of this room? What if
- 23. When you sit, we can receive an event
- 24. The world is event based!
- 25. Our control room is in the Cloud
- 26. How can we make Things talk? http://www.flickr.com/photos/iboy_daniel/77412822/in/photostream/
- 27. Pidgeons are not a communication protocol See RFC1149 http://500px.com/photo/32895129
- 28. http://www.flickr.com/photos/clearlyambiguous/48185613/ HTTP is slow and safe
- 29. We need a fast, binary protocol http://www.flickr.com/photos/grrphoto/305649629
- 31. • Binary • Publish/Subscribe • Free • Standard (in a few months)
- 32. How to use on
- 34. on Arduino: Setup String server = String("qest.me"); PubSubClient client = PubSubClient(server, 1883, callback);
- 35. if (!client.connected()) { client.connect("arduino"); } client.loop(); char s[10]; itoa(get_temperature(), s, 10); client.publish("temp", s); on Arduino: publishing
- 36. if (!client.connected()) { client.connect("arduino"); } client.loop(); char s[10]; itoa(get_temperature(), s, 10); client.publish("temp", s); This is called a topic, and it is where we publish data on MQTT. on Arduino: publishing
- 37. Your app cannot serve two masters. http://500px.com/photo/35382862
- 39. • MQTT broker • REST interface • can be deployed on top of very pub/sub systems • built in node.js QEST REST Server Redis MQTT Server QEST Data Layer HTTP Clients MQTT Clients
- 40. • Ascoltatori: the pub/sub library for node backed by Redis, MongoDB,AMQP (RabbitMQ), ZeroMQ, MQTT (Mosquitto) or just plain node: https://github.com/ mcollina/ascoltatori • Mosca, the multi-transport MQTT broker for node.js. It supports AMQP, Redis, ZeroMQ or just MQTT: https://github.com/mcollina/mosca • MQTT.js, the MQTT library for node: https:// github.com/adamvr/MQTT.js QEST’s pillars
- 41. Strings are the most common data format. http://500px.com/photo/28990737
- 43. Strings are not the better way of sending data What else
- 44. There are LOTs of choices • JSON • MessagePack • BSON • Bysant • Protobuf Size matters if we pay for every byte sent!
- 45. There are LOTs of choices
- 46. There are LOTs of choices Developers think in Lists and Maps, not in nodes and children. XML will not play a major role in the Internet of Things
- 47. • What devices can a user monitor? • What devices can 'listen' to the state of other devices? • Who can access the devices state? • Is the communication secure? Security Issues
- 48. We need to interconnect Users Social profiles to the Devices!
- 49. http://500px.com/photo/31083423 We need a Bridge between the REST and the “Things” world
- 50. http://500px.com/photo/31083423 • Multiple communication protocols • Data representation • Security and provisioning We need to address: From an end-user perspective
- 53. The initial contribution is QEST
- 54. will play well with the others
- 56. http://500px.com/photo/26425201 Ruby on Rails has drastically changed how web apps are built A 10-minutes blog video changed everything
- 57. http://500px.com/photo/26425201 We aim to a Rails-like experience for the IoT Our goal is to deliver a 10-minutes M2M app video
- 58. Credits • Font Awesome for the Icons. • Flickr and 500px for LOTS of CC images :). • Keynotopia for the iPad mockups
- 59. Matteo Collina ([email protected]) Thank You! @matteocollina http://www.flickr.com/photos/axel-d/479627824/