NST Selection

Interfaces

1. NST selection Request
   1. Input: Service profiler parameters.

      {

      "requestInfo":{

      "transactionId":"c86b3019-39f4-4cd3-b847-b22afe9f36dc",

      "requestId":"c86b3019-39f4-4cd3-b847-b22afe9f36dc",

      "sourceId":"so",

      "timeout":600,

      "callbackUrl":"http://0.0.0.0:9000/callback/"

      },

      "serviceProfile":{

      "serviceProfileParameters":{

      "latency":20,

      "areaTrafficCapDL" : 10000,

      "coverageAreaTAList" : "India"
      }

      }

      }

2. Fetch Optimization policies
   1. vnfPolicy - it will identify the inventoryProvider and inventoryType - Forms demand policy.
   2. Attribute policy - for storing the serviceprofileparameters and its value as attribute - value pair- Constraint policy.
   3. QueryPolicy -  Its used to query the serviceprofileparameters from the input so that it can be added as a value to the attribute.
   4. Optimization policies if required.
3. NSI selection request - HAS
   1. Demand: NSI
   2. Constraint: Threshold policy, New policy(for CoverageArea )??
   3. Optimization: Maximize/minimize the service profile parameters
4. Fetch NSI for AAI
   1. Input: NST info
   2. Output: List of NSIs as candidates
5. Run Optimization
6. Consolidated Solution based on the policy
   1. Solution List. Solution object can have NSI/Slice profiles

NST Template example

Formed candidates:

A new dict candidate is formed. Then all the keys and values from the above template are added. Apart from these new keys inventory_provider,  'inventory_type' , 'candidate_id' , 'cost' are also added.