OCR A-Level Computer Science: Networks & Communication — Complete Revision Guide (H446)
OCR A-Level Computer Science: Networks & Communication — Complete Revision Guide
Networking is the topic that explains how the abstract machine of the rest of the course actually talks to the world. Every web request, email, video call and cloud save is a story about packets, protocols and addresses, and OCR A-Level Computer Science expects you to tell that story precisely — from the physical hardware that moves bits, up through the layered protocol stack that gives those bits meaning, to the security measures that protect them in transit. The H446 specification places this material in sections 1.3.3 (networks) and 1.3.4 (web technologies), and the examiners reward candidates who can move fluently between the big picture (why we layer protocols at all) and the concrete detail (what a router does that a switch does not).
This is Component 01 (Computer systems) content — the written paper that covers the 1.x sections of the specification — and it rewards crisp definitions, accurate comparisons and the ability to trace what happens to a message as it crosses a network. Networking also connects outward across the qualification: the packet-switching and addressing ideas here lean on the queues and graphs from the data-structures course, the security material dovetails with the legislation you meet in the databases-and-ethics course, and the client–server model underpins how every database-backed web application is actually deployed. A candidate who understands networking as a coherent layered system, rather than a bag of acronyms, answers these questions with the structure examiners are looking for.
This is Course 7 of 11 on the LearningBro OCR A-Level Computer Science learning path. The course, OCR A-Level CS: Networks & Communication, builds from the basic classification of networks, through the hardware and topologies that physically connect them, into the protocols and the TCP/IP stack that govern communication, and finishes with web technologies, security and wireless. By the end you should be able to define each network type and topology, explain the role of each piece of hardware, describe the layered protocol model and walk a packet through it, and evaluate the threats to a network and the defences against them.
Guide Overview
This course is a ten-lesson sequence that ascends the networking stack from physical media to web applications and security. Work through them in order, because the protocol and web material assumes the hardware and addressing introduced earlier.
- Network Types
- Network Topologies
- Network Hardware
- Communication Methods
- Protocols and Standards
- TCP/IP in Detail
- Packet Switching
- Web Technologies
- Network Security
- Wireless Networking
Network Types: LAN, WAN and the Client–Server Question
The Network Types lesson establishes the basic geography. A Local Area Network (LAN) connects devices over a small, single-site area — a home, office or school — typically over media the organisation itself owns, giving high speeds and low latency. A Wide Area Network (WAN) connects devices across large geographic distances — between cities or countries — usually over infrastructure leased from third parties, the internet being the largest WAN of all. You should be able to compare them on geographic scale, ownership of the transmission media, typical speed, and cost.
The second axis this lesson establishes is the model of how machines relate. In the client–server model, powerful central servers provide resources and services (files, web pages, authentication) to client machines that request them; this centralises management, security and backup but creates a single point of failure and a potential bottleneck. In the peer-to-peer model, every machine is an equal that both provides and consumes resources, which is cheap and resilient with no central server, but harder to secure and back up. Be ready to recommend one model over the other for a given scenario and to justify the choice — a small home network of equals leans peer-to-peer, while a managed organisation leans client–server. These models recur throughout the course, because the web itself is the client–server model operating at global scale.
Network Topologies: Star, Mesh and the Logical–Physical Distinction
The Network Topologies lesson covers the shapes networks take. In a star topology, every device connects to a central node (typically a switch); this is the dominant wired LAN layout because a single cable fault isolates only one device, and performance is easy to manage, though the central node is a single point of failure. In a mesh topology, devices interconnect with multiple paths between them; a full mesh connects every node to every other, giving maximum resilience and no single point of failure at the cost of many connections, while a partial mesh is a pragmatic compromise. Mesh thinking underlies the resilience of the internet itself and of modern wireless mesh systems.
The conceptual point OCR cares about is the distinction between physical and logical topology — how the cables are actually arranged versus how the data logically flows. A network can be physically wired as a star (every device to a central switch) yet behave logically as a bus or operate as a logical mesh of routes. Being able to separate the physical wiring from the logical data path, and to evaluate a topology on resilience, cost and ease of fault-finding, is exactly the kind of comparison that earns marks. Tabulating the trade-offs is a sound revision habit.
| Topology | Resilience | Cost / cabling | Single point of failure? |
|---|---|---|---|
| Star | Good (one cable fault isolates one device) | Moderate; one cable per device to the hub | Yes — the central node |
| Full mesh | Excellent (many redundant paths) | High; connections grow rapidly with nodes | No |
| Partial mesh | Good (some redundant paths) | Medium | Reduced |
Network Hardware: Who Does What
The Network Hardware lesson demands precise role definitions, because a frequent exam error is conflating devices that operate at different layers. A Network Interface Card (NIC) gives a device its physical connection and carries its MAC address, a unique hardware identifier burned in at manufacture. A switch connects devices within a LAN and is intelligent: it learns which MAC address sits on which port and forwards each frame only to its destination port, reducing unnecessary traffic — unlike the older hub, which blindly repeated every signal to every port. A router operates one level up: it connects different networks together (for example a home LAN to the internet), forwarding packets between them on the basis of IP addresses and the routing decisions it makes.
You should also know the Wireless Access Point (WAP), which lets wireless devices join a wired network, and the role of a gateway as the device that bridges networks using different protocols. The discriminator examiners probe is the switch-versus-router boundary: a switch forwards frames within a network using MAC addresses; a router forwards packets between networks using IP addresses. Holding that distinction firmly — frames/MAC/within versus packets/IP/between — is worth several marks across the paper and underpins your understanding of how a message actually travels.
Communication Methods: How Bits Move
The Communication Methods lesson covers the lower-level mechanics of transmission. You should distinguish serial transmission (bits sent one after another down a single line — slower per line but reliable over distance and the basis of modern high-speed links) from parallel transmission (multiple bits sent simultaneously over several lines, fast over short distances but prone to skew, where bits arrive out of step, over longer runs). You should also distinguish the directional modes: simplex (one-way only), half-duplex (both directions but only one at a time, like a walkie-talkie) and full-duplex (both directions simultaneously, like a telephone call).
This lesson also covers the related ideas of bandwidth (the capacity of a link, the rate at which data can be carried) and bit rate, and the practical media that carry signals — copper, fibre-optic and wireless — each with its own speed, cost and susceptibility to interference. The point to internalise is that these are the physical realities the higher protocol layers depend upon: when later lessons talk about throughput and latency, they are ultimately constrained by the transmission choices made here.
Protocols and Standards: Why We Layer
The Protocols and Standards lesson introduces the central organising idea of the whole course: a protocol is an agreed set of rules governing communication between devices, and a standard is an agreed specification that lets equipment from different manufacturers interoperate. Without shared protocols, two machines would have no common language; without standards, no two vendors' devices would connect. You should be able to name and state the purpose of the common application-layer protocols — HTTP and HTTPS for web pages, FTP for file transfer, SMTP for sending email, POP3 and IMAP for retrieving it, and DNS for resolving human-readable domain names into IP addresses.
The deeper exam idea is layering: networking is organised into a stack of layers, each responsible for one well-defined job and each communicating only with the layer directly above and below it. Layering brings two benefits the examiners want you to articulate — abstraction, so that a layer can be designed and reasoned about without knowing the internals of the others, and modularity, so that one layer's implementation (say, swapping copper for fibre at the physical level) can change without disturbing the rest. This principle of separating concerns into independent layers is the conceptual key that the next lesson unlocks with a concrete model.
TCP/IP in Detail: The Four-Layer Stack
The TCP/IP in Detail lesson makes the layering idea concrete with the TCP/IP model, the four-layer stack that the internet actually runs on. Each layer has a defined responsibility, and a message travelling out of a machine is encapsulated as it passes down the stack — each layer adding its own header — and de-encapsulated on the way up at the receiving machine. You should know the layers, their order, and what each contributes.
| Layer | Responsibility | Example protocols / units |
|---|---|---|
| Application | Provides network services to user programs | HTTP, FTP, SMTP, DNS |
| Transport | End-to-end delivery; splits data into segments; ports | TCP (reliable), UDP (fast, connectionless) |
| Internet (Network) | Logical addressing and routing between networks | IP; works with packets and IP addresses |
| Link (Network access) | Physical transmission on the local medium | Ethernet, Wi-Fi; frames and MAC addresses |
The roles of the two headline protocols must be clear. IP (Internet Protocol) handles addressing and routing — getting a packet from source network to destination network — but offers no delivery guarantee. TCP (Transmission Control Protocol) sits above it and provides reliable, ordered, connection-oriented delivery: it splits data into numbered segments, uses acknowledgements and retransmission to recover lost data, and reassembles segments in the right order at the far end. You should contrast TCP with UDP, which is connectionless and unreliable but faster and lighter, suiting real-time applications like streaming and online gaming where speed matters more than perfect delivery. You should also understand ports as the numbers that direct traffic to the correct application on a host, and the difference between an IPv4 address (32-bit, increasingly exhausted) and an IPv6 address (128-bit, vastly larger address space). Encapsulation is the unifying mental model: a web page is HTTP data wrapped in a TCP segment, wrapped in an IP packet, wrapped in an Ethernet frame — and unwrapped layer by layer at the destination.
Packet Switching: How Data Crosses the Internet
The Packet Switching lesson explains the mechanism that makes the internet efficient and resilient. In packet switching, a message is broken into small packets, each carrying a header with the source and destination IP addresses, a sequence number and other control data; the packets are sent independently across the network and may take different routes, with routers at each hop choosing the best onward path based on current conditions. At the destination, the packets are reassembled into the original message using their sequence numbers, and any that are lost can be retransmitted. This contrasts with circuit switching, which reserves a dedicated end-to-end path for the whole conversation (as the traditional telephone network did) — guaranteeing capacity but wasting it when idle and failing entirely if any link on the reserved path breaks.
The advantages of packet switching that examiners reward are efficient use of shared capacity (links carry packets from many conversations interleaved), resilience (if one route fails, packets simply take another), and graceful handling of congestion. The router's routing decision is, at heart, a shortest- or best-path search over a graph of networks — a direct echo of the graph algorithms from Course 6 — and the queues that buffer packets at busy routers are the FIFO structures from Course 5. Be ready to explain why a network might deliver packets out of order (independent routing) and how the receiving transport layer restores order using sequence numbers.
Web Technologies: How the Web Is Built
The Web Technologies lesson covers section 1.3.4 — the technologies that turn the network into the World Wide Web. You should know the three pillars of a web page and the separation-of-concerns they embody: HTML defines the structure and content, CSS defines the presentation and styling, and JavaScript defines the behaviour and interactivity. Crucially, you must distinguish client-side processing (JavaScript running in the user's browser — responsive and offloading work from the server, but visible to and modifiable by the user, so never to be trusted for security) from server-side processing (code running on the server — necessary for anything that must be secure or touch a database, but adding load and a round-trip).
This lesson also covers the role of search engines and an outline of how page-ranking algorithms weigh the importance of pages — for example by treating links from other pages as votes of relevance — and the meaning of a URL, DNS resolution turning a domain name into an IP address, and the request–response cycle of HTTP. The unifying point is that the web is the client–server model from Course 7's opening lesson, operating at global scale over the TCP/IP stack: a browser (client) issues an HTTP request, DNS finds the server, packets cross the internet by packet switching, the server responds with HTML/CSS/JavaScript, and the browser renders it. Being able to narrate that whole journey end to end is a high-value synoptic answer.
Network Security: Threats and Defences
The Network Security lesson catalogues the threats a network faces and the defences that mitigate them, and the examiners want both the threat and a specific countermeasure. Common threats include malware (viruses, worms, trojans, ransomware), phishing (deceiving users into revealing credentials), brute-force password attacks, denial-of-service (DoS / DDoS) attacks that overwhelm a service with traffic, SQL injection that exploits unsanitised input to attack a database, and packet sniffing / interception of unencrypted traffic. You should be able to describe how each works at a level sufficient to explain why it is dangerous.
On the defensive side, you should know the role and mechanism of each measure: a firewall filters incoming and outgoing traffic against a rule set, often using packet filtering to inspect packet headers; encryption scrambles data so that intercepted traffic is unreadable without the key (the basis of HTTPS, which is HTTP carried over an encrypted connection); authentication measures such as strong passwords, two-factor authentication and MAC address filtering restrict who may connect; and proxy servers mediate and can anonymise or cache requests. A strong answer pairs each threat with a proportionate defence — encryption against interception, input validation against SQL injection, firewalls and rate-limiting against DoS — and recognises that the human user is often the weakest link, which is why education against phishing matters as much as any technical control. This lesson connects directly to the Computer Misuse Act 1990 in the next course, which criminalises much of what these threats attempt.
Wireless Networking: Connecting Without Wires
The Wireless Networking lesson covers the technologies that let devices join a network over radio rather than cable. Wi-Fi connects devices to a LAN through a Wireless Access Point, with the standards governing speed, range and frequency band, while Bluetooth provides short-range device-to-device links for peripherals. You should be able to compare wired and wireless connections on the trade-offs that matter — wireless offers mobility and ease of installation but is generally slower, more susceptible to interference and obstruction, and inherently easier to intercept because the signal radiates into the air.
That last point makes wireless security essential, and the examiners expect you to know the measures: modern WPA-family encryption to protect the radio link, an SSID that can be hidden, MAC address filtering to restrict which devices may associate, and the use of strong keys. You should also understand the broad principle of how wireless shares a medium — multiple devices contending for the same airspace and the protocols that coordinate them — and why range and bandwidth fall off with distance and obstacles. Wireless brings the course full circle: it is another way to realise the LANs, topologies and TCP/IP stack from earlier lessons, with its own characteristic strengths, weaknesses and security demands.
How to Revise Networks & Communication
Revise networking by tracing a message end to end and by building precise comparison tables. Take a single concrete journey — typing a web address and pressing enter — and narrate every stage: DNS resolves the name to an IP address, the browser (client) issues an HTTP request, the data is encapsulated down the TCP/IP stack into packets, packet switching routes those packets through routers across the internet, the server processes the request and responds, and the browser de-encapsulates and renders the HTML, CSS and JavaScript. That single narrative exercises almost every lesson at once. Alongside it, build crisp comparison tables for the boundaries examiners probe: LAN versus WAN, client–server versus peer-to-peer, star versus mesh, switch versus router, serial versus parallel, simplex/half-duplex/full-duplex, TCP versus UDP, packet versus circuit switching, client-side versus server-side, and wired versus wireless.
Then drill the security material as threat–defence pairs, learn the four TCP/IP layers and the protocols that live at each, and practise explaining why we layer protocols at all — abstraction and modularity. When you can walk a packet through the stack, define every device by the layer it operates at, and evaluate a network's resilience and security with specific measures, you have the structured command of the topic that H446 rewards. Work through every lesson in OCR A-Level CS: Networks & Communication, then continue to the databases, ethics and law course that follows it on the OCR A-Level Computer Science learning path.