...

• Implement O-RAN defined A1 interface specifications in ONAP controller (e.g. SDN-R).
• Enhance CDS to capture A1 configuration details.
• Enhance VID GUI to invoke intent based policy configuration using A1 interface
• Enhancements to VES events
• Software Upgrade flow enhancement to fully meet O-RAN specifications (beyond R6)

Business Impact - Most ONAP service providers are O-RAN members.  These service providers are expected to support O-RAN specifications with the products they include in their networks.  Modifying ONAP to be O-RAN compliant for FCAP implementation (configuration management, including intent based policy configuration, fault and performance data collection) will be usable by all the service providers, avoid duplicate development effort.

...

Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)

DEVELOPMENT IMPACTS

List of PTLs:Approved Projects

...

This section documents the impacted Management Services

Provisioning Management:--R6

1. Define new VES domain to support CM Notifications:

   -notifyMOICreation, notifyMOIDeletion, notifyMOIAttributeValueChange. TS 28.532 Rel 16

These notifications are introduced with the following E2E EPIC (stored in DCAE project, which will benefit the most form this new functionality):

Fault Supervision:--R6

1. Modify existing fault event or create new fault3gpp event to support Harmonization work in TS 28.532
2. Determine which of the 3GPP supported IS notifications will be supported in ONAP—refine how fault3gpp is filled in for the different notification types

...

   4.  Drive the use of IOC objects to configure subscribe/unSubscribe control on a NF via NetConf commands e.g. Provisioning what notifications a manager wants to receive from a NF. ONAP may not necessarily want to receive everything a NF is capable of sending

Performance Assurance (G Release)

1. Modify the File Ready Notification to support additional Use Cases. It should be used for Performance Assurance but also for a number of other kinds of files—log files that are requested etc.  Propose that ONAP should work with 3GPP reps to change the notification perhaps renaming the changeIdentifier field in the Notification event to a name like fileType so it is more generic.  This will be included in Frankfurt pending 3GPP stabilization in October.
2. ONAP needs to incorporate the job control IOC defined in 3GPP for creating, starting and stopping PM jobs. This should be done via NetConf.

...