Intent-driven Deployment

What Is Intent-driven Deployment?

Intent-driven deployment integrates Huawei's network planning expertise to create a knowledge base. By inputting network intents, customers receive customized solutions automatically. The system self-learns from customer modifications, adapting to dynamic network environments. This boosts deployment efficiency, reduces costs, and minimizes errors.

Why Do We Need Intent-driven Deployment?

The CloudCampus Solution follows a standardized network deployment process, which includes the following steps:

• 1. Prepare a technical proposal based on the customer's network requirements, encompassing factors like customer flows, access quantity, and areas. This involves network design, device model selection, networking model determination, and service planning.

• 2. Carry out low-level design (LLD) after finalizing the solution. This includes planning device names, topology, VLANs, device links, IP addresses, WLAN, and providing construction guidance.

• 3. Onboard devices in plug-and-play mode, followed by configuring VLANs, interfaces, subnets, and WLAN services individually on iMaster NCE-Campus.

However, this process often results in repetitive work for customers, as the technical proposal, LLD document, and iMaster NCE-Campus configurations are separate and independent. To address this, intent-driven deployment offers a solution.

Intent-driven deployment facilitates intent conversion for customers. It generates professional network solutions based on customer-entered service-related and network-agnostic requirements, streamlining the configuration process and reducing learning costs. The system also possesses self-learning capabilities, allowing it to incorporate customer-driven solution modifications into its AI module for continuous improvement and adaptation to dynamic network environments.

Another advantage of intent-driven deployment is ESN-free deployment. With ESN-free deployment, customers no longer need to record precise equipment serial numbers (ESNs) for each device. Instead, they can simply follow the device models provided in the construction guide. As long as the root device is onboarded, all devices on the network can go online. When a downstream device is powered on, it transmits its ESN to the root device through Link Layer Discovery Protocol (LLDP). The root device then shares the link and ESN information with iMaster NCE-Campus, which fills in the ESN based on available link information in the controller system.

How Does Intent-driven Deployment Work?

Intent-driven deployment optimizes the entire process of pre-sales solution communication, order placement reference, construction, and network service deployment, ensuring consistency throughout. It eliminates redundant communication and enhances service deployment efficiency. The implementation of intent-driven deployment involves the following steps:

• 1. The system recommends a pre-set or AI-learned standard network solution based on the customer's network requirements. This solution includes networking, device selection, service network configuration, IP address planning, and allows for customization.

• 2. The system automatically generates a technical proposal based on the recommended network solution, streamlining the pre-sales solution communication process.

• 3. The system automatically generates a Low-Level Design (LLD) document, simplifying the construction process.

• 4. The system generates a solution package that can be imported with a single click to facilitate seamless service deployment.

Customers input their intents on the cloud platform, which are transformed into a network solution for confirmation. The solution can be modified, improving subsequent recommendations. The system generates three items for the customer: a technical proposal, an LLD document, and a deployment solution package.