Downloaded 25 times
More Related Content
Azure iot
- 1. Azure IoT Tim @Trend Micro
- 3. IoT Suite IoT Hub EventHub Stream Analytics Machine Learning Notification Hub
- 4.
- 5.
- 7.
- 8. • Connect upto 1 M devices • 2 way communication • per-device authentication • Multi-protocol (AMQP, HTTP, MQTT) • Open source SDK for multi-platform
- 9. SDKs • Available onGitHub • Support 5 languages • (C, Node, Java, .NET, Python) • Available on GitHub • Support 4 platforms • Ubuntu 14, 15, Yocto on Intel Edison, Windows 10 https://github.com/Azure/azure-iot-gateway-sdkhttps://github.com/azure/azure-iot-sdks
- 12. Certified devices Arduino Zero IntelEdison Raspberry pi 2 ………. 110 + …… 10 +
- 13.
- 14. sendEvent() {device ID} {device key} IoThub Device Registry Event hub Registry Service Cloud SDK Device create() Message service subscribe() amqp://http://
- 15. Registry operations • Createdevice identity • Update device identity • Retrieve device identity by ID • Delete device identity • List up to 1000 identities • Export all identities to blob storage • Import identities from blob storage
- 16. Security • Access control •Authentication • Protocol specifics • Scoping hub level credentials
- 17. Security • Access control •Authentication • Protocol specifics • Scoping hub level credentials
- 18. Registry read Grant readaccess to device identity registry Registry write Grant read access to device identity registry Service connect Grant permission to back-end cloud service to receive / send device messages Device connect Grant permission to device to receive / send cloud messages
- 20. Security • Access control •Authentication • Protocol specifics • Scoping hub level credentials
- 21. urity tokens toauthenticate devices and services to avoid sendin
- 22. HostName + DeviceId+ SharedAccessKey(deviceKey) SharedAccessSignature (security token) SHA256 Cloud • TTL 60 minutes • Renew every 45 minutes SimulateDevice.js From Registry service
- 23. Security • Access control •Authentication • Protocol specifics • Scoping hub level credentials
- 24. All IoT Hubendpoints use the TLS protocol, and no endpoint is ever exposed on unencrypted/unsecured channels.
- 25. HTTP/1 Include token inrequest header / query parameter AMQP {policyName}@sas.root.{iothubName} in the case of hub-level tokens. username : {deviceId} in the case of device-scoped tokens. password : {security token} MQTT {deviceID} {iothubhostname} / {deviceID} clientID : username : password : {security token}
- 26. Security • Access control •Authentication • Protocol specifics • Scoping hub level credentials
- 27. You can changesecurity policies by creating tokens with a restricted resource URI (Endpoints)
- 28. Support REST API Thinkthese as topic
- 29. Device Cloud /devices/{deviceId}/messages/events /messages/events DeviceCloud /devices/{deviceId}/messages/devicebound /messages/devicebound
- 31. Web console DEMO(3 min)
- 32.
- 34.
- 35. • Real-time analysis •Up to millions of data per sec • SQL-like syntax available • Custom alarms
- 38. Scenario 1 Goal :Total car weight for past 10 seconds
- 39.
- 40. Scenario 2 Goal :First car every 10 minutes
- 41.
- 43.
- 44. • Accept JSON,XML, CSV… • AMQP & HTTP support • Configurable data detention • 1-30 days
- 46.
- 47.
- 48.
- 49. Training Data End ofEngine life 21 sensors data
- 50.
- 51. RUL (Remain UsefulLife)
- 52. Compare & Summary AzureAWS Access Control Attached on IoT hub IAM Authentication security token X.509 certificate Protocols MQTT, AMQP, HTTP/1 MQTT, Websocket, HTTP/1 Target solution remote monitoring tend to be general Integration SDK is needed in most case can be integrated without SDK Partnership 10+ OS certified 110+ device tested N/A Launch status Feb, 2016 still in beta
- 53.