-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major
-
None
-
Affects Version/s: None
-
Component/s: MQTT-SN
-
None
-
Environment:
It should be possible for the GW to optionally interrupt the sleep of a client when the GW deems it necessary (for example it has a large buffer or important messages to deliver).
The client may not be able to respond or CHOOSE not to respond, in which case all the rules of sleep are maintained.. however if it CAN respond and if it chooses to, it should be able to wake up by responding with a PINGRESP and then awaiting outstanding messages - the rest of the sleep state is governed by the normal rule, ie. GW terminated using a PINGRESP.
Why? many new cellular technologies provide the capability of waking devices up from various states of sleep or deep sleep (for example WuS 3gpp rev 15). It would be wise to enable the network to attempt to wake devices when it deems fit.
It should be possible for the GW to optionally interrupt the sleep of a client when the GW deems it necessary (for example it has a large buffer or important messages to deliver). The client may not be able to respond or CHOOSE not to respond, in which case all the rules of sleep are maintained.. however if it CAN respond and if it chooses to, it should be able to wake up by responding with a PINGRESP and then awaiting outstanding messages - the rest of the sleep state is governed by the normal rule, ie. GW terminated using a PINGRESP. Why? many new cellular technologies provide the capability of waking devices up from various states of sleep or deep sleep (for example WuS 3gpp rev 15). It would be wise to enable the network to attempt to wake devices when it deems fit.
Cf. comment below (MQTT-606#8483) for a possible diagram / structure of the packet as part of a proposal for a new section.