Skip to topic
    ← Back to course topics

    Networks — Edexcel GCSE Computer Science

    Verified courseTeaching note checked against the official specification.

    Networks explained

    Networks covers 8 specification points, including Understand why computers are connected in a… and Understand different types of networks (LAN,….

    Read the full explanation

    Open a point below for its explanation and revision guidance.

    4.1.1 understand why computers are connected in a network

    A network links two or more computing devices so they can exchange data and share resources. Computers are connected because sharing is cheaper and more flexible than giving every user a separate copy of everything. A school office can send a document to a networked printer instead of buying one printer per desk, and staff can open the same shared folder rather than swapping USB sticks. Connections also let users communicate through email, messaging and video calls, and let a central server hold files, accounts and backups that many machines reach at once. Central management means one administrator can update software, set permissions and monitor use across all devices, which is faster and more consistent than visiting each machine. Networks also allow users to log on at any connected computer and still reach their own files.

    4.1.2 understand different types of networks (LAN, WAN)

    Networks are classified by the area they cover and who controls them. A local area network, or LAN, covers a small area such as one building or campus, for example a school where computers, printers and a file server are linked by the school's own cabling and wireless access points. A wide area network, or WAN, covers a large geographical area and typically links separate LANs using infrastructure that the organisation does not own, such as leased telecoms lines. A bank with branches in several cities runs a WAN so each branch LAN can reach the central accounts system. The key distinctions are scale, ownership of the communication medium and the hardware needed: a LAN usually uses owned cabling, switches and wireless access points, while a WAN depends on external links and routers.

    4.1.3 understand how the internet is structured (IP addressing, routers)

    The internet is a network of networks: many independently owned networks are joined so that any device can exchange data with any other. Each device needs an address so data reaches the right destination. An IP address identifies a device or interface on a network; a public address is globally unique, while a private address is reused inside a local network and translated at the boundary. Data is split into packets, each carrying a destination IP address. Routers are the devices that read that destination address and forward each packet along the best available path, hop by hop, until it arrives. Because routers choose routes dynamically, traffic can take different paths at different times, and a packet may pass through several routers. A router also connects separate networks, for example a home network to an internet service provider.

    4.1.4 understand how the characteristics of wired and wireless connectivity impact on performance (speed, range, latency, bandwidth)

    Wired and wireless connections differ in how they carry data, and this affects performance. Wired links, such as Ethernet, use a physical cable, which usually gives higher speed, greater bandwidth and lower latency, but the device is limited by the cable length and must be plugged in. Wireless links, such as Wi-Fi, carry data through the air, so devices can move within range, but speed and bandwidth generally fall as distance increases or as walls and interference weaken the signal. Latency is the delay before data starts to arrive; wired links often have lower latency, while wireless links can suffer more delay and variation. Bandwidth is the amount of data that can be transferred per unit time, so a higher-bandwidth link can carry more data at once. Range is how far a signal can travel while remaining usable.

    4.1.5 understand that network speeds are measured in bits per second (kilobit, megabit, gigabit) and be able to construct expressions involving file size, transmission rate and time

    Network speed is a rate: how many bits pass a point each second, written in bits per second (bit/s). The prefixes scale by 1000: 1 kilobit per second (kbit/s) = 1000 bit/s, 1 megabit per second (Mbit/s) = 1000 kbit/s = 1,000,000 bit/s, and 1 gigabit per second (Gbit/s) = 1000 Mbit/s = 1,000,000,000 bit/s. File size is a quantity of bits, so time = file size ÷ transmission rate. Convert units before dividing: 2 MB = 2 × 8 × 1,000,000 = 16,000,000 bits; at 8 Mbit/s, time = 16,000,000 ÷ 8,000,000 = 2 s. Rearranged expressions give file size = rate × time and rate = file size ÷ time. Keep bits and bytes distinct: 1 byte = 8 bits.

    4.1.6 understand the role of and need for network protocols (Ethernet, Wi-Fi, TCP/IP, HTTP, HTTPS, FTP ) and email protocols (POP3, SMTP, IMAP)

    A protocol is an agreed set of rules that lets devices communicate. Without shared protocols, different hardware and software could not interpret each other's signals, so protocols are needed for reliable, standardised exchange. Ethernet defines wired local-network communication; Wi-Fi defines wireless local-network communication; TCP/IP governs how data is packetised, addressed, routed and reassembled across networks, with TCP checking delivery and IP handling addressing. HTTP transfers web pages, HTTPS does the same with encryption for security, and FTP transfers files. For email, SMTP sends messages from client to server and between servers, POP3 downloads messages to one device, and IMAP keeps messages on the server so they can be synchronised across devices.

    4.1.7 understand how the 4-layer (application, transport, internet, link) TCP/IP model handles data transmission over a network

    The TCP/IP model splits network communication into four layers, each with a distinct job. The application layer creates data for a service such as sending an email or requesting a web page. The transport layer breaks that data into segments, adds port numbers and, with TCP, sequence numbers and checksums so lost or corrupted segments can be resent. The internet layer adds source and destination IP addresses so routers can forward packets across networks. The link layer frames the data with MAC addresses for delivery on the local network segment. At the receiver the process reverses: link, internet, transport, then application. Each layer adds or removes its own header, which is encapsulation and de-encapsulation. A useful method is to trace one message down the sender's stack and up the receiver's stack, naming the header added at each layer.

    4.1.8 understand characteristics of network topologies (bus, star, mesh)

    A network topology is the arrangement of nodes and connections. In a bus topology all nodes share one backbone cable; data travels along the backbone and terminators absorb signals at the ends. It needs little cable but a break in the backbone can stop the whole network and performance falls as traffic increases. In a star topology every node connects to a central switch or hub; a failed node or cable affects only that node, but the central device is a single point of failure. Star is common in schools and offices because it is easy to add nodes and troubleshoot. In a mesh topology nodes connect to multiple other nodes; a full mesh gives every node a direct link to every other node, so it is highly resilient but needs many cables and ports. Partial mesh connects some nodes by more than one path. A useful method is to compare cost, fault tolerance and ease of adding nodes.

    Your focus

    1. State at least two reasons why computers are connected in a network
    2. Identify a shared resource or communication service that a network provides
    3. Distinguish a benefit of networking from a claim about a single computer's performance
    Show all 24 objectives
    1. Define a LAN and a WAN in terms of the area covered
    2. Explain how ownership of the communication medium differs between a LAN and a WAN
    3. Classify a described network scenario correctly as a LAN or a WAN
    4. State that the internet is a network of networks joined by routers.
    5. Describe the role of an IP address in delivering packets to the correct destination.
    6. Explain how a router forwards packets between networks using destination IP addresses.
    7. Compare wired and wireless connections in terms of speed, range, latency and bandwidth.
    8. Explain how distance and interference affect wireless performance.
    9. Select a suitable connection type for a given scenario and justify the choice using these characteristics.
    10. State that network speeds are measured in bits per second and use the kilobit, megabit and gigabit prefixes.
    11. Convert between bit/s, kbit/s, Mbit/s and Gbit/s and between bits and bytes.
    12. Construct and solve expressions linking file size, transmission rate and time, giving the correct unit.
    13. Define a protocol and explain why protocols are needed for network communication.
    14. Describe the roles of Ethernet, Wi-Fi, TCP/IP, HTTP, HTTPS and FTP.
    15. Describe the roles of POP3, SMTP and IMAP in sending and accessing email.
    16. Name the four TCP/IP layers in order and state the role of each.
    17. Describe how a header is added at each layer as data moves down the sender's stack and removed as it moves up the receiver's stack.
    18. Explain how port numbers, IP addresses and MAC addresses are used at different layers during transmission.
    19. Describe the layout and connection method of bus, star and mesh topologies.
    20. Compare bus, star and mesh topologies in terms of cost, fault tolerance and ease of adding nodes.
    21. Explain the effect of a single cable or node failure in each topology.

    Networks exam tips

    Marking Points
    • Sharing hardware such as printers and scanners between many users instead of buying one device per computer
    • Sharing data and files through a central store so users work on the same up-to-date version
    • Communication between users by email, messaging or video calls over the connection
    • Central management of accounts, software updates, permissions and backups from one point
    • Users can access their own files and settings from any connected device after logging on
    • Recognition that networking brings costs and risks such as extra hardware, configuration and wider impact of failure or attack
    • A LAN covers a small area such as a single building or site, while a WAN covers a large geographical area such as a country or the world
    • A LAN is usually owned and managed by the organisation, whereas a WAN typically uses external communication links that the organisation does not own
    • A WAN commonly connects two or more separate LANs together, for example linking branch offices to a head office
    • LAN hardware includes owned cabling, switches and wireless access points, while WAN links rely on routers and telecommunications infrastructure
    • Both LAN and WAN allow connected devices to share data and resources, so the difference is one of scale and ownership rather than purpose
    • Correctly classifying a described scenario, such as a single school site as a LAN and a bank's nationwide branch links as a WAN
    • An IP address uniquely identifies a device or interface so packets can be delivered to the correct destination.
    • A router forwards packets between networks by reading the destination IP address and choosing a route.
    • The internet is a network of networks, so data may cross several routers before reaching its destination.
    • Packets may travel by different routes, so routers make forwarding decisions rather than using one fixed path.
    • Private IP addresses are used inside local networks and are not directly reachable from the public internet.
    • Wired connections use a physical cable and typically offer higher speed, greater bandwidth and lower latency than wireless.
    • Wireless connections allow mobility within range but speed and bandwidth usually decrease as distance increases or interference grows.
    • Latency is the delay before data transfer begins, and it affects how responsive a connection feels.
    • Bandwidth is the amount of data that can be transferred per unit time, so higher bandwidth supports more simultaneous data.
    • Range is the distance over which a connection remains usable, and it limits where wireless devices can operate.
    • States that network speed is measured in bits per second (bit/s), with kilobit, megabit and gigabit prefixes scaling by 1000.
    • Converts between bit/s, kbit/s, Mbit/s and Gbit/s correctly, e.g. 1 Mbit/s = 1,000,000 bit/s.
    • Distinguishes bits from bytes and applies 1 byte = 8 bits when a file size is given in bytes.
    • Selects and rearranges the relationship time = file size ÷ transmission rate to find time, file size or rate.
    • Carries out a multi-step calculation with consistent units and states the unit of the answer, e.g. seconds.
    • Defines a protocol as a set of rules for communication between devices.
    • Explains the need for protocols: standardisation and reliable interpretation of data between different systems.
    • Matches Ethernet to wired and Wi-Fi to wireless local-network communication.
    • Describes TCP/IP as the suite controlling packet addressing, routing, delivery checking and reassembly across networks.
    • Distinguishes HTTP (web page transfer), HTTPS (encrypted web transfer) and FTP (file transfer).
    • Distinguishes SMTP (sending email), POP3 (downloading email to one device) and IMAP (server-stored, synchronised email access).
    • Application layer: provides services and protocols that create or consume the user's data, for example HTTP for web pages or SMTP for email.
    • Transport layer: splits data into segments, adds port numbers, and with TCP adds sequence numbers and checksums to support reliable delivery and reassembly.
    • Internet layer: adds source and destination IP addresses and routes packets between networks using routers.
    • Link layer: adds MAC addresses and frames data for transmission on the local network segment.
    • Encapsulation: each layer adds its own header as data moves down the stack; de-encapsulation removes headers as data moves up the receiver's stack.
    • Order of processing: sender uses application, transport, internet, link; receiver uses link, internet, transport, application.
    • Bus: all nodes share a single backbone cable, with terminators at each end; a break in the backbone can disrupt the whole network.
    • Star: each node connects to a central switch or hub; a single node or cable failure affects only that node, but the central device is a single point of failure.
    • Mesh: nodes connect to multiple other nodes; a full mesh links every node directly to every other node, giving high resilience but requiring many connections.
    • Partial mesh: some nodes have more than one path to other nodes, balancing resilience against cost.
    • Comparison factors: cost of cabling and hardware, fault tolerance, ease of adding or removing nodes, and performance under load.
    Examiner Tips
    • 💡Read the question carefully to see whether it asks for benefits of connecting computers or drawbacks, and answer only that side.
    • 💡Give a specific shared resource or activity, such as a networked printer or a shared folder, rather than the vague phrase 'to share things'.
    • 💡Where an option mentions speed of a single processor, treat it as a distractor because networking is about sharing and communication.
    • 💡Look for the size of the area and who owns the connections; these two clues usually decide whether the scenario is a LAN or a WAN.
    • 💡When a question describes several sites linked together, check whether each site is a LAN joined by a WAN rather than labelling the whole system a LAN.
    • 💡Avoid answers that describe wireless or wired transmission as the definition of LAN or WAN, because both types can use either method.
    • 💡Read the question stem for the key term, such as router or IP address, before looking at the options.
    • 💡Eliminate options that describe a different device, such as a switch or hub, rather than a router.
    • 💡Check whether the question asks about addressing, forwarding or structure, and choose the option that matches that focus.
    • 💡Match each option to the correct characteristic, such as speed, range, latency or bandwidth, before choosing.
    • 💡Use the scenario in the question, such as a device that must move around, to decide whether wired or wireless is more suitable.
    • 💡Eliminate options that confuse delay with capacity, since latency and bandwidth are different measures.
    • 💡Write the formula triangle or equation first: time = file size ÷ rate, file size = rate × time, rate = file size ÷ time.
    • 💡Convert every quantity to bits and bit/s before substituting, and show the conversion line so method marks are visible.
    • 💡Check the magnitude of the answer: a small file at a fast rate should give a small time, and include the unit (s, bit/s or bits).
    • 💡Learn each protocol as a short role statement, for example 'SMTP sends email', to answer matching questions quickly.
    • 💡For 'need for protocols' questions, link rules to interoperability and reliability rather than listing protocol names.
    • 💡Read scenario questions carefully: choose the protocol that matches the task, such as FTP for transferring a file or IMAP for reading mail on several devices.
    • 💡Match each layer to its main job and its typical address or identifier: application to data and protocols, transport to ports and segments, internet to IP addresses, link to MAC addresses.
    • 💡When asked about order, state the sender's downward order and the receiver's upward order explicitly.
    • 💡Use the term encapsulation for adding headers on the way down and de-encapsulation for removing them on the way up.
    • 💡Compare topologies using the same factors, such as cost, fault tolerance and ease of adding nodes.
    • 💡Link each topology to a realistic context: bus for a small, low-traffic network; star for a school or office; mesh where resilience matters.
    • 💡State the effect of a single failure in each topology rather than only describing the layout.
    Common Mistakes
    • Thinking a network exists mainly to make a single computer faster: correction, the purpose is sharing and communication between devices, not boosting one machine's processing speed.
    • Assuming all networked computers must be in the same room: correction, connections can span a building or the world, which is why network types such as LAN and WAN are distinguished.
    • Believing files are automatically safe because they are on a network: correction, shared access increases the need for permissions, passwords and backups.
    • Confusing the internet with a network: correction, the internet is one very large network of networks, while any set of connected devices is a network.
    • Treating LAN and WAN as different in purpose rather than in size and ownership: correction, both share data and resources, but a LAN is small and locally owned while a WAN spans a large area using external links.
    • Assuming a WAN must be wireless: correction, WAN links often use cables, satellites or leased lines, and wireless is simply one possible transmission method.
    • Thinking the internet is the only possible WAN: correction, any large-area network linking sites, such as a company's private links between offices, is a WAN.
    • Believing a LAN cannot connect to the internet: correction, a LAN commonly connects to the internet through a router, which is a link to a much larger WAN.
    • Thinking a router stores the whole file: routers forward individual packets, and the destination device reassembles them.
    • Confusing a router with a switch: a switch forwards frames within one local network, while a router forwards packets between networks.
    • Believing an IP address identifies a person: it identifies a device or interface, and addresses can be shared or reassigned.
    • Assuming all packets take the same path: routers can forward packets along different routes.
    • Treating bandwidth and speed as identical: bandwidth is the capacity per unit time, while speed is how quickly data travels.
    • Assuming wireless is always slower: wireless can be fast at close range, but it is more affected by distance and interference.
    • Confusing latency with bandwidth: latency is delay, while bandwidth is the amount of data carried per unit time.
    • Ignoring range: a wireless connection outside its usable range will drop or slow down, regardless of its rated speed.
    • Treating bits and bytes as interchangeable: a file size in bytes must be multiplied by 8 to give bits before dividing by a rate in bit/s.
    • Using 1024 instead of 1000 for kilobit, megabit and gigabit: these network-speed prefixes scale by powers of 1000.
    • Dividing rate by file size instead of file size by rate: time = file size ÷ transmission rate, so the larger the rate the smaller the time.
    • Forgetting to convert a rate such as 8 Mbit/s into 8,000,000 bit/s before dividing, which gives an answer 1,000,000 times too large.
    • Confusing POP3 and IMAP: POP3 typically downloads and may remove messages from the server, while IMAP leaves them on the server for access from multiple devices.
    • Thinking SMTP receives email: SMTP is for sending; receiving and accessing use POP3 or IMAP.
    • Treating HTTP and HTTPS as unrelated: HTTPS is HTTP with encryption, so it protects data in transit.
    • Believing Ethernet is wireless: Ethernet is the wired networking protocol, while Wi-Fi is the wireless one.
    • Assuming TCP/IP is only one protocol: it is a suite in which TCP and IP have separate roles.
    • Confusing the transport layer with the internet layer: the transport layer handles ports, segmentation and reliability, while the internet layer handles IP addressing and routing.
    • Thinking the link layer uses IP addresses: the link layer uses MAC addresses for the local segment; IP addresses belong to the internet layer.
    • Believing each layer sends data independently: the layers work in sequence, and each layer adds a header before passing data to the next layer.
    • Assuming TCP/IP and OSI have the same number of layers: TCP/IP has four layers, while OSI has seven.
    • Saying a star topology has no single point of failure: the central switch or hub is a single point of failure.
    • Confusing a bus backbone with a star's central device: in a bus all nodes share one cable, while in a star each node has its own cable to the centre.
    • Thinking a mesh always means every node is directly connected to every other node: that is a full mesh; a partial mesh has some nodes with multiple links only.
    • Ignoring cost: mesh gives high resilience but needs more cable and ports than bus or star.