Arm Mbed Edge Nick Zhou Senior Technical Account Manager Arm Tech Symposia 2017
IoT increasing efficiency, yield, and convenience Commercial buildings Better energy & space utilization Precision farming and connected sites Increased yield combined with efficient use of resources Home Increased security, more convenience, freeing up time 2
Arm Mbed: Bridging IoT cloud and device security 3
Key problems solved by IoT gateway solutions A ccess C ontrol M bed C loud A PP A PP A PP H VAC,Lighting, Energy M anagem ent G atew ay w ith M bed C loud Edge ` Proprietary Business Solutions (com petitive edge) 4
Multi-protocol device management Expands Industrial IoT SAM by 4x to non-ip devices Connect the unconnected Non-IP is large % of wireless device installed base Prevalence of non-ip devices across Industrial IOT 2.1B ~20% IP connectable Non-IP 3.4B ~24% ~76% By 2020, 90% of Internet of Things (IoT) projects will utilize an IoT gateway, up from 60% today. ~80% 2017 2020 >75% require gateways to connect - Gartner, Explore the Roles of IoT Gateways in Five Edge Use Cases, 16 June 2017 Source: 2017 IHS data - Industrial IoT Segment Includes Building automation, commercial transportation, retail systems, industrial automation, lighting, power & energy, security, signage, construction equipment, fueling, professional entertainment equipment, broadcasting 5
Gateway Management Uptime, Uptime, Uptime! Factory automation Gateways provide local execution Online & offline operation Equipment can shut down, stopping factory lines Emergency situations, could require hard real-time control to stop Critical requirements Accurate, detailed, & timely error reporting Ability to react and respond - Automation - Quick recovery from failure 6
Edge Compute Application orchestration Not all data can or needs to go to cloud Latency Offline operation Simplification Data conservation Development platform & native bindings Cloud Edge synchronization Multi-tenancy 7
Gateway key components mainly gateway gateway & cloud mainly cloud Gateway Protocol stack implementation Protocol normalization Gateway & endpoint management Gateway services Security services Compute Application services Cloud Log database Backup / Restore Gateway & endpoint management Gateway service management Identity & access management Edge compute orchestration Portal & API gateway 8
Introducing Mbed Edge protocol translation Provided as SDK for gateway OEMs to integrate into their hardware/software platform 9
Key components of Mbed Edge protocol translation Mbed Cloud Gateway device type in cloud device registration Mbed Edge core Gateway to proxy for protocol Gateway endpoint device Legacy protocol translator & control Manage and controls legacy devices connected Firmware update Update Mbed Cloud firmware Mbed Edge core Mbed Cloud Mbed Edge software components legacy protocol translator & control firmware update Legacy sensors 10
Gateway management Mbed Edge Mbed Edge protocol translation - logical flow 5 BT Device Arm provided Partner provided Mbed Cloud (Ethernet /LTE / Wifi) Gateway 4 Device registration Mbed Cloud clients (Ethernet /LTE / Wifi) Gateway Process 3 Proxy registration 11 LWM2M ENDPOINT Mbed Cloud Client LWM2M CoAP UDP / TCP Mbed OS or other OS Protocol translation Native protocol non-lwm2m ENDPOINTS Bluetooth 2 Identifier (MAC, ID, Serial #, etc.) 1 BT pairing
Mbed Edge protocol translation Working together: Partner and Arm responsibilities Mbed Edge Security between gateway and Mbed Cloud Reporting of any errors in either the protocol translation interface to the legacy interface or connection to Mbed Cloud Maintaining & reporting status of connectivity to Mbed Cloud Partner (Gateway developer) Onboard and pairing of legacy devices to the gateway legacy interface (e.g. BLE, Zigbee, Modbus) Protocol interface implementation between legacy interface and Mbed Edge Monitoring status of protocol translation interface and connectivity to Mbed Cloud, including error reporting to the cloud (arm provides example) Offline control and management of legacy interface in the event of loss of connectivity to Mbed Cloud Factory provision keys into the gateway 12
Mbed Edge protocol translation How to get started: Deliverables Mbed Partner* availability: Q4 2017 Available in source code API Format Protocol translation: C mbed cloud status: REST (http) Hardware reference design: Qualcomm IPQ4029 (OpenWRT) Advantech WISE-3610 - LoRA Call to action If not already, join Arm Mbed Partner Program Review protocol translation API Download* Mbed Edge source & integrate onto your gateway platform Write necessary code to bridge non-ip endpoints using Mbed Edge translation protocol translation API 13 * Available in Q4 2017, watch for partner newsletter
Mbed Edge gateway management & edge compute components EdgeJS APIs Device normalization, control, events, on-boarding Alarming is a major IoT use case: Raise & lower Application specific alarming - customizable Subscribe to device events, take action EdgeJS Apps Control, listen, take action on devices locally without cloud Apps run across all gateways in the site Containers & Multi-tenancy apps are protected from each other Cross-platform Protocol & Device Support Built-in: BACnet, modbus, ZigBee, Z-Wave, Bluetooth, UPnP, others Extensible. Vendors / customers can add their own support. Device controllers can be dynamically updated from the cloud. EdgeDB Distributed database for gateways Allows storage to be shared across all gateways in a site Storage is local, works if cloud is down, syncs when cloud up Enables local edge computing across a site 14
Mbed Edge gateway management & edge compute Gateway Management Large scale management. Status, backup & restore, configurations, logging and remote access Edge App & Device Support Deployment Deploy new edge applications (secure docker containers), new device controller components, configure, rollback, etc. Dashboard & monitoring APIs, Alarming Deploy, manage & maintain many gateways, watch & monitor for custom alarms across many sites Roles & Permissions Assign user roles across sites, determine device access. Mobile Support Users can control & monitor devices. 15
Porting Mbed Edge enhanced stack onto new hardware Complete Port Component Port Entire Linux OS system with all components Standard Linux OS kernel All systems management capabilities Key components port: Full protocol support (given that radios can be supported) Time must be spent understanding & potentially updating / patching portions of the OEM s existing BSP Support will be limited Radio support is the majority of time / cost Known, tested system. Full support Kernel patches and drivers for OEM hardware will be merged into the kernel, and Linux OS kernel for the OEM HW is provided 16
Mbed Edge Portal Key Capabilities Manages geographically dispersed gateways Sites: allow multiple gateways to share data redundant, durable. Full systems management: web UI control, logging, console if required Purpose built for IoT (compare this to solutions meant for servers which are repurposed for gateways) Provides insight down to the end-device level Deploy IoT scripts fast using EdgeJS containers 17
Mbed Cloud Edge Portal Demo Viconics 8600 (BACnet technology) actual installation Fibaro Motion / Light / Temp Sensor (Z-Wave technology) Small commercial building Gateway with Mbed Cloud Edge Wired Temperature Sensor (Modbus technology) 18 ios & Android Mobile App Control & Monitoring
Arm Mbed: Bridging IoT cloud and device security 19
Summary IoT gateways will continue to play a critical role in IoT deployments for decades 3 critical components of Gateways (1) Protocol Translation (2) Gateway Management (3) Edge Compute Mbed Edge protocol translation available in Q4 2017 for Mbed partners Mbed Edge gateway management & edge compute, available in 2018 Arm is looking for OEM and silicon partners 20
For further information Find demos and more information at the Arm booth (402) and Mbed booth (712) At TechCon Accelerating intelligence-at-the-edge for embedded & IoT applications Govind Wathan Connect your IoT device: Bluetooth 5, 802.15.4, NB- IoT Prithi Ramakrishnan Enabling firmware updates over LPWAN Jan Jongboom Connecting what you want, when you want to the IoT cloud Karthik Ranjan Diversity of connectivity required for IoT devices Sam Grove After TechCon Panel: Breakthrough technologies enabling the future of IoT Moderated by Jason Hillyard Resolving the perfomance vs efficiency conflict for embedded and IoT applications Kinjal Dave Building firmware updates: the devil is in the details Brendan Moran 21 https://developer.arm.com shiv.ramamurthi@arm.com
Thank You! Danke! Merci! 谢谢! ありがとう! Gracias! Kiitos! 22
The Arm trademarks featured in this presentation are registered trademarks or trademarks of Arm Limited (or its subsidiaries) in the US and/or elsewhere. All rights reserved. All other marks featured may be trademarks of their respective owners. www.arm.com/company/policies/trademarks 23
Customer example: Major convenience store operator Opportunity 6000 stores, 10-30 devices per store Sales Cycle: - Pilot 3 months - Rollout: 6 mos ~ 2 years What does it do? - Energy Management System (EMS) - Mobile control (HVAC, lighting) - Preventive maintenance for HVAC, ice makers and refrigeration - Lighting control - Future: fuel tank management, customer analytics 24
Customer example: Major convenience store operator 25