Computer networks: OxfordAQA IGCSE Computer Science Complete Notes

Treat networking as a stack of layered problems

A computer network is, at its core, a solution to one problem: how do you get data reliably from one device to another, possibly on the other side of the world, without the two devices needing to know every detail of how the journey happens. The oxfordaqa igcse computer science computer networks content solves that problem in layers, each one handling a narrower piece of the job, and that layered structure is the most useful way to think about the whole topic rather than treating every fact as a separate item to memorise.

Defining a network, and weighing its benefits and risks

A computer network is two or more devices connected together so they can share data and resources. The benefits are fairly intuitive: shared files, shared printers and other hardware, and communication between users. The risks are the flip side of exactly those same benefits: connecting devices together also creates a route for unauthorised access, malware to spread, or a single point of failure to take down shared resources for everyone at once. A strong exam answer states both sides of that trade-off rather than only listing benefits or only listing risks. It is also worth thinking about scale when you weigh those factors: a two-device home network faces a very different risk profile from a large organisation's network carrying sensitive records, even though the underlying technology is built from the same basic components.

LAN and WAN

Networks can also be wired, using cables such as fibre or copper, or wireless. Wired connections tend to be more reliable and less exposed to interception, while wireless networks offer mobility and easier installation at the cost of some additional exposure to interference and unauthorised access. Being able to weigh those two factors against each other for a given scenario, rather than declaring one option universally better, is exactly what this part of the specification is testing.

Physical topologies

Two topologies are named: star and bus. In a star topology, every device connects individually to a central point, such as a switch; in a bus topology, every device connects to a single shared cable running along the network. You should be able to draw both topology diagrams and explain the practical differences between them, such as how a single cable failure affects a bus topology far more severely than a star topology, where only the one connected device loses its link.

What a protocol actually is

A protocol is a set of rules that governs how data is transmitted and received by devices. Think of it like a shared language: two devices can only communicate successfully if they are both following the same agreed rules for how a message is structured and exchanged. This specification names a specific set of protocols you need to know, each with its own defined job.

Ethernet and Wi-Fi are worth a specific note: both are families of related protocols rather than a single protocol each, so an exam answer that treats either one as a single fixed rule is slightly missing the point. You do not need to know the individual protocols that make up either family, only that they exist as a group under that name, and that Wi-Fi specifically is a trademark, with WLAN being the generic term for that type of network.

Network security

Four methods matter here, and they work best in combination rather than as a single line of defence.

• Authentication: confirming a user is who they claim to be, typically through a username and password.
• Encryption: scrambling data so it cannot be read if intercepted, only reversible with the correct key.
• Firewall: monitors and controls incoming and outgoing network traffic based on defined security rules.
• MAC address filtering: allows or blocks devices from accessing a network based on their physical address, embedded within the device's network adapter.

A good exam answer explains not just what each method does individually, but how they reinforce each other; a firewall might block unauthorised traffic entirely, while encryption protects the data that does get through from being read if it is somehow intercepted, and MAC address filtering adds a further layer that operates independently of both.

The four layer TCP/IP model

This is where the layered thinking from the start of this guide gets made explicit. Four layers, each handling a distinct part of the journey a piece of data takes across a network.

1. Application layer: where network applications, such as web browsers and email programs, actually operate. HTTP, HTTPS, SMTP, IMAP and FTP all sit here.
2. Transport layer: sets up communication between two hosts and agrees settings such as packet size. TCP and UDP operate here.
3. Network layer: addresses and packages data for transmission, and routes packets across the network. IP operates here.
4. Link layer: where the actual network hardware, such as the network interface card, sits, along with the operating system's device drivers for that hardware.

You should be able to name each layer, describe its main function, and correctly place each protocol from the earlier table into the layer it belongs to. Some teaching material calls the network layer the internet layer, and the link layer the network interface layer, but you are not expected to know or use those alternative names in an exam answer; stick with application, transport, network and link.

Worked example: tracing an email through the model

Sending an email touches every layer in turn. At the application layer, your email program uses SMTP to hand the message off. At the transport layer, TCP breaks the message into manageable segments and agrees delivery settings with the receiving server. At the network layer, IP addresses each packet and works out the route it should take across the network. At the link layer, the actual network hardware transmits those packets physically, whether over a wired or wireless connection. Being able to walk through a scenario like this, layer by layer, is a strong way to demonstrate genuine understanding rather than memorised definitions. Try the same exercise with a different scenario, such as loading a web page using HTTPS or downloading a file using FTP, and check that you can correctly assign each stage of the process to application, transport, network or link before checking your answer against the table above.

Common mistakes to avoid

• Placing a protocol in the wrong layer, particularly confusing TCP, a transport layer protocol, with IP, a network layer protocol.
• Describing Wi-Fi or Ethernet as if each were a single specific protocol rather than a family of related protocols.
• Listing only the benefits or only the risks of networks, rather than weighing both sides against each other.
• Confusing encryption, which protects data content, with authentication, which confirms user identity; they solve different problems.

Self-check questions

1. Explain the difference between a LAN and a WAN, giving one real example of each.
2. Draw a star topology and a bus topology, and state one advantage of each over the other.
3. State which layer of the TCP/IP model each of the following operates at: HTTP, TCP, IP, FTP.
4. Explain how a firewall and encryption work together to improve network security.
5. Define the term protocol, using your own words rather than the textbook definition.

Working through this material layer by layer, rather than as one long list of protocols and acronyms, is the most efficient way to hold it all in your head under exam conditions. These oxfordaqa igcse computer science revision notes on computer networks are structured that way deliberately, and revisiting them alongside a fresh set of oxfordaqa igcse computer science practice questions will make the layer-by-layer structure stick far faster than reading definitions in isolation.

Where this fits in your revision

Computer networks connects naturally to cyber security, since several of the security measures and threats covered there depend on understanding how networks and protocols actually function, so it is worth studying the two topics close together. Treat this page as your igcse 9210 computer networks reference, keep it among your core oxfordaqa igcse computer science notes, and return to it whenever a protocol or a layer needs checking. Every rule covered here has been oxfordaqa igcse computer science explained with a concrete, workable example, precisely so the abstract parts of networking, like layers and protocols, become something you can actually picture rather than just recite; that is what a genuinely useful computer networks oxfordaqa igcse guide should deliver.