This page captures the details of the Modeling enhancements (IM, DM of NSST, NSSI, service and slice profiles, etc.) and the associated component impacts (e.g., SDC, AAI), as a part of E2E Network Slicing.

Details of SDC Template design for Option 1:  Template Design for Option 1

Details of SDC Template design for Option 2:  Template Design for Option2

Main Contact(s): Chuyi Guo, Borislav Glozman

Participants: LIN MENG, Swaminathan Seetharaman, Seshu Kumar Mudiganti, Chuanyu Chen, Shankaranarayanan Puzhavakath Narayanan,Fei Zhang Alessandro Gerardo D'Alessandro

Enhancement Aspects

E2E Model structure optimization

1. New/Enhanced features
   
   
   • Introduce Slice Profile Templates to carry user slicing subnet requirements, in ONAP we have 3 kinds of Slice Profile Templates, for RAN, Core and CN separately.
   • Add RAN NSST and TN NSST to support RAN and TN NSSI deployment, in TN side, also add TN Network Requirement Template to support TN connection links creation.
   • Has allotted resource relationship between slice subnet requirements and subnet slice resource, see 1, 2, 3. Allotted resource 4 is inner TN, between subnet resource and logical network resource.
   • Update relationship between NST and NSST using allotted resource, instead of nested, see 5. 
2. Supprting for both option 1 and option 2
   ONAP option 1 and 2 differs on the RAN and FH/BH relationship, in option 1, RAN NSSMF will decide FH/MH requirements and send to TN side, so RAN NSST will nest FH/MH NSST, and slice profile requirements will contain not only RAN side requirements but also FH/MH. In option 2, FH and MH are independent requirments when doing E2E requirements decomposition. Detailed background of option 1 and 2, please see  E2E Network Slicing Use Case in R7 Guilin.
   
   

3 domain combination solution -Endpoint 

  In order to enable 3 subnet connectivity, making end-to-end forwarding and control plane interacting, in slicing services, we need slicing interworking identifier and information to tell how RAN and Core connect with TN. Slicing interworking identifier(in ONAP is vlan Id, allocated by NSMF) is used to isolate differerent service datas, and identify the unique slicing service across RAN, TN and Core, 1 S-NSSAI will need to be assigned with 1 slicing interworking identifier(vlan Id).  The slicing interworking  information is used as bridges to connect RAN/Core and TN, it should be RAN/Core side outgress and TN ingress, like port, ipAddress, next hops and etc.

  In ONAP, we refer 3GPP proposal 3GPP S5-203419 and S5-203420.rar in TS 28.541, and introduce Endpoint(EP) to ONAP Network Slicing model.

3GPP reference:

ONAP Model:

Design Time: In R7, EP allocation starts from UUI, when doing service profile decomposition to slice profiles, NSMF will give EP information along with slice subnet requirements delivery to RAN and Core, TN will get the information and store EP Ids after RAN and Core instantiation.

Run Time: 

Run time model reuses node NetworkRoute to carry EP information, 1 NSSI can have multiple EPs, 1 EP will have a Slicing interworking identifier(vlan Id).

(Note: 1 EP can support multiple S-NSSAIs, but in R7, we only support EP and S-NSSAI 1 : 1.)

EP attributes and AAI NetworkRoute schema mapping:

Add RAN Model

Add TN model

Supporting Files

Model Design Files

Design Time Template

Note: in Guilin release, option 2 only supports BH TN.

AAI Instance Model

Service Profile and Slice Profile Attributes Mapping in R7

Note: Support "M" means this attribute must have a value in the slice profile when doing decomposition, "O" means may have a value or not depending on customer requirements.