Introduction to IoT Platform
Everhett Raman - Solution Architect (Persistent Systems Malaysia)
Content
Delivered
● Recap: IoT Components & Solution
● Introduction to IoT Platform (IoTP)
● B2C & B2B Scenario
Recap: IoT Components
Device Device Gateway Device API Solution
● The actual ‘THING’ ● Bridge between device & app ● Ingest data from Gateways ● The customer’s business
requirement is implemented
● Actuators & Sensors ● Messaging: retrieve data & ● Cloud storage (warm data)
here
send command
● Supported Commands (RPC) ● Provides API for application
● Backend service to integrate
● Edge computing (hot data) integration
● Standards: OMA-DM, TR 069, with Device API - to pull data
LwM2M ● Client/server (usually) ● Webhooks to push data (near & send command
real-time)
● Software (OS + DM): ● Supports Token/Certificate ● Frontend for displaying
MindSphere, Free-RTOS based authentications ● Database + API meaningful device
● Authentication: ● Security (Transit): SSL ● DM Proxy information and sending
Token/Certificate command via API integration
● Device Management (DM) ● Subscription managed by the
● Security (Transit): SSL device vendor ● User dashboards & widgets
● Communication Protocols
● Communication Protocols
Recap: Device Management (DM)
Software Update Architecture
Onboarding
Gateway pushes latest device
Turn on, and add device to
firmware or security patch.
network. Device calls home for
Gateway
the first time.
G S D
E E A
T T T
Device A
Lifecycle
Monitor & Diagnostic Discovery DM
SDK
Gateway continuous Gateway auto-discovers
monitoring of device new device calling home OS
status. for onboarding.
Hardware
Configuration
Gateway pushes required configuration to device.
Recap: Communication Protocols
TCP/IP Model IoT Protocols
Application HTTP, MQTT, CoAP
Transport UDP, TCP
Internet IP, 6LowPAN, RPL
Network & Physical WiFi, BLE, Ethernet, Cellular, LPWAN
(LoRA, ZigBee)
Recap: Build a Typical Solution
Device Gateway API Solution
● Source for vendors & study the API thoroughly ● Build backend to receive data & send command
● Unless necessary, extend the API (functions) ● Store time-series in NoSQL and relational data in RDB
● Look for standard integration HTTP/MQTT ● Decouple, and build responsive frontend
● Webhooks/callback - near real-time data ● Control user permission, and secure data (motion & rest) -
only admin could perform device management etc.
Introduction to
IoTP
● What is it?
● Why we need it?
● How it’s done?
What is IoTP?
● A middleware between a device
and application
● Enables Connectivity
● Provides Device Management
(DM)
● Provides Security
● Cloud-Native/Cloud-Ready
● Enablement Platform
Get Confused to Clarify ...
Why We Need it?
1. The Thing/Device
2. Connectivity
3. Communication
4. Data Collection
5. Configuration Management
6. Messaging
7. Software Updates
8. Identity Management
9. Rule Engine
10. Analytics
11. Visualization Reporting
12. Alerting
Alternative
Device Gateway API Solution
● IoTP can be useful for building IoT solutions ● Use IoTP to manage data ingestion, storage and device
● Data ingested from device (via Gateway) management
● Sending supported commands to device (RPC) ● Unless necessary, extend dashboard to external service
● Good widgets & dashboards available ● Use rule-engine for unavailable OOB features
● Can pipeline data to other application/services ● Admin performs UAC & device management
B2C & B2B
Scenario
Business to Consumer B2C
● Problem Scenario
● Solution
Business to Business (B2B)
Business Model
Functional Architecture - IoT Platform SI
Functional Architecture - Service & License Management + IoT Platform Integration
● Understand requirements
● Have a SI mindset
● Know ‘Tools of the Trade’
● Don’t reinvent the wheel
Summary ●
●
Consider multi-tenancy
Pay attention to security
● Always consider NFR
● Know when to develop, and when
to integrate (right balance for
cost)
Thank you!
