Bosch IoT Rollouts

SOUP Features

The System Software Update extension is currently under development. The provided documentation aims to give insights into the general concepts of the future offering. However, details including APIs may be subject to change.


images/confluence/download/attachments/3496952754/soup-infographic-version-2-modificationdate-1700237049000-api-v2.png

Preface: Modules vs. Targets

In the context of a system an updatable device is called a module. This differs from the Bosch IoT Rollouts terminology where target is used to address not only a device, but also a complete system and particular parts of a device.

System repository

  • Manage systems consisting of a gateway and multiple updatable and non-updatable modules.

  • System identification: Algorithm and options on how a system is identified by a set of modules.

  • System lifecycle: Handle creation of systems and modifications on the set of modules within the system.

Recipe management

  • Recipe lifecycle: Differentiates between draft, release-candidate (limited access for testing), released and retired.

  • 4-eyes principle for approving recipes to released state.

  • Signatures: Detect undesired modifications of released recipes.

  • Customizable recipe transformation to a format which is understood by the system's gateway - default transformation/example:

System update management

  • Identify the latest matching recipe for a specific system.

  • Enable online and offline update scenarios.

  • Track the latest known state of a system.

  • Concepts to support release-notes and user consent

Interfaces

  • Graphical user interface for managing systems and recipes.

  • HTTP/REST APIs (with Swagger documentation), in particular:

    • a user-facing API for managing and listing content,

    • a device facing API exposing recipes and software to be installed on systems.

Authentication

  • Bosch.IdM integration

  • Bosch IoT Suite OAuth2 clients

  • Bosch User Hub + Single Key ID