0% found this document useful (0 votes)
25 views26 pages

3.2 Mix Demux Video Slides

Uploaded by

Seif.A. Sayed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
25 views26 pages

3.2 Mix Demux Video Slides

Uploaded by

Seif.A. Sayed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 26

Transport Layer COMPSCI 453 Computer Networks

Professor Jim Kurose


College of Information and Computer Sciences
 Transport-layer services University of Massachusetts

 Multiplexing and demultiplexing


 Connectionless transport: UDP
 Principles of reliable data transfer Class textbook:
Computer Networking: A Top-
 Connection-oriented transport: TCP Down Approach (8th ed.)
J.F. Kurose, K.W. Ross
Pearson, 2020
 Principles of congestion control http://gaia.cs.umass.edu/kurose_ross

 TCP congestion control


 Evolution of transport-layer functionality
Multiplexing/demultiplexing
multiplexing at sender: demultiplexing at receiver:
handle data from multiple use header info to deliver
sockets, add transport header received segments to correct
(later used for demultiplexing) socket

application

application P1 P2 application socket


P3 transport P4
process
transport network transport
network link network
link physical link
physical physical
HTTP server
client
application application
HTTP msg
Ht HTTP msg
transport
Hnetwork
n Ht HTTP msg
transport transport
network link network
link physical link
physical physical
HTTP server
client
application application

transport

transport network transport


network link network
link physical link
physical physical

Hn Ht HTTP msg
HTTP server
client1 client2
application P-client1 P-client2 application

transport

transport network transport


network link network
link physical link
physical physical
How demultiplexing works
 host receives IP datagrams 32 bits
• each datagram has source IP source port # dest port #
address, destination IP address
• each datagram carries one other header fields
transport-layer segment
• each segment has source,
application
destination port number data
 host uses IP addresses & port (payload)
numbers to direct segment to
appropriate socket TCP/UDP segment format
Connectionless demultiplexing
Recall: when receiving host receives
 when creating socket, must UDP segment:
specify host-local port #: • checks destination port # in
segment
DatagramSocket mySocket1
= new DatagramSocket(12534); • directs UDP segment to
socket with that port #
 when creating datagram to
send into UDP socket, must
IP/UDP datagrams with same dest.
specify port #, but different source IP
• destination IP address addresses and/or source port
• destination port # numbers will be directed to same
socket at receiving host
Connectionless demultiplexing: an example
DatagramSocket
serverSocket = new
DatagramSocket
DatagramSocket mySocket2 = DatagramSocket mySocket1 =
new DatagramSocket (6428); new DatagramSocket (5775);
(9157); application
application P1 application
P3 P4
transport
transport transport
network
network link network
link physical link
physical physical

source port: 6428 source port: ?


dest port: 9157 dest port: ?

source port: 9157 source port: ?


dest port: 6428 dest port: ?
Connection-oriented demultiplexing

 TCP socket identified by  server may support many


4-tuple: simultaneous TCP sockets:
• source IP address • each socket identified by its
• source port number own 4-tuple
• dest IP address • each socket associated with
• dest port number a different connecting client
 demux: receiver uses all
four values (4-tuple) to
direct segment to
appropriate socket
Connection-oriented demultiplexing: example
application
application P4 P5 P6 application
P3 P2 P3
transport
transport transport
network
network link network
link physical link
physical server: physical
IP
address
B
host: IP source IP,port: B,80 host: IP
address dest IP,port: A,9157 source IP,port: C,5775 address
A dest IP,port: B,80 C
source IP,port: A,9157
dest IP, port: B,80
source IP,port: C,9157
dest IP,port: B,80
Three segments, all destined to IP address: B,
dest port: 80 are demultiplexed to different sockets
Summary
 Multiplexing, demultiplexing: based on segment,
datagram header field values
 UDP: demultiplexing using destination port
number (only)
 TCP: demultiplexing using 4-tuple: source and
destination IP addresses, and port numbers
 Multiplexing/demultiplexing happen at all layers
Transport Layer COMPSCI 453 Computer Networks
Professor Jim Kurose
College of Information and Computer Sciences
 Transport-layer services University of Massachusetts

 Multiplexing and demultiplexing


 Connectionless transport: UDP
 Principles of reliable data transfer Class textbook:
Computer Networking: A Top-
 Connection-oriented transport: TCP Down Approach (8th ed.)
J.F. Kurose, K.W. Ross
Pearson, 2020
 Principles of congestion control http://gaia.cs.umass.edu/kurose_ross

 TCP congestion control


 Evolution of transport-layer functionality
Video: 2020, J.F. Kurose, All Rights Reserved
Powerpoint: 1996-2020, J.F. Kurose, K.W. Ross, All Rights Reserved
HTTP server
client
application application

transport

transport network transport


network link network
link physical link
physical physical
HTTP server
client
application application

transport

transport network transport


network link network
link physical link
physical physical
?

de-multiplexing
application

? transport

de-multiplexing
multiplexing
application

transport

multiplexing
HTTP server
client1 client2
application P-client1 P-client2 application

transport

transport network transport


network link network
link physical link
physical physical
Multiplexing
Demultiplexing
HTTP server
client
application application
HTTP msg
transport

transport network transport


network link network
link physical link
physical physical
HTTP server
client
application application
HTTP msg
Ht HTTP msg
transport

transport network transport


network link network
link physical link
physical physical

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy