AI & ML
How Far Can Lightweight LLMs Go in Intent-to-SLO Translation?
arXiv cs.NI0 views
arXiv:2611.07982v1 Announce Type: new Abstract: Intent-based networking (IBN) promises QoS provisioning in which the network derives the configuration from operator-stated goals. Its first step, translating a natural-language intent into enforceable service-level objectives (SLOs) grounded in a live snapshot of the network state, increasingly relies on large language models (LLMs). These large models add cost and energy to the management loop and typically require multi-GPU, cloud-hosted infrastructure. Can lightweight open LLMs take over this step dependably? We answer this question with a five-dimensional evaluation of ten LLMs with <10B parameters from five families, under four prompting setups, on 716 placement intents. We evaluate translation performance, intent validation, hallucination, energy impact, and robustness to diverse phrasing. The best configurations translate intents with a strict F1 of 0.943 and reject up to 191 of 195 invalid intents. With few-shot reasoning, the strongest models hallucinate unsupported QoS requirements in only about one response in a hundred, whereas the zero-shot setup struggles. A translated intent costs 0.044-0.148 Wh of GPU energy without reasoning, and added energy cost for reasoning pays off for the weaker models. Furthermore, we show that realistic rephrasing lowers the rejection of invalid intents in 15 of 16 configurations for the best-performing models, leaving robust intent validation as a key open challenge for reliable IBN. Our code and data are available: https://github.com/ggck43/intent2slo.
Source:https://arxiv.org/abs/2611.07982PreviousInstantiating the Knowledge PlaneNextBeyond Quantum Messages: Toward Quantum-Native Network Functioning
Related posts
A small business running 8 projects on Claude Code for 30 days: rules ignored, projects crossing into each other, and what finally helped
0dev.to AI
L'IA trouve les peptides, la VR les révèle : pourquoi Antigravity change la donne pour la découverte de médicaments
0dev.to AI
Why Tesseract Fails on Cursive Handwriting (And How We Built a Two-Tier Vision Pipeline in Node.js)
0dev.to AI
OFX looks like XML. It isn't, and QuickBooks will reject it
0dev.to WebDev
Before You Buy GEO Monitoring Software, Build a 50-Line Baseline
0dev.to Python
Building Self-Improving AI Models Without Blinding Yourself to Failure
0dev.to Python