38 Choosing the Right Network Type

38.2 Overview: Classify The Requirement, Not The Brand

Network classification is a shortcut for reasoning about reach, bandwidth, power, ownership, mobility, and failure boundaries. PAN, LAN, WAN, and LPWAN labels are useful only after the deployment requirement is bounded. A wearable badge, a PoE camera, a campus gateway, and a field soil sensor may all belong to one IoT system, but they should not use one network class.

The first decision is the communication job: how far the device must reach, how much data it sends, how often it wakes, whether it moves, who owns the infrastructure, and what happens when coverage is weak.

A class label is therefore an engineering filter, not a product category. PAN usually means the device can live close to a phone, reader, hub, or coordinator; LAN usually means the site can provide local infrastructure such as access points, switches, cabling, and power; WAN usually means the device or gateway must cross wider geography, operator networks, or remote backhaul; LPWAN narrows that wide-area problem for small payloads and long battery life. The useful question is not "which technology is best?" but "which class leaves the fewest unresolved assumptions for this device job?" A fixed camera, for example, may prefer Ethernet and PoE because power and predictable capacity matter more than mobility. A soil sensor may prefer LPWAN because reach and sleep time matter more than throughput. A wearable badge may prefer a PAN path because local readers keep the radio and battery budget small.

Ground overview: classify the requirement, not the brand with the visual at Figure 38.1. Start from Network Classification by Range, but keep Decision factor visible while evaluating pan, lan, and wan describe useful reach bands, but each band still contains several technology choices.

Use Decision factor to test Network Classification by Range in the diagram at Figure 38.1. Then inspect PAN as the final qualifier on pan, lan, and wan describe useful reach bands, but each band still contains several technology choices. That sequence keeps overview: classify the requirement, not the brand tied to what is visibly labelled.

Figure 38.2 makes overview: classify the requirement, not the brand inspectable through Bandwidth vs. Coverage for IoT Protocols and Q2: High BW / Short Range. Those diagram labels establish the scope of the common trade is reach versus throughput, with power and ownership deciding which option is realistic.

Trace the visual from Bandwidth vs. Coverage for IoT Protocols to Q2: High BW / Short Range in Figure 38.2; verify Q1: High BW / Long Range before concluding. Together those labels make the common trade is reach versus throughput, with power and ownership deciding which option is realistic testable. Apply their boundary when working through overview: classify the requirement, not the brand.

38.3 Practitioner: Build A Classification Record

A useful network classification record is a small design artifact. It does not just say "use Wi-Fi" or "use LoRaWAN." It records the tier, the reason that tier fits, the boundary where traffic moves to another tier, and the evidence that proves the choice under real conditions.

Write the record so another engineer can challenge it. For each device type, name the class, the next boundary, the normal payload, the peak payload, the wake or mobility pattern, the owner of the infrastructure, and the field test that would falsify the choice. If a badge depends on doorway readers, the reader density is part of the classification record. If a camera depends on PoE, switch power and uplink capacity are part of the record. If a remote meter depends on an operator network, coverage evidence and subscription lifecycle are part of the record.

Inspect Figure 38.3 before this decision: Wireless Technologies: Bandwidth vs Coverage must be judged beside HIGH BW. Together Wireless Technologies: Bandwidth vs Coverage and HIGH BW bound this claim.

Wireless Technologies: Bandwidth vs Coverage begins the diagram in Figure 38.3; locate Wireless Technologies: Bandwidth vs Coverage, compare HIGH BW, and verify MEDIUM BW. Wireless Technologies: Bandwidth vs Coverage states the starting condition; HIGH BW supplies its counterpart; MEDIUM BW limits the conclusion; retain its labelled boundary.

Inspect Figure 38.4 before this decision: Network Coverage Areas must be judged beside WAN. Together Network Coverage Areas and WAN bound this claim.

Network Coverage Areas begins the diagram in Figure 38.4; locate Network Coverage Areas, compare WAN, and verify LAN. Network Coverage Areas states the starting condition; WAN supplies its counterpart; LAN limits the conclusion; retain its labelled boundary.

38.4 Under The Hood: Each Class Hides A Boundary

Classification is not a protocol stack. It is a boundary model. A PAN device still needs local addressing, pairing, channel access, and a bridge to wider services. A LAN device still needs switch or access-point capacity, power, VLAN or security policy, and backhaul. A WAN device still depends on gateway density, operator coverage, spectrum rules, provisioning, and lifecycle continuity.

The hidden work is usually translation and ownership. A short-range device may speak Bluetooth LE, Zigbee, Thread, or another local protocol, but the enterprise system often expects IP topics, HTTP APIs, MQTT messages, or database records. The phone, hub, border router, or gateway that performs that handoff changes addressing, trust, timing, retry behavior, and failure visibility. When that boundary is not recorded, teams blame the "network class" even though the real problem is a pairing policy, gateway queue, credential rotation, backhaul outage, or missing device-to-cloud mapping.

The same pattern appears in LAN and WAN choices. Ethernet can remove radio uncertainty, but it introduces cable plant, PoE budget, switch-port, VLAN, and maintenance boundaries. Wi-Fi can reuse building infrastructure, but access-point placement, channel planning, roaming behavior, and client density decide whether the class is actually adequate. Cellular and LPWAN (LoRaWAN, Sigfox, NB-IoT, or a narrower option such as Weightless) can reach remote assets, but SIM provisioning, roaming policy, regional spectrum rules, gateway density, payload limits, and operator lifecycle become design dependencies. The classification is credible only when those dependencies are visible and testable, so boundary review becomes part of the architecture rather than a note for later.

Use Figure 38.5 to prepare the decision in under the hood: each class hides a boundary. The diagram names BLE Personal Area Network Topology and BLE, the two anchors needed to assess pan boundaries are usually reader, phone, hub, or coordinator boundaries.

Compare BLE Personal Area Network Topology with BLE inside the visual at Figure 38.5. Next find Phone, which completes the scope of pan boundaries are usually reader, phone, hub, or coordinator boundaries. The decision in under the hood: each class hides a boundary must preserve that labelled boundary.

Before under the hood: each class hides a boundary, inspect Figure 38.6: LAN Topology with Wi-Fi and Ethernet IoT Devices must be considered with Ethernet. That visual pairing grounds lan boundaries are access-point, switch, cable, power, and building-coverage boundaries in named evidence.

Locate LAN Topology with Wi-Fi and Ethernet IoT Devices on Figure 38.6 before checking Ethernet. The visual’s third anchor, Wi-Fi, completes lan boundaries are access-point, switch, cable, power, and building-coverage boundaries. Carry LAN Topology with Wi-Fi and Ethernet IoT Devices into under the hood: each class hides a boundary; use Wi-Fi as its limiting condition.

To test under the hood: each class hides a boundary, open the diagram in Figure 38.7. Smart City LoRaWAN WAN Topology supplies one named condition; LoRa supplies the necessary comparison for wan boundaries are gateway, operator, backhaul, roaming, and service-continuity boundaries.

At Smart City LoRaWAN WAN Topology in Figure 38.7, compare the diagram with LoRa; then locate IP backhaul. That labelled check bounds wan boundaries are gateway, operator, backhaul, roaming, and service-continuity boundaries. For under the hood: each class hides a boundary, retain IP backhaul as evidence for the resulting choice.