A technology selection framework for range, traffic, topology and energy constraints

Abstract

Wireless mesh deployments span radio technologies that differ in range, medium access, throughput and energy requirements. A direct comparison is meaningful only if physical layer capabilities are separated from the network and routing protocols above them. This analytical review examines IEEE 802.11s, IEEE 802.15.4 and Zigbee, Bluetooth Low Energy Mesh, and proprietary multi hop architectures using LoRa. A normalized evaluation matrix links the choice of radio to payload size, reporting interval, link budget, hop depth and relay duty cycle. Rather than assigning a universal winner, the study specifies the design questions that select a technology for a particular sensing task. Results are qualitative and model based; no cross platform field experiment is claimed.

Keywords: wireless mesh networks; sensor networks; communication technologies comparison; analytical modeling; reliability; network design.

1 Introduction

Wireless mesh designs connect nodes using multiple wireless links and forwarding relays, but the existence of an alternate link does not by itself guarantee end to end service. Performance depends on radio quality, control traffic, source reporting rates, topology changes and gateway capacity. This study addresses one distinct subset of those coupled design concerns, using the models and engineering constraints developed in MESH2026-v07. Its findings are analytical statements with explicit assumptions rather than claims about a completed controlled deployment.

The objective is to define a technically traceable decision framework that converts the supplied study into testable engineering criteria. The manuscript draws solely on the source report and bibliographic entries present in that report. References retain the original source numbering so each item can be reconciled directly with the underlying bibliography. No new externally obtained sources are introduced.

2 Analytical Scope and Method

The method proceeds by identifying the system boundary, selecting a small number of measurable state variables, deriving a simplified relationship or comparison, and then distinguishing mathematical consequences from assumptions that require experimental verification. Conceptual drawings show component or information relationships; calculated charts visualize nominal conditions. They are not field measurements. This separation is especially important in wireless systems, where terrain, interference, retransmission policy and time synchronization can dominate apparent theoretical advantage.

Source basis: MESH2026-v07, sections 3.2, 3.3, 3.4, 4.4. Reference numbers preserve the numbering of its chapter 7 bibliography. The analytical figures are original illustrations of stated assumptions, not experimental observations.

Figure 1. Functional architecture developed from the relevant MESH2026 concepts; schematic, not a tested implementation.

Figure 1. Functional architecture developed from the relevant MESH2026 concepts; schematic, not a tested implementation.

3 Radio and network layer separation

The concept of mesh belongs to the forwarding topology, while LoRa, Bluetooth and Wi Fi describe different physical and media access capabilities. Conventional LoRaWAN uses a star of stars arrangement in which gateways deliver end device packets to a network server. A LoRa mesh requires an additional forwarding and route management design, and therefore cannot inherit claims made for standard LoRaWAN without qualification. Similarly, IEEE 802.15.4 defines low rate link operation but does not alone fix a mesh routing algorithm. These distinctions matter when comparing network behavior.

IEEE 802.11s includes a mesh coordination and path selection framework; Zigbee adds network and application functions over IEEE 802.15.4; Bluetooth Mesh is commonly associated with managed flooding and relaying; and proposed LoRa MESH solutions differ by implementation. An application comparison must state which stack, device role and firmware are being evaluated. A passive sensor with occasional uplinks is not the same duty profile as a continuously listening relay. In an energy constrained network the latter role can dominate lifetime even when individual packets are short. [1], [20], [21], [22], [23].

Figure 2. Calculated or qualitative illustration of the design mechanism. Axes and assumptions are described in the main text.

Figure 2. Calculated or qualitative illustration of the design mechanism. Axes and assumptions are described in the main text.

4 A multi criterion technology selection model

The comparative method starts with five dimensions: useful range in the intended environment, payload and aggregate data rate, acceptable end to end latency, frequency of relay receive windows, and robustness to changes in topology. These properties are constrained by antenna placement, regulatory channel limits and traffic timing. The model treats one hop as a unit with uncertain successful delivery; route reliability and airtime are then built from the chosen number of hops. Any technology score therefore belongs to a defined scenario rather than to the protocol name in isolation.

For transparency, assign an ordinal judgment only after defining a service profile. A rural environmental sensor might prefer low reporting rate and longer hops. A local equipment network might prefer rapid exchange and shorter range. A system carrying large sensor records may need higher throughput even though it consumes more power per unit active time. The source document motivates heterogeneity: one radio may collect local data while a different backhaul transports aggregated readings. Cross technology gateways are architectural boundaries requiring separate security and reliability treatment. [6], [7], [9].

Table 1. Scope of the principal design comparison.

Technology Mesh organization Primary design tradeoff

Capacity and real-time behavior IEEE 802.11s Mesh path selection in WLAN versus power

Low-rate PHY/MAC plus routing IEEE 802.15.4 / Zigbee Low rate energy versus interference stack

Bluetooth Mesh Relaying / managed flooding Local reach versus relaying duty

Longer links versus airtime and LoRa MESH Implementation-specific multi-hop capacity

5 Range, capacity and duty cycle tradeoffs

The physical distance reached by a single link does not by itself establish a 50 km system. A long hop can reduce intermediate relay count, but lower data rate or increased time on air can reduce network capacity. Conversely, short range links increase hop depth and relay workload. Both mechanisms are visible in the source manuscript’s proposed Bluetooth and LoRa line models. A fair range comparison must control transmit power, receiver sensitivity, antenna gain, target packet error rate, obstacles and seasonal conditions.

Repeated radio transmissions also increase battery use and contention. The analytical framework counts transmission, reception, scanning, acknowledgements and forwarding separately. A relay that wakes to receive many neighboring packets has a different average current from an end device that sleeps between infrequent measurements. Consequently, advertised end device lifetime is not automatically a mesh relay lifetime. The appropriate output is a per role energy budget linked to measured application packet delivery and age. [19], [35], [50], [68].

6 Operational selection and deployment constraints

A reasonable initial architecture chooses short hop local media for richer or more frequent traffic and long range media for compact periodic status messages, subject to measured reliability. LoRa MESH design must budget airtime and any duty cycle constraints, while BLE operation must account for reception windows and multi hop synchronization. IEEE 802.11s can support richer traffic but requires careful analysis of radio scheduling, interference and electrical supply. Zigbee and 802.15.4 approaches are often relevant where low rate sensing and structured routing are priorities.

Technology selection should also include provisioning, software update strategy, stable addressing, key management, diagnostic visibility and maintainability. In a field deployment two theoretically comparable radios may differ substantially in antenna integration, enclosure loss or supply current peaks. The physical installation therefore becomes part of the communication experiment, not an implementation detail. Any superiority claim should be supported by replicated measurements for the same application workload. [29], [70].

Evaluation parameters

A reproducible trial should log per-node packet identifiers, generation and reception timestamps, route changes, radio retransmissions, queue age and battery current. All measurement and reporting intervals, payload formats, antenna geometry and firmware revisions should be recorded. Reliability must be reported with variation over trials, not as a single best-run percentage. A successful link in one season or installation position is not equivalent to a verified network-level service guarantee.

7 Experimental confirmation and limitations

A controlled comparison should use identical source payloads and desired reporting age, declare one common service target, and measure application packet delivery, distribution of latency, consumed charge and actual throughput at the gateway. Tests should repeat under several obstacle and interference states and with different hop counts. The comparison must report whether routing, retransmissions, scanning and encryption are enabled. The experiment should also document which nodes are battery powered and which operate as infrastructure relays.

This article does not assign numeric throughput or range superiority because the provided manuscript supplies different model assumptions for different technologies rather than a matched laboratory campaign. The useful conclusion is a decision procedure: select candidate stacks, construct explicit service and energy budgets, then validate them under deployment conditions. Any claimed general ranking without common payload, topology and energy boundaries would be misleading. [71].

8 Reproducible Experiment Design

Matched traffic radio comparison

For every candidate stack, transmit the same application record at a fixed desired reporting rate, but retain technology-appropriate frame and security overhead. Test a one-hop baseline, an intermediate route, and a route at the intended maximum depth. Compare application delivery and packet age rather than raw modulation bit rate. The critical analysis is whether the selected radio can provide its intended service while sharing receive and forwarding demands across battery- powered relays.

All trials should state the hypothesis before measurements begin. In particular, baseline and modified networks must generate a comparable number of application messages under identical payload semantics. Time synchronization, radio configuration, antenna placement and test duration should be documented. Apply a predefined definition of a valid delivery, including how duplicate frames, acknowledgements, partial packets and expired records are treated. Report distributions and uncertainty rather than interpreting isolated examples as population-level network behavior.

The primary measurement vector is: Payload size, gateway-delivered PDR, end-to-end latency, average node charge and busy channel fraction. The experiment should archive raw records and configuration files so that independent reviewers can reconstruct packet success, route depth and energy exposure. Failed configurations and unavailable nodes must remain in the results table rather than being discarded as outliers. Where an event is delayed by buffering, store both the origin timestamp and the gateway arrival timestamp to avoid falsely classifying a stale packet as timely delivery.

9 Model Sensitivity and Acceptance Criteria

A design parameter has operational meaning only relative to an application threshold. For packet delivery, an acceptable loss ratio may differ between a periodic weather reading and an emergency alarm. For latency, a median value can be misleading when occasional extreme delay is harmful. Therefore the acceptance plan should name the threshold and its aggregation level: individual node, gateway sector or whole deployment. At minimum, retain a reliability target, a maximum age for useful data, and a minimum expected autonomy for each energy role.

Sensitivity analysis should vary one major assumption at a time and then test coupled effects. Candidate variables include per-hop reception probability, reporting frequency, number of downstream children, active listening duration, gateway count and available battery capacity. An improvement observed under one parameter combination may disappear when the network is congested or when temperature reduces battery availability. The purpose of a sensitivity plot is to identify which physical measurement would most change the final design decision, not to predict field performance without evidence.

An identical advertised range is not a fair radio comparison when payload and receiver wake behavior differ. Preserve every radio setting and distinguish measurements from theoretical link budgets.

A final acceptance matrix should include four outcomes: the test condition, the expected service limit, the observed numerical result and the engineering decision. The source technical study supports the selection of variables and design mechanisms, but a numerical pass/fail result requires an actual implemented protocol and controlled measurements. The distinction prevents a model assumption from being silently promoted to verified specification.

Evaluation scenario matrix

Scenario Variable held constant Question to resolve

Same radio / payload / gateway Does the reference service meet its Nominal baseline position target?

Same node count and physical Does age or packet loss rise before a Increased offered traffic layout stated limit?

Can useful records still reach the Relay or link interruption Same sensor sample generation gateway?

Same routing and application Which role becomes the limiting Reduced energy reserve service component?

Does adaptation improve the Configuration change Same declared application goal system-level outcome?

The nominal baseline provides a necessary denominator for every claimed improvement. A second, more demanding workload should keep the number and location of devices unchanged, which helps isolate the effect of the altered report rate or route policy. The failure trial should define in advance whether losing the first packet after an outage counts as unacceptable service or whether a bounded recovery period is allowed. A device can legitimately buffer packets for later transfer, but the resulting data age must be visible in the assessment.

Energy experiments should compare the same battery assumptions and device roles. A measured reduction in the charge consumed by a leaf node may be offset by increased listening or forwarding costs in its parent. The appropriate system measure is therefore not simply the largest lifetime estimate in the network; it is the minimum acceptable service continuity across critical coverage points. Temperature, battery cutoff and intermittent backhaul availability may change which node becomes critical even when network geometry is unchanged.

Finally, sensitivity should be reported as an envelope rather than an unexplained single-number promise. State which parameters were deliberately changed, identify the origin of every numerical assumption, and preserve the complete measured distribution if physical tests are later performed. When the source provides only theoretical values, label the result a calculation or hypothesis. This audit trail makes the framework useful for deciding the next experiment and reduces the risk that an optimistic reference scenario will be mistaken for a certified operating limit.

10 Discussion

The analysis points to a recurring challenge: radio reach, packet reliability, bounded latency and energy endurance are not independently optimizable in a shared forwarding network. Improving one dimension can worsen another. Greater redundancy adds possible routes but can increase scanning or contention. More frequent reporting improves data freshness but increases relay burden. Stronger integrity protection changes frame overhead and configuration responsibilities. These effects require a scenario specific performance contract before hardware or protocol claims can be generalized.

The most defensible next step is a measured comparison with a declared baseline and pre- registered acceptance thresholds. Test design should preserve the conditions under which the mathematical assumptions are approximately valid, document deviations, and present limits as prominently as advantages. This article supplies an analytical framework suitable for subsequent empirical investigation but does not claim experimental superiority or compliance certification.

11 Conclusion

The MESH2026 material supports a structured analytical treatment of comparative assessment of lora bluetooth zigbee and wi fi for wireless mesh sensor networks. The resulting framework separates topology, traffic, radio and energy constraints, supplies scenario dependent decision criteria, and defines a path to experimental verification. The final engineering choice should be guided by the application’s maximum data age, required delivery probability, actual relay workload and maintainability under failure. Numerical examples are conditional calculations, and validation against physical deployments remains necessary.

References

[1] A. Cilfone et al., “Wireless Mesh Networking: An IoT-Oriented Perspective Survey on Relevant Technologies,” Future Internet, 11(4), 99, 2019. DOI 10.3390/fi11040099.

[6] I. F. Akyildiz et al., “Wireless mesh networks: a survey,” Computer Networks, 47(4), 445–487, 2005. DOI 10.1016/j.comnet.2004.12.001.

[7] K. Mekki et al., “A comparative study of LPWAN technologies for large-scale IoT deployment,” ICT Express, 5(1), 1– 7, 2019. DOI 10.1016/j.icte.2017.12.005.

[9] U. Raza et al., “Low power wide area networks: An overview,” IEEE Communications Surveys & Tutorials, 19(2), 855–873, 2017. DOI 10.1109/COMST.2017.2652320.

[19] I. F. Akyildiz and X. Wang, “A survey on wireless mesh networks,” IEEE Communications Magazine, 43(9), S23– S30, 2005. DOI 10.1109/MCOM.2005.1509968.

[20] X. Wang and A. O. Lim, “IEEE 802.11s wireless mesh networks: Framework and challenges,” Ad Hoc Networks, 6(6), 970–984, 2008. DOI 10.1016/j.adhoc.2007.09.003.

[21] P. Baronti et al., “Wireless sensor networks: A survey on the state of the art and the 802.15.4 and ZigBee standards,” Computer Communications, 30(7), 1655–1695, 2007. DOI 10.1016/j.comcom.2006.12.020.

[22] S. M. Darroudi and C. Gomez, “Bluetooth Low Energy Mesh Networks: A Survey,” Sensors, 17(7), 1467, 2017. DOI 10.3390/s17071467.

[23] R. P. Centelles et al., “Beyond the Star of Stars: An Introduction to Multihop and Mesh for LoRa and LoRaWAN,” IEEE Pervasive Computing, 20(2), 63–72, 2021. DOI 10.1109/MPRV.2021.3063443.

[29] G. R. Hiertz et al., “IEEE 802.11s: The WLAN Mesh Standard,” IEEE Wireless Communications, 17(1), 104–111, 2010. DOI 10.1109/MWC.2010.5416357.

[35] G. Koulouras et al., “Evolution of Bluetooth Technology: BLE in the IoT Ecosystem,” Sensors, 25(4), 996, 2025. DOI 10.3390/s25040996.

[50] J. R. Cotrim and J. H. Kleinschmidt, “LoRaWAN Mesh Networks: A Review and Classification of Multihop Communication,” Sensors, 20(15), 4273, 2020. DOI 10.3390/s20154273.

[68] A. Augustin et al., “A Study of LoRa: Long Range & Low Power Networks for the Internet of Things,” Sensors, 16(9), 1466, 2016. DOI 10.3390/s16091466.

[70] T. G. Durand and M. J. Booysen, “Performance Evaluation of a Mesh-Topology LoRa Network,” Sensors, 25(5), 1602, 2025. DOI 10.3390/s25051602.

[71] D. Rodenas-Herraiz et al., “Current Trends in Wireless Mesh Sensor Networks,” Sensors, 13(5), 5958–5995, 2013. DOI 10.3390/s130505958.

[M] MESH2026-v07. Technical study, sections 3.2, 3.3, 3.4, 4.4. Unpublished technical material.


Pridaj komentár

Vaša e-mailová adresa nebude zverejnená. Vyžadované polia sú označené *