OOF-PCI use case is ready for M2 - based on feedback from 5G Use Case Committee
Rutgers ONAP Lab: Meeting of stakeholders. Committment and support from Rutgers Winlab has been re-validated. Plan to present to ONAP in coming weeks.
Decision: Modified figure to reflect discussions. Removed step 12 (query for new cell) and also mark CL Setup as manual.
Yang model, API, all have by March 8 (M3)
Discussion of PCI/ANR functionality: see slide 6. Introduction of joint PCI/ANR optimizer in OOF. Inclusion of list of poor HO KPI neighbors in OOF API in step 5.
Two Control Loops (control loop names): PCI: change pci value, triggered by pci confusion alarm and/or nbr addition ANR: modify Neighbor Relations Table, and NbrRelations. triggered by poor/bad HO KPI and/or PCI confusion state
When SON MS sends request to change pci for some cell X, it may also send modify message for NRT table of the neighbors of X.
