Airtime, relay scheduling and scalable low rate communication

Abstract

Long range LoRa radio links create an opportunity to reduce hop counts in low rate sensor networks, but the conventional LoRaWAN star of stars does not define arbitrary multihop mesh forwarding. This paper evaluates the separate LoRa MESH concept developed in MESH2026, focusing on path organization, airtime, spreading factor, packet scheduling, energy and regulatory constraints. A 1 km nominal spacing scenario and a sensitivity case with 2 km spacing illustrate geometric relay counts for 1–100 km lines; neither is a guaranteed radio reach. The analysis identifies scheduler feasibility, airtime occupancy and gateway-adjacent relay load as decisive constraints. A field validation program is specified to turn these conceptual comparisons into defensible performance evidence.

Keywords: wireless mesh networks; sensor networks; lora mesh architecture; 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.8, 4.4–4.4.6. 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 LoRa radio is not LoRaWAN mesh

LoRa is a physical modulation, while LoRaWAN defines a higher level network and device management architecture generally described as star of stars. A multi hop arrangement using LoRa radios requires its own addressing, route selection, repeated transmissions, acknowledgements, frame format and security scheme. The mere ability to receive a distant packet does not guarantee support for forwarding it across peers. A research paper must therefore specify which capabilities are inherited from radio hardware and which are additional functions of the proposed mesh stack.

The MESH2026 model adopts a conceptual LoRa MESH architecture that resembles the gateway oriented logic of its shorter range mesh examples. Gateway and relay placement are proposed at nominal 1 km spacing, with 2 km considered for sensitivity. Both assume sufficient packet delivery at the target terrain and antenna configuration. Propagation margins, obstacles, regulation and seasonal losses must be evaluated before these values become operational design parameters. [10], [23], [50].

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 Hop count and latency budget

The geometric number of hops is h ≈ ceil(L/R), where L is line length and R nominal relay spacing. Thus a 50 km line gives 50 hops at 1 km and 25 at 2 km, compared with 500 hops at 100 m spacing. The reduced hop count does not prove lower latency because LoRa packet airtime can be much longer than for other physical layers and can require longer slots.

If a scheduled forwarding slot lasts Tslot, a best case pipeline requires about h·Tslot plus queue and processing overhead. The source model compares 2 s and 60 s slots, and explicitly warns that 2 s cannot fit a 56 byte SF12 frame at its reference physical settings because the payload airtime itself is about 2.63 s. A superframe can generate substantially longer delays if nodes wait for a future window at every hop. The experiment must include real framing, acknowledgement, CAD where used, and all radio turnaround intervals. [68], [70].

Table 1. Scope of the principal design comparison.

Line Hops at 1 km Hops at 2 km Design caution

Link must meet target 1 km 1 1 PDR

Verify intermediate relay 5 km 5 3 load

10 km 10 5 Latency depends on slot

Consider gateway 25 km 25 13 placement

50 km 50 25 Watch first relay airtime

Sectorization likely 100 km 100 50 required

5 Airtime and channel constraints

The LoRa time on air depends on spreading factor, bandwidth, coding rate, preamble and payload length. Increasing spreading factor generally makes packets more robust under marginal link budgets but lengthens transmission and consumes shared channel capacity. The source model uses 125 kHz bandwidth, coding rate 4/5, explicit header, CRC, an eight symbol preamble and 56 byte application payload. Actual mesh frames need extra addressing and security bytes and acknowledgements.

Duty cycle and channel access constraints must be assessed against the full volume of upstream and forwarded traffic. A gateway-adjacent relay can be forced to receive and transmit many packets, sometimes becoming a stricter constraint than a distant leaf node. A small daily payload generated by each end device can still create high busy-time near a central collection point. Regulatory budgets and channel contention need per-relay accounting. [14], [37], [45], [46], [51].

6 Route maintenance and resilience

A useful mesh stack requires loop avoidance, neighbor quality measurements and a bounded response to link failure. Because a single long hop may suffer deep fading or obstruction, route selection should consider actual delivery and retransmission costs rather than nominal range. A backup path needs physical radio visibility, schedule capacity and energy reserve. Merely increasing retransmission limits can consume shared airtime and delay more important messages.

Any proposed LoRa mesh gateway architecture should separate transport reliability from command semantics. A control message may require an authenticated acknowledgement and explicit expiration. Delayed sensing records need timestamps so that consumers can distinguish historical data from real-time alarms. The path protocol must also handle networks temporarily disconnected from the backhaul without confusing cached delivery with current connectivity. [48], [49], [69].

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 Validation and limitations

A test program should measure PDR, latency, current draw, airtime occupation and parent changes across SF values and obstacle types. It should directly compare 1 km and 2 km positions where the terrain permits and include low temperature or wet vegetation conditions. Payload definitions must include security overhead and acknowledgements. Compare a single gateway segment with multiple gateways for the same area and reporting requirement.

The geometrical hop table and airtime examples are predictions from selected assumptions, not measured operational capability. A production LoRa MESH network requires a fully specified protocol, compliance review and repeatable field evidence. Standard LoRaWAN data should not be presented as validation of a separate custom mesh implementation. [8], [42], [54].

8 Reproducible Experiment Design

Airtime constrained LoRa relay trial

Hold a fixed application payload and vary spreading factor within legal radio settings. Measure actual on-air occupancy including routing headers and acknowledgements. Compare short and longer nominal relay spacing without assuming the latter is feasible in all terrain. A second trial adds more reporting nodes and measures gateway-adjacent relay load. The comparison should explicitly log any regulatory limits imposed on transmissions.

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: Per-frame airtime, application PDR, hops, delivered bytes per hour, duty budget and receive current. 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.

A LoRaWAN gateway star experiment is not a validation of a separately designed LoRa MESH routing and relay protocol.

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 lora based multihop mesh architecture for distributed 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

[8] A. Diane et al., “A systematic and comprehensive review on low power wide area network,” Discover Internet of Things, 5, 7, 2025. DOI 10.1007/s43926-025-00097-6.

[10] M. A. Ertürk et al., “A survey on LoRaWAN architecture, protocol and technologies,” Future Internet, 11(10), 216, 2019. DOI 10.3390/fi11100216.

[14] ETSI, EN 300 220-2 V3.3.1, Short Range Devices radio spectrum standard, March 2025.

[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.

[37] Semtech Corporation, AN1200.22 LoRa Modulation Basics, Rev. 2, May 2015.

[42] M. Jouhari et al., “A Survey on Scalable LoRaWAN for Massive IoT,” IEEE Communications Surveys & Tutorials, 25(3), 1841–1876, 2023. DOI 10.1109/COMST.2023.3274934.

[45] T. Polonelli et al., “Slotted ALOHA on LoRaWAN—Design, Analysis, and Deployment,” Sensors, 19(4), 838, 2019. DOI 10.3390/s19040838.

[46] F. Adelantado et al., “Understanding the Limits of LoRaWAN,” arXiv:1607.08011v2, 2017. DOI 10.48550/arXiv.1607.08011.

[48] A. Loubany et al., “Improving Energy Efficiency in LoRaWAN Networks with Multiple Gateways,” Sensors, 23(11), 5315, 2023. DOI 10.3390/s23115315.

[49] LoRa Alliance, LoRaWAN Relay Specification TS011-1.0.0, 2022.

[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.

[51] M. Saelens et al., “Impact of EU duty cycle and transmission power limitations for sub-GHz LPWAN SRDs,” EURASIP J. Wireless Communications and Networking, 2019, 219. DOI 10.1186/s13638-019-1502-5.

[54] R. Kufakunesu et al., “A Survey on Adaptive Data Rate Optimization in LoRaWAN,” Sensors, 20(18), 5044, 2020. DOI 10.3390/s20185044.

[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.

[69] J. Dias and A. Grilo, “LoRaWAN multi-hop uplink extension,” Procedia Computer Science, 130, 424–431, 2018. DOI 10.1016/j.procs.2018.04.063.

[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.

[M] MESH2026-v07. Technical study, sections 3.2.8, 4.4–4.4.6. Unpublished technical material.


Pridaj komentár

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