MétaCan
Menu
Back to cohort
Record W4213430637 · doi:10.1186/s13677-022-00280-y

KeyPIn – mitigating the free rider problem in the distributed cloud based on Key, Participation, and Incentive

2022· article· en· W4213430637 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

VenueJournal of Cloud Computing Advances Systems and Applications · 2022
Typearticle
Languageen
FieldComputer Science
TopicBlockchain Technology Applications and Security
Canadian institutionsIBM (Canada)
FundersResearch Foundation of The City University of New YorkCity University of New York
KeywordsCloud computingIncentiveKey (lock)Free rider problemScheme (mathematics)Computer scienceResource (disambiguation)LimitingFree ridingComputer securityEnvironmental economicsComputer networkMicroeconomicsEngineeringEconomicsPublic good

Abstract

fetched live from OpenAlex

Abstract In a distributed cloud, unlike centralized resource management, users provide and share resources. However, this allows for the existence of free riders who do not provide resources to others, but at the same time use resources that others provide. In a distributed cloud, resource providers share resources in a P2P fashion. In this paper, we propose a 3-pronged solution KeyPIn—a Key-based, Participation-based, and Incentive-based scheme to mitigate the free rider problem in a distributed cloud environment. We propose an incentive-based scheme based on game theory for providers to participate in the cloud by providing resources. This participation will be low for free riders thereby limiting their access to resources. A secure time instant key is generated based on a key management scheme that enables good users’ more time to access resources as their participation is high, whereas free riders are given limited or no time as their participation is low. Simulation results show that our scheme is effective in mitigating the free rider problem in the distributed cloud.

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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.854
Threshold uncertainty score0.775

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.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.010
GPT teacher head0.254
Teacher spread0.245 · 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