Wired and wireless networks, protocols and layers: The concept of layers

The idea

Layering splits network communication into separate jobs so each layer handles one concern and offers services to the layer above. A common model has four layers: application (HTTP, FTP, SMTP), transport (TCP, UDP), network (IP) and link (Ethernet, Wi-Fi). When you send a message, data passes down the stack: each layer adds its own header, a process called encapsulation. The receiving device passes data up, and each layer removes and acts on its header. This means a web browser only needs HTTP, while the link layer worries about cables and radio. Layers are self-contained, so a change in one layer, such as swapping copper for fibre, need not affect the others. Standard interfaces between layers let different vendors' hardware and software interoperate, which is why the internet works across mixed equipment.

What earns the marks

• Layering divides network communication into distinct levels, each with a defined role and interface to adjacent layers.
• Each layer provides services to the layer above and uses services from the layer below.
• Data moves down the stack on sending and up the stack on receiving.
• Encapsulation adds layer-specific headers as data descends, and decapsulation removes them as data ascends.
• Named examples: application (HTTP, FTP, SMTP), transport (TCP, UDP), network (IP), link (Ethernet, Wi-Fi).
• Benefits include simpler design, easier troubleshooting, interoperability and independent replacement of one layer.

Common mistakes and how to put them right

• Treating layers as physical devices.

  Put it right by stressing that layers are logical divisions of function, not pieces of hardware.

• Saying data travels only downwards.

  Put it right by describing the down-then-up path between sender and receiver.

• Confusing encapsulation with encryption.

  Put it right by explaining that encapsulation adds addressing and control headers, while encryption scrambles payload for confidentiality.

Exam tips

• Name the layer and give a matching protocol in the same sentence to show precise understanding.
• Use the phrase 'provides services to the layer above' when explaining a layer's role.
• When asked for benefits, link each benefit to a concrete change, such as replacing Wi-Fi with Ethernet without altering the application layer.