A2.1.5 Describe the function of the TCP/IP model. (HL only)
• Application, transport, internet, network interface
• The role of each layer and the interaction between these layers to ensure reliable data transmission over a network
The big idea
The TCP/IP model (also called the Internet Protocol Suite) is the conceptual framework that decomposes all internetworking activity into four ordered layers.
Each layer solves one well-defined subset of the end-to-end communication problem and exposes a clean service interface to the layer above.
Because the layers are independent yet complementary, engineers can innovate or replace any one of them without rewriting the whole stack—one of the key reasons the Internet scales from sensor networks to hyperscale data centres.
┌──────────────────────┐
│ Application layer │ ← software that users & apps see
├──────────────────────┤
│ Transport layer │ ← process-to-process data pipe
├──────────────────────┤
│ Internet layer │ ← global packet delivery across networks
├──────────────────────┤
│ Network-interface │ ← local link access (hardware or driver)
└──────────────────────┘
1 Network-interface (link) layer
- Primary job – move raw frames between directly connected nodes and detect corruption on the local medium.
- Typical protocols & tech – Ethernet (IEEE 802.3), Wi-Fi (802.11), fibre-channel, DSL, cellular.
- Reliability contribution – link-level CRC/CRC32 checksums, optional automatic repeat requests (ARQ) in Wi-Fi, collision/back-off logic.
- Service it offers up – “Here is a frame whose payload is an Internet-layer packet; either it was delivered intact to the next-hop or it was dropped.”
2 Internet layer
- Primary job – deliver variable-length packets across multiple interconnected links and networks.
- Core protocol – IP (currently IPv4 and IPv6) provides global addressing, fragmentation, and routing.
- Supporting protocols – ICMP for error signalling, IGMP/MLD for multicast group management, routing protocols (OSPF, BGP) in routers.
- Reliability contribution – best-effort delivery without guarantees; however, it reports problems via ICMP so higher layers can recover.
- Service it offers up – an unreliable datagram service that sends a packet from source IP to destination IP, independent of physical media.
3 Transport layer
- Primary job – create a logical end-to-end channel between two host processes, adding ports for multiplexing.
- Key protocols
- TCP – connection-oriented, in-order, loss-free byte stream; implements sequence numbers, ACKs, flow control, congestion control.
- UDP – connection-less, minimal-overhead datagrams; applications add reliability if they need it.
- QUIC – user-space, stream-multiplexed transport running over UDP with built-in TLS.
- Reliability contribution – TCP (or QUIC) masks loss and reordering, ensures data integrity with checksums, throttles transmissions to avoid congestion collapse.
- Service it offers up – “Write bytes to this socket and they will arrive at the peer socket in the same order (TCP/QUIC) or as individual best-effort messages (UDP).”
4 Application layer
- Primary job – define the semantics and syntax of the actual user data exchanged.
- Examples – HTTP/HTTPS, SMTP, DNS, SSH, DHCP, FTP, RTP/RTCP.
- Reliability contribution – uses transport guarantees or adds its own (e.g., application-layer retries, checksums inside payloads, idempotent verbs in HTTP).
- Service it offers up – meaningful operations such as “GET /index.html”, “MAIL FROM:”, “QUERY example.com A”, rather than raw bytes.
5 Inter-layer interaction for reliable delivery
| Operation | Network-interface | Internet | Transport | Application |
|---|---|---|---|---|
| Error detection | CRC detects corrupted frame; bad frames discarded. | IP header checksum (IPv4) verifies header integrity. | TCP/UDP checksum protects segment; TCP retransmits if ACK missing. | Many protocols (e.g., HTTPS) add TLS MAC; HTTP clients retry idempotent requests. |
| Addressing & multiplexing | NIC MAC address | IP address | Port numbers (plus CIDs for QUIC) | URLs, e-mail addresses, resource IDs |
| Flow/congestion control | Half-duplex media rules, Wi-Fi TxOP limits | — | TCP sliding window, CUBIC/BBR algorithms | Application-level throttling (e.g., adaptive bitrate streaming) |
| Path selection | Switch learns MAC → port mapping | Routers compute next hop via routing tables | — | CDN selection, DNS load balancing |
The cumulative effect is reliability:
- Local link ensures clean hand-off to the first router.
- Internet layer forwards the packet hop-by-hop along a viable route.
- Transport layer repairs losses, orders segments, paces traffic.
- Application layer interprets the bytes safely, retries when sensible, and surfaces only correct, complete data to the user.
6 Why the model matters
- Modularity – a new optical link layer or a new congestion-control algorithm can deploy independently.
- Interoperability – any vendor can implement one layer as long as it respects the interface contract with its neighbours.
- Scalability – global routing complexity stays below local-link details, and application innovations (e.g., HTTP/3 over QUIC) need no changes to routers.
Take-away
The TCP/IP model turns the formidable problem of “deliver my data reliably from any device on Earth to any other” into four manageable sub-problems, one per layer.
By orchestrating link-level integrity checks, network-wide routing, end-to-end retransmission, and application semantics, the layers cooperate to present users with what feels like a single, dependable network—no matter how many heterogeneous technologies lie underneath.