OSAM Architecture Proposal June 2018 1 OSAM Architecture

OSAM Architecture Proposal June 2018 1 OSAM Architecture

5 G Use Case 2 6/12/2018

2 - PNFD Onboarded & Resource Created SDC 4 - Service Created by using CU and DU 6 - PNF Service Instantiation is requested with correlation id 5 - PNF Service Requested SDNC OOF 7 - Selects the optimal CU for PNF SO VID SDNR A&AI DCAE Initial EM 11 - Initial EM, tells Cor_id_1, onap_ip_add and also some certifications Cor_id_1 8 - PNF entry is created 9 - Creates VES topic by using Cor_id_1 12 - Receives onap ip address and cor_id_1 with it’s own ip DU OSAM Architecture ONAP 10 - Waiting for PNF to register 1 -Onboarded and instantiated v. DHCP as a VNF IPdu_1 A&AI CU 3 - Defined As an Allotted Resource

16 - Assigns network relations SDNC OOF A&AI SO SDC DCAE VID ONAP Cor_id_1 IPdu_1 14 - Update cor_id_1 with IPdu_1 SDNR 13 - Registers the ONAP with cor_id_1, IPdu_1 15 - Send CU IPcu and some configurations CU 17 - Sends configurations IPdu_1 DU OSAM Architecture A&AI 16 - Open connection to CU

OSAM Use Case 5 6/12/2018

OSAM Architecture OSAM CORE OSAM OOF UI Portal Service VID Layer OSS/BSS ONAP A&AI OSAM DB SO Service Flow OSAM GW Adaptor DCAE Layer APPC PNF Locator Manager OSAM Gateway OSAM Core Adaptor Layer NEM Adaptor Layer GRPC SEBA Pod 1 OSAM Architecture GRPC NEM Volt. HA SEBA Pod 2 Ves Agent OSAM Gateway Distributed Cache

2 - OSAM CORE Onboarded as a VNF Application 3 - PNFD Onboarded & Resource Created OSAM CORE SO SDC VID APPC DCAE 4 - Defined As an Allotted Resource 5 - Service Created by using CU and DU OSAM Gateway 2 OSAM Gateway 1 GRPC Northbound APIs IPpod_1 SEBA Pod_1 OSAM Architecture ONAP A&AI OOF A&AI 0 -Manually installed and obtained IPpod , IPosam and correlation id from Local DHCP 1 - Onboarded and instantiated as a VNF Application

9 - Selects the optimal OSAM CU for PNF CORE VID 7 - PNF Service Instantiation is requested with correlation id SDNR 8 - Request to instantiate service OSAM Gateway 2 IPpod_1 SEBA Pod_1 OSAM Architecture DCAE 12 - Waiting for PNF to register OSAM Gateway 1 6 -SEBA Service Requested Corr_1 10 - PNF entry is created with cor_id_1 SO SDC ONAP A&AI OOF A&AI 11 - Creates VES topic by using Cor_id_1

OSAM CORE SDC 16 - Assigns network relations 14 - Update cor_id_1 with IPpod_1 SO SDNC VID SDNR DCAE 13 - Registers the ONAP with cor_id_1, IPpod_1 18 - Associate Osam_gw 1 and seba_pod_1 OSAM Gateway 2 OSAM Gateway 1 17 - Set GW Corr_1 IPpod_1 SEBA Pod_1 OSAM Architecture ONAP A&AI OOF 15 - Send OSAM Gateway IPogw and some configurations A&AI Corr_1 IPpod_1

• Open Issues • • Can we store SEBA topology information in AAI? Action: talk with the AAI team and PTL Can we add BPMN(Business Process Model and Notation) to SO at design time from SDC? Action: investigate SDC code base delivered on Beijing release. SEBA NB module (NEM) will provide an interface on GRPC. Which ONAP module can replace the OSAM NEM adaptor layer? Action: In ONAP casablanca meeting, suggested that DCAE will probably have protobuf support over TCP/TLS. Can service and service profile provisioning be done using EXT_API module? Action: EXT_API service flows will be investigated. For now it seems that EXT_API directly interacts with AAI, if it is not allowed to store subscriber information store in AAI, we have to manipulate the service flows of EXT_API. We have to discuss it with ONAP community. Can we receive CU ip address of PNF from AAI? Action: will be investigated. Technology profile is SEBA specific. We have to provide an abstract data model for it. Action: Take in to consider during data model design. What type of data properties will be stored for OLT/ONT? Action: will be investigated. Related to service provider requirements. OSAM Architecture

THANK YOU 11 OSAM Architecture