How To Build An Internet Of Things (Iot)

Transcription

1 The Internet of Things: Devices, Avatars, Worlds, and APPs Tom Berarducci Director, Platform Product Mgmt Zebra Technologies Corp.

2 Zebra Technologies Corp.

3 Goal of the Internet of Things (IoT) A key goal of the IoT is a rapidly-expanding ecosystem of rich applications that make use of devices and their data Tons of Cool APPs for Connected Devices

4 But how can a cloud app connect to a device? No easy way to connect a cloud app to a device Protocols Getting through firewalls Dealing with legacy devices Discovery of devices

5 How do you Scale? Old way: If device mfr wanted an app, they had to write it. 1:1 DeviceType : App Then: Create an API! But then devs must learn your API. 1: Small# DeviceType : App Now: Device-agnostic platforms Devs have to Learn (a small number) of APIs. Big benefits. 1: Large# DeviceType : App Future: Consolidation A small number of winners (and a lot of losers). 1: Huge# DeviceType : App The Key is to Decouple Devices from Apps Santa Clara, CA USA April

6 Four Key Components for the IoT APPs Enable rich applications Worlds Share device access and data with others Permissions App Knowledge Avatars Create a device-agnostic environment Device Device Knowledge Devices Connect your device to the Internet. Abstraction All delivered in a secure and robust environment

7 Devices Modern and legacy devices both need a system that: Maintains a reliable and secure connection between device and server Encrypts data to and from the cloud Can use wired and wireless connections, including telecom Uses a gateway to connect to legacy devices Uses corporate grade security to connect from within firewalls

8 Avatars Avatars are the Facebook page of devices in the cloud. They expose: Sensors Actuators Status Activities Settings They provide a consistent representation for diverse devices and a consistent interface for applications to interact with devices. Applications talk to avatars, and avatars talk to devices: you never expose devices directly to the internet.

9 Connect Devices to the Cloud using Standards Legacy devices use gateways. New devices connect directly using one of two standards: 1. HTTP REST Simple POST of device data in JSON 2. Lightweight Machine-to-Machine (LwM2M) client Self-describing client for rich device interfaces OMA Standard for IoT devices Adopted by ARM for new mbed architecture Uses CoAP protocol to deliver standardized payloads Over UDP, TCP, or SMS Authentication using PSKs Encryption through TLS/dTLS Goal: To Enable Reuse Cloud Service Driver Device Or Gateway

10 Link Device Driver to Avatar Driver author describes device functionality in Avatar Definition. Device Registers on cloud service, associating with Avatar Definition Authentication with PSKs Uses pre-defined Avatar Definition ID User claims Device which instantiates Avatar in their Account Uses device ID info (e.g serial number) Goal: To Abstract Device Details Away Cloud Service Avatar Definition Driver Device Or Gateway

11 Enable Controlled Sharing with Worlds Worlds are a convenient metaphor for permissions Users organize devices and avatars in worlds: Private worlds: nothing is shared Shared worlds: users decide which data to share with which user or application Public worlds: everything is available to every user Worlds are a modern and simple way to control who has access to devices and their data.

12 Use an Accepted Application API HTTP REST CRUDXO model (POST, GET, PUT, DELETE) JSON Payload OAuth 2.0 Authentication TLS/SSL Encryption Goal: To Drive Adoption Santa Clara, CA USA April

13 Home World Example JSON { "permission":"crudxo", "name":"tom_at_zatar", "lasttimemodified": , "creationtime": , "users":{"href":" QP/users","length":2}, "avatars":{"href":" 2QP/avatars","length":24}, "avatarsgroups":{"href":" AEQNO2QP/avatargroups","length":1}, "avatarsprofiles":{"href":" AEQNO2QP/avatarprofiles","length":0}, "href":" "owner":"

14 Printer Avatar

15 Printer Avatar Example JSON { "avatardefinitionid":"3", "attributes":{ "Model":"QLn320", "UDI":"XXQLJ ", "Status":"1", "Name":"Tom's QLn", "Location":"Granite Bay", "Manufacturer":"Zebra Technologies", "Type":"Printer", "Firmware":"V Z, motor.over.temperature":"false", odometer.headclean.cm":"8797, label.shift":"", media.handling":"1, mac.address":"00:22:58:6d:40:62", head.open":"false"}, "lastupdatedtime":" t18:58:10.009z", "href":" ", "commandjobs":" ars/ /jobs", "homeworld":" "worldssharedwith":[{"href":" }], "sysprefix":"qln320" },

16 An Avatar Decouples Device Details from App Development Avatar Device Knowledge APP Knowledge

17 Avatars

18 Avatars

19 Avatars

20 Avatars

21 Avatars

22 APPs - WebApp

23 APPs - iphone

24 In Summary IoT Vision is for an Ecosystem of Apps Scale requires decoupling Device Knowledge from Application Knowledge Through Avatars and Worlds When choosing platforms, consider: Device connection through standards like LwM2M and HTTP HTTP REST as the application API Standards like OAuth 2.0 for Authentication Santa Clara, CA USA April

25 Resources Developer Zone : Client API : Client API documentation : Device API : Device library : LwM2M: CoAP: OAuth 2.0: Contact us : developers@zatar.com