Download
transport layer n.
Skip this Video
Loading SlideShow in 5 Seconds..
Transport Layer PowerPoint Presentation
Download Presentation
Transport Layer

Transport Layer

103 Vues Download Presentation
Télécharger la présentation

Transport Layer

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Kingdom of Saudi Arabia • Prince Norah bint Abdul Rahman University • College of Computer Since and Information System • NET331 Transport Layer T.Najah Al-Subaie

  2. Introduction • The Internet model has three protocols at the transport layer: UDP, TCP, and SCTP. • UDP: Is the simplest of the three. • TCP: A complex transport layer protocol. • SCTP: The new transport layer protocol that is designed for specific applications such as multimedia.

  3. Process-to-process Delivery • Real communication takes place between two processes (application programs). We need process-to-process delivery. • We need a mechanism to deliver data from one of these processes running on the source host to the corresponding process running on the destination host. • The transport layer is responsible for process-to-process delivery.

  4. Types of Data Delivery

  5. Connectionless Versus Connection-Oriented Service • A transport layer protocol can either be connectionless or connection-oriented. • Connectionless Service • In a connectionless service, the packets are sent from one party to another with no need for connection establishment or connection release. • The packets are not numbered; they may be delayed or lost or may arrive out of sequence. • There is no acknowledgment . • UDP is a connectionless transport layer protocols.

  6. Connectionless Versus Connection-Oriented Service • Connection Oriented Service • In a connection-oriented service, a connection is first established between the sender and the receiver. • Data are transferred. • At the end, the connection is released. TCP and SCTP are connection-oriented protocols.

  7. Reliable Versus Unreliable • The transport layer service can be reliable or unreliable. • If the application layer program needs reliability, we use a reliable transport layer protocol by implementing flow and error control at the transport layer. This means a slower and more complex service. • On the other hand, if the application program does not need reliability then an unreliable protocol can be used.

  8. Transport Layer Protocols • UDP is connectionless and unreliable; TCP and SCTP are connection oriented and reliable. • These three protocols can respond to the demands of the application layer programs.

  9. Error Control

  10. User Datagram Protocol (UDP) • UDP is a connectionless, unreliable transport protocol. • It does not add anything to the services of IP except to provide process-to process communication instead of host-to-host communication. • UDP is a very simple protocol using a minimum of overhead. • If a process wants to send a small message and does not care much about reliability, it can use UDP. • Sending a small message by using UDP takes much less interaction between the sender and receiver than using TCP or SCTP.

  11. User Datagram • UDP packets, called user datagrams, have a fixed size header of 8 bytes.

  12. User Datagram • Source port number: This is the port number used by the process running on the source host. • Destination port number: This is the port number used by the process running on the destination host. • Length: This is a 16-bit field that defines the total length of the user datagram. • Checksum: This field is used to detect errors over the entire user datagram (header plus data).

  13. Connectionless Services • UDP provides a connectionless service: • no relationship between the different user datagram even if they are coming from the same source process and going to the same destination program. • The user datagrams are not numbered. • Also, there is no connection establishment and no connection termination. • Each user datagram can travel on a different path.

  14. Connectionless Services • There is no flow control: The receiver may overflow with incoming messages. • There is no error control mechanism in UDP except for the checksum. • The sender does not know if a message has been lost or duplicated. • When the receiver detects an error through the checksum, the user datagram is discarded.

  15. Use of UDP • UDP is suitable for a process that requires simple request-response communication with little concern for flow and error control. • UDP is suitable for a process with internal flow and error control mechanisms. For example, the Trivial File Transfer Protocol (TFTP) process includes flow and error control. • UDP is used for management processes such as SNMP.

  16. Transmission Control Protocol(TCP) • TCP is called a connection-oriented, reliable transport protocol. It adds connection-oriented and reliability features to the services of IP. • TCP uses flow and error control mechanisms at the transport level.

  17. Connection-oriented Services • TCP creates an environment in which the two processes seem to be connected by an imaginary "tube“ that carries their data across the Internet.

  18. Connection-oriented Services • When a process at site A wants to send and receive data from another process at site B, the following occurs: • The two processes establish a connection between them. • Data are exchanged in both directions. • The connection is terminated.

  19. Reliable Transport Protocol • TCP is a reliable transport protocol. It uses an acknowledgment mechanism to check the safe arrival of data. • Flow Control: • The receiver of the data controls the amount of data that are to be sent by the sender. • Error Control. • Congestion Control: • The amount of data sent by a sender is controlled by the level of congestion in the network.

  20. TCP Segment Format

  21. TCP Segment Format • The segment consists of a 20-60-byte header. • Source port address: • This is a 16-bit field , it defines the port number of the application program in the host that is sending the segment. • Destination port address: • This is a 16-bit field, it defines the port number of the application program in the host that is receiving the segment.

  22. TCP Segment Format • Sequence number: • This 32-bit field defines the number assigned to the first byte of data contained inthis segment. • Acknowledgment number: • This 32 bit field defines the number of the next byte a party expects to receive. • Header length: • A 4-bit field that indicates the number of 4-byte words in the TCP header.

  23. TCP Segment Format • Control. This field defines 6 different control bits or flags. One or more of these bits can be set at a time.

  24. TCP Segment Format

  25. TCP Connection • A Connection-oriented transport protocol establishes a virtual path between the source and destination. • In TCP, connection-oriented transmission requires three phases: connection establishment, data transfer, and connection termination.

  26. Connection Establishment • TCP transmits data in full-duplex mode • Example: Client-server communication using TCP as the transport layer protocol. • The server issues a request for a passive open: • The server program tells its TCP that it is ready to accept a connection. • The client program issues a request for an active open: • A client that wishes to connect to an open server tells its TCP that it needs to be connected to that particular server.

  27. Three-step Connection Establishment • The client sends the first segment, a SYN segment: • A SYN segment does not carry data, but it consumes one sequence number. • The server sends the second segment, a SYN +ACK segment. • It is a SYN segment for communication in the other direction and an acknowledgment for the SYN segment. • A SYN +ACK segment cannot carry data, but does consume one sequence number. • The client sends the third segment. This is just an ACK segment. It acknowledges the receipt of the second segment. • An ACK segment, if carrying no data, consumes no sequence number.

  28. Three-step Connection Establishment Using Three-way Handshaking

  29. Data Transfer

  30. Connection Termination Using Three-way Handshaking

  31. Lost Segment

  32. Notes • The FIN segment consumes one sequence number if it does not carry data. • The FIN + ACK segment consumes one sequence number if it does not carry data. • The FIN + ACK segment consumes one sequence number if it does not carry data. • No retransmission timer is set for an ACK segment. • Data may arrive out of order and be temporarily stored by the receiving TCP, but TCP guarantees that no out-of-order segment is delivered to the process.