A Reliable Trust Computing Mechanism Based on Multisource Feedback and Fog Computing in Social Sensor Cloud
Bibliographic record
Abstract
Social sensor cloud (SSC) is combined with social network, wireless sensor network, cloud computing, and fog computing, which is currently a new type of Internet of Things (IoT). In order to provide a convenient, open, and highly reliable SSC services, the devices of fog computing are distributed at the edge of cloud computing. The devices of fog computing can independently process and store data, and feedback more quickly in SSC. The sensing layer of SSC faces different types of physical attacks and communication attacks, such as message forgery, message tampering, reply attacks, hidden data attacks, etc., lead to the lack of trust between social sensors and cloud data centers in SSC. Therefore, the trust evaluation between the sensing layer and the network layer is necessary. However, computing the reliability of the social sensor data in cloud data centers will generate a large amount of trust computing overhead, communication overhead, and communication delay, which hinder the widespread application of SSC services. To combat this issue, a reliable trust computing mechanism (RTCM) based on multisource feedback and fog computing fusion is proposed. First, a new metric is designed for the trust of social sensor nodes, and multisource feedback trust value collection is performed at the sensing layer to improve the detection of malicious feedback nodes. Second, the trust feedback information of the sensing layer is collected by the devices of fog computing, and the recommendation trust calculation is performed, which reduces the communication delay and computing overhead. Third, a fusion algorithm is designed to aggregate different types of feedback trust values, which overcomes the limitation of trust weights in artificial weighting and subjective weighting in traditional trust mechanisms. Theoretical analyses and simulation results show that the proposed trust computing mechanism has better computational efficiency and higher reliability compared with existing methods.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.001 | 0.003 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".