MétaCan
Menu
Back to cohort
Record W2888982783 · doi:10.1109/comst.2018.2867268

Resource Allocation for Ultra-Dense Networks: A Survey, Some Research Issues and Challenges

2018· article· en· W2888982783 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 Surveys & Tutorials · 2018
Typearticle
Languageen
FieldEngineering
TopicAdvanced MIMO Systems Optimization
Canadian institutionsUniversity of British ColumbiaCarleton University
Fundersnot available
KeywordsComputer scienceResource allocationData scienceQuality of serviceManagement scienceTelecommunicationsEngineeringComputer network

Abstract

fetched live from OpenAlex

Driven by the explosive data traffic and new quality of service requirement of mobile users, the communication industry has been experiencing a new evolution by means of network infrastructure densification. With the increase of the density as well as the variety of access points (APs), the network benefits from proximal transmissions and increased spatial reuse of system resources, thus introducing a new paradigm named ultra-dense networks (UDNs). Since the limited available resources are shared by ubiquitous APs in UDNs, the demand for efficient resource allocation schemes becomes even more compelling. However, the large scale of UDNs impedes the exploration of effective resource allocation approaches particularly on the computational complexity and significance overhead or feedback. In this paper, we provide a survey-style introduction to resource allocation approaches in UDNs. Specifically, we first present some common scenarios of UDNs with the relevant special issues. Second, we provide a taxonomy to classify the resource allocation methods in the existing literatures. Then, to alleviate the main difficulties of UDNs, some prevailing and feasible solutions are elaborated. Next, we present some emerging technologies thriving UDNs with special RA features discussed. Additionally, the challenges and open research directions are outlined in this field.

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.014
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.940
Threshold uncertainty score0.985

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0140.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0010.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.176
GPT teacher head0.375
Teacher spread0.199 · 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