MétaCan
Menu
Back to cohort
Record W2043943624 · doi:10.1109/tvt.2014.2303081

Stability Region of Opportunistic Scheduling in Wireless Networks

2014· article· en· W2043943624 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 Vehicular Technology · 2014
Typearticle
Languageen
FieldEngineering
TopicAdvanced Wireless Network Optimization
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsScheduling (production processes)Round-robin schedulingFair-share schedulingDynamic priority schedulingRate-monotonic schedulingComputer scienceProportionally fairTwo-level schedulingMathematical optimizationErgodic theoryFlow shop schedulingEarliest deadline first schedulingDistributed computingMathematicsComputer networkMathematical analysis

Abstract

fetched live from OpenAlex

The stability regions of two opportunistic scheduling policies, i.e., utility-based (UB) scheduling and the channel-rate-based (CRB) scheduling, in wireless networks are discussed, respectively. UB scheduling is a generalized proportional fair scheduling in an unsaturated system, and CRB scheduling is a variant of the UB scheduling. We give the closed-form expression of the stability region of CRB scheduling and a numerical method to obtain the stability region of UB scheduling. Both two scheduling policies are not throughput optimal, and thus, in general, their stability regions are less than the ergodic capacity region. With CRB scheduling, the stability region is a convex hull, whereas with UB scheduling, the stability region is generally even nonconvex and may exhibit some undesirable properties such as decreasing the traffic of one flow leading another flow being unstable and proportionally decreasing the traffic of all flows leading a stable system to be unstable. We further show that, as long as the arrival rate lies inside the ergodic capacity region, we can assign a proper weight to each user, and based on the weighted UB/CRB scheduling policies, the system can be stabilized. Detailed numerical examples and simulations are given to illustrate the stability region of the two policies and validate our analysis.

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.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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.740
Threshold uncertainty score0.817

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.001
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.011
GPT teacher head0.205
Teacher spread0.193 · 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