← Back to the chapter · Previous detail

Technical detail · Network Design: Prototype Strategy

Capacity and Recovery Scenarios

12.6.1 Capacity and Recovery Scenarios

Network capacity is not just average payload rate. Joins, retries, acknowledgements, route repair, security handshakes, firmware rollout traffic, multicast commands, and gateway buffering can dominate the busy moments. The design must show behavior under normal, peak, failure, maintenance, and growth scenarios.

Recovery behavior is also topology-specific. Thread or Zigbee routes may repair after a relay disappears. RPL parent choices may shift after link quality changes. LoRaWAN devices may increase spreading factor after weak uplinks. Wi-Fi devices may reconnect slowly after access-point or DHCP disruption. Cellular devices may roam, back off, or lose service during congestion.

The under-the-hood model must include scenarios beyond average bytes. A 500-node environmental system may look light if each node sends 40 bytes every five minutes. It can overload during commissioning if every device joins, negotiates keys, downloads configuration, and publishes diagnostic state in the same window. A mesh can also create hidden load when a small set of routers carries traffic for a whole floor. The design should show which nodes forward, which links are bottlenecks, and which queues fill first.

Security and operations can change the topology as much as radio physics. A virtual LAN (VLAN) is a logical division of a local network that separates traffic while using shared network equipment. Separate VLANs, broker authorization rules, per-tenant gateways, certificate lifetimes, and maintenance access boundaries may require a hybrid design even when one radio could technically cover the site. For example, safety alarms may need a local gateway and local fallback path, while analytics telemetry can tolerate cloud delay. Firmware rollout traffic may need staging by floor or zone so the update process does not consume the same channel needed for alarms.

A defensible design records recovery drills. It should say how many messages can buffer during a backhaul outage, whether acknowledgements are retried or suppressed, how stale data is marked, how route repair is detected, how a gateway is replaced, and which logs prove the system recovered. Those details turn a topology from a picture into an operating claim that can be tested before launch.

  • Traffic model: Include payload size, interval, burst trigger, retry policy, acknowledgement rule, and priority for each class.
  • Failure model: Include gateway loss, relay loss, backhaul outage, interference, power recovery, credential expiry, and maintenance windows.
  • Security model: Include device identity, key or certificate lifetime, broker authorization, network segmentation, and support access boundaries.

← Back to the chapter · Previous detail