In the Field
Once an IoT Gateway has completed commissioning with its unique certificate and an assigned business unit, it enters its main lifecycle period in the field.
During this period, the device operates under the ownership of its assigned business unit, maintaining a bidirectional link with Bifrost to report edge telemetry and receive instructions from your cloud services:
Reporting telemetry and receiving commands
While active in the field, the device communicates over its dedicated certificate connection:
- Outbound telemetry: The device captures data from its connected controllers and sensors and publishes telemetry payloads to Bifrost according to its configuration and setup.
- Inbound commands and updates: The device listens for instructions issued through Bifrost, including day-to-day operational commands and OTA firmware updates.
Accessing device data downstream
As telemetry arrives from a device in the field, Bifrost decodes the payload against the controller's registered schema and routes the data to the owning business unit (see Where Data Lands).
Consumers in that business unit can access the incoming data using their business unit's IAM roles (see Permission Levels and Authenticating) through two interfaces:
- Real-time streaming: Consume records directly from your business unit's Kinesis stream (
bifrost-prod-telemetry-{businessUnitKey}). See Consuming the Telemetry Stream. - On-demand queries: Query recent telemetry for your devices over HTTP via
GET /v1/telemetry. See Consuming the Data API.
When a unit eventually reaches the end of its deployment or needs to be retired from active rotation, it moves to Decommissioning.