[OASIS Issue Tracker] (MQTT-599) In ASLEEP state also a PUBLISH-1 should trigger the sending of the pending messages on the subscribed topics

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=82424#comment-82424 ] 

Davide Lenzarini commented on MQTT-599:
---------------------------------------

Hi Simon,

The scenario that I have in mind is the following:
 * A device sends CONNECT with very long Session Expiry Interval, REGISTER a topic name 1, SUBSCRIBE to a topic2 and finally send DISCONNECT with very long Session Expiry Interval
 * Every 24 hours the device sends a PUBLISH-1 on the registered topic alias, so the Gateway moves it from ASLEEP to ACTIVE state and sends it the PUBLISH messages queued on topic2. Finally the Gateway moves it back from ACTIVE to ASLEEP by sending a PINGRESP

In this scenario the device that needs to send a PUBLISH-1 is not required to send also the PINGREQ and so it can save energy. The PUBLISH-1 message should not only reset the keep alive but also move the device status from ASLEEP to AWAKE.

Does it make sense to you?

Thanks

Davide

> In ASLEEP state also a PUBLISH-1 should trigger the sending of the pending messages on the subscribed topics
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MQTT-599
>                 URL: https://issues.oasis-open.org/browse/MQTT-599
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>            Reporter: Davide Lenzarini
>            Priority: Major
>
> In ASLEEP state also a PUBLISH-1 should trigger the sending of the pending messages on the subscribed topics terminating with a PINGRESPÂ
> The scenario that I have in mind is the following:
>  # A client CONNECT to a gateway (client enrollment) with a very long session expiry interval
>  # The client subscribe to a certain topic to receive pending messages as soon as it sends a publish-1 message to a certain (also different) topic
>  # The client DISCONNECTÂwith a very long session expiry interval
>  # After some time the client send a PUBLISH-1 message and would like to receive (like with the PINGREQ when in ASLEEP state) all pending messages on the topic it has subscribed toÂ
> Â
> Â



--
This message was sent by Atlassian Jira
(v8.3.3#803004)