Eclipse IOT [IoT World Santa Clara]
•Télécharger en tant que PPTX, PDF•
1 j'aime•1,817 vues
Presentation given at IoT World in Santa Clara.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Eclipse IOT [IoT World Santa Clara]
Similaire à Eclipse IOT [IoT World Santa Clara] (20)
Plus de Ian Skerrett
Plus de Ian Skerrett (20)
Dernier
Dernier (20)
Eclipse IOT [IoT World Santa Clara]
- 1. 3 Software Stacks for IoT Solutions Ian Skerrett Eclipse Foundation @ianskerrett
- 2. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Eclipse Foundation • Not-for-profit open source foundation responsible for the Eclipse community • 320+ open source projects • Working groups for Geo-spatial tech, IoT, System engineering and embedded dev., Science, Automotive, … • 250+ members
- 3. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Typical IoT Architecture Devices (sensors & actuators) Applications telemetry commands telemetry commands IoT Cloud Platform Gateways
- 4. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Role & Characteristics DEVICE GATEWAY / SMART OBJECT CLOUD PLATFORM constrained low-power specialized connectivity messaging edge computing scale out integration data analytics
- 5. Copyright © 2016 The Eclipse Foundation. All Rights Reserved The 3 IoT Software Stacks TOOLS & SDKsONTOLOGIESSECURITY CONSTRAINED DEVICES Hardware Abstraction Layer (HAL) OS / RTOS Communication Remote Management Field protocols IoT protocols IOT CLOUD PLATFORM Connectivity MessageRouting OS / PaaS Device Management Data Management Event Management, Analytics & UI Device Registry Application Enablement GATEWAYS AND SMART DEVICES RemoteManagement Application Runtime Data Management & Messaging OS / RTOS Connectivity Field protocols IoT protocols Network Management
- 6. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Communication IoT Device Stack OS / RTOS* * optional timers, tasks, file system, … API enabling access to memory, GPIOs, MEMS, serial interfaces ,… Protocols such as Bluetooth, Z-Wave, Thread, CAN bus, MQTT, CoAP, … over-the-air firmware upgrade, health monitoring, factory reset, … OS / RTOS Hardware Abstraction Layer (HAL) Remote Management Hardware Abstraction Layer (HAL) OS / RTOS Communication Remote ManagementField protocols IoT protocols CONSTRAINED DEVICES
- 7. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Application Runtime Network Management Data Management & Messaging IoT Gateway Stack connect to different types of networks ensure reliability, security (VPN, firewall, …) local persistence (network latency) offline mode data analytics at the edge Virtual Machine / Application container GATEWAYS AND SMART DEVICES RemoteManagement Application Runtime Data Management & Messaging OS / RTOS Connectivity Field protocols IoT protocols Network Management
- 8. Copyright © 2016 The Eclipse Foundation. All Rights Reserved IoT Cloud Platform Stack ingest and normalize huge amounts of data into an enterprise backend identify devices, allow for over-the-air software provisioning, configuration changes, … scalable data store, time series IOT CLOUD PLATFORM Connectivity MessageRouting OS / PaaS Device Management Data Management Event Management, Analytics & UI Device Registry Application Enablement Connectivity Message Routing Device Registry Device Management Data Management
- 9. Copyright © 2016 The Eclipse Foundation. All Rights Reserved IoT Cloud Platform Stack (cont’d) scalable event processing create reports, graphs, dashboards, … make decisions based on the data expose API for application integration Event Management, Analytics & UI Application Enablement IOT CLOUD PLATFORM Connectivity MessageRouting OS / PaaS Device Management Data Management Event Management, Analytics & UI Device Registry Application Enablement
- 10. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Cross-layer concerns SECURITY ONTOLOGIES TOOLS
- 11. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Characteristics of Open IoT Stacks loosely coupled modular platform-independant based on open standards API
- 12. Copyright © 2016 The Eclipse Foundation. All Rights Reserved
- 13. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Eclipse IoT Community 2.2 29* 210+ 110K million lines of code projects developers monthly visitors * and counting!
- 14. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Eclipse IoT… from building blocks … to stacks …
- 15. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Hardware Abstraction Layer (HAL) OS / RTOS Communication Remote Management Field protocols IoT protocols CONSTRAINED DEVICES OS Stack for IoT Devices Wakaama C implementation of OMA LWM2M Portable on any POSIX-compliant system C implementation of MQTT 3.1.1 < 2,000 lines of C ANSI code JAVA API for MCUs “Android for IoT” Hardware Abstraction Layer (HAL) OS / RTOS Communication Remote Management Field protocols IoT protocols CONSTRAINED DEVICES OS Stack for IoT Devices Wakaama C implementation of OMA LWM2M Portable on any POSIX-compliant system C implementation of MQTT 3.1.1 < 2,000 lines of C ANSI code JAVA API for MCUs “Android for IoT”
- 16. Copyright © 2016 The Eclipse Foundation. All Rights Reserved OS Stack for IoT Gateways OSGi implementation Native support for MQTT Serial, RS-485, BLE, MODBUS, OPC-UA, CAN Bus, … NAT, firewall, modem configuration, … Remote Management over MQTT Milo GATEWAYS AND SMART DEVICES RemoteManagement Application Runtime Data Management & Messaging OS / RTOS Connectivity Field protocols IoT protocols Network Management
- 17. Copyright © 2016 The Eclipse Foundation. All Rights Reserved GATEWAYS AND SMART DEVICES RemoteManagement Application Runtime Data Management & Messaging OS / RTOS Connectivity Field protocols IoT protocols Network Management OS Stack for Home Automation OSGi implementation Rule engine to orchestrate “things” Home automation protocols such as Belkin WeMo, LIFX, Philips Hue, … Remote firmware update through the GW Web UI and API for remote control
- 18. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Device Management Device Registry OS Stack for IoT Cloud OMA LWM2M implementation in Java built on top of Eclipse Californium (CoAP) Manage software upgrade campaigns independently of the actual DM protocol IOT CLOUD PLATFORM
- 19. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Eclipse hawkBit
- 20. Copyright © 2016 The Eclipse Foundation. All Rights Reserved IOT CLOUD PLATFORM Connectivity OS Stack for IoT Cloud C implementation of an MQTT server MQTT 3.1.1 compliant Scalable (1000 clients = 3MB RAM) Extensible (e.g authentication plug-ins)
- 21. Copyright © 2016 The Eclipse Foundation. All Rights Reserved IOT CLOUD PLATFORM Connectivity MessageRouting OS / PaaS Device Management Data Management Event Management, Analytics & UI Device Registry Application Enablement OS Stack for IoT Cloud Platform Abstract the actual communication protocols via “protocol adapters” Deploy on: An Integration Platform for IoT Services NoSQL data store REST API
- 22. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Cross-layer concerns SECURITY ONTOLOGIES TOOLS
- 23. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Cross-layer concerns SECURITY ONTOLOGIES TOOLS
- 24. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Eclipse Vorto
- 25. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Cross-layer concerns SECURITY ONTOLOGIES TOOLS
- 26. Copyright © 2016 The Eclipse Foundation. All Rights Reserved > Focus on an industry solution > Showcase a technical solution + vendor ecosystem Examples: IoT Testbeds? Smart manufacturingWaste management Asset tracking
- 27. Copyright © 2016 The Eclipse Foundation. All Rights Reserved First testbed: Asset Tracking
- 28. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Architecture https://iot.eclipse.org/testbeds/asset- tracking
- 29. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Our community
- 30. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Join us! http://iot.eclipse.org Booth 844 @ IoT World
- 32. Backup slides
- 33. Copyright © 2016 The Eclipse Foundation. All Rights Reserved The 3 IoT Software Stacks TOOLS & SDKsONTOLOGIESSECURITY CONSTRAINED DEVICES Hardware Abstraction Layer (HAL) OS / RTOS Communication Remote Management Field protocols IoT protocols IOT CLOUD PLATFORM Connectivity MessageRouting OS / PaaS Device Management Data Management Event Management, Analytics & UI Device Registry Application Enablement GATEWAYS AND SMART DEVICES RemoteManagement Application Runtime Data Management & Messaging OS / RTOS Connectivity Field protocols IoT protocols Network Management
- 34. Copyright © 2016 The Eclipse Foundation. All Rights Reserved Eclipse IoT stack on Cloud FoundryRouter Eclipse ACS <<Hono Adapter>> <<Hono Adapter>> Kapua Web Console Kapua UAA
- 35. Copyright © 2016 The Eclipse Foundation. All Rights Reserved OS Stack for IoT Cloud Great! But… what if: ↳I want my platform to archive the data? ↳I want to support more than just MQTT? ↳I want a multi-tenant solution? ↳…
Notes de l'éditeur
- From a 20,000 foot view, this how most if not all IoT architectures are implemented. In order for your data to make it to the cloud, and hence to the final application/user, the devices (think “microcontroller” and tiny brain that are the heart of sensors and actuators) need to be able to communicate. While some might have this capability (and more on that in the next slide), a gateway is typically in charge of connecting the constrained devices to the IoT.
- Let’s look a bit closer at the key characteristics of each element of an IoT solution. Devices - or I should say constrained devices - are really doing a specific task (e.g measuring the vibrations of a motor). We’re talking brains (microcontrollers) that are probably 1$, if not less, and that are by definition constrained in terms of computing capabilities, number of I/Os, etc. Often, but not always, power consumption is a key aspect. So this will have impact on the H/W and S/W capabilities. These devices are very specialized. If you can save 2 cents by getting rid of a H/W feature that you don’t need, you will do it. Similarly, you will make choices in your software, and you will e.g probably support the protocol you need and only this one. Gateways / Smart Objects - as per the explanation I just did, you realize that most of the times, devices won’t have the ability to implement direct communication to the Internet. This is where you need what I call smarter objects, or gateways. Here, connectivity is essential (of course, you aim at reaching a backend/cloud server eventually), an a smart object often will have many options for connectivity Not only can the device/gateway communicate, but typically you want it to also be smart enough to actually manipulate messages, as opposed to “raw” data. That is to say, the smart object is already able to make some smart...er decisions when it comes to forwarding sensor data to the cloud or not, or figuring out which device a command being received from the cloud is targeted to All in all, the gateway/smart object enables so-called edge computing Cloud – this is where a lot of the IoT magic happens :-) Of course, scalability is important. Horizontally, as the number of devices on the field grows (zillions of devices, eh?), as well as vertically, to deal with different business cases and their specificities It’s all about integration, since you need to enable third party to e.g consume your sensors’ “fire hose”, or people to be able to build their own application and dashboards. Lots of the value for IoT is in the data, and the cloud platform needs to help not only storing the huge amounts of data, but also analyzing and making sense out of it. So assuming we are on the same page now on what those 3 key components are, let’s look in more details at what are the core features that need to be provided by each of them.
- Some concerns actually span across all the components. You want security at each level, and things like the ability to only run trusted code on your devices, the ability to secure your communication channels against eavesdropping, or the ability to secure your Cloud platform REST APIs for giving users access only to what they’re supposed to have access to IoT data is very diverse. If your IoT datastore does not give you a way to figure out the difference between temperature and pressure data, or to figure out what is in Celsius and what is in Fahrenheit, you will be in big troubles. Ontologies are needed to describe data that flows in the IoT value chain. Tools. You need simulators, debuggers, emulators, etc. in order to accelerate IoT development, simplify testing, etc. Of course if you know us (Eclipse) you do realize we provide a lot in that area.
- So why doing this categorization anyways? Well, identifying the different layers of a software stacks, and the interfaces through which each stack can communicates helps define an interoperable architecture: each stack is independent from one another. You can use whichever cloud stack/provider you want, no matter your gateway stack – no vendor lock-in within each stack, the layers are interchangeable. If you want to replace the communication layer of your gateway to speak HTTP WebSockets instead of MQTT, this is something that should be possible. Each stack should be independent of the underlying platform. E.g for the the cloud stack, you probably want to leverage the likes of Docker, Cloud Foundry, Kubernetes, … Open Standards have proven key (look at the history of the Internet, or in IoT and more recently: MQTT) for enabling interoperability too. Of course, each component/service of your IoT stacks will need to expose well-defined APIs, as it’s what enables composition/reuse by others who add value on top of the stack.
- If you’ve been following us (we’ve been around for 5 years now!) from the beginning, and even if you have not, you realize we’re this open source community providing key components and libraries – let’s call them building blocks – that can be used to create an IoT solution. Want an MQTT protocol stack? Sure, you can get it from Eclipse Paho. A security layer for your microcontrollers? Maybe you will use Eclipse tinydtls… But more recently, we’ve seen a trend towards delivering more integrated platforms/stacks that take the building blocks I just mentioned, and integrate them in a readily usable stack. Much like the LAMP (Linux-Apache-MySQL-PHP) stack for the WWW, if you will.