2  Network Topologies

Key Concepts
  • Network Topology: The pattern or arrangement of nodes and connections in a network, determining how devices communicate with each other
  • Star Topology: All devices connect to a central hub; simple and cheap but hub is a single point of failure
  • Mesh Topology: Devices connect to multiple neighbours; self-healing and resilient but requires routing protocols
  • Hybrid Topology: A combination of two or more basic topology types to balance cost, reliability, and scalability
  • Graph Theory: The mathematical framework used to analyse topology properties such as diameter, connectivity, and path length
  • Fault Tolerance: The ability of a network to continue operating when one or more components fail
  • Protocol-Topology Alignment: The matching of a wireless protocol (Zigbee, LoRaWAN, Thread) to the topology it natively supports

2.1 In 60 Seconds

Network topology defines how IoT devices are physically cabled and logically connected. The four fundamental types – star (central hub, simple but single point of failure), bus (shared medium, cheap but collision-prone), ring (sequential, deterministic but fragile), and mesh (redundant paths, resilient but complex) – combine into hybrid designs for real deployments. IoT commonly uses star-of-stars (Wi-Fi APs to router) and mesh (Zigbee, Thread) topologies, selected based on reliability, scalability, and power requirements.

2.2 Learning Objectives

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

  • Distinguish Physical from Logical Topologies: Contrast physical device placement with logical data flow in any network
  • Classify Topology Types: Categorize star, bus, ring, and mesh configurations by their structural properties
  • Interpret Network Diagrams: Analyse logical topology symbols and hierarchical layout conventions
  • Design IoT Networks: Construct topology plans that meet specific reliability, cost, and scalability targets
  • Produce Network Documentation: Create physical and logical network diagrams following industry standards
  • Evaluate and Select Topologies: Justify topology choices based on quantified application requirements

A network topology describes how devices are connected to each other. Think of it as a map: some networks look like a wheel with spokes (star), others like a grid of interconnected streets (mesh), and others like a family tree (tree topology). The shape you choose affects everything from reliability to cost.

“How we are all connected matters more than you might think,” said Max the Microcontroller. “The topology – the shape of our network – determines how fast messages travel, what happens when a device breaks, and how much the whole system costs.”

“I am part of a star network,” said Sammy the Sensor. “All of us connect to one central gateway, like spokes on a wheel. It is simple and works great, but if that gateway fails, we all go dark.”

“I am in a Zigbee mesh,” said Lila the LED. “We connect to each other, not just to a central hub. If one path breaks, data finds another way. It is more resilient but also more complex to manage.”

“This chapter covers ALL the topology types and helps you choose the right one,” said Bella the Battery. “Star for simplicity, mesh for resilience, tree for scalability, and hybrid designs that combine the best features. Every IoT deployment starts with a topology decision – get it right, and everything else falls into place!”

Chapter Overview

This chapter provides a comprehensive guide to network topologies for IoT systems. The content is organized into focused sections for easier navigation and learning.

Chapter Sections:

  1. Basic Topology Types - Fundamental topology concepts, the four basic topologies (star, bus, ring, mesh), visual guides, and comparison tables

  2. Topology Analysis - Graph theory metrics, failure analysis, routing overhead calculations, and real-world protocol examples

  3. Communication Patterns - Data flow patterns (unicast, broadcast, multicast, many-to-one), addressing schemes, and protocol mapping

  4. Hybrid Design Patterns - Real-world hybrid topologies, design patterns, cost-benefit analysis, and deployment guidelines

  5. Topologies Fundamentals - Physical vs logical topologies, detailed topology characteristics and variations

  6. Topologies Labs - Design exercises and documentation practice

  7. Topologies Review - Advanced concepts and assessment

2.3 Prerequisites

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

  • Networking Basics: Understanding fundamental networking concepts including switches, routers, hubs, and basic network design principles
  • Layered Network Models: Knowledge of the OSI and TCP/IP models helps explain why physical and logical topologies can differ
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.

Key Takeaway

In one sentence: Your network topology determines fault tolerance, latency, and scalability - star is simple but has a single point of failure, mesh is resilient but complex.

Remember this: Start with star topology for simple deployments (easy to manage), but plan for mesh when reliability matters more than simplicity.

2.4 Quick Reference: The Four Basic Topologies

Topology Structure Pros Cons IoT Examples
Star Central hub Easy management Single point of failure Wi-Fi, LoRaWAN
Bus Shared backbone Low cost Limited scalability Industrial fieldbus
Ring Circular chain Deterministic timing Single break disrupts BACnet MS/TP
Mesh Multiple paths Fault-tolerant Complex routing Zigbee, Thread

Real-world IoT deployments typically use hybrid topologies combining multiple types to optimize for different device requirements.

Topology Metrics Comparison for 10-Node Network

Compare star, ring, and full mesh topologies quantitatively:

Star topology (1 hub + 10 devices): \[ \text{Links} = n = 10 \] \[ \text{Max hops} = 2 \text{ (device → hub → device)} \] \[ \text{Avg path length} = 2 \text{ hops (all leaf-to-leaf paths pass through the hub)} \]

Ring topology (10 nodes): \[ \text{Links} = n = 10 \] \[ \text{Network diameter} = \lfloor n/2 \rfloor = 5 \text{ hops (worst case)} \] \[ \text{Avg path length} = \frac{n^2}{4(n-1)} = \frac{100}{36} \approx 2.78 \text{ hops} \]

Full mesh topology (10 nodes): \[ \text{Links} = \frac{n(n-1)}{2} = \frac{10 \times 9}{2} = 45 \] \[ \text{Network diameter} = 1 \text{ hop (direct connections)} \] \[ \text{Link cost ratio vs star} = \frac{45}{10} = 4.5\times \text{ more expensive} \]

Key insight: Star and ring both use 10 links, but star’s average path length is exactly 2 hops (all traffic through hub) versus ring’s ≈2.78 hops average. Mesh minimizes diameter to 1 hop (direct connections) but costs 4.5× more links (45 vs 10). For IoT: star trades centralization for simplicity, mesh trades hardware cost for resilience.

Try It: Topology Metrics Calculator

2.5 Chapter Navigation

Recommended Learning Path

Beginners: Start with Basic Topology Types for fundamental concepts and visual guides.

Intermediate: Continue to Topology Analysis for quantitative metrics and Communication Patterns for data flow understanding.

Advanced: Explore Hybrid Design Patterns for real-world deployment strategies and cost-benefit analysis.

Hands-On: Apply knowledge in Topologies Labs with design exercises.

Routing:

Mesh Networking:

IoT Protocols:

Learning:

2.6 Knowledge Check

Hybrid topologies combine two or more basic topologies to balance competing requirements. Use this framework to determine when hybrid makes sense versus pure topology:

Criterion Use Pure Topology Use Hybrid Topology Reasoning
Deployment Scale < 50 devices > 100 devices Hybrid adds complexity; only justified for large scale
Geographic Spread Single location (< 100m radius) Multiple buildings or campuses Pure star/mesh works for single location; hybrid needed for wide area
Device Types Homogeneous (all same protocol) Heterogeneous (Wi-Fi + Zigbee + LoRa) Hybrid naturally segments protocols with gateways
Bandwidth Needs Uniform (all low or all high) Mixed (cameras + sensors) Hybrid uses star for high-bandwidth, mesh for low
Reliability Tier Same requirement everywhere Critical + non-critical zones Hybrid provides mesh for critical areas, star for non-critical
Budget Constraint Tight budget, minimize cost Moderate budget, optimize value Pure star minimizes cost; hybrid balances cost vs features
Future Expansion No growth planned 2x growth expected in 2 years Hybrid tree backbone scales without redesign

Common Hybrid Patterns:

2.6.1 Pattern 1: Tree Backbone + Mesh Access (Most Common)

  • Use when: Large building, campus, or city deployment
  • Structure: Wired/fiber tree connects buildings/zones; wireless mesh within each zone
  • Example: University campus with Ethernet backbone and Zigbee mesh per building
  • Benefits: Isolation (building failures don’t cascade), scalability (add buildings easily), high backbone bandwidth

2.6.2 Pattern 2: Star Core + Mesh Edge

  • Use when: High-bandwidth core devices + battery-powered sensor swarm
  • Structure: Wi-Fi/Ethernet star for cameras/controllers, Zigbee mesh for sensors
  • Example: Warehouse with IP cameras (star to PoE switch) + inventory sensors (Zigbee mesh)
  • Benefits: Optimize each network layer for its requirements (bandwidth vs battery)

2.6.3 Pattern 3: Dual-Star Redundancy

  • Use when: Reliability critical but mesh complexity unacceptable
  • Structure: Two independent star networks with failover
  • Example: Hospital patient monitoring with primary and backup gateways
  • Benefits: Simpler than mesh (easy troubleshooting) with gateway redundancy

2.6.4 Pattern 4: Star-of-Stars (Hierarchical Star)

  • Use when: Wide geographic area, battery-powered sensors, no multi-hop needed
  • Structure: Sensors star to local gateways, gateways star to central server
  • Example: LoRaWAN smart city (sensors → gateways → network server → cloud)
  • Benefits: Extends range without mesh complexity, preserves battery life

Decision Algorithm:

START
  └─ Devices > 100? ──────────┐
                               │ YES
                               ▼
       Consider Hybrid ────────┤
           │                   │
           │                   │ Multiple buildings?
           │                   │ ──────────────────┐
           │                   │                    │ YES
           │                   │                    ▼
           │                   │        Use Tree + Mesh
           │                   │
           │                   │ Mixed bandwidth needs?
           │                   │ ──────────────────┐
           │                   │                    │ YES
           │                   │                    ▼
           │                   │        Use Star Core + Mesh Edge
           │                   │
           │                   │ Reliability critical?
           │                   │ ──────────────────┐
           │                   │                    │ YES
           │                   │                    ▼
           │                   │        Use Dual-Star or Full Mesh
           │                   │
           │                   ▼
           │              Evaluate Cost
           │
           ▼ NO (devices < 100)
     Use Pure Topology
           │
           ▼
     Battery-powered? ────────┐
           │                  │ YES
           │                  ▼
           │          Use Pure Star (LoRaWAN/Wi-Fi)
           │
           │ NO
           ▼
     Reliability critical? ───┐
           │                  │ YES
           │                  ▼
           │          Use Pure Mesh (Zigbee/Thread)
           │
           │ NO
           ▼
     Use Pure Star (cheapest)

Cost-Benefit Example:

Smart city streetlight deployment (1,000 lights across 50 blocks):

Topology Infrastructure Cost Operational Cost (10 yr) Reliability Verdict
Pure Mesh $170k (mesh radios) $0 High (self-healing) Good reliability, low opex
Pure Star (Cellular) $50k (cellular modems) $1.2M ($10/mo/light × 10 yr) Medium (carrier dependent) High opex prohibitive
Hybrid (Fiber + Mesh) $850k (fiber backbone) + $120k (mesh access) $0 Very High High capex, but best long-term
Hybrid (Wireless Backhaul + Mesh) $300k (backhaul radios) + $120k (mesh access) $0 High Best cost-benefit balance

Winner: Hybrid wireless backhaul (point-to-point radios between blocks) + mesh within blocks. Cost-effective, no recurring fees, reliable.

Key Insight: Hybrid topologies typically cost 20-40% more upfront than pure topologies but provide 2-5x better scalability, reliability, and flexibility. Justified when deployment exceeds 100 devices or spans multiple locations.

Try It: Topology Selector

Answer these questions about your deployment to get a topology recommendation.

2.7 Concept Relationships

Foundation Concepts:

Core Topology Concepts:

Design and Implementation:

Hands-On Application:

Protocol Implementations:

2.8 See Also

Learning Resources:

Advanced Topics:

Architecture Patterns:

Design Tools:

Common Pitfalls

Choosing Zigbee first and then “discovering” it uses mesh topology is backwards. Fix: identify topology requirements first, then select a protocol that natively implements that topology.

In a mesh network, router nodes relay traffic for their neighbours and cannot sleep as aggressively as star end devices. Fix: separate router and end-device power budgets in the design spreadsheet.

Security cameras (high bandwidth, mains powered) and soil sensors (low bandwidth, battery powered) have different optimal topologies. Fix: segment the network and choose a topology per device class.

2.9 What’s Next

If you want to… Read this
Study the four fundamental topology types Basic Types
Understand graph-theoretic topology analysis Topology Analysis
Learn topology selection criteria Topology Selection
Design hybrid topologies Hybrid Design
Run hands-on topology labs Topology Lab