Table of Contents
Abbreviations
| Abbreviations | Description |
|---|---|
| CN | Core Network |
| NSI | Network Slice Subnet Instance |
| NSMF | Network Slice Management Function |
| NSSMF | Network Slice Subnet Management Function |
| RAN | Radio Access Network |
| TN | Transport Network |
| UUI | User-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
- Step 29b: NSSI id shall be passed from NSMF to NSSMF in case of (external) NSSMF that cannot do NSSI selection.
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
- 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.
- 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.
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)