WSO2Con USA 2015: WSO2 Platform for IoT

Post on 15-Apr-2017

469 views 2 download

Transcript of WSO2Con USA 2015: WSO2 Platform for IoT

WSO2 Platform for IoT

Sumedha RubasingheDirector - API Architecture

IoT is not new.

**

M2M, IoT

Source: http://community.arm.com/groups/internet-of-things/blog/2014/06

IoT Ecosystem

nogini.com is a manufacterer of fire safety devices.

Sumedha has purchases a fire alarm from nogini.com.

Device Manufacturer’s Perspective

IoT Ecosystem

**

IoT Platform ChallengesDevice Registration & Management

Integration

Security - Data

ScalabilityEvent Management

App/Firmware Management

Security – Device Access

WSO2 Reference Architecture for IoT

WSO2 Reference Architecture for IoT

WSO2 IoT Server

● Implementation of WSO2 Reference Architecture for IoT

● Offering WSO2 IoT Platform as a single distribution pack

● 1.0.0-Beta – 2015 Q1

● 1.0.0 GA - 2016 Q1

WSO2 IoT Platform - Target Market● Device Manufacturers

○ Looking for software processing platform for new devices

○ Registering new device types

○ Device enrolment for device owners

○ Personalized dashboard for devices (device owners)

○ App building for device control

● Architects

○ Device Integration to existing solution architectures

● Part of WSO2 Cloud (App, API, Integration, Device - cloud)

○ http://cloud.wso2.com

Connected Device Management Framework

WSO2 IoT Server

**

IoT Device

● Piece of hardware● Built for a purpose● Capable of a limited functionality● Control interface● Input/output● Consumes power● Constrained Environment

Characteristics

Summary● Functional Capabilities (Actuators)● Administration Capabilities (Management)● Monitoring Capabilities (Sensor Data)

**

Modeling Device as an API

● eg : HTTP API (not limited to)○ Lock

■ GET http://{ip}/{locationid}/sensors/door1lock/staus■ POST http://{ip}/{locationid}/sensors/door1lock/lock

○ Temperature Sensor■ GET http://{ip}/{locationid}/sensors/temperature1

○ Motor■ POST http://{ip}/{locationid}/actuators/motor1/rotate/{turns}/{direction}

■ GET http://{ip}/{locationid}/actuators/motor1/status

**

Advantages - Devices as APIs● APIs - Standard Integration Pattern○ Heterogenous devices■ protocols, access control mechanisms, data formats

● App Developers - Already familiar programming paradigm

● Seamless Integration with existing systems● Ability to re-user known patterns for securing, hardening

APIs● API Economy

Writing Device Plugins

IoT Analytics

IoT Analytics

● How fast do you results?

● How much data to keep?

● Hindsight, insight, foresight

● Acting on data/events

WSO2 Data Analytics Server

“A Framework for processing data to create hindsight, insight and foresight”

Device as an API in WSO2 API Manager

Summarizing Sensor Data

Dealing with real time data

Dealing with real time data

Event Receivers

Simulate Events

Event Stream Repo

Trying out Siddhi Queries

Virtual Devices for simulation

**

Currently Support for protocols

● MQTT

○ Topic per device instance

○ Single topic for IoT Server

● XMPP

○ Jabber account per device instance

● Web sockets

○ Device -> Event Listener -> CEP Output Adaptor (Web

Sockets)

● HTTP

○ HTTP server @ device gateway end

○ CoAP like

Security Challenges

How enterprises can use IoT Platform?

● Device Management

● On boarding new device types with custom

transport/protocol needs

● Performing Analytics on existing device data streams

● Device to middleware integration

● Device to Application lifecycle management via APIs