E1a: Models & relationship between Config, Operational DB & AAI

Epic#1 - OOF/SON Enhancements

Enhance Yang model to align with 3GPP and O-RAN

Configuration/Operational Database, Config History (e.g. to revert changes)

RAN Simulator – enhance and include in ONAP codebase*

Related O-RAN Jira: https://jira.o-ran-sc.org/secure/RapidBoard.jspa?rapidView=7&projectKey=OAM&view=detail&selectedIssue=OAM-9 

1

Successful reception and handling of DMaaP message by SDN-R with CM notification (simulated from RAN).

2

Successful update of ConfigDB with CM notification updates by SDN-R (upon reception of CM notification over DMaaP from RAN)

3

Control Loop co-ordination – denial of 2^nd control loop trigger (by Policy) received from SON-Handler MS when first control loop is active

4

Control Loop co-ordination – re-submitting of 2^nd control loop trigger (by SON-Handler MS) and initiating appropriate actions

5

Keep track of PCI updates being successfully implemented in the RAN and update DB accordingly for future optimizations.

6

Trigger OOF for adaptive SON with FixedPCI cell list (by SON-Handler MS) when previous PCI updates are not implemented in the RAN

7

Yang-model based schema and API generation for ConfigDB (PoC only)