| S.No | Topic | Description | Dependency | Tester | Status | Remarks | Test Details |
|---|
| 1 | Service Instantiation(new ran nssi) | OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping | OOF | | NOT STARTED | Prerequisite: CPS needs to be preloaded with coverage Area TA list |
|
| 2 | Service Instantiation(new ran nssi) | SDNR integration with CPS - allocate flow: CPS should be updated with the RAN configurations | SDN-R, CPS | | | TBDMT templates should be preloaded |
|
| 3 | Service Instantiation (new RAN NSSI) | SDN-R configures RAN NFs via O1. All NFs and the cells should be updated with the proper configuration | SDN-R, CPS, RANSimulator | | |
|
|
| 4 | Service Instantiation(reuse existing ran nssi) | OOF should return slice profiles with Coverage Area to coverageAreaTAList mapping | OOF | | NOT STARTED | Prerequisite: CPS needs to be preloaded with coverage Area TA list |
|
| 5 | Service Instantiation(reuse existing ran nssi) | SDNR integration with CPS - modify allocate flow: CPS should be updated with the RAN configurations | SDN-R, CPS | | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | NOT STARTEDcompleted |
|---|
|
| Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, - Configure SDN-R to support Config DB (ran-slice-api-dg.properties)
- Trigger (UUI) and complete the allocate flow with ConfigDB
- Manually preload the initial RAN NF configuration and RAN Slice (RAN NF NSSI) configuration in CPS
- Configure SDN-R to support CPS (ran-slice-api-dg.properties)
- Trigger the E2E Slice shared flow from UUI
- Verify the results
|
|
| 6 | Service Instantiation(reuse existing ran nssi) | SDN-R sends relevant (netconf) messages to RAN-NFs and update the relevent cells | SDN-R, CPS, RANSimulator | | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | NOT STARTEDcompleted |
|---|
|
| Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, - Configure SDN-R to support Config DB (ran-slice-api-dg.properties)
- Trigger (UUI) and complete the allocate flow with ConfigDB
- Manually preload the initial RAN NF configuration and RAN Slice (RAN NF NSSI) configuration in
CPS and RAN Simulator- CPS
- Configure SDN-R to support CPS (ran-slice-api-dg.properties)
- Trigger the E2E Slice shared flow from UUI
- Verify the results
|
|
| 7 | Service Activation | Required details should be properly queried from CPS | SDN-R, CPS | | | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS |
|
| 8 | Service Activation | RAN Slice should be activated: status should be set to ACTIVE in honeycomb devices | SDN-R, CPS, RANSimulator | | | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS and RAN Simulator |
|
| 9 | Service Deactivation | Required details should be properly queried from CPS | SDN-R, CPS | | | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS |
|
| 10 | Service Deactivation | RAN Slice should be deactivated: status should be set to INACTIVE in honeycomb devices | SDN-R, CPS, RANSimulator | | | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS and RAN Simulator |
|
| 11 | Service Termination | Remove the RAN slice details from CPS from the applicable NFs | SDN-R, CPS | | | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS |
|
| 12 | Service Termination | Remove the RAN Slice from the RAN NFs and cells | SDN-R, CPS, RANSimulator | | | Prerequisite: 1. TBDMT templates should be preloaded 2. As RAN Slice allocate is not done, preload the RAN Slice configuration in CPS and RAN Simulator |
|