NSI Selection

Sequence diagram

Interfaces

1. NSI selection Request
   1. Input: Service profile
   2. NST details
   3. NSST details with subnet capabilities
   4. reuse: true/false
2. Fetch Optimization policies
   1. Demand policy for NSI and Slice profiles
   2. Constraint policies for Selection
   3. Optimization policies for NSI selection and slice profile generation.
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

Note:

For the non-shared scenario, Only slice profiles will be generated. HAS need not fetch the existing NSIs.

Demand

Candidates:

• NSI (AAI Inventory)
• Slice profiles (Generator)

Demand Examples:

Note: Creation cost will come from policy

List of Constraints

• Threshold Constraint (Matching NSI and slice profile tuple)

NSI Selection Policies

Demand Policy(NSI)

• Demand name(NST)
• For NSI 
  • inventory provider (AAI)
  • Inventory type(nsi)
  • filtering attributes
  • Uniqueness
  • Passthrough attributes
• For Slice profiles
  • inventory provider (Generator)
  • Inventory type(slice_profiles)
  • filtering attributes
  • Uniqueness
  • Passthrough attributes

Threshold Policy

• Demand name(NST)
• List of Constraints

Query policy

• Existing (All service profile parameters)

Optimization policy

• minimize latency
• maximize throughput
• minimize creation cost
• maximize creation cost

HAS Candidates

NSI candidate

Slice profiles Candidate

Consumed APIs (AAI)

GET NSI info from AAI

???