You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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
The text was updated successfully, but these errors were encountered: