No code impact foreseen for Frankfurt release. Update A&AI schema with Network Slicing model (stretch goal for Frankfurt)

Need to check whether this is needed.

Enhance ONAP model with Network Slicing related constructs, including time based activation and KPI monitoring

Provide a demo Network Slicing SDC model

Provide a demo Network Slicing A&AI modelIntention is to re-use existing constructs for Frankfurt release.

No code impact foreseen for Frankfurt release

• Config policy for slice allocation, slice sharing, slice sub-net allocation and slice sub-net sharingConfig policy for resource allocation for a slice sub-net
• Config policy for optimization constraints – e.g., network resource optimization, resiliency, etc.

• DGs for receiving DMaaP message from SO with RAN NSSI details, map them to netconf messages and send to RAN.
• Interaction with PNF PnP to be discussed
• Runtime DB interaction

(Stretch goal for FrankfurtNot in scope for Frankfurt release, may be realized as a PoC for impacts associated with RAN slice sub-net (still under discussion)

• CSMF impacts, workflows for service instantiation, involving service decomposition, NST selection, NSI allocation trigger, service instantiation
• NSMF impacts, workflows for NSI selection, NSI instantiation, NSSI selection, trigger for NSSI instantiation, NSI activationNSSMF impacts under discussion with ArchCom
• Interface to external NSSMF
• Store slice catalog items, update active slice inventory

(NSSMF impacts still under discussion with ArchCom, not in scope for Frankfurt release)