Versions Compared

Key

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

Table of Contents

Table of Contents

Abbreviations

AbbreviationsDescription
CNCore Network
NSINetwork Slice Subnet Instance
NSMFNetwork Slice Management Function
NSSMFNetwork Slice Subnet Management Function
RANRadio Access Network
TNTransport Network
UUIUser-to-User Information


1. NSI Instantiation

1.1. This sequence diagram shows the NSMF and NSSMF interactions for RAN Slicing Option 1, and when all NSSMFs are within ONAP.

Assumptions

...

  • RAN Option 1 or Option 2 shall be determined by NSMF by examining the NST contents.
  • NSMF shall determine if it has to do NSSI selection (in case of external NSSMF) for a domain by checking the vendor in the NSST

...

  • .
  • In case of internal NSSMF, the "<Domain> NSSMF" (domain = AN/TN/CN) shown in below figure shall be SO. SO (NSSMF) will further interact with other components (e.g. SDN-C/SDN-R/CDS) for domain-specific NSSMF actions.
  • Steps in Blue are applicable only in case of external NSSMF.

Notes in the figure

  1. Step 29b: NSSI id shall be passed from NSMF to NSSMF in case of (external) NSSMF that cannot do NSSI selection.

Gliffy
macroIddf839247-2bf0-42ba-b7f9-9df3f62ff1cb
displayNameNSI instantiation
nameNSI instantiation
pagePin

...

44


1.2. This sequence diagram shows the NSMF and NSSMF interactions for RAN Slicing Option 2, and when RAN and Core NSSMFs are outside ONAP.

Some of the key aspects are provided in above diagram in Section 1. We will prepare a separate diagram soon for clarity.

2. NSI/NSSI

...

Deallocation

...


Notes

  1. In G-release, OOF may simply check if there is only 1 Service Profile linked to the NSI (and assume it is linked to the NSI that is being queried for termination). In this case, Service Profile need not be passed as a parameter in the terminateNxI API towards OOF.
  2. In G-release, OOF may simply check if there is only 1 Slice Profile linked to the NSSI (and assume it is linked to the NSSI that is being queried for termination). In this case, Slice Profile need not be passed as a parameter in the terminateNxI API towards OOF.


Gliffy
macroId65943fa3-d459-4cb4-a270-bbd9d1e0e6d7
nameNSI_NSSI_Termination
pagePin14

Interface details

Actions

New APIs

...

Deallocate NSI api (NSMF)

Input: NSI details

Output: Terminating/Cannot terminate

Final output: Success/Failure with reason

...

Deallocate NSSI api (NSSMF)

Input: NSSI details

Output: Terminating/Cannot terminate

Final output: Success/Failure with reason

...

NxI Termination (OOF)

Input: NSI/NSSI details

Output: Yes/No with reason

Consumed APIs (Existing)

  • Get related Service profile instance (AAI)
  • Get related NSI (AAI)
  • Get NSSI details related to NSI (AAI)
  • Delete NSI-NSSI relationship (AAI)
  • Delete NSI/NSSI entry from AAI (AAI)


Old diagram - just for reference (not to be used, please refer to the diagram above for NSI deallocation)

Drawio
bordertrue
diagramNameNSI termination
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth850
revision8