3  Network Topology Concepts

In 60 Seconds

Network topology describes how devices are connected in a network, with two distinct views: physical topology (where devices are physically located and cabled) and logical topology (how data actually flows between nodes). Understanding basic topology types—star, bus, ring, mesh, and tree—is essential for designing IoT networks that meet your requirements for reliability, cost, and scalability.

3.1 Learning Objectives

By the end of this section, you will be able to:

• Define Network Topology: Explain what topology means in the context of networking and IoT
• Distinguish Physical from Logical Topologies: Contrast physical device placement with logical data flow paths
• Classify Basic Topology Types: Categorize star, bus, ring, and mesh configurations by their structural properties
• Justify Topology Choices for IoT: Argue why topology selection directly impacts reliability, cost, and scalability

3.2 Prerequisites

Before diving into this chapter, you should be familiar with:

• Networking Basics: Understanding fundamental networking concepts including network devices (routers, switches, hubs), connection types, and basic network design principles provides the foundation for topology concepts
• Layered Network Models: Knowledge of the OSI model helps you understand how topologies relate to different network layers and why physical and logical topologies can differ
• Basic IoT device types: Familiarity with sensors, actuators, gateways, and their communication needs helps you appreciate which topologies work best for different IoT deployment scenarios

Cross-Hub Connections

This chapter connects to multiple learning hubs for deeper exploration:

Simulations Hub: Try the Interactive Network Topology Visualizer (included in this chapter) to experiment with star, mesh, tree, and hybrid topologies. Compare metrics like latency, fault tolerance, and cost trade-offs in real-time.

Videos Hub: Watch visual explanations of physical vs logical topologies, mesh self-healing demonstrations, and real-world IoT topology deployments in smart cities and industrial environments.

Quizzes Hub: Test your understanding with scenario-based questions on topology selection for different IoT applications (smart homes, factories, campuses). Includes Understanding Checks for smart factory and smart city streetlight scenarios.

Knowledge Gaps Hub: Address common misconceptions about mesh complexity, star reliability, and the physical vs logical topology confusion that causes deployment failures.

MVU: Minimum Viable Understanding

Core concept: Network topology defines the arrangement of devices and connections in a network. There are two views: physical topology (where devices are located) and logical topology (how data flows). These views are often different for the same network.

Why it matters: Your topology choice determines fault tolerance, scalability, latency, and cost. A poor choice can cause entire systems to fail when a single device breaks.

Key takeaway: For IoT, star topology (all devices connect to one hub) is simplest but has a single point of failure. Mesh topology (devices connect to multiple neighbors) is more reliable but complex. Most real-world IoT uses hybrid approaches.

Why Network Topologies Matter for IoT

Understanding network topologies is essential for designing scalable IoT systems. Whether deploying smart home sensors, industrial monitoring, or smart city infrastructure, the topology determines reliability, scalability, and performance. Physical placement of sensors and logical communication patterns directly impact system effectiveness.

For Kids: Meet the Sensor Squad!

Network Topology is like choosing how to arrange friends so everyone can pass notes to each other!

3.2.1 The Sensor Squad Adventure: The Great Connection Contest

Temperature Terry, Light Lucy, Motion Marley, Pressure Pete, and Signal Sam were moving into a brand new smart house. But there was a big problem - they needed to figure out how to arrange themselves so they could all send messages to each other!

“I know!” said Signal Sam. “Let’s have a Connection Contest to find the best arrangement!”

Round 1 - The Star Shape:

Signal Sam stood in the middle of the room. “Everyone connect to ME! I’ll be the message center - like a post office!” So Terry, Lucy, Marley, and Pete each ran a wire to Sam in the middle.

“This is easy!” said Temperature Terry. “I just tell Sam, and Sam tells everyone else!”

But then Signal Sam pretended to fall asleep. “Zzzzz…”

“Oh no!” cried Light Lucy. “If Sam stops working, NONE of us can talk to each other! The star has ONE big weakness - the middle!”

Round 2 - The Ring Shape:

“Let’s try standing in a circle!” suggested Motion Marley. So they arranged themselves: Terry next to Lucy, Lucy next to Marley, Marley next to Pete, Pete next to Sam, and Sam back to Terry - forming a ring!

“To send a message, we pass it around the circle - like the telephone game!” explained Pressure Pete.

But when Light Lucy covered her ears (pretending to be broken), the message from Terry couldn’t get past her to reach Marley!

“Hmm,” said Terry. “One broken sensor stops the whole ring!”

Round 3 - The Mesh Shape:

“I have an idea!” said Signal Sam excitedly. “What if we ALL connect to EACH OTHER? Like a spider web!”

So they created a web of connections - Terry could talk to Lucy, Marley, Pete, AND Sam. Everyone was connected to everyone!

Motion Marley tested it by covering her ears. “Can Terry still talk to Pete?”

“Yes!” cheered Pete. “The message goes Terry to Lucy to Pete, OR Terry to Sam to Pete! There are LOTS of paths!”

The Winner:

“The mesh is the most reliable,” concluded Signal Sam. “But it uses the most wires. Let’s use mesh in important rooms like the kitchen, and stars in simple rooms like the garage!”

3.2.2 Key Words for Kids

Word	What It Means
Topology	The shape or pattern of how things connect - like a map of connections
Star	Everyone connects to ONE thing in the middle (like a pizza with slices)
Ring	Everyone connects in a circle, passing messages around
Mesh	Everyone connects to everyone else - like a spider web
Router	The “helper” in the middle of a star that passes messages around
Fault Tolerance	When a network keeps working even if one part breaks

3.2.3 Try This at Home!

The Network Shape Game (play with 4-6 friends or stuffed animals):

1. Star Game: One person is the “router” in the middle. Everyone else can ONLY whisper to the router, who passes messages along. Time how long it takes to send “Hello” from one side to the other!

2. Ring Game: Stand in a circle. Pass a message by whispering to the person on your right ONLY. What happens if someone covers their ears?

3. Mesh Game: Everyone holds hands with at least two other people (making a web). Now try passing a message when one person “falls asleep.” Can the message still get through a different way?

Questions to think about:

• Which shape was fastest?
• Which one still worked when someone stopped playing?
• Which one needed the most “wires” (hand-holding)?

You just discovered why engineers choose different topologies for different jobs!

For Beginners: What is Network Topology?

Think of network topology like arranging furniture in a room—it’s about how things are connected and positioned.

Imagine you’re organizing a group project with your classmates. You could:

1. Star arrangement: Everyone sends their work to one team leader who coordinates everything (like a star with the leader in the center)
2. Ring arrangement: You pass notes around in a circle—Alice to Bob to Carol and back to Alice
3. Mesh arrangement: Everyone can talk directly to everyone else (like a group chat)
4. Bus arrangement: Everyone shares one whiteboard and takes turns writing on it

Each arrangement has trade-offs—just like network topologies!

Two ways to look at any network:

View	Question It Answers	Real-World Analogy
Physical Topology	“Where is everything located?”	A floor plan showing where desks are placed
Logical Topology	“How does information flow?”	An org chart showing who reports to whom

Why the difference matters: Your sensors might be scattered all over a building (physical), but they all send data to one central hub (logical star topology). The physical layout doesn’t have to match the logical pattern!

Key topology types at a glance:

Topology	Shape	Best For	Watch Out For
Star	Hub in center	Home networks, simple setups	Hub failure = network down
Ring	Circular chain	Industrial control systems	One break stops everything
Mesh	Everything connected	Smart homes with Zigbee	Complex, but very reliable
Bus	Shared line	Legacy systems, car networks	Collisions when busy

Pro tip: Most IoT systems use star (simple) or mesh (self-healing) topologies. You’ll rarely see bus or ring in modern IoT deployments.

For Beginners: Network Shapes - Like Road Layouts in Cities

Think of network topologies as different ways to design roads connecting neighborhoods in a city.

Just like city planners choose how to connect neighborhoods with roads, network engineers choose how to connect IoT devices. Each “road layout” has different costs, traffic patterns, and what happens when a road is blocked.

The Four Main “Road Layouts”:

3.2.4 Star = Hub-and-Spoke (Like an Airport)

All flights go through ONE central airport
San Francisco → Denver → New York
Los Angeles → Denver → Chicago

• Good: Easy to manage, central control
• Bad: If central hub fails, everything stops
• IoT Example: Wi-Fi router in your home - all devices connect to it

3.2.5 Mesh = Multiple Routes (Like City Streets)

Many ways to get from A to B:
Home → Main St → Oak Ave → Work  (usual route)
Home → Elm St → Park Rd → Work   (if Main St closed)
Home → Maple → Pine → Oak → Work (if both blocked)

• Good: If one path fails, use another - self-healing!
• Bad: More expensive (need many roads/connections)
• IoT Example: Zigbee smart lights - messages hop through nearest devices

3.2.6 Ring = Circular Highway (Like a Beltway)

Cities arranged in a circle:
City A → City B → City C → City D → back to City A

• Good: Fair - everyone gets equal access
• Bad: If one segment breaks, the whole circle fails
• IoT Example: Rarely used in modern IoT (legacy industrial systems)

3.2.7 Bus = Single Main Street (Like a Train Line)

All buildings on ONE main street:
Building 1 — Building 2 — Building 3 — Building 4
     ↓             ↓            ↓            ↓
Main Street (everyone shares this one road)

• Good: Cheap - only need one main cable
• Bad: If main street breaks, everyone disconnected
• IoT Example: Old Ethernet cables, car CAN bus

Quick Decision Guide:

Your Need	Choose This	Why
Simple home setup	Star (Wi-Fi)	Easy, cheap, one router
Reliable industrial system	Mesh (Zigbee)	Self-heals when devices fail
Large building complex	Tree (Star + layers)	Organized by floor/department
Maximum range outdoors	Star (LoRaWAN)	Long-range to central gateway

Real numbers:

• Star: 1 hub failure = 100% network down
• Mesh: Can survive 30-40% node failures (Zigbee)
• Ring: 1 link failure = 100% network down (unless dual-ring)
• Bus: Main cable failure = 100% network down

3.2.8 Basic Topology Types at a Glance

Four Basic Network Topology Types

Figure 3.1: Four Basic Network Topology Types

---

3.3 What is Network Topology?

Network topology is the arrangement of elements (nodes and links) in a communications network.

Network Topology: Physical vs Logical Views

Figure 3.2: Network Topology: Physical vs Logical Views

Two perspectives:

1. Physical topology: Where devices are actually located
2. Logical topology: How data flows between devices

Important: Physical and logical topologies are usually different for the same network!

Common Misconception: “Physical Layout Must Match Logical Topology”

The Mistake: Many IoT engineers assume that if devices are physically arranged in a line (e.g., sensors along a hallway), the network must use bus topology. Or if devices are in a circle, they need ring topology.

The Reality: Physical placement is independent from logical topology. This confusion causes real deployment failures.

Real-World Example with Numbers:

A smart building company deployed 50 temperature sensors in a 200-meter hallway (physical: linear arrangement). The engineer incorrectly chose bus topology to “match” the linear layout.

The Failure:

• Week 1: 15% packet loss due to signal reflections on the bus
• Week 2: One damaged sensor brought down the entire bus (50 sensors offline)
• Repair cost: $8,000 (technician had to trace the entire 200m bus cable to find the fault)
• Downtime: 14 hours (entire HVAC control system non-functional)

The Correct Solution:

After the failure, they switched to star topology (Wi-Fi mesh): - Each sensor connects to nearest access point (logical star) - Physical layout stayed the same (still in a hallway line) - Result: 99.7% uptime, 2-hour repair time for any single sensor failure (others stay online) - Cost savings: $12,000/year avoided downtime vs old bus system

Key Insight: Physical = “WHERE devices are located” (floor plan). Logical = “HOW data flows” (network diagram). Choose topology based on communication requirements (reliability, bandwidth, cost), NOT physical arrangement!

Quick Rule: If physical layout could work with bus but reliability matters, use star or mesh instead. Don’t let walls and hallways dictate your logical topology!

---

3.4 Physical vs Logical Topologies

3.4.1 Key Differences

Physical vs Logical Topology Comparison

Alternative View: Physical vs Logical - Smart Office Example

This variant shows the same network from both perspectives - a practical example where devices physically arranged in a line form a logical star topology.

Smart Office Physical vs Logical Topology

Key Takeaway: When designing IoT networks, always draw BOTH views. Physical views help installers find devices; logical views help engineers troubleshoot connectivity.

Aspect	Physical Topology	Logical Topology
Purpose	Show actual layout	Explain network operation
Shows	Locations, distances, cable runs	Connections, data flow
Scale	Drawn to scale	Not to scale
Details	Room dimensions, wall materials	Device types, IP addresses
Users	Installers, facility managers	Network engineers, troubleshooters
IoT Focus	Sensor/actuator placement	Communication protocols, data paths

3.4.2 Example: Same Network, Different Views

Physical Topology:

• Devices shown on office floor plan
• Cable bundles along walls
• Actual distances measured
• Wireless coverage areas marked

Logical Topology:

• Simplified symbols for devices
• Lines show connections (not cable routes)
• No physical distances
• Focus on which devices communicate

3.4.3 Failure Impact by Topology Type

Understanding how different topologies respond to component failures is critical for IoT system design:

Failure Impact Comparison Across Topology Types

Figure 3.3: Failure Impact Comparison Across Topology Types

---

3.5 Engineering Trade-offs

Tradeoff: Star vs Mesh Topology

Option A: Star Topology - Simple configuration, predictable latency, easy troubleshooting, lower device cost ($5-10 per node saved)

Option B: Mesh Topology - Self-healing capability, extended range via multi-hop, survives 30-40% node failures without network loss

Decision factors: Choose star for small deployments (<30 devices), cost-sensitive projects, or when skilled staff unavailable. Choose mesh when reliability is critical, coverage area exceeds single-hop range, or battery-powered sensors need low-power multi-hop routing. Hybrid approaches (Wi-Fi star for cameras + Zigbee mesh for sensors) often provide best balance.

Tradeoff: Physical Redundancy vs Protocol Redundancy

Option A: Physical Redundancy - Duplicate hardware (dual gateways, redundant cables), immediate failover, higher upfront cost but proven reliability

Option B: Protocol Redundancy - Mesh self-healing, AODV/RPL routing finds alternate paths, lower hardware cost but dependent on network density and algorithm convergence time

Decision factors: Mission-critical industrial systems (manufacturing lines, safety systems) should invest in physical redundancy with automatic failover. Cost-sensitive deployments can rely on mesh protocol redundancy if device density ensures 2-3 alternate paths exist. Consider geographic spread - wide-area deployments may need both approaches at different network tiers.

Tradeoff: Flat vs Hierarchical Topology

Option A: Flat Topology - All devices at same level, simpler addressing, works well for small networks, lower latency for local communication

Option B: Hierarchical (Tree) Topology - Organized by zones/floors/departments, scalable to thousands of devices, easier management but single points of failure at branch nodes

Decision factors: Use flat topology for single-room or small-building deployments with <50 devices. Use hierarchical when scaling beyond 100 devices, spanning multiple buildings, or requiring organizational segmentation (IT/OT separation, department isolation). Hierarchical enables aggregation and filtering at each tier, reducing backbone traffic.

3.5.1 Quick Topology Selection Guide

Topology Selection Decision Tree for IoT Deployments

Figure 3.4: Topology Selection Decision Tree for IoT Deployments

3.5.2 IoT Protocol to Topology Mapping

Different IoT protocols are designed for specific topologies. Understanding this mapping helps you choose the right technology for your deployment:

IoT Protocol to Topology Mapping

Figure 3.5: IoT Protocol to Topology Mapping

Protocol Category	Topology	Range	Best For
Wi-Fi	Star	30-50m indoor	High bandwidth, video streaming
LoRaWAN	Star-of-stars	2-15km	Low-power, wide-area sensing
Zigbee	Mesh	10-100m per hop	Battery-powered sensor networks
Thread	Mesh	10-30m per hop	IP-based smart home devices
Bluetooth Mesh	Mesh	10-30m per hop	Lighting control, beacons
Z-Wave	Mesh	30-100m per hop	Home automation, reliable
Matter	Multi-topology	Varies	Cross-protocol interoperability

---

3.6 Knowledge Checks

3.6.1 Check 1: Physical vs Logical Topology

3.6.2 Check 2: Fault Tolerance

3.6.3 Check 3: IoT Deployment Scenario

3.6.4 Check 4: Understanding Trade-offs

3.6.5 Check 5: Protocol and Topology Selection

---

Worked Example: Physical vs Logical Topology in Smart Building Deployment

Scenario: An IoT integrator is installing environmental sensors across a 5-floor office building. Understanding the difference between physical and logical topology is critical for installation planning and troubleshooting.

Building Layout:

• 5 floors, each 50m × 30m (1,500 m² per floor)
• 10 sensors per floor (50 total sensors)
• Central equipment room on 3rd floor

Physical Topology Design:

Floor 5:  [S1] [S2] [S3] ... [S10]  ~~ wireless ~~> [GATEWAY]
Floor 4:  [S1] [S2] [S3] ... [S10]  ~~ wireless ~~> [GATEWAY]
Floor 3:  [S1] [S2] [S3] ... [S10]  ~~ wireless ~~> [GATEWAY] (equipment room)
Floor 2:  [S1] [S2] [S3] ... [S10]  ~~ wireless ~~> [GATEWAY]
Floor 1:  [S1] [S2] [S3] ... [S10]  ~~ wireless ~~> [GATEWAY]

Physical Topology Characteristics:

• Devices physically arranged in grid pattern across each floor
• Gateway physically located in equipment room (3rd floor center)
• Vertical signal propagation through concrete floors
• Distances from gateway vary: 0-35m horizontal + 0-6m vertical

Logical Topology Design:

All 50 sensors use star topology - every sensor connects directly to the central gateway via Wi-Fi:

                    [GATEWAY]
                        |
         +--------------+----------+----------+
         ↓              ↓          ↓          ↓
    [Floor 1: S1-S10] [Floor 2: S1-S10] [Floor 3: S1-S10] ...

Why They Differ:

Aspect	Physical View	Logical View
Purpose	Where to install sensors for coverage	How sensors communicate
Drawn to Scale	Yes (shows 50m × 30m floor)	No (simplified diagram)
Shows Distance	Yes (15m between sensors)	No (all look equidistant)
Building Structure	Walls, floors, equipment room	Not shown
Used By	Installation team, RF engineer	Network engineer, troubleshooter

Installation Decision Using Physical Topology:

Putting Numbers to It

Let’s calculate the RF link budget to determine if sensors on all floors can reach the gateway.

Given: Gateway on Floor 3, \(P_{\text{tx}} = +20\) dBm transmit power, sensor sensitivity \(S_{\text{rx}} = -90\) dBm

Link budget: \[L_{\text{budget}} = P_{\text{tx}} - S_{\text{rx}} = 20 - (-90) = 110 \text{ dB}\]

Path loss components for Floor 5 sensor (2 floors away, 35m horizontal): \[L_{\text{floor}} = n_{\text{floors}} \times 15 \text{ dB/floor} = 2 \times 15 = 30 \text{ dB}\] \[L_{\text{free-space}} = 20\log_{10}(d) + 20\log_{10}(f) - 27.55 = 20\log_{10}(35) + 20\log_{10}(2400) - 27.55 \approx 71 \text{ dB}\] \[L_{\text{total}} = L_{\text{floor}} + L_{\text{free-space}} = 30 + 71 = 101 \text{ dB}\]

Margin: \[M = L_{\text{budget}} - L_{\text{total}} = 110 - 101 = 9 \text{ dB} \quad \text{(adequate; minimum 6 dB typically required)}\]

Result: All sensors within 2 floors and 35m have sufficient link margin (>6 dB minimum required for reliable Wi-Fi; 9 dB margin is acceptable for this application). For \(n = 50\) sensors, star topology requires 50 radio links; full mesh would need \(\frac{50 \times 49}{2} = 1{,}225\) links (impractical).

Troubleshooting Decision Using Logical Topology:

Network engineer sees Floor 5 sensors offline: - Logical topology shows: Floor 5 Sensor 3 → GATEWAY (star connection) - Debug steps: 1. Check gateway status (hub in star = single point of failure) 2. Check sensor 3 is powered 3. Verify sensor 3 can reach gateway (ping/trace) - Logical diagram doesn’t show physical obstruction (metal ductwork on Floor 4)

Key Lesson: Physical topology guided installation (gateway placement for RF coverage). Logical topology guides troubleshooting (verify star connection to gateway). Both views are essential and serve different purposes.

Deliverables for Client:

1. Physical diagram: Floor plans showing sensor locations with measurements
2. Logical diagram: Star topology showing all 50 sensors → gateway connectivity
3. Documentation: Mapping between physical (Floor X, Sensor Y) and logical (192.168.1.Z IP address)

3.7 How It Works: Network Topology in Action

To understand how topology works, let’s trace a message through different network configurations:

Star Topology Message Flow:

Sensor A wants to send data to Sensor B:

1. Sensor A → Gateway (TX)
   - A transmits packet destined for B
   - Gateway receives on Port 1

2. Gateway → Sensor B (RX)
   - Gateway checks address table: "B is on Port 5"
   - Gateway forwards packet to Port 5
   - B receives packet

Total hops: 2 (A → Gateway → B)
Latency: 20ms (10ms per hop)

Mesh Topology Message Flow:

Sensor A wants to send data to Sensor D:

1. Sensor A → Sensor B (direct neighbor)
   - A checks routing table: "D is 3 hops via B"
   - A transmits to B

2. Sensor B → Sensor C (relay)
   - B checks routing table: "D is 2 hops via C"
   - B forwards to C

3. Sensor C → Sensor D (final hop)
   - C checks routing table: "D is direct neighbor"
   - C forwards to D
   - D receives packet

Total hops: 3 (A → B → C → D)
Latency: 30ms (10ms per hop)

When a Node Fails (Mesh Self-Healing):

Same scenario, but Sensor B fails:

1. Sensor A attempts to send to B (times out)
2. A marks B as unreachable in routing table
3. A recalculates route: "D is 4 hops via E"
4. A → E → F → C → D (alternate path)

Self-healing time: 15-30 seconds
No manual intervention required

Key Insight: The topology determines BOTH the path (hops) AND what happens during failures.

3.8 Incremental Example: Smart Home Topology Evolution

Let’s build a smart home network step-by-step, showing how topology choice affects the design:

Stage 1: Just 3 Devices (Start Simple)

Devices: 1 smart bulb, 1 temperature sensor, 1 gateway

Topology choice: Star (simplest)
  [Smart Bulb] ───┐
                  ├──> [Gateway] → Internet → Cloud
  [Temp Sensor]──┘

Why it works:
- Only 3 devices, no range issues
- Bulb and sensor both within 10m of gateway
- Total cost: $150 (gateway $100, 2 devices $25 each)

Stage 2: Add 10 More Devices (Still Star)

Devices: 10 smart bulbs, 3 sensors, 1 gateway (14 total)

Topology: Extended star
  All 13 devices → [Gateway]

Limitation appears:
- Two bulbs in basement, 15m from gateway
- Signal strength marginal (-85 dBm, ~30% packet loss)
- Star can't solve this (no relay capability)

Stage 3: Need Range Extension (Switch to Mesh)

Devices: 10 bulbs, 3 sensors, 1 coordinator (becomes mesh)

Topology: Mesh with coordinator
  Basement bulbs → [Nearby router bulb] → [Coordinator]

How it changed:
- Smart bulbs become routers (relay for others)
- Basement bulbs now 2 hops from coordinator
- Range extended from 15m to 30m effectively

Trade-off:
- More complex (routing protocol overhead)
- Bulbs must stay powered (can't turn off at switch)
- But: network now covers whole house

Stage 4: High-Bandwidth Device (Hybrid Topology)

Devices: Add 1 security camera (needs 2 Mbps)

Problem: Mesh can't handle 2 Mbps (Zigbee max 250 kbps raw data rate)

Solution: Hybrid topology
  Camera → [Wi-Fi AP] → [Router] → Internet (star for camera)
  10 bulbs + 3 sensors → [Zigbee mesh] → [Coordinator] → Router
               (mesh for low-power devices)

Two separate networks:
- Wi-Fi star: High bandwidth, mains-powered devices
- Zigbee mesh: Low power, battery-capable devices

Key Lessons:

1. Start with simplest topology that works
2. Switch when you hit limitations (range, bandwidth, reliability)
3. Hybrid is common in real deployments (different devices have different needs)

Match: Topology Concepts

Order: Physical-to-Logical Topology Analysis

Common Pitfalls

1. Thinking Network Topology Is Only About Physical Cables

In IoT, most connections are wireless. Topology decisions are about RF link management and routing strategy, not just cable layout. Fix: always think in terms of logical connectivity, not physical cable runs.

2. Assuming Topology Is a One-Time Decision

Adding 50 more sensors to a star network designed for 20 nodes can overload the gateway. Fix: design topology with a documented growth plan and re-evaluate at each 2× node count increase.

3. Learning Topology in Isolation From Protocol Choice

Star topology is easy to implement with LoRaWAN, but mesh topology requires protocols that support multi-hop routing (Zigbee, Thread). Fix: always study topology and protocol together; they constrain each other.

Label the Diagram

Code Challenge

3.9 Summary

3.9.1 Key Concepts

• Network topology describes how devices are arranged and connected in a network
• Physical topology shows actual device locations, cable routes, and building layouts
• Logical topology illustrates how data flows between devices regardless of physical placement
• Physical and logical topologies are independent - a linear physical arrangement can use star logical topology
• Star, mesh, ring, bus, and tree are the main topology types
• Each topology has trade-offs between simplicity, reliability, cost, and scalability

3.9.2 Quick Reference: Topology Comparison

Topology	Single Point of Failure	Scalability	Cost	Best IoT Use Case
Star	Yes (hub)	Medium	Low	Smart home (Wi-Fi), LPWAN
Mesh	No (self-healing)	High	High	Industrial, smart buildings
Ring	Yes (any link)	Low	Medium	Legacy industrial (rare)
Bus	Yes (cable)	Low	Very Low	Vehicle networks (CAN bus)
Tree	Yes (per branch)	High	Medium	Multi-floor buildings
Hybrid	Varies	Very High	Varies	Large enterprise deployments

3.9.3 Decision Checklist

Use this checklist when selecting a topology for your IoT deployment:

• Scale: How many devices? (<30 = star, 30-100 = mesh, >100 = tree/hybrid)
• Reliability: Is self-healing required? (yes = mesh)
• Coverage: Single building or multiple? (multiple = tree/hybrid)
• Power: Battery-powered sensors? (star with LPWAN for sleep efficiency)
• Latency: Real-time requirements? (star for predictable latency)
• Budget: Cost constraints? (star < tree < mesh)

3.10 Concept Relationships

Foundation Concepts:

• Networking Basics - Switches vs hubs determines whether physical star is also logical star
• Layered Network Models - Physical topology (Layer 1) can differ from logical topology (Layer 2-3)

Related Concepts:

• Network Mechanisms - Circuit switching (ring) vs packet switching (star/mesh)
• Routing Fundamentals - Topology determines routing protocol choice

Advanced Applications:

• Wireless Sensor Networks - WSNs typically use clustered mesh topologies
• Edge Computing - Edge deployments often use hierarchical tree topologies

Real Implementations:

• Zigbee Architecture - Implements self-forming mesh topology
• LoRaWAN Architecture - Uses star-of-stars for wide-area coverage
• Thread Operation - Mesh with border routers creating tree structure

3.11 See Also

Visual Learning:

• Topology Visualizer - Interactive tool to explore topology types
• Simulations Hub - Network topology simulation tools

Design Guidance:

• Topology Selection - Framework for choosing appropriate topology
• Network Design - Complete network design methodology

Hands-On:

• Topology Lab - Build and compare topologies with ESP32 simulation

3.12 Try It Yourself

Exercise 1: Map Your Home Network

Draw both topologies for your current home network: 1. Physical topology: Where are devices located? Draw floor plan. 2. Logical topology: How do they connect? (All to router = star? Mesh Wi-Fi = mesh?)

Expected finding: Physical is spatially distributed, logical is usually star (all → router).

Exercise 2: Failure Test

If you have a mesh network (Wi-Fi mesh, Zigbee smart home): 1. Unplug one mesh node 2. Observe: Do other devices lose connection? 3. If not: You’ve witnessed self-healing! Time how long it takes to reroute.

Expected: 10-60 seconds for automatic recovery (mesh advantage over star).

Exercise 3: Topology Comparison

Calculate for a hypothetical 10-device network: 1. Star: How many links? (Hint: 10) 2. Full mesh: How many links? (Hint: n(n-1)/2 = 45) 3. Partial mesh (40%): How many links? (Hint: 45 × 0.4 = 18)

Question: Which is most cost-effective for home use? Why?

Try It: Topology Link Count Calculator

Adjust the device count to compare the number of links required for each topology type.

viewof numDevices = Inputs.range([2, 50], {
  value: 10,
  step: 1,
  label: "Number of Devices (n)"
})

{
  const n = numDevices;
  const starLinks = n;
  const fullMeshLinks = (n * (n - 1)) / 2;
  const partialMesh40 = Math.round(fullMeshLinks * 0.4);
  const ringLinks = n;
  const busLinks = n - 1;

  const data = [
    { topology: "Star", links: starLinks, spof: "Yes (hub)", scalability: "Medium", cost: "$" },
    { topology: "Full Mesh", links: fullMeshLinks, spof: "No", scalability: "High", cost: "$$$$" },
    { topology: "Partial Mesh (40%)", links: partialMesh40, spof: "Reduced", scalability: "High", cost: "$$$" },
    { topology: "Ring", links: ringLinks, spof: "Yes (any link)", scalability: "Low", cost: "$$" },
    { topology: "Bus", links: busLinks, spof: "Yes (cable)", scalability: "Low", cost: "$" }
  ];

  return html`
    <div style="font-family: Arial, sans-serif; margin-top: 12px;">
      <p style="color: #2C3E50; font-weight: bold; margin-bottom: 8px;">
        With <strong>${n}</strong> devices:
      </p>
      <table style="width:100%; border-collapse: collapse; font-size: 0.9em;">
        <thead>
          <tr style="background: #2C3E50; color: white;">
            <th style="padding: 8px; text-align: left;">Topology</th>
            <th style="padding: 8px; text-align: right;">Links Required</th>
            <th style="padding: 8px; text-align: center;">Single Point of Failure</th>
            <th style="padding: 8px; text-align: center;">Relative Cost</th>
          </tr>
        </thead>
        <tbody>
          ${data.map((row, i) => html`
            <tr style="background: ${i % 2 === 0 ? '#f8f9fa' : 'white'}; border-bottom: 1px solid #dee2e6;">
              <td style="padding: 8px; font-weight: bold; color: #16A085;">${row.topology}</td>
              <td style="padding: 8px; text-align: right; color: #E67E22; font-weight: bold;">${row.links}</td>
              <td style="padding: 8px; text-align: center;">${row.spof}</td>
              <td style="padding: 8px; text-align: center;">${row.cost}</td>
            </tr>
          `)}
        </tbody>
      </table>
      <p style="margin-top: 10px; color: #7F8C8D; font-size: 0.85em;">
        Full mesh grows as n(n-1)/2. At ${n} devices, full mesh requires
        <strong>${fullMeshLinks}</strong> links vs <strong>${starLinks}</strong> for star
        — a <strong>${fullMeshLinks > starLinks ? (fullMeshLinks / starLinks).toFixed(1) + "x" : "1x"}</strong> increase.
      </p>
    </div>
  `;
}

Try It: Mesh vs Star Coverage Area Estimator

Estimate how topology choice affects the coverage area your network can serve.

viewof singleHopRange = Inputs.range([5, 150], {
  value: 30,
  step: 5,
  label: "Single-hop radio range (meters)"
})

viewof maxHops = Inputs.range([1, 8], {
  value: 3,
  step: 1,
  label: "Maximum mesh hops allowed"
})

{
  const r = singleHopRange;
  const hops = maxHops;
  const starArea = Math.PI * r * r;
  const meshLinearReach = r * hops;
  const meshArea = Math.PI * meshLinearReach * meshLinearReach;
  const areaRatio = (meshArea / starArea).toFixed(1);

  const fmt = (v) => v >= 1e6
    ? (v / 1e6).toFixed(2) + " km²"
    : v >= 10000
    ? (v / 10000).toFixed(2) + " ha"
    : v.toFixed(0) + " m²";

  return html`
    <div style="font-family: Arial, sans-serif; margin-top: 12px;">
      <div style="display: grid; grid-template-columns: 1fr 1fr; gap: 12px; margin-bottom: 12px;">
        <div style="background: #EBF5FB; border-left: 4px solid #3498DB; padding: 12px; border-radius: 4px;">
          <div style="color: #2C3E50; font-weight: bold; margin-bottom: 4px;">Star Topology</div>
          <div style="font-size: 1.4em; color: #3498DB; font-weight: bold;">${fmt(starArea)}</div>
          <div style="color: #7F8C8D; font-size: 0.85em;">radius: ${r}m, 1 hop</div>
        </div>
        <div style="background: #E9F7EF; border-left: 4px solid #16A085; padding: 12px; border-radius: 4px;">
          <div style="color: #2C3E50; font-weight: bold; margin-bottom: 4px;">Mesh Topology (${hops} hops)</div>
          <div style="font-size: 1.4em; color: #16A085; font-weight: bold;">${fmt(meshArea)}</div>
          <div style="color: #7F8C8D; font-size: 0.85em;">reach: ${meshLinearReach}m</div>
        </div>
      </div>
      <p style="color: #E67E22; font-weight: bold; margin: 0;">
        Mesh extends coverage by <strong>${areaRatio}x</strong> over star (${hops} hops × ${r}m per hop).
      </p>
      <p style="color: #7F8C8D; font-size: 0.85em; margin-top: 6px;">
        Note: Real-world coverage depends on obstacles, interference, and node placement density.
      </p>
    </div>
  `;
}

3.13 What’s Next

If you want to…	Read this
Study fundamental topology concepts	Topology Fundamentals
Learn the four basic topology types	Basic Types
Understand how topologies are analysed	Topology Analysis
Learn how to select the right topology	Topology Selection
Go to the module overview	Topologies Overview

3.14 Related Chapters

Deep Dives:

• Topologies Types - Detailed topology type characteristics
• Topologies Selection - Decision framework for choosing topologies
• Topologies Labs and Design - Hands-on topology design and simulation

Network Architecture:

• Wireless Sensor Networks - WSN topology patterns and deployment
• Mesh Network Architectures - Ad-hoc and self-organizing topologies

Technology-Specific Topologies:

• Zigbee Architecture - Mesh networking in Zigbee
• Thread Operation and Implementation - Thread mesh topology
• Wi-Fi Architecture and Mesh - Wi-Fi mesh networking
• LoRaWAN Architecture - Star-of-stars LPWAN topology