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

Flow control in TCP

ozzie avatar
ozzie
9 diapositives · 565 Views · Aug 10, 2014

Flow control in TCP. End-to-end control across a path possibly passing through multiple networks (internet transport protocol) Flow Control: How to prevent receiver buffer overflows? Flow Control in TCP Window-based flow control Called sliding window flow control.

#flow control in tcp #flow control in tcp ppt #powerpoint #presentation
Flow control in TCP - slide 1
01 / 9Flow control in TCP
1 / 17

Télécharger la présentation

Flow control in TCP
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. Flow control in TCP • End-to-end control across a path possibly passing through multiple networks (internet transport protocol) • Flow Control: How to prevent receiver buffer overflows? • Flow Control in TCP • Window-based flow control • Called sliding window flow control

  2. TCP header fields related to flow control and error control • Three fields of interest to error control and flow control in the TCP header • The interpretation of the AckNo and Window size fields: • The sender of the TCP segment with the Ack Number field set to “AckNo” and Window size field set to “Win” is communicating to the far end that it is ready to receive new data with SeqNo= AckNo, AckNo+1, …., AckNo+Win-1 • Receiver can acknowledge data without opening the window • Receiver can change the window size without acknowledging data

  3. TCP header fields - Sequence Number • Sequence Number (SeqNo): • Sequence number is 32 bits long. • So the range of SeqNo is 0 <= SeqNo <= 232 -1  4.3 Gbyte • The sequence number identifies the byte in the stream of data from the sending TCP to the receiving TCP that the first byte of data in this segment represents. • Initial Sequence Number (ISN) of a connection is set during connection establishment

  4. Sliding Window Flow Control • Sliding Window Protocol is performed at the byte level: • Here: Sender can transmit sequence numbers 6,7,8.

  5. Sliding Window: “Window Closes” • Transmission of a single byte (with SeqNo = 6) and acknowledgement is received (AckNo = 5, Win=4):

  6. Sliding Window: “Window Opens” • Acknowledgement is received that enlarges the window to the right (AckNo = 5, Win=6): • A receiver opens a window when TCP buffer empties (meaning that data is delivered to the application).

  7. Sliding Window: “Window Shrinks” • Acknowledgement is received that reduces the window from the right (AckNo = 5, Win=3): • Shrinking a window should not be used - Host requirements RFC strongly discourages this

  8. Sliding Window: Example

  9. TCP error control • Cumulative ACKs are used • In popular implementations, an ACK-every-other-segment strategy is used • Sender keeps an associated timeout value for segments sent. If an ACK is not received before the timer times out, it resends the segment • Retransmission scheme is Go-Back-N ARQ • But Selective repeat along with Selective ACKs have been added as extensions • Piggybacking of ACKs on data segments is indeed used. • If there is no data to send before a delayed-ACK timer expires, a zero-payload segment is sent as an ACK