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 4 Next »

NSI Selection

Options while instantiating a new NSI that can be shared:

  1. This will have

Option 1Option 2
Instantiation of new (shareable) NSI

Instantiate the NSI (and constituent NSSI) so that it can cater to some additional dimensions, e.g., allow for 20% buffer (the 20% may come from Policy or be pre-configured).

Impacts: SO (NSMF and NSSMF), SDN-R/C ???

Instantiate it only with the required dimensions as required by the Service Profile
Reuse of existing NSI
  • Consider (static) spare capacity based on allocated resources and ability to cater to the new Service Profile. Good short-term solution.

Impacts: OOF (logic) - the 20% configuration should be accessible to both SO and OOF

(OR)

  • Consider (predicted) dynamic spare capacity (considering also peaks) and ability to cater to the new Service Profile. This will be a good long-term solution if implemented properly.

Impacts: DCAE (Slice Analysis MS - data analysis, API/interface for querying by OOF), OOF (query DCAE, logic)

  • Consider 
Reuse of existing NSSI

Points to consider

Which dimension attributes to consider - maxNumberofUEs, bandwidth, throughput, ???





Notion of capacity (soft, hard)

Current resource occupancy levels

Scaling and modification (expansion of coverage area, resource reallocation)

Re-use approach for allocation of "resources" for RAN and TN NSSI

  • No labels