© 2017 TM Forum | 1

Relationships of ONAP and OSS/BSS

Jenny S. HuangStandards and Industry Alliances, AT&T

Distinguished Fellow, ZOOM Project Co-chair, TM Forum

© 2017 TM Forum | 2

OSS/BSS – What for?

http://passionateaboutoss.com/oss-call-for-innovation/

schedule

scopebudget

risk resource

quality

Complexity

They are systems designed to manage and reduce the complexities of the

businesses.

schedule

scopebudget

risk resource

quality

Complexity

© 2017 TM Forum | 3

• Network and OSS/BSS transformation, happened independently!

• ONAP and OSS/BSS, rivals or match made in heaven?

• Way forward …

Topics

© 2017 TM Forum | 4

Quick Overview of OSS/BSS EvolutionOSS/BSS 1.0

•~ 1970’ – 1990’•Disruptor: computing technology•Automation of FCAPS•Purposely built, telecom specific technologies & Protocols

•Silo systems

OSS/BSS 2.0•~ 1990’ – 2010’•Disruptor: Internet, SoA•Leveraging IT technology, Model Driven

•System consolidation•Separations of concerns – via modeling/abstractions/APIs

OSS/BSS 3.0•2010’ – Now•Disruptor: Cloud, SDN, NFV•Become business enabler•Platform multi-side business models

•Embracing ecosystem•System simplification

OSS/BSS 4.0•2018 --•Disruptor: Industrial 4.0•High Cohesion Architecture•Big Data, AI/ML/DL•Containers & Microservices•Knowledge plane to support the businesses

Faul

t Man

agem

ent

Serv

ice

Prov

isio

ning

Capa

city

Pla

nnin

g

Perf

orm

ance

M

anag

emen

t

Inve

ntor

y M

anag

emen

t

Prem. Access Metro Core

EMSes

Prem. Access Metro Core

Common communication Vehicle/mediation layer

Platform Capabilities

PNFs PNFs VNFs VNFs

© 2017 TM Forum | 5

Many companies have adopted TM Forum design

principles, models and APIs for their OSS/BSS

They also use TM Forum abstracted APIs for Hybrid

infrastructure Mgmt. (Legacy, NFV, 5G …)

Realization by TM Forum Member Companies

To promote ONAP adoption, ease of integration

with exiting & future operations systems is important.

ONAP aims to support hybrid infrastructure, multi-cloud & multiple deployment flavors.

Resource & Infrastructure

OSS/BSS

Customer Facing

TM Forum Scope

ONAPRefactors some traditional OSS &

EMS functions to support virtualization and multi-vendor

solutions.

ONAP Scope

Scope of ONAP and TM Forum work

ONAP R1 Architecture(overlapping features with traditional OSS/BSS)

Storage Compute

VNFs / ApplicationsNetworking

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 & APIsControllers

Service OrchestratorActive & Available

Inventory

DashboardOA&MOperation

Administration& Maintenance

ONAP Controller

Recipe/Engineering Rules & Policy Distribution

Service Design & Creation

Analytic Application Design

Policy Creation

Infra.Cont

networkCont

App.Cont

3rd Party Controller

VNFM / EMS

VFCont

SDNAgent

VNF SD

K

© 2017 TM Forum | 7

A Closer Look at Some Commentary Work

• APIs• Onboarding

7

Platform Capabilities

PNFs PNFs VNFs VNFs

© 2017 TM Forum | 8

Business Objects & Organization Capabilities eTOM & TAM

Information ModelsSID

Metrics Metamodel & metrics APIs

Data Models

Functions

Model Driven ApproachModels

Code

TM Forum Frameworx provides a comprehensive and cohesive view of

all essential business & operation support concepts (Business Objects)

within the Enterprise

Business Objects, APIs skeletons are extended with domain specific data models for technology

specific implementation and deployment.

8

TM Forum Model Driven Approach

TM Forum Standards,

Models, Swagger APIs

Other SDO extension(e.g. MEF)

Open source, product specific

implementation etc.

Focusing on modeling the business problems

Artifacts

© 2017 TM Forum | 99

Apply TM Forum Technology Neutral APIs

sd Simple

BSS/OSS ONAPCustomer Network Cloud

NF & Connect Activation()

Service Fulfi l lment()

Response()

Customer Order()

Response()

Response()

Feasibility & Quote Inq()

Component Serviceability()

Response()Response()

Response()

Test Rqst()

ONAP External API Project - Serviceability and Ordering Use Case

© 2017 TM Forum | 10

OSS Support Hybrid Deployment Scenarios

Customer & Product Management

End-to-End ServiceManagement

ResourceManagement

Application & Transmission

TechnologyManagement

Customer Management: Managing Commercial relationship with Customers Masters Products, CRM, Billing, Commercial Orders

Service Management: Manages end-to-end Customer-Facing Services built by service-chaining multiple Technical Components (Resource-Facing Services) together.

Resource Management: Management and Orchestration of component services (Resource-Facing Services) from each technology domain.

Application & Transmission: physical and virtual application and Infrastructure technologies

EMS

SDN control

VNFm

VIM

WAN/LAN

VNFi

CPE/vCPE

VNFs/Apps

Resource and Technology

Management

Technology Management: Management of the physical and virtual application and Infrastructure technologies

Technology specific ,Vendor Specific

Technology specific,Vendor independent

Technology independentVendor independent

Hybrid Infrastructure

Capability(TM Forum HIP

program)

Deployment Scenario X Deployment Scenario Y

ONAP

Deployment Scenario Z

© 2017 TM Forum | 11

ONAP External and OSS Service Mgmt API Candidates

E2E Service Management

SchemaRepository

Service Catalog

API

ServiceInventory

API

Service Qualification API

Service Activation &

ConfigurationAPI

ServiceOrdering

API

Service Quality Mgmt API

Service Problem Management API

Usage Mgmt API

Service Test Mgmt API

SLA Mgmt API

AddressQualification

API

PM Threshold API

Alarm API

PM Monitoring API

Metric API

HIP

Native Capabilities

Resource Catalog

Resource Inventory

Resource Inventory

RF Activation and Configuration

Capability Delivery

Assurance

Capability Delivery Assurance

RF Activation and Configuration

Capacity Management

Security Management

Actor Management

TM Forum APIs

Source : Pierre Gauthier, TM Forum Chief API Architect

© 2017 TM Forum | 12

• Official liaison in place between TM Forum and the Linux Foundation

• Convert TM Forum APIs to Apache 2 License (in progress)

• Joint planning with ONAP TSC to introduce TM Forum APIs in Beijing release

Current Status

© 2017 TM Forum | 13

Package ID VF Package Type

SLA License Metadata

Functional Descriptors

Testing Descriptors

OperationalMetrics

[body of package]

Vendor Onboarding

•Market place•B2B Partnership

Procurement

•Market Intelligence•Procurement Strategy•Product Maturity

Capability Onboarding

•Validation•Acceptance•Cataloging (product, service,

resource)

Offer Creation

•Composition•Blueprinting•Cataloguing (offering)

Use

•Service design•Configure (service)•Instantiate•Inventory

Manage

•Monitor•Update•Upgrade•Billing•Usage/metrics

Retire

Migrate User

pack

age

lifec

ycle

Service designerService component builder

Service implementer

Implementation project managerProduct manager

Service delivery managerPartner manager

Subscriber/EnterpriseProduct end user

Policy engineerCustomer care

Market Analyst/ ProcurementProduct solution designer

Process engineer

stak

ehol

ders

13

VF Package Onboarding Automation

Metadata driven

Focus on non-functional and stakeholder needs to manage the expectations.

ONAP VNF Package Model

14

Vendor ID

Prod. Name

Version

Change LogLicense – terms and

conditions

VNF Package Model

Business

Description, type, category from VNF-D

LCM scripts

Mgmt. API – SOL005

Fault/PM scripts

Usage scripts

Scale Scripts

Policy Scripts

Operational Lifecycle

Storage Req.

Compute Req.

Networking Req.Resource Metadata

VNF flavors

SW Image

Technical - VNF Descriptor

Connection Graph

Testing Scripts

Security Features

ScaleMonitoring FM,

PM, Usage

SOL001

Policy

TestingOpt. Functional

Ca[abilitiesPackage Integrity & Authenticity

Artifacts Integrity & Authenticity

Sensitive Artifacts Encryption

SOL004

Package ID VF Package Type

SLA License Metadata

Functional Descriptors

Testing Descriptors

OperationalMetrics

[body of package]

pack

age

ONAP can be enriched with additional Operational standards

© 2017 TM Forum | 15

15

VF Package ID

ETSI, ONAP • Based on ETSI ISG NFV SOL004

• Specific VNF Vendor Requirements

TM Forum Focus (OSS/BSS Requirements):• Follow industry software asset management practices

• Supporting SP business & operational semantics

• Package ID: SKU = SWID + Product Usage Right (PUR)

• SWID: ISO 19770-2

• PUR: ISO 19770-3

• License/Asset Management:

• SKU Instance & inventory

• License metrics (for metering based licensing model)

• VF categorization

• Based on multi-year independent SP market surveys

• Support different back-office activities based on VF categories e.g. firewall, CPE etc.

Package ID(SKU)

Maturity (VF Typing)

SLA License Metadata

Functional Descriptors

Testing Descriptors

OperationalMetrics

[body of package]

pack

age

© 2017 TM Forum | 16

ONAP and Future OSS/BSS Impact

16

© 2017 TM Forum | 17

Open Source - Transformative Business Impact

Agile InnovationCollective Intelligence,

leadership & Inspiration

Reduced TCOShared resources,

eliminating redundant projects internally &

externally

Market AdoptionDisruptive innovation, new business models,

new players

Speed of DevelopmentProven processes, scale-up

projects, thousands of developers

Stakeholder Transparency

Level playing field for the entire ecosystem

Transformative business impact delivered via culture & mindset changes

Open Source and Open Standards – Network Transformation

18Harmonizing Open Source and Standards in the Telecom World – Linux Foundation White Paper

© 2017 TM Forum | 1919

Virtualization Transformation is a Journey

The boundaries between Net-OS and OSS/BSS will continue to change.

Source: Serverless architecture

Datacenter

You Manage Delivered as Service

© 2017 TM Forum | 2020

Open Digital Architecture (ODA)

ONAP, OSM …

TM Forum Future OSS/BSS Architecture (separations of concerns)

© 2017 TM Forum | 2121

Considerations for ODA Future Work

Understand OSS/BSS relationships with emerging SDN/NFV management platform like ONAP, OSM among others (e.g. catalogue, inventory, data analytics etc.)

The boundaries will be blurred, it is important that we work together to address common business goals.

OSS/BSS future-proof focuses:– Cognitive Business

– Natural Language UI

– Loose Coupling, High Cohesion Architecture

– Data Drive, Machine Learning, Predictive Analytics

– Exposed OSS/BSS functional ‘capabilities’

– “Open source” culture

– …

© 2017 TM Forum | 22

Thank You