Test Lab: Win Lab, Rutgers University
Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
JIRA: REQ-1154 - Getting issue details... STATUS
E2E network slicing test
S. No | Test Case | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details | |
|---|---|---|---|---|---|---|---|---|---|
| 1. | Service/template design (Option1) | Design of CST, and necessary templates: NST, NSST for RAN, RAN NF, Core & TN, Service Profile and Slice Profiles | 1 | Deepika S | COMPLETED | ||||
| 2 | Service Instantiation (Option1) | Reuse existing TN BH NSSI | 1 | At least 1 service needs to be instantiated | Deepika S | COMPLETED | Pre-requisite: There is an existing TN BH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN BH NSSI is reused, or creating a suitable and shareable TN BH NSSI upfront. | ||
| 3 | Service Termination (Option1) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN BH NSSI | 1 | Service instantiation test case involving reuse should be completed | IN PROGRESS | This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN BH NSSI. | |||
| 4 | Service Instantiation with CPS (Option1) | Allocate a service - this should result in allocation of new NSI and associated new NSSIs. | 1 | Deepika S | COMPLETED | TBDMT templates should be preloaded | |||
| 5 | Service reuse with CPS (Option1) | Allocate a service - this should result in modifying the allocated NSI and associated NSSIs. | 1 | COMPLETED | At least 1 service needs to be instantiated | ||||
| 6 | Service Activation with CPS (Option1) | Activate a service - this should result in activation of new NSI and associated new NSSIs. | 1 | At least 1 service needs to be instantiated | |||||
| 7 | Service deactivation with CPS (Option1) | Deactivate a service - this should result in deactivation of new NSI and associated new NSSIs. | 1 | At least 1 service needs to be instantiated | |||||
| 8 | Service termination of a shared slice with CPS (Option1) | Terminate a service - this should terminate NSI but terminate only Core NSSI and TN BH NSSI, and not RAN NSSI. | 1 | This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to Core & TN BH NSSIs, but > 1 Slice Profile is linked to RAN NSSI. | |||||
| 9 | Service termination with CPS (Option1) | Terminate a service - this should terminate NSI and ALL associated NSSIs. | 1 | At least 1 service needs to be instantiated | |||||
| 10 | Service activation (Option 2) | Service activation from CSMF portal (UUI) resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF | 1 | Deepika S | At least 1 service needs to be instantiated | ||||
| 11 | Service deactivation (Option 1) | Service deactivation from CSMF portal (UUI) resulting in NSI Deactivation API called towards SO (NSMF). SO (NSMF) calls DeactivateNSSI APIs towards internal Core and Transport NSSMFs, and external RAN NSSMF | 1 | Deepika S | At least 1 service needs to be instantiated | ||||
| 12 | Service/template design (Option2) | Design of CST, and necessary templates: NST, NSST for RAN, Core & TN, Service Profile and Slice Profiles | 1 | Option2 - NSMF Driven TN Slices in Network Slicing | |||||
| 13 | Service instantiation (Option 2) - Reuse existing NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing details of existing NSI to be reused in the response. | 1 | At least 1 service needs to be instantiated | sravya sherla | ||||
| 14 | Service instantiation (Option 2) - Reuse existing NSI | NSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles. | 1 | At least 1 service needs to be instantiated | |||||
| 15 | Service instantiation (Option 2) - Reuse existing NSI | NSMF (SO) provides details of existing NSI and Slice Profiles to UUI (NSMF Portal) for manual intervention. Existing NSI is chosen via UUI (regression) | 1 | At least 1 service needs to be instantiated | sravya sherla | ||||
| 16 | Service instantiation (Option 2) - Reuse existing NSI | NSMF then calls modifyNSSI API towards RAN, Core and Transport NSSMFs with details of existing NSI to be reused and the respective Slice Profile NOTE: This involves reuse of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI | 1 | At least 1 service needs to be instantiated | sravya sherla | ||||
| 17 | Service instantiation (Option 2) - Reuse existing TN BH NSSI | Reuse existing TN BH NSSI | 1 | sravya sherla | Pre-requisite: There is an existing TN BH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN BH NSSI is reused, or creating a suitable and shareable TN BH NSSI upfront. | ||||
| 18 | Service instantiation (Option 2) - Reuse existing TN MH NSSI | Reuse existing TN MH NSSI | 1 | sravya sherla | Pre-requisite: There is an existing TN MH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN MH NSSI is reused, or creating a suitable and shareable TN MH NSSI upfront. | ||||
| 19 | Service instantiation (Option 2) - Reuse existing TN FH NSSI | Reuse existing TN FH NSSI | 1 | sravya sherla | Pre-requisite: There is an existing TN FH NSSI that is suitable and can be reused. This requires either providing the service parameters in such a way TN FH NSSI is reused, or creating a suitable and shareable TN FH NSSI upfront. | ||||
| 20 | Service activation (Option 2) | Service activation from CSMF portal (UUI) for Option 2 resulting in NSI Activation API called towards SO (NSMF). SO (NSMF) calls activateNSSI APIs towards internal Core and Transport NSSMFs, and internal RAN NSSMF NOTE: This involves activation of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI | 1 | At least 1 service needs to be instantiated | |||||
| 21 | Service deactivation (Option 2) | Service deactivation from CSMF portal (UUI) for Option 1/2 resulting in NSI Deactivation API called towards SO (NSMF). SO (NSMF) calls DeactivateNSSI APIs towards RAN, Core and Transport NSSMFs NOTE: This involves deactivation of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI | 1 | At least 1 service needs to be activated | |||||
| 22 | Service Termination (Option2) | Service termination from CSMF portal (UUI) for Option 2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should be terminated | 1 | At least 1 service needs to be instantiated | sravya sherla | ||||
| 23 | Service Termination (Option2) | SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO (NSMF). NOTE: This involves termination of RAN NF NSSI, CORE NSSI, TN BH NSSI, TN FH NSSI and TN MH NSSI | 1 | At least 1 service needs to be instantiated | sravya sherla | ||||
| 24 | Service Termination (Option2) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN BH NSSI | 1 | sravya sherla | This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN BH NSSI. | ||||
| 25 | Service Termination (Option2) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN MH NSSI | 1 | sravya sherla | This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN MH NSSI. | ||||
| 26 | Service Termination (Option2) | Terminate a service - this should terminate NSI but terminate only Core NSSI and RAN NSSI, and not TN FH NSSI | 1 | sravya sherla | This can happen when only 1 Service Profile is linked to NSI and 1 Slice Profile each is linked to RAN & CORE NSSIs, but > 1 Slice Profile is linked to TN FH NSSI. |
E2E network slicing test(using resource occupancy details)
S. No | Test Case | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details |
|---|---|---|---|---|---|---|---|---|
| 1 | Generate PM data | Generate closed-loop PM data in Ransim, store the XML files in VM and send VES notification. DataFileCollector reads the VES notification, fetches the PM xml file from the VM (using SFTP) and posts it in data router. PM Mapper reads the PM file from data router, generates PM events and posts the data in the message router(uses unauthenticated topic) | 1 | Niranjana Y | COMPLETED | This step is a prerequisite for steps 3-5 | ||
| 2 | Store PM data | Datalake-feeder reads the PM message and stores it in mongo DB. | 1 | Niranjana Y | COMPLETED | This step is a prerequisite for steps 3-5 | ||
| 3. | Retrieve PM data | Data Extraction Service reads the stored PM data from mongo DB. | 1 | Niranjana Y | COMPLETED | |||
| 4 | Service instantiation - Reuse existing NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing details of existing NSI to be reused based on the resource occupancy data received from DCAE(slice-analysis-ms). | 1 | At least 1 service needs to be instantiated | Niranjana Y | |||
| 5 | OOF requests for resource occupancy data | OOF (HAS) should fetch the resource occupancy details from DCAE (slice-analysis-ms). | 1 | Malarvizhi Paramasivam | ||||
| 6 | Get resource occupancy data | Slice analysis MS receives request from OOF for resource occupancy details. Slice-analysis requests DES (Data Exposure Service) for the PM data for a specific time interval, converts it into configuration data, aggregates and calculates the available resources for the requested slices and returns it back to OOF. | 1 | Niranjana Y | ||||
| 7. | Update candidate list in HAS | HAS finds the difference between the response from DCAE and the requested config in service/slice profile and adds the difference attributes to the candidate list for the optimization based on the found difference value. | 1 | Malarvizhi Paramasivam | ||||
| 8. | Return solution to SO | HAS runs the optimization to choose the suitable NSI/NSSI. The selected NSI/NSSI is returned to OSDF, which forwards it to SO. | 1 | Malarvizhi Paramasivam |