MétaCan
Menu
Back to cohort

Situation-Aware Hybrid Time Synchronization Based on Multi-Source Timestamping Uncertainty Modeling

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

Venue2022 IEEE 96th Vehicular Technology Conference (VTC2022-Fall) · 2022
Typearticle
Languageen
FieldComputer Science
TopicNetwork Time Synchronization Technologies
Canadian institutionsWestern University
Fundersnot available
KeywordsComputer scienceSynchronization (alternating current)Data synchronizationRedundancy (engineering)Distributed computingTime synchronizationReal-time computingProcess (computing)Scheme (mathematics)Computer networkChannel (broadcasting)Operating system

Abstract

fetched live from OpenAlex

Timestamping accuracy is of the utmost importance to achieve accurate time synchronization of large-scale connected systems. However, the heterogeneity and complexity inherent to Internet of Things (IoT) systems lead to multi-source timestamping uncertainties and significantly deteriorate performance of traditional inflexible synchronization methods. In this paper, a situation-aware hybrid time synchronization protocol is designed based on multi-source timestamping uncertainty modeling and integrated time information exchange mechanism for heterogeneous IoT systems. More specifically, the multi-source timestamping error inherent to the overall synchronization process are accurately modeled by exploring the impact of the multi-faceted operating conditions. By analyzing the real-time timestamping uncertainties, a hybrid time synchronization scheme is actualized, which can achieve optimal synchronization strategy for clock parameters estimation. In addition, an integrated time information exchange mechanism is designed to reduce timestamping redundancy during time synchronization. Simulation results show that the proposed scheme can enhance the synchronization accuracy for heterogeneous operating scenarios.

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), Science and technology studies
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.940
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0020.004
Science and technology studies0.0020.000
Scholarly communication0.0000.001
Open science0.0040.002
Research integrity0.0000.002
Insufficient payload (model declined to judge)0.0010.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.014
GPT teacher head0.225
Teacher spread0.210 · 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