|
Cellular forums Home > Archive > Cell Phones in Great Britain > April 2008 > Keeping a data connection alive on Three
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Keeping a data connection alive on Three
|
|
| Simon Tennant 2008-04-02, 4:33 am |
| It's a long shot, but I wonder if someone from Three network ops side
can comment (off the record if necessary) on the TCP time outs that
their GPRS data connection uses by default?
Our application tries to hold open a socket on a Symbian phone and
then
waits for TCP packets from a server. The sever then pushes events to
the phone on a semi-regular intervals. However sometimes an event will
not be
received inside of 3 minutes and we notice the connection being
terminated from the operator's side.
We've not encountered this problem on Voda, O2, T-Mobile and Orange.
However on Three we are encountering regular TCP time outs forcing
our
application to reconnect every 3 minutes if not data has been sent.
To me a 3 minute TCP time out already seems low. Do we need to be
polling on a more regular basis just to keep the socket open?
As an aside, do the operators gateways honour TCP Keep-alive packets
sent from the server to phone? I've tried sending them every 60
seconds
but we still see our application having to go through a reconnect
cycle.
Any pointers welcomed.
S.
| |
| White Knight 2008-04-02, 12:34 pm |
| * Simon Tennant wrote:
> It's a long shot, but I wonder if someone from Three network ops side
> can comment (off the record if necessary) on the TCP time outs that
> their GPRS data connection uses by default?
>
> Our application tries to hold open a socket on a Symbian phone and
> then
> waits for TCP packets from a server. The sever then pushes events to
> the phone on a semi-regular intervals. However sometimes an event will
> not be
> received inside of 3 minutes and we notice the connection being
> terminated from the operator's side.
>
> We've not encountered this problem on Voda, O2, T-Mobile and Orange.
> However on Three we are encountering regular TCP time outs forcing
> our
> application to reconnect every 3 minutes if not data has been sent.
>
> To me a 3 minute TCP time out already seems low. Do we need to be
> polling on a more regular basis just to keep the socket open?
>
> As an aside, do the operators gateways honour TCP Keep-alive packets
> sent from the server to phone? I've tried sending them every 60
> seconds
> but we still see our application having to go through a reconnect
> cycle.
>
> Any pointers welcomed.
>
> S.
Aren't you better off just sending a keep-alive ping once every so often
just to keep the connection open? It does seem a bit strange of Three
to do this as it will break most apps that have any period of inactivity
such as the Nokia Maps application.
|
|
|
|
|