Gateways - The Center of Complexity for Update
summary
Gateways act as the translation hub between multiple IoT frameworks and therefore become the update bottleneck: each physical device and its corresponding virtual device image on every gateway must be signed, distributed and coordinated, often forcing gateway reboots that break availability. The talk recommends a publish-subscribe cloud repository that countersigns vendor packages so gateways need just a single verification key, automated rollback and installer provisioning, and research into no-reboot dynamic updates to reduce combinatorial complexity and improve scalability.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:52Software Update Process
- 2:50Software Update Complexity
- 5:12Standards
- 6:19Framework
- 8:00Object Models
- 13:58Update Gateway
- 17:41Multiple Gateways
- 20:47Update Security
- 25:40Essential Features
- 30:34Update Scalability
- 33:16Key Management
- 35:50Key Management scalability
- 40:14Repository options
- 42:51Conclusions
related talks
18mGateways are All You Need
29mHow Protocol Gateways May Introduce More Problems than They Solve
28mGateway Architecture 3.0
10mGateway management at scale
12mTowards an Architecture for Trusted Edge IoT Security Gateways
19mMastering Multi-API Gateways: Strategies for Scale, Security & Success.
38mEurope's Landing Strategy for Smart Automation
13mRethinking the LoRaWAN Gateway through Extensions