MétaCan
Menu
Back to cohort
Record W4411143146 · doi:10.1109/mnet.2025.3577627

Enabling Scalability and Flexibility Into Network Routing Protocol Using Behavior Tree

2025· article· en· W4411143146 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 Network · 2025
Typearticle
Languageen
FieldComputer Science
TopicNetwork Packet Processing and Optimization
Canadian institutionsToronto Metropolitan University
FundersNational Key Research and Development Program of China
KeywordsComputer scienceComputer networkScalabilityRouting protocolZone Routing ProtocolEnhanced Interior Gateway Routing ProtocolFlexibility (engineering)Protocol (science)Routing (electronic design automation)Distributed computingDynamic Source RoutingHierarchical routingWireless Routing Protocol

Abstract

fetched live from OpenAlex

Current network routing protocol design is faced with novel challenges due to evolving network scale, various network service demands, and dynamic network states. However, the conventional finite state machine models lack both scalability and flexibility for the description of network routing protocol states. In this article, we enable scalability and flexibility into network routing protocol by exploring and exploiting behavior trees, where behavior trees can reformulate the network routing protocol by characterizing state transformation as action nodes. We first present a generic routing protocol architecture with a comparative analysis of the behavior tree, finite state machine, etc. Then, we propose an implementable functional scheme, which provides a foundation for extending the functionality and enabling flexible configurations towards the network routing protocol. Finally, we design two use cases to verify that behavior trees can effectively replace finite state machines and the excellent scalability of behavior trees in terms of routing protocols.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.602
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0010.000
Research integrity0.0000.000
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.028
GPT teacher head0.320
Teacher spread0.292 · 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