TCP overage

  • 1
  • Question
  • Updated 7 days ago
im sending 64 bytes tcp (non ssl) to a server, and its sending 1 byte back every 3 minutes.
my billing and data usage shows 272 bytes from device and 129 to device...???? 
what with that..  billing is 5 times larger than it should be
Photo of Breck Ricketts

Breck Ricketts

  • 2 Posts
  • 0 Reply Likes

Posted 2 months ago

  • 1
Photo of Royce Arnold

Royce Arnold

  • 9 Posts
  • 0 Reply Likes
A couple of thoughts:

1.  Are you considering TCP/IP overhead?  There are about 40 bytes of non-payload data consumed by every data packet.

2.  If you are not transmitting directly to an IP address, there may be a domain look up occurring.   Based on your usage, I suspect that you are transmitting to an IP address.  Otherwise, I would expect higher values.

3.  TCP/IP is also connection based.  That means that additional data is consumed to open / close the port and to acknowledge data transmissions.  If you want to minimize that, you may want to consider UDP which is connection-less, but may not be as reliable for all applications.

RA

Photo of Breck Ricketts

Breck Ricketts

  • 2 Posts
  • 0 Reply Likes
1.  no, im not.  my service plan is per 750k/month.  and the overhead has been about 240 bytes, not 40. and if its TCP, it can be much more if the connection wasn't reliable.  so my business model is if Im sending 750k per month, I want to billed for 750k per month, not  3 to 4 meg....

2. no im not using lookup

3.  UDP has overcharge also.  If I send 64 bytes, I get billed for 92.  thats not what it should be
Photo of Royce Arnold

Royce Arnold

  • 9 Posts
  • 0 Reply Likes
Breck,

I'm just a fellow user...  It sounds like from your response, that you are expecting that your purchase of 750K should exclude overhead required by the protocols that you are using.  I'm unaware of any cellular carrier that works that way (or any internet service provider).

Sorry, I was just offering an explanation of where the additional data may have been coming from.

RA