MétaCan
Menu
Back to cohort
Record W2096223912 · doi:10.1109/wcnc.2010.5506386

Reducing Handoff Latency for WiMAX Networks Using Mobility Patterns

2010· article· en· W2096223912 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicIPv6, Mobility, Handover, Networks, Security
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsHandoverComputer networkBase stationComputer scienceWiMAXNetwork packetSoft handoverPacket lossWireless networkWirelessTelecommunications

Abstract

fetched live from OpenAlex

In recent years, Worldwide Interoperability for Microwave Access (WiMAX) has become an important technology providing wireless connections for mobile terminals in a wireless Metropolitan Area Network (MAN), due to its large radio range. In a MAN environment, wireless clients always have high mobility; therefore, it is possible that the mobile clients will move away from the service coverage of serving base stations and change their associating base stations. The process of switching between different base stations is known as the handoff process. During the handoff process, the connection between the mobile terminal and the serving base station ceases. The quality of mobile wireless networks is significantly affected by handoff latency and packet loss ratio. In this paper, we propose a fast handoff scheme using mobility patterns for WiMAX networks. Mobility patterns are adopted to predict the next base station and therefore waive unnecessary scans, and the serving base station forwards the data packets received during the handoff process to the target base station for the minimizing of the packet loss ratio. Extensive simulation experiments are conducted to evaluate the performance of the proposed scheme. The results demonstrate that our scheme can shorten the handoff latency.

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: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.235
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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.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.012
GPT teacher head0.234
Teacher spread0.222 · 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