MétaCan
Menu
Back to cohort
Record W2131199936 · doi:10.1109/mcom.2008.4644119

Improved VoIP capacity in mobile WiMAX systems using persistent resource allocation

2008· article· en· W2131199936 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 Communications Magazine · 2008
Typearticle
Languageen
FieldEngineering
TopicAdvanced Wireless Network Optimization
Canadian institutionsNortel (Canada)
Fundersnot available
KeywordsVoice over IPWiMAXComputer scienceComputer networkMobile communications over IPWireless broadbandIEEE 802Overhead (engineering)Mobile broadbandResource allocationWirelessMobile telephonyTelecommunicationsMobile radioWireless networkThe InternetQuality of servicePublic land mobile network

Abstract

fetched live from OpenAlex

Efficient support of voice traffic has always been one of the key metrics for evaluating and selecting radio access technologies. Even for next-generation broadband wireless technologies primarily focused on the mobile Internet, special handling of VoIP traffic in the physical and MAC layers is required to maximize voice capacity. While Mobile WiMAX Release 1.0 and 802.16e have all the key features necessary to support mobile VoIP traffic, special attention is given in Mobile WiMAX Release 1.5 and 802.16REV2 to further optimizing VoIP capacity through reduction in the MAC layer overhead associated with signaling messages. This article focuses on features and solutions used in Mobile WiMAX and the 802.16 standard to support voice traffic and the expected performance in Release 1.0/802.16e-2005, as well as gains from optimization concepts such as persistent allocation added in Release 1.5/802.16REV2. In each case, MAP overhead reduction and the projected improvements in VoIP capacity are presented using typical industry accepted models and assumptions. The results show about 15 percent increase in bidirectional VoIP capacity.

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: Empirical
Teacher disagreement score0.286
Threshold uncertainty score0.854

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.052
GPT teacher head0.247
Teacher spread0.195 · 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