3.5 Network protocols

This resource supports AQA GCSE Computer Science 3.5 Network protocols. It expands the core idea that protocols are agreed rules for communication and keeps the focus on what teachers actually need in lessons and in marking: what each protocol does, where students confuse them, and how those distinctions appear in exam answers. It is designed to help teachers move quickly from explanation to assessment without turning the lesson into a giant acronym soup.

At a Glance

🧭 Specification context

• Part of AQA GCSE Computer Science networking content.

• Students need to understand that protocols are rules that allow devices and services to communicate correctly.

• The main focus is recognising the purpose of common protocols and using accurate technical language.

Students must know

• what a protocol is

• the purpose of TCP/IP

• the difference between HTTP and HTTPS

• the purpose of FTP

• the roles of SMTP, POP and IMAP in email communication

Key exam focus

• selecting the correct protocol for a scenario

• explaining secure versus non-secure transfer

• distinguishing sending email from receiving email

• separating the role of TCP from the role of IP

Common student challenges

• mixing up POP and IMAP

• saying HTTPS is a completely different internet rather than a secure version of HTTP

• describing TCP/IP as one vague thing instead of two linked roles

• giving protocol names without explaining purpose

Understanding the Topic

A network protocol is a set of rules that devices follow so data can be sent, received and understood correctly. Without shared rules, communication across networks would be unreliable, inconsistent or impossible.

For AQA GCSE Computer Science, students should know the purpose of the main protocols rather than memorising unnecessary technical detail. The strongest answers stay precise and link each protocol to its job.

Core protocol knowledge

• TCP/IP underpins communication across networks.
• TCP checks that data is split into packets, transmitted reliably and reassembled in the correct order.
• IP is responsible for addressing and routing packets to the correct destination.
• HTTP is used to transfer web pages.
• HTTPS is the secure version of HTTP because data is encrypted.
• FTP is used to transfer files.
• SMTP is used to send email.
• POP and IMAP are used to receive email.

What students need to grasp securely

• A protocol is not a physical device or a piece of hardware.
• Different applications use different protocols because the rules needed for web browsing, file transfer and email are not the same.
• Reliable delivery and correct addressing are separate ideas, which is why TCP and IP are taught together but have different roles.
• Secure communication questions usually reward the word encryption, not just “safer”.

💡 Teacher tip
A quick way to improve recall is to group protocols by purpose:

• web: HTTP, HTTPS

• files: FTP

• email: SMTP, POP, IMAP

• reliable internet communication: TCP/IP

This stops every protocol becoming “the internet one” by period 5.

Key Terms and Concepts

How to Teach This Topic

Teaching approaches

• Start with the big idea that protocols are agreed rules.
• Use everyday comparisons carefully, such as classroom routines or game rules, then move quickly back to technical examples.
• Teach protocols in functional groups: web, file transfer, email, and reliable data transfer.
• Build a retrieval grid where students match protocol, full name and purpose.
• Use short scenarios such as “uploading a website file” or “sending an email” and ask students to choose the protocol.
• Revisit the difference between purpose and security when comparing HTTP and HTTPS.

Scaffolds and extension

• Give sentence stems such as “The purpose of SMTP is...” and “HTTPS is preferred because...”.
• Use dual coding with a simple flow from sender to server to receiver for email protocols.
• Ask students to sort cards into send, receive, web, file, and reliability.
• For stretch, ask students to explain why TCP and IP are paired rather than treated as identical.
• Challenge stronger students to improve weak one-mark answers into full two-mark explanations.

Useful discussion prompts

• Why is “used on the internet” not a strong enough definition for most protocols?
• Why does an exam answer about HTTPS usually need the idea of encryption?
• Why are SMTP and IMAP not interchangeable?
• Why is it helpful to separate reliable delivery from addressing?

🧠 Classroom move that works well
Give students six mini scenarios and ask them to justify the protocol choice in a full sentence. The justification matters more than the match. That is usually the difference between surface recall and an exam-ready answer.

How to Mark This Topic Effectively

Strong answers in this area are usually precise, functional and comparative. Students do better when they explain what a protocol does in context rather than simply naming it.

What strong answers contain

• the correct protocol for the scenario
• a clear purpose linked to the protocol
• technical vocabulary such as encryption, packets, addressing, routing, receive, or send
• a comparison when required, especially for HTTP versus HTTPS or POP versus IMAP

What examiners reward

• accurate distinction between TCP and IP
• explicit reference to security through encryption for HTTPS
• clear explanation that SMTP sends email
• clear explanation that POP and IMAP receive email
• answers that go beyond “it is faster” or “it is better” and explain why

Common marking issues

• awarding too much credit for vague phrases like “used for the internet”
• accepting “HTTPS is safer” without the mechanism of encryption when the question requires explanation
• overlooking the difference between retrieving email to a device and managing email on the server
• giving full credit when a student writes “TCP/IP sends packets” without separating reliability from addressing

📝 Marking reminder
If a question asks students to explain, look for a developed point, not just a named protocol. In many scripts, the protocol name is correct but the explanation is too thin to earn full marks.

Example Student Responses

Example question

Explain the difference between HTTP and HTTPS and give one reason why HTTPS is preferred for online shopping. [4 marks]

Marking guidelines

• 1 mark for identifying that both are used to transfer web pages or web data.
• 1 mark for stating that HTTPS is the secure version of HTTP.
• 1 mark for explaining that HTTPS uses encryption.
• 1 mark for linking encryption to protecting sensitive data such as passwords or payment details.

Practice Questions

Exam-style questions for teaching, revision and assessment

1. State what is meant by a network protocol. [1 mark]
   • Marking guidance: credit a clear idea of agreed rules for communication over a network.
2. Explain the role of TCP and the role of IP in network communication. [4 marks]
   • Marking guidance: reward separation of roles. TCP should be linked to reliable transmission, packet ordering or error checking. IP should be linked to addressing or routing to the correct destination.
3. Give one protocol used to send email and one protocol used to receive email. [2 marks]
   • Marking guidance: SMTP for sending. POP or IMAP for receiving.
4. Explain why HTTPS is used instead of HTTP when entering login details on a website. [3 marks]
   • Marking guidance: reward identification of HTTPS as secure, reference to encryption and explanation that this protects sensitive data.
5. A web developer needs to upload files from a local computer to a server. Name the protocol most likely to be used and explain why. [3 marks]
   • Marking guidance: reward FTP and an explanation linked to transferring files between systems.
6. A student says POP and IMAP do exactly the same thing, so there is no difference worth learning. How would you correct this? [4 marks]
   • Marking guidance: reward the shared idea that both retrieve email, then credit a distinction such as POP downloading to a device and IMAP managing email on the server across devices.

🎯 Exam technique
When students answer protocol questions, encourage the structure name it, define it, link it to the scenario. That simple routine often turns a one-mark response into a full-mark explanation.

Common Misconceptions

• “TCP/IP is just one thing with one job.”
  • Correction: TCP and IP work together, but TCP handles reliability while IP handles addressing and routing.
• “HTTPS means the website is trustworthy.”
  • Correction: HTTPS shows that data is encrypted in transit. It does not guarantee everything on the site is reliable or safe.
• “SMTP is for receiving email.”
  • Correction: SMTP is for sending email. POP and IMAP are for receiving it.
• “POP and IMAP are identical.”
  • Correction: Both retrieve email, but IMAP keeps email managed on the server, while POP is commonly taught as downloading email to a device.
• “HTTP is insecure because it does not work properly.”
  • Correction: HTTP still transfers web data correctly. The issue is that it does not provide the same encrypted protection as HTTPS.
• “A protocol is the same as hardware such as a router.”
  • Correction: A protocol is a rule set. Routers and other devices use protocols.

FAQ

Mark Faster, Keep Feedback Sharp

Marking.ai helps teachers save time while keeping marking accurate, consistent and useful for students. It is especially handy when you want faster feedback on extended answers without losing sight of what the mark scheme is actually rewarding.

✅ Use this page as a teaching and assessment companion: introduce the protocols clearly, revisit them with quick scenarios, and then apply the same precision when marking student responses.