MétaCan
Menu
Back to cohort

Cross-Layer Schemes for Reducing Delay in Multihop Wireless Networks

2012· article· en· W1993549324 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIEEE Transactions on Wireless Communications · 2012
Typearticle
Languageen
FieldComputer Science
TopicMobile Ad Hoc Networks
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsComputer scienceComputer networkScheduling (production processes)Distributed computingStatic routingEqual-cost multi-path routingNetwork packetRouting protocolMathematical optimizationMathematics

Abstract

fetched live from OpenAlex

End-to-end delay is an important QoS metric in multihop wireless networks such as sensor networks and mesh networks. End-to-end delay is defined as the total time it takes for a single packet to reach the destination. It is a result of many factors including the length of the route and the interference level along the path. In this paper we address how to minimize end-to-end delay jointly through optimizing routing and link layer scheduling. We present two cross-layer schemes, a loosely coupled cross-layer scheme and a tightly coupled cross-layer scheme. In the loosely coupled cross-layer scheme, routing is computed first and then the information of routing is used for link layer scheduling; in the tightly coupled scheme, routing and link scheduling are solved in one optimization model. The two cross-layer schemes involve interference modeling in multihop wireless networks with omnidirectional antenna. A sufficient condition on conflict-free transmission is established, which can be transformed to polynomial-sized linear constraints, and a linear program based on the sufficient condition is developed. Through simulation, we show that the proposed routing and scheduling schemes can outperform their counterparts in each layer, and the integrated cross-layer schemes are superior to the combination of the existing routing and scheduling schemes.

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.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.904
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0030.000
Research integrity0.0000.001
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.042
GPT teacher head0.315
Teacher spread0.273 · 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