Jira reference:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-635 |
|---|
|
Test lab: CMCC Lab for CL_01 - CL_04, and Winlab for CL_05 - CL_15
Legend:
IN PROGRESS DEFERRED COMPLETEDItalics - Regression test cases
Note: This includes test cases for KPI Computation (used for KPI Monitoring), Closed Loop and ML-based Closed Loop (Intelligent Slicing) features.
| S. No. | Topic | Test Case Description | Priority | Dependency/Issue | Tester | Status |
|---|
| CL_01 | KPI Computation | Creation of suitable policies for KPI computation - formulas, PM data items, etc. | 1 |
| | |
| CL_02 | KPI Computation | KPI computation MS fetches of relevant policies: Formulas and PM data items by KPI Computation MS | 1 |
| | |
| CL_03 | KPI Computation | KPI Computation MS fetches PM data from DMaaP (posted by PM Mapper). Note: For this test case, we should have a simulator that sends PM data based on which PM Mapper then posts on DMaaP, alternatively, PM Mapper output should be manually posted (simulated) on DMaaP. | 1 |
| | |
| CL_04 | KPI Computation | KPI Computation MS computes KPIs and posts the results on DMaaP | 1 |
| | |
| CL_05 | Closed Loop | PM data on DL/UL PRBs used for data traffic as reported by RAN-Sim (in a file) are posted on DMaaP by PM-Mapper. | 1 | To be checked | | |
| CL_06 | Closed Loop | RAN-Sim sends PM data fileReadyNotification to VES-Collector for RAN PM data | 1 | To be checked | | |
| CL_07 | Closed Loop | Slice Analysis MS triggers Control Loop action towards Policy for throughput update at Near-RT RIC level based on analysis of DL/UL PRB used for data traffic for each S-NSSAI | 1 |
| | |
| CL_08 | Closed Loop | Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources. | 1 | To be checked | | |
| CL_09 | Closed Loop | Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R for updating the throughput per Near-RT RIC. | 1 | To be checked | | |
| CL_10 | Closed Loop | Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim (Near-RT RIC) successfully. | 1 |
| | |
| CL_11 | Intelligent Slicing | PM data on PDU sessions requested, setup successfully and failed to setup reported by RAN-Sim (in a file) are posted on DMaaP by PM-Mapper. | 1 | To be checked | | |
| CL_12 | Intelligent Slicing | Slice Analysis MS receives updates to maxNumberofConns per cell for each S-NSSAI from ML-MS (onboarded just for flow testing and demo), and triggers Policy for Control Loop action | 1 |
| | |
| CL_13 | Intelligent Slicing | Upon reception of CL action from Slice Analysis MS, Policy triggers SO (RAN NSSMF) for reconfiguration of RAN resources. | 1 |
| | |
| CL_14 | Intelligent Slicing | Upon CL trigger from Policy, SO (RAN NSSMF) triggers SDN-R for updating the throughput per Near-RT RIC. | 1 | To be checked | | |
| CL_15 | Intelligent Slicing | Upon receiving the reconfiguration trigger from SO, SDN-R sends the config updates to RAN-Sim (Near-RT RIC) successfully. | 1 | To be checked | | |
...