Home / iot / How to manage software updates in the IoT

How to manage software updates in the IoT

How you can organize instrument updates within the IoT – Bosch ConnectedWorld Weblog

Producers or carrier suppliers must continuously strengthen their IoT merchandise to satisfy the ever-changing wishes of the marketplace. That is accompanied by way of the want to stay firmware, instrument, and packages at the IoT instrument up-to-the-minute. The use of a scalable firmware/instrument over-the-air provisioning carrier with complete marketing campaign control options turns out like the best resolution. However what are the important thing traits of such an IoT instrument replace device?

The replace procedure generally

When looking at the replace procedure from a backend viewpoint, it briefly turns into obvious instrument replace is a rather domain-independent operation.

Take a small edge sensor for instance: Updating such sensors is an easy procedure. It comes to turning in a instrument replace artifact to the instrument, which is then due to this fact put in by the use of an acceptable mechanism for constrained gadgets.

Olaf Weinmann

Olaf Weinmann has been running for Bosch Device Inventions since 2011, the place he’s answerable for other sides throughout the Bosch IoT Ecosystem. Recently, he’s product proprietor for Bosch IoT Rollouts. He studied arithmetic and data era on the College of Konstanz and holds a PhD in arithmetic. In his spare time, he enjoys sports activities and educating arithmetic.

Cars are any other instance. It’s evident automobile is a extremely advanced device, composed of dozens of updateable ECUs (Digital Keep watch over Devices) with advanced dependencies. Then again, usually, triggering a backend instrument replace isn’t an elaborate operation. The advanced good judgment for putting in the replace within the automobile is contained both throughout the instrument replace package deal or is a part of the native instrument replace mechanism within the automobile itself.

In the long run, the method of updating instrument is ready bringing in combination a tool and a number of information. What’s vital is that those updates must be controlled in a safe and dependable method at the backend. And that is exactly the place a carrier like Bosch IoT Rollouts comes into play.

Openness as a key feature

A software update system has to be open for any kind of connectivity – this is something we learned early on when it came to our Bosch IoT Rollouts service. That is why Rollouts provides the Direct Device Integration (DDI) API as a standard, off-the-shelf solution. But, it also allows other protocol adapters to be plugged in via the Device Management Federation (DMF) API. On the one hand, this enables the use of standardized device management protocols that cover software update processes such as LWM2M, OMA-DM, and TR-069. On the other hand, it also allows the use of custom protocols.

Depending on the use case, software updates might have to be carried out on disparate data models. A connected sensor might just have a single firmware, while a vehicle has dozens of firmware that have to be rolled out. App-store-like scenarios might also be in play, which means you want to push optional functionality onto a device as part of your business case. That aside, it’s also important to remember that a software update system needs to be tightly coupled to the rest of your IoT landscape.

“Altogether, the system needs to be extensible and flexible.”

Olaf Weinmann, Product Owner Bosch IoT Rollouts

A software update service deeply integrated with your IoT landscape leads to dependencies on the service provider. This undoubtedly poses a risk. Bosch IoT Rollouts is not only based on but also fully API compatible with the Eclipse Open Source project hawkBit. This reduces the aforementioned risk to a minimum for our customers.

Infographic illustrating Bosch IoT Rollouts.

What a cloud-ready IoT software update system needs

  • Scalability: The update system has to be scalable – both from a technical and functional standpoint. The update system has to connect millions of devices and ship terabytes of software. Also, rollouts with hundreds of thousands of individual devices have to be managed.
  • Reliability: Software updates are the last line of defense against device faults and vulnerabilities, making reliability a crucial factor.
  • Integration flexibility: The update system needs to connect and integrate directly through various (non-)standardized device management protocols or indirectly through federated device management servers.
  • Security & integrity: There has to be a chain of trust between the software/firmware release manager and the device itself.

The first feature is the device and software repository. Rollouts is focused and specialized on software updates in the IoT, which means it is not a full-blown asset management or device management solution. It only retains the information of the device that is related to software updates. This includes the software update history, information on what version is currently installed, or how Rollouts can reach the device. Depending on the use case, further metadata can be attached to device representations, but are not mandatory.

The second element is artifact content delivery. Depending on the installation, we are able to ship the artifacts directly to the device or via content delivery network providers like AWS CloudFront. This allows artifacts to be shipped on a global scale.

Software update and rollout management is the third feature that is the at the heart of the product. It’s also often referred to as campaign management. It eliminates the need to update devices individually. Instead, it provides an orchestrated and managed approach for software updates on a large scale.

In a scenario that involves millions of devices, nobody wants to be responsible for triggering the update for all devices at the same time. No longer best may this motive an issue in appreciate to technical infrastructure, or the information facilities, it’s additionally dangerous as a result of mistakes might happen. A greater manner is first of all a small selection of gadgets after which transfer on from there. This guarantees that no longer all gadgets are impacted in case a instrument replace downside arises.

Final however no longer least, a reporting and tracking serve as is needed to stay observe of the replace’s rollout and make sure safety.

“When you’ve got hundreds of thousands of gadgets, no person desires to be answerable for triggering the replace for they all on the identical time.”

Olaf Weinmann, Product Proprietor Bosch IoT Rollouts

How other domain names can have the benefit of Bosch IoT Rollouts

As you’ll be able to see, many sides must be thought to be when offering updates over the air. Along with practical sides, the variety of the IoT panorama will have to be thought to be. A cloud-ready IoT instrument replace device must cater to quite a lot of other domain names. Let’s check out the other fields of software for Bosch IoT Rollouts:

  • Car: Previously, instrument updates have been manually provisioned at automobile restore retail outlets. Via connecting those automobiles and offering instrument updates over the air this procedure may also be controlled at once and mechanically managed by way of a cloud resolution.
  • Hooked up Industries: IoT gateways in manufacturing environments and embedded instrument in machines may also be up to date by the use of a instrument provisioning carrier. This removes the want to perform a handbook replace. A cloud-based marketing campaign control resolution allows updates to be timed consistent with shift and manufacturing schedules.
  • Power: Power resolution suppliers are increasingly more turning to instrument replace gear and products and services to raised organize the hundreds of thousands of families that at the moment are hooked up to good meter techniques.
  • Client Items: Embedded instrument of client items may also be up to date over the air. Those come with client digital gadgets, house home equipment, e-bikes, and multimedia techniques in automobiles.
  • Construction: Control and keep an eye on of instrument updates for security-relevant apparatus reminiscent of safety cameras.
  • Agriculture: Common instrument updates for sensors, gateways, and controllers in IoT answers for the rural sector.

Extra on instrument updates within the IoT & Bosch IoT Rollouts

Are you searching for a extra normal creation to SOTA and FOTA? We have were given you coated.

Bosch IoT Rollouts is certainly one of 3 Bosch IoT Suite products and services this is to be had on AWS Market.

Bosch IoT Rollouts may be to be had at the IBM Market and within the IBM Cloud Catalog.

To find out extra about Bosch IoT Rollouts.

Check out the documentation to achieve an in-depth figuring out of what Bosch IoT Rollouts is all about.

A site-independent back-end framework for rolling out instrument updates within the IoT: take a look at the primary unlock of Eclipse hawkBit.

Cookie Knowledge

This web site makes use of cookies for causes of capability, convenience, and statistics. In case you consent to this use of cookies, please click on ”Good enough“. In case you love to disable the cookies for webtracking, please click on right here. For more info see our Privateness Coverage


About admin

Check Also

stamford develops ai powered optical computer for driverless cars drones 310x165 - Stamford develops AI-powered optical computer for driverless cars, drones

Stamford develops AI-powered optical computer for driverless cars, drones

A brand new AI-enabled digital camera device may enormously scale back the desire for independent …

Leave a Reply

Your email address will not be published. Required fields are marked *