Glossary

Bosch IoT Suite

The Bosch IoT Suite provides middleware capabilities needed to build sophisticated IoT applications from top to bottom. It is provided as a set of cloud services.

Bosch IoT Suite website

All pages visible in the www to an anonymous user (as well as web crawlers etc.)

E.g. It presents the service catalog for general information

https://www.bosch-iot-suite.com/service-catalog/

Bosch IoT Suite portal

All functionality which is visible to the authenticated users.
The range of items visible to the authenticated user may vary, based on what he is authorized to see or do.

E.g. It allows to register as a potential customer (B2B), to subscribe free plans, to manage your subscriptions, maintains the legal framework and terms of use

https://www.bosch-iot-suite.com/legal/

https://www.bosch-iot-suite.com/legal/terms-of-use/

Bosch IoT Suite package

A pre-configured instance composed of at least two Suite services.

Asset

An asset can be anything from a tangible and physical device to the more intangible such as a system or the reputation of a company.
In our context, we define an asset as any item, entity, application or even system of applications that can be registered at the Bosch IoT Suite.

Suite authorization

The Bosch IoT Suite portal provides authorization functionality like creating OAuth2 clients.
See https://accounts.bosch-iot-suite.com/oauth2-clients/

Developers can define Clients for a specific Scope.

This component is not subject to be made available as the other Bosch IoT Suite services, but is usable implicitly for all service instances subscribed as a package.

Suite OAuth2 client

An OAuth2 client is created and managed in Suite portal. It grants access to one or more subscribed services. The client consists of client ID, secret and scope. This information is provided as configured into a client application. The client application uses the client to get a token from the Suite authorization token endpoint.

Suite authorization token endpoint

The endpoint (URL) to request authorization tokens. The tokens can be requested according to the OAuth 2 spec RFC 6749. See https://oauth.net/2/.
At the time of writing, we support only "Client Credentials grant".
See https://oauth.net/2/grant-types/client-credentials/.

Suite authorization token

The Bearer token issued by the Suite portal - authorization token endpoint. The token authorizes access to service APIs.

Suite OAuth2 client - client ID

The UUID is generated by the Suite authorization component of the Bosch IoT Suite portal.

Bosch IoT Hub

The Bosch IoT Hub is a cloud service of the Bosch IoT Suite.

It allows you to connect devices through various protocols to IoT applications in an easy and secure manner.

See Bosch IoT Hub

Bosch IoT Hub - Tenant

A tenant in context of the Bosch IoT Hub is a service instance that has been booked via the Suite Portal or marketplaces like the AWS Marketplace.

Bosch IoT Hub - Telemetry

The simplest message type for sending device data to your application via Bosch IoT Hub is telemetry messages.

Bosch IoT Hub - Command and control

Command and control messages provide a way to send messages from Bosch IoT Hub to a device.

Bosch IoT Hub - Device

A device is a representation of physical or logical IoT device at the Bosch IoT Hub service.

Bosch IoT Hub - Gateway

A gateway is a special device which communicates on behalf of another device with the Bosch IoT Hub service.

Bosch IoT Things

The Bosch IoT Things is a cloud service of the Bosch IoT Suite.

A thing is a generic entity and is mostly used to cluster multiple features and manage the access to the data and functionality the thing represents.
A thing may have additional (static) meta data (attributes) that describes the thing in more detail.
See Things and Features.

Bosch IoT Things - Policy

A policy enables developers to configure fine-grained access control in an easy way.
A specific policy defines who (subject) is granted or revoked permissions (rights) on a specific resource.
The resource can be defined as rough or as fine-grained as necessary for the respective use case.
See Bosch IoT Things > Basic concepts > Policies.

Bosch IoT Gateway Software

The Bosch IoT Gateway Software is a middleware stack of the Bosch IoT Suite which provides edge-computing capabilities.

It allows modelling gateway resources such as edge devices, their capabilities and data as functional items.
A device abstraction layer offers a unified interface for devices, regardless of the device type or connectivity protocol.
Additionally, local rules execution and historical data store are available.

Bosch IoT Gateway Software - Device Access (DA)

The Device Access (DA) module aims to abstract away the differences between the various home protocols by defining a common API which enables you to control the devices in your network based on their functionality instead of on the protocol which is used to maintain a connection with them. In the Device Access implementation unification of devices is represented by defining the DA API.
See http://documentation.bosch-si.com/iot/SDK/v9/en/index.htm#85063.htm

Bosch IoT Gateway Software - Functional Items Management (FIM)

The Functional Items Management (FIM) module is part of the Bosch IoT Gateway Software edge computing product.
It aims to unify the control of miscellaneous units (Functional Items or FIs). Within the OSGi framework it provides a common interface to manage different types of controllable components (e.g. devices, user groups, automation, cloud services, UI widgets).
See http://documentation.bosch-si.com/iot/SDK/v9/en/index.htm#78546.htm