A Content Dissemination Technique Based on Priority to Improve Quality of Service of Vehicular Ad Hoc Networks
Post-publication record
Source: Retraction Watch, joined by DOI. OpenAlex records retraction as is_retracted, a boolean over a state space with at least four values, so it cannot express an expression of concern, a correction or a reinstatement; it reports them as false, which reads as “fine”.
Bibliographic record
Abstract
Due to the ability of Vehicular Ad Hoc Networks (VANETs) to improve mobility and create innovative services, they have received increasing attention from both industry and academia fields. Named Data Networking (NDN) is a network service that has been developed for Internet’s host-based packet delivery model. In VANETs, NDN is used as an emerging architecture for improving the quality of service (QoS) of the networks connected cloud and mobile Internet of Things (IoT). We can achieve this improvement using an efficient content dissemination and forwarding technique that depends on name-based routing, in-network content caching, and interest-based content retrieval. The large amount of data processed by several IoT sensors or nodes of VANETs makes content prioritizing and forwarding mechanism is crucial, especially when many end-users need common content simultaneously. Therefore, in this paper, we propose a content dissemination technique based on priority for boosting the service requirements of NDN-based cloud and mobile IoT nodes in the VANETs. The approach prioritizes the data flow of traffic into four classes: urgent, emergency, least, and average using a novel constrained location and deadline method, called New method employing Deadline Distance and Size of Data (NDDS). The highest priority is assigned to the data traffic with the emergency class, then urgent, average, and least class. To evaluate this proposed technique, a numerical simulation experiment is conducted by using the CloudSim toolkit. The simulation results demonstrate that the emergency data flow has minimum processing time, compared to the average, urgent, and least data flow, which can significantly enhance the QoS of NDN protocol-based Ad Hoc networks.
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.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.001 |
| 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".