IoTOnAzure Dotnetconf
IoTOnAzure Dotnetconf
26
billions
IoT business scenarios
Manufacturing
Smart City
Smart Building
Healthcare
Energy
Transportation and Smart Vehicles
Logistics and Inventory Management
Retail
Agriculture
IoT Business Maturity Model
1. Operational efficiency
Internationalization
Device recovery High availability
Deployment
Updating devices Cloud-to-device
Transport protocols commands
Device lifecycle
Warm path analytics
Drivers Things Disaster recovery Insights Hot path analytics
Actions
Device updates Data ownership
< ---- E N D - T O - E N D SECURITY ---- >
On device analytics Data visualization
Manufacturing scale Industry and government compliance
HW certification Securing data
Device commercialization
… and why IoT needs simplifying
IoT architecture requirements
Handle extreme hardware and software heterogeneity
Build for hyper-scale and enable low data latency
Think about security, be secure by design; support defense in depth
Lower barriers to entry: evaluate -> prototype -> deploy -> update
Think big, but start small (experiment, learn and refine)
Deliver telemetry and notifications that are meaningful even at extreme
scale
Provide hot-path and cold-path analysis and action/response.
Azure IoT Architecture
Things Insights Actions
Technology
Cloud Technology
Field Protocol Gateway Azure Stream Analytics, and HDInsight Spark & Storm
Business
Gateway Adaptation Integration
Connect to business process
Warm Path Analytics
Connect and Ad-hoc visual exploration of time series data
Technology
Manage
Azure Logic Apps, API
Field Devices Technology Management, Biztalk Services
Gateway Azure Time Series Insights
Lambda Architecture
Things Insights Actions
slow path
Store Display
Analyze Action
IoT Hub
Cloud fast path
Gateway
Analyze Action
Bi-directional communication
IoT Communication - Information Exchange Patterns
Information flowing from a device to
Telemetry other systems for conveying status of
device and environment
Bi-directional communication
Millions of Devices
Multi-language, open
Multi-language, source
open SDKsSDKs
source
HTTPS vs AMQPS vs MQTTS
HTTPS/AMQPS/MQTTS
Azure IoT Hub
Bi-directional communication
Millions of Devices
Multi-language, open
Multi-language, source
open SDKs
source SDKs
HTTPS vs AMQPS vs MQTTS
HTTPS/AMQPS/MQTTS
Send Telemetry
Receive Commands
Device Management
Device Management
Device Twin
Device Twins
Queries & Jobs
Azure IoT Hub Device
Device Twin
Twin
Device Management
Software
Firmware IoT Hub
Configuration
Telemetry Telemetry channel
IoT Device
Device Twin Device Twin
Properties Properties
Cloud owned,
Desired Desired device visible
Device owned,
Reported Reported cloud visible
Cloud only,
Tags device metadata
Cloud initiated C2D
Methods Methods with response
Commands
Cloud initiated C2D
message
Device Twin vs Digital Twin
Twin is a cloud base representation of something that is remote
Device Twin is
• A key/value flat representation of
• Desired configuration
• Reported configuration
• Keys to match to an external database
Digital Twin is
• A graph
• Richer semantics
• Not only devices – focused on resources
Azure IoT Hub
to a network. URL
, De
vic eN
ame 4
HW with ID “123ABC” , Sy I am “DigitalSign(Key)”:
mK
was produced I am ey [Data] & [DM]
d ev
i ce
“1 2
3AB
1 C”
2
123ABC 123ABC
SaaS
Azure IoT Hub
Azure Stream Analytics
Azure Time Series Insights
Azure Machine Learning
Azure Logic Apps
More
PaaS
Azure IoT solution accelerators
Device Connectivity & Management
Preconfigured Solutions
Remote monitoring
Predictive maintenance
Connected factory
Azure IoT solution accelerators
Azure IoT Central
Device Connectivity & Management