26  IoT Communications Technology

In 60 Seconds

Four network classifications serve different IoT ranges: PAN (Bluetooth/Zigbee, up to 10m for wearables), LAN (Wi-Fi, up to 100m for buildings), MAN (LoRaWAN/NB-IoT, up to several km for cities), and WAN (cellular/satellite, thousands of km for vehicles). Five selection factors determine the right technology: range, power consumption, data rate, network topology, and cost – there is no universal “best” protocol.

Minimum Viable Understanding
  • Four network classifications serve different IoT ranges: PAN (Bluetooth/Zigbee, up to 10m for wearables), LAN (Wi-Fi, up to 100m for buildings), MAN (LoRaWAN/NB-IoT, up to several km for cities), and WAN (cellular/satellite, thousands of km for vehicles).
  • Five selection factors determine the right communication technology: range, power consumption, data rate, network topology, and cost – there is no universal “best” protocol.
  • UART is a fundamental two-wire serial protocol for IoT device interfaces, using start/stop bits for asynchronous communication without a shared clock signal.

The Sensor Squad had friends all over – some nearby, some very far away – and they needed different ways to communicate!

Bluetooth (Sammy’s walkie-talkie): “I use this to talk to my friend the smartphone just a few meters away. It barely uses any of Bella’s battery power!” Perfect for wearables and health monitors.

Wi-Fi (Lila’s megaphone): “I can shout across the whole house! Great for streaming video from security cameras.” But Bella the Battery warned: “Wi-Fi uses a LOT of my energy – I need to be plugged into the wall!”

LoRaWAN (Max’s long-range radio): “I can whisper all the way across the farm – 10 kilometers! And I barely use any battery.” Perfect for soil sensors in smart agriculture. But Max admitted: “I can only send tiny messages, not videos.”

Cellular (the satellite phone): “I can reach ANYWHERE in the world!” But it costs money every month and uses lots of power. Best for connected cars and GPS trackers that move around a lot.

Bella the Battery summed it up: “Close friends use Bluetooth (low energy). House friends use Wi-Fi (needs power). Farm friends use LoRa (low energy, long range). Traveling friends use Cellular (expensive but everywhere).”

Think of communication technologies like different transportation options:

  • Bluetooth (PAN) is like walking – short distance, low energy, perfect for nearby errands
  • Wi-Fi (LAN) is like a bicycle – covers your neighborhood but needs more effort
  • LoRaWAN (MAN) is like a bus – goes across the whole city, carries small packages efficiently
  • Cellular (WAN) is like a car – goes anywhere, but costs fuel (battery) and tolls (monthly fees)
Term Simple Explanation
PAN Personal Area Network – covers a room (Bluetooth, Zigbee)
LAN Local Area Network – covers a building (Wi-Fi, Ethernet)
MAN Metropolitan Area Network – covers a city (LoRaWAN, NB-IoT)
WAN Wide Area Network – covers the country/world (Cellular, Satellite)
UART Simple two-wire serial connection for debugging and module communication

26.1 Learning Objectives

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

  • Classify Network Types: Distinguish between PAN, LAN, MAN, and WAN network classifications and their IoT applications
  • Evaluate Communication Technologies: Compare protocols like Bluetooth LE, Zigbee, Wi-Fi, LoRaWAN, and cellular based on range, power, and data rate
  • Match Technologies to Applications: Select appropriate communication technologies for specific IoT verticals
  • Explain UART Operation: Describe how UART serial communication works and its role in IoT device interfaces
Key Concepts
  • Personal Area Network (PAN): Short-range networks (up to 10 meters) for wearables and personal devices using Bluetooth, Zigbee, NFC
  • Local Area Network (LAN): Medium-range networks (up to 100 meters) for homes and offices using Wi-Fi and Ethernet
  • Metropolitan Area Network (MAN): Wide-range networks (up to several kilometers) for cities using LoRaWAN and NB-IoT
  • Wide Area Network (WAN): Very wide-range networks (thousands of kilometers) using cellular and satellite
  • UART: Universal Asynchronous Receiver-Transmitter, a fundamental hardware protocol for serial communication between microcontrollers and peripherals

26.2 Prerequisites

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

Chapter Position in Series

This is the second chapter in the Architectural Enablers series:

  1. IoT Evolution and Enablers Overview - History and convergence
  2. IoT Communications Technology (this chapter) - Protocols and network types
  3. Technology Selection and Energy - Decision frameworks
  4. Labs and Assessment - Hands-on practice

26.3 Communications Technology Overview

~18 min | Intermediate | P04.C08.U08

Communication technologies are critical to the functioning of IoT systems. They enable the connectivity and data exchange between IoT devices, ensuring that information flows smoothly from sensors and devices to data processing units and end-users.

26.3.1 Personal Area Networks (PAN)

  • Examples: Bluetooth, Zigbee, NFC, Z-Wave
  • Range: Short (up to 10 meters)
  • Data Rate: Low to moderate
  • Power Consumption: Low
  • Applications: Wearable devices, home automation, personal health monitoring

26.3.2 Local Area Networks (LAN)

  • Examples: Wi-Fi, Ethernet, Powerline communication
  • Range: Medium (up to 100 meters)
  • Data Rate: High
  • Power Consumption: Moderate to high
  • Applications: Smart homes, offices, building automation

26.3.3 Metropolitan Area Networks (MAN)

  • Examples: LoRaWAN, NB-IoT
  • Range: Wide (up to several kilometers)
  • Data Rate: Low to moderate
  • Power Consumption: Low to moderate
  • Applications: Smart cities, industrial IoT, agriculture

26.3.4 Wide Area Networks (WAN)

  • Examples: Cellular (2G, 3G, 4G, LTE), Satellite
  • Range: Very wide (up to thousands of kilometers)
  • Data Rate: High
  • Power Consumption: High
  • Applications: Connected vehicles, remote monitoring, global asset tracking

26.3.5 Choosing the Right Technology

When selecting a communication technology for an IoT application, several factors must be considered:

  • Range: The distance over which the data needs to be transmitted.
  • Power Consumption: The amount of power the communication module consumes, which affects the battery life of the device.
  • Data Rate: The volume of data that needs to be transmitted within a specific timeframe.
  • Network Topology: The structure of the network, whether it’s a star, mesh, or point-to-point configuration.
  • Cost: The cost of implementing and maintaining the communication technology.
Overview of IoT communication technologies organized by network type: PAN (Bluetooth, Zigbee, NFC with short range), LAN (Wi-Fi, Ethernet with medium range), MAN (LoRaWAN, NB-IoT with city-wide range), and WAN (Cellular, Satellite with global reach), showing data rates, power consumption, and typical applications for each category
Figure 26.1: Communications Technology Overview

26.4 Communication Technologies and Application Domains

Selecting the right communication technology for a specific IoT vertical is crucial to ensure optimal performance, efficiency, and cost-effectiveness. The following table outlines the applicability of various communication technologies across key IoT verticals.

Key IoT Verticals LPWAN (Star) Cellular (Star) Zigbee (Mostly Mesh) BLE (Star & Mesh) Wi-Fi (Star & Mesh) RFID (Point-to-point)
Industrial IoT O O
Smart Meter *
Smart City *
Smart Building * O O
Smart Home * * * O
Wearables O *
Connected Car *
Connected Health *
Smart Retail O * *
Logistics & Asset Tracking O * *
Smart Agriculture *
  • Legend:
    • * Highly applicable
    • O Moderately applicable

26.4.1 LPWAN (Low-Power Wide-Area Network)

  • Highly applicable for Smart Meter, Smart City, Smart Building, and Smart Agriculture.
  • Moderately applicable for Logistics & Asset Tracking.
  • Description: LPWAN is ideal for applications requiring long-range communication with low power consumption. It is particularly suited for large-scale deployments in smart cities and agriculture where devices are dispersed over wide areas.

26.4.2 Cellular

  • Highly applicable for Connected Car.
  • Moderately applicable for Industrial IoT, Wearables, Smart Retail, and Logistics & Asset Tracking.
  • Description: Cellular networks offer extensive coverage and high data rates, making them suitable for mobile and wide-area applications such as connected cars and wearables.

26.4.3 Zigbee

  • Highly applicable for Smart Home and Logistics & Asset Tracking.
  • Moderately applicable for Smart Building.
  • Description: Zigbee’s low power consumption and mesh networking capabilities make it ideal for home automation and asset tracking within buildings.

26.4.4 Bluetooth Low Energy (BLE)

  • Highly applicable for Smart Home, Wearables, Connected Health, and Smart Retail.
  • Description: BLE is designed for low power consumption, making it suitable for devices that require frequent communication but need to conserve battery life, such as health monitors and wearable devices.

26.4.5 Wi-Fi

  • Highly applicable for Smart Home.
  • Moderately applicable for Smart Building.
  • Description: Wi-Fi provides high data rates and is widely available, making it ideal for home automation and smart building applications where power consumption is less of a concern.

26.4.6 RFID

  • Highly applicable for Smart Retail and Logistics & Asset Tracking.
  • Moderately applicable for Industrial IoT and Smart Home.
  • Description: RFID is used for point-to-point communication and is suitable for applications involving tracking and identification of items, such as in logistics and retail environments.

The choice of communication technology in IoT systems should be guided by the specific requirements of the application, such as range, power consumption, data rate, and network topology.

26.5 Universal Asynchronous Receiver-Transmitter (UART)

~10 min | Intermediate | P04.C08.U09

Universal Asynchronous Receiver-Transmitter (UART) is a fundamental hardware communication protocol used in many IoT devices for serial communication between microcontrollers and peripherals. UART enables asynchronous serial communication, meaning data is transmitted without a shared clock signal between the transmitter and receiver.

26.5.1 How UART Works

UART communication uses two wires: - TX (Transmit): Sends data from the device - RX (Receive): Receives data to the device

Both devices must agree on: - Baud rate: Speed of data transmission (e.g., 9600, 115200 bps) - Data bits: Typically 8 bits per frame - Parity: Error checking (none, even, odd) - Stop bits: End-of-frame markers (1 or 2 bits)

26.5.2 UART Frame Structure

UART serial communication frame structure diagram showing sequential transmission components: Idle state (logic high) transitions to Start Bit (logic 0) signaling new data frame, followed by 5-9 Data Bits containing payload information, optional Parity Bit for error detection, and 1-2 Stop Bits (logic 1) marking frame end before returning to Idle, demonstrating asynchronous serial protocol where start/stop bits enable receiver clock synchronization without shared clock signal
Figure 26.2: UART frame structure showing start bit, data bits, optional parity, and stop bits for asynchronous serial communication
UART timing diagram showing voltage waveforms on TX line: idle high (logic 1), start bit drops to logic 0, eight data bits follow at the configured baud rate with receiver sampling at center of each bit period, optional parity bit, then one or two stop bits return to logic 1, illustrating how both devices synchronize without a shared clock signal
Figure 26.3: Alternative view: Timing sequence diagram showing UART communication flow. Start bit (LOW) signals frame beginning, receiver samples data bits at agreed baud rate, optional parity enables error detection, stop bit (HIGH) marks frame end. No shared clock - both devices must configure identical baud rate for reliable communication.

26.5.3 Advantages of UART

  • Simple two-wire interface (plus ground)
  • Well-established and widely supported
  • No clock signal required
  • Full-duplex communication (simultaneous TX and RX)

26.5.4 Limitations of UART

  • Limited to point-to-point communication
  • No standardized voltage levels (RS-232, TTL, etc.)
  • Maximum distance typically limited to ~15 meters
  • Speed limited by baud rate agreement

UART is commonly used for: - Debugging and logging from microcontrollers - GPS module communication - Bluetooth module interfaces - Sensor data collection - Programming and configuration of IoT devices

26.6 Knowledge Check

Test your understanding of communication technologies.

26.7 Technology Comparison Reference

Quick reference table for exam and design decisions:

Technology Range Power (Active) Data Rate Best Use Case
BLE 10-30m 10-20mW 1-2 Mbps Wearables, smartphones
Zigbee 10-100m 30-50mW 250 kbps Home automation, mesh
Wi-Fi 30-100m 200-400mW 1-100 Mbps High data, power available
LoRaWAN 2-15km 30-50mW 0.3-50 kbps Smart cities, agriculture
NB-IoT 10-15km 50-100mW 20-200 kbps Asset tracking, meters
Cellular 1-50km 500-2000mW 1-100 Mbps Connected vehicles, mobile

Power consumption pattern: BLE < Zigbee < LoRa < NB-IoT < Wi-Fi < Cellular

Range pattern: BLE < Zigbee/Wi-Fi < LoRa/NB-IoT < Cellular

26.8 Worked Example: Protocol Selection for a Smart Campus

Scenario: A university campus (2 km^2) needs to deploy IoT sensors for four use cases simultaneously. The IT department must select communication protocols and estimate infrastructure costs for a 5-year deployment.

Use Case 1: Classroom Occupancy (400 rooms)

  • Data: Binary occupied/empty, updated every 5 minutes
  • Payload: 4 bytes per message
  • Power source: Battery (ceiling-mounted PIR sensors)
  • Latency requirement: 5 minutes acceptable

Use Case 2: Parking Guidance (800 spaces)

  • Data: Vehicle presence, updated on state change
  • Payload: 8 bytes per message
  • Power source: Battery (in-ground sensors)
  • Latency requirement: 30 seconds

Use Case 3: Security Cameras (120 cameras)

  • Data: 1080p video stream, 4 Mbps per camera
  • Power source: PoE (mains)
  • Latency requirement: Real-time (<200 ms)

Use Case 4: Environmental Monitoring (50 weather stations)

  • Data: Temperature, humidity, pressure, wind, rain – every 10 minutes
  • Payload: 32 bytes per message
  • Power source: Solar + battery
  • Latency requirement: 10 minutes acceptable

Protocol selection analysis:

Use Case BLE Zigbee Wi-Fi LoRaWAN NB-IoT Selected
Occupancy (400) Too many for BLE Mesh overhead high Power too high Low data, long range Monthly fees LoRaWAN
Parking (800) Range insufficient Need 100+ routers Power too high Ideal fit Viable but costly LoRaWAN
Cameras (120) No bandwidth No bandwidth 4 Mbps per cam No bandwidth No bandwidth Wi-Fi 6
Weather (50) Range insufficient Could work but mesh Overkill Perfect fit Works but adds cost LoRaWAN

Infrastructure cost comparison:

Infrastructure LoRaWAN (1,250 sensors) Wi-Fi 6 (120 cameras) NB-IoT alternative
Gateways/APs 3 gateways x $400 = $1,200 40 APs x $300 = $12,000 Existing cellular
Per-device module $5 x 1,250 = $6,250 Included in camera $15 x 1,250 = $18,750
Annual network cost $0 (private network) $0 (campus network) $1.50/device/month = $22,500/year
5-year total $7,450 $12,000 $131,250

Key decision: LoRaWAN wins for the 1,250 low-data sensors because 3 gateways cover the entire campus with zero recurring fees. NB-IoT would cost 17.6x more over 5 years due to monthly per-device charges. Wi-Fi is mandatory for cameras (bandwidth requirement), but using Wi-Fi for all 1,370 devices would require 80+ access points and far higher power consumption.

5-year total cost of ownership (TCO) comparison:

\[ \text{TCO}_{\text{LoRa}} = C_{\text{gateways}} + (n \times C_{\text{module}}) + (5 \times C_{\text{annual ops}}) \]

\[ = \$1{,}200 + (1{,}250 \times \$5) + 0 = \$7{,}450 \]

\[ \text{TCO}_{\text{NB-IoT}} = 0 + (n \times C_{\text{module}}) + (5 \times n \times \$1.50/\text{month} \times 12) \]

\[ = (1{,}250 \times \$15) + (1{,}250 \times \$90) = \$131{,}250 \]

Cost ratio: NB-IoT is \(131{,}250 / 7{,}450 \approx 17.6\times\) more expensive over 5 years. The recurring connectivity fees (\(\$1.50 \times 1{,}250 \times 60\) months \(= \$112{,}500\)) dominate total cost.

26.9 Chapter Summary

This chapter examined the communication technologies that enable IoT connectivity:

  • Network Classifications: PAN (personal), LAN (local), MAN (metropolitan), and WAN (wide area) each serve different range and power requirements
  • Technology Selection: Match protocol capabilities to application requirements - range, power budget, data rate, and cost
  • Application Mapping: Different IoT verticals (smart home, agriculture, vehicles) align with specific communication technologies
  • UART Fundamentals: Serial communication remains essential for device interfaces, debugging, and peripheral connectivity

Understanding these communication options enables informed selection when designing IoT systems.

26.10 What’s Next

Direction Chapter Description
Next Technology Selection and Energy Decision frameworks and energy management strategies
Next Labs and Assessment Hands-on practice and exam preparation
Back IoT Evolution and Enablers Overview History and convergence of enabling technologies

Common Pitfalls

A LoRaWAN gateway covering 10 km radius can be overwhelmed if 10,000 devices simultaneously transmit during a power restoration event. Coverage (geographic reach) and capacity (simultaneous devices) are independent constraints — design for both.

Wi-Fi at 2.4 GHz shares spectrum with Bluetooth, ZigBee, microwave ovens, and neighbors. Industrial environments generate RF interference causing packet loss. Perform a site survey with a spectrum analyzer before committing to Wi-Fi in industrial or warehouse settings.

Connecting two UART devices at different baud rates produces garbled output with no error indication. Always explicitly configure the same baud rate on both sides, and verify with a logic analyzer or oscilloscope when debugging unexplained serial communication failures.

Designing a system assuming Bluetooth or ZigBee (10–100 m PAN range) can span a 200 m warehouse floor. Conduct range tests in the actual deployment environment — building materials attenuate signals by 10–30 dB compared to open-air lab conditions.