"Achieving high data rates using TCP/IP over satellite networks can be difficult" - review and discuss.

Authors Avatar

CCM 3060        Page         5/6/2007        

Coursework 1

Question 1

a). “Achieving high data rates using TCP/IP over satellite networks can be difficult”- review and discuss  

       some of the reasons TCP/IP has difficulty with satellite links, including the following issues: IP

       Throughput, IP Time To Live, IP Fragmentation, TCP Throughput and Throughput Expectations, TCP

       Sequence Numbers, TCP Transmission Window, Slow Start, and Congestion Avoidance.

 Achieving high data rates using Transmission Control Protocol & Internet Protocol (TCP/IP) over satellite networks can be difficult because satellite links have a high latency, which causes the reduction of the performance of some protocols like TCP/IP that are commonly used.

The main reason to this problem is the design of TCP/IP. They were not designed to be applied in wireless environment, they were actually meant to be used in fixed networks only that are end-to-end and based on reliability and connection orientation.

For example, the Internet, which is the biggest computer network consisting of millions of terminals is based on the TCP/IP protocol architecture, since it is a fixed Virtual Area Network (VAN). The architecture of TCP was designed to be used in networks with high Bit Error Rates (BERs), and it will not work well in wireless environment, where losses are due to high BERs. Besides, because IP relies on end-to-end data verification, it is unsuitable for wireless links. TCP/IP has not the ability to handle the delay that occurs when performing transmission to and from the satellite. This is also due to the time delay of the physical link.

IP Throughput

As already has been mentioned, IP’s job is to perform end-to-end data verification, which means providing a protocol to join various networks together enable data exchange. IP datagrams will be moved by routers among the different media and their encapsulations. The information about the path to the right destination will be found in the IP datagram itself. But IP’s service is unreliable, since it may loose data, deliver data with errors or duplicate datagrams. It also does not limit its throughput and has no control on the speed of the system for generating and receiving datagrams. But the IP’s throughput can be affected by the “IP Time To Live and “IP Fragmentation”.

IP Time To Live

Because IP datagrams sometimes loop among the routers without reaching the destination, IP puts a limitation, which determines how long a datagram should live in the network. This limit will be set by the so called “Time to Live “ (TTL) field for every second, which will apply the limit on every router the datagram passes on and will discard the datagram when the TTL is at 0. Because of this, the higher layer protocols have to be careful that they do not send to similar datagrams within two minutes, since the maximum time for a datagram to live in the network is only two minutes, if so there will be a confusion. This particularly implies for sequence numbers, which will be discussed later.

Join now!

IP Fragmentation

Applying this to different network media, since they put different limitations on the maximum size of the datagram, IP supports fragmentation that allows to split the data into smaller datagrams, and finally reassemble them at the destination. To identify the fragments, a fragment offset will be used indicating the offset of the fragment of the datagram from its very beginning.

Heiko Holtkamp, “TCP/IP in Detail”

 (13/10/02)

TCP Throughput

Besides IP, TCP is the one who performs the primary transportation in the TCP/IP protocol suite. As discussed earlier, IP provides an unreliable ...

This is a preview of the whole essay