What Is a Network? The Elements of Communication

What Is a Network? The Elements of Communication

What you'll learn

• Name the elements that every act of communication requires — between people or between machines
• Explain the two ingredients that turn a pile of electronics into a network: a physical signal and a shared protocol
• Recognize the networks already all around you, and sketch how their pieces connect
• Take a first, informal look at what the "box in the middle" of a network is doing

This lesson builds directly on Chapter 1 of Network Essentials, the textbook by Dr. Tahseen Al-Doori that forms the academic backbone of this course. The chapter opens not with cables, addresses or acronyms, but with a deceptively simple question: what does any communication need in order to work? Answer that question well and computer networking stops being mysterious. It becomes engineering applied to something you have been doing your whole life.

Communication needs three things

Strip communication down to its essentials and you find the same three requirements every time, whether it is a wave across the street, a letter, or a video call crossing an ocean:

1. A sender and a receiver. Something must produce the message, and something must be there to take it in. A radio station broadcasting into a desert with no listeners is transmitting, but it is not communicating.
2. A signal that can physically travel. The message has to ride on something real. When you speak, your message rides on pressure waves in the air. When you write, it rides on ink shapes that reflect light into someone's eyes. When you gesture, it rides on light itself. No physical signal, no message.
3. A shared way to interpret the signal. The receiver must be able to turn the signal back into meaning. Sound waves carrying Japanese reach the ears of someone who only speaks Portuguese perfectly well — the signal arrives intact, but the communication fails, because the two people do not share the rules for interpreting it. Those shared rules are a language. In networking, we call them a protocol.

Keep this trio in your pocket: sender and receiver, physical signal, shared rules. Every failure you will ever troubleshoot in this course is a failure of one of these three, dressed up in technical clothing.

From signals and languages to computers

Computers communicate with exactly the same three requirements — they just use different raw materials.

For the physical signal, computers have three options, and you will meet all of them in this course:

• Voltage — patterns of electrical charge on a copper wire. This is what an Ethernet cable carries.
• Light — pulses of light inside a glass fiber. This is how your data crosses cities and oceans.
• Radio waves — electromagnetic waves through the air. This is Wi-Fi, Bluetooth and mobile data.

For the shared rules, computers use agreed patterns built from just two states — on and off, high and low, one and zero. Everything a computer sends, from a text message to a movie, is first turned into patterns of these two symbols: binary. A protocol then defines what the patterns mean, in what order they may be sent, how a conversation starts and ends, and how the receiver confirms it understood. Where humans improvise, computers cannot: both sides must follow the protocol exactly, bit for bit, or nothing happens. That strictness is not a weakness — it is why a laptop built in one country can talk flawlessly to a server built in another, made by a company it has never heard of. We will devote a whole lesson to protocols in Module 2; for now, hold on to the definition: a protocol is the complete set of rules two devices agree to follow so that signals become meaning.

So here is our working definition of the course's central object. A computer network is a set of devices that can exchange data because they share a physical signal path and common protocols.

The networks you already live inside

Chapter 1 of the book makes this point with two drawings. The first shows what, for many people at the time, was their entire experience of networking: one computer and the box that connected it to the outside world. The second shows what homes and small businesses had already become — several computers, a printer, and a central device tying them together.

Redraw that second picture for your own home in 2026 and it explodes. A typical household now has laptops, phones and tablets, but also a TV, a game console, a printer, smart speakers, a doorbell camera, a thermostat, a watch, maybe a robot vacuum — a dozen to two dozen devices, almost all of them communicating by radio through one central box. You live inside a network. You also pass through others all day: your campus or office network, the café hotspot, the mobile network your phone falls back to in between, the short-range radio link between your phone and your earbuds. One of this lesson's quiet goals is to make these networks visible to you, because you cannot reason about what you have never consciously noticed. The activity below does exactly that.

A first look at the box in the middle

In a wired network, devices meet at a device called a switch. Its ancestor, the hub (obsolete), simply repeated every signal to everyone — even the 2007 edition of our textbook already treated hubs as history, and nobody has manufactured them for years. A switch is smarter, and a classic analogy from Dr. Al-Doori's course explains how, using a classroom.

Imagine your instructor pairs everyone up for lab work. Within minutes, you and your partner are locked onto each other's voices and barely register the chatter of the other pairs. Your pair has, in effect, a private lane of conversation — networking calls such a private lane a micro-segment. It is not perfectly private in one respect: if you and your partner both speak at the same instant, your words collide and you have to repeat yourselves. Networking borrows exactly this vocabulary — the space in which transmissions can collide is called a collision domain, and your pair forms a small one. But notice what happens when the instructor claps and makes an announcement: every pair hears it, no matter how absorbed they were. The whole classroom is one broadcast domain — the space an announcement reaches. Small collision domains, nested inside one large broadcast domain.

A switch builds the same structure electronically. It memorizes which device sits on which of its ports and then connects only the ports that are actually talking to each other, giving each conversation its own private lane, so devices on different lanes can never collide with each other. And when a switch receives data for a device whose port it has not yet learned? It sends the data out of every other port at once. The book's memorable image for this — retold in our words — is the furious manager who does not know who is responsible, so he shouts at the entire office. The right device answers, the switch learns its port, and the shouting stops. That everyone-gets-a-copy behavior is called flooding, and it is one reason the broadcast domain matters.

This is a preview, not the full story. In Module 3 you will build networks with and without switches in a simulator and watch collisions appear and disappear with your own eyes. For now it is enough to recognize the pattern: private lanes inside a shared room.

Activity: Home network inventory

This is an observation activity — no tools to install, nothing to configure, nothing you can break.

Objective. Discover every networked device where you live and produce your first network sketch — the raw material for the next lesson's diagram.

Setup. Pen and paper (or any drawing app). Access to your home, dorm or small office. Optional: the app or admin page of your Wi-Fi router, if you know how to reach it.

Steps.

1. Write down every device you can think of that communicates over a network. Then walk through each room and catch the ones you forgot — TVs, consoles, printers, speakers, cameras, thermostats, plugs, e-readers, watches.
2. Find the central equipment: the box (or boxes) your Internet provider installed, your Wi-Fi router, and any extra boxes such as mesh pods or a small switch. Add them to the list.
3. Mark each device W if it connects wirelessly or E if a cable runs to it. If you are unsure, check the device's settings or simply look for a cable.
4. Sketch the network: central box in the middle, one line from it to every device — solid lines for cables, dashed lines for wireless.
5. Count the devices and write the total on the sketch.

Expected result. A typical home yields somewhere between 8 and 25 devices, the large majority on dashed (wireless) lines, all radiating from one or two central boxes. Your sketch will look like a wheel with spokes — remember that shape; it gets a name in Lesson 3.

Verify. If you can open your router's app or admin page, find its list of connected devices and compare the count with yours. Almost everyone discovers at least one device they missed — that is the point of the exercise.

Questions.

1. Which device on your list surprised you most?
2. For three of your lines, name the physical signal they carry (voltage, light or radio).
3. If the central box lost power, which of your devices could still communicate with each other, if any?
4. Where exactly does your network end and your Internet provider's begin? (Keep your answer — the next lesson is about precisely this question.)

If it goes wrong.

• You cannot find the router. Follow the cable from the wall socket or the provider's box; the router is usually the device everything else points at, often blinking near where the Internet line enters the home.
• You have mesh Wi-Fi pods. Treat the main pod (the one cabled to the provider's box) as the center and draw the satellite pods as secondary centers with their own dashed lines.
• The router lists more devices than you found. Old phones, smart plugs and long-forgotten gadgets linger. Cryptically named entries can usually be identified by switching them off and watching which entry disappears.

Check yourself

Work each item before opening the answers.

1. Two ships signal each other at night with lamp flashes in Morse code. Map the three elements of communication onto this scene.
2. You connect two laptops with a known-good cable, but a file-transfer tool on one cannot see the other. In elements-of-communication terms, which elements are clearly present, and which one is the prime suspect?
3. Match each link to the physical signal it uses: (a) a laptop on Wi-Fi, (b) a desktop on an Ethernet cable, (c) the provider's line that enters your building underground.
4. During paired lab work, two classmates start talking at exactly the same moment and must repeat themselves; a minute later the instructor's announcement reaches every pair at once. Which networking concept does each of the two events illustrate?
5. A switch receives data addressed to a device it has not yet learned the port for. What does it do, and why did this lesson compare that behavior to a manager shouting at the whole office?
6. Your smart thermostat reports the temperature to your phone while you are in another city. Name at least two different networks involved in carrying that message.

Answers

1. Sender and receiver: the two crews. Physical signal: light. Shared rules (protocol): Morse code, which both crews must know for the flashes to become words. All three present — communication works.
2. Present: sender and receiver (the laptops) and the physical signal (voltage on a working cable). Prime suspect: the shared rules — the machines are not yet agreeing on the same protocols and settings. Later in the course you will name the specific missing pieces (matching addresses, for one).
3. (a) radio waves, (b) voltage on copper, (c) light in fiber (in most modern buildings; older ones may still use voltage on copper lines).
4. The simultaneous talkers illustrate a collision inside one collision domain (the pair). The announcement illustrates a broadcast reaching the whole broadcast domain (the classroom).
5. It floods the data out of every port except the one it came in on. The comparison fits because the switch does not know who is responsible for answering, so it addresses everyone; when the right device replies, the switch learns its port and stops shouting.
6. Any two of: your home Wi-Fi network (the thermostat's network), your Internet provider's network and the wider Internet, and the mobile network your phone is using in the other city.

Key terms

• Network — a set of devices that can exchange data because they share a physical signal path and common protocols.
• Sender / receiver — the parties producing and consuming a message; communication requires both.
• Signal — the physical carrier of a message; computers use voltage, light or radio waves.
• Protocol — the complete set of rules two devices agree to follow so that signals become meaning.
• Binary — the two-symbol (one/zero) representation computers use for all data.
• Switch — the device that connects computers in a modern wired network by learning which device is on which port (full treatment in Module 3).
• Hub (obsolete) — the switch's ancestor, which repeated every signal to every port.
• Collision domain — the region of a network in which two simultaneous transmissions can interfere (preview).
• Broadcast domain — the region of a network that a broadcast transmission reaches (preview).
• Flooding — a switch's everyone-gets-a-copy behavior when it does not yet know the destination's port.

Summary

• Every communication needs a sender and receiver, a physical signal, and shared rules for interpreting it — three requirements as true for lamp signals as for laptops.
• Computer signals come in three physical forms: voltage on copper, light in fiber, radio through the air.
• Protocols are the "language" of machines: exact, mandatory, and the reason unrelated devices can interoperate worldwide.
• All data is expressed in binary — patterns built from two states — before it ever touches a wire or the air.
• You already live inside multiple networks; a modern home easily contains a dozen or two networked devices around one central box.
• A switch gives wired devices private conversation lanes (small collision domains) while everyone still shares one broadcast domain — like lab pairs in a classroom who all still hear the instructor.
• When a switch doesn't know where to deliver, it floods to everyone and learns from who answers.

Next lesson

You can now say what a network is — next we sort networks by reach and ownership, and find the exact spot in your home where your network ends and the Internet begins.

Sources and further study

• Network Essentials, Dr. Tahseen Al-Doori — Chapter 1, "Introduction to Networking": the academic backbone of this lesson (elements of communication, the classroom and office analogies).
• Cisco Networking Academy — Networking Basics (free course): its opening modules cover the same ground with interactive checks, and this course's device taxonomy follows the same tradition.
• Kurose & Ross, Computer Networking: A Top-Down Approach — Chapter 1, for a university-depth second telling of what a network is.
• Stanford CS144, Introduction to Computer Networking — publicly available materials, if you want a rigorous preview of where this course is headed.