IOT and System Platform From Concepts to Code
Download as PPTX, PDF1 like1,254 views
The document presents an overview of IoT (Internet of Things) concepts, focusing on various data transmission protocols such as HTTP, XMPP, CoAP, AMQP, and MQTT, along with their benefits and drawbacks. It discusses the communication models and implementations relevant to IoT systems under the guidance of Andy Robinson, an expert in information solutions. The document also highlights specific examples of MQTT usage in system platform applications and provides resources for further exploration of these technologies.
IOT and System Platform From Concepts to Code
- 1. IOT and System Platform From Concepts to Code Andy Robinson Avid Solutions
- 3. Introductions • Andy Robinson • Information Solutions Consultant with Avid Solutions in Raleigh • 2 years as Principal at Phase 2 Automation in Taiwan • 10 years with Avid Solutions • 5 years with Monsanto/Solutia in Decatur, AL and Houston, TX • Co-Founder of aaOpenSource • The Archestranaut 1/10/2016 3
- 5. Overview/One-Eyed People I am NOT an expert In the land of the blind …the one eyed man is king 1/10/2016 5
- 6. Overview/My Definition of IOT What would/could you do differently if the cost to send data to/from your system approached $0? 1/10/2016 6 Sensor Transmitter I/O Channel Complex Machine Gateway Data Server Visualization Alarming Storage
- 7. Overview/Parts and Pieces • Many Moving Pieces Clients Data Transmission/ Receipt Servers Storage Visualization Analytics Notifications 1/10/2016 7
- 8. Overview/Data Transmission • Two Core Pieces • Transport • TCP – connection oriented, packets are confirmed and retransmitted if failed • UDP - connectionless , fire and forget • Protocol • HTTP • XMPP • CoAP • AMQP • MQTT 1/10/2016 8
- 9. Overview/Data Transmission/HTTP • Same core protocol as web page delivery • Uses a RESTful pattern (GET/POST) • Client-Server with Request/Response 1/10/2016 9
- 10. Overview/Data Transmission/HTTP • Benefits • Easy path through firewalls (HTTP/80, HTTPS/443) • Out of the box transport security with SSL/TLS • Very well known so easy to get started 1/10/2016 10
- 11. Overview/Data Transmission/HTTP • Drawbacks • Huge overhead from headers 700-800 bytes1 (should be better with HTTP/2) • RESTful patterns are inherently slow and require polling (1) http://dev.chromium.org/spdy/spdy-whitepaper 1/10/2016 11
- 12. Overview/Data Transmission/XMPP • eXtensible Messaging and Presence Protocol • XML over TCP • Originally started as a chat protocol to support contact lists and presence • Ask Eliot Landrum anything https://en.wikipedia.org/wiki/XMPP 1/10/2016 12
- 13. Overview/Data Transmission/XMPP • Benefits • Open standard • Flexible • Very mature (originated in 1999) https://en.wikipedia.org/wiki/XMPP 1/10/2016 13
- 14. Overview/Data Transmission/XMPP • Drawbacks • No QOS inherent at the protocol layer • Higher network overhead due to XML being text based https://en.wikipedia.org/wiki/XMPP 1/10/2016 14
- 15. Overview/Data Transmission/CoAP • Constrained Object Access Protocol • UDP but similar to HTTP with RESTful functions (GET/PUT/POST/DELETE) • Asynchronous communications model • Client-Server http://www.slideshare.net/rickgaribay/from-the-internet-of-things-to-intelligent-systems-a-developers-primer-garibay-final-34875117 http://www.realtimecommunicationsworld.com/topics/realtimecommunicationsworld/articles/408622-pros-cons-the-major-iot-communications-protocols.htm 1/10/2016 15
- 16. Overview/Data Transmission/CoAP • Benefits • Ultra small header (4 bytes) leads to ultra small packet sizes • DTLS for security • Combined with LWM2M for robust device management • Discovery methods built into protocol • Great for ultra low power, ultra low bandwidth • Datagram packet model can work over non IP transports like SMS • IETF Standard 1/10/2016 16 http://www.slideshare.net/rickgaribay/from-the-internet-of-things-to-intelligent-systems-a-developers-primer-garibay-final-34875117 http://www.realtimecommunicationsworld.com/topics/realtimecommunicationsworld/articles/408622-pros-cons-the-major-iot-communications-protocols.htm
- 17. Overview/Data Transmission/CoAP • Drawbacks • Core protocol is client-server with server initiated communications requires inbound packets to client device security concerns • As single client to single server there is no built-in concept of data broadcast 1/10/2016 17 http://www.slideshare.net/rickgaribay/from-the-internet-of-things-to-intelligent-systems-a-developers-primer-garibay-final-34875117 http://www.realtimecommunicationsworld.com/topics/realtimecommunicationsworld/articles/408622-pros-cons-the-major-iot-communications-protocols.htm
- 18. Overview/Data Transmission/AMQP • Advanced Message Queue Protocol • Originally developed by big financial orgs for middleware messaging • Message oriented binary protocol typically over TCP • OASIS Standard https://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol 1/10/2016 18
- 19. Overview/Data Transmission/AMQP • Benefits • Built for resiliency and scaling • Load balancing patterns • Messages can contain payload and metadata • Powerful routing patterns • Security based on SSL/TLS 1/10/2016 19
- 20. Overview/Data Transmission/AMQP • Drawbacks • Not lightweight – built with servers and fat networks in mind (60 byte minimum packet size) • Can be complex to implement client – thanks Paolo for SBLite 1/10/2016 20
- 21. Overview/Data Transmission/MQTT • Message Queue Telemetry Transport • Created by IBM to support oil pipeline telemetry data over slow, unreliable networks • TCP Transport • Publish-Subscribe with Broker Model 1/10/2016 21 http://www.slideshare.net/rickgaribay/from-the-internet-of-things-to-intelligent-systems-a-developers-primer-garibay-final-34875117 http://www.realtimecommunicationsworld.com/topics/realtimecommunicationsworld/articles/408622-pros-cons-the-major-iot-communications-protocols.htm
- 22. Overview/Data Transmission/MQTT • Benefits • Very small header (7 bytes) leads to very small packet sizes • TLS for security • Great for low power, low bandwidth • No incoming connection to client much more secure • 3 levels of QOS • OASIS Standard 1/10/2016 22 http://www.slideshare.net/rickgaribay/from-the-internet-of-things-to-intelligent-systems-a-developers-primer-garibay-final-34875117 http://www.realtimecommunicationsworld.com/topics/realtimecommunicationsworld/articles/408622-pros-cons-the-major-iot-communications-protocols.htm
- 23. Overview/Data Transmission/MQTT • Benefits - Small size and low overhead 1/10/2016 23 https://mobilebit.wordpress.com/2013/05/03/rest-is-for-sleeping-mqtt-is-for-mobile/
- 24. Overview/Data Transmission/MQTT • Drawbacks • TCP is connection oriented so more complex to put device to sleep (MQTT-S supports UDP) • No standard model for metadata and discoverability • No standard method for device management http://www.slideshare.net/rickgaribay/from-the-internet-of-things-to-intelligent-systems-a-developers-primer-garibay-final-34875117 http://www.realtimecommunicationsworld.com/topics/realtimecommunicationsworld/articles/408622-pros-cons-the-major-iot-communications-protocols.htm 1/10/2016 24
- 25. Overview/Data Transmission/Winner • And the best protocol is…the one that matches your requirements and capabilities • One of many comparisons • www.slideshare.net/paolopat/mqtt-iot-protocols-comparison • Would also love to talk about DDS (ultra high performance, data-centric) • ….. but let’s talk about MQTT 1/10/2016 25
- 26. MQTT – The Details 1/10/2016 26
- 27. MQTT/Details/Transport • Utilizes single, duplex, persistent TCP connection for transport • Client connects to broker and broker sends data back down the connection • Broker NEVER connects directly to client. Security Win! • Client can use SSL/TLS to connect to Broker. Security Win! • Many brokers support authentication and ACL Client Broker (Server) 1/10/2016 27
- 28. MQTT/Details/Communication Model • Pub/Sub with Central Broker • Conceptually similar to Mxaccess in System Platform http://www.codeproject.com/KB/IP/PubSubUsingWCF/pubsub.png 1/10/2016 28
- 29. MQTT/Details/Broker • Broker is meeting point for publishers and subscribers • Many different brokers available • Run locally or in the cloud 1/10/2016 29
- 30. MQTT/Details/Broker • Local • mosquitto – The old man of the brokers, full featured, easy, single exe • GnatMQ – written in C#, open source • HiveMQ – extra features, commercial, extensible • Mosca – node.js, open source • Verne.MQ – written in Erlang, scalable and resilient, open source 1/10/2016 30
- 31. MQTT/Details/Broker • Cloud • CloudMQTT – uses mosquitto • Verne.MQ - extensible, highly available • Public testers – test.mosquito.org, broker.mqtt-dashboard.com, … 1/10/2016 31
- 32. MQTT/Details/Topics • Mailboxes organized into folders • “/” separates the folders • Wildcards • Single Level “+” • home/+/temp home/1/temp home/2/temp • Multi-Level “#” • /home/# home/1/temp home/2/temp home/1/rh home/2/rh1/10/2016 32
- 33. MQTT/Details/Topics vs Queues Feature Topics Queues Big Idea Real Time Asynchronous FIFO/Stack Dropped Data Can Be OK (but QOS) Never Ok Pub/Sub Yes Partial (only one client) Applications Sensor Data Alarms Alarms Events Value History “Client” Broker Topics Queue Value Alarms Events HMI Historical Values, Alarms, Events HMI HMI HMI Publish Subscribe Timestamped Values Alarms Events 1/10/2016 33
- 34. MQTT – The Code 1/10/2016 34
- 35. MQTT/Code/Client Library • You only need a client library to pub and sub .. unless you want to run a broker too • Client libraries for almost every language • Best C# library is M2MQTT from Paolo Patierno • Open Source • Full Featured • Nuget Package Available 1/10/2016 35
- 36. MQTT/Code/Pseudocode Create Client Set Options (ClientID, SSL/TLS?, QOS, Credentials) Connect to Single Broker by Name or IP Address ….. Subscribe to Topic(s) Receive Callback for Subscribed Topic …. Publish UTF-8 encoded binary data to Topic(s) 1/10/2016 36
- 37. MQTT/Code/System Platform/Publish … Declarations…. configHost = "localhost"; configclientID = Me.Tagname; MQTTClient = new uPLibrary.Networking.M2Mqtt.MqttClient(configHost); MQTTClient.Connect(configclientID); if (MQTTClient.IsConnected) then Topic = "data/" + Me.Tagname + "/value"; MQTTClient.Publish(Topic,System.Text.Encoding.UTF8.GetBytes(Me.Value)); endif; 1/10/2016 37
- 38. MQTT/Code/System Platform/Subscribe • Not possible due to requirement for callback registration • But you can use the AOT – been there done that.. mostly _mqttClient.MqttMsgPublishReceived += _mqttClient_MqttMsgPublishReceived; _mqttclient.subscribe(Topic) … void _mqttClient_MqttMsgPublishReceived(object sender, MqttMsgPublishEventArgs e) { Process new message e } 1/10/2016 38
- 39. MQTT – The Demos 1/10/2016 39
- 40. MQTT/Demo • Demo 1 – Publishing simple data from System Platform 1/10/2016 40
- 41. MQTT/Demo • Demo 2 – Publishing complex data from System Platform 1/10/2016 41
- 42. MQTT/Demo • Demo 3 – Subscribing to Data “in” System Platform 1/10/2016 42
- 43. MQTT/Demo • Demo 4 – MQTT Wonderware Historian (no System Platform) 1/10/2016 43
- 44. MQTT/Demo • Demo 5 – MQTT Node-Red ?? • MQTTWarn 1/10/2016 44 amqp apns asterisk carbon dbus dnsupdate emoncms file freeswitch gss http instapush irccat linuxnotify log mqtt mqttpub mysql mysql_dynamic mythtv nma nntp nsca osxnotify osxsay pastebinpub pipe prowl pushalot pushbullet pushover redispub rrdtool slack sqlite smtp syslog twilio twitter xbmc xmpp xively zabbix
- 45. MQTT – Resources 1/10/2016 45
- 46. MQTT/Resources • MQTT.org • Paolo! - m2mqtt.wordpress.com/ • Eclipse paho- www.eclipse.org/paho/ • AMQP on Microsoft Azure - github.com/ppatierno/azuresblite • Talk to Alvaro Martinez about the new OI Server for MQTT! • aaOpenSource Github Repo github.com/aaOpenSource/aaMQTT 1/10/2016 46
- 48. Wrap-Up/Takeaways • Just a seed • No solutions, just ideas • Take these concepts and scale up • Consuming public MQTT data – weather? Energy prices? • Disconnected warehouse with no VPN – real situation with current customer • We are all now composers, not luthiers 1/10/2016 48
- 49. Wrap-Up/Upcoming Talks • October 8 – Avid Solutions, Atlanta • IOT – similar talk • Basic of good security hygiene • October 20 – All Things Open – Raleigh • Dear Open Source: Please help. Love, Manufacturing 1/10/2016 49
Editor's Notes
- #7: Not going to try to one up what’s been said by many people smarter than me have defined IOT in terms of the technology and the promise for hundreds of trillions of dollars in savings. Instead when I think of IOT I think about a mindset. That mindset being “what would you…”
- #8: So when you dive a little deeper you find a lot of moving parts when it comes to tx/rx of IOT data. In this talk I’m going to focus almost exclusively on the data transmission and receipt part. So… let’s get started because I’ve got about 50 slides to get through.. With demos…
- #9: Any time you send/receive data over a network you have to consider both the transport and the protocol. For transport you’ve got two primary options, TCP and UDP. The simplistic difference between the two is that TCP confirms receipt of a packet, allowing for retransmission if it doesn’t make it while UDP does not. This makes UDP a lot lighter weight and easier to wake up and send data but you have to deal with a lot of issues yourself. The next part is the protocol. And that’s what I’m about to spend a lot of time talking about. The protocol is how the two ends of the conversation know how to interpret the packets flying back and forth.
- #10: So first up, HTTP. This is your old school method for delivering web pages but with a new twist, a RESTFUL pattern. Without getting too far into it, RESTful patterns are a way you can use existing HTTP verbs like GET/POST, etc. and specially formulated URL’s to get data and send data to the server. But fundamentally this is a request/response pattern where every time you want data it’s a new independent transaction as well as sending data.