Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Queued mode operation, update and send operations clarification #554

Open
davidahoward opened this issue Jan 18, 2023 · 0 comments
Open

Comments

@davidahoward
Copy link

When in Queued mode operation, would the server recognize the send operation as an indication that the client was awake, and be able to send any queued downlink requests?

LwM2M V1.1.1 transport mentions registration update message, but not send:
6.5. Queue Mode Operation
The LwM2M Client lets the LwM2M Server know it is awake by sending a registration update message as a Confirmable message.

It seems to me that a send and a registration update are in fact underneath a CoAP POST command, so the server would be able to know that the client was awake.

If this is the case, can this be made clear in the transport doc and core doc?

OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A
OMA-TS-LightweightM2M_Transport-V1_1_1-20190617-A.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant