chap5transportlayer4创新.ppt

TCP Flow Control receive side of TCP connection has a receive buffer: TCP Flow Control speed-matching service: matching the send rate to the receiving application’s drain (排干) rate! TCP Flow control: how it works (Suppose TCP receiver discards out-of-order segments) spare room in buffer = RcvWindow = RcvBuffer-[LastByteRcvd - LastByteRead] Receiver advertises spare room by including value of RcvWindow in segments Sender limits unACKed data to RcvWindow guarantees receive buffer doesn’t overflow TCP Connection Management Recall: TCP sender, receiver establish “connection” before exchanging data segments initialize TCP variables: seq. #s 【ISN, Initial Sequence Number】 buffers, flow control info (e.g. RcvWindow) client: connection initiator Socket clientSocket = new Socket(hostname,port number); connect （server，destPort） server: contacted by client Socket connectionSocket = welcomeSocket.accept(); TCP Connection Management Three way handshake: Step 1: client host sends TCP SYN segment to server specifies initial seq # no data Step 2: server host receives SYN, replies with SYNACK segment server allocates buffers specifies server initial seq. # Step 3: client receives SYNACK, replies with ACK segment, which may contain data TCP Connection Management (cont.) Closing a connection: client closes socket: clientSocket.close(); Step 1: client end system sends TCP FIN control segment to server Step 2: server receives FIN, replies with ACK. Closes connection, sends FIN. TCP Connection Management (cont.) Step 3: client receives FIN, replies with ACK. Enters “timed wait” - will respond with ACK to received FINs Step 4: server, receives ACK. Connection closed. Note: with small modification, can handle simultaneous FINs. TCP Connection Management (cont) TCP Congestion Control end-end control (no network assistance) If the sender perceives that there is little congestion, the sender increases its send rate If the sender perceives that there is a co