...

E2E Model structure optimization

1. New/Enhanced features
   ( Blue means new in Guilin. )
   
   
   • 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 separatelyseparatedly.
   • 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 Supporting 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.
   
   

...

Add RAN Model

Add TN model

Transport Network Slicing refers IETF TSCi model, in ONAP design time, there has TN NSST and TN Req T, in run time, reusing logicalLink netwokPolicy and etc. to express IETF nodes, details please see  

Supporting Files

Model Design Files

...