System overview and technical considerations

G cluster0 cluster4 cluster1 cluster2 celltower thingy91 celltower->thingy91 satellite satellite->thingy91 asset_tracker_v2 thingy91->asset_tracker_v2 AWS gellceo AWS->gellceo aws_api AWS->aws_api Azure azure_api Azure->azure_api nrfcloud gellceo->nrfcloud agnsscloud agnsscloud->nrfcloud pgpscloud pgpscloud->nrfcloud aws_iot aws_iot->AWS azure_iot azure_iot->Azure asset_tracker_v2->aws_iot asset_tracker_v2->azure_iot agnss asset_tracker_v2->agnss web_app_aws aws_api->web_app_aws web_app_azure azure_api->web_app_azure phone web_app_azure->phone web_app_aws->phone

Devices connect to the message broker using TLS over TCP. The messaging protocol is JSON over MQTT. The TLS certificates are generated offline by the developer to simplify the provisioning during production.

The nRF Asset Tracker provides the tools to configure the developer’s cloud account for use with the developer’s devices and the single-page application (SPA). After the cloud account has been configured, it provides the necessary resources for the trackers to connect to the message broker and to send and receive messages. It also provides the appropriate APIs for the SPA to interact with the developer’s devices.

The mobile-first SPA provides a reference implementation of a user interface to control and interact with the devices.