MétaCan
Menu
Back to cohort
Record W1975298189 · doi:10.1364/jocn.4.000210

Interleaved Polling Versus Multi-Thread Polling for Bandwidth Allocation in Long-Reach PONs

2012· article· en· W1975298189 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

VenueJournal of Optical Communications and Networking · 2012
Typearticle
Languageen
FieldEngineering
TopicAdvanced Photonic Communication Systems
Canadian institutionsUniversity of Ottawa
FundersNational Plan for Science, Technology and InnovationKing Saud University
KeywordsPollingComputer scienceDynamic bandwidth allocationComputer networkPassive optical networkThread (computing)Bandwidth allocationPropagation delayQueueing theoryBandwidth (computing)Real-time computingOperating systemWavelength-division multiplexing

Abstract

fetched live from OpenAlex

Long-reach passive optical networks (LR-PONs) suffer from extremely long propagation delays that degrade the performance of centralized algorithms proposed for upstream bandwidth allocation in traditional PONs. This is because these algorithms are based on bandwidth negotiation messages frequently exchanged between the optical line terminal in the central office and optical network units near the users, which become seriously delayed when the network is extended causing the performance to degrade. In this paper, we review and analyze two centralized dynamic bandwidth allocation algorithms, online interleaved polling and offline multi-thread polling that was recently proposed in the literature for LR-PONs. We investigate and compare their performances together in detail, by studying and observing their elemental delays. Unexpectedly, simulation results show that, although multi-thread polling succeeds in decreasing reporting and queueing delays, interleaved polling keeps a lower grant delay and therefore has better overall delay performance. The latter also achieves better throughput compared to multi-thread polling.

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 categoriesnone
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.861
Threshold uncertainty score0.544

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.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.089
GPT teacher head0.340
Teacher spread0.251 · 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