TMF Service Model Catalyst

Copyright © 2009 TeleManagement Forum, All Rights Reserved.

Service Model

Catalyst

Getting the Provider to Cloud 9

Copyright © 2009 TeleManagement Forum, All Rights Reserved.2

Executive Summary

Achieve consistent Service Model definition for services from the provider or the Cloud

Holistic Service Catalog that facilitates Service Lifecycle Management functional definitions for all Services

• Create/Define, Fulfill, Assure

• Cross-domain interaction with a Service Broker (Service Delivery Framework)


Business Challenges

Increasing Demands for Product Convergence

Need to reduce time and cost to introduce and manage

Higher Customer Expectations

Drives the need to operate more rapidly and effectively in an increasingly complex telecom environment.

Current Solutions Lacking

• Can’t afford long product development cycles

• Need for open standards and technologies to facilitate interaction

We Need a Holistic Model-Driven Approach to Product Development

• Align business, operations, and network

• Manage our processes, rules and data supporting our products

• Standards-based to facilitate rapid partnering

CSP

NetworkCloud

CloudCloud

Customer ExpectationsProduct Convergence

Performance

Lower Cost

Product Providers

Delivery time


Cloud Marketplace Conceptual Solution

Hosted Exchange Email

Customer Web

Portal

Software and Platform

as a Service (SaaS/PaaS)

Active

Catalog

Cloud CSP2

CSP1

Product

Offerings

Create Fulfill Assure ChargeService

ExecutionAnalytics

Service Fabric Broker

4


Mo

del

Co

mp

on

ents

Ser

vice

Cat

alo

g

Pro

du

ct

Cat

alo

g

The Service ModelA Holistic Service Management Approach

Product

Specification

Service

Specification

Service

Specification

Service

Specification

Fulfillment

Process

Data Model

(SID)Assurance

Process

Assurance

RulesFulfillment

Rules

5


Service Model DefinitionTechnologies

Bonita XPDLProcess/Workflow

Comptel Catalog /

DXSI Active Catalog (PSA) /

Data Model (SID)

DroolsRules/Policy

Rules Engine

Service Fabric Broker Execution

Workflow /

Process Engine

Publish

Orchestration Plan

Define

and

Design

Store

and

Reuse

Deploy

and RunComplex Event

Processing

Service Model

Repository

Common

Data Model


Demonstration Goals:

A Service Model and Service Catalog enables: Association of resources to products, regardless of the resource

providing the services (aka “Parts”)

Facilitation of converged product offerings across technical and corporate boundaries (aka “Assembly”)

Demonstrate the feasibility of creating service specifications that support and complement the full product development lifecycle:

• Graphical representation of the service definition

• Creation & assembly of composite services in Service Catalog (Comptel Catalog) following the Service Component Architecture (SCA) Pattern

• Operational execution of composite services for decomposition and fulfillment

• Invocation of the service management interface for provisioning and assurance.


Scenario setup: Superior Supply Co.

Hosted Exchange

Denver

Dallas

DetroitToledo

Network

Cloud Broker

Web Hosting (SaaS)

IP PBX

IP PBX

IP PBX

Customer purchases a VoIP SIP Trunk Network to service 3 locations: Denver, Dallas and Detroit.

They would like Direct Inward Dial (DID) numbers in Toledo that are localized and routed to the Detroit office.

Along with voice and data, the customer is also provided hosted Exchange email (SaaS) and platform as a service (SaaS/PaaS) to serve as their web store front.

Entire solution is white-labeled to the customer, but provided across different domains

8


Scenario 3:

Cloud

Failover

BT Cloud Broker

[Fulfill, Assure]

PSAInterface

Hosted EmailAWS EC2

SDF Fulfill Web

ServiceInterface

Product Manager

Service Configuration

Qwest

Customer

Qwest Network

EMS

DataXtend

[SID]

Service Modeler

SOA Designer

•XPDL Workflow

•Business Rules

•SID Data Model

•SCA Assemblies

Organization

Network Cadence

Qwest/Comptel

BT

Progress Software

Order Entry

Active Catalog

BT Koala

Cloud Providers

Product Catalog

Technical Architecture

WebService

Scenario 4:

Alarm


[Create, Fulfill, Assure]

Scenario 1:

Design

Scenario 2:

FulfillPSAInterface

9


Scenario 1: View and Create Services

Context

Qwest identifies a market opportunity & establishes a new product to manage VoIP QoS & Managed Email platform.

Step 1: View Existing• Review existing WAN and SIP Trunk service definitions.

• Service definition mapping (product/rules/process)

• Observe common building blocks that have been reused

Step 2: Create New Service Definitions• Create VoIP Product Quality Analyzer

• Create Managed Exchange using external catalog


Service AssemblyReusing Existing Services

11


Fulfill

BT Cloud Broker

[Fulfill, Assure]

PSAInterface

Exchange EmailAWS EC2

Product Manager

Customer

Qwest Network

EMS

DataXtend

[SID]

Organization

Network Cadence

Qwest/Comptel

BT

Progress Software

Order Entry

Active Catalog

BT Koala

Cloud Providers

Product Catalog

Scenario 2 – Fulfill

FulfillService Fabric Broker


Fulfill

OrderPSAInterface

12


Scenario 2: Fulfill Qwest & Cloud Products

Context• Fulfill Superior Supply Co Order request:

VOIP SIP Trunk service with DID at 3 locations

MS Exchange Email via Cloud partner

Cloud-based Web Application via Cloud partner

Step 1: Configure & Submit Order

Step 2: Demonstrate Service Catalog • Order validation – data, rules & dependencies verified

• Order decomposition – service level rules

• Order processing – order orchestration & process execution plan generation

Step 3: Show resulting output• Qwest and Cloud provisioning systems.


Cloud ServiceFulfillment Orchestration Process

14


Cloud Burst

BT Cloud Broker

[Fulfill, Assure]

PSAInterface


Service

Configuration

Customer

Qwest Network

EMS

DataXtend

[SID]

Service Modeler

SOA Designer

•XPDL Workflow

•Business Rules

•SID Data Model

•SCA Assemblies

Organization

Network Cadence

Qwest/Comptel

BT

Progress Software

Order Entry

Active Catalog

BT Koala

Cloud Providers

Product Catalog

Scenario 3 – Cloud Burst



PSAInterface

Product Manager

15


Role of the BT Cloud Broker

Support the assembly of cloud-based services

• Reduce service development cycle times

• Reduce service development costs

Provide a single shop front to our customers

• Build on brand name to deliver trusted cloud services

• Reuse various cloud, network and IT resources

You can‟t go it alone

• Add value to underlying resources

e.g. Provide guarantees, improve customer experience, speed access to

resources

16


BT Cloud Broker Architecture

17

BT Cloud Broker

Active Catalog

Deployment

ManagerPolicy Manager

Fault Manager

AWS EC2

BT Koala

Element

Manager

Martlesham, UK

Orlando, USA

East Coast, USA

UK


BT Cloud Broker – Service Scenarios

Cloud App without Business Continuity

• Provision of „unassured‟ App on Cloud “A”

• Traumatic failure of Cloud “A”

• Resultant failure of App

Cloud App with Business Continuity

• Provision of „assured‟ App on Cloud “A”

• Traumatic failure of Cloud “A”

• Temporary failure of App

• App migration to Cloud “B”

• Restoration of App

18


Cloud App Without Business Continuity

19

Customer

AWS EC2 Cloud

(JBOSS, Orlando App)

3. Provide

BT Cloud Broker

2. Provide

App users

4. Use app

1. Order cloud app without

business continuity

6. Unable

to use app

Service Active Catalog /

Implementation

Product Active Catalog /

Implementation

5. Infrastructure

failure

http://www.thetechherald.com/media/images/200810/InternetExplorer_1.jpg


Cloud App With Business Continuity

20

Customer

AWS EC2 Cloud


3. Provide

BT Cloud Broker

2. Provide

App users

7. Use app

1. Order cloud app with

business continuity

15. Continue to use app

AWS EC2 Cloud

(nginx)

4. Provide

6. Configure11. Fault

event14. Reconfigure

BT Koala Cloud*


12. Provide

* Part of BT’s VDC programme

10. Fault

event

Nagios

Fault Assurance

5. Register13. Register

9. Temporarily

unable to use app

8. Infrastructure

failure Service Active Catalog /

Implementation

Product Active Catalog /

Implementation

http://www.thetechherald.com/media/images/200810/InternetExplorer_1.jpg


Network

Event

BT Cloud Service

Broker

PSAInterface


Qwest Product Mgmt

Customer

Qwest Network

EMS

DataXtend

[SID]

Organization

Network Cadence

Qwest/Comptel

BT

Progress Software

Order Entry

Active Catalog

BT Koala

Cloud Providers

Product Catalog

Scenario 4 – Assure

Event



PSAInterface

Repair

Workflow

Process

Network

Operations

21


Scenario 4: Customer Care Event Has Occurred

Context• Network event has occurred that affects Superior Supply

Co‟s VoIP Trunk Product

Step 1: Demonstrate execution of Care process steps.


Service Catalog• Correlate the products we sell with the resources

needed to provide them

• Facilitate rapid delivery of converged products provided by Qwest and our service partners

Catalyst• Demonstrate services catalog feasibility for both

traditional telecom and cloud-based products

• Evaluate the role of a Service Catalog in enabling rapid service definition, reconfiguration and reuse

Q&A• Visit our booth

Wrap-Up and Q&A

23


Conclusion


A.Technical Details

B.Data Models

C.Process Workflows and Rules

D.Active Catalog Screenshots

E. Catalyst Architecture

F. TMForum Alignment

Appendices


Appendix A

Technical Implementation

Details

26


Catalyst Technical Demonstration

Technical construction of Service Model

• XSD that comprises Workflow (XPDL), Rules (Drools), and Model (XSD/SID)

• Open source tools for defining model

Bonita (XPDL)

Drools Editor

SCA (SOA assembly and interaction diagrams)

System interaction with the Model

• Provisioning workflow execution

• PSA Interfaces (Active Catalog)

• SaaS capabilities on “cloud” (Amazon)

DXSI –Data Xtend Semantic

Integrator Designer

PSA – Product Service Assembly

SCA – Service Component

Architecture

SDF – Service Delivery Framework

SID – Shared Information Data

Model

SOA – Service Oriented

Architecture

XPDL – XML Process Definition

Language

Acronyms


Detailed Technical Architecture - Qwest

Service Component

Architecture (SCA)

Create Fulfill Assure Charge AnalyticsRevenue

Assurance

Service Broker Orchestration

Service Model Repository

Process/Workflow Data Model (SID) Rules/Policy

Service Functional Definition

Network

Resources

PSA Interface

Provisioning

System

Service Management

Interfaces

Service Management

Interfaces

Comptel CatalogService Assembly

SCA Component

Order Entry Order Mgmt CRM Billing

Customer Management Layer

PSA Interface:

iQuery, List,

Transaction

PSA

Interface:

Capabilities

MS Exchange

Provisioning

BT Cloud Catalog


Service Model Repository

Service SME create, modify and delete definitions• Understand characteristics and interactions of

services

• Understand the details in the service management functional definitions (example: Fulfill VOIP, charging rules for Hosted Exchange)

Effectively a database with well defined structure and interfaces

Expose PSA for manageability and inter-catalog messaging

Active Catalog aggregates catalogs from Qwest, BT, and Cloud providers


Service Broker Details

Process engine for orchestrated execution of automated or manual workflows• Acts similar to BPM/ESB

• Web console (or exposure to portal) for manual task assignments

Policy definition and engine• Similar to process engine, dynamically applies rules to data

Interface to provisioning systems• Performs service fulfillment and activation

Interface to Service Assurance (NMS/EMS):• Determining impact or interaction of services

• Retrieve KPI/KQI data

• Maintain fault/alarm correlation rules or workflow.


System Details

Service Model Definition Creation

• Bonita Eclipse Designer for Workflow Definitions and Drools for rules definition

• Stubbed flow process definitions for Qwest provided services (VOIP, SIP Trunk)

• Fully capable process flows for Chinook (Hosted Exchange)

• Data store for the Service Model Definition

Service Broker

• Execution platform for XPDL process flows – Bonita engine

• Dashboard for monitoring flows – Bonita web view

• Rules engine for interpreting SLM definition rules - Drools

Service Component Architecture (Granular Service Assembly)

• SCA design and composition tool for assembling services

Comptel Catalog

• Assemble service definitions from multiple sources for a product offering

• Act as a central Catalog for the Order Management System

• Order Management fulfillment orchestration

BT Catalog

• Provide fulfillment and assurance interfaces for BT private cloud and Amazon EC2 services


BT Trusted Cloud Broker:Cloud Burst Fail-Over service scenario showing Service Assembly, Publication, Delivery, Configuration and Assurance

Gary Bruce, BT Innovate & Design


Trusted Cloud Broker (Composition Scenarios)

EC2 Cloud Computing

(nginx)

Koala Cloud Computing

(LAMP)

EC2 Cloud Computing

(LAMP)

Capability: Computing

With Burst On Failure

Dependency: Broadband

ConnectivityItem 1: Premium Fail-Over

Cloud Computing

Fault Assurance Cyclic-based Pricing

EC2 Cloud Computing

(nginx)

Koala Cloud Computing

(LAMP)

EC2 Cloud Computing

(LAMP)

Capability: Computing

With Burst To Scale Up

Dependency: Broadband

ConnectivityItem 2: Premium Scale-Up

Cloud Computing

Performance Assurance Usage-based Pricing

Premium Cloud Computing Catalog

Management

Items


Premium Cloud Computing <Provide>

Premium Fail-Over† Cloud Computing (Provide Scenario)

Provide

EC2 Cloud Computing <Provide> Koala Cloud Computing <Provide>

RequestNumber of Instances = 1

Instance Type = m1.small

Platform Type = LAMP


Security Group = default


AMI ID = // e.g. nginx

Availability Zone = us-east-1

CompleteInstance ID

Instance Public IP Address1


Security Group = BCOS


AMI ID = // e.g. LAMP

Availability Zone = harmondsworth

CompleteInstance ID

Instance Public IP Address2

Lookup

AMI ID

Provide load

balancer

Provide Koala

computing capability

Configure load

balancer

CompleteInstance Public IP Address2

LB Public IP Address1

Identify available cloud

infrastructure*S J

* Done according to SLAs

Item <Transaction>

† The Premium Scale-Up Cloud Computing scenario is the same as this and the following scenarios.

Workflow action


Premium Cloud Computing <Deploy App>

Premium Fail-Over Cloud Computing (Deploy App Scenario)

Deploy App

Koala Cloud Computing <Deploy App>

RequestApp Type = // e.g. Web App

RequestApp URI = // Web App location

Instance ID

App Destination = // Deployment directory

CompleteStatus

Lookup App URI(s)

CompleteStatus

Deploy App on KoalaS J


Premium Cloud Computing <Cloud Burst>

Premium Fail-Over Cloud Computing (Cloud Burst Scenario)

Cloud Burst†

EC2 Cloud Computing <Provide> EC2 Cloud Computing <Deploy App>

RequestCloud Infrastructure To Burst


Security Group = default


AMI ID = // e.g. LAMP

Availability Zone = us-east-1

CompleteInstance ID

Instance Public IP Address

RequestApp URI = // Web App location

Instance ID

App Destination = // Deployment directory

CompleteStatus

Lookup

AMI ID

Provide EC2


Configure load

balancer

CompleteCloud Burst Status

Identify available

cloud infrastructure*S J

† For the Fail-Over product, this transaction will be invoked upon detection of a catastrophic failure.

For the Scale-Up product, this transaction will be invoked by an internal SLA event.

Deploy App

on EC2

Lookup

App URI

* This is done according to SLA


Premium Cloud Computing <Cloud Unburst>

Premium Fail-Over Cloud Computing (Cloud Unburst Scenario)

Cloud Unburst†

EC2 Cloud Computing <Cease>

RequestCloud Infrastructure To Unburst

RequestInstance ID

CompleteStatus

Configure load

balancer

Cease EC2


Configure load

balancer

CompleteCloud Unburst Status

Identify cloud

infrastructure to clear*

Period of

grace

* This is done according to SLA

† For the Fail-Over product, this transaction will be invoked upon detection of the failure clearing.

For the Scale-Up product, this transaction will be invoked by an internal SLA event.

Note, a cloud unburst transaction will be gracefully undone (e.g. load-balancer reconfigured) if a cloud burst transaction is received from the same cloud infrastructure.

S J


Appendix B

Data Models

38


SID Context

TMF Catalyst

Relevant Portions of the TMF SID

SID Abstract Class

Legend

SID Abstract Class

In Service Catalogue

Service Catalogue

Data Domain

Catalyst Scenarios

Data Domain

ProductProduct Specification

ResourceResource Specification

Service

Resource Facing Service Customer Facing Service

Service Specification

Customer Facing Service Spec Resource Facing Service Spec

0..1

*

t RFSSpecHasResourceSpecs

prodSpecMadeAvailableAs u productOfferDescribes u1

*

serviceSpecSpecifiedService u

productSpecRealizedAsCFSServiceSpec

q

*

*

*1

productRealizedAsCFSService

q

0..1

* 0..1 resourceSpecSpecifiesResource u

*

*

0..1

*

**

*

pro

du

ctR

ea

lize

dA

sR

eso

urc

e u

pro

du

ctS

pe

cR

ea

lize

dA

sR

eso

urc

eS

pe

c u

involveResourceSpecs u

**

Product Offering


CSF Service Spec Objects


Service

1

* p

specifiesService

SID Abstract Class

Scenario Concrete

Class

Legend IQ Networking with SIP Trunk

Non-Attributed SID-compliant Object Model

**

involvedServiceSpecs u

Managed Entity

Service Spec Characteristic

Service Spec Characteristic Value

1

*

1

*

isCharacterisedBy u

takesOnServiceSpecCharacteristicValue qCustomer Facing Service (CFS) Spec

CFS Spec Composite

0..1

* hasCFSSpecs u

ASSURANCE

MANAGED

SERVICE

PaaS

TRANSPORT

ACCESS

CPE

IQ Networking

With SIP Trunk

Service Package Spec

CFS Spec Atomic

LOCAL LOOP

PORT

DEVICE

(ROUTER)

MANAGED

e-MAIL

(BT)

TELEPHONY

SERVICESIP TRUNK


CSF Service Spec Objects with Sample Attributes

MANAGED e-MAIL

(BT)


Service

1

* p

specifiesService

SID Abstract Class

Scenario Concrete

Class


Partially-Attributed SID-compliant Object Model

**


Managed Entity

Service Spec Characteristic

Service Spec Characteristic Value

1

*

1

*

isCharacterisedBy u

takesOnServiceSpecCharacteristicValue qCustomer Facing Service (CFS) Spec

CFS Spec Composite

0..1

* hasCFSSpecs u

ASSURANCE

MANAGED

SERVICE

PaaS

TRANSPORT

ACCESS

CPE

IQ Networking

With SIP Trunk

Service Package Spec

CFS Spec Atomic

TELEPHONY

SERVICE

NOTE: Partial attribution shown to illustrate highlights

of IQ Networking with SIP Trunk scenario.

ASSURANCE

PORT

ACCESS TYPE

CIRCUIT SPEED

CONNECTION TYPE

QoS

LOCAL LOOP

LOOP PACKAGE

SIP TRUNK

INTERCONNECT TYPE

DIVERSITY TYPE

MAX SESSIONS FIXED

MAX SESSIONS USAGE

VOIP LOCATIONS

TELEPHONE NUMBERS

REMOTE DID

DEVICE (ROUTER)

VENDOR

MODEL

TYPE

CONFIG TEMPLATE


Logical Product/Service Model mapping

Service SpecificationSID Abstract Class

Scenario Concrete

Class


Sample CSF to RFS Mapping

**


Customer Facing Service (CFS) Spec

CFS Spec Atomic

NOTE: Partial attribution shown to illustrate highlights

of IQ Networking with SIP Trunk scenario.

MANAGED e-MAIL

(BT)

ASSURANCE

DEVICE (ROUTER)

VENDOR

MODEL

TYPE

CONFIG TEMPLATE

PORT

ACCESS TYPE

CIRCUIT SPEED

CONNECTION TYPE

QoS

LOCAL LOOP

LOOP PACKAGE

SIP TRUNK

INTERCONNECT TYPE

DIVERSITY TYPE

MAX SESSIONS FIXED

MAX SESSIONS USAGE

VOIP LOCATIONS

TELEPHONE NUMBERS

REMOTE DID

Resource Facing Service (RFS) Spec

RFS Spec Atomic

VOIP TELEPHONE NUMBER

NUMBER MANAGEMENT ID

PORTED TN FLAG

PROVIDER TO QCC

TELEPHONE NUMBER

TRIGGER POINT

VOICE MAILBOX IND

VOIP COMPRESSION COMBO

WHITEPAGES LISTING QTY

SIP TRUNK NON-PORTED TN

TRIGGER POINT

SIP TRUNK STD PORTED TN

TRIGGER POINT

>Ref: Usage Parameters

USAGE PARAMETERS

CANADIAN USAGE FLAG

DIRECTORY ASSIST FLAG

DOMESTIC USAGE FLAG

INTERNATIONAL FLAG

LOCAL USAGE FLAG

MEXICO USAGE FLAG

VOIP TN SEID

SIP TRUNK TN

911 PPUL SEID

NUMBER MANAGEMENT ID

VOIP BIDIRECTIONAL SEID

Or


Appendix C

Process Flows and Rules

43


VoIP Trunk Service Provisioning


CPE Provisioning


Layer 1 Circuit Provisioning


VoIP Trunk Provisioning


VoIP Assurance Service


Rules ScreenshotDrools Editor

49


Appendix D

Active Catalog Screenshots

50


Active Catalog: Qwest Local Items


Active Catalog: VoIP Service


Appendix E

Alignment with TMForum

53

Documents

TMF Service Model Catalyst