Presentation for IoT workshop at Sinhagad University (Feb 4, 2016) - 1/2
2 likes664 views
The document provides a comprehensive overview of the Internet of Things (IoT), discussing its definition, protocols such as MQTT, COAP, and HTTP, and their respective advantages and disadvantages. It covers hardware and software considerations, implementation practices, and future projections for IoT applications, including smart cities. The session concludes with a hands-on activity focused on creating a minimal viable prototype using the concepts learned.
![The Internet of Things (IoT) is the network of physical objects, devices, vehicles, buildings and
other items which are embedded with electronics, software, sensors, and network connectivity, which
enables these objects to collect and exchange data.[1]
The Internet of Things allows objects to be
sensed and controlled remotely across existing network infrastructure,
[2]
creating opportunities for
more-direct integration between the physical world and computer-based systems, and resulting in
improved efficiency, accuracy and economic benefit
"Things," in the IoT sense, can refer to a wide variety of devices such as heart monitoring implants,
biochip transponders on farm animals, electric clams in coastal waters,[15]
automobiles with built-in
sensors, DNA analysis devices for environmental/food/pathogen monitoring
[16]
or field operation
devices that assist firefighters in search and rescue operations.
[17]
These devices collect useful data
with the help of various existing technologies and then autonomously flow the data between other
devices
Source: Wikipedia](https://image.slidesharecdn.com/internetofthings1-160206143020/85/Presentation-for-IoT-workshop-at-Sinhagad-University-Feb-4-2016-1-2-6-320.jpg)
Presentation for IoT workshop at Sinhagad University (Feb 4, 2016) - 1/2
- 2. HELLO! I am Bhavin I am here because I love technology You can find me at @BhvainIoT IIT Madras - grad. May 2014: M.Tech (Dual Degree) Co-founder AviPulse - Jan 2014 - present Co-founder Phaneron Inc. - Launching in Apr 2016
- 3. Logistics Takeoff Session (Protocols): Introduction to IoT Protocols: MQTT, CoAP, HTTP MQTT in depth: Headers, QoS, Topics, Persistence & Will Conclusion: Comparison of protocols Consolidation Session (Implementation): Hardware: Arduino, ESP8266 & NodeMCU, Raspberry Pi, UDOO Software: Brokers, APIs, Frameworks Practices: Cloud, Battery Life, Mobile Apps, Securit Future: Smart Cities, Mission 2020 Hands-on Session (Demo): The Participants will form groups and make a hands on “Minimal Viable Prototype” demo using lean principles and concepts learned in the above sessions 120 mins 10 mins 30 mins 60 mins 20 mins 120 mins 40 mins 40 mins 30 mins 10 mins 120 mins
- 4. 1. Introduction Let’s start with the basics
- 5. Big Picture What is IoT really?
- 6. The Internet of Things (IoT) is the network of physical objects, devices, vehicles, buildings and other items which are embedded with electronics, software, sensors, and network connectivity, which enables these objects to collect and exchange data.[1] The Internet of Things allows objects to be sensed and controlled remotely across existing network infrastructure, [2] creating opportunities for more-direct integration between the physical world and computer-based systems, and resulting in improved efficiency, accuracy and economic benefit "Things," in the IoT sense, can refer to a wide variety of devices such as heart monitoring implants, biochip transponders on farm animals, electric clams in coastal waters,[15] automobiles with built-in sensors, DNA analysis devices for environmental/food/pathogen monitoring [16] or field operation devices that assist firefighters in search and rescue operations. [17] These devices collect useful data with the help of various existing technologies and then autonomously flow the data between other devices Source: Wikipedia
- 7. → Hardware agnostic → Software agnostic → Protocols matter ! → Concerns: ↠ Battery life, energy consumption ↠ Connectivity vs Security ↠ Processing Power & Memory Ideal IoT solution
- 8. 2. Protocols HTTP, MQTT, CoAP
- 9. OSI Model
- 10. Bits & Frames - Wireshark
- 11. Protocols in Transport Layer
- 12. Protocols in Transport Layer
- 13. TCP/IP and UDP → (Slightly more than) Transport Layer Protocols ↠ TCP/UDP contain functions such as graceful close that OSI assigns to Session Layer ↠ They are closest to class 4 (TP4) of OSI TCP: Reliability over Latency UDP: Latency over Reliability
- 14. TCP → TCP provides reliable, ordered, and error- checked delivery of a stream of octets between applications running on hosts communicating over an IP network → The sequence (SEQ) of octets matters → Receiver has to acknowledge (ACK) and synchronize (SYN) the sequence with the transmitter
- 15. TCP
- 16. TCP
- 17. UDP → With UDP, computer applications can send messages, in this case referred to as datagrams, to other hosts on an Internet Protocol (IP) network without prior communications to set up special transmission channels or data paths → Un-sequenced data with no ACK or error handling
- 18. UDP
- 19. TCP → Reliable → Ordered → Heavyweight → Slow(er) → Streaming → Congestion Control → Unicast (1 to 1) TCP vs UDP UDP → Unreliable → Unordered → Lightweight → Fast(er) → Datagrams → No Congestion Control → Broadcast (1 to many) Multicast (many to many)
- 20. Protocol Stacks → HTTP: TCP like session on top of TCP → MQTT: UDP like session on top of TCP → CoAP: TCP like session on top of UDP (also, it has binary headers)
- 21. This is a slide title → Here you have a list of items → And some text → But remember not to overload your slides with content You audience will listen to you or read the content, but won’t do both.
- 22. HTTP → The Hypertext Transfer Protocol (HTTP) is a protocol for distributed, collaborative, hypermedia information systems → HTTP functions as a request response protocol in a client-server computing model → HTTP resources are identified and located on the network by uniform resource locators (URLs), using the uniform resource identifier (URI) schemes http and https. URIs and hyperlinks in HTML documents form inter- linked hypertext documents → URI:
- 23. HTTP
- 24. HTTP Methods/Verbs → GET*$ → POST$ → PUT$ → DELETE$ → HEAD* → CONNECT → PATCH → TRACE* → OPTIONS* * No changes to database $: REST API
- 25. HTTP → HTTP is a stateless protocol. A stateless protocol does not require the HTTP server to retain information or status about each user for the duration of multiple requests. → However, some (read: most) web applications implement states or server side sessions using for instance HTTP cookies or hidden variables within web forms
- 26. MQTT → MQTT is Client-Server publish/subscribe messaging transport protocol → It is lightweight, simple, open, and designed to be as easy to implement → It runs over TCP/IP but can be implemented over any stack that provides ordered, lossless, bi-directional connections → MQTT is an OASIS standard since v3.1.1 (current version) Note: MQTT = MQ Telemetry Transport. MQ doesn’t stand for message queue. Infact there’s NO queuing in MQTT
- 27. MQTT
- 28. MQTT
- 29. CoAP → Constrained Application Protocol → Works over UDP. Has Binary Headers → Provides a RESTful API over UDP → CoAP was the de-facto “IoT” protocols since before IoT was mainstream → It is especially useful in embedded devices with limited processing power and memory → But it hasn’t aged well with Moore’s law → With competition in IoT hardware market, a lot powerful devices are available for cheap
- 30. CoAP
- 31. CoAP
- 32. 3. Diving into MQTT All about MQTT Protocol
- 33. MQTT
- 34. MQTT
- 35. MQTT
- 36. MQTT
- 37. MQTT
- 38. MQTT
- 39. MQTT
- 40. MQTT
- 41. MQTT
- 42. MQTT
- 43. MQTT
- 44. MQTT
- 45. MQTT
- 46. MQTT
- 47. 4. Conclusion An Overview of what we’ve covered
- 48. Comparisons: MQTT vs HTTP
- 49. Comparisons: MQTT vs CoAP
- 50. THANKS! Any questions? See you in the next session! I’m Bhavin Chandarana, find me at → @BhavinIoT → bhavin@phaneronsystems.com → +91-8380013130 | +91-9840425583 Do Checkout: http://www.meetup.com/Internet-Of-Things-Pune-IoTPune