nRF93M1 integrates with nRF Cloud to provide device provisioning, data messaging, device shadow, cell- and Wi-Fi-based location, firmware update, and firmware observability.
Overview
nRF Cloud services are exposed through a family of %NRFCLOUD* AT commands.
The transport is CoAP over DTLS 1.2 (libcoap and Mbed TLS), which keeps message overhead
small while secure and is compatible with cellular power-saving modes. Each cloud
transaction emits a %COAP: URC that carries the transport-layer status for
that request.
Provisioning and authentication
Each device presents two stable identities and two short-lived credentials to the cloud:
%DEVICEUUID— a 36-character device UUID that is generated once and stored in non-volatile memory.%CLOUDACCESSKEY— a P-256 ECC public key in Base64-DER form. The corresponding private key is generated on-chip once and never leaves the device.%REGJWT— a signed registration JWT used during device on-boarding.%JWT— a short-lived authentication JWT (approximately 1 hour validity). The device system time must be valid for the JWT to be accepted by the cloud.
Data services
- Location (
%NRFCLOUDLOCATION) — several location methods covering single-cell, multi-cell, Wi-Fi, and combinations. The response carries<latitude>, <longitude>, <uncertainty_m>, <fulfilled_method>. Multi-cell and Wi-Fi methods require the modem to be in RRC Idle. - Messaging (
%NRFCLOUDMESSAGE) — publishes a JSON payload to the cloud over CoAP (for example{"appId":"BUTTON","data":"1"}). - Shadow (
%NRFCLOUDSHADOW) — reads a dotted path from the device's desired shadow and writes a dotted path into the reported shadow. - FOTA (
%NRFCLOUDFOTA) — see the firmware-update description in the LTE Modem chapter.