MétaCan
Menu
Back to cohort
Record W1638344160 · doi:10.1109/iwcmc.2015.7289218

Proactive maintenance in RPL for 6LowPAN

2015· article· en· W1638344160 on OpenAlexaff
Nesrine Khelifi, Sharief Oteafy, Hossam S. Hassanein, Habib Youssef

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware-Defined Networks and 5G
Canadian institutionsQueen's University
Fundersnot available
Keywords6LoWPANIPv6Routing protocolComputer scienceComputer networkPacket lossNetwork packetTestbedDistributed computingThe InternetOperating system

Abstract

fetched live from OpenAlex

Maintenance is a core challenge in all routing protocols. The utilization of IPv6 for Low Power and Lossy Networks (6LowPAN) resulted in the recent standardization of a dedicated routing protocol called RPL (Routing Protocol for Low Power and Losy Neworks). In 6LowPAN, a critical challenge exists in decreasing packet loss under the stringent energy-efficiency mandate to increase network longevity. Moreover, the challenge of failed nodes/links, and operating in a lossy environment where connections require rapid maintenance, present significant challenges. Recent attempts at routing maintenance in RPL presented advancements in handling failures, yet under reactive mechanisms that respond to failures and attempt to reduce network down-time. In this paper we design and implement a proactive RPL (Pro-RPL) maintenance scheme that enables the network to selectively predict and mitigate failures before they impact network connectivity. In Pro-RPL we capitalize on a suffering index that is associated with RPL nodes, and monitors their tendency to result in a failure. This dynamic monitoring is decentralized in nature, and presents a conforming yardstick across RPL nodes, to eliminate overhead in implementation and potential control-traffic over the network. We evaluate the efficiency of Pro-RPL in reducing packet loss, energy consumption and extending network lifetime via extensive simulations with the Cooja Simulator over the Contiki OS.

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 distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.786
Threshold uncertainty score0.210

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.052
GPT teacher head0.267
Teacher spread0.215 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreMethods

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

Quick stats

Citations18
Published2015
Admission routes1
Has abstractyes

Explore more

Same topicSoftware-Defined Networks and 5GFrench-language works237,207