Functionality

Things - features

Management of IoT assets

  • Manage data of things - also known as digital twins
    especially their attributes - which are rather static
    and their feature properties - which are rather dynamic (e.g. for configuration, status and fault)
  • Manage life-cycle of things
    • device provisioning
    • updates based on telemetry data and events (device-to-cloud)
    • updates based on remote messages (cloud-to-device)
    • deletion
  • Represent and use the functionality of things
  • Complex search
  • Dashboard, to
    • browse all IoT assets
    • manage your connections, namespaces
    • keep track on quota limits, etc.

Integration for applications

  • Easy to use REST-like HTTP API for access and interaction with data and functionality of things
  • Java client and JavaScript client to access all data and functionality of your things
  • Protocol based communication on twin and live channel
  • Persistent connections to various endpoints
    (e.g. Bosch IoT Hub, Bosch IoT Insights, AMQP, MQTT, AWS IoT MQTT, Apache Kafka)
    and optional payload mapping - in case your endpoint expects another type on how the payload is organized
    See also Which API to use?
  • Option to enrich and/or filter the events which are forwarded to authorized subjects

Integration for devices

  • Integration for devices is supported via Java client, JavaScript client and WebSocket protocol
    including support for custom Hubs/Gateways
  • Your “direct” devices (IP ready) can be connected via Bosch IoT Hub
  • Your “indirect” devices (non-IP ready) can be connected via Bosch IoT Gateway Software
  • See also Bosch IoT Suite for Asset Communication

Security

  • Secured access to information about things via all protocols
  • Fine-grained access control on things via policies
  • User authentication for users with a JWT issued by
    • the Bosch IoT Suite - Suite Auth service
    • a Bosch ID account,
    • a Google account,
    • or your custom registered OAuth2 authorization provider
      (which needs to be OpenID Connect compliant)
  • Client authentication with a JWT issued by
    • the Bosch IoT Suite - Suite Auth service
    • or your custom registered OAuth2 authorization provider
      (which needs to be OpenID Connect compliant)
  • Optional - custom business activation process to take ownership of a thing (See Claiming)
  • Fine-grained access control on your subscription via solution policy

Messaging, events and notifications

  • Secured subscriptions on authorized information for applications via managed connections (integrations)
  • Fine-grained read permissions on things, in case notifications for each changes on data and life-cycle changes are needed
  • Live messages can be routed directly to devices

Meta model for device abstraction

  • Unified language to describe devices based on Eclipse Vorto
    See http://www.eclipse.org/vorto/
  • Describes structures and functionality of devices
  • Leverage device description for contract-based development of large-scale or cross-domain solutions
  • Basis for implementation of device drivers and device-specific protocols
    as well as code templates for solution development

Development kit

  • Code generator plug-in for Eclipse Vorto to support solution development (open source)
  • Eclipse Ditto tooling (open source)
  • Additionally, for Asset Communication package
    • Device Provisioning API
    • Developer Console
    • Bosch IoT Gateway Software SDK
Imprint Legal info Privacy statement