MétaCan
Menu
Back to cohort

Evaluation of Failure Analysis of IoT Applications Using Edge-Cloud Architecture

2022· article· en· W4280522970 on OpenAlex
Mohammad S. Jassas, Qusay H. Mahmoud

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

Venue2022 IEEE International Systems Conference (SysCon) · 2022
Typearticle
Languageen
FieldComputer Science
TopicIoT and Edge/Fog Computing
Canadian institutionsOntario Tech University
FundersUmm Al-Qura University
KeywordsCloud computingComputer scienceInternet of ThingsArchitectureEnhanced Data Rates for GSM EvolutionComputer architectureEmbedded systemOperating systemTelecommunications

Abstract

fetched live from OpenAlex

The most important features of the Internet of Things (IoT) application architecture are connectivity, detection, scalability, intelligence and integration. IoT devices should be designed and installed so that they can be scaled up or down based on business and application requirements. Cloud computing has faced various challenges due to its rapid expansion. Due to the growing number of IoT devices and the data they generate, cloud computing cannot meet quality-of-service requirements such as low latency due to its remote geographic location. Edge computing models are urgently needed to develop IoT applications. This paper investigates the impact of combining IoT, cloud, and edge computing for failure analysis and prediction. Furthermore, based on the Edge-Cloud architecture, we offer an architecture for a highly reliable and available IoT application that can support the new paradigm of cloud-IoT applications. The proposed model can reduce the number of failed tasks for cloud-IoT applications. We have also examined how many tasks fail when different architectures are used. The evaluation results show that failed tasks and CPU usage have decreased after applying the “Edge and Cloud” architecture. Using “Edge and Cloud” architecture can also control network traffic compared to other architecture.

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 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.719
Threshold uncertainty score0.744

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.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0020.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.065
GPT teacher head0.317
Teacher spread0.252 · 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