The main list of test cases is available at E2E Network Slicing Use Case in R7 Guilin.
1. Common CSMF, NSMF
Venue: CMCC Lab
| S.No. | Category | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|---|
| COM_01 | Service/template design | Successful design of CST and Service Profile Templates | 1 | NOT YET TESTED | ||
| COM_02 | Service/template design | Successful design of NST (option 1 and option 2) | 2 | NOT YET TESTED | ||
| COM_03 | Service instantiation | Service instantiation via CSMF Portal (UUI) for Option 1 (RAN NSSMF within ONAP) resulting in NST Selection request from SO towards OOF, and receiving the NST details in the callback from OOF. | 3 | COM_01, COM_02 | NOT YET TESTED | |
| COM_04 | Service instantiation (Option 1) | After NST selection, NSMF (SO) fetches sub-net capabilities for the 3 constituent sub-nets (RAN, Core and Transport) for Option 1. | 3 | COM_03 | NOT YET TESTED | |
| COM_05 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing Slice Profiles (in callback API) for new NSI creation (Option 1). | 3 | COM_04 | NOT YET TESTED | |
| COM_06 | Service instantiation (Option 1) - New NSI | SO (NSMF) presents the NSI solution to NSMF Portal (UUI) for manual intervention. NSMF Portal (UUI) provides endpoints for RAN and Core sub-nets while allowing creation of new NSI. | 3 | COM_05 | NOT YET TESTED | |
| COM_07 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers RAN NSSMF with allocateNSSI operation via the NSSMF adaptor, and RAN NSSI is allocated successfully. | 3 | COM_06 | NOT YET TESTED | |
| COM_08 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSI is allocated successfully. | 3 | COM_06 | NOT YET TESTED | |
| COM_09 | Service instantiation (Option 1) - New NSI | NSMF (SO) triggers TN NSSMF with allocateNSSI operation via the NSSMF adaptor along with the RAN & Core endpoint info, and TN NSSI is allocated successfully. | 3 | COM_08 | NOT YET TESTED | |
| COM_10 | Service instantiation (Option 2) - New NSI | After NST selection, NSMF (SO) fetches sub-net capabilities for the 3 constituent sub-nets (RAN, Core and Transport) for Option 2. | 4 | COM_03 | NOT YET TESTED | |
| COM_11 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing Slice Profiles (in callback API) for new NSI creation (Option 2). | 4 | COM_10 | NOT YET TESTED | |
| COM_12 | Service instantiation (Option 2) - New NSI | NSMF (SO) calls OOF using selectNSSI API for the RAN NSSI selection (in case of external RAN NSSMF) with RAN Slice Profile and RAN sub-net capabilities. OOF provides (empty) response that no RAN NSSI exists (that can be reused). | 4 | COM_11 | NOT YET TESTED | |
| COM_13 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers External RAN NSSMF with allocateNSSI operation via the NSSMF adaptor (it also sends Slice Profile info), and new RAN NSSI is created successfully. RAN EP info is updated in AAI by NSMF Adaptor. | 4 | COM_12 | NOT YET TESTED | |
| COM_14 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers Core NSSMF with allocateNSSI operation via the NSSMF adaptor, and Core NSSI is allocated successfully. (This is more of a regression test case as new Core NSSI is already covered in COM_08) | 4 | COM_12 | NOT YET TESTED | |
| COM_15 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers TN NSSMF with allocateNSSI operation via the NSSMF adaptor along with the RAN & Core endpoint info, and TN NSSI is allocated successfully. (This is more of a regression test case as new Core NSSI is already covered in COM_09) | 4 | COM_14 | NOT YET TESTED | |
| COM_16 | Service instantiation (Option 2) - New NSI | NSMF (SO) calls OOF using selectNSSI API for the RAN NSSI selection (in case of external RAN NSSMF) with RAN Slice Profile and RAN sub-net capabilities. OOF provides response with a suitable RAN NSSI exists (that can be reused). | 5 | COM_11 | NOT YET TESTED |
Note:
2. RAN Slicing
Venue: Winlab
| S.No. | Category | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|---|
| RAN_01 | Service/template design | Successful design of RAN NSST, RAN NF NSST, RAN Slice Profile and RAN NF Slice Profile Templates | 2 | NOT YET TESTED | ||
| RAN_02 | Service instantiation (Option 1) - New NSI | Provide RAN subnet capabilities when queried by NSSMF adaptor | 3 | NOT YET TESTED | ||
| RAN_03 | Service instantiation (Option 1) - New NSI | When triggered by NSSMF Adaptor with allocateNSSI for allocating a new RAN NSSI, RAN NSSMF (SO) triggers OOF for RAN NSSI selection, OOF provides Slice Profiles for RAN NF, TN FH and TN BH NSSIs (i.e., creation of a new RAN NSSI). | 3 | COM_07 | NOT YET TESTED | |
| RAN_04 | Service instantiation (Option 1) - New NSI | SO (RAN NSSMF) creates new RAN NF NSSI and configuring it by calling SDN-R | 3 | RAN_03 | NOT YET TESTED | |
| RAN_05 | Service instantiation (Option 1) - New NSI | SDN-R updates Config DB with the details of the new RAN NSSI and S-NSSAI and other configuration details (e.g., RRM Policy, Slice Profile) for the new S-NSSAI | 3 | RAN_04 | NOT YET TESTED | |
| RAN_06 | Service instantiation (Option 1) - New NSI | SDN-R configures RAN NFs (CUs, DUs, Near-RT RICs) with the info related to the new RAN NSSI/S-NSSAI (by sending suitable messages to RAN-Sim) | 3 | RAN_04 | NOT YET TESTED | |
| RAN_07 | Service instantiation (Option 1) - New NSI | SO triggers |
3. Core Slicing
Venue: ???
| S.No. | Category | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|---|
| CORE_01 | Service/template design | Successful design of Core NSST, Core NF NSST, Core Slice Profile and Core Network Service | 2 | NOT YET TESTED | ||
| CORE_02 | Service instantiation | When triggered by NSSMF Adaptor with allocateNSSI for allocating a new Core NSSI, Core NSSMF (SO) triggers OOF for Core NSSI selection, OOF provides Slice Profiles for Core NF. | 3 | NOT YET TESTED | ||
| CORE_03 | Service instantiation (New NSSI) | SO (Core NSSMF) creates new Core NSSI in AAI | 3 | NOT YET TESTED | ||
| Prepare Service order and trigger EXTAPI for instantiating new Core NFs | 3 | NOT YET TESTED | ||||
| On successful response from EXTAPI for the serviceOrderId associate instantiated core network service to NSSI. And update SO database with service operation status | 3 | NOT YET TESTED | ||||
| CORE_04 | Service instantiation (Existing NSSI) | When triggered by NSSMF Adaptor with allocateNSSI for allocating a new Core NSSI, Core NSSMF (SO) triggers OOF for Core NSSI selection, OOF provides Slice Profiles for Core NF. | 3 | NOT YET TESTED | ||
| OOF returns existing NSSI. Find the associated network service with NSSI | 5 | |||||
| Prepare request payload to trigger SO macro flow to update the Core network service NFs | 5 | |||||
| Trigger SO macro flow (by calling serviceInstance api PUT method). | 5 | |||||
| On successful response update the SO database with service operation status | 5 | |||||
| CORE_05 | Service Activation and Service Deactivate | When triggered by NSSMF Adaptor with activateNSSI or deactivateNSSI for activating/deactivating Core NSSI | 7,8 | NOT YET TESTED | ||
| Get all s-nssai and orchestration status from slice profiles associated with NSSI | 7.8 | |||||
| Get VNF/VFs associated with NSSI. Prepare request payload to trigger SO macro service to activate/deactivate the status of s-nssai received from NSSMF adapter | 7.8 | |||||
| Onsuccessful response update slice profile instance in AAI | 7.8 | |||||
| CORE_06 | Service Deallocate | When triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI | 9, 10, 15 | NOT YET TESTED | ||
| Get the network service instance and slice profile associated with NSSI | ||||||
| If TerminateNSSI=true then | ||||||
| trigger EXPAPI to delete network service instance Remove NSSI association with NSI Remove association of slice profile instance with NSSI Delete the slice profile instance Delete NSSI service instance | ||||||
| Update SO database with operation status | ||||||
| CORE_07 | Service Deallocate | When triggered by NSSMF Adaptor with deAllocate for deallocating Core NSSI | 9 | NOT YET TESTED | ||
| Get the network service instance and slice profile associated with NSSI | ||||||
| If TerminateNSSI=false then | ||||||
| Get VNF/VFs associated with NSSI. Get all the s-nssai and orchestration status from the slice profiles associated with NSSI | ||||||
| Prepare request payload to trigger SO macro flow to update the Core network service NFs | ||||||
| Remove NSSI association with NSI Remove association of slice profile instance with NSSI Delete the slice profile instance | ||||||
| Update SO database with operation status | ||||||
| CORE_08 | Service Modify (create new slice profile instance) | When triggered by NSSMF Adaptor with modify for modifying Core NSSI | NOT YET TESTED | |||
| Get the network service instance and slice profile associated with NSSI | ||||||
| Get VNF/VFs associated with NSSI. Get all the s-nssai and orchestration status from the slice profiles associated with NSSI | ||||||
| Prepare request payload to trigger SO macro flow to update the Core network service NFs | ||||||
| On success response, create slice profile instance in AAI Associate slice profile instance with NSSI | ||||||
| Update SO database with operation status | ||||||
| CORE_09 | Service Modify (delete slice profile instance) | When triggered by NSSMF Adaptor with modify for modifying Core NSSI | NOT YET TESTED | |||
| Get the network service instance and slice profile associated with NSSI | ||||||
| Get VNF/VFs associated with NSSI. Get all the s-nssai and orchestration status from the slice profiles associated with NSSI | ||||||
| Prepare request payload to trigger SO macro flow to update the Core network service NFs | ||||||
| On success response, remove NSSI to slice profile association Delete the slice profile instance | ||||||
| Update SO database with operation status |
4. Transport Slicing
Venue: ???
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|
| TN_01 | Successful design of Transport NSST and Transport Slice Profile Templates | 1 | NOT YET TESTED | ||
| TN_02 | |||||
5. Interaction with external RAN and Core NSSMF
Venue: CMCC Lab
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|
| EXT_01 | 1 | NOT YET TESTED | |||
| EXT_02 | |||||
6. KPI Monitoring
Venue: CMCC Lab
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|
| KPI_01 | 1 | NOT YET TESTED | |||
| KPI_02 | |||||
7. Closed Loop
Venue: Winlab
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|
| CL_01 | RAN-Sim sends PM data fileReadyNotification | 1 | NOT YET TESTED | ||
| CL_02 | |||||
8. Intelligent Slicing
Venue: Winlab
| S.No. | Test Case Description | Reference to main TC | Dependency | Tester | Status |
|---|---|---|---|---|---|
| EXT_01 | 1 | NOT YET TESTED | |||
| EXT_02 | |||||