MétaCan
Menu
Back to cohort
Record W4312984188 · doi:10.1109/access.2022.3210254

Applications of Machine Learning in Resource Management for RAN-Slicing in 5G and Beyond Networks: A Survey

2022· article· en· W4312984188 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 Access · 2022
Typearticle
Languageen
FieldComputer Science
TopicSoftware-Defined Networks and 5G
Canadian institutionsCarleton University
Fundersnot available
KeywordsComputer scienceContext (archaeology)SlicingResource management (computing)Resource (disambiguation)Radio access networkRadio resource managementDistributed computingComputer networkWireless networkBase stationWorld Wide WebTelecommunicationsWireless

Abstract

fetched live from OpenAlex

One of the key foundations of 5 <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">th</sup> Generation (5G) and beyond 5G (B5G) networks is network slicing, in which the network is partitioned into several separated logical networks, taking into account the requirements of diverse applications. In this context, resource management is of great importance to instantiate and operate network slices and meet their performance and functional requirements. Resource management in Radio Access Networks (RANs) is associated with a range of challenges due to network dynamics and the specific requirements of each application while ensuring performance isolation. In this paper, we present a survey on state-of-the-art works that employ Machine Learning (ML) techniques in RAN slicing. We begin by reviewing the challenges, then we review the existing papers on resource management in a comprehensive manner, and classify the papers based on the used ML algorithm, the addressed challenges, and the type of allocated resources. We evaluate the maturity of current methods and state a number of open challenges and some solutions to address these challenges in RAN resource management.

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 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.938
Threshold uncertainty score0.362

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.001
Science and technology studies0.0000.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.021
GPT teacher head0.276
Teacher spread0.255 · 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