Cellular Billing - Includes TCP / IP Headers

I am currently creating an application designed to work in an embedded system connected to a cellular data card. I have been informed of some plans with low data from several operators, and our application generates only about 5 bytes per second, lending itself to such plans.

However, I cannot understand that the overhead of TCP / IP (about 40 bytes, give or receive) is included in the calculation for using the data. Since I need real-time data, I turned off the Nagle algorithm. This means that every 5-byte packet I send, I send a new header. If the TCP / IP headers are taken into account in the data usage price, this will overshadow the amount of data that I send.

+4
source share
2 answers

I cannot answer definitively, but I would suggest that they should. Otherwise, this can be used by adding additional data to the headers. Using TCP, you send a 40-byte packet and then receive a 40-byte acknowledgment packet. You can try using UDP instead of TCP so you donโ€™t have to spend data with confirmation packets.

+4
source

According to an email from Sprint, "any data that passes through our network, including the header of the network [sic.], Will be billed or counted according to your plan."

+3
source

Source: https://habr.com/ru/post/1343938/


All Articles