MétaCan
Menu
Back to cohort
Record W2132268129 · doi:10.1109/mwc.2007.4407223

Applications and design issues for mobile agents in wireless sensor networks

2007· article· en· W2132268129 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 Wireless Communications · 2007
Typearticle
Languageen
FieldComputer Science
TopicEnergy Efficient Wireless Sensor Networks
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsComputer scienceWireless sensor networkMobile agentMiddleware (distributed applications)Flexibility (engineering)Distributed computingComponent (thermodynamics)Mobile computingSystems designSoftware deploymentComputer networkEmbedded systemSoftware engineering

Abstract

fetched live from OpenAlex

Recently, research interest has increased in the design, development, and deployment of mobile agent systems for high-level inference and surveillance in a wireless sensor network (WSN). Mobile agent systems employ migrating codes to facilitate flexible application re-tasking, local processing, and collaborative signal and information processing. This provides extra flexibility, as well as new capabilities to WSNs in contrast to the conventional WSN operations based on the client-server computing model. In this article we survey the potential applications of mobile agents in WSNs and discuss the key design issues for such applications. We decompose the agent design functionality into four components, that is, architecture, itinerary planning, middleware system design, and agent cooperation. This taxonomy covers low-level to high-level design issues and facilitates the creation of a component-based and efficient mobile agent system for a wide range of applications. With a different realization for each design component, it is expected that flexible trade-offs (e.g., between energy and delay) can be achieved according to specific application requirements.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.791
Threshold uncertainty score1.000

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.0030.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.046
GPT teacher head0.318
Teacher spread0.273 · 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