Downloaded 162 times
Uploaded byTutun Juhana
Transport Layer Part 1
This document discusses various aspects of transport layer protocols in computer networks, including: - Addressing processes using port numbers between 0-65,535 - The client-server model where clients use ephemeral ports over 1023 and servers use well-known ports - Transport layer services like multiplexing, demultiplexing, flow control using buffers, error control using sequence numbers and acknowledgments, and congestion control - Connection-oriented protocols like TCP provide reliable data delivery compared to connectionless protocols like UDP. - Stop-and-wait, go-back-N, and selective-repeat protocols aim to increase efficiency over simple retransmission by allowing multiple outstanding packets.
More Related Content
Similar to Transport Layer Part 1
More from Tutun Juhana
Transport Layer Part 1
- 1. 6 Tutun Juhana Telecommunication Engineering TransportLayer School of Electrical Engineering & Informatics Institut Teknologi Bandung Computer Networks
- 2.
- 3.
- 4. Addressing: Port Numbers •To define the processes, we need identifiers called port numbers • In the TCP/IP protocol suite, the port numbers are integers between 0 and 65,535 4
- 5. • In client-serverparadigm: – Client program defines itself ephemeral port number Short lived recommended to be greater than 1,023 – Server process must use well-known port numbers 5
- 6.
- 7.
- 8.
- 9. Socket Addresses • Socketaddress is the combination of an IP address and a port number 9
- 10.
- 11.
- 12.
- 13.
- 14. Although flow controlcan be implemented in several ways, one of the solutions is normally to use two buffers. One at the sending transport layer and the other at the receiving transport layer 14
- 15. Error Control 1. Detectand discard corrupted packets. 2. Keep track of lost and discarded packets and resend them. 3. Recognize duplicate packets and discard them. 4. Buffer out-of-order packets until the missing packets arrive. 15
- 16.
- 17.
- 18. Acknowledgment • We canuse both positive and negative signals as error control • The receiver side – can send an acknowledgement (ACK) for each or a collection of packets that have arrived safe and sound – can simply discard the corrupted packets • The sender can detect lost packets if it uses a timer – When a packet is sent, the sender starts a timer; when the timer expires, if an ACK does not arrive before the timer expires, the sender resends the packet. – Duplicate packets can be silently discarded by the receiver. Outof order packets can be either discarded (to be treated as lost packets by the sender), or stored until the missing ones arrives.18
- 19. Combination of Flowand Error Control 19
- 20.
- 21. Congestion Control • Congestioncontrol refers to the mechanisms and techniques to control the congestion and keep the load below the capacity 21
- 22. Open-Loop Congestion Control •Retransmission Policy • Window Policy • Acknowledgment Policy 22
- 23. Closed-Loop Congestion Control •Closed-loop congestion control mechanisms try to alleviate congestion after it happens 23
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30. Efficiency • The Stop-and-Waitprotocol is very inefficient if our channel is thick and long – By thick, we mean that our channel has a large bandwidth (high data rate) – by long, we mean the round-trip delay is long – The product of the above two is called the bandwidth-delay product – We can think of the channel as a pipe. The bandwidth-delay product then is the volume of the pipe in bits – The pipe is always there. If we do not use it, we are inefficient. – The bandwidth-delay product is a measure of the number of bits a sender can transmit through the system while waiting for an acknowledgment from the receiver. 30
- 31.
- 32. Pipelining • In networkingand in other areas, a task is often begun before the previous task has ended This is known as pipelining • There is no pipelining in the Stop-and-Wait protocol because a sender must wait for a packet to reach the destination and be acknowledged before the next packet can be sent 32
- 33.
- 34.
- 35.
- 36.
- 37. • Timers – Althoughthere can be a timer for each packet that is sent, in our protocol we use only one. The reason is that the timer for the first outstanding packet always expires first. We resend all outstanding packets when this timer expires. • Resending packets – When the timer expires, the sender resends all outstanding packets 37
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.