Device resource management
Resources are sensors and actuators in a device. Device Resource management means, for example, reading a temperature value or controlling a device-activated door lock.
You can use the Device Management services to manage device Resources and execute actions on these devices. The functionality relies on an integration of the Device Management Connect API for your web-server application and on the Device Management Client API for your device application.
Device Management Client also supports periodic and event-triggered reporting of Resource values. The web application, through the Cloud LwM2M server, can set a rule-based subscription to an Object, an Object Instance or a Resource, which then results in asynchronous notifications when an Object Instance changes. You can do this for each resource that you have specified to be Observable.
Read more in the Event notification channel section.
The overall device communication flow is illustrated in this diagram:
- Devices register to make their Resources discoverable in a standard way. This was covered in the Connecting section.
- The web application is notified of the device registration.
- Web applications send REST requests to Device Management Connect to receive information from the device, or to send instructions to the application on the device.
- Most REST requests are handled in asynchronous mode, so Device Management Connect returns the code 202 to the application.
- Device Management Connect ensures that the request is delivered to the device.
- The client responds to Device Management Connect.
- Device Management Connect sends the final asynchronous response (also called notification) to the web application's webhook.
About the documentation
This section reviews the resource model Device Management Connect uses, then explains how to use the APIs to:
- Create and configure Objects and Resources.
- Access and use Objects and Resources.
- Observe Resource values.
- Manage Resources through the Device Management Portal.