Transport Layer: TCP vs UDP, Segmentation, Flow Control & Error Handling

Core Concepts: What is the Transport Layer?

The Transport Layer (Layer 4) sits between the Network Layer (IP) and Application Layer. Its job:

• Segmentation: Breaks application data into smaller chunks (segments) for transmission.
• Reliability: Ensures data arrives correctly (TCP) or prioritizes speed (UDP).
• Flow Control: Manages sender/receiver speeds to avoid overload.
• Error Handling: Detects and recovers lost/corrupted data.

Why does this matter? Without the Transport Layer, apps like WhatsApp (end-to-end encryption) or eSewa (secure transactions) couldn’t guarantee messages arrive intact or payments process without errors.

1. TCP (Transmission Control Protocol): The Reliable Messenger

How TCP Works

TCP is like a phone call:

1. Handshake: Three-way process to establish a connection (SYN, SYN-ACK, ACK).
2. Segmentation: Splits data into segments (each with sequence numbers).
3. Acknowledgment (ACK): Receiver confirms receipt; sender retransmits if missing.
4. Flow Control: Uses sliding window to adjust data rate (prevents buffer overflow).
5. Congestion Control: Avoids network overload (e.g., slows down if packets are lost).

flowchart TD
    A["Application Data"] --> B["Segmentation\n(Sequence #, Ports)"]
    B --> C["SYN\n(Connection Request)"]
    C --> D["SYN-ACK\n(Accept)"]
    D --> E["ACK\n(Connection Established)"]
    E --> F["Data Transfer\n(ACKs/Retransmissions)"]
    F --> G["FIN\n(Close Request)"]
    G --> H["FIN-ACK\n(Accept)"]
    H --> I["ACK\n(Connection Closed)"]

TCP Segment Structure

Worked Example: File Transfer Delay (TCP vs UDP)

Scenario: Downloading a 100 MB file from Daraz to your laptop.

• TCP:
  • Breaks file into 1,000 segments (100 KB each).
  • If Segment #45 is lost, TCP waits for retransmission (adds delay).
  • Total time: ~2 minutes (with retries).
• UDP:
  • Sends all segments at once (no retries).
  • If Segment #45 is lost, the file is corrupted (but faster).
  • Total time: ~1.5 minutes (but file may be incomplete).

Why TCP wins here: Reliability matters more than speed for downloads.

2. UDP (User Datagram Protocol): The Speed Demon

How UDP Works

UDP is like sending postcards:

• No handshake, no connection.
• Fire-and-forget: Sends data without confirmation.
• No retransmission: If a packet is lost, it’s gone (but fast).

flowchart LR
    A["Application Data"] --> B["Segmentation\n(No Sequence #)"]
    B --> C["Send\n(No ACK)"]
    C --> D["Receiver\n(May Drop Packets)"]

UDP Datagram Structure

A labelled UDP header showing Source Port, Destination Port, and Checksum. (Image: Jigs35 at English Wikibooks, CC BY-SA 2.5, via Wikimedia Commons)

When to Use UDP

Real-World Example: WhatsApp Calls

• Uses UDP for voice packets (prioritizes speed over perfection).
• If a packet is lost, the receiver’s app interpolates (guesses) the missing audio.
• Result: Slight crackle but no 5-second delay.

3. Key Differences: TCP vs UDP

4. Advanced Topics: Flow Control and Congestion Control

Flow Control: Sliding Window

• Problem: Fast sender overwhelms slow receiver.
• Solution: Receiver advertises window size (buffer capacity).
  • Example: If window = 1,000 bytes, sender stops after sending 1,000 bytes until ACK.
  • Dynamic adjustment: Window grows/shrinks based on network conditions.

flowchart TD
    A["Sender\n(Sends 1,000 bytes)"] --> B["Receiver\n(ACKs 500 bytes)"]
    B --> C["Sender\n(Sends next 500 bytes)"]
    C --> D["Receiver\n(ACKs all 1,000 bytes)"]
    D --> E["Window Increases\n(If no loss)"]

Congestion Control: Avoiding Network Gridlock

TCP uses 4 algorithms to prevent congestion:

1. Slow Start: Exponentially increases window size (e.g., 1, 2, 4, 8 segments).
2. Congestion Avoidance: Linearly increases window (e.g., +1 segment per RTT).
3. Fast Retransmit: If 3 duplicate ACKs arrive, retransmit lost segment.
4. Fast Recovery: Reduces window size after loss (avoids timeout).

Real-World Example: NTC Internet Slowdowns

• During peak hours (evening), NTC’s network gets congested.
• TCP’s congestion control automatically throttles speeds to avoid crashes.
• Result: Slower downloads but stable connections.

5. Case Study: How eSewa Uses Both TCP and UDP

Scenario: Making a payment via eSewa.

1. Initial Request (UDP):
   • Your phone sends a DNS query (UDP) to resolve esewa.com.
   • Why UDP? Fast lookup (retry if failed).
2. Secure Transaction (TCP):
   • Once connected, eSewa switches to TCP for:
     • Encrypted payment data (HTTPS).
     • Confirmation emails (SMTP).
   • Why TCP? No lost transactions allowed!

Diagram of eSewa’s Protocol Stack:

classDiagram
    class Application {
        +eSewa App\n(UDP for DNS, TCP for HTTPS)
    }
    class Transport {
        +TCP\n(Reliable)
        +UDP\n(Fast)
    }
    class Internet {
        +IP\n(Routing)
    }
    class NetworkAccess {
        +Wi-Fi/Mobile\n(Physical Layer)
    }
    Application --> Transport : Uses
    Transport --> Internet : Uses
    Internet --> NetworkAccess : Uses

6. Common Exam Questions and How to Answer

Question Type 1: Explain TCP’s 3-Way Handshake

Model Answer: The TCP 3-way handshake establishes a connection between client and server:

1. SYN: Client sends a segment with SYN flag and a random sequence number (e.g., seq=1000).
2. SYN-ACK: Server responds with SYN (its own sequence number, e.g., seq=2000) and ACK (client’s seq+1, e.g., ack=1001).
3. ACK: Client sends ACK (server’s seq+1, e.g., ack=2001). Connection is now open for bidirectional data transfer.

Visual:

sequenceDiagram
    Client->>Server: SYN (seq=1000)
    Server->>Client: SYN-ACK (seq=2000, ack=1001)
    Client->>Server: ACK (seq=1001, ack=2001)

Question Type 2: Why Does UDP Have No Port in Some Cases?

Model Answer: UDP’s Source Port is optional because:

• No connection state: Unlike TCP, UDP doesn’t track conversations.
• Broadcast/Multicast: Packets (e.g., DNS responses) may not need a reply.
• Efficiency: Saves 2 bytes in the header (but still requires Destination Port).

Example: A DNS query (UDP) from your laptop to Google’s DNS server (8.8.8.8) may omit the source port if the OS doesn’t need to track the response.

Question Type 3: Calculate TCP Checksum

Worked Example: Given a TCP segment with:

• Pseudo-header: Source IP=192.168.1.1, Dest IP=10.0.0.1, Protocol=6 (TCP), Length=40.
• TCP Header: Source Port=50000, Dest Port=80, Sequence=1000, ACK=2000, Data Offset=5, Flags=ACK, Window=65535, Checksum=0 (to be calculated).

Steps:

1. Pad header + data to 16-bit boundary (add padding if needed).
2. Split into 16-bit words and sum all (including pseudo-header).
3. Wrap around if sum > 65,535 (e.g., 0xFFFF + 1 = 0).
4. Complement the sum (1’s complement) to get the checksum.

Final Checksum: 0xABCD (example; actual calculation requires binary addition).

In the Real World

1. WhatsApp (Meta):

   • Uses UDP for voice/video calls (low latency).
   • Switches to TCP for message delivery (reliability).
   • Why? Calls need speed; messages need to arrive intact.

2. eSewa (F1Soft):

   • UDP for initial API requests (fast transaction initiation).
   • TCP for secure data transfer (no lost payment records).
   • Real Example: During Dashain, eSewa handles 10,000+ transactions/minute. UDP speeds up the first request; TCP ensures no money is lost.

3. YouTube (Google):

   • Uses UDP for adaptive bitrate streaming (ABR).
   • How? If your network is slow, YouTube drops lower-priority UDP packets to maintain playback speed.
   • Nepali Tie-In: YouTube Premium in Nepal uses UDP to reduce buffering during poor NTC speeds.

4. Ncell’s Mobile Data:

   • TCP for browsing (reliable pages).
   • UDP for live sports streams (tolerates some packet loss).
   • Problem: Ncell’s congestion control sometimes misinterprets high UDP traffic as congestion, slowing down TCP (e.g., Facebook).

5. NEPSE (Stock Exchange):

   • Uses UDP multicast to broadcast stock prices to all traders simultaneously.
   • Why? Speed > reliability (a delayed price is worse than a lost one).

Exam Tip

1. Memorize the TCP/UDP headers (fields and sizes). Examiners often ask to "draw and label" them.
2. Handshake Questions: Always draw the 3-way handshake sequence diagram.
3. Flow Control: Know the sliding window concept—explain how it prevents buffer overflow.
4. Congestion Control: Mention Slow Start and Fast Retransmit in answers about TCP efficiency.
5. Real-World Links: Relate TCP to file transfers and UDP to gaming/live streams. Use examples like eSewa (UDP for speed, TCP for security).
6. Checksum Calculation: Practice with pseudo-header + header + data. Show all steps (padding, summing, complementing).
7. Common Pitfalls:
   • Don’t confuse port numbers (Layer 4) with IP addresses (Layer 3).
   • UDP has no sequence numbers (only TCP does).
   • ACK in TCP confirms receipt of data; SYN starts a connection.

Quick Revision Checklist

• Can you draw the TCP 3-way handshake?
• Do you know the 5 TCP flags (SYN, ACK, FIN, RST, PSH)?
• Can you list 3 UDP applications and why they use UDP?
• Understand flow control (sliding window) and congestion control (Slow Start)?
• Know how to calculate a TCP checksum (even if not asked, practice once).
• Can you explain eSewa’s use of both protocols in one sentence?