Business Intent

Business Intent expresses what the enterprise needs, not how the network should achieve it. A declaration such as 'prioritize video conferencing traffic' specifies a desired business outcome—maintaining collaboration quality—without referencing QoS markings, queueing disciplines, or DSCP values. This decoupling allows the underlying intent engine to select optimal technical implementations based on current network state, available resources, and competing demands. The declaration remains stable even as the underlying infrastructure evolves, preserving the business logic across hardware refreshes and topology changes.

Business Intent is expressed using enterprise-domain language that business stakeholders understand, completely free of vendor-specific syntax or protocol-level terminology. Key characteristics include:

• No device references: Intent never specifies routers, switches, or firewalls by name or role
• No protocol details: BGP, OSPF, VLAN IDs, and port numbers are absent from the declaration
• Measurable outcomes: Intent includes quantifiable service-level objectives such as 'sub-50ms latency' or '99.999% availability'
• Temporal scope: Intent may specify time-bound requirements like 'during trading hours' or 'for the fiscal quarter-end close' This abstraction enables the same intent to be fulfilled across heterogeneous, multi-vendor environments without modification.

A declared Business Intent creates a persistent, closed-loop contract between the business and the network. The intent assurance function continuously monitors operational state against the declared outcome, not merely checking that configurations were pushed correctly. If video conferencing quality degrades despite correct QoS policies being in place—perhaps due to unexpected congestion on a backup link—the assurance loop detects the intent drift and triggers automated remediation. This binding transforms network management from a configuration-centric model to an outcome-verification model, where compliance is measured at the business experience layer rather than the device configuration layer.

Business Intent serves as the authoritative input for resolving resource contention across the enterprise. When multiple intents compete—such as 'prioritize video conferencing' conflicting with 'guarantee backup replication bandwidth'—the intent conflict resolution engine uses business-level priority metadata attached to each intent to arbitrate. This arbitration occurs at the policy level before any technical translation, ensuring that resource allocation decisions reflect business priorities rather than network-level heuristics. The resolution may produce a negotiated intent that partially satisfies both demands according to weighted business importance, with the trade-off explicitly logged for auditability.

Business Intent provides the governance framework for the entire IBN lifecycle. Each intent progresses through a formal intent state machine with stages including:

• Declaration: Business stakeholder authors the intent in domain language
• Validation: The intent engine checks for logical consistency and resource feasibility
• Translation: Algorithmic conversion to device-specific configurations
• Fulfillment: Orchestrated deployment to infrastructure
• Assurance: Continuous monitoring and drift detection
• Decommissioning: Orderly removal when the business need expires This lifecycle ensures that every technical configuration in the network traces back to an active, authorized business requirement, eliminating configuration sprawl and orphaned policies.

A single Business Intent declaration can span multiple network domains—campus, WAN, data center, and cloud—without the business stakeholder needing to understand these boundaries. The intent 'ensure PCI-compliant segmentation for payment processing' applies uniformly whether the transaction traverses a retail store switch, an MPLS backbone, or a public cloud virtual network. The intent translation engine decomposes this unified declaration into domain-specific sub-intents, each fulfilled by the appropriate domain controller. This cross-domain coherence ensures that end-to-end business policies remain consistent regardless of the underlying administrative or technological boundaries.