Intent creation

For the MVS, we have simplified the creation of intents by providing templates for the two types of intents that can be handled in the use case (network configuration and workload deployment). We have also provided a template for the combination of the two in one single intent (meaning that the intent contains expectations for both the network and the deployment). The templates are conformant with the TM Forum Intent Ontology. An overview of the structure of intents following the TM Forum Intent ontology is shown in the image below.

To accurately define network QoS expectations in the intent template, the following parameters must be extracted or deduced from the dialogue with the customer:

1. The expected end-to-end latency (in milliseconds) for the workload
2. The required bandwidth (in Mbps) for the workload
3. The geographical area where the network slice should be valid (geo polygon)
4. Additional considerations (e.g., sustainability goals, cost constraints, or other future requirements)

To properly specify deployment expectations in the intent template, the following details must be established:

1. The edge data center where the workload will be deployed
2. The required compute latency for the workload
3. The workload to be deployed (unique ID from the catalog)
4. The workload deployment descriptor URL (also available in the catalog)

We have created a PoC workload catalog with an API that can be used to retrieve the workload details needed in the intent deployment template (Click on the "View catalog" button to see the front end for the "Workload catalog". The API is described in the ChartMuseum documentation. Our 5G4Data workload catalog frontend uses ChartMuseum as the backend.)

When a high level intent with the needed high level expectation(s) have been created, it is time for inChat to send it to inSwitch, and when inSwitch has created the needed lower level intent(s) it is time to send them to inNet and inOrch. TM Forum has designed an intent management API that can be used. Click the next button to get to know more about that (and yes, we have created a reference implementation)