SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Understanding the Transport Layer: Functions, Connection Management, and TCP Protocols

daria-allison avatar
daria-allison
22 diapositives · 382 Views · Dec 01, 2014

This presentation discusses the transport layer of computer networks, focusing on protocols like TCP and their critical functions. It explains the concepts of multiplexing, demultiplexing, and connection management, including the establishment and teardown of connections. The three-way handshake for TCP connection setup and the importance of managing sequence numbers to ensure reliable data transmission are detailed. Additionally, the presentation covers error control mechanisms and flow control, vital for maintaining performance and reliability in data communication.

#understanding the transport layer: functions, connection management, and tcp protocols #understanding the transport layer: functions, connection management, and tcp protocols ppt #powerpoint #presentation
Understanding the Transport Layer: Functions, Connection Management, and TCP Protocols - slide 1
01 / 22Understanding the Transport Layer: Functions, Connection Management, and TCP Protocols
1 / 17

Télécharger la présentation

Understanding the Transport Layer: Functions, Connection Management, and TCP Protocols
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. SidevõrgudIRT 0020loeng 7 11. okt. 2005 Avo Otstelekommunikatsiooni õppetool, TTÜ raadio- ja sidetehnika inst.avo.ots@ttu.ee

  2. Basic Telephone Network • Supports a single application: Telephone • An end host is a telephone • Each telephone makes only one voice stream • Even with call-waiting and 3-way calling Application Telephone Layer Telephone numbering, signaling, routing TelephoneNetwork (Data) Link TDMA Layer

  3. Application telnet, ftp, email Layer Transport TCP, UDP Layer Network IP Layer (Data) Link 802.3, 802.11 Layer Datagram Computer Network • Supports many applications • Each end host is usually a general purpose computer • Each end host can be generating many data streams simultaneously • Insert Transport Layer to create an interface for different applications • Provide (de)multiplexing • Provide value-added functions

  4. ports p1 p2 p1 p2 p3 p1 p2 A B C Using Transport Layer Port Number (De)multiplex traffic telnet HTTP ssh Application TCP Transport IP In TCP, a data stream is identified by a set of numbers: (Source Address, Destination Address, Source Port, Destination Port)

  5. Transport • Lowest level end-to-end protocol. • Header generated by sender is interpreted only by the destination • Routers view transport header as part of the payload • Adds functionality to the best-effort packet delivery IP service. • Make up for the shortcomings of the core network 5 5 Transport Transport IP IP IP Datalink 2 2 Datalink Physical 1 1 Physical router

  6. Transport Protocol Functions • Multiplexing/demultiplexing for multiple applications. • Port abstraction • Connection establishment. • Logical end-to-end connection • Connection state to optimize performance • Error control. • Hide unreliability of the network layer from applications • Many types of errors: corruption, loss, duplication, reordering. • End-to-end flow control. • Avoid flooding the receiver

  7. Transmission Control Protocol • Reliable bidirectional in-order byte stream • Socket: SOCK_STREAM • Connections established & torn down • Multiplexing/ demultiplexing • Ports at both ends • Error control • Users see correct, ordered byte sequences • End-end flow control 0 16 32 Source Port Dest. Port Sequence Number Acknowledgment Number HL/Flags Advertised Win. Checksum Urgent Pointer Options..

  8. High Level TCP Features • Sliding window protocol • Use sequence numbers • Bi-directional • Each host can be a receiver and a sender simultaneously

  9. Connection Setup • Mainly to agree on starting sequence numbers • Starting sequence number is randomly chosen • Reason, to reduce the chance that sequence numbers of old and new connections from overlapping

  10. Important TCP Flags • SYN: Synchronize • Used when setting up connection • FIN: Finish • Used when tearing down connection • ACK • Acknowledging received data

  11. Establishing Connection • Three-Way Handshake • Each side notifies other of starting sequence number it will use for sending • Each side acknowledges other’s sequence number • SYN-ACK: Acknowledge sequence number + 1 • Can combine second SYN with first ACK SYN: SeqC Client Server ACK: SeqC+1 SYN: SeqS ACK: SeqS+1

  12. Client Server TCP State Diagram: Setup CLOSED active OPEN Snd SYN passive OPEN CLOSE CLOSE LISTEN delete TCB SEND rcv SYN SYN RCVD SYN SENT snd SYN ACK snd SYN rcv SYN snd ACK Rcv SYN, ACK rcv ACK of SYN Snd ACK CLOSE ESTAB Send FIN

  13. Tearing Down Connection • Either Side Can Initiate Tear Down • Send FIN signal • “I’m not going to send any more data” • Other Side Can Continue Sending Data • Half open connection • Must continue to acknowledge • Acknowledging FIN • Acknowledge last sequence number + 1 A B FIN, SeqA ACK, SeqA+1 Data ACK FIN, SeqB ACK, SeqB+1

  14. Active Close Passive Close State Diagram: Tear-down CLOSE ESTAB send FIN CLOSE rcv FIN send FIN send ACK FIN WAIT-1 CLOSE WAIT rcv FIN CLOSE snd ACK ACK snd FIN rcv FIN+ACK FIN WAIT-2 CLOSING LAST-ACK snd ACK rcv ACK of FIN rcv ACK of FIN TIME WAIT CLOSED rcv FIN Timeout=2 MSL snd ACK

  15. Sequence Number Space • Each byte in byte stream is numbered. • 32 bit value • Wraps around • Initial values selected at start up time • TCP breaks up the byte stream in packets (“segments”) • Packet size is limited to the Maximum Segment Size • Set to prevent packet fragmentation • Each segment has a sequence number. • Indicates where it fits in the byte stream 13450 14950 16050 17550 segment 8 segment 9 segment 10

  16. Setting Retransmission Timeout (RTO) • Time between sending & resending segment • Challenge • Too long: Add latency to communication when packets dropped • Too short: Send too many duplicate packets • General principle: Must be > 1 Round Trip Time (RTT) Initial Send Initial Send RTO RTO Ack Retry Retry Ack Detect dropped packet RTO too short

  17. Round-trip Time Estimation • Every Data/Ack pair gives new RTT estimate • Can Get Lots of Short-Term Fluctuations Data Sample Ack

  18. Original TCP Round-trip Estimator • Round trip times estimated as a moving average: • New RTT = a (old RTT) + (1 - a) (new sample) • Recommended value for a: 0.8 - 0.9 • 0.875 for most TCP’s • Retransmit timer set to b RTT, where b = 2 • Want to be somewhat conservative about retransmitting

  19. A B Original transmission RTO ACK Sample RTT retransmission RTT Sample Ambiguity • Ignore sample for segment that has been retransmitted A B Original transmission X RTO Sample RTT retransmission ACK

  20. Congestion (1) • The load placed on the network is higher than the capacity of the network • Not surprising: independent senders place load on network • Results in packet loss: routers have no choice • Can only buffer finite amount of data • End-to-end protocol will typically react, e.g. TCP

  21. Congestion (2) • Wasted bandwidth: retransmission of dropped packets • Poor user service : unpredictable delay, low user goodput • Increased load can even result in lower network goodput • Switched nets: packet losses create lots of retransmissions • Broadcast Ethernet: high demand -> many collisions Goodput “congestion collapse” Load

  22. How Fast to Send • Send too slow: link sits idle • wastes time • Send too fast: link is kept busy but.... • queue builds up in router buffer (delay) • overflow buffers in routers (loss) • Many retransmissions, many losses • Network goodput goes down safe operating point Goodput Load