MétaCan
Menu
Back to cohort

Community-Oriented Resource Allocation at the Extreme Edge

2022· article· en· W4320029327 on OpenAlex
Abdalla A. Moustafa, Sara A. Elsayed, Hossam S. Hassanein

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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueGLOBECOM 2022 - 2022 IEEE Global Communications Conference · 2022
Typearticle
Languageen
FieldComputer Science
TopicIoT and Edge/Fog Computing
Canadian institutionsQueen's University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceJob shop schedulingBipartite graphResource allocationResource management (computing)Enhanced Data Rates for GSM EvolutionDistributed computingExploitContext (archaeology)Edge computingComputer networkGraphComputer securityTheoretical computer scienceRouting (electronic design automation)Artificial intelligence

Abstract

fetched live from OpenAlex

The surging demand for Edge Computing (EC) to cope with the proliferation of latency-critical and data-intensive applications has inspired the notion of recycling ample yet underutilized computational resources of end devices, also referred to as Extreme Edge Devices (EEDs). Maintaining data privacy and cost efficiency remain core challenges for the viability of EED-enabled computing paradigms. In this context, we propose the Community-Oriented Resource Allocation (CORA) scheme. CORA exploits business, institutional, and social relationships to build clusters and communities of requesters and EEDs that can eliminate recruitment costs and preserve privacy. However, community-imposed constraints on resource allocation can lead to unbalanced work distribution. To address this issue, CORA considers community restrictions, minimizes flowtime and makespan for the allocated services, and retains a reasonable scheduler runtime for real-time resource allocation. Towards that end, CORA formulates the resource allocation problem as a Bipartite Graph Matching problem. Furthermore, CORA exposes tuneable parameters that allow prioritizing flowtime or makespan, making it suitable for different scenarios. Extensive simulations show that CORA outperforms six prominent heuristic-based resource allocation schemes by up to 24% in terms of average makespan while sustaining the same level of flowtime and runtime.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies, Open science
Consensus categoriesOpen science
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.784
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.003
Science and technology studies0.0090.000
Scholarly communication0.0000.000
Open science0.0130.016
Research integrity0.0000.002
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.075
GPT teacher head0.286
Teacher spread0.211 · 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