Zum Inhalt springen

English:Networks, protocols and connectivity - Computing Year 10

Aus MOOCsWiki Staging
Version vom 14. November 2026, 05:51 Uhr von Glanz (Diskussion | Beiträge) (AI MOOC Plugin 229116b000723e699ef660745a6aee04)
(Unterschied) ← Nächstältere Version | Aktuelle Version (Unterschied) | Nächstjüngere Version → (Unterschied)
aiMOOC-Siegel aiMOOC

Networks, protocols and connectivity - Computing Year 10

QR-Code



Introduction

Historical partial internet connectivity visualisation with many interconnected nodes
The Opte Project’s early-2005 partial visualisation is historical context, not a current or complete network map. Our original school diagram and connection table define the learning task independently of its colours or tiny labels.

Design a school network with wired desktops, wireless tablets, a local server and an internet route. Distinguish device roles, compare protocols and layers, trace local/external traffic, and justify safe access controls and shared-capacity assumptions.


Choose network scope devices and connectivity


Describe scope and purpose before choosing a connection

A network connects devices so that they can exchange data and use services under agreed rules. A local area network or LAN covers a limited local setting, such as a school site. A wide area network or WAN connects across larger geographic distances or between sites. Geographic scope is different from whether a link uses a cable or radio: a LAN can include both Ethernet and Wi-Fi.

The internet is an interconnected network of networks. The World Wide Web is an application/service environment using web resources over networks; it is not a synonym for every internet service. A school can have a functioning local file service even while its external internet connection is unavailable. A Wi-Fi signal by itself does not prove that DNS, the router or an external service is working.

Role Purpose in the original school design Distinction
Switch Connects the local Ethernet devices and forwards frames within the local network Not the same job as selecting routes between different IP networks
Wireless access point Connects the tablets’ Wi-Fi link to the local network A radio connection does not itself supply every internet service
Router Forwards IP traffic between the school network and another network Can share a physical enclosure with other roles without becoming identical to them
Local server Provides an approved local service to permitted school clients Not necessarily the same machine or network as a public web server
Client device Requests or uses an authorised service It can use wired or wireless connectivity depending on requirements

A consumer or school gateway appliance may combine router, switch, access point and firewall functions in one box. A conceptual diagram still distinguishes the roles. A switch usually forwards local Ethernet frames using link-layer information; a router forwards packets between IP networks. More advanced devices can perform several functions, so these labels describe the declared role rather than an absolute rule about every product.


Ethernet can give a stable fixed connection and reduce dependence on shared radio conditions, but requires suitable cabling and ports. Wi-Fi supports mobility and flexible device placement, but coverage, interference, shared airtime and access control affect performance. Neither medium is automatically secure, free from faults or always fastest in every real environment.

For fixed desktops and the local server, the original design uses approved Ethernet links to a switch. Mobile tablets use an access point attached to that switch. The router provides the path to another network and the internet. This is a simplified single-LAN design; a real school may need several subnets, controlled guest access and multiple access points under its own policy.


Interpret the historical network image

The Commons image is a partial historical internet connectivity visualisation based on early-2005 data. It illustrates many interconnected relationships, not a current geographic map, a complete internet inventory or our school’s topology. Its colours and line lengths must not be used as present-day measurements or as the answer to the school-design task. The original labelled diagram in the next chapter defines our own fictional links.

CodeAI / Code.org: IP Addresses & DNS. Identify naming and addressing roles, then distinguish the video’s examples from our fictional school diagram. The written explanations and native tasks remain usable without the player. Original: CodeAI, The Internet: IP Addresses & DNS. The written explanations and native tasks work without sound or the external player. Use about 55 minutes for the core lesson: five for retrieval, ten for device/link explanation, twelve for a worked route, ten for guided protocol matching, thirteen for the required complete design and five for evidence/reflection. Further activities extend the work. Year 10 allocation is editorial within the common GCSE/KS 4 pathway.



Trace the school topology and protocol layers


Build the required school network

The required transfer includes a local server, wired desktops, Wi-Fi tablets and an internet connection. Name each device and each link. Our design uses Desktop A, Desktop B, Local server, Switch, Access point, Tablets, Router, Internet and a remote Web server. "Tablets" represents a group connected to the same access point, not one physical cable into every tablet.

Desktop A --Ethernet-- Switch --Ethernet-- Router --WAN-- Internet -- Web server
Desktop B --Ethernet--/  |
Local server --Ethernet--+
                        |
                    Access point
                        |
                       Wi-Fi
                        |
                      Tablets

The connection table removes any ambiguity from the text sketch. Draw the school LAN boundary around the clients, server, switch, access point and router’s school-facing interface; the router’s external connection leads out through the provider/WAN. The Internet label is a simplification of a larger path, not a single switch on the school premises.

Connection Medium or role
Desktop A to Switch Ethernet
Desktop B to Switch Ethernet
Local server to Switch Ethernet
Access point to Switch Approved wired backhaul in this design
Tablets to Access point Wi-Fi
Switch to Router Local Ethernet
Router to Internet Provider/WAN path, simplified
Internet to Web server Remote network path, simplified

For a desktop’s external request, trace Desktop A → Switch → Router → Internet → Web server. For a tablet, trace Tablets → Access point → Switch → Router → Internet → Web server. Responses return through the corresponding connectivity path in this simplified model. Real internet return routes need not match every outbound hop.

For the local service, trace Tablets → Access point → Switch → Local server. The local-server path does not need the internet-facing link under this single-LAN assumption. A packet’s final destination and the next device on its path are different concepts; a tablet does not automatically treat the access point as the final web server.


Explain protocol rules and a four-layer teaching model

A protocol defines rules for communication, such as message meaning, format or behaviour. A layer groups related responsibilities behind an interface. A layer is not necessarily a separate box, software application or physical wire. We use a four-layer TCP/IP teaching model; other textbooks may name or group layers differently, including the seven-layer OSI model.

Layer in this course Responsibility Examples
Application Meaning of an application exchange HTTP for web messages; DNS for name-related records
Transport Communication between application endpoints TCP provides a reliable ordered byte stream; UDP provides datagrams without that stream guarantee
Internet IP addressing and delivery across networks IP and routing between networks
Link Communication over a particular local link Ethernet or Wi-Fi framing and media access

TCP does not itself encrypt the application data. IP provides a best-effort delivery service rather than guaranteeing that every packet arrives once and in order. UDP’s smaller service does not mean that every application built on UDP must lack reliability; a higher protocol can provide additional behaviour. Keep the layer’s own role separate from the complete application’s behaviour.


Follow a stated secure web exchange

Our worked example is HTTP/1.1 over TLS over TCP over IP, carried first by Wi-Fi or Ethernet on the local link. If the needed name result is not already available, DNS can help obtain a suitable address record. TCP establishes its transport connection, TLS provides the selected secure-channel protections and checks the server identity under its trust model, and HTTP carries the request/response semantics.

Do not claim that all HTTPS uses TCP. HTTP/3 uses QUIC over UDP, with secure transport and stream behaviour supplied by QUIC; the page still uses HTTP semantics. Also do not claim that DNS is always UDP: traditional DNS supports both UDP and TCP, with later encrypted mechanisms beyond this introductory exchange. The chosen example should be stated before naming its stack.

CodeAI / Code.org: HTTP & HTML. Distinguish the web-exchange protocol from document markup and compare its conceptual request with the explicitly stated modern transport alternatives above. Native text and tasks remain usable without the player.

TLS can protect a connection under its assumptions, but an encrypted connection does not prove that a site’s claims are true or that a compromised endpoint is safe. DNS naming, transport delivery, web meaning, encryption and school permission are related but different functions. A good explanation names which problem each part solves.



Evaluate security faults and shared capacity


Make network security part of the design

Specify who needs which service before adding controls. School-managed clients may need approved learning services, while guest devices may be restricted from internal files. A physical path to a server does not imply permission to use it. Authentication checks a claimed identity; authorisation determines permitted actions. Encryption protects particular communications or stored data, not every possible weakness.

Design need Reasoned control Limit to state
Managed client access Approved accounts and least-privilege service permissions A valid account is not permission for every resource
Wireless access Approved secure Wi-Fi configuration and managed credentials Coverage and encryption do not prove external service availability
Traffic boundaries Policy-controlled firewalling and network segmentation where needed A route or firewall label alone does not prove every rule is correct
Device maintenance Supported updates and approved configuration management Do not disable protections just to obtain a faster test
Availability and recovery Monitoring and an approved recovery/backup plan A second copy or path must be checked against the actual failure
Incident response Report observed symptoms using the school’s agreed route Do not scan, probe or reconfigure a live school network without authority

The course requires a design and explanation, not intrusion testing. Use the fictional nodes and table rather than collecting real school addresses, credentials or packet contents. A teacher-approved isolated simulator or paper model is sufficient for the topology task. If any real practical observation is separately authorised, record exactly what was observed without exposing private configuration.


Diagnose faults by comparing paths

In our model, removing the access point disconnects the tablet group, while a wired desktop can still have its external path. Removing only the Router–Internet link prevents external access for both groups, but the tablet-to-local-server path can still exist. Removing the Local server–Switch link affects the local server while the external web path can remain intact. These predictions depend on the declared simplified topology and functioning remaining services.

A DNS failure can prevent a name-based request even if the required physical links are present. A permission failure can block a service even if the named host is reached. If one approved page fails while another works, do not immediately label every cable broken. Record the symptom, the relevant path/function and a distinguishing safe test or report; avoid changing several variables at once.


Twenty fictional tablets each need an 8 MB payload. Here MB is decimal, so each payload is 8,000,000 bytes. Total payload is 20×8,000,000 = 160,000,000 bytes, or 1,280,000,000 bits. If the group could use a constant 80,000,000-bit-per-second shared payload rate, the ideal time would be 16 seconds.

This is a declared arithmetic model, not a measured Wi-Fi speed or completion guarantee. Real protocol overhead, retransmission, server limits, shared airtime and other traffic can increase the time. The aggregate group does not give every tablet an independent 80 Mbit/s at the same time. With equal continuous sharing and no other constraints, each would average 4 Mbit/s and its own 64,000,000-bit payload would also take 16 seconds.

Doubling the group to forty tablets at the unchanged aggregate payload rate doubles the ideal total time to 32 seconds. Increasing a local link rate does not necessarily change the remote server or WAN bottleneck. A faster headline link alone cannot prove a faster end-to-end lesson download. Always state bits versus bytes, the aggregate rate and the idealising assumptions.


Submit the complete required design

Provide a labelled diagram with server, wired desktops, Wi-Fi tablets, switch, access point, router and external connection. Annotate the media, school boundary, local and external paths, and switching-versus-routing roles. Explain protocols and layers using the stated web stack, noting that other valid transports exist. Add a security decision tied to an access requirement and a separate physical-connectivity explanation.

Include the three changed-link predictions and the shared-capacity calculation with units and limits. State whether your evidence is a paper trace, an isolated simulation or an actually authorised observation. A diagram and quiz do not certify a real school network’s security or practical competence. Current awarding-organisation conventions and teacher review remain relevant, and any real network change needs its own authority.



Interactive Tasks


Quiz: Test Your Knowledge

Which statement correctly distinguishes LAN scope from a link medium? (A local school network can contain both Ethernet and Wi-Fi) (!Every LAN must use only radio) (!Every wireless link is automatically a WAN) (!A LAN is defined by the number of websites opened)



What is the switch’s declared main role here? (Forward local Ethernet traffic among the attached LAN devices) (!Replace every internet router across the world) (!Translate every web document into a password) (!Guarantee all users are authorised)



What connects the tablet Wi-Fi link to this school LAN? (The access point attached to the switch) (!The remote web server acting as a keyboard) (!The local-server filename) (!The shared-link calculation alone)



Which local service path matches the declared design? (Tablets to access point to switch to local server) (!Tablets directly to a mandatory overseas server for every local file) (!Desktop A to an unconnected power socket) (!Internet directly to the tablet without any local link)



What is a protocol layer? (A grouping of related communication responsibilities) (!Always a separate physical box) (!The colour assigned to a network cable) (!A guarantee of unlimited bandwidth)



Which distinction about TCP and encryption is correct? (TCP supplies an ordered reliable byte stream while TLS supplies separate secure-channel protections in the stated stack) (!TCP alone proves every website is truthful) (!Every UDP application must be unreliable at every higher layer) (!IP alone guarantees ordered delivery exactly once)



Which claim about the worked web stack is sound? (It uses HTTP/1.1 over TLS and TCP, while HTTP/3 uses QUIC over UDP) (!Every HTTPS connection must use TCP with no exceptions) (!DNS always uses only UDP under every mechanism) (!HTTP and HTML are identical names for a cable)



What remains possible when only the router-to-internet link fails in the stated model? (The tablet-to-local-server path through the access point and switch) (!External internet access with no alternative route) (!Every service must necessarily fail for the same reason) (!No wired desktop can ever contact the switch)



What is the ideal group time for the stated twenty-tablet payload and shared rate? (16 seconds before real-world limitations) (!0.2 seconds because every tablet gets an independent aggregate link) (!160 seconds by ignoring the stated units) (!Exactly 16 seconds guaranteed on every real school Wi-Fi network)



What is appropriate evidence for this course’s design task? (A labelled fictional topology, reasoned routes, protocol roles and honestly described safe tests) (!Scanning the real school network without authorisation) (!Publishing real credentials to make the diagram complete) (!Removing firewall protection to avoid explaining permissions)





Memory Game

Switch Forwards local traffic among devices in the declared LAN role
Router Forwards IP traffic between different networks
Access point Connects wireless clients to the local network
DNS Provides name-related records used in addressing decisions
Protocol Defines communication rules and behaviour
Layer Groups related network responsibilities behind an interface





Drag and Drop

Trace a local request Follow tablets through access point and switch to the local server
Trace an external request Include the router and provider/internet path to the remote service
Distinguish naming and delivery Separate a DNS record lookup from moving application traffic
Diagnose a wireless-only failure Compare access-point reachability with an unaffected wired path
State a shared-rate assumption Use the aggregate payload rate once for the group and retain bit/byte units





Crossword Puzzle

ROUTER Which device role forwards traffic between IP networks?
SWITCH Which device role forwards local Ethernet traffic here?
PROTOCOL What defines communication rules?
LAYER What groups related communication responsibilities?
CLIENT What requests or uses an authorised service?
SERVER What provides a service to clients?





LearningApps

Optional extra practice. Choose an appropriate activity with your teacher. If the external collection is unavailable, use the native activities and independent tasks in this course.


Cloze Text

Complete the explanation.
A school LAN may use Ethernet and

. Wireless clients connect through an access

. A

connects the local Ethernet devices in this design. A

forwards traffic to another network. Protocol

group responsibilities. Naming and packet delivery are

functions. Twenty 8 MB payloads total

MB. At the stated aggregate rate the ideal group time is

seconds. A physical path does not by itself give

.



Open Tasks


Easy

  1. Distinguish LAN and WAN: Explain scope separately from wired or wireless media.
  2. Explain device roles: Give different jobs for switch, access point, router and server.
  3. Trace the local route: List every node from Tablets to Local server under the declared design.
  4. Explain a protocol layer: Match one responsibility and example to each of the four teaching layers.


Standard

  1. Complete the required school diagram: Include server, desktops, tablets, media, switch, access point, router and internet boundary with labelled paths.
  2. Trace the stated web exchange: Separate DNS naming, HTTP meaning, TCP delivery and TLS protections in the declared example.
  3. Diagnose three changed links: Predict access-point, external-link and local-server-link failures without probing a real network.
  4. Show the shared-rate arithmetic: Calculate 160 MB,1280 million bits and 16 ideal seconds, stating the aggregate assumption.


Advanced

  1. Challenge a universal-protocol claim: Explain why all HTTPS uses TCP and DNS always uses UDP are both overstatements.
  2. Separate access and connectivity: Design a guest/internal-service permission rule without pretending that a path grants authority.
  3. Change the group size: Calculate the forty-tablet ideal time and explain possible bottlenecks beyond the local link.
  4. Defend the network design: Combine the complete topology, layered exchange, security decision, fault predictions and honest evidence limits.



Learning Check

  1. Required school-network transfer: Describe the labelled topology and two traffic paths.
  2. Switching, routing and access points: Explain their distinct functions.
  3. Protocol layers and modern alternatives: Explain the explicitly chosen secure web stack.
  4. Fault predictions: Compare the changed-link cases.
  5. Shared-capacity calculation: Calculate twenty and forty tablet cases.
  6. Security and evidence: Evaluate what a correct design proves.


Worked checks and assessment guidance

  1. Desktops and local server use Ethernet to the switch; tablets use Wi-Fi to an access point connected to that switch. The switch connects to the router for external networks. External tablet traffic follows Tablets→Access point→Switch→Router→Internet→Web server; local traffic follows Tablets→Access point→Switch→Local server. Diagram roles and medium labels are required.
  2. The switch forwards local Ethernet frames in this LAN role; the access point joins the Wi-Fi clients to the local network; the router forwards IP traffic between networks. One physical appliance can combine roles, so the conceptual distinction is not a demand for one box per layer. Geographic LAN/WAN scope is different from cable/radio medium.
  3. The worked exchange is HTTP/1.1 over TLS over TCP over IP and a local Ethernet/Wi-Fi link. DNS can provide name-related address records when needed. TCP is not encryption. HTTP/3 instead uses QUIC over UDP with its own secure/reliable transport behaviour; traditional DNS supports UDP and TCP. A layer groups functions, not necessarily physical boxes.
  4. Without the access point, the tablet group loses its path while wired desktops can remain connected. Without only the Router–Internet link, external access fails but local tablet-to-server connectivity can remain. Without Local server–Switch, the server loses its path while other external routes can remain. These predictions assume the remaining model links and services work.
  5. Twenty times 8000000 bytes gives 160000000 bytes or 1280000000 bits. Divide by 80000000 bits per second to get 16 ideal seconds. Forty unchanged payloads at the same aggregate rate take 32 ideal seconds. With equal sharing among twenty, the per-client average is 4 Mbit/s, not 80 Mbit/s. Overhead, other traffic, radio conditions and endpoints prevent treating these figures as measured guarantees.
  6. Tie managed/guest access to authentication, authorisation, appropriate segmentation/firewall policy, supported configuration and recovery. A physical route is not permission; an encrypted connection is not proof of truthful content or uncompromised endpoints. Submit a fictional diagram, reasoning and honestly labelled paper/simulator/authorised observations. No unauthorised scanning, credential collection or protection changes are part of this course.


Learning evidence

Submit the complete original school topology, media and boundaries, local/external routes, distinct device functions and four-layer explanation with a stated web stack. Include a justified access-control decision, three changed-link predictions and the 20/40-tablet shared-rate calculations with units and assumptions. Label paper reasoning, isolated simulation and actually authorised observations separately; expose no real school configuration or credentials.


OER and Wikipedia

DfE GCSE Computer Science subject content is the mapped common baseline; Year 10 allocation is editorial. IETF RFC 1122: host communication layers supplies the foundational protocol-layer model; it is not a complete current catalogue of all internet mechanisms. IETF RFC 1035, section 4.2 documents traditional DNS over UDP and TCP. IETF RFC 9114: HTTP/3 describes the QUIC-based HTTP mapping. Original topology, capacity cases, fault reasoning, tasks and feedback were created for this course. Reviewed 14 November 2026.

Internet map 1024.jpg, The Opte Project, CC BY 2.5. Unchanged original; caption and learning activities are original.

https://www.youtube.com/watch?v=5o8CwafCxnU — CodeAI: The Internet: IP Addresses & DNS; unchanged original publisher embed. https://www.youtube.com/watch?v=kBXQZMmiA4s — CodeAI: The Internet: HTTP & HTML; unchanged original publisher embed.



Linked learning areas


aiMOOC Projects



Schulfach+




aiMOOCs



aiMOOC Projekte









MOOCwiki · Deutsch

Nach dem Lernen ist vor dem Lernen

Entdecke direkt den nächsten Lernkurs. Weitere Inhalte erscheinen, wenn Du weiter nach unten scrollst.

Zur MOOCwiki-Hauptseite

Mediathek

Suche verfeinern

Dein Lernplan bestimmt, was oben steht. Alle anderen Inhalte bleiben erreichbar. Seitenaufrufe beeinflussen die Auswahl nicht.

Inhalte werden geladen ...

Mediathek wird aus dem Wiki geladen ...