| No. | Description | Involved components | Status | Remarks |
1 | Successful reception and handling of DMaaP message by SDN-R with CM notification. | DMaaP, SDN-R | IN PROGRESS | The trigger for the DMaaP message shall actually come from RAN as a CM-Notify, but now the DMaaP message shall be simulated for the testing, since the CM-Notify VES format wasn't defined in time for Frankfurt, and hence not implemented in RAN-Simulator. OOM-2400 - Getting issue details... STATUS |
2 | Successful update of ConfigDB with CM notification updates by SDN-R (upon reception of CM notification over DMaaP from RAN) | SDN-R, DMaaP | IN PROGRESS | OOM-2400 - Getting issue details... STATUS |
3 | Control Loop co-ordination – denial of 2nd control loop trigger (by Policy) received from SON-Handler MS when first control loop is active | SON-Handler MS, OOF, Policy, SDN-R, RAN-Sim | IN PROGRESS | DCAEGEN2-2216 - Getting issue details... STATUS POLICY-2573 - Getting issue details... STATUS |
4 | Control Loop co-ordination – re-submitting of 2nd control loop trigger (by SON-Handler MS) and initiating appropriate actions (stretch goal) | SON-Handler MS, Policy, SDN-R, RAN-Sim | DEFERRED | This needs further interaction with Policy and the evolution of CLC functionality, it will be taken up in Guilin release. |
5 | Keep track of PCI updates being successfully implemented in the RAN and update DB accordingly for future optimizations. | SON-Handler MS, Policy, SDN-R, RAN-Sim | IN PROGRESS | |
6 | Trigger OOF for adaptive SON with FixedPCI cell list (by SON-Handler MS) when previous PCI updates are not implemented in the RAN | OOF, SON-Handler MS | COMPLETED | DCAEGEN2-2249 - Getting issue details... STATUS |
7 | Yang-model based schema and API generation for ConfigDB (PoC only) | ConfigDB | NOT APPLICABLE | It will be shown as a PoC demo as originally proposed. The actual work will be done only when O-RAN yang models are available |
General
Content
Integrations