Test Lab: Win Lab, Rutgers University
Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
RAN NSSMF with CPS
| 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 | Sandeep Shah |
| 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 | Sandeep Shah |
| ||||||||||
| 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 | Ahila P |
| TBDMT templates should be preloaded | |||||||||
| 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 | Ahila P |
| ||||||||||
| 7 | Service Activation | Required details should be properly queried from CPS | SDN-R, CPS | YASHWANTH GANDHAPU |
| ||||||||||
| 8 | Service Activation | RAN Slice should be activated: status should be set to ACTIVE in honeycomb devices | SDN-R, CPS, RANSimulator | YASHWANTH GANDHAPU |
| ||||||||||
| 9 | Service Deactivation | Required details should be properly queried from CPS | SDN-R, CPS | YASHWANTH GANDHAPU |
| ||||||||||
| 10 | Service Deactivation | RAN Slice should be deactivated: status should be set to INACTIVE in honeycomb devices | SDN-R, CPS, RANSimulator | YASHWANTH GANDHAPU |
| ||||||||||
| 11 | Service Termination | Remove the RAN slice details from CPS from the applicable NFs | SDN-R, CPS |
| |||||||||||
| 12 | Service Termination | Remove the RAN Slice from the RAN NFs and cells | SDN-R, CPS, RANSimulator | Hariharan Ramanathan |
|
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
NSMF driven TN Slices
| S.No | Topic | Description | Dependency | Tester | Status | Remarks | Test Details | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Option2 template creation | Design option2 templates in SDC and distribute it to SO & AAI | SDC, SO, AAI |
| |||||||
| 2 | Service Instantiation (Shared Scenario) | Instantiate service instance for option2 template with resource sharing level shared | SO, OOF, AAI | krishna moorthy |
| ||||||
| 3 | Service Instantiation (Non shared Scenario) | Instantiate service instance for option2 template with resource sharing level non shared | SO, OOF, AAI |
|
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Closed Loop with CPS
| S.No | Topic | Description | Dependency | 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 |
| ||||||||
| 2 | Generate PM data | DataFileCollector reads the VES notification, fetches the PM xml file from the VM (SFTP) and posts it in data router |
| ||||||||
| 3 | Generate PM data | PM Mapper reads the PM file from data router, generates PM events and posts in the message router |
| ||||||||
| 4 | Closed Loop | Slice Analysis MS reads the message from message router and triggers Control Loop action towards Policy for throughput update |
| ||||||||
| 5 | Closed Loop | Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources. |
| ||||||||
| 6 | Closed Loop | Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R for updating the throughput per Near-RT RIC. |
| ||||||||
| 7 | Closed Loop | Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim. |
| ||||||||
| 8 | Reconfigure | RAN-Sim updates DB and netconf servers. |
|
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Closed Loop with Intelligent Slicing
| S.No | Topic | Description | Dependency | Tester | Status | Remarks | Test Details | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Generate PM data | Generate intelligent slicing PM data in Ransim and send VES notifications. |
| ||||||||
| 2 | ML MS action | ML microservice reads the message, calculates the maxNumberofConns per cell and posts the data on message-router. |
| ||||||||
| 3 | Slice Analysis MS action | Slice Analysis MS receives updates to maxNumberofConns per cell for each S-NSSAI from ML-MS and triggers Policy for Control Loop action |
| ||||||||
| 4 | Closed Loop | Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources. |
| ||||||||
| 5 | Closed Loop | Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R. |
| ||||||||
| 6 | Closed Loop | Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim (Near-RT RIC) successfully. |
| ||||||||
| 7 | Reconfigure | RAN-Sim updates DB and netconf servers. |
| ||||||||
KPI Monitoring
| S.No | Topic | Description | Dependency | Tester | Status | Remarks | Test Details |
|---|---|---|---|---|---|---|---|
| 1. | KPI policy type and policy instance | Create Kpi policy type and Kpi policy instance and deploy the policies. | Policy | Completed | |||
| 2. | Config Fetch from policy | Mention the deployed policy-id in the pom.xml of kpi-ms and the corresponding policy is fetched using the policy sidecar container during deployment and placed inside the kpi-ms container. And during the startup of the microservice the config is fetched from the policy. | Policy | Hariharan Ramanathan | Completed | Earlier the "kpi.config" was fetched from the app-config/application_config.yaml and stored in the variable kpiConfig inside the code and now when the config is fetched using the policy the config is overridden with the config fetched from policy. | |
| 3. | Configurable Kpi Config. | By updating the SDK version to 1.8.6 in pom.xml of KPI-MS, the config is configurable in run-time .By changing the Kpi-config value in the policy inside the /etc/policies/policy.json , the Config gets updated in the code without the need to redeploy the application. | Cbs-client | Hariharan Ramanathan | Completed | ||