The Base PCI (SON) Wiki is at: 5G - OOF and PCI (Casablanca carry-over items)
...
- Onboard RAN-Simulator as an official ONAP component (e.g., as part of Demo VNFs repo or Integration test repo),
- Contribute to ConfigDB (or RuntimeDB) enhancements for SON use case (including any impacts in SON-Handler MS, OOF and SDN-C) => this scope currently only includes yang model driven automatic Config DB schema and API generation.
2. Alignment with O-RAN
- Netconf config (O1-CM interface), yang model sourced from OIM => this is now de-scoped as we don't have yang models from O-RAN as of Jan 20th, 2020
- VES messages for config-update notifications also => the scope only includes reception of DMaaP message by SDN-R that would be triggered when RAN sends a VES config-update message. The real VES message sending as well as reception by VES Collector in DCAE is de-scoped as we don't yet have the VES message definition from O-RAN.
3. Control Loop Co-ordination (CLC)
Demonstrate CLC with PCI and ANR CLs
...
Test cases
| No. | Description | Status | ||||
1 | Successful storing of PCI and neighbor list datareception and handling of DMaaP message by SDN- C in Runtime DBR with CM notification from RAN. | NOT YET TESTED | ||||
2 | Successful fetching of PCI and neighbor list data from Runtime DB by SON-Handler MS | NOT YET TESTED | 3 | Successful fetching of PCI and neighbor list data from Runtime DB by OOF update of ConfigDB with CM notification updates by SDN-R (upon reception of CM notification over DMaaP from RAN) | NOT YET TESTED | 4 | Successful update of HO blacklist indication by SDN-C in Runtime DB
3 | Control Loop co-ordination – queuing of 2nd control loop trigger (by Policy) received from SON-Handler MS when first control loop is active | NOT YET TESTED | ||||
| 5 | Successfully bring RAN-Sim online and interface with SDN-C | NOT YET TESTED | ||||
| 6 4 | Control Loop Coco-ordination scenario - e.g., defer a control loop until another one acting on the same PNF gets completed– de-queuing of 2nd control loop trigger (by Policy) and initiating appropriate actions | NOT YET TESTED | 7 | Successful interaction between SDN-C and RAN-Sim using the O-RAN aligned yang models|||
5 | Keep track of PCI updates being successfully implemented in the RAN and update DB accordingly for future optimizations. | NOT YET TESTED | 8 | |||
6 | Trigger OOF for adaptive SON with PCIunchangeable cell list (by SON-Handler MS /OOF | NOT YET TESTED | 9 | Successful PCI control loop (regression but involving Runtime DB and AI/ML algorithm, RAN-Sim as part of ONAP repos) ) when previous PCI updates are not implemented in the RAN | NOT YET TESTED | 10 | Successful ANR control loop (regression but involving Runtime DB, RAN-Sim as part of ONAP repos
7 | Yang-model based schema and API generation for ConfigDB (PoC only) | NOT YET TESTED |
Detailed Impacts
Refer to the child wiki pages for the detailed impacts.
...