5  Network Topologies: Core Concepts

Key Concepts

• Physical Topology: How devices are physically connected by cables or radio links in the real world
• Logical Topology: How data actually flows between devices, which may differ from the physical layout
• Node: Any device in a network — sensor, gateway, router, or server
• Link: A communication path between two nodes, either wired or wireless
• Hop: A single link traversal; multi-hop networks forward data through intermediate nodes to reach the destination
• Broadcast Domain: The set of nodes that receive a broadcast frame; topology choice affects broadcast domain boundaries
• Network Density: The ratio of actual connections to the maximum possible connections; higher density improves resilience but raises cost

5.1 In 60 Seconds

Network topology describes how devices are physically wired and logically connected – and these can differ. A star topology physically connects all devices to a central hub but may logically operate as a bus. Understanding both physical and logical topology is critical for IoT because it determines fault tolerance, scalability, cost, and which protocols (Wi-Fi, Zigbee, LoRaWAN) best fit your deployment.

5.2 Learning Objectives

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

• Differentiate Physical and Logical Topologies: Explain why the same network can have different physical and logical representations
• Classify Topology Types: Categorize star, bus, ring, and mesh configurations by their structural properties
• Interpret Network Diagrams: Decode logical topology symbols and connection conventions accurately
• Design IoT Networks: Apply topology principles to architect IoT deployments meeting specific requirements
• Create Network Documentation: Produce physical and logical network diagrams for real deployments
• Justify Topology Selection: Defend topology choices based on IoT application constraints and trade-offs

5.3 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.

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!

5.3.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!”

5.3.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

5.3.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”:

5.3.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

5.3.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

5.3.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)

Ring Topology

Figure 5.1: Ring topology with circular data flow pattern

5.3.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

---

5.4 What is Network Topology?

Time: ~10 min | Level: Foundational

5.4.1 Definition

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

Figure 5.2: Topology concepts: physical layout vs logical connections

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!

---

5.5 Physical vs Logical Topologies

Time: ~12 min | Level: Intermediate

5.5.1 Key Differences

Figure 5.3: Physical (floor plans) vs logical (data flow) perspectives

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.

Figure 5.4: Physical: Linear arrangement along hallway. Logical: All sensors connect to central hub (star topology). The physical layout does NOT dictate the 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

5.5.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

---

5.6 Engineering Tradeoffs

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.

---

5.7 Decision Framework: Topology Selection for IoT Deployments

Selecting the right network topology requires balancing reliability, cost, complexity, and scalability. This quantitative framework provides concrete decision criteria based on real deployment data from industrial IoT projects.

Putting Numbers to It

Let’s calculate the total cost of ownership for star vs mesh topologies in a 400-device warehouse deployment.

Given: \(N = 400\) devices, star AP capacity \(C_{\text{AP}} = 50\) devices/AP

Star topology costs: \[\text{APs needed} = \left\lceil\frac{N}{C_{\text{AP}}}\right\rceil = \left\lceil\frac{400}{50}\right\rceil = 8 \text{ APs}\] \[C_{\text{star}} = N \times \$10 + 8 \times \$800 = \$4{,}000 + \$6{,}400 = \$10{,}400\]

Mesh topology costs: \[C_{\text{mesh}} = N \times (\$10 + \$8) = 400 \times \$18 = \$7{,}200\]

Cost savings: \(C_{\text{star}} - C_{\text{mesh}} = \$10{,}400 - \$7{,}200 = \$3{,}200\) (mesh saves 31%)

Reliability impact: If star APs have 97% uptime (maintenance windows), expected annual downtime per zone \(= 365 \times 24 \times 0.03 = 263\) hours. Mesh with 99.7% uptime \(= 26\) hours downtime. Downtime cost at \(\$250\)/hour (lost productivity) \(= (263-26) \times \$250 = \$59{,}250\) annual savings. Mesh pays for itself in under 20 days (\(\$3{,}200 \div (\$59{,}250/365) \approx 19.7\) days).

Try It: Topology Cost Calculator

viewof numDevices = Inputs.range([10, 1000], {value: 400, step: 10, label: "Number of IoT devices (N)"})
viewof apCapacity = Inputs.range([10, 100], {value: 50, step: 5, label: "Devices per AP (star topology)"})
viewof apCost = Inputs.range([100, 2000], {value: 800, step: 50, label: "Cost per AP ($)"})
viewof baseNodeCost = Inputs.range([1, 30], {value: 10, step: 1, label: "Base node cost (radio, $)"})
viewof meshExtra = Inputs.range([1, 30], {value: 8, step: 1, label: "Extra cost for mesh routing firmware per node ($)"})
viewof downtimeCostPerHr = Inputs.range([10, 1000], {value: 250, step: 10, label: "Downtime cost per hour ($)"})
viewof starUptime = Inputs.range([90, 99.9], {value: 97, step: 0.1, label: "Star AP uptime (%)"})
viewof meshUptime = Inputs.range([90, 99.9], {value: 99.7, step: 0.1, label: "Mesh network uptime (%)"})

{
  const apsNeeded = Math.ceil(numDevices / apCapacity);
  const starCost = numDevices * baseNodeCost + apsNeeded * apCost;
  const meshCost = numDevices * (baseNodeCost + meshExtra);
  const costDiff = starCost - meshCost;
  const savingsPct = Math.abs(costDiff / Math.max(starCost, meshCost) * 100).toFixed(1);

  const annualHrs = 365 * 24;
  const starDowntime = annualHrs * (1 - starUptime / 100);
  const meshDowntime = annualHrs * (1 - meshUptime / 100);
  const annualSavings = (starDowntime - meshDowntime) * downtimeCostPerHr;
  const paybackDays = costDiff > 0 && annualSavings > 0
    ? (costDiff / (annualSavings / 365)).toFixed(1)
    : "N/A";

  return html`
    <div style="display:grid;grid-template-columns:1fr 1fr;gap:16px;margin-top:12px">
      <div style="background:#f0f7f4;border-left:4px solid #16A085;padding:12px;border-radius:4px">
        <div style="font-weight:bold;color:#2C3E50;margin-bottom:8px">Star Topology</div>
        <div>APs required: <strong>${apsNeeded}</strong></div>
        <div>Infrastructure: <strong>$${(apsNeeded * apCost).toLocaleString()}</strong></div>
        <div>Node cost: <strong>$${(numDevices * baseNodeCost).toLocaleString()}</strong></div>
        <div style="font-weight:bold;color:#E67E22">Total: $${starCost.toLocaleString()}</div>
        <div style="margin-top:8px">Annual downtime: <strong>${starDowntime.toFixed(0)} hrs/yr</strong></div>
      </div>
      <div style="background:#f0f4f7;border-left:4px solid #3498DB;padding:12px;border-radius:4px">
        <div style="font-weight:bold;color:#2C3E50;margin-bottom:8px">Mesh Topology</div>
        <div>No central APs needed</div>
        <div>Infrastructure: <strong>$0</strong></div>
        <div>Node cost (w/ routing): <strong>$${(numDevices * (baseNodeCost + meshExtra)).toLocaleString()}</strong></div>
        <div style="font-weight:bold;color:#E67E22">Total: $${meshCost.toLocaleString()}</div>
        <div style="margin-top:8px">Annual downtime: <strong>${meshDowntime.toFixed(0)} hrs/yr</strong></div>
      </div>
    </div>
    <div style="background:#fff8e1;border:1px solid #E67E22;padding:12px;border-radius:4px;margin-top:12px">
      <strong style="color:#2C3E50">Analysis:</strong>
      ${costDiff > 0
        ? html`<span style="color:#16A085"> Mesh saves <strong>$${Math.abs(costDiff).toLocaleString()}</strong> upfront (${savingsPct}% cheaper).</span>`
        : html`<span style="color:#3498DB"> Star saves <strong>$${Math.abs(costDiff).toLocaleString()}</strong> upfront (${savingsPct}% cheaper).</span>`
      }
      ${annualSavings > 0
        ? html`<span> Reliability savings: <strong>$${annualSavings.toLocaleString(undefined, {maximumFractionDigits:0})}/year</strong>. ${paybackDays !== "N/A" ? html`Mesh pays for itself in <strong>${paybackDays} days</strong>.` : ""}</span>`
        : html`<span style="color:#7F8C8D"> At these uptime levels, star has lower annual downtime cost.</span>`
      }
    </div>
  `;
}

Decision Criterion	Star	Mesh	Tree (Hierarchical)	Ring
Setup cost per node	$5-15 (radio only)	$15-30 (routing firmware)	$10-20 (tiered radios)	$10-15 (dual interface)
Infrastructure cost	High (central hub required)	Low (peer-to-peer)	Medium (branch nodes)	Low (loop cabling)
Max nodes per network	100-8,000 (AP dependent)	30-250 (routing table limits)	1,000-50,000 (tiered)	10-100 (token passing)
Fault tolerance	0% (hub failure = total loss)	30-40% node loss tolerated	Branch-level isolation	0% (single break = total loss)
Latency (10 hops)	1 hop always (<10 ms)	5-10 hops (50-200 ms)	2-4 hops (20-80 ms)	5 hops average (50-100 ms)
Power per node	Low (single TX)	High (routing + forwarding)	Medium (tier-dependent)	Medium (token management)
Self-healing	No	Yes (automatic rerouting)	Partial (within branches)	No (unless dual-ring)

When to use each topology:

• Star: Best for cost-sensitive deployments where a reliable central gateway exists. Examples: LoRaWAN sensor networks, Wi-Fi smart buildings, single-room automation. Choose when: budget is tight, latency must be predictable, and you can afford gateway redundancy ($500-2,000 for failover).

• Mesh: Best when reliability outweighs cost and devices are dense enough to maintain 2-3 alternate paths. Examples: Zigbee smart lighting (100+ bulbs per floor), Thread home automation, industrial monitoring in hazardous areas where technician access is limited. Choose when: downtime cost exceeds $100/hour and device density provides path redundancy.

• Tree (Hierarchical): Best for large-scale multi-building or multi-floor deployments. Examples: campus-wide BMS (Building Management Systems), smart city districts, multi-floor office IoT. Choose when: device count exceeds 500, geographic span exceeds single-hop range, and organizational boundaries (floors, buildings) naturally map to hierarchy levels.

• Ring: Rarely used in modern IoT. Legacy industrial control systems (PROFIBUS, HART) still use token-ring variants. Choose only when: deterministic latency is required and existing ring infrastructure is already installed.

Real deployment example: A warehouse logistics company compared star (Wi-Fi) vs mesh (Zigbee) for 400 asset tracking tags across a 50,000 m² facility. Star topology required 8 access points (at 50 devices/AP capacity) at $800 each ($6,400 infrastructure) with single-point-of-failure risk per zone. Mesh required 400 Zigbee radios at $8 extra per tag ($3,200 total) with self-healing capability. They chose mesh – the $3,200 infrastructure savings paid for itself quickly, and the 99.7% uptime (vs 97% with star during AP maintenance windows) eliminated 18 lost-asset incidents per month worth $4,500 in delayed shipments.

---

Match: Network Example to Topology Type

Order: Steps to Design an IoT Network Topology

Common Pitfalls

1. Confusing Physical and Logical Topology

A wireless mesh network has a star physical layout (all devices radiate from a central area) but a mesh logical topology (data routes through multiple hops). Fix: always specify whether you mean physical or logical topology when discussing network design.

2. Assuming Every Node Is Identical in Capability

IoT networks mix battery-powered end devices, mains-powered routers, and gateways. Applying the same topology rules to all node types leads to misconfigured networks. Fix: classify nodes by capability before assigning topology roles.

3. Ignoring the Impact of Topology on Address Space Requirements

A flat star topology with 1,000 nodes requires a /22 subnet. A hierarchical tree topology can reuse addresses across branches. Fix: plan the addressing scheme alongside the topology design.

Label the Diagram

Code Challenge

5.8 Summary

• Network topology is the arrangement of nodes and links in a communications network
• Physical topology shows actual device locations, cable routes, and building layouts
• Logical topology illustrates data flow patterns and connection relationships
• Physical and logical topologies are often different for the same network
• Choose topology based on communication requirements, not physical arrangement

5.9 Knowledge Check

Quiz: Core Topology Concepts

5.10 How It Works: Physical and Logical Topologies in Practice

Understanding how physical and logical topologies differ requires seeing how real networks implement both layers:

Layer 1: Physical Topology Implementation

Consider a smart building with 50 temperature sensors arranged in a grid pattern across floors 1-5:

Physical Layout (Floor 3):
[S31] [S32] [S33] [S34] [S35]  (5 sensors across hallway)
  |     |     |     |     |
 Wi-Fi signals propagate to AP in center of floor
  |     |     |     |     |
[AP3] (Access Point 3, mounted on ceiling)

The physical topology is distributed grid - sensors are spatially separated for coverage. But they don’t cable to each other physically.

Layer 2/3: Logical Topology Implementation

The same 50 sensors form a logical star topology:

Logical Data Flow:
All 50 sensors → [AP3] → [Switch] → [Gateway] → [Cloud]

Each sensor maintains:
- Association table: AP3 (BSSID: AA:BB:CC:DD:EE:FF)
- Routing table: Default gateway via AP3
- No peer-to-peer connections to other sensors

Why They Differ:

• Physical: Optimized for RF coverage - grid placement ensures no dead zones
• Logical: Optimized for data flow - star minimizes hops and simplifies routing

Real-World Consequences:

When troubleshooting, you need BOTH views: - Physical diagram: Helps find why Sensor 34 has weak signal (it’s 15m from AP, beyond wall) - Logical diagram: Helps find why Sensor 34 can’t reach cloud (AP3’s uplink to switch is down)

5.11 Incremental Example: Building a Multi-Floor Sensor Network

Let’s design a network step-by-step, showing how physical and logical topologies evolve:

Step 1: Single Room (10 Sensors)

Physical topology: 10 sensors distributed across room Logical topology: Star (all → 1 AP) Why it works: Direct line-of-sight, simple management

Step 2: Add Second Room (20 Sensors Total)

Physical topology: Now 2 rooms, sensors distributed Logical topology: Still star? Or two stars?

Decision: Add second AP → Two-star with shared uplink

Logical evolution:
Room 1: 10 sensors → [AP1] ─┐
                              ├→ [Switch] → Gateway
Room 2: 10 sensors → [AP2] ─┘

Step 3: Add Second Floor (40 Sensors Total)

Physical topology: 2 floors × 2 rooms × 10 sensors Logical topology: Tree topology emerges

              [Core Switch]
                    |
        ┌───────────┴───────────┐
    [Floor 1 Switch]      [Floor 2 Switch]
        |       |             |       |
      [AP1]   [AP2]         [AP3]   [AP4]

Notice: Physical grid distribution (sensors spread for coverage) but logical tree hierarchy (switches aggregate traffic).

Step 4: Scale to 50 Floors (2,000 Sensors)

Now the mismatch between physical and logical becomes critical:

Physical: 50 floors × 4 rooms/floor × 10 sensors = 2,000 sensors distributed vertically and horizontally Logical: Hierarchical tree with 3 tiers (Core → Floor Switches → APs)

If you designed logical topology to match physical topology (e.g., daisy-chain floors), you’d get:

• 50-hop maximum path (Floor 1 sensor → Floor 50 core)
• 500ms+ latency (10ms/hop × 50)
• UNACCEPTABLE for real-time control

Key Lesson: Physical topology follows building structure (floors, rooms). Logical topology follows traffic patterns (aggregation, hierarchy). They SHOULD differ.

Related Topics

Foundation Concepts:

• Networking Basics - Understanding hubs vs switches explains why physical star can be logical bus (hub) or logical star (switch)
• Layered Network Models - Physical topology maps to Layer 1, logical topology maps to Layer 2-3 operations
• Network Mechanisms - Circuit switching vs packet switching affects whether physical layout matters
• Routing Fundamentals - Logical topology determines routing table structure
• Design Implications - How topology affects system design
• Network Traffic Analysis - Topology impact on traffic patterns

Deep Dives in This Module:

• Topologies Labs and Design - Hands-on topology design and simulation; drawing exercises for floor plans (physical) and network diagrams (logical)
• Topologies Comprehensive Review - Complete topology coverage with implementation examples
• RPL Fundamentals - Routing for low-power lossy networks
• Routing Labs and Quiz - Practical routing implementation

Technology-Specific Topologies:

• Zigbee Architecture - Physical mesh grid but logical tree DODAG for routing
• Thread Operation and Implementation - Physical mesh with logical RPL DODAG
• Wi-Fi Architecture and Mesh - Wi-Fi mesh networking
• LoRaWAN Architecture - Physical: sensors scattered across city; Logical: pure star to gateways

Advanced Applications:

• Wireless Sensor Networks - WSN physical placement (for coverage) often differs dramatically from logical clustering (for data aggregation)
• Mesh Network Architectures - Ad-hoc and self-organizing topologies
• Software-Defined Networking - SDN completely decouples logical topology from physical infrastructure
• Network Design and Simulation - How to document both physical and logical topologies

Common Mistakes:

• Knowledge Gaps Hub - “Physical layout must match logical topology” is the #1 beginner misconception

5.12 Try It Yourself

Exercise 1: Identify Physical vs Logical

Examine your home Wi-Fi network: 1. Draw physical topology: Where is router, where are devices located? 2. Draw logical topology: How do devices communicate? 3. Are they the same or different? Why?

Expected observation: Physical is spatially distributed (devices in different rooms), logical is star (all → router).

Exercise 2: Redesign for Reliability

Given: Office with 20 computers in a line along a hallway, currently using star topology with AP at one end.

Problem: Computers at far end (18m away) have weak signal.

Task: Redesign physical topology (add second AP) while maintaining logical star topology.

Solution approach: - Physical: Add AP in middle of hallway (9m from each end) - Logical: Both APs connect to same switch → still star topology

Exercise 3: Topology Mismatch Diagnosis

Scenario: Factory floor has 30 sensors arranged in physical ring around conveyor belt. Engineer configures them in logical ring topology “to match the physical layout.”

Result: Network fails when one sensor loses power (entire ring breaks).

Task: Explain why matching physical to logical was wrong. What logical topology should be used instead?

Answer: Physical ring is just sensor placement for coverage. Logical topology should be star or mesh for fault tolerance, NOT ring.

5.13 What’s Next

Direction	Chapter	Focus
Next	Basic Topology Types	Star, bus, ring, mesh with detailed characteristics and IoT use cases
Previous	Networking Basics	Fundamental networking concepts and devices
Related	Topology Failures	What happens when topologies break