...
E2E Model structure optimization
- 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.
- 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, and introduce Endpoint(EP) to ONAP Network Slicing model
Supporting Files
Model Design Files
...