Defining ONAP APIs With BSS/OSS 28 June 2017 Andy Mayer, Ph.D. © 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.

What Common APIs between ONAP and BSS/OSS allow Service Providers to utilize the capabilities of ONAP while using their existing BSS/OSS environment minimizing customization ONAP Architecture Storage Compute VNFs / Applications Networking ONAP Portal Design Functions Operational Functions E – Services BSS / OSS Big Data External Data Movement & APIs Data Collection & Analytics Common Services, Data Movement, Access Control & APIs Controllers Engineering Rules & Inventory Service Orchestrator Active & Available Inventory Dashboard OA&M Operation Administration & Maintenance ONAP Controller Recipe/Engineering Rules & Policy Distribution Service Design & Creation Analytic Application Design Policy Creation

Why Service Providers need a clear and unambiguous ONAP service abstraction so that the BSS/OSS can exchange service requirements and service capabilities in a common and consistent fashion. Service Providers want to rapidly integrate new Services and Service Components into ONAP so that they can quickly introduce capabilities for their customers and within their infrastructure. Service Providers want to manage the entire lifecycle of Services within ONAP in a common way so that they can ensure orchestration, manageability and control of each Service in an easily integrateable and low cost way. Model Driven approach: a cohesive way to have a shared view of information across ONAP external interfaces that can be used for or be input into a model driven process whereby the cost of delivering platform functionality is drastically reduced and the time to delivery is dramatically decreased.

BSS/OSS Interactions With ONAP E – Services BSS / OSS Big Data Service feasibility; Service provisioning configuration & activation; Request fallout; Usage events & metrics; License accounting; Service performance & quality (e.g., KPI); Service trouble management; Service policy; Capacity engineering; Address allocation management; Dashboard External Data Movement & APIs ONAP Portal OA&M Operation Administration & Maintenance Active & Available Inventory Service Orchestrator Recipe/Engineering Rules & Policy Distribution Common Services, Data Movement, Access Control & APIs Data Collection & Analytics Controllers Engineering Rules & Inventory Service Design & Creation Operational Functions Policy Creation ONAP Controller Storage Compute Analytic Application Design Networking Design Functions VNFs / Applications © 2017 AT&T Intellectual Property. All rights reserved. AT&T, Globe logo, Mobilizing Your World and DIRECTV are registered trademarks and service marks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks are the property of their respective owners.

BSS/OSS Interactions With ONAP E – Services BSS / OSS Big Data Initial Focus on BSS/OSS: Service provisioning configuration & activation; License management; Address allocation management; Dashboard External Data Movement & APIs ONAP Portal OA&M Operation Administration & Maintenance Active & Available Inventory Service Orchestrator Recipe/Engineering Rules & Policy Distribution Common Services, Data Movement, Access Control & APIs Data Collection & Analytics Controllers Engineering Rules & Inventory Service Design & Creation Operational Functions Policy Creation ONAP Controller Storage Compute Analytic Application Design Networking Design Functions VNFs / Applications © 2017 AT&T Intellectual Property. All rights reserved. AT&T, Globe logo, Mobilizing Your World and DIRECTV are registered trademarks and service marks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks are the property of their respective owners.

Related ONAP Projects Modeling Project Service Orchestrator Project Identify overall modeling guidelines and approaches, determine modeling tools and tool chaining, and identification of industry standard models (e.g., TMF SID, ONF TAPI, etc.) that may be applied to the APIs Service Orchestrator Project Gather information about the relevant Service Orchestrator APIs (particularly the Service Instantiation API). Will collaborate with Service Orchestrator team to ensure that APIs remain consistent for R1. Change Management project Define external API capabilities to support the Change Management DMaaP Data Filtering, data transport, and data processing Standards Coordinator  Related activities in the TM Forum, MEF, etc.

High Level Project Plan For Release 1 Focus: Service Instantiation; License Management; Network Address Space Management Common APIs between ONAP and BSS/OSS allow Service Providers to utilize the capabilities of ONAP using their existing BSS/OSS environment with minimal customization Analysis of current Service Orchestrator APIs and flows Functional description of target ONAP capabilities for interactions with BSS/OSS Functional reference architecture (MEF LSO mapping, Interface Reference Point definition, etc.) Note that the BSS/OSS to ONAP APIs are relevant to the MEF LSO Legato Interface Reference Point. Identify BSS/OSS – ONAP Use Cases and interactions Definition of information model for ONAP service abstraction (with Modeling Project) API definition (e.g., JSON) in cooperation with ONAP Projects (including Service Orchestrator)

Time Line M1 Project Scope 29 June M2 Functionality 3 August M3 API

Possible Approach Define BSS/OSS – ONAP Use Cases, Interactions, Information Model, and API description Apply MEF’s LSO Reference Architecture; Interface Reference Points, Operational Threads, etc. (MEF was working with OPEN-O on relating architecture and APIs) Work with Modeling Project to determine base service abstraction Information Model on best in breed standard models (e.g., ONF TAPI, TM Forum, etc.) API Development: Well defined specifications for the BSS/OSS APIs (e.g., JSON Swagger). These define what the BSS/OSSs would need to build to. An ONAP implementation of these APIs Engage MEF / ONF TAPI based APIs where applicable Explore use of Tool Chain to automatically generate APIs based on models

Characterize Current ONAP Interactions with BSS/OSS Identify relevant ONAP Component APIs Characterize and describe interactions supported by each API This set of interactions becomes the current capabilities base that will be used for gap analysis and identification of API enhancements or the need for additional APIs ONAP Component BSS/OSS Type Interaction Description Service Orchestrator Ordering Service Instantiation . . .

Describe Target Use Cases & Interactions (Example) Serviceability and Ordering

Describe Shared ONAP Service Abstraction (Example)

Define APIs (Example) createServiceInstance replaceServiceInstance Client Service Instantiation replaceServiceInstance POST /serviceInstances/v3/ {serviceInstanceId}/replace POST /serviceInstances/v3 202 with serviceInstanceId and requestId 202 with new serviceInstanceId and requestId updateServiceInstance PUT /serviceInstances/v3/{serviceInstanceId} 4xx/5xx with requestError (0 … Many) asyncRequestStatus callbacks or sync response optional async responses deleteServiceInstance DELETE /serviceInstances/v3/{serviceInstanceId}

BACKUP MATERIAL © 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.