New LWM2M Send Scheduler objects

[jvermillard]

I would like to register two new object on the behalf of my customer EDF R&D

The two objects are described in this DDF file:
https://github.com/clunkymachines/lwm2m-sendsched/blob/main/ddf/send_scheduler.xml

The Telemetry Sampling & Send Scheduler object provides a standardized way to configure how LwM2M devices collect, filter, batch, and transmit telemetry using the LwM2M Send/Data Push mechanism.

Today, vendors implement this behavior in proprietary ways, leading to inconsistent sampling rules and incompatible telemetry policies. This object family defines:

• Sampling Rules (resource paths, thresholds, step, min/max intervals)
• Send Scheduling (flush on max age, max samples, or registration update)

The goal is to enable consistent, energy-efficient telemetry behavior across LPWA devices and ensure cross-vendor interoperability.

More details:

A Zehpyr based open-source implementation: https://github.com/clunkymachines/lwm2m-sendsched/
And a demo video: https://drive.proton.me/urls/FP9F2WS5MR#1WTEyTWWbU7F
Discussions about possible Zephyr up-streaming: zephyrproject-rtos/zephyr#97621

[gocadimic]

@jvermillard,

The DDF.xml file was updated with new placeholders for 10523 and 10524.

We created a new branch edf-obj-reserve, with the two placeholders for the object reservation, IDs 10523-10524.
Your next step is to fork the lwm2m-registry repository and, there, prepare your object contribution.

Fully qualified 10523.xml and 10524.xml files should be submitted to the given branch edf-obj-reserve for version 1.0. Please ensure that the content of DDF.xml matches the request in issue #858.

Once the new Object is submitted, the 10523.xml and 10524.xml files, with the same content as in DDF.xml, must be submitted to the version_history folder and named 10523-1_0.xml and 10524-1_0.xml, respectively.

The final step would be creating a PR against the prod branch.
Once we see your PR, we will proceed with the validation.

Please let us know if you have any questions.
For more explanation, see README.md

[jvermillard]

#860