Intent-Based Networking (IBN) is an approach to network management that shifts the focus from manually configuring individual devices to specifying desired outcomes or business objectives, referred to as "intents".[1]
Description
editRather than relying on low-level commands to configure the network, administrators define these high-level intents, and the network dynamically adjusts itself to meet these requirements.[1] IBN simplifies the management of complex networks by ensuring that the network infrastructure aligns with the desired operational goals. For example, an implementer can explicitly state a network purpose with a policy such as "Allow hosts A and B to communicate with X bandwidth capacity" without the need to understand the detailed mechanisms of the underlying devices (e.g. switches), topology or routing configurations.[2]
Architecture
edit
Advances in Natural Language Understanding (NLU) systems, along with neural network-based algorithms like BERT, RoBERTa, GLUE, and ERNIE, have enabled the conversion of user queries into structured representations that can be processed by automated services.[3] This capability is crucial for managing the increasing complexity of network services. Intent-Based Networking (IBN) leverages these advancements to simplify network management by abstracting network services, reducing operational complexity, and lowering costs.
A proposed three-layered architecture integrates intent-based automation into network management systems. In the business layer, intents are based on Key Performance Indicators (KPIs) and Service Level Agreements (SLAs), reflecting business objectives.[3] The intent layer evaluates and re-plans actions dynamically, where a Knowledge module abstracts and reasons about intents, while an Agent interfaces with network objects to execute actions.[3] The data layer observes network objects, updates topology information, and interacts with the Knowledge and Agent modules to ensure accurate and timely responses to network changes. At the bottom, the network layer contains the physical infrastructure, transforming network data into a usable format for the intent layer to act upon.[3]
References
edit- ^ a b Ujcich, Benjamin E.; Bates, Adam; Sanders, William H. (June 2020). "Provenance for Intent-Based Networking". 2020 6th IEEE Conference on Network Softwarization (NetSoft). IEEE. pp. 195–199. doi:10.1109/NetSoft48620.2020.9165519. ISBN 978-1-7281-5684-2.
- ^ Sanvito, Davide; Moro, Daniele; Gulli, Mattia; Filippini, Ilario; Capone, Antonio; Campanella, Andrea (June 2018). "ONOS Intent Monitor and Reroute service: Enabling plug&play routing logic". 2018 4th IEEE Conference on Network Softwarization and Workshops (NetSoft). IEEE. pp. 272–276. doi:10.1109/NETSOFT.2018.8460064. ISBN 978-1-5386-4633-5.
- ^ a b c d e Zeydan, Engin; Turk, Yekta (May 2020). "Recent Advances in Intent-Based Networking: A Survey". 2020 IEEE 91st Vehicular Technology Conference (VTC2020-Spring). IEEE. pp. 1–5. doi:10.1109/VTC2020-Spring48590.2020.9128422. ISBN 978-1-7281-5207-3.