Bandwidth save GPRS and TCP?

Let's do some math here. Every 5 seconds is 720 connections per hour plus data. 20K / 720 is about 28 bytes of payload (your GPS data) for each connection.

IP and TCP headers along are 48 bytes in addition to whatever data is being sent. 3-way handshake connection: 3 packets (2 out, 1 in) == 96 bytes out and 48 bytes in Outbound Data-packet: 48+28 bytes == 76 bytes (out) Inbound Ack: 48 bytes (in) Close: 48 bytes (out) Final Ack: 48 bytes (in) Total out per connection: 220 Total in per connection: 144 Total data send/received per connection: 220+144 = 364 Total data usage in one hour = 364 * 720 = 262K So I'm in the ballpark of your data usage estimates. If you're looking to reduce bandwidth usage, here's two ideas: Scale back on your update rate.

Don't tear down the socket connection each time. Just keep it open. Given your GPS coordinates are periodically updated, you could consider using UDP instead of TCP.

There's potential for packet loss, but given you're retransmitting fresher data every 5 seconds anyway, an update getting lost isn't worth the bandwidth to retransmit. IP and UDP headers combined are only 28 bytes with no "connection" overhead.

Thank you ,very helpful estimation :) – Parhs Mar 6 at 12:50 I sent 290 packets gps info. 8240 bytes total. According to calcuations it should take ~106 kb.

But it took 150kb. I cant figure out where did these bytes came from – Parhs Mar 6 at 14:41.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.