Wireless Notes
Learn IoT communication with architecture layers, connectivity options BLE LoRa NB-IoT WiFi Zigbee, protocol stack MQTT CoAP, design trade-offs range power speed cost for engineering students.
What Makes IoT Communication Different?
Internet of Things communication is fundamentally different from traditional internet or mobile communication. In the conventional internet, devices are powerful — laptops and smartphones have large batteries, fast processors, and continuous power. They can afford energy-hungry protocols like TCP/IP over WiFi or cellular.
IoT devices, however, face extreme constraints. A soil moisture sensor buried in a field runs on a coin-cell battery for five years. A smart lock must respond within milliseconds but sleep 99.9% of the time. A factory vibration sensor must transmit high-frequency data reliably in an electromagnetically noisy environment. No single communication technology can serve all these diverse requirements.
This is why IoT communication is defined by trade-offs: range versus power, data rate versus battery life, latency versus cost, reliability versus simplicity. Understanding these trade-offs and knowing which technology fits which use case is the core skill of an IoT systems engineer.
📡 IoT Connectivity Technologies Compared
Choosing the right wireless technology is the most critical design decision in any IoT project. Here is a comprehensive comparison:
| Technology | Range | Data Rate | Power | Cost/Device | Best For |
|---|---|---|---|---|---|
| BLE 5.0 | 50-200m | 2 Mbps | Very Low | $1-3 | Wearables, beacons, indoor sensors |
| Zigbee | 10-100m (mesh extends to km) | 250 kbps | Very Low | $2-4 | Smart home, industrial mesh |
| Z-Wave | 30-100m (mesh) | 100 kbps | Very Low | $4-6 | Home automation |
| WiFi (HaLow) | 1 km | 150 kbps-78 Mbps | Medium-High | $3-5 | IP cameras, high-data sensors |
| LoRa | 10-15 km | 0.3-50 kbps | Ultra Low | $3-5 | Agriculture, meters, asset tracking |
| NB-IoT | 10-15 km | 200 kbps | Low | $5-10 + subscription | Smart city, utilities |
| LTE-M | 10 km | 1 Mbps | Medium | $5-10 + subscription | Mobile assets, wearables with voice |
| 5G mMTC | 1-10 km | Variable | Low | $8-15 | Massive IoT (1M devices/km²) |
| Satellite IoT | Global | 1-10 kbps | Medium | $10-50 | Remote/marine/arctic assets |
| Thread | 30m (mesh extends) | 250 kbps | Very Low | $2-4 | Smart home (Matter protocol) |
🎯 The IoT Design Trade-off Triangle
Every IoT communication decision involves balancing three competing requirements:
Range vs. Power: Physics dictates that transmitting further requires more power. LoRa achieves long range at low power by sacrificing data rate (spread spectrum at very low bitrates). Cellular achieves long range at high data rates but requires significantly more power.
Data Rate vs. Battery Life: Higher data rates mean more radio-on time and more power consumption. A BLE sensor sending 20 bytes every minute can last 5 years on a coin cell. A WiFi camera streaming video drains a large battery in hours.
Cost vs. Coverage: Licensed spectrum technologies (NB-IoT, LTE-M) provide guaranteed coverage and QoS but incur monthly subscription fees. Unlicensed technologies (LoRa, BLE, Zigbee) are free to operate but require you to deploy and maintain your own infrastructure.
| Decision Factor | Questions to Ask |
|---|---|
| Range needed | How far is the device from the gateway/base station? Indoor? Outdoor? |
| Data volume | How many bytes per message? How often? |
| Latency tolerance | Seconds OK (sensors)? Milliseconds needed (actuators)? |
| Power source | Battery (how long must it last)? Mains-powered? Solar? |
| Deployment scale | 10 devices? 10,000? 1 million? |
| Environment | Urban? Rural? Underground? Moving vehicle? |
| Budget | One-time hardware cost? Ongoing subscription acceptable? |
📊 IoT Application Layer Protocols
Once data reaches the network layer, IoT uses specialized application protocols designed for constrained environments:
| Protocol | Transport | Model | Overhead | Best For |
|---|---|---|---|---|
| MQTT | TCP | Publish/Subscribe | Very Low (2-byte header) | Cloud telemetry, sensor data streaming |
| CoAP | UDP | Request/Response (REST-like) | Very Low | Constrained devices, resource-limited MCUs |
| HTTP/HTTPS | TCP | Request/Response | High | Gateway-to-cloud, non-constrained devices |
| AMQP | TCP | Queuing/Pub-Sub | Medium | Reliable enterprise messaging |
| LwM2M | CoAP/UDP | Object model | Low | Device management, firmware updates |
MQTT (Message Queuing Telemetry Transport): The most popular IoT protocol. Uses a publish/subscribe model with a central broker. Sensors publish data to "topics" (e.g., farm/field1/moisture), and subscribers receive updates automatically. Three QoS levels: 0 (at most once), 1 (at least once), 2 (exactly once). Minimal overhead — a complete MQTT publish can be as small as 4 bytes of protocol overhead.
CoAP (Constrained Application Protocol): Designed for extremely resource-limited devices that cannot afford TCP's connection overhead. Uses UDP, supports GET/PUT/POST/DELETE like HTTP, but with 4-byte fixed headers. Ideal for devices with only kilobytes of RAM.
🔐 Security Considerations
IoT security is uniquely challenging because devices are often physically accessible to attackers, have limited processing power for encryption, and may operate for years without updates:
- Device authentication: Every device must prove its identity before being trusted on the network
- Data encryption: Even "boring" sensor data can reveal patterns (e.g., occupancy detection from motion sensors)
- Firmware updates: Secure over-the-air (OTA) update mechanisms are essential for patching vulnerabilities
- Network segmentation: IoT devices should be isolated from critical IT networks (separate VLANs)
- Minimal attack surface: Disable unnecessary services, close unused ports, change default credentials
📝 Summary
IoT communication requires matching wireless technology to specific application constraints — no single solution fits all. The decision framework centers on the trade-offs between range, power consumption, data rate, latency, and cost. Short-range applications use BLE or Zigbee, long-range low-data use LoRa or NB-IoT, and high-bandwidth applications use WiFi or cellular. Application-layer protocols like MQTT and CoAP are optimized for constrained devices with minimal overhead. A well-designed IoT system considers all layers — from sensor hardware through wireless connectivity to cloud analytics — as an integrated communication pipeline.
Exam Focus
Revise definitions, diagrams, examples, and short-answer points for IoT Communication Basics Protocols Architecture Connectivity.
Interview Use
Prepare one clear explanation, one practical example, and one common mistake for this Wireless Communications topic.
Search Terms
wireless-communications, wireless communications, wireless, communications, iot, and, communication, basics
Related Wireless Communications Topics