Description of Use Case / Requirement:

 This Epic captures the requirements for 5G OOF SON use case for Guilin release. It shall cover:

 1. O-RAN alignment (VES, O1 interface) (subject to availability of relevant specs from O-RAN, and VES-specification)

(M2/M3 update: This has been deferred to the next release, as the VES spec updates in VES collector is being done now, and it may have further impacts in SON-Handler MS also).

2. SON function to demonstrate SON functionality applying AI/ML

(M2/M3 update: This will be realized in Guilin by using an offline-trained ML model to provide additional inputs to the PCI optimizer (in OOF), based on PM/KPI data).

3. Stretch Goal - Control Loop Coordination (CLC) extensions and CL mechanism enhancements. Apart from Policy component impacts, this shall have impacts in DCAE and SDN-C(R) also. This is at present a stretch goal as we are still checking regarding resource commitments for Policy.

(M2/M3 update: There is no change in status except that even if this functionality is implemented, it will be demonstrated only as a PoC, and official integration will happen beyond Guilin release).

Note: While it is agreed to use updated yang models (if available) (see 1 above), C&PS updates relevant to this use case - including possible auto-generation of data models/DB-schema and APIs from yang models shall be deferred to H-release.

Owners (one of these should be the Assignee - use @ notation):

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

None

Project Impact (Test Only (TO), Code (C)):

DCAE (C)

SDN-C (R)/CCSDK (C)

OOF (C)

Policy (C) (Stretch goal)

Configuration & Persistency Service (now documented as SDNC) -  we have decided to continue to use the same approach as in Release 6, which avoids impact in CPS. Any enhancements may be considered as a PoC/demo only, and taken up in Release 8.

Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):

Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

DCAE (S)

SDN-C (R)/CCSDK (S)

OOF (S)

Policy (S - subject to resource availability) (Stretch goal)

Integration Leads (use @ notation): 

Company Engagement: 

DCAE - Wipro

SDN-C (R)/CCSDK - IBM

OOF - Wipro

Policy - AT&T and Wipro have intention to commit, but since it is not confirmed yet, the corresponding parts of the use case (item (3)) is indicated currently as a stretch goal - we will revisit this by 3rd week of July. The remaining parts of the use case can proceed even if the stretch goal is not realized.