MétaCan
Menu
Back to cohort
Record W1636364634 · doi:10.1016/j.procs.2015.08.317

Resource Sharing in Mobile Cloud-computing with Coap

2015· article· en· W1636364634 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

VenueProcedia Computer Science · 2015
Typearticle
Languageen
FieldComputer Science
TopicIoT and Edge/Fog Computing
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsComputer scienceCloud computingResource (disambiguation)Distributed computingMobile cloud computingShared resourceComputer networkWorld Wide WebOperating system

Abstract

fetched live from OpenAlex

Mobile Cloud-Computing (MCC) is a term introduced by Marc Baccue in 2009 20 that popularized the idea of using cloud-hosted components as a means to overcome the resource-constraints of mobile devices. But as the smartphones and tablets overcame their resource-constraints, the meaning of the term MCC changed. Nowadays MCC is mainly associated with using mobile devices to engage cloud-hosted services and to a lesser extend with combining multiple mobile devices (e.g. cloud of devices). However, as the number of users with multiple mobile devices increases there is a growing demand for enabling apps on mobile devices to share hardware and software resources. This in turn leads to questions regarding decentralized interaction, coordination and resource sharing among multiple mobile devices. This paper focusses on the “horizontal scalability” of apps e.g. the ability to combine multiple mobile devices (executing the same mobile app) into a single compute environment that utilizes all available hardware and software resources in a decentralized manner. One possible approach to achieve this is by designing mobile apps as sets of RESTful micro-services and to allow these services to communicate via low-bandwidth IoT communication protocols. This paper presents the results of our performance evaluations using RESTful micro-services on mobile devices that communicate via the IoT protocol CoAP in different WIFI environments.

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)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.919
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.0010.004
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0040.003
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.023
GPT teacher head0.250
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