How is network communication organised into layers, and what does each layer of the TCP/IP model do?
Describe the layered TCP/IP model, the role of each layer, and how encapsulation passes data between layers
A focused answer to the H2 Computing outcome on the TCP/IP model. The application, transport, internet and link layers, the role of each, encapsulation of data into segments and packets and frames, and why layering matters.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
SEAB wants you to describe the layered TCP/IP model, the role of each layer, and how encapsulation passes data between layers. The central idea is that network communication is split into independent layers, each solving one part of the problem and hiding its detail from the others, which is what lets the internet interoperate across countless technologies.
The answer
Why layering
A network must do many things at once: let programs talk, deliver data reliably, route it across networks, and physically transmit bits. Doing all this in one monolithic system would be unmanageable. The TCP/IP model divides the work into layers, each with a defined job and a defined interface to its neighbours, so each can be designed, changed and reasoned about independently.
The four layers
From the application down to the wire:
- Application layer - protocols that programs use directly (HTTP for the web, SMTP for email, DNS for name lookups). It deals with the meaning of the data.
- Transport layer - end-to-end communication between programs, identifying them by port numbers. TCP provides reliable, ordered delivery (acknowledgements, retransmission); UDP is faster but unreliable. It splits data into segments.
- Internet (network) layer - addressing and routing. It wraps segments in packets carrying source and destination IP addresses and moves them across networks toward the destination.
- Link (network access) layer - the physical and data-link transmission on the local network (Ethernet, Wi-Fi), framing packets and putting bits on the medium.
Encapsulation
As data travels down the layers at the sender, each layer wraps the data from above with its own header of control information:
Application data
-> Transport adds header = Segment (ports)
-> Internet adds header = Packet (IP addresses)
-> Link adds header/trailer = Frame (physical addressing)
The receiver reverses this, de-encapsulating by stripping each header in turn as data moves up the layers. Each layer only reads its own header.
Examples in context
Example 1. Streaming over different connections. A video app streams the same content whether you are on home Wi-Fi, mobile data or office Ethernet. Because the link layer is abstracted below, the application and transport layers are unchanged; only the bottom layer differs, which is the whole benefit of layering.
Example 2. TCP versus UDP choices. A file download uses TCP for guaranteed, ordered delivery, while a live video call uses UDP to minimise delay, tolerating the odd lost packet. Both sit at the transport layer over the same internet and link layers below, illustrating how one layer offers alternatives without disturbing the others.
Try this
Q1. Name the four layers of the TCP/IP model from top to bottom. [2 marks]
- Cue. Application, transport, internet (network), link (network access).
Q2. State the main responsibility of the internet layer. [1 mark]
- Cue. Addressing and routing - placing data in packets with source and destination IP addresses and forwarding them across networks.
Q3. What is encapsulation in the context of the protocol stack? [2 marks]
- Cue. Each layer wraps the data from the layer above with its own header of control information (segment, packet, frame), reversed by de-encapsulation at the receiver.
Exam-style practice questions
Practice questions written in the style of SEAB exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
Original6 marks(a) Name the four layers of the TCP/IP model in order from the application down to the physical network. (b) State the main responsibility of the transport layer and of the internet layer. (c) Explain what encapsulation means as data passes down the layers.Show worked answer →
(a) From top to bottom: application layer, transport layer, internet (network) layer, link (network access) layer.
(b) The transport layer provides end-to-end communication between programs: it splits data into segments, and (with TCP) ensures reliable, ordered delivery using ports to identify the application. The internet layer handles addressing and routing: it places segments into packets with source and destination IP addresses and gets them across networks toward the destination.
(c) Encapsulation means each layer wraps the data from the layer above with its own header (and sometimes trailer) of control information. The application data becomes a transport segment, then an internet packet, then a link-layer frame, each adding the addressing or control its layer needs. The receiver reverses this, stripping headers layer by layer.
Markers reward the four layers in order, the transport (end-to-end, ports, reliability) and internet (IP addressing and routing) roles, and encapsulation as each layer adding its own header.
Original5 marksExplain two advantages of organising network communication into layers, and state why a web browser does not need to know the details of the link layer.Show worked answer →
Two advantages of layering:
Modularity and interoperability. Each layer has a defined interface to the layers above and below, so a layer's internals can change (a new physical medium, a new routing method) without affecting the others, and equipment from different vendors interoperates as long as it follows the standards.
Simplicity through abstraction. Each layer solves one part of the problem (delivery, routing, addressing, physical transmission) and hides its detail from the others, so designers and programs reason about one concern at a time.
A web browser works at the application layer and relies on the transport layer to deliver data reliably; it does not need to know whether the link layer is Wi-Fi, Ethernet or fibre, because that detail is abstracted away below. The same browser works over any link technology.
Markers reward two genuine layering benefits (modularity/interoperability and abstraction/simplicity), and the point that abstraction lets the browser ignore the link layer and work over any medium.
Related dot points
- Explain packet switching, the structure of a packet, how routers forward packets, and contrast it with circuit switching
A focused answer to the H2 Computing outcome on packet switching. How data is split into packets, packet structure with headers, how routers forward packets hop by hop, and the contrast with circuit switching.
- Explain how DNS resolves domain names to IP addresses, and describe the HTTP/HTTPS request-response model and the client-server architecture
A focused answer to the H2 Computing outcome on DNS and the web. Resolving domain names to IP addresses through DNS, the HTTP and HTTPS request-response cycle, status codes, and the client-server model.
- Explain symmetric and public-key (asymmetric) encryption, digital signatures and common network threats and defences
A focused answer to the H2 Computing outcome on network security. Symmetric and public-key encryption, the key-distribution problem, digital signatures for authenticity, hashing, and common threats and defences.
- Explain IPv4 addressing, the role of the subnet mask in separating network and host parts, and the motivation for IPv6
A focused answer to the H2 Computing outcome on IP addressing. The structure of an IPv4 address, how a subnet mask divides network and host bits, calculating hosts per subnet, and why IPv6 was introduced.
- Apply decomposition, modularity and abstraction to structure software, explaining the benefits for maintenance and reuse
A focused answer to the H2 Computing outcome on decomposition and abstraction. Breaking problems into modules, the role of interfaces, information hiding through abstraction, and the benefits for maintainability and reuse.