The integration testing shall be was done in Winlab at Rutgers University.
Important Note: All Regression flows (=>test cases) which have no relevance/interaction to the enhancements done in Guilin release have been deferred from the official Integration Testing scope for Guilin. However, we will continue the testing to cover the regression scenarios for a formal use case demo after Guilin release, but it has no bearing on Guilin Integration Test completion.
| S. No. | Description | Involved components | Status | Remarks | ||||||||
| 1 | Successful Control Loop trigger for PCI collision/confusion (Regression Test) | SON-Handler MS, VES, OOF, Policy, SDN-R, RAN-Sim, Config DB |
| Regression test, not critical for Guilin. Testing will continue beyond Guilin for a demo. Note: Actual testing is in progress, but has no impact for Guilin scope. | ||||||||
| 2 | Successful Control Loop trigger for ANR update based on PM data (Regression Test) | SON-Handler MS, VES, OOF, Policy, SDN-R, RAN-Sim, Config DB |
| Guilin enhancements don't have any interaction with this functionality. Testing will be done completion of Guilin integration test for a demo. Note: Actual testing is in progress, but has no impact for Guilin scope. | ||||||||
| 3 | SON-Handler MS and SDN-R to include the relevant fields in the control loop request/response messages for Policy to correlate the request and the response (Regression Test) | SON-Handler MS, Policy, SDN-R, RAN-Sim |
| Guilin enhancements don't have any interaction with this functionality. Testing will be done completion of Guilin integration test for a demo. | ||||||||
| 4 | After execution of the Control Loop (CL) and getting (N)ACK from SDN-R, Policy to successfully send back the result of the CL execution (success or failure, with relevant details) to SON-Handler MS In DCAE (Regression Test) | SON-Handler MS, Policy, SDN-R, RAN-Sim |
| Regression test, Guilin enhancements don't have any interaction with this functionality. So it will be tested with the complete flow, after completion of Guilin integration test | ||||||||
| 5 | Successful storage of PM data reported by RAN-Sim onto Mongo DB | RAN-Sim, DFC, VES Collector, Mongo DB |
| Completed by storing it manually. Fully automated flow will depend on Data Lake Feeder MS, which will be considered for Honolulu (no impact to this use case). | ||||||||
| 6 | Define the required sql templates in DES MS that are needed for fetching PM data by OOF | DES MS |
| |||||||||
| 7 | When triggered for PCI optimization, OOF (OSDF) to fetch the required PM data from datalake (Mongo DB) using the DES MS API | OOF, SON-Handler MS, DES MS, Mongo DB |
| |||||||||
| 8 | When triggered for PCI optimization, OOF (OSDF) to employ (offline trained) ML model to update the list of cells whose PCI values should be fixed during PCI optimization | OOF, SON-Handler MS |
| |||||||||
| 9 | End-to-end flow for PCI optimization involving ML | SON-Handler MS, VES, OOF, Policy, SDN-R, RAN-Sim, Config DB |
| Major part should be covered by previous test cases 1, 4-8. This is just an e2e test, and will be done for the e2e demo after Guilin release. |