MétaCan
Menu
Back to cohort
Record W2944741907 · doi:10.1109/tmc.2019.2915071

A Seamless Mobility Management Protocol in 5G Locator Identificator Split Dense Small Cells

2019· article· en· W2944741907 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 Mobile Computing · 2019
Typearticle
Languageen
FieldEngineering
TopicAdvanced MIMO Systems Optimization
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsComputer scienceComputer networkMobility managementHandoverPacket lossNetwork packetScalabilityRouting protocolDistributed computingOperating system

Abstract

fetched live from OpenAlex

Network densification with Small Cells (SCs) has emerged as a key technique to increase the 5G network capacity. However, in a densified network, fast mobile nodes will experience frequent handovers with a high signaling load, handover latency, and packet loss, due to the short cell radius. Indeed, Distributed Mobility Management (DMM) protocols aim to solve the shortcomings of centralized mobility management solutions such as poor scalability and non-optimal routing. However, when the cell residence time is short, DMM protocols might suffer from increased costs and limited performance. This paper proposes a localized mobility management protocol in 5G dense SCs, based on the locator identifier separation protocol, local mobility anchoring, and fast handovers concepts. The proposed scheme divides a local domain into several location service areas, each controlled by a local anchor. We provide the analytical models of several handover metrics, namely the average total signaling cost, the data delivery cost, the handover latency, and the packet loss. Numerical and simulation results show significant cost savings, up to 30 percent in signaling overhead, up to 53 percent of packet loss, and up to 90 percent of processing load reduction at the core of the network compared to the existing lisp mobile node protocol.

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 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: none
Teacher disagreement score0.807
Threshold uncertainty score1.000

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.009
GPT teacher head0.236
Teacher spread0.227 · 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