Page History

...

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. NSI Solution
   1. Selected NSI candidate
7. Slice profile generation request - HAS
   1. Demands: Slice profiles
   2.  Constraints: Threshold constraint, CrossDemandAggregation constraint
   3. Optimization:  Maximize/minimize the service profile parameters
8. Generate slice profiles as candidates and select a suitable set of slice profiles
9. Slice profile Solution
10. Consolidated Solution based on the policy

...

{"URLLC":[{"inventory_provider":"aai","inventory_type":"nsi","unique":"true", "passthrough_attributes": {"creation_cost": 0}, "filtering_attributes":{"service-role":"nsi","model-invariant-id":"21d57d4b-52ad-4d3c-a798-248b5bb9124a","model-version-id":"bfba363e-e39c-4bd9-a9d5-1371c28f4d22"}}, {"inventory_provider":"generator","inventory_type":"slice_profiles","unique":"true", "passthrough_attributes": {"creation_cost": 1.0},"filtering_attributes":{}}]}

Note: Filtering attributes will have the upper and lower bounds for each subnet(based on capability set and service profile)

Note: Creation cost will come from policy

{
"core": {"latency": {"min": 5, "max": 20, "steps": 1}, "reliability": {"values": [99.9, 99.999]}},
"ran": {"latency": {"min": 10, "max": 20, "steps": 1}, "reliability": {"values": [99.9, 99.9]}},
"transport": {"latency": {"min": 7, "max": 20, "steps": 1}, "reliability": {"values": [99.9, 99.99]}}
}

...

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

{
"candidate_id": "1ac71fb8-ad43-4e16-9459-c3f372b8236d",
"candidate_type": "nsi",
"inventory_type": "nsi",
"inventory_provider": "aai",
"cost": "1","uniqueness": "true","current_availability": {
},"passthrough_attributes": {"creation_cost": 0}}

Slice profiles Candidate

{
"candidate_id": "1ac71fb8-ad43-4e16-9459-c3f372b8236d",
"candidate_type": "slice_profiles",
"inventory_type": "slice_profiles",
"inventory_provider": "generator",
"cost": "1",

"uniqueness": "true",
"subnet_requirements": {
"core": {},
"ran": {},
"transport": {}
},
"slice_requirements": {}
"passthrough_attributes": {"creation_cost": 0}

}

Consumed APIs (AAI)

GET NSI info from AAI

???