WSO2Con USA 2015: WSO2 Platform for IoT

1. WSO2 Platform for IoT
Sumedha Rubasinghe
Director - API Architecture

4. IoT is not new.

5. **
M2M, IoT
Source: http://community.arm.com/groups/internet-of-things/blog/2014/06

6. IoT Ecosystem

7. nogini.com is a manufacterer of fire safety
devices.

8. Sumedha has purchases a fire alarm from
nogini.com.

26. Device Manufacturer’s Perspective

27. IoT Ecosystem

28. **
IoT Platform Challenges
Device Registration & Management
Integration
Security - Data
Scalability
Event Management
App/Firmware Management
Security – Device Access

29. WSO2 Reference Architecture for IoT

30. WSO2 Reference Architecture for IoT

31. 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

32. 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

33. Connected Device Management Framework

34. WSO2 IoT Server

35. **
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)

36. **
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

37. **
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

38. Writing Device Plugins

39. IoT Analytics

40. IoT Analytics
● How fast do you results?
● How much data to keep?
● Hindsight, insight, foresight
● Acting on data/events

42. WSO2 Data Analytics Server

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

44. Device as an API in WSO2 API Manager

45. Summarizing Sensor Data

46. Dealing with real time data

47. Dealing with real time data

48. Event Receivers

49. Simulate Events

50. Event Stream Repo

51. Trying out Siddhi Queries

52. Virtual Devices for simulation

53. **
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

54. Security Challenges

55. 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