Open Source Access Manager ONAP Use Case Sumithra

Open Source Access Manager™ ONAP Use Case Sumithra Bhojan (AT&T) Bora Eliacik (Netsia)

VOLTHA Project Agenda • Unified Management and Control of the Access Devices (E. g. OLTs, Gfast, ONTs…) • Provides Hardware abstraction for the Access Devices • Provides means for Zero Touch for the Access Devices • Favors and provides a white box solution • Significant support from the SP Community • Planned for production (preferably with ONAP)

Access Network Peripheral POD-Reference Design

Open Source Access Manager™ (OSAM) Agenda • OSAM brings VOLTHA to ONAP in a generic way: • Activation of Access Network Peripherals • Management of Access Network Peripherals • Wireline and Mobile Access • x. PON, G. Fast • As well as x. RAN, x. Haul….

Open Access Architecture Disaggregated Device SW Merchant Silicon w/Open SW Domain Ctrl & v. Access VNFs Central Compute OSAM Open Source Access Manager Generally Edge ONAP Foundation REST & NETCONF ONAP Tech Dev OSS/BSS (Reduced) Community Collaboration Vendor Agnostic APIs ONF Distributed Access Management & Dev. Ops Tooling OCP ONAP Integration v. Access Tenants v. Access Applications NETCONF Open. Flow OSAM Hardware Abstract. Hardware Adapters Adapter Driven White Box OCP Hardware x. PON, G. fast, NGFW, x. RAN, x. HAUL…

Integration of Access Network Peripheral POD to ONAP What is Access Network Peripheral POD? ● Self contained ‘Light & Right’ deployable unit for access network ● Edge Cloud (AKRAINO) use case ● Dynamic control and user plane for providing Broadband services ● Access network VNF’s and PNF’s ● Access network peripheral POD use case as a plug n play black box

Technical Integration to ONAP 1 Should have no impact on existing architecture of ONAP Consume, Monitor and Operate in ONAP terms 2 Should be simple and fast to implement Should require little or no development on the ONAP side (from the OSAM team) 3 Should be future safe Should be able to align with Akraino

Use of existing ONAP Architecture Phased Approach: Initial Support of OSAM : Target Casablanca Access Peripheral POD activation/placement similar to PNF Subscriber management/activation will be contained within the POD ONAP components used as is: SDC, APPC, SO, AAI, DCAE, SDNC Target Architecture: Post Casablanca External Controller support with ONAP

Open Source Access Manager™ for ONAP Metro Cloud ONAP Operations Manager (OOM) OSAM-UI Dashboard OA&M (VID) Portal Framework UI, CLAMP, ONAP CLI Orchestration (SO) Active & Available Inventory (AAI) VNF SDK PNFD Design Time Resource Onboarding Data Collection Analytics and Events (DCAE) Policy Framework AAF OOF DMaa. P Service & Product Design Policy Creation & Validation Common Services External API Framework Logging APP-C Multi-Cloud Adaptation Cloud/VIM Driver Catalog (L 4 -L 7) SDN-C VFC (L 0 -L 3) (ETSI-Aligned) Leaf/Spine Access Peripheral – Generally Edge Recipe/Eng Rules & Policy Distribution PNF Access Network Peripheral POD OSAM Control OSAM HA OSAM Collector Others

Demo of MWC 18 and ONS 18

Demo of MWC 18 and ONS 18 Istanbul Los Angeles

DEMO Video

The whole POD as a PNF Access Network Peripheral POD

PNFD Describes a whole Autonomous Access POD OSS BSS End User Portals OSAM PNFD ONAP IP CO 1 IP CO 2 OTHER CLOUDs

Each CO is a PNF instance PNF 1 CO 1 PNF 2 PNF 3 Household 1 Port 1 Household 2 Port 2 Household 3 Household 4 OLT 1 Port 3 OLT Port 4 OLT PNF 4 Tens of Thousands of COs

PNF registered data IP Household 1, GEM ID, port_ID, OLT_ID Household 2, GEM ID, port_ID, OLT_ID Household 3, GEM ID, port_ID, OLT_ID … Household 20000, GEM ID, port_ID, OLT_ID For Centralized Monitoring

PNF Onboarding and Service Design

Service Instantiation

Access Peripheral POD updates

Centralized Closed Loop Control

Modifications on ONAP Components • Northbound Rest services need to be added to communicate with the OSAM UI BPMN flows are going to be added. A&AI • OSAM specific definitions such as Households will be added APPC • To apply provision with Net. Conf, new direct graphes will be added. PRH • PNF Handler needs to be updated to handle OSAM specific data SO •

Modifications on ONAP Components VES Collector Holmes Policy Framework • To collect and divide into the channels, ves schema and configuration files are going to be changed. • To filter the events which trigger the action, drool rules are going to be added on runtime • To filter the action, drool rules are going to be added on runtime. In current policy actors, some actions are not provided by default. New actor classes are needed to be added due to supply required specific actions •