MétaCan
Menu
Back to cohort
Record W4294316343 · doi:10.5957/imdc-2022-280

Setting Technical Requirements for Intra-Ship Maritime Communication Services Over 3GPP Systems

2022· article· en· W4294316343 on OpenAlexaff
Xin Chen, David G. Michelson

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicMaritime Navigation and Safety
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsDeliverableService (business)Computer scienceTelecommunicationsSystems engineeringWirelessCommunications systemVariety (cybernetics)Engineering managementEngineeringBusiness

Abstract

fetched live from OpenAlex

The first 3GPP Technical Specification covering service requirements (Stage 1) for the support of maritime communication (MARCOM) over 3GPP systems (TS 22.119) was approved in December 2018 at the TSG SA Plenary meeting in Sorrento. It represents one of several 3GPP initiatives that aim to ensure that future 3GPP/5G systems meet the needs and requirements of a variety of vertical domains and result in a unified communication platform for a broad set of industrial applications. In particular, TS 22.119 has the potential to support both a new wave of Global Maritime Distress and Safety System (GMDSS) modernization and broader 5G maritime services. Despite efforts by 3GPP to engage IALA, IMO, and other groups within the maritime community, much work remains in realising the full potential of this effort. One of the strengths of the 3GPP approach is the manner in which common requirements are re-used by different groups. To this end, wherever possible, the groups will take existing service requirements from 3GPP Stage 1 specifications. Maritime is a good example of this principle, with more general Mission Critical needs covered in other specifications, allowing TS 22.119 to be the deliverable that identifies only specific maritime needs including the service requirements for the support of autonomous shipping and the broader digitalization and mobilization of maritime shipping. Here, we propose a framework that will help to reveal new and emerging wireless system requirements for 3GPP systems in shipboard environments. In the first phase, we consider a current ship within which current wireless technology is deployed. Such scenarios are characterized by a limited set of use cases, a brute-force approach to design and deployment, a disconnect between the reference environments for which the wireless technology was developed, and the new operating environment. The result is suboptimal performance with glaring deficiencies. To a large extent, this is where we are today as technologies such as Wi-Fi, ZigBee, and Bluetooth are deployed aboard ship. In the second phase, airlink and radio resource management are modified to meet the needs of the new operating environment. Different service level requirements are identified, and more ambitious applications are deployed. At this stage, the primary impact is on shipboard operations with relatively little impact on ship design. To a large extent, this reflects the majority of current forward looking thinking concerning the application of wireless technology aboard ship today. In the third phase, ship design & construction are modified, subtly or otherwise, to account for both the nature of wireless propagation and the implications of the enhanced connectivity. In some cases, this may include lessons learned that allow crew sizes to be reduced, perhaps dramatically, in light of significant increases in the depth and sophistication of shipboard automation. We believe that this approach is well suited to bridging the gaps between wireless developers, naval architects, and standards developers, and contribute to the long-term success of efforts such as TS 22.119.

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 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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.858
Threshold uncertainty score0.678

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.253
Teacher spread0.239 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreEmpirical

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".

Quick stats

Citations0
Published2022
Admission routes1
Has abstractyes

Explore more

Same topicMaritime Navigation and SafetyFrench-language works237,207