4.5. Notifications support
Some Resources may represent values that change over time, like sensor readings. A LwM2M Server may be interested in variance of such values and use the Observe operation to request notifications when they change, or when their value meets certain criteria.
See also
More information about available notification criteria can be found under <NOTIFICATION> Class Attributes description in Attributes.
When some part of the data model changes by means other than LwM2M, one has to tell the library about it by calling an appropriate function:
if a Resource value changed -
anjay_notify_changed()
,if one or more Object Instances were created or removed -
anjay_notify_instances_changed()
.
Anjay then decides if the notification shall be sent, based on the currently assigned Attributes (to the part of the data model being changed) and LwM2M Servers that are interested in seeing the change.
Note
One should not call anjay_notify_changed()
/anjay_notify_instances_changed()
when the value change was directly caused by LwM2M (e.g. by Write or Create
request). Anjay handles these cases internally.
See also
Detailed description of these functions can be found in API docs.
Calling anjay_notify_changed()
/anjay_notify_instances_changed()
does not
send notifications immediately, but schedules a task to be run on next event
loop iteration. That way, notifications for multiple values can be handled as a
batch, for example in case where the server observes an entire Object Instance.
4.5.1. LwM2M attributes
Correct handling of LwM2M Observe requests requires being able to store Object/Instance/Resource attributes. For that, one needs to either implement a set of attribute handlers, or use the pre-defined Attribute Storage subsystem. In this tutorial, we use pre-defined Attribute Storage subsystem here.
4.5.2. Example
As an example we’ll add notification support for the Time Object implemented
in previous Implementing standard Object section. It contains a Current Time
Resource, whose value changes every second. We need to periodically notify the
library about that fact and for this purpose, we create a
time_object_notify()
function in the time_object.c
file, but first, we
need to modify time_instance_t
a little. This will allow to store the last
timestamp when the anjay_notify_changed()
was successfully called, to avoid
calling it twice during one second. Although it will not result in sending two
notifications with the same Resource value, because Anjay checks it internally,
it will lead to performing some unnecessary actions (like calling read handler
for example).
typedef struct time_instance_struct {
anjay_iid_t iid;
char application_type[64];
char application_type_backup[64];
int64_t last_notify_timestamp;
} time_instance_t;
void time_object_notify(anjay_t *anjay, const anjay_dm_object_def_t **def) {
if (!anjay || !def) {
return;
}
time_object_t *obj = get_obj(def);
int64_t current_timestamp;
if (avs_time_real_to_scalar(¤t_timestamp, AVS_TIME_S,
avs_time_real_now())) {
return;
}
AVS_LIST(time_instance_t) it;
AVS_LIST_FOREACH(it, obj->instances) {
if (it->last_notify_timestamp != current_timestamp) {
if (!anjay_notify_changed(anjay, 3333, it->iid, RID_CURRENT_TIME)) {
it->last_notify_timestamp = current_timestamp;
}
}
}
}
At last, we need to declare the function in the object’s header file.
#ifndef TIME_OBJECT_H
#define TIME_OBJECT_H
#include <anjay/dm.h>
const anjay_dm_object_def_t **time_object_create(void);
void time_object_release(const anjay_dm_object_def_t **def);
void time_object_notify(anjay_t *anjay, const anjay_dm_object_def_t **def);
#endif // TIME_OBJECT_H
Now we need to somehow call this function while the Anjay main loop is running.
This may be performed in several ways - additional tasks may be handled in a
separate thread, or a Custom event loop may be
implemented instead of using anjay_event_loop_run()
. However, the simplest
solution is to utilize Anjay’s internal scheduler.
Before calling anjay_event_loop_run()
, our application extracts the
scheduler object by calling anjay_get_scheduler() and schedules a
specially crafted notify_job()
function to run, using AVS_SCHED_DELAYED().
To run the function periodically, this call to AVS_SCHED_DELAYED()
is in
fact called at the end of notify_job()
, and notify_job()
itself is
called from the main function to schedule the first run for simplicity.
#include <anjay/anjay.h>
#include <anjay/security.h>
#include <anjay/server.h>
#include <avsystem/commons/avs_log.h>
#include "time_object.h"
typedef struct {
anjay_t *anjay;
const anjay_dm_object_def_t **time_object;
} notify_job_args_t;
// Periodically notifies the library about Resource value changes
static void notify_job(avs_sched_t *sched, const void *args_ptr) {
const notify_job_args_t *args = (const notify_job_args_t *) args_ptr;
time_object_notify(args->anjay, args->time_object);
// Schedule run of the same function after 1 second
AVS_SCHED_DELAYED(sched, NULL, avs_time_duration_from_scalar(1, AVS_TIME_S),
notify_job, args, sizeof(*args));
}
// Installs Security Object and adds and instance of it.
// An instance of Security Object provides information needed to connect to
// LwM2M server.
static int setup_security_object(anjay_t *anjay) {
if (anjay_security_object_install(anjay)) {
return -1;
}
static const char PSK_IDENTITY[] = "identity";
static const char PSK_KEY[] = "P4s$w0rd";
anjay_security_instance_t security_instance = {
.ssid = 1,
.server_uri = "coaps://eu.iot.avsystem.cloud:5684",
.security_mode = ANJAY_SECURITY_PSK,
.public_cert_or_psk_identity = (const uint8_t *) PSK_IDENTITY,
.public_cert_or_psk_identity_size = strlen(PSK_IDENTITY),
.private_cert_or_psk_key = (const uint8_t *) PSK_KEY,
.private_cert_or_psk_key_size = strlen(PSK_KEY)
};
// Anjay will assign Instance ID automatically
anjay_iid_t security_instance_id = ANJAY_ID_INVALID;
if (anjay_security_object_add_instance(anjay, &security_instance,
&security_instance_id)) {
return -1;
}
return 0;
}
// Installs Server Object and adds and instance of it.
// An instance of Server Object provides the data related to a LwM2M Server.
static int setup_server_object(anjay_t *anjay) {
if (anjay_server_object_install(anjay)) {
return -1;
}
const anjay_server_instance_t server_instance = {
// Server Short ID
.ssid = 1,
// Client will send Update message often than every 60 seconds
.lifetime = 60,
// Disable Default Minimum Period resource
.default_min_period = -1,
// Disable Default Maximum Period resource
.default_max_period = -1,
// Disable Disable Timeout resource
.disable_timeout = -1,
// Sets preferred transport to UDP
.binding = "U"
};
// Anjay will assign Instance ID automatically
anjay_iid_t server_instance_id = ANJAY_ID_INVALID;
if (anjay_server_object_add_instance(anjay, &server_instance,
&server_instance_id)) {
return -1;
}
return 0;
}
int main(int argc, char *argv[]) {
if (argc != 2) {
avs_log(tutorial, ERROR, "usage: %s ENDPOINT_NAME", argv[0]);
return -1;
}
const anjay_configuration_t CONFIG = {
.endpoint_name = argv[1],
.in_buffer_size = 4000,
.out_buffer_size = 4000,
.msg_cache_size = 4000
};
anjay_t *anjay = anjay_new(&CONFIG);
if (!anjay) {
avs_log(tutorial, ERROR, "Could not create Anjay object");
return -1;
}
int result = 0;
// Setup necessary objects
if (setup_security_object(anjay) || setup_server_object(anjay)) {
result = -1;
}
const anjay_dm_object_def_t **time_object = NULL;
if (!result) {
time_object = time_object_create();
if (time_object) {
result = anjay_register_object(anjay, time_object);
} else {
result = -1;
}
}
if (!result) {
// Run notify_job the first time;
// this will schedule periodic calls to itself via the scheduler
notify_job(anjay_get_scheduler(anjay), &(const notify_job_args_t) {
.anjay = anjay,
.time_object = time_object
});
result = anjay_event_loop_run(
anjay, avs_time_duration_from_scalar(1, AVS_TIME_S));
}
anjay_delete(anjay);
time_object_release(time_object);
return result;
}
That’s all you need to make your client support LwM2M Observe/Notify operations!
Note
Complete code of this example can be found in examples/tutorial/BC-Notifications subdirectory of main Anjay project repository.