Extensible, server-side, open IoT architecture for device management, complete with integration capabilities, IoT analytics, and security for devices and data.

1. WSO2 IoT Server 1.0.0
<Insert Presenter Name>
<Insert Designation>

2. Overview
2
• The Challenge
• WSO2 Open Platform for IoT
• Introducing WSO2 IoT Server
• Customer benefits
• Deployment Options

3. IoT Platform Requirements
3
● Device Management
○ Connect to and manage a wide range of devices
○ Update and manage apps/ firmware
● Integrate the IoT and the IT world
○ Enterprise and their partners services and processes integrating with the world of IoT
● IoT Analytics
○ Batch and real-time analytics
○ Available at the edge
● Events Processing
○ Business Process Management (workflows)
○ Complex Event Processing
● Security
○ Control access to collected data and devices

4. WSO2 Reference Architecture for IoT
4

5. Deployed by customers today
5
● For Integration (ESB, Message Broker)
○ Capture IoT traffic, apply transformations to data and events, and integrate with back-end
services/business processes.
● Events streams are sent to analytics platform for two purposes
○ Batch analysis of data for reporting purposes
○ Streaming analysis of data for real-time processing of events
● Real-time alerts are used to trigger business processes
● API Management is used to securely expose devices to 3rd party
developers
● Products have been extended to support IoT specific transports, security
requirements.

6. API Management
6
Modelling Devices as APIs
● Devices are modelled as APIs
○ API Gateway becomes the gateway to devices actuators
● Benefits
○ APIs are a standard integration pattern
○ App Developers are already familiar with programming
paradigm
○ Standard interface on top of heterogenous devices
protocols, access control mechanisms, data formats
○ Seamless integration with existing systems
○ Ability to use known patterns for securing, hardening
APIs
Temperature Sensor
http://{ip}/{locationid}/sensors/temperature1 - GET
Motor
http://{ip}/{locationid}/actuators/motor1/rotate/{turns}/{direction} - GET
http://{ip}/{locationid}/actuators/motor1/status - GET

7. 7
● Provides a solid foundation for an IoT analytics
solution, should it be for device manufacturers or
device users
● Platform can be leveraged to:
○ React in a few hours, a few mins or a few ms to a condition,
leveraging batch and streaming analytics.
○ Implement closed loop control (autonomic computing)
leveraging Machine Learning.
○ Embed streaming engine in IoT devices or gateways
○ Use a SDK and data agent to directly publish events at the
device hardware level.
● Pre-built visualizations customers can extend.
● Scales to 250.000 events / sec
● Very low latency for streaming analytics (< 1ms)
Events Processing & Analytics
Analytics Platform

8. Events Processing & Analytics
8
Integrating with Services & Workflows

9. 9
Events Processing & Analytics
Applying Machine Learning to IoT

10. Introducing IoT Server
10

11. WSO2 IoT Server Vision
11
Extensible, server-side, open IoT architecture for device management,
complete with integration capabilities, IoT analytics, and security for
devices and data.

12. WSO2 IoT Server
12

13. WSO2 IoT Server
13
● Offers the most important components of WSO2 IoT Platform as a single
distribution pack for ease of development.
● Centralized device management
○ Third parties to add their own device to our device management platform
○ Device type encompasses all artefacts related to a device (actuators API, sensors data for example)
○ Device-specific analysis
● Extensible underlying connected device management framework
● Pre-defined set of devices and protocols
● Introduction of IoT Analytics at the edge
● Support for specific IoT protocols
○ Device integration
○ Security

14. WSO2 IoT Server
14
● Builds on current expertise with IoT projects deployed in production.
● Customers are free to consume the platform components of their choice.
● Cloud enabled.
● Natively multi-tenant.
● Integrated packaging/ download
● SaaS deployment

15. Customer Benefits
15

16. Device Management Framework
16
● Customers use their favourite IDE to define a device type (eg: iBeacon)
○ Management APIs
○ Controller APIs
○ Event streams
○ Database structure to store data
○ User interface components to register/
manage devices
○ UI representation (logos etc)
○ Analytics Scripts
● At deployment time
○ APIs are published in API Manager
○ Event streams are defined for IoT Analytics
○ Analytics scripts are deployed to analytics engine
○ Configuration UI is assembled from UI components
Creating a device type

17. Device Management Framework
17
● APIs
○ Management APIs: used by Device
Management layer and administrative
apps
○ Controller APIs: used by end-users’
applications
● Security
○ OAuth2 token
○ Certificate generated at enrolment type
via SCEP (Simple Certificate Enrolment
Protocol)
Using device APIs and events

18. Manage Devices
18
● Self-service enrolment and management of connected devices
● Group, manage and monitor connected devices
● Share device operations/ data with other users
● Distribution and management of applications and firmware to devices
● Edge computing powered by Siddhi (http://github.com/wso2/siddhi)
● OOTB support for some known device types such as RaspberryPi, Arduino
Uno, IRIS+ Drone

19. Sample UI
19

20. IoT Protocol Support
20
● Leverage IoT protocols for device communications with IoT Server
○ MQTT
○ XMPP
○ Websockets
○ HTTP
● Framework extension for adding more protocols and data formats

21. Pre-built Visualisation for Sensor Readings
21
● View instant, visualised statistics
● Pre-built graphs for common sensor reading types: temperature and
velocity
● Traverse through or analyze and zoom in/out of filtered data
● Stats-API to write your own visualisation

22. IoT Analytics
22
● Turn data from IoT devices into
actionable insights.
● Batch analytics
○ Predefined analytics by device
○ Template gadgets for visualisation
○ Grouped data (all iBeacon in terminal 1, all
iBeacon in terminal 2)
● Real-time analytics
○ Predefined alerts if a certain condition is met
○ Alerts can be SMS, email, start a service, a
business process
● Edge analytics
○ Manage centrally real-time analytics rules
deployed on edge devices or gateways

23. Why WSO2 for IoT?
23
● Lean and innovative platform
● Component architecture built from a single consistent codebase
gives customers what they need, when they need it and no more.
● Already proven in production
● Cloud native
● Scalable
● OEM friendly
● Cost effective
● 100% Open Source

24. Deployment Options
24

25. Deployment Options
25
Managed Cloud
● Dedicated hosting of WSO2 based IoT Server/
Platform solutions
● WSO2 Operations team manages deployment and
keeps it running
● 99.99% uptime SLA
● Any AWS region of choice
● Can be VPNed to local network
● Includes monitoring, backups, patches, updates
On-premise/ Stand-alone servers
● Private Clouds (eg: Kubernetes)
● Public Clouds (eg: AWS)
● Hybrid deployments

26. Device Cloud - coming soon
26
● Part of WSO2 Public Cloud
● SaaS deployment of IoT Server
● Planned for Beta early Q2 2016.
● Part of overall Cloud deployment
strategy
● Combines Apps Dev, API
Management, Integration, IoT
Analytics, Identity under a single

27. CONTACT US
!