Connecting your IoT devices to azure - Techorama 2019
•Download as PPTX, PDF•
0 likes•79 views
Azure offers multiple different ways to connect your IoT devices to Azure and even more options regarding data transfer. This sessions covers them and gives you ideas how to choose the right one.
Recommended
More Related Content
What's hot
What's hot (15)
Similar to Connecting your IoT devices to azure - Techorama 2019
Similar to Connecting your IoT devices to azure - Techorama 2019 (20)
More from Teemu Tapanila
More from Teemu Tapanila (7)
Recently uploaded
Recently uploaded (20)
Connecting your IoT devices to azure - Techorama 2019
- 1. Connecting your IoT Devices to Azure Teemu Tapanila
- 2. Teemu Tapanila • Helping software development teams to build services on top of Azure with focus on Azure DevOps • Microsoft Azure MVP since 2014 • Microsoft Certified Trainer @TapanilaT
- 3. Information Exchange Patterns Basics of IoT Communication Telemetry Information flowing from a device to other systems for conveying status of device and environment Inquiries Requests from devices looking to gather required information or to initiate activities Commands Commands from other systems to a device or a group of devices to perform specific activities Notifications Information flowing from other systems to a device (group) for conveying status changes
- 9. https://azure.microsoft.com/en-us/pricing/calculator/ Service type Description Estimated Cost Virtual Machines 1 D2 v3 (2 vCPU(s), 8 GB RAM) x 730 Hours $152,62 Service Fabric Service Fabric Cluster Scale Set 1: 5 Virtual Machine(s) x 730 Hours $511,02 Azure Kubernetes Service (AKS) 1 A1 (1 vCPU(s), 1.75 GB RAM) nodes x 730 Hours $45,34
- 18. EDITION TYPE PRICE PER IOT HUB UNIT (PER MONTH) TOTAL NUMBER OF MESSAGES/DAY PER IOT HUB UNIT B1 $10 400,000 B2 $50 6,000,000 B3 $500 300,000,000 S1 $25 400,000 S2 $250 6,000,000 S3 $2,500 300,000,000
- 26. IoT Device Device Twin Methods Properties Desired Reported IoT Hub Device Twin Tags Methods Telemetry Properties Desired Reported Telemetry channel Cloud owned, device visible Device owned, cloud visible Cloud only, device metadata Cloud initiated C2D with response Commands Cloud initiated C2D message
- 27. IoT Hub Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Device Twin Jobs Schedule and Broadcast Device Twin Changes Set Desired Properties, Tags, Call Methods Queries Query Across Device Twin State For Business Logic, Reporting and Compliance
- 31. Straightforward Business Logic Smart Building Protocol Translation Industrial IoT Adapters Autonomous Driving Straightforward Filtering Batch Data Processing Home Automation Hubs Smart Meeting Solutions w/ People Recognition Custom Code Requirements ReliabilityRequirements LowMediumHigh Typical Hardware Requirements Interactive Tier (Single CPU, 128MB Memory) Gateway Tier or Higher Low Portable Modules / Functions Medium E.g.: Custom Code in Containers High E.g.: ML/DNNs in Containers
- 32. Azure IoT Edge IoT Hub Devices Local Storage Nebulus IoT Gateway (Container) Functions RuntimeContainer Management Device Twin Device Twin Azure Stream Analytics (Container) Azure Functions (Container) Cognitive Services (Container) Azure Machine Learning (Container) Module Twin Module Twin Module Twin Module Twin Module Twin Module Twin Module Twin Module Twin Module Twin Module Twin
Editor's Notes
- Device manufacturer adds the device registration information to the enrollment list in the Azure portal. Device contacts the provisioning service endpoint set at the factory. The device passes the identifying information to the provisioning service to prove its identity. The provisioning service validates the identity of the device by validating the registration ID and key against the enrollment list entry using either a nonce challenge (Trusted Platform Module) or standard X.509 verification (X.509). The provisioning service registers the device with an IoT hub and populates the device's desired twin state. The IoT hub returns device ID information to the provisioning service. The provisioning service returns the IoT hub connection information to the device. The device can now start sending data directly to the IoT hub. The device connects to IoT hub. The device gets the desired state from its device twin in IoT hub.