LoRa Network Planning and Communication Strategies to Support Multiple IoT Use Cases
Bibliographic record
Abstract
Long range (LoRa) is a popular low-power wide-area networking (LPWAN) technology that can support multitude of Internet of Things (IoTs) use cases. LoRa drives its popularity from its ability to dynamically conFigure PHY layer transmission parameters, such as, bandwidth, spreading factor, coding rate, and transmission power. These parameters impact coverage, reliability, data rate, and energy consumption. Therefore, the parameters should be carefully selected based on an IoT use case’s requirements. Ideally, a deployed LPWAN should simultaneously support multiple IoT use cases. This requirement complicates networking planning and the transmission parameters assignment because not only multiple use cases’ dynamics have to be considered, but possible impact of use cases on each other has to be taken into account. Here, we present and evaluate three different LoRa-based LPWAN planning and communication strategies. The presented strategies consider the following: (i) IoT use case’s data generation model, (ii) transmission parameters selection, (iii) network topology, and (iv) communication model. Our simulation results have demonstrated that the network planning and communication strategy that allocates fastest data rate PHY layer transmission parameters to LoRa nodes, partitions a network into different cells, and uses separate gateway inside each cell is the best LoRa-based LPWAN deployment and communication strategy. The strategy outperforms other presented network planning strategies that use hybrid communication model based on separate communication channels and a combination of single-hop and multi-hop communication.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".