ICT 0417 – Networks and Electronic Conferences
Learning Objective
Know and understand the hardware, software and network connection required to set up each type of electronic conference, and relate this knowledge to the wider Cambridge IGCSE ICT syllabus.
1. How This Topic Fits into the Whole ICT Syllabus
| Syllabus Area | Key Content Covered Here | Where to Find Further Detail |
|---|
| 1 – Types & components of computer systems | CPU, RAM, storage, operating‑system requirements for conference software; firmware/driver updates for webcams and audio interfaces. | Section “Computer Systems – Hardware & Software” (notes 1‑1) |
| 2 – Input & output devices | Microphones, webcams, headsets, speakers, interactive whiteboards; comparison of device types and testing checklist. | Section “Input & Output Devices” (notes 1‑2) |
| 3 – Storage devices & media | Local vs. cloud storage for recordings, recommended file formats, retention policies, GDPR‑compliant cloud services. | Section “Storage” (notes 1‑3) |
| 4 – Networks (general) | NICs, routers, switches, Wi‑Fi, protocols (TCP/IP, UDP), firewalls, QoS, typical school/office network diagram. | Section “Network Fundamentals” (notes 4‑1) |
| 5 – Effects of using IT | Health (screen fatigue, posture, “Zoom‑fatigue” mitigation), environmental impact (reduced travel, data‑centre energy), data‑privacy. | Section “Effects of Using IT” (notes 5‑1) |
| 6 – ICT applications (communication) | Electronic conferencing as a communication tool alongside email, instant messaging, VoIP; real‑world case study. | Section “Communication Applications” (notes 6‑1) |
| 7 – Systems life‑cycle | Planning, designing, configuring, testing, implementing and evaluating a conference solution (5‑step checklist). | Section “Systems Development” (notes 7‑1) |
| 8 – Safety & security | e‑safety, encryption, password hygiene, GDPR/HIPAA for recorded sessions, firewall ports. | Section “Safety & Security” (notes 8‑1) |
| 9 – Audience & copyright | Choosing appropriate settings for different audiences; respecting copyright of shared media. | Section “Legal & Ethical Issues” (notes 9‑1) |
| 10 – Communication (email & internet use) | Sending meeting invites, follow‑up emails, netiquette for chat and Q&A. | Section “Email & Netiquette” (notes 10‑1) |
| 11‑16 – File management, images, layout, styles, proofing, graphs/charts | Saving, naming and proof‑reading slides, screenshots, charts used in conferences. | Sections “File Management” to “Graphs & Charts” (notes 11‑16) |
| 17‑21 – Document production, databases, presentations, spreadsheets, website authoring | Preparing agendas (documents), sharing data (spreadsheets), publishing recordings (websites). | Sections “Word Processing” to “Web Authoring” (notes 17‑21) |
2. Types of Electronic Conference
- Audio Conference – voice‑only, telephone or VoIP.
- Video Conference – point‑to‑point or multipoint video with audio.
- Web Conference – screen‑sharing, chat, whiteboard, collaborative tools.
- Webinar – presenter‑focused, large audience, often with registration.
- Virtual Classroom – interactive learning environment with breakout rooms, polls, assessments.
3. Required Components for Each Conference Type
| Conference Type | Hardware | Software / Platform | Network Connection | Typical Bandwidth* |
|---|
| Audio Conference | - Headset or desk microphone
- Loudspeaker or headphones
- Optional telephone handset (PSTN or mobile)
| - VoIP client (e.g., Skype, Teams Audio, Zoom Audio)
- Conference bridge service (free‑conference‑call, corporate PBX)
| Wired Ethernet or stable Wi‑Fi (IP connectivity) | 64–128 kbps (mono) / 128–256 kbps (stereo) |
| Video Conference | - HD webcam (720 p min, 1080 p optional)
- Microphone and speakers/headphones
- Optional capture card for DSLR/4 K video
| - Video‑calling apps (Zoom, Microsoft Teams, Cisco Webex, Google Meet)
- Dedicated room systems (Polycom, Cisco Room Kit) for larger venues
| Wired Ethernet preferred; high‑quality Wi‑Fi acceptable if signal > ‑60 dBm | 720 p ≈ 1–2 Mbps; 1080 p ≈ 3–4 Mbps per participant |
| Web Conference | - Computer or tablet with webcam & mic
- Dual monitors (helpful for presenter)
| - Web‑based platforms (GoToMeeting, Adobe Connect, Microsoft Teams)
- Modules: screen‑share, whiteboard, chat, polling
| Wired Ethernet recommended; Wi‑Fi OK if stable | 1.5–3 Mbps (depends on shared content quality) |
| Webinar | - HD webcam (optional for presenter video)
- Professional cardioid microphone
- Lighting kit (soft‑box or ring light) for clear image
| - Webinar platforms (Zoom Webinar, Webex Events, GoToWebinar)
- Streaming encoder (OBS Studio, Wirecast) when using RTMP
| Wired Ethernet with low latency; upload speed critical | 720 p ≈ 3–5 Mbps upload; 1080 p ≈ 5–8 Mbps upload |
| Virtual Classroom | - Computer or tablet for each learner
- Headset with mic (reduces background noise)
- Interactive whiteboard or large‑format display (optional)
| - LMS with live‑class module (Moodle, Canvas, Google Classroom)
- Integrated video‑conference tool (Zoom, Teams)
| Wired Ethernet preferred in schools; robust Wi‑Fi for remote learners | 2–4 Mbps per active video stream; higher if multiple streams run simultaneously |
*Bandwidth figures are per participant and assume a good quality connection; actual needs may vary with codec, resolution and number of simultaneous streams.
4. Operating‑System, Driver & Firmware Requirements
- Supported OSes: Windows 10/11, macOS 10.15+, Linux (Ubuntu 20.04 LTS or later) – all provide the necessary audio/video drivers and support for TLS/SSL encryption.
- Browser compatibility: Chrome, Edge, Firefox, Safari (latest versions) for web‑based platforms.
- Driver updates: Ensure webcam, microphone and graphics drivers are up‑to‑date to avoid latency or compatibility problems.
- Firmware updates: Apply the latest firmware to routers, switches and access points before large‑scale conferences to improve QoS handling.
5. Input & Output Devices – Comparison & Testing Checklist
| Device | Pros | Cons | Typical Price (GBP) | Ideal Use‑Case |
|---|
| USB Headset (with mic) | All‑in‑one, easy plug‑and‑play, good noise isolation | Limited audio fidelity for music | £20‑£60 | Audio conferences, small‑group video calls |
| External USB/Webcam (1080 p) | Higher video quality, interchangeable lenses (some models) | Requires separate mic for best audio | £40‑£150 | Video conferences, webinars, virtual classrooms |
| Dedicated Conference Camera (4 K, PTZ) | Professional video, remote pan/tilt/zoom, auto‑framing | Expensive, needs dedicated mounting | £300‑£1,200 | Large boardrooms, webinars with many attendees |
| Interactive Whiteboard | Touch‑enabled drawing, easy sharing of annotations | High upfront cost, needs robust network | £800‑£3,000 | Virtual classrooms, design workshops |
Device‑Testing Checklist (run before every session)
- Connect the device and verify OS recognises it (Device Manager / System Settings).
- Open the conference software’s audio/video settings and run the built‑in test tone and video preview.
- Check audio level – aim for a peak of –12 dB without clipping.
- Check video framing – eyes roughly one‑third down from the top of the frame.
- Record a 10‑second test clip and play it back to confirm no echo, lag or pixelation.
- Ensure the device’s driver is the latest version (manufacturer’s website).
6. Storage Considerations for Recordings
- Recommended recording formats:
- Video: MP4 container with H.264/AVC codec (widely compatible, good compression).
- Audio: AAC (inside MP4) or separate MP3 for audio‑only recordings.
- File‑size estimate: 1‑hour 1080 p MP4 ≈ 1.5 GB (≈ 5 Mbps). Adjust based on required quality.
- Local vs. Cloud storage:
- Local SSD/HDD – fast access, but must implement backup.
- Cloud services (OneDrive, Google Drive, Dropbox, Microsoft Stream) – automatic versioning, remote access, GDPR‑compliant options.
- Retention policy: Keep recordings for the period required by the organisation (e.g., 30 days for internal meetings, 12 months for training sessions) and then archive or delete.
7. Core Network Fundamentals (Syllabus 4.1‑4.2)
- Network Interface Card (NIC) – wired (Ethernet) or wireless (Wi‑Fi) adapter.
- Router – connects LAN to WAN, performs NAT, may include firewall and QoS features.
- Switch – creates separate collision domains; typical school/office switch has 24–48 ports.
- Wireless Access Point (WAP) – provides Wi‑Fi coverage; supports 2.4 GHz and 5 GHz bands.
- Topologies – star (most common), mesh (redundancy), bus (legacy).
- Protocols – TCP (reliable, used for file transfer, email), UDP (low‑latency, used for VoIP/video), TLS/SSL (encryption for signalling).
- IP Addressing – IPv4 (e.g., 192.168.1.10) or IPv6; static vs. dynamic (DHCP).
- Quality of Service (QoS) – prioritises voice/video packets to reduce latency and jitter.
Typical School/Office Network Diagram (described):
Internet → ISP Router → Core Switch → (a) Wired endpoints (PCs, conference room PCs) and (b) Wi‑Fi Access Points → End‑user devices (laptops, tablets, smartphones). Conference clients sit on the end‑user devices and communicate via the router to the external conference service (e.g., Zoom cloud).
8. Effects of Network Performance on Conference Quality
- Latency – delay between sending and receiving data. Good practice: keep < 150 ms for interactive sessions.
- Jitter – variation in packet arrival time; causes choppy audio/video. Use buffering and QoS to minimise.
- Packet loss – missing data packets. Acceptable loss: < 1 % for voice, < 0.5 % for video.
- Bandwidth saturation – total traffic exceeds capacity, leading to reduced quality or dropped connections.
- Network congestion – heavy traffic on shared networks (e.g., school Wi‑Fi) raises latency and jitter.
Practical Activity (Year 10/11)
- Run a speed test (e.g., speedtest.net) on a classroom PC and record download, upload, ping and jitter.
- Compare the results with the bandwidth requirements in the table above.
- Discuss in groups how the measured values would affect an audio, video or webinar session.
- Suggest at least two ways to improve performance (e.g., enable QoS, use wired Ethernet, schedule meetings outside peak school hours).
9. Systems Life‑Cycle for an Electronic Conference
Use the following 5‑step checklist to align the set‑up with the ICT systems development life‑cycle.
- Requirements Analysis
- Identify audience size, security level, recording needs, and required collaboration tools.
- Design
- Select hardware (camera, mic, headset), software platform, and network topology.
- Plan for backup devices and alternative connectivity (mobile hotspot).
- Configuration / Development
- Install and configure the conference application, set up user accounts, enable encryption and passwords.
- Configure router QoS and open necessary firewall ports (see Section 9).
- Testing
- Run a trial meeting with a colleague; test audio, video, screen‑share, and recording.
- Check network performance (latency, jitter) during the test.
- Implementation & Evaluation
- Run the live conference, monitor quality, and collect feedback.
- Review logs, storage usage and any security incidents; update documentation for future sessions.
10. Safety, Security & e‑Safety (Syllabus 8.1‑8.3)
- Authentication & passwords – strong, unique passwords; enable two‑factor authentication where available.
- Encryption – TLS/SSL for signalling; SRTP for audio/video streams.
- Data protection – comply with GDPR (EU) or HIPAA (US) when recording or sharing personal data; obtain consent.
- Firewalls & port management – typical ports: TCP 443 (HTTPS), UDP 3478‑3480 (STUN/TURN), TCP 1935 (RTMP).
- e‑Safety etiquette – do not share meeting links publicly; use waiting rooms or passwords for webinars.
- Backup & retention – store recordings on secure cloud storage with appropriate access rights; define retention periods.
11. Health, Well‑being & Environmental Impact (Syllabus 5.1‑5.2)
- Zoom‑fatigue mitigation:
- Schedule a 5‑minute break every 45 minutes.
- Allow optional camera‑off periods for large meetings.
- Encourage use of virtual backgrounds to reduce visual strain.
- Ergonomic guidelines:
- Screen top at eye level; sit upright with feet flat.
- Use a headset to keep the microphone away from the mouth and reduce shouting.
- Adjust lighting to avoid glare.
- Environmental impact:
- Reduced travel cuts carbon emissions – a typical business trip of 200 km avoided saves ~30 kg CO₂.
- Data‑centre energy use: choose providers that publish renewable‑energy statistics.
12. Practical Set‑up Checklist (Before the Session)
- Verify hardware connections (camera, mic, speakers/headset) and run the device‑testing checklist.
- Run a speed test; confirm download/upload meet the minimum bandwidth for the chosen conference type.
- Ensure QoS is enabled on the router for VoIP/video traffic.
- Open required firewall ports (see Section 10).
- Update the conference software to the latest version.
- Perform a trial run with a colleague – test audio echo, video framing, screen‑share quality.
- Prepare a backup communication channel (phone number or instant‑messaging group) in case the primary connection fails.
- Check that recording settings (format, storage location, consent) are configured correctly.
13. Context‑Specific Effects of Using Networks
| Context | Positive Effects | Negative Effects / Risks |
|---|
| Business Meetings | - Reduced travel costs and carbon footprint
- Instant document sharing and collaborative editing
- Flexibility for remote teams across time zones
| - Security threats – unauthorised access, data leakage
- Technical failures can delay decision‑making
|
| Education – Virtual Classroom | - Access to learning resources for remote or home‑bound pupils
- Interactive tools – polls, breakout rooms, real‑time quizzes
| - Digital divide – inconsistent bandwidth among students
- Potential for distraction on personal devices
|
| Public Webinars | - Large audience reach, no venue limitation
- Recording for later reuse or on‑demand viewing
| - Risk of “Zoom‑bombing” or disruptive participants
- Server overload if capacity is exceeded
|
| Healthcare – Tele‑consultations | - Quick specialist access, especially in rural areas
- Reduced waiting times and travel for patients
| - Strict legal requirements (HIPAA, GDPR) for data protection
- Need for high‑quality video and low latency to ensure accurate diagnosis
|
14. Case Study: Virtual Parent‑Teacher Meeting (Cambridge IGCSE Level)
Scenario: A secondary school wants to hold a virtual parent‑teacher conference for Year 9 students. The meeting will involve a teacher, up to 10 parents, and a school administrator.
- Requirements analysis: Secure login, ability to share a PowerPoint agenda, record the session for absent parents, and use a chat function for questions.
- Design:
- Hardware – teacher uses a USB headset, 1080 p webcam, and a dual‑monitor setup.
- Software – Microsoft Teams (school licence) for video, screen‑share and recording.
- Network – wired Ethernet to the staffroom PC; QoS enabled for video traffic.
- Configuration:
- Create a Teams meeting, enable “Waiting room” and set a password.
- Upload the agenda to OneDrive and share the link in the meeting invitation.
- Set recording to store automatically in the school’s GDPR‑compliant SharePoint site.
- Testing: Teacher runs a 5‑minute test with the administrator, checks audio levels, video framing, and confirms that the recording starts correctly.
- Implementation & Evaluation:
- Meeting runs for 45 minutes; no technical issues reported.
- Post‑meeting survey shows 92 % of parents found the audio clear and the screen‑share useful.
- Recording is uploaded, and a link is emailed to parents who could not attend.
This case study illustrates how the hardware, software, network and safety considerations interlink with the ICT syllabus areas of communication, safety & security, and the systems life‑cycle.