Note that there are some explanatory texts on larger screens.

plurals
  1. POPUSH notifications via GPRS/3G. How stable are they?
    primarykey
    data
    text
    <p>I do an application design for a soft real-time software application now. </p> <p>The application will probably need to notify its mobile users about some events in the system. An event can happen during a 15-minute time frame which starts after the user's first interaction with the system. The event notification should be done in soft real-time: if a user notified later than 15-20 seconds he was supposed to be notified, then it is critical. Basically, I need to notify a mobile user about an event no later than 15-20 seconds after that event happens during a 15-minutes time frame.</p> <p>I plan to do that with some kind of <a href="http://en.wikipedia.org/wiki/Push_technology" rel="nofollow noreferrer">PUSH technology</a> (XMPP/Jabber, native app with <a href="http://en.wikipedia.org/wiki/Comet_%28programming%29" rel="nofollow noreferrer">Comet</a> connection or maybe <a href="http://en.wikipedia.org/wiki/Push_email" rel="nofollow noreferrer">PUSH email</a>).</p> <p>Unfortunately, the most obvious solution which is to have mobile web-site (example: <a href="http://www.lightstreamer.com/" rel="nofollow noreferrer">http://www.lightstreamer.com/</a>) with real-time push notifications is not suitable, because in that case the user will have to stare at the screen during all the 15-minute time frame. Notifying a user with a sound or a vibration would be a much more pleasant user experience (connect to the system via smartphone -> start interaction with the system -> put the smartphone back into the pocket or a bag -> get notified).</p> <p>I have done a simple experiment by sending Jabber chat messages between my laptop (WiFi/100Mbit) and my Android smartphone (GPRS/3G). The thing is that some of the messages sent to the smartphone are late (it takes about 1 minute until they arrive at the smartphone) or just lost (they never arrive at the smartphone). Moreover, I have noticed that the Jabber client at the smartphone goes offline regularly for a few seconds. I do not know if it is because I have a very cheap Android smartphone or because the 3G connection is not very good, but this behaviour is not acceptable for the software application that I design.</p> <p>Thus, I am interested in the following:</p> <ul> <li>is there any technology standard that can <em>guarantee</em> pushed message delivery to mobile (GPRS/3G) consumers in <em>soft real-time</em>? I.e. a technology standard which guarantees that a mobile client will be notified no later than N seconds from now;</li> <li>do you know any examples of mobile apps which have soft <em>real-time</em> push notifications?</li> <li>what are the ways to address the issue of delivering/pushing soft real-time messages to mobile devices in soft real-time? (e.g. keep sending the same message until the mobile device confirms the receipt of the message)</li> </ul> <p><em>P.S. The intended use of the software application is with any smartphone, be it iPhone, Android, WP or any other internet-connected smartphone.</em></p> <p><em>Note: This question is similar to <a href="https://stackoverflow.com/questions/10499388/real-time-two-side-push-communication-via-gprs">one</a> of my previous questions, but this one is about on a completely different use-case with strong focus on soft real-time requirements.</em></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload