MétaCan
Menu
Back to cohort
Record W2575192927 · doi:10.5555/3375069.3375118

LLDP Based Link Latency Monitoring in Software Defined Networks

2016· article· en· W2575192927 on OpenAlexaff
Lingxia Liao, Victor C. M. Leung

Bibliographic record

VenueConference on Network and Service Management · 2016
Typearticle
Languageen
FieldComputer Science
TopicSoftware-Defined Networks and 5G
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsNetwork packetForwarding planeOpenFlowLatency (audio)Computer scienceComputer networkSoftware-defined networkingReal-time computingEmbedded systemTelecommunications

Abstract

fetched live from OpenAlex

Current latency monitoring approaches for Software Defined Network often use the control plane as the infrastructure to inject time-stamp data packets as probe packets to measure the network latency at a particular time, but suffer from three major issues when the network latency needs to be continuously monitored: 1) the increased control plane's overhead, 2) the feasibility of using data packets as probe packets, and 3) the increasing measurement error using OpenFlow messages to measure the time from the controller to a switch as the network scale grows. To overcome these issues, this paper proposes link latency monitoring using time-stamped Link Layer Discovery Protocol (LLDP) packets, aided by a linear calibration function to reduce errors of measuring switch-controller delays. Time-stamping LLDP packets, which are used to discover the global network topology in SDNs, does not add extra workload to the control plane and the results always reach the controller thus while avoiding measurement failures that might occur in existing approaches. Our linear calibration function can reduce the measurement error to less than 5\% of the link latency measured by ping in a network with up to 30 switches and the link latency not less than 1ms.

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 imitation

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

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.005
Version: metacan-v3-hybrid-931329e0061cValidation 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.003
Threshold uncertainty score0.010

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.005
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.001
Science and technology studies0.0000.000
Scholarly communication0.0010.002
Open science0.0010.001
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.026
GPT teacher head0.227
Teacher spread0.202 · 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 source (direct Gemma or distilled Codex), 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

Citations16
Published2016
Admission routes1
Has abstractyes

Explore more

Same venueConference on Network and Service ManagementSame topicSoftware-Defined Networks and 5GFrench-language works237,207