Data-Driven Trajectory Quality Improvement for Promoting Intelligent Vessel Traffic Services in 6G-Enabled Maritime IoT Systems
Bibliographic record
Abstract
Future generation communication systems, such as 5G and 6G wireless systems, exploit the combined satellite-terrestrial communication infrastructures to extend network coverage and data throughput for data-driven applications. These ground-breaking techniques have promoted the rapid development of Internet of Things (IoT) in maritime industries. In maritime IoT applications, intelligent vessel traffic services can be guaranteed by collecting and analyzing high volume of spatial data flows from automatic identification system (AIS). This AIS system includes a highly integrated automatic equipment, including functionalities of core communication, tracking, and sensing. The increased utilization of shipboard AIS devices allows the collection of massive trajectory data. However, the received raw AIS data often suffers from undesirable outliers (i.e., poorly tracked timestamped points for vessel trajectories) during signal acquisition and analog-to-digital conversion. The degraded AIS data will bring negative effects on vessel traffic services (e.g., maritime traffic monitoring, intelligent maritime navigation, vessel collision avoidance, etc.) in maritime IoT scenarios. To improve the quality of vessel trajectory records from AIS networks, we propose to develop a two-phase data-driven machine learning framework for vessel trajectory reconstruction. In particular, a density-based clustering method is introduced in the first phase to automatically recognize the undesirable outliers. The second phase proposes a bidirectional long short-term memory (BLSTM)-based supervised learning technique to restore the timestamped points degraded by random outliers in vessel trajectories. Comprehensive experiments on simulated and realistic data sets have verified the dominance of our two-phase vessel reconstruction framework compared to other competing methods. It thus has the capacity of promoting intelligent vessel traffic services in 6G-enabled maritime IoT systems.
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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 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".