Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

General Intent Model and General Intent Interface Proposal:

Intent Analysis Server Proposal:

The Use Case Description:

Intent Analysis

Background:

     A video business Enterprise have local site and cloud site,  so they need a CLL VPN to support their daily office from local site to cloud site. And some times  they will trans a lot of videos from local to the cloud , they hope the service provider can support this high-flow transfer  to ensure their office  work.

Original Intent:

     An intent  for one CLL VPN  , from local site to cloud site,  and 1G banwidth. And sporadic high-flow transfer support.

Intent Analysis Servier:

     Intent analysis server receive the original intent ,  the intent have two parts, one to provision a CLL VPN with 1G bandwidth from local site to cloud site. Another to support the sporadic high-flow transfer. Based on the detection-investigation-definition-distribution-operation lifecycle of the intent. The original intent is decomposed to the two sub intents. 

     The service provision sub intent will be translate to the service provisioning call , Intent analysis server will call SO to  create the CLL instance.

     The service assurance sub intent will be translate to the closed-loop call . Intent analysis server will call DCAE(through configuration policy) to create the monitor logic for the CLL service and also call Policy to create the policy rules.( The logic will be based on the CCVPN-IBN use case.)


  • No labels