MétaCan
Menu
Back to cohort
Record W4399728363 · doi:10.1109/mcom.001.2300563

Synchronization Plane in O-RAN: Overview, Security and Research Directions

2024· article· en· W4399728363 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

VenueIEEE Communications Magazine · 2024
Typearticle
Languageen
FieldEngineering
TopicWireless Body Area Networks
Canadian institutionsEricsson (Canada)Concordia University
Fundersnot available
KeywordsComputer scienceSynchronization (alternating current)RanTelecommunicationsRouting control planePlane (geometry)Computer networkComputer security

Abstract

fetched live from OpenAlex

Under the efforts to transition to an open radio access network (RAN), movements like O-RAN have emerged. One of these movements' goals is opening RAN interfaces (like the open fronthaul (O-FH)), to break the vendor lock-in of RAN resources. However, this raises concerns about RAN's security especially in elements that are bound to latency and performance requirements like the O-FH's synchronization plane (S-plane). In this article, we provide a comprehensive discussion of S-plane threats following O-RAN architecture, considering used synchronization protocols and mandatory security requirements. Further, we discuss the identified threats' impact on S-plane synchronization topologies and comment on possible countermeasures. Finally, we leverage O-RAN properties and benefits to propose future research directions for better S-plane security.

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 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.693
Threshold uncertainty score0.485

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.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.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.041
GPT teacher head0.321
Teacher spread0.279 · 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