dynamic apis for the connected carrier catalyst co-leads dave duggal, enterpriseweb, cloudnfv greg...

Dynamic APIs for the Connected Carrier

Catalyst Co-LeadsDave Duggal, EnterpriseWeb, CloudNFV

Greg Tilton, DGIT, Agile Markets

Two Award Winning Catalysts

Dynamic APIs Catalyst

CloudNFV Most Innovative Catalyst

Award, TMF Live 2014

Agile Markets Most Significant Contribution to

Frameworx Award, TMF Live 2014

End-to-End Solution: Orders to Orchestration


CloudNFV Most Innovative Catalyst

Award, TMF Live 2014

Agile Markets Most Significant Contribution to

Frameworx Award, TMF Live 2014

OSS

Management& Orchestration

Use Cases: CPE and VoLTE over Cloud-RAN

Demonstrates TMForum Assets enabling ZOOM


Based on Standard TMF InterfacesEnables InteroperabilityAccelerates IntegrationProvides Transparency

Promotes Open Eco-Systems & Exchanges

Open Digital REST API

TR 211, SID, TMF 622

TR 244, TR 235, TR 238, TMF 622

Expanded Scope and Team for new Catalyst



Multi-vendor, Multi-technology, Multi-Domain



OSS BSS

Management and

Orchestration

DPI

Pulls Product SpecificationsPushes Orders Receives Billing EventsExposes Billing Policies

Exposes Product SpecificationsReceives Orders Pushes Billing EventsPulls Billing Policies

Reports EventsDeploys/Configures Monitoring


OSS BSS

Management and

Orchestration

DPI

Pulls Product SpecificationsPushes Orders Receives Billing EventsExposes Billing Policies

Exposes Product SpecificationsReceives Orders Pushes Billing EventsPulls Billing Policies

Reports EventsDeploys/Configures Monitoring

ZOOM!


Zero-Touch Operations,

Orchestration and Management

with an Open Eco-System


Step-by-Step (1 of 4)

BSS (Comverse) exposes product billing policies via Open Digital REST API*

MANO (CloudNFV) exposes catalog of product specifications via Open Digital REST API*

OSS (DGIT) fetches product specifications from MANO via Open Digital REST API*

OSS (DGIT) submits orders with customer/product details to MANO via Open Digital REST API*

MANO (CloudNFV) fulfills order, orchestrates Network Service, instantiate Virtual Network Functions

MANO (CloudNFV) manages lifecycle operations (scale-up, down)





CloudNFV flexibly represents industry standards interfaces as entities in a graph-connected info model

CloudNFV supports rapid on-boarding of VNFs & declarative composition of Network Services

CloudNFV enables products to be declaratively composed from Network Services mapped to TR 244 classes** / TR 238 interfaces*** / TR 235 models**** and linked to BSS (Comverse) billing policies











MANO (CloudNFV) fulfills order, orchestrates Network Service, instantiates Virtual Network Functions


CloudNFV associates product billing policy to customer with BSS through the TMF Open Digital REST API*

CloudNFV instantiates related VNFs through TMF TR 244 classes** / TMF TR 238 interfaces***

CloudNFV deploys DPI monitoring (Qosmos) to endpoints

CloudNFV reports service state to OSS through the TMF Open Digital REST API (TMF622)*









CloudNFV monitors Network State directly through TMF TR 244 classes** / TMF TR 238 interfaces***

CloudNFV balances Network Services as required through TMF TR 244 classes** / TMF TR 238 interfaces***

CloudNFV reports billing event to BSS as they occur through the TMF Open Digital REST API*


CloudNFV Frameworx AlignmentOpen Digital REST API* Leverages and extends with metadata (re: types, constraints, operations, etc.), which enable “Dynamic” APIs (as per Metamodel contributed by EnterpriseWeb)

TMF TR 244** - Frameworx Enhancements to Support ZOOMMaps existing classes and extends them to support CloudNFV’s dynamic, data-driven, policy-controlled orchestration (as per Metamodel contributed by EnterpriseWeb)

TMF TR 238*** - Fulfilling NFV MANO Interface Requirements Maps interfaces and extends them to support CloudNFV’s dynamic, data-driven, policy-controlled orchestration (as per Metamodel contributed by EnterpriseWeb)

TMF TR 235**** - Policy Model & ArchitectureMaps policy models to support CloudNFV’s application model (as per Metamodel contributed by EnterpriseWeb)


Why “Dynamic” APIs

Because your environment is dynamic!

Volatile Networks

Rapidly Evolving Protocols

Demand for New Products

Cheaper / Better VNFs

Intensifying Competitive Pressure

Rate of Technology Change


Dynamic APIs for Agility• Dynamic Configuration:

optimize service behavior based on real-time context

• Automate Interoperability: Late-binding of all connections and transformations

• Dynamic Adaptation: non-disruptive change for resilient services

• Automate Non-Functional Concerns:Real-time processing of security, compliance, governance


Situationally-Aware Services

One Unified Model

EventsMetadata-driven

Software Contracts (GB942)

Feedback Loop

Operations Processes& Lifecycle Entities

Resource Processes& Lifecycle Entities

Service Dataand Metadata

Active Contract(GB922)

Resource Dataand Metadata

Active Resource

EventsService and

Resource Events (State changes )

make requests / monitor state

provide service / report state


Thanks to all of our Championsfor Valued Input and Support


Sequence Diagram 1


Sequence Diagram 2

dynamic apis for the connected carrier catalyst co-leads dave duggal, enterpriseweb, cloudnfv greg...

Documents