Versions Compared

Old Version 3

changes.mady.by.user Swaminathan Seetharaman

Saved on

compared with

New Version 4

changes.mady.by.user Swaminathan Seetharaman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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

: 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, ???

Reuse of existing NSIReuse of existing NSSI





Notion of capacity (soft, hard)

...