Versions Compared

Key

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

...

Instantiation - Should involve call to NSMF, calls to NSSMFs (allocate or modifyNSSI API calls), and then SB calls/actions on NSSI constituents. In case of RAN NSSI, it should involve calls to TN (for FH and MH) and RAN NF NSSI creation/update.


Note: TN NSSMF supports reuse of TN NSSI only when the NSI is reused. This is because, the interface from SO (TN NSSMF) to OOF for TN NSSI selection is not yet implemented.


S.No.PriorityInput serviceNSIRAN NSSICore NSSITN BH NSSITesterStatusRemarks
a1

eMBB like service parameters

No sharing

NewNewNewNew

Status
colourYellow
titleIN PROGRESS


b1

eMBB like service parameters

Sharing allowed

NewNewNewNew

Status
colourYellow
titleIN PROGRESS

Pre-requisite: There is no existing shareable suitable NSI or NSSIs
c1

eMBB like service parameters

Sharing allowed

ReuseXXX

Status
colourYellow
titleIN PROGRESS

X = automatically all NSSIs are reused
d1

eMBB or mMTC like service parameters

Sharing allowed

NewReuseNewNew

Status
titleNOT STARTED

Pre-requisite: There is an existing RAN NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way RAN NSSI is reused, or creating a suitable and shareable RAN NSSI upfront.
e1

eMBB or mMTC like service parameters

Sharing allowed

NewNewReuseNew

Status
titleNOT STARTED

Pre-requisite: There is an existing Core NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way Core NSSI is reused, or creating a suitable and shareable Core NSSI upfront.
f2

eMBB or mMTC like service parameters

Sharing allowed

NewNewReuseNew

Status
titleNOT STARTED

Pre-requisite: There is an existing RAN & Core NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way RAN & Core NSSI are reused, or creating suitable and shareable RAN & Core NSSIs.
g2

eMBB or mMTC like service parameters. with coverageArea more than what is already supported in a suitable existing and shareable NSI

Sharing allowed

NewNewNewNew

Status
titleNOT STARTED

Pre-requisite: There should be a suitable existing NSI that is shareable, but whose coverageArea is smaller or does not have full overlap with the new service request. 

...