Implementierungskonzepte für das. Internet der Dinge

Transkript

1 Implementierungskonzepte für das Renate Franken Internet der Dinge

2 Context Das Internet der Dinge Technology MQTT MQ Telemetry Transport WebSphere MQ Telemetry Demo Future Use Cases 2

3 The Internet of Things Das Internet der Dinge Video Viele digitale Einheiten instrumentieren unsere Welt bereits heute Verknüpft die virtuelle mit der realen Welt 3 In 2020 ist alles miteinander verbunden, geschätzte 60 Milliarden Smart Devices Gartner

4 Einige Zahlen 2005 waren 1.3 Milliarden RFID Tags im Umlauf sind es mehr als 33 Milliarden Source : Gartner Geschätzte 2 Milliarden Menschen sind 2011 im Internet... und Milliarden von verbundene Objekte Pipelines, intelligente Stromzähler, Fahrzeuge, Maschinen, techn. Geräte, 4 4 zusammengefaßt als das Internet der Dinge

5 Wir bauen einen smarten Planeten + + = Instrumeted Interconnected Intelligent Die Herausforderung neu zu denken und zu handeln ökonomisch, sozial und technisch. 5

6 Connectivity für smarte Verbindungen intelligent Erweitert Verbindungen über Unternehmensgrenzen hinaus zu den intelligenten Geräten interconnected Ermöglicht optimiert Anbindungen für Sensoren und intelligente Geräte (M2M) Erlaubt massive Skaliberbarkeit im Einsatz und Betreiben von Lösungen Liefert relevante Daten für intelligente Entscheidungen instrumented 6

7 Context Das Internet der Dinge Technology MQTT MQ Telemetry Transport WebSphere MQ Telemetry Demo Future Use Cases 7

8 Schlüsselfaktoren von MQ Telemetry Transport MQTT Protokoll Die MQTT Spezifikationen sind offen Klein, reduziert die Komplexität und Systemanforderungen Einfach / minimale pub/sub Nachrichten Semantik Asynchrone ( push ) Nachrichtenauslieferung an Anwendungen Einfache Aufrufe wie connect, publish, subscribe und disconnect. Minimalisierte Nachrichtenübertragungslänge Protokoll mit komprimiert mit bit-wise Header und variablem Längenfeld Kleinste mögliche Nachricht ist 2 Bytes. Byte Array Nachrichteninhalt ohne zusätzlichen Anwendungsheader Eingebaute Unterstützung bei Verbindungsabbruch. Last will and testament wird publiziert wenn die Client Verbindung abbricht Stateful roll-forward Semantik und durable Subskriptionen. 8

9 Qualities of Service Drei Quality of Services publizierter und subskribierter Nachrichten QoS 0: At most once delivery (non-persistent) Keine Wiederholversuche sind im Portokoll definiert. Die Nachricht wird höchstens einmal geschickt, die Nachricht kommt entwerder einmal an oder nie QoS 1: At least once delivery (persistent, dups possible) Client schickt Nachricht mit Message ID im header Server bestätigt mit einer PUBACK Nachricht Message wird wiederholt geschickt mit einem DUP bit gesetzt falls keine PUBACK erhalten wurde QoS 2: Exactly once delivery (persistent) Zusätzlicher Nachrichtenaustausch um Sicherzustellen dass die Nachricht nicht dupliziert geschickt wird Server bestätigt mit einer PUBREC Nachricht Client entläßt die Nachricht mit einer PUBREL Nachricht Server bestätigt Abschluß mit einer PUBCOMP Nachricht 9

10 WebSphere MQ Telemetry implementiert MQTT WebSphere MQ Telemetry integriert mit WebSphere MQ Publizierer und Subskribtoren können über MQI oder JMS Nachrichten austauschen Out of the box installierbar mit MQ7.1 Basic Telemetry Client Ist hoch skallierbar An einen MQ Queue Manager können über 100,000 gleichzeitig verbundene Devices angebunden werden Wird mit 2 verschiedene Clients ausgeliefert: Basic direkte Verbindung von einem Device Advanced Deamon for Devices Agiert als Konzentrator/Hub for kleine Telemetry Device Netzwerke Kann sich zu mehreren Backend Server verbinden Unterstützt alternativen Backendserver im Fehlerfall Kann Nachrichten zwischenspeichern oder locale Devices verbinden Backend Server WebSphere MQ MQXR Zusätzlich kann jeder third party oder Open Source MQTT Client verwendet werden unterstützt MQTT v3.1 Protokoll Umfangreiche Sicherheit Networkverschlüsselung: SSL Authentifikation: JAAS 10 Authorisierung: OAM MQ Telemetry Daemon for Devices Advanced Telemetry Client

11 MQ Explorer Integration 11

12 Example: connect and send an MQTT message public void sendamessage() throws MqttException { MqttProperties mqttprops = new MqttProperties(); mqttprops.setcleanstart( true ); MqttClient client = MqttClientFactory.INSTANCE. createmqttclient("testclient", tcp://localhost:1883, mqttprops); client.registercallback(this); client.connect(); client.publish( abc/123, new MqttPayload(( Hello World! ).getbytes(),0), (byte) 2, false); client.disconnect(); } Create a connection using the connection factory, this time for a clean starting client Register the class as a listener and connect to the broker Publish a message to the given topic and disconnect public void publisharrived(string topicname, MqttPayload payload, byte qos, boolean retained, int msgid) { System.out.println( Got it! ); } On receipt of a publication, simply print out a message on the console to say we received it 12

13 Topologie Beispiel: Enterprise Gateway Web Services HTTP Multiplex devices at edge of enterprise Integrate any-to-any via WMB WebSphere Message Broker WebSphere MQ Telemetry WebSphere MQ CICS, IMS DB Files MQXR 13

14 HTTP und MQTT Vergleich bzgl. Datentransfer MsgFlow C = Client S = Server HTTP Bytes MQTT (Data) Bytes C -> S S -> C C -> S Send Msg POST HTTP/1.1 Content-Length: 7 Content-Type: text/xml; charset=utf-8 Host: :7080 SOAPAction: "" Connection: keep-alive X-Remote-Addr: X-Remote-Host: X-Server-Name: X-Server-Port: 7080 X-Scheme: http Message 316 (66) Connect -> D E00046D Connack (Server Acknowlege) < Publish Msg: 3A0F F D S -> C Ackn Back POST /post HTTP/1.1 Host: localhost Content-Length: 7 message HTTP/ OK Content-Type: text/xml;charset=utf-8 Content-Length: 7 Date: Mon, 10 Oct :08:00 GMT Server: Apache-Coyote/1.1 Message 147 (75) Pubback (server Acknowlege for QoS1) C -> S HTTP/ OK Date: Mon, 10 Oct :08:00 GMT Content-Length: 0 Disconnect: E Total 463 (141) 47

15 MQ Telemetry Transport versus HTTP(S) MQTT ist Datenzentrisch gegenüber Dokumentenzentrischen HTTP MQTT ist einfach: connect publish/subscribe disconnect MQTT ist bidirektional für 'always-on' Devices (push zum Client anstatt pull vom Server) MQTT hat optimierte Nachrichtenlänge (im Vergleich HPPT vs. MQTT QoS1) MQTT verteilt Nachrichten 1:1, 1:vielen über pub/sub, vs. Http über Point-to-Point Zuverlässiges MQTT ünterstützt verschiedene Quality of Service (fire and forget oder fire and confirm) vs. unzuverlässigem HTTP Skalierbar (> Clients /Qmgr) Gut integriert in WebSphere MQ Weniger Batterieverbrauch als HTTP Weniger Übertragungsdaten bedeutet auch weniger Daten zu Verarbeitung im Back-end 15 Scenario HTTP MQTT 10 Bytes Msg lesen vom Server 126 bytes 69 bytes 10 Bytes Msg schreiben auf den Server 141 bytes 47 bytes 100 Msgs lesen vom Server bytes 2445 bytes 100 Msgs schreiben auf den Server bytes 2126 bytes 1 Msg alle 15 Minuten 365 Tage (ca Msg) 1 Msg alle 15 Minuten 365 Tage SSL (HTTPS vs MQTT-SSL) ca. 5 MB ca. 219 MB ca 0,7 MB ca.23mb

16 MQ Telemetry PoC Ergebnisse beim Kunden Advantages of WebSphere MQ Telemetry (MQT) MQT Clients have a lower footprint on the devices (around 100kB) First testcases run within a day without problems MQT is stable and well encapsulated API MQT supports different quality of services to assure message delivery MQT is real bi-directional (without fake and repeating polling from the server) MQT is fast (in comparison to tests with CometD to toggle 1000 messages between Androids Apps results in twice faster message exchange with MQ Telemetry as CometD. Average with CometD was around 200ms for a msg roundtrip) 16

17 WebSphere und das Internet der Dinge Internet der Dinge DataPower (with MQTT Extended Reach client for passthru to MQ) Cast Iron - Mobile Devices HTTP MQTT WebSphere Mobile Technology Preview - Worklight Build Control Governance Intelligence: Cognos, ILOG,SPSS, WebSphere Business Events, BPM, - Embedded Controler - Sensor MQTT IBM WebSphere MQ Queue Manager A WebSphere Message Broker MQ JMS HTTP WebService Enterprise Applications - Actuators MQ Telemetry Transport Messaging integration hub and logic systems MQ / JMS / HTTP MQ Server is used for scale 17 Firewall + + =

18 MQTT Client on Android - Experiences Push Notification Real-time Alerts Analytics Tracking Assured Delivery Rich Framework Two-way Communication Rich / HTML Messages Status Channels Security Simple Low Bandwidth & Cost Very efficient bandwidth usage Much cheaper alternative to SMS Low Power Usage % % % Battery per Hour 18

19 Context Das Internet der Dinge Technology MQTT MQ Telemetry Transport WebSphere MQ Telemetry Demo Future Use Cases 19

20 Ausblick: Erweiterte Anbindung MQ Web Messaging Bietet Anbindung für Business to Customer (B2C) Business to Employee (B2E) Von mobilen and festinstallierten Einheiten mit einem modernen web browser Basiert auf Erweiterungen (MQ Telemetry) für WebSphere MQ MQ Web Messaging wird für die folgenden primären Absichten entwickelt: 1st class web support aufbauend auf Websockets, ein Web Standard (IETF and w3c) Zielgerichted für eine neue Klasse von hochwertigen Internet Anwendugen die in einem Web Browser laufen Bietet effizentes Nachriten und Ereignis Verteilung von und zu einem Web Browser. Im Gegensatz zu HTTP können Nachriten/Events in beide Richtungen geschickt werden. Ein publish/subscribe Nachrichten Paradigma zugreifbar via JavaScript API Bietet traditionelles Messaging Service-Qualität für moderne Wege 20 Einzelheiten Einzelheiten können können noch noch geändert geändert werden werden

21 Context Das Internet der Dinge Technology MQTT MQ Telemetry Transport WebSphere MQ Telemetry Demo Future Use Cases 21

22 Smarter Healthcare Medical organization created a remote pace-maker monitoring solution to provide better patient care Client Pains Physicians needed better monitoring of cardiac patients Improve efficiency of checkups Meet healthcare data capture standards Enables higher level of patient care and peace of mind Improves administrative efficiency and maintenance Helps conform to standards and ease integration of data 22

23 Improving Energy Usage Utility company developing an Intelligent Utility Network offering for optimizing load on electricity grids Business Partner Needs robust middleware technology to connect to remote smart meters Needs to be able to rapidly scale solution nationally Able to offer daily energy savings of 15-20% Enables utilities to reduce peaks and avoid punitive charges Helps save electricity through better peak load management 23

24 Facebook Messenger Lucy Zhang, a software engineer at Facebook, has written about their new Facebook Messenger app: One of the problems we experienced was long latency when sending a message. The method we were using to send was reliable but slow, and there were limitations on how much we could improve it. With just a few weeks until launch, we ended up building a new mechanism that maintains a persistent connection to our servers. To do this without killing battery life, we used a protocol called MQTT that we had experimented with in Beluga. MQTT is specifically designed for applications like sending telemetry data to and from space probes, so it is designed to use bandwidth and batteries sparingly. By maintaining an MQTT connection and routing messages through our chat pipeline, we were able to often achieve phone-to-phone delivery in the hundreds of milliseconds, rather than multiple seconds. 24

25 Device Management Car Tracking 25

26 Mein Stromverbrauch zu Hause mit Android Anbindung 26

27 Mein Stromzähler 27

28 Das Display (über USB Kabel verbunden) 28

29 Mein derzeitiges MQTT Projekt 29

30 Weiter mögliche Einsatzgebiete für MQTT Water Management Grid Food Safety Logistics Healthcare Transportation Retail Home Automation Finance 30

31 Easy to try out! Really small message broker: Download rsmb zip Unzip Run nohup./broker >> /dev/null & Play with C client utils, code, and be merry! Available for Linux IA32, IA64 kernel ; Linux on IBM System z; Linux for ARM XScale, kernel (Crossbow Stargate or Eurotech Viper); Windows XP; Mac OS X Leopard; Unslung (Linksys NSLU2) Binary only, request other platforms from IBM 31

32 Broader integration Simple Lightweight (CPU,Mem,**Net) Data-centric Distribution (pub/sub) Range of QoS => developer/community interest! 32

33 MQTT.org: Latest News 33

34 Nützliche links Announcement Letter P MQTT The Smarter Planet Protocol (blog post) MQTT 3.1 specification IBM developerworks WebSphere MQ Telemetry Performance Evaluation SupportPac MP0A 8&lang=en MQTT Community 34

35 We love our users! developerworks MQSeries.net community Global WebSphere Community GWC MQTT IBMer's Blog on Messaging on developerworks YouTube Podcasts - Store and Forward T.Rob's WMQ Security blog Open, vibrant ecosystem e.g. PyMQI, mosquitto, github projects, etc. etc

36 Fragen? Mobile: /

37 37

38 Legal Disclaimer IBM Corporation All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus Sametime Unyte ). Subsequent references can drop IBM but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to for guidance on which trademarks require the or symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. If you reference Adobe in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. If you reference Java in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. If you reference Microsoft and/or Windows in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. If you reference Intel and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. If you reference UNIX in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries. If you reference Linux in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only. 38