A&AI Instance Model Structure for E2E Network Slicing Case
Overview
E2E Network Slicing implements CSMF, NSMF and NSSMF in ONAP, in A&AI there has entities respectively corresponding to different instance management function.
For the whole network slicing management lifecycle. there has 2 parallel lines, one is for single s-NSSAI requirements which is dynamic and comes from slicing user requests, there are CSIs, sevice profile instances and slice profile instances for different user requirements. In design time, you can find CST, Service profile T and Slice Profile T for them(Templates details can be found at Template Design for Option2).
Another line is for network slicing requirements which can carry multiple s-NSSAI(user) requirements, there are NSIs and NSSIs. In design time, you can find NST and NSST for them. User requirements will be translated and mapped to network slicing requirements.
The overall E2E Network Slicing A&AI instance model photo is:
Papyrus Diagram and AAI object mapping is:
Note: only when option 1, there will have self-nested cycles for RAN slice profile instance and RAN NSSI.
The whole design time Modeling framework can be found at Modeling enhancements.
New feature in R8
In Guilin release, there has 3 new features:
- Transport Slicing models, details please refer
- Add completed Slice profile service instance(changing node SliceProfile relationship from NSSI to sevice instance object)
- Have resource level associations with NSSI
Transport Network Slicing Model
Overview
Transport Slicing model is part of the E2E Nerwork Slicing Modeling Structure, which will be used and maintained by TN NSSMF at Management and Control Plane level. Transport Slicing model will be mapped to TN Network reosurce model- CCVPN Model. Transport Slicing model refers IETF specification draft-rokui-5g-transport-slice-00.pdf.
Details of how to map to CCVPN Network model can be found at:
IETF Model Reference
IETF original model expression:
Transport model mapping:
