ONAP Orchestration for Multi-Access Edge Cloud
Mesut Soyturk, Madhu KashyapNETSIA
Agenda
• Why Multi-Access Edge Cloud?• Orchestration as a key control point• ONAP orchestration for Multi-Access Edge Cloud• Future Direction …
Broadband - the infrastructure for the digital society
3
Sample countries with National Broadband
initiatives
1 Billion users on 5G by 2023
~ 1Billion FTTH users by 2022
Globally, IP traffic (consumer & business, mobile & fixed) will reach 278.1 Exabytes per month in 2021, up from 96.1 Exabytes per month in 2016.- Cisco VNI, Sep. 2018
Operator Access Network challenges
Complex Protocols
Device Proliferation
High OPEX/CAPEX
Service Monetization
Vendor lock-in
Operational Issues
4
Service Support
Operator – Next Gen Technology Adoption
SDN NFV Cloudification White Box & Disaggregation Open Source
5
Edge Cloud Evolution
6
Core Cloud
OLT
EPCCPE
ANY VNF
Edge Cloud
Router, FW, VOIP, IPS …
DHCP, NAT, VOIP …
BBU
VNFs
DistributedCloud
VirtualizationCentralization
vEPC SEBA
DPI vCU
MEC APPS
IoT IPS
vCPE vFW
CPE
Splitter
RG
ResidentialServices
ONT
ONT
DUIoTGW
Mobile Wireless Services
ONT
Device Edge Infrastructure Edge Edge Cloud
7
OLT
SPBackbone
PON Network
Business Connectivity
Services
NFVI
ROUTER
Access IP / MPLS
IPTVVO
IPHSI
EPC / IoT
Business Services
Residential Services
Mobile
Services
VNFs VNFs
Global Orchestrator
Multi-Access Cloud for the Edge
• Cost savings by creating a single MANO domain for wired and wireless in the access network
• Increased velocity of new service roll-outs• Example: ONF COMAC
• Disaggregate all mobile and broadband components• Common data plane and control plane
• UPF & BNG
8
Value of Multi-access convergence
There will be thousands of Edges
9
CORECORE
AGG
ACCESS
Thousands of Edge Clouds
Need for a Global Orchestrator
10
CORE
AGG
ACCESSThousands of Edge Clouds
Need for a Global Orchestrator
COREOrchestrator
ONAP for Multi-Access Edge Orchestration
11
ONAP strategy for Core and Edge
12
Use ONAP as End2End Orchestrator
Centralized Monitoring of Access-Edge
Configure, Manage, Monitor and Closed Loop Automation
Integration with the OSS/BSS Systems
Multi-Access Telco Cloud for the Edge
13
Multi Access Edge Cloud Orchestration - RAN
14Access
Netsia MAC
vCU vCU
vCU vCUOLT
Switching FabricNFVI Platform
Intelligent RAN Controller
vHAG
Infrastructure Edge
Splitter
ONT
ONT
DU
ONT
RG
IoTGW
Mobile Service
s
Residential
Services
Business Connectivity Services
Fixed Mobile Coordination
AggregationCoordination
Core
vEPC
vEPC
(ONAP , OSS/BSS Systems, etc)
ONAP with E2E slicing
15
ONAP
OLT
ONT
5G vCore 5G vCore
RAN Intelligent Controller
End-to-end Network Slice Manager (NSMF)
OLT Slice Manager (TN Manager)
Core Slice Manager (Core NSSMF)
RAN Slice Manager (RAN NSSMF)
vCU vCU
vCU vCU
DU
DU
DU
ONT
ONT
POC : Multi-Access Cloud for Next Gen CO
16
Initial PoC with OSAM
17
• Seba is fully container based – ONAP cannot onboard• The decision is made to have SEBA represented as a simple PNF to ONAP• 5G was the only use case that was using PNF approach• We based OSAM architecture on 5G
OSAM Architecture
18
OSS/BSS
VoltHA
SEBA Pod 1
NEM
GRPC
ONAPA&AI
APPC DCAEVID
SO
OOFOSAM CORE
OSAM Gateway
OSAM Gateway
OSAM Gateway
VoltHA
NEM
GRPC
SEBA Pod 2
Future Direction
19
SEBA Central
20
SEBA CENTRALMIDDLEWARE
OSS/BSS Systems
SEBA
GPON NWWB OLT
CRMPROVISIONINGINVENTORYFCAPS
North Bound Integration
ALARM UI
STATS LOG
OSS/BSS API Gateway
SEBA Central
21
ONAP Integration
PointSEBA CENTRALMIDDLEWARE
OSS/BSS Systems
SEBA
GPON NWWB OLT
CRMPROVISIONINGINVENTORYFCAPS
North Bound Integration
ALARM UI
STATS LOG
OSS/BSS API Gateway
• SDN-R is an approved ONAP project as subproject to ONAP SDNC. The SDN-R project enhances SDNC by adding functions for wireless technologies.
• Exploring SDN-F (Fixed Broadband) for PON (Passive Optical Network)
22
Similar approach to SDN-R
ONAP Integration with SEBA Central
23
ONAP
OSS/BSS Systems
SEBA
GPON NWWB OLT
CRMPROVISIONINGINVENTORYFCAPS
North Bound Integration
HOLMES POLICY
SDN-F DCAE
OSS/BSS API Gateway
SO
Thank You