Legend:
| Status | ||
|---|---|---|
|
E2E Integration Tests
- Instantiation - create new NSI (not-shared, no match with shared, all matching are not-shared, different coverageArea so not matching)
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - new
- RAN NF NSSI - new, ??
- RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - new
- RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - new
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - reuse
- RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - new
- RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - reuse
- RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - reuse
- RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - reuse (but all 3 are not part of same NSI, otherwise that NSI would have been reused)
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - new
- Instantiation - reuse existing NSI
- Activation
- Deactivation
- Termination
Test Automation
Option 1: RAN NSSMF shall be responsible for entire RAN subnet, including RAN NFs, FH and MH. All 3 NSSMFs are within ONAP.
| S.No. | Topic | Description | Dependency | Tester | Status | Remarks | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1. | Service Design | 1a. Design of CST, and necessary templates for 1 type of service (e.g., eMBB): NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles 1b. Design of necessary templates for 2nd type of service (e.g., mMTC): NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles |
| |||||||
| 2. | Service instantiation | |||||||||
Option 2: RAN NSSMF shall be responsible for RAN NFs alone. FH and MH are not included. Only TN NSSMF is within ONAP.
Note: Core NSSMF can be inside ONAP or outside ONAP for this Option. Only RAN NSSMF has to be outside ONAP.
...