Transport Layer Fundamentals

Transport Layer Overview

The transport layer is the fourth layer of the OSI reference model. It is responsible for providing a reliable data transfer service between endpoints.

---

1. The Core Role of the Transport Layer

1.1 End-to-End Process Communication: The Final Link in Network Communication

Why Is Process Communication Needed?

The building analogy:

A concrete case:

• Network layer: find your computer (192.168.1.10)
• Transport layer: find your browser (port 80)
• Application layer: retrieve the web page (HTTP service)

A more vivid analogy:

The network layer is like a courier finding your home address; the transport layer is like the courier knocking on your door and handing the parcel to you personally.

How Process Communication Is Implemented

The transport layer identifies processes with port numbers:

Sender:

• Your computer’s IP: 192.168.1.10
• Browser process port: an ephemeral port (for example 54321)
• Target server IP: 202.108.22.5
• Target service port: 80 (the HTTP service)

What the transport layer guarantees: the data travels from port 54321 on 192.168.1.10 to port 80 on 202.108.22.5, completing end-to-end communication.

---

1.2 Transport Layer Addressing: The World of Port Numbers

The Role of Port Numbers

The room number analogy:

What port numbers do:

1. Identify a process: tell the data which process it belongs to
2. Distinguish services: separate different network services (HTTP, FTP, and so on)
3. Manage connections: distinguish different connections in TCP
4. Dispatch data: deliver data to the correct application

Classification of Port Numbers

1. Well-known ports: 0-1023

Analogy: the public service zone of a building (reception, lifts, fire escapes).

These ports are allocated centrally by IANA for common services:

2. Registered ports: 1024-49151

Analogy: the office zone of a building (the company’s offices).

These ports are allocated to specific applications:

3. Dynamic ports: 49152-65535

Analogy: the temporary activity rooms of a building (for occasional use).

The operating system allocates these dynamically for temporary client connections:

For example, when you open a browser and visit a site, the operating system assigns the browser a temporary port such as 54321; when the connection closes the port is released and made available to other programs.

Allocation and Management of Port Numbers

How the operating system allocates ports:

Server side:

• Well-known services use fixed ports (for example HTTP uses 80)
• The port is bound at start-up
• The service then waits for client connections

Client side:

• When a connection is initiated, the operating system allocates a port dynamically
• It normally comes from the dynamic range (49152-65535)
• The port is released automatically when the connection ends

Port conflicts:

The problem: two programs both want to use port 80.

The resolution:

1. The program that starts first takes the port
2. The program that starts second reports “port already in use”
3. One of them has to change port or the port holder has to be closed

---

1.3 Multiplexing and Demultiplexing: The Switching Centre of Data Transmission

The Process of Multiplexing and Demultiplexing

The telephone exchange analogy:

Multiplexing (several people calling): Zhang San, Li Si, and Wang Wu → the telephone → the line → the exchange (three people share the same telephone while calling).

Demultiplexing (forwarding an incoming call): the exchange → the line → the telephone → Zhang San / Li Si / Wang Wu (the call is forwarded to the person identified by the caller display).

Multiplexing and demultiplexing in the network:

Sender (multiplexing): three applications (browser 54321, mail client 54322, chat client 54323) share the transport layer service and hand everything to the network layer as one stream.

Receiver (demultiplexing): network → network layer → transport layer, which distributes the data to the matching application process according to the port number.

How Multiplexing and Demultiplexing Are Implemented

How the transport layer demultiplexes:

Receiving a packet: IP packet → TCP/UDP segment → extract the port numbers.

The demultiplexing steps:

1. Check the destination port: 80 (the HTTP service)
2. Look up the process bound to that port: the web server process
3. Hand the data to that process
4. The process handles the data

A concrete example:

Scenario: the server receives several requests.

Demultiplexing: data on port 80 → the web server; data on port 25 → the mail server.

---

1.4 Error Detection and Reliability: The Quality Guarantee of Data Transmission

The Error Detection Mechanism

Error detection in the transport layer:

Sender:

1. Segment the data
2. Add a checksum
3. Send the segment

Receiver:

1. Receive the segment
2. Compute the checksum
3. Compare it with the sender’s checksum
4. If they do not match, discard the segment
5. If they match, accept the segment

What the checksum does:

The courier analogy: the courier inspects the appearance of the parcel (the checksum), refuses a damaged parcel (discarding the data), and accepts an intact one (accepting the data).

The Reliability Mechanism

How TCP guarantees reliability:

1. Sequence numbers: every byte is numbered, so the order of the data is preserved
2. Acknowledgements: the receiver confirms receipt and the sender learns that the data has arrived
3. Retransmission: unacknowledged data is sent again, so nothing is lost
4. Flow control: the sending rate is controlled so the receiver is not overloaded
5. Congestion control: network congestion is controlled so the network stays stable

The simplicity of UDP:

UDP offers no reliability guarantee: no sequence numbers, no acknowledgements, no retransmission, no flow control — only basic error detection.

---

2. The Difference Between the Transport Layer and the Network Layer

2.1 Comparison by Layer Function

2.2 How the Two Layers Relate

The network layer is the foundation, the transport layer is the extension:

Network layer: handles communication between hosts, provides IP addressing and routing, and moves data from one host to another.

Transport layer: builds on the network layer to provide process-to-process communication, adds port-based addressing, and moves data from one process to another.

The building analogy:

Network layer: finds the building address (the IP address) and delivers the letter to the entrance of the building.

Transport layer: finds the specific room number (the port number), delivers the letter to the door of that room, and makes sure the letter arrives intact (reliability).

---

3. The Two Transport Layer Protocols

3.1 TCP: Reliable Transmission

Characteristics of TCP

Connection-oriented:

• A connection has to be established beforehand (the three-way handshake)
• Connection state is maintained during the exchange
• The connection is released at the end (the four-way teardown)

Reliability guarantees:

• Intact data: errors are detected with a checksum
• Ordered data: order is preserved with sequence numbers
• Error-free data: errors are corrected by retransmission
• No loss: delivery is confirmed with acknowledgements

Flow control:

• The sliding window mechanism
• Prevents the sender from going too fast
• The receiver controls the sending rate

Congestion control:

• Slow start and congestion avoidance
• Fast retransmit and fast recovery
• Prevents network congestion

Where TCP Applies

---

3.2 UDP: Fast Transmission

Characteristics of UDP

Connectionless:

• No connection has to be established
• Data is sent directly
• No connection state is maintained

Simple and efficient:

• Small protocol overhead
• Fast processing
• Straightforward implementation

No reliability guarantee:

• Data may be lost
• Data may arrive out of order
• Nothing is retransmitted

Good real-time behaviour:

• Low latency
• No delay for establishing a connection
• Suitable for real-time applications

Where UDP Applies

---

3.3 TCP vs UDP

Choosing between them:

When to use TCP:

• Data integrity matters, loss is unacceptable, the volume is large, and real-time behaviour is not critical.

When to use UDP:

• Real-time behaviour matters, the volume is small, some loss is acceptable, and reliability is not critical.

---

4. Worked Examples

Example 1: The Process of Visiting a Website

Let us look at the role of the transport layer when you visit a website.

Scenario: a browser visits www.baidu.com.

1. Application layer: the browser issues an HTTP request
2. Transport layer (TCP):
   • Port selection: the client’s (browser) ephemeral port 54321, the server’s (Baidu) HTTP port 80
   • Connection establishment: the three-way handshake
   • Data transfer: the HTTP request is sent
3. Network layer:
   • IP address: the client 192.168.1.10 → the server 202.108.22.5
   • Routing and forwarding: the packets reach the server hop by hop
4. The server receives:
   • Network layer: receives the IP packet
   • Transport layer: extracts destination port 80 and hands the data to the web server
   • Application layer: the web server handles the HTTP request
5. The response returns:
   • Transport layer: server port 80 → client port 54321
   • Network layer: server IP → client IP
   • Application layer: the browser renders the page

Example 2: Several Applications Running at Once

Several network applications run on your computer at the same time. How does the transport layer cope?

Scenario: browsing a site, collecting mail, and sending a chat message all at once.

Multiplexing in the transport layer: the browser (54321), the mail client (54322), and the chat client (54323) all go out through TCP and on to the network layer.

Uniform handling in the network layer: all of the data uses the same IP address (192.168.1.10), and the transport layer separates the applications by port number.

Demultiplexing on receipt: network → network layer → TCP, which dispatches by port: 54321 → the browser, 54322 → the mail client, 54323 → the chat client.

Example 3: The DNS Lookup Process

DNS lookups use the UDP protocol.

Scenario: the browser looks up the IP address of www.baidu.com.

1. Application layer: the browser needs the domain name resolved
2. Transport layer (UDP):
   • Client port: 49152 (an ephemeral port)
   • DNS server port: 53
   • The DNS query request is sent as a UDP datagram
3. Network layer: client IP → DNS server IP
4. The DNS server:
   • Receives the UDP datagram
   • Looks up the IP for the domain
   • Returns the IP address as a UDP datagram
5. The client:
   • Receives the UDP response and obtains the IP address: 202.108.22.5
   • The browser uses that IP address to reach the site

Characteristics: UDP is simple and fast, one request produces one response, no connection has to be established, and the response comes back quickly.

---

Exercises

Exercise 1

What is the difference between the transport layer and the network layer, and how do the two cooperate?

Exercise 2

What is a port, what does it do, and how are ports classified?

Exercise 3

What are multiplexing and demultiplexing? Give an example of how the transport layer implements both.

Exercise 4

How do TCP and UDP differ, and what scenarios suit each of them?

---