Topic Leader(s)
- LIN MENG
- Swaminathan Seetharaman
- @Saravanan Ayyadurai
- Ahila P
Topic Overview
60m, Ahila P LIN MENG This session will provide a brief overview of E2E Network Slicing use case - what has been achieved so far and the road ahead. A Demo of a part of the functionality realized up to Honolulu will be given.
Slides & Recording
Demo
- E2E Network Slicing Presentation document - E2E_Network_Slicing_LFN_DTF_Demo_v2.0.pdf
- E2E Network Slicing Demo sequences - E2E Network Slicing-LFN_DTF_Demo_screenshots.pdf
- Supporting Logs - (a) E2E Slice - New & Reuse.zip (b) Closed Loop.zip
Recording
Note on UUI inputs:
Screen: Create Communication Service Service
1. New Slice & Shared Slice scenario - 'Mobility' in the 'Create Communication Service Service' screen should not be Stationary for eMBB Slices
2. Shared scenario - Data Rate Uplink and Data Rate Downlink values can be less than the existing slice and the latency can be greater than the existing slice for reusing the existing slice
Agenda
Awesome presentation
- Presentation on E2E Slicing use case overview and what has been achieved so far
- Demo on (a) Creating a new E2E slice (b) Sharing an existing E2ESlice (c) Closed Loop (partial)
- Istanbul Release roadmap
Minutes
Question: Does ONAP Slicing solution allow operator to enter S-NSSAI value as input during service ordering?
Response: This is not supported currently. ONAP acting as CSMF generates S-NSSAI value when the service is created. In a future ONAP release, we can definitely consider implementing a provision for the operator to provide S-NSSAI value as input (in UUI, and perhaps also ExtAPI for TMF 641 API) during service creation. Our view is this would be important only when the operator wants to control the S-NSSAI values that are to be used, e.g., when considering roaming agreements also.