When observing the update process from a backend perspective, it quickly becomes apparent that a software update is a relatively domain-independent operation.
Take a small edge sensor as an example: Updating such sensors is a simple process. It involves delivering a software update artifact to the device, which is then subsequently installed via a suitable mechanism for constrained devices.
Olaf Weinmann
Olaf Weinmann has been working for Bosch.IO (formerly Bosch Software Innovations) since 2011, where he is responsible for different aspects within the Bosch IoT Ecosystem. Currently, he is Product Owner for Bosch IoT Rollouts. He studied mathematics and information technology at the University of Konstanz and holds a PhD in mathematics. In his spare time, he enjoys sports and teaching mathematics.
Automobiles are another example. It’s obvious that a car is a highly complex machine, composed of dozens of updateable ECUs (Electronic Control Units) with complex dependencies. However, in most cases, triggering a backend software update isn’t an elaborate operation. The complex logic for installing the update in the car is contained either within the software update package or is part of the local software update mechanism in the car itself.
iMessage App