E2E 5G network slicing in ONAP
summary
ONAP proves an end-to-end slicing pipeline: the Frankfurt release implements a core NSMF that accepts slice requests and creates a Network Slice Instance (NSI) with a core NSSI via an external NSSMF, while the Guilin release extends NSMF functionality to Core, RAN and Transport NSSMFs aligned to 3GPP Rel‑16. The stack uses SDC/CDS, SO, A&AI, OOF, SDNC, DCAE and multi‑cloud/Helm plugins to orchestrate VNFs/PNFs/CNFs, keeps backward compatibility for brownfield deployments, and plans ML driven closed‑loop KPI analytics.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:275G Network Slicing Requirement
- 1:39ONAP-based Slice Management Overall Architecture Choices
- 5:48Impact overview: Guilin
- 8:39ONAP CNF Orchestration - Impacted Components - Guilin
- 9:29Guilin - K8s Adapter (Helm) Simplified Flow Day 0 + Day 1
- 10:59Core NSSMF - CNF orchestration scenario
- 11:58RAN and Transport Slicing Overview
- 14:35RAN Slicing Overview
- 17:09Support for integrated & distributed TN NSSMF
- 18:00Roadmap: Beyond Guilin release
related talks
17mApplication-Level Service Assurance with 5G RAN Slicing
34mE2E 5G Cloud Native Network
35mKeynote Panel: SDN/NFV Deployment Progress - Ecosystem Perspective
22mKeynote: Harmonizing of Open Source Networking
21mThe Service Enabling Wireless Network
19mKeynote: #Generation5G Powered by Automation
38mONAP (Open Network Automation Platform) Introduction and Use Case Deep Dive
32mKeynote: How Open Source and Open Standards are Collaboratively Accelerating Next-Gen Networks