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

Need to check whether this is needed.

Intention 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 sharing
• Config policy for optimization constraints

SDNC-915 - Getting issue details... STATUS

Not 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 activation
• 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)

Successful design of CST ,Service Profile Template

Service instantiation via CSMF portal resulting in NSI selection without any override by operator via NSMF portal - new NSI to be instantiated

Service instantiation via CSMF portal resulting in NSI selection without any override by operator via NSMF portal - existing NSI to be selected

Service instantiation via CSMF portal resulting in NSI selection with operator overriding automatically selected option from NSMF portal - new NSI to be instantiated

Service instantiation via CSMF portal resulting in NSI selection with operator overriding automatically selected option - existing NSI to be selected

Service activation from CSMF portal – resulting in slice service activation

Service de-activation from CSMF portal – resulting in slice service deactivation

Service termination (remove service profile/slice profile from NSI/NSSI)