Glossary
Term |
Context |
Definition |
Acknowledgement |
Digital twin layer |
An acknowledgement (ACK) is a confirmation that a request was processed successfully. |
Acknowledgement |
Device connectivity layer |
An acknowledgement is sent from Bosch IoT Hub to a device or to a business application as a confirmation for receiving of a message. The devices and applications can also send acknowledgements to Bosch IoT Hub. |
Action |
Software updates layer |
Requested operations for the targets. Usually a software update. Other supported actions are the cancellation of a running update action, or a refresh request for target attributes. See software updates layer > Bosch IoT Rollouts > Action |
Action |
Mass management layer |
The action element of a mass management task, or of a mass management rule respectively, is a Groovy script which defines the effect which the task/rule is intended to produce, for example the execution of device actions and/or the calling of internal or external cloud service APIs. See Tasks |
Action Status |
Software updates layer |
Status information of an action which can be provided by the target. This can be the start of the action life-cycle, the end, or update notifications in between. See software updates layer > Bosch IoT Rollouts > Action Status |
Artifact |
Software updates layer |
An artifact is a file of any type which has been uploaded to the software updates layer, namely Bosch IoT Rollouts. It may contain firmware, an application, or a link to external artifact references. See software updates layer > Bosch IoT Rollouts > Artifact |
Asset |
Bosch IoT Suite |
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.
|
Auto Assignment |
Software updates layer |
Targets which match a target filter get a distribution set automatically assigned. See software updates layer > Bosch IoT Rollouts > Auto Assignment |
Bosch IoT Edge |
Bosch IoT Edge |
Bosch IoT Edge has two components:
See Bosch IoT Edge |
Bosch IoT Edge Services |
Bosch IoT Edge |
Bosch IoT Edge Services is part of the Bosch IoT Edge offering. |
Bosch IoT Hub |
Device connectivity layer |
Bosch IoT Hub is a cloud service of Bosch IoT Suite. It allows you to connect devices through various protocols to IoT applications in an easy and secure manner. See Device connectivity layer, namely Bosch IoT Hub |
Bosch IoT Manager |
Mass management layer |
Bosch IoT Manager is a flexible cloud service that provides a valuable set of device management functionalities needed in IoT solutions. These include mass device management, rule-based automation, monitoring, diagnostics and troubleshooting of various connected devices communicating via different protocols. |
Bosch IoT Suite |
Bosch IoT Suite |
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 UI |
Bosch IoT Suite |
A Web UI available for customers of Bosch IoT Suite. Sometimes Bosch IoT Suite UI is also referred to as Bosch IoT Suite Console or Developer Console. |
Bosch IoT Suite website |
Bosch IoT Suite |
All the pages visible in the www to an anonymous user (as well as web crawlers etc.) For example, it presents the service catalog for general information: |
Bosch IoT Things |
Digital twin layer |
Bosch IoT Things is the digital twin layer of Bosch IoT Suite. The digital twin of a physical device is called a thing. See digital twin layer > Things and Features |
Bosch IoT |
Software updates layer |
Bosch IoT Rollouts is a domain-independent cloud service for rolling out software updates to constrained edge devices, as well as more powerful controllers, and gateways connected to IP-based networking infrastructure. See software updates layer > Bosch IoT Rollouts |
Client certificate |
Device connectivity layer |
A client certificate is the credential type to authenticate the devices. |
Cloud Protocol Gateway |
Device connectivity layer |
The cloud protocol gateway is a custom component that must be implemented and operated by customers. It acts like a software gateway and needs to be registered in the device connectivity layer, namely Bosch IoT Hub Device Registry, as a device. It is responsible for authenticating the physical devices which communicate via this gateway and for transferring the device’s proprietary protocol into the protocol used by the device connectivity layer protocol adapter. |
Command and control |
Device connectivity layer |
Command and control messages provide a way to send messages from the device connectivity layer, namely Bosch IoT Hub, to a device . |
Condition |
Mass management layer |
The condition of a mass management rule determines whether the firing of the respective rule will lead to its triggering, i.e. to the execution of the defined action on the managed devices. It may be implemented as:
See Rules |
Connection |
Digital twin layer |
A connection in general describes that two parts are linked with each other. See Connections |
Credential registry management |
Device connectivity layer |
Credential registry management is one of the central components of Bosch IoT Hub for persisting of the information that is required to connect devices to Bosch IoT Hub. It exposes service endpoints implementing credentials API of Eclipse Hono™. |
Credentials |
Device connectivity layer |
Credentials serve as a proof-of-identity in the context of the Bosch IoT Hub service. |
Developer Console |
Bosch IoT Suite |
A Web UI available for customers of Bosch IoT Suite. Sometimes Bosch IoT Suite UI is also referred to as Developer Console as per the button from which you enter. |
Device |
Device connectivity layer |
A device is a representation of a physical or logical IoT device at the device connectivity layer, namely the Bosch IoT Hub service. |
Device connection time |
Device connectivity layer |
Device connection time is the time during which the device is connected to Bosch IoT Hub. |
Device identity management |
Device connectivity layer |
Device identity management is one of the central components of Bosch IoT Hub for persisting of the information that is required to connect devices to Bosch IoT Hub. The device identity management component exposes service endpoints implementing the device registration of Eclipse Hono™. |
Device Inventory |
Mass management layer |
The Device Inventory provides capabilities for detailed monitoring of device states and configurations, as well as for listing, filtering and grouping devices, which is also needed when defining the scope of mass management operations. |
Device via gateway |
IoT devices |
A device behind a gateway will in general not need to register its own credentials with the device connectivity layer. Instead it will authenticate via the gateway credentials. |
Digital twin |
Digital twin layer |
The concept of a digital twin, its definition, and thus the expectations vary from one manufacturer to another. |
Distribution Set (DS) |
Software updates layer |
A distribution set defines a meta package that combines a set of software modules which have to be provisioned entirely See software updates layer > Bosch IoT Rollouts > Distribution Set |
Distribution Set Type |
Software updates layer |
A distribution set type is an abstract definition of a distribution set that indicates which types of software modules can be added (optionally or mandatorily). See software updates layer > Bosch IoT Rollouts > Distribution Set Type |
Eclipse Ditto |
Digital twin layer |
Eclipse Ditto is a framework for providing the digital twin pattern for IoT applications in order to interact with IoT devices. The Bosch IoT Things service is based on and powered by the open source project Eclipse Ditto. |
Eclipse hawkBit |
Device connectivity layer |
Eclipse hawkBit is a domain-independent back-end framework for rolling out software updates to constrained edge devices as well as to more powerful controllers and gateways connected to IP-based networking infrastructure. The Bosch IoT Rollouts service is based on and powered by the open source project Eclipse hawkBit. |
Eclipse Hono |
Device connectivity layer |
Eclipse Hono provides remote service interfaces for connecting large numbers of IoT devices to a back end and interacting with them in a uniform way regardless of the device communication protocol. The Bosch IoT Hub service is based on and powered by the open source project Eclipse Hono. |
Eclipse Vorto |
Device model |
Eclipse Vorto is an open source project for semantic modelling of digital twins and their capabilities. |
Event |
Digital twin layer |
In the context of the digital twin layer, an event reports that a change has been applied to a thing entity. Example: A property value of a feature is modified.
Find further details related to the communication protocol at digital twins > Protocol. |
Event message |
Device connectivity layer |
Via events you can send messages from your device to your application.
See Event example |
Event storage time (TTL) |
Device connectivity layer |
Event storage time is the time interval during which event messages are stored in the Bosch IoT Hub messaging system to guarantee the delivery of the messages to a business application. |
Functional Items Management (FIM) |
Bosch IoT Edge |
The Functional Items Management (FIM) module is part of Bosch IoT Edge Services. It aims to unify the control of miscellaneous units (functional items or FIs). See Bosch IoT Edge Services > Functional Items Management |
Gateway |
Device connectivity layer |
A gateway is a special device which communicates on behalf of another device with the Bosch IoT Hub service. |
Gateway device |
IoT devices |
A gateway device is supposed to be able to reach the device connectivity layer by itself, e.g. to be IP-ready, and to help other devices to authenticate via its gateway credentials. |
Guaranteed delivery |
Device connectivity layer |
Bosch IoT Hub guarantees delivering of a message to a business application. The delivery is guaranteed only for event messages. |
LoRaWAN enabled devices
|
Device connectivity layer |
LoRaWAN enabled devices use LoRaWAN protocol for communication with a LoRa gateway. |
Mass Management |
Mass management layer |
A process which simplifies and facilitates the execution of management actions over large numbers of devices
with a single operation. See Mass Management |
Message |
Digital twin layer |
In the context of the digital twin layer a message can be used to transport arbitrary data between IoT devices and applications. A message does not directly affect the state of a thing entity. Therefore, Bosch IoT Things does not handle messages like commands, i.e. there are no responses which are produced by our service and no events which are emitted for messages. Instead, the message needs to be handled respectively by your device or application. Example: From an application’s perspective, a message can be sent to a thing or one of its features to call e.g. an operation at a device.
Find further details related to the communication protocol at digital twin> Protocol. |
Metadata |
Digital twin laye r |
A thing may optionally contain metadata information, e.g. about single feature properties, complete features and also attributes or other data stored in a digital twin (thing). This metadata can contain additionally information which shall not be treated as part of the twin’s value, however may be useful to provide some context of the twin’s data. Metadata has not its own API but can only be updated/set while modifying the state of a twin as a side effect. By default, metadata is not returned at API requests, but must be asked for explicitly.
|
Metadata |
Software updates layer |
Metadata is key-value based information which can be freely modified for describing and identifying distribution sets (DS) and software modules (SM). See software updates layer > Bosch IoT Rollouts > Metadata |
Namespace |
Digital twin layer |
A namespace is the prefix for your things and policies. You can use the namespace to separate things from different solution spaces from each other, or to organize things of different types within your subscription. |
One-way-command
|
Device connectivity layer |
One-way-command is a communication pattern supported by Bosch IoT Hub. One-way-commands are sent from a connected business application through Bosch IoT Hub to a connected device. The device does not confirm the receipt of the command. |
Organization |
Bosch IoT Suite |
The Bosch IoT Suite provides the possibility to book the Bosch IoT services for your projects. All bookings of one account is represented as an organization. Each booking within the organization is depicted as subscription. All users invited to participate in a organization is represented as a team. All team members will be able to see all subscriptions of the organization they are invited for. The separation per subscription additionally helps to better track the service usage (e.g. data storage and data transfer) belonging to the service instances.
|
Policy |
Digital twin layer |
A policy enables developers to configure fine-grained access control in an easy way. See digital twin layer > Policies |
Protocol adapter
|
Device connectivity layer |
Protocol adapters enable devices that communicate via different protocols to be connected to Bosch IoT Hub. |
Request/response command
|
Device connectivity layer |
Request/response command is a communication pattern supported by Bosch IoT Hub. The request/response commands are sent from a connected business application through Bosch IoT Hub to a connected device. After the command was received by a device, the device confirms the receipt of the command. |
Rollout |
Software updates layer |
A software update on (a large set of) devices in a managed and defined way. See software updates layer > Bosch IoT Rollouts > Rollout |
Rule |
Mass management layer |
A rule is the automated execution of a mass management task or a series of such tasks upon the occurrence of a defined trigger, which consists of an event and condition. When the relevant event occurs, the rule is fired and this leads to evaluation of its condition. If the condition is satisfied, the rule is triggered, i.e. a new task is launched and the execution of the defined action script is started. One triggering of the rule launches one new task.
In addition, rules provide a number of ways in which this automation can be tailored to the needs of the use case. See Rules |
Scope |
Mass management layer |
The scope element of a mass management task or rule defines the targets (devices) on which a management action will be executed. There are two scope alternatives - device scope and system scope. See Tasks |
Sensor
|
Device connectivity layer |
A sensor is a module of a device that detects and measures changes in the environment and sends this information to Bosch IoT Hub. |
Software Module (SM) |
Software updates layer |
A software module is a logical bracket for a set of artifacts based on a defined software module type. See software updates layer >Bosch IoT Rollouts > Software Module |
Software Module Type |
Software updates layer |
A software module type is an abstract definition of a software module and can be either firmware or software. The names for each of these types in the web UI are OS and Application, respectively. A distribution set of the type OS only can contain only one software module of the firmware type. A distribution set of the type App(s) only can contain multiple software modules of the software type. A distribution set of the type OS with Apps can contain only one software module of the firmware type and multiple software modules of the software type. Each new subscription is provided with the default distribution set types and software module types, which can be used as an example of the described concept. If needed, you can create your own abstract representation of a distribution set and software module following the same principle.
See Software updates layer > Bosch IoT Rollouts > Software Module Type |
Stand-alone device |
IoT devices |
A stand-alone device is supposed to be able to reach the device connectivity layer by itself, e.g. to be IP-ready, and to authenticate itself at the device connectivity layer (not via gateway). |
Subscription |
Bosch IoT Suite |
The Bosch IoT Suite provides the possibility to book the Bosch IoT services for your projects. All bookings of one account is represented as an organization. Each booking within the organization is depicted as subscription. All users invited to participate in a organization is represented as a team. All team members will be able to see all subscriptions of the organization they are invited for. The separation per subscription additionally helps to better track the service usage (e.g. data storage and data transfer) belonging to the service instances.
|
Suite authorization |
Bosch IoT Suite |
The Bosch IoT Suite provides authorization functionality such as creating OAuth2 clients. Developers can define clients for a specific scope. This component is usable implicitly for all service instances subscribed as a solution. |
Suite authorization token |
Bosch IoT Suite |
The bearer token issued by the Bosch IoT Suite - authorization token endpoint. The token authorizes access to service APIs. |
Suite authorization token endpoint |
Bosch IoT Suite |
The endpoint (URL) to request authorization tokens. |
Suite OAuth2 client |
Bosch IoT Suite |
An OAuth2 client is created and managed in the Bosch IoT Suite. 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 OAuth2 client - client ID |
Bosch IoT Suite |
The UUID is generated by the Suite authorization component of the Bosch IoT Suite. |
Tag |
Mass management layer |
Тhe Device Inventory of Bosch IoT Manager provides three group types - static directory groups and tag groups, and dynamic filter groups. Tags are also treated as groups and facilitate the search for devices according to flexible criteria. If you add multiple tags to a device, it will be included in multiple tag groups. See mass management layer > Bosch IoT Manager > Grouping devices |
Tag |
Software updates layer |
Tags are strings used to describe and identify targets and distribution sets. See software updates layer > Bosch IoT Rollouts > Tag |
Target |
Software updates layer |
A target identifies which device, gateway etc. needs the software update. (a.k.a. controller) See software updates layer > Bosch IoT Rollouts > Target |
Target Attributes |
Software updates layer |
Attributes are key-value based meta data information sent by a target and stored within the Rollouts server. See software updates layer > Bosch IoT Rollouts > Target Attributes |
Target Filter |
Software updates layer |
Filtering of targets by a defined query. Target filters are used for auto assignments or to select targets for a rollout. See software updates layer> Bosch IoT Rollouts > Target Filter |
Task |
Mass management layer |
Tasks are instantly launched one-off executions of a management action script on a set of devices (i.e. scope), as adjusted by execution options. One of the main building blocks of the mass management process. See Tasks |
Team |
Bosch IoT Suite |
The Bosch IoT Suite provides the possibility to book the Bosch IoT services for your projects. All bookings of one account is represented as an organization. Each booking within the organization is depicted as subscription. All users invited to participate in a organization is represented as a team. All team members will be able to see all subscriptions of the organization they are invited for. The separation per subscription additionally helps to better track the service usage (e.g. data storage and data transfer) belonging to the service instances.
|
Telemetry message |
Device connectivity layer |
The simplest message type for sending device data to your application via the device connectivity layer is telemetry messages. A telemetry message provides a way to send device data to your application without guaranteed delivery. |
Tenant |
Device connectivity layer |
A tenant in context of the device connectivity layer, namely Bosch IoT Hub, is a service instance that has been booked via the Bosch IoT Suite. |
Thing |
Digital twin layer |
A thing is the digital representation of an IoT device or any type of asset. |
Time to disconnect (TTD)
|
Device connectivity layer |
Time to disconnect specifies the time the device remains connected to the protocol adapter. |
Trigger |
Mass management layer |
A trigger is an element of a mass management rule, which starts the automatic execution of a management action script (launching of a mass management task) upon the occurrence of the defined events and conditions. The triggers supported by Bosch IoT Manager are:
|
Vorto model |
Device model |
Semantic models of digital twins that can be used by Bosch IoT Suite and third party applications. |