TMF Service Model Catalyst

Service Model
Catalyst
Getting the Provider to Cloud 9
Copyright 2009 TeleManagement Forum, All Rights Reserved.
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
Customer Expectations
Product Convergence
Lower Cost
Performance
Delivery time
Product Providers
Cloud
CSP
Network
Cloud
Cloud
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
Cant 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
Cloud Marketplace Conceptual Solution

Customer Web
Portal
Product
Offerings
Hosted Exchange Email
Active
Catalog
Cloud
Create
Fulfill
Assure
Charge
Software and Platform

as a Service (SaaS/PaaS)
Service
Execution
Analytics
Service Fabric Broker
CSP2
CSP1
The Service Model
Model
Components
Service
Catalog
Product
Catalog
A Holistic Service Management Approach
Product
Specification
Service
Specification
Fulfillment
Rules
Service
Specification
Fulfillment
Process
Data Model
(SID)
Service
Specification
Assurance
Process
Assurance
Rules
Service Model Definition

Technologies
Define
and
Design
Comptel Catalog /
DXSI
Bonita XPDL
Process/Workflow
Drools
Rules/Policy
Active Catalog (PSA) /

Data Model (SID)
Store
and
Reuse
Service Model
Repository
Publish
Orchestration Plan
Deploy
and Run
Workflow /
Process Engine
Complex Event
Processing
Rules Engine
Common
Data Model
Service Fabric Broker Execution

6
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.
7
Scenario setup: Superior Supply Co.

Customer purchases a VoIP SIP
Trunk Network to service 3
Toledo
locations: Denver, Dallas and
Detroit
Detroit.
They would like Direct Inward
Dial (DID) numbers in Toledo
that are localized and routed to
Network
the Detroit office.
Along with voice and data, the
customer is also provided hosted
Exchange email (SaaS) and
Cloud Broker
platform as a service
Web Hosting (SaaS)
(SaaS/PaaS) to serve as their
web store front.
Entire solution is white-labeled
to the customer, but provided
Hosted Exchange
across different domains
IP PBX
IP PBX
Denver
IP PBX
Dallas
Technical Architecture
XPDL Workflow
Business Rules
SID Data Model
SCA Assemblies
Order Entry
Product Catalog
Qwest
Customer
Active Catalog
Scenario 4:
Alarm
PSA
Interface
PSA
Interface
BT Cloud Broker
[Fulfill, Assure]

[Create, Fulfill, Assure]
BT
Network Cadence
Progress Software
Web
Service
Service
Interface
BT Koala
EMS
Hosted Email
Cloud Providers
9
Organization
Qwest/Comptel
DataXtend
[SID]
SDF Fulfill Web
Qwest Network
Service
Configuration
Product Manager
Scenario 2:
Fulfill
Service Modeler
SOA Designer
Scenario 1:
Design
AWS EC2
Scenario 3:
Cloud
Failover
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
10
Service Assembly
Reusing Existing Services
11
Scenario 2 Fulfill
Order Entry
Product Catalog
Customer
Active Catalog
Product Manager
Order
PSA
Interface
Organization
Qwest/Comptel
DataXtend
[SID]
Fulfill
PSA
Interface
BT Cloud Broker
[Fulfill, Assure]

BT
Network Cadence
Progress Software
Fulfill
BT Koala
EMS
Qwest Network
Exchange Email
Cloud Providers
12
AWS EC2
Fulfill
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.
13
Cloud Service
Fulfillment Orchestration Process
14
Scenario 3 Cloud Burst

XPDL Workflow
Business Rules
SID Data Model
SCA Assemblies
Order Entry
Product Catalog
Customer
Active Catalog
Service
Configuration
Product Manager
PSA
Interface
Service Modeler
SOA Designer
PSA
Interface
Qwest/Comptel
DataXtend
[SID]

BT Cloud Broker
[Fulfill, Assure]
Exchange Email
Cloud Providers
15
BT
Network Cadence
Progress Software
BT Koala
EMS
Qwest Network
Organization
AWS EC2
Cloud Burst
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 cant go it alone
Add value to underlying resources
16
e.g. Provide guarantees, improve customer experience, speed access to

resources
BT Cloud Broker Architecture
BT Cloud Broker
Active Catalog
Orlando, USA
Deployment
Manager
Policy Manager
Martlesham, UK
Element
Manager
East Coast, USA
AWS EC2
BT Koala
17
Fault Manager
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
18
Provision of assured App on Cloud A

Traumatic failure of Cloud A
Temporary failure of App
App migration to Cloud B
Restoration of App
Cloud App Without Business Continuity
1. Order cloud app without

business continuity
App users
Customer
4. Use app
6. Unable
to use app
2. Provide
BT Cloud Broker
3. Provide
AWS EC2 Cloud

(JBOSS, Orlando App)
5. Infrastructure
failure
Product Active Catalog /

Implementation
Service Active Catalog /
Implementation
19
Cloud App With Business Continuity

App users
1. Order cloud app with

business continuity
Customer
7. Use app
15. Continue to use app

9. Temporarily
unable to use app
2. Provide
BT Cloud Broker
11. Fault
event
5. Register
13. Register
Nagios
Fault Assurance
10. Fault
event
4. Provide
12. Provide
6. Configure
14. Reconfigure
3. Provide
AWS EC2 Cloud

8. Infrastructure
failure
20
AWS EC2 Cloud

(nginx)
BT Koala Cloud*
* Part of BTs VDC programme
Product Active Catalog /

Implementation
Service Active Catalog /
Implementation
Scenario 4 Assure
Event
Order Entry
Product Catalog
Customer
Active Catalog
Network
Operations
Qwest Product Mgmt
Repair
Workflow
Process
PSA
Interface

BT Cloud Service
Broker
BT
Network Cadence
Progress Software
BT Koala
EMS
Qwest Network
Organization
Qwest/Comptel
DataXtend
[SID]
Network
Event
PSA
Interface
Exchange Email
AWS EC2
Cloud Providers
21
Scenario 4: Customer Care Event Has Occurred
Context
Network event has occurred that affects Superior Supply

Cos VoIP Trunk Product
Step 1: Demonstrate execution of Care process

steps.
22
Wrap-Up and Q&A
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
23
Conclusion
24
Appendices
A. Technical Details
B. Data Models
C. Process Workflows and Rules
D. Active Catalog Screenshots
E. Catalyst Architecture
F. TMForum Alignment
Appendix A
Technical Implementation
Details
26
Acronyms
DXSI Data Xtend Semantic
27
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
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)
Detailed Technical Architecture - Qwest

Comptel Catalog
PSA Interface:
iQuery, List,
Transaction
Order Entry
Service Assembly
Order Mgmt
CRM
Billing
Customer Management Layer
PSA Interface
BT Cloud Catalog
Service Component
Architecture (SCA)
PSA
Interface:
Capabilities
Create
SCA Component
Service Management
Interfaces
Fulfill
Assure
Charge
Analytics
Revenue
Assurance
Service Broker Orchestration

Process/Workflow
Data Model (SID)
Rules/Policy
Service Management
Interfaces
Service Functional Definition
Service Model Repository

28
Network
Resources
Provisioning
System
MS Exchange
Provisioning
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
29
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.
30
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
31
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)

Premium Cloud Computing Catalog
Item 1: Premium Fail-Over

Cloud Computing
Dependency: Broadband
Connectivity
Capability: Computing
With Burst On Failure
EC2 Cloud Computing

(nginx)
Koala Cloud Computing

(LAMP)
Fault Assurance
Item 2: Premium Scale-Up

Cloud Computing
EC2 Cloud Computing
(nginx)
EC2 Cloud Computing

(LAMP)
Cyclic-based Pricing
Capability: Computing
With Burst To Scale Up
Koala Cloud Computing
(LAMP)
Performance Assurance
Management
Items
Dependency: Broadband
Connectivity
EC2 Cloud Computing
(LAMP)
Usage-based Pricing
Premium Fail-Over Cloud Computing (Provide Scenario)

Provide
Request
Complete
Instance Public IP Address2
LB Public IP Address1
Number of Instances = 1
Instance Type = m1.small
Platform Type = LAMP
Provide load
balancer
Identify available cloud

infrastructure*
Lookup
AMI ID
Provide Koala
computing capability
Configure load
balancer
Premium Cloud Computing <Provide>
Request
Complete
Security Group = default
AMI ID = // e.g. nginx
Availability Zone = us-east-1
Instance ID
Request
EC2 Cloud Computing <Provide>
Complete
Security Group = BCOS
AMI ID = // e.g. LAMP
Availability Zone = harmondsworth
Instance ID
Koala Cloud Computing <Provide>
The Premium Scale-Up Cloud Computing scenario is the same as this and the following scenarios.
* Done according to SLAs

Item <Transaction>
Workflow action
Premium Fail-Over Cloud Computing (Deploy App Scenario)
Deploy App
Complete
Request
Status
App Type = // e.g. Web App
Lookup App URI(s)
Deploy App on Koala
Premium Cloud Computing <Deploy App>
Request
App URI = // Web App location
Instance ID
App Destination = // Deployment directory
Complete
Status
Koala Cloud Computing <Deploy App>
Premium Fail-Over Cloud Computing (Cloud Burst Scenario)

Cloud Burst
Request
Complete
Cloud Burst Status
Cloud Infrastructure To Burst
Identify available
cloud infrastructure*
Lookup
AMI ID
Provide EC2
Lookup
App URI
Deploy App
on EC2
Configure load
balancer
Premium Cloud Computing <Cloud Burst>
Request
Complete
Security Group = default
AMI ID = // e.g. LAMP
Availability Zone = us-east-1
Instance ID
Instance Public IP Address
Request
EC2 Cloud Computing <Provide>
Complete
App URI = // Web App location

Instance ID
App Destination = // Deployment directory
Status
EC2 Cloud Computing <Deploy App>
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.
* This is done according to SLA
Premium Fail-Over Cloud Computing (Cloud Unburst Scenario)
Cloud Unburst
Request
Complete
Cloud Unburst Status
Cloud Infrastructure To Unburst
Identify cloud
infrastructure to clear*
Configure load
balancer
Period of
grace
Configure load
balancer
Cease EC2
Premium Cloud Computing <Cloud Unburst>
Request
Instance ID
Complete
Status
EC2 Cloud Computing <Cease>
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.
* This is done according to SLA
Appendix B
Data Models
38
SID Context
Legend
SID Abstract Class
In Service Catalogue
SID Abstract Class
Service Catalogue
Data Domain
Catalyst Scenarios
Data Domain
TMF Catalyst
Relevant Portions of the TMF SID
prodSpecMadeAvailableAs u
productOfferDescribes u
Product Offering
0..1
Product Specification
Product
0..1
*
productSpecRealizedAsCFSServiceSpec
productRealizedAsCFSService
productSpecRealizedAsResourceSpec u
Service Specification
Customer Facing Service Spec
Resource Facing Service Spec
productRealizedAsResource u
serviceSpecSpecifiedService u
1
Service
Resource Facing Service
Customer Facing Service
0..1
RFSSpecHasResourceSpecs
0..1
Resource Specification
resourceSpecSpecifiesResource u
Resource
involveResourceSpecs u
39
CSF Service Spec Objects

Legend
Managed Entity
IQ Networking with SIP Trunk

Non-Attributed SID-compliant Object Model
SID Abstract Class
Service
Scenario Concrete
Class
p
specifiesService
involvedServiceSpecs u
*
*
1
1
isCharacterisedBy u
Service Spec Characteristic

hasCFSSpecs u
1
Customer Facing Service (CFS) Spec
takesOnServiceSpecCharacteristicValue q
Service Spec Characteristic Value

0..1
CFS Spec Composite
TRANSPORT
ACCESS
CFS Spec Atomic
Service Package Spec
IQ Networking
With SIP Trunk
PORT
LOCAL LOOP
TELEPHONY
SERVICE
SIP TRUNK
CPE
DEVICE
(ROUTER)
ASSURANCE
MANAGED
e-MAIL
MANAGED
SERVICE
(BT)
PaaS
CSF Service Spec Objects with Sample Attributes

Legend
Managed Entity

Partially-Attributed SID-compliant Object Model
SID Abstract Class
Service
Scenario Concrete
Class
p
specifiesService
*
*
1
1
isCharacterisedBy u
Service Spec Characteristic

hasCFSSpecs u
1
takesOnServiceSpecCharacteristicValue q
Service Spec Characteristic Value

0..1
CFS Spec Composite
TRANSPORT
ACCESS
TELEPHONY
SERVICE
CFS Spec Atomic
Service Package Spec
IQ Networking
With SIP Trunk
PORT
ACCESS TYPE
CIRCUIT SPEED
CONNECTION TYPE
QoS
LOCAL LOOP
NOTE: Partial attribution shown to illustrate highlights

of IQ Networking with SIP Trunk scenario.
DEVICE (ROUTER)
VENDOR
MODEL
TYPE
CONFIG TEMPLATE
ASSURANCE
LOOP PACKAGE
MANAGED e-MAIL
CPE
SIP TRUNK
(BT)
ASSURANCE
MANAGED
SERVICE
INTERCONNECT TYPE
DIVERSITY TYPE
MAX SESSIONS FIXED
MAX SESSIONS USAGE
VOIP LOCATIONS
TELEPHONE NUMBERS
REMOTE DID
PaaS
Logical Product/Service Model mapping

Legend
SID Abstract Class

Sample CSF to RFS Mapping
NOTE: Partial attribution shown to illustrate highlights
of IQ Networking with SIP Trunk scenario.
Scenario Concrete
Class
Resource Facing Service (RFS) Spec
CFS Spec Atomic
RFS Spec Atomic
VOIP TELEPHONE NUMBER

DEVICE (ROUTER)
VENDOR
MODEL
TYPE
CONFIG TEMPLATE
ASSURANCE
PORT
ACCESS TYPE
CIRCUIT SPEED
CONNECTION TYPE
QoS
LOCAL LOOP
NUMBER MANAGEMENT ID
PORTED TN FLAG
PROVIDER TO QCC
TELEPHONE NUMBER
TRIGGER POINT
VOICE MAILBOX IND
VOIP COMPRESSION COMBO
WHITEPAGES LISTING QTY
LOOP PACKAGE
SIP TRUNK TN
MANAGED e-MAIL
SIP TRUNK
(BT)
INTERCONNECT TYPE
DIVERSITY TYPE
MAX SESSIONS FIXED
MAX SESSIONS USAGE
VOIP LOCATIONS
TELEPHONE NUMBERS
REMOTE DID
911 PPUL SEID

NUMBER MANAGEMENT ID
VOIP BIDIRECTIONAL SEID
SIP TRUNK NON-PORTED TN
TRIGGER POINT
Or
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
Appendix C
Process Flows and Rules
43
VoIP Trunk Service Provisioning
CPE Provisioning
Layer 1 Circuit Provisioning
VoIP Trunk Provisioning
VoIP Assurance Service
Rules Screenshot
Drools Editor
49
Appendix D
Active Catalog Screenshots
50
Active Catalog: Qwest Local Items
Active Catalog: VoIP Service
Appendix E
Alignment with TMForum
53

TMF Service Model Catalyst

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TMF Service Model Catalyst

Uploaded by

Copyright:

Available Formats

Service Model

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Achieve consistent Service Model

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Increasing Demands for Product

We Need a Holistic Model-Driven Approach to Product Development

Cloud Marketplace Conceptual Solution

Software and Platform

Service Fabric Broker

Copyright 2009 TeleManagement Forum, All Rights Reserved.

The Service Model

A Holistic Service Management Approach

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Service Model Definition

Active Catalog (PSA) /

Service Fabric Broker Execution

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Demonstrate the feasibility of creating service specifications that

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Scenario setup: Superior Supply Co.

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Service Fabric Broker

SDF Fulfill Web

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Scenario 1: View and Create Services

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Service Fabric Broker

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Scenario 2: Fulfill Qwest & Cloud Products

Fulfill Superior Supply Co Order request:

VOIP SIP Trunk service with DID at 3 locations

Step 1: Configure & Submit Order

Order validation data, rules & dependencies verified

Step 3: Show resulting output

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Scenario 3 Cloud Burst

Service Fabric Broker

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Role of the BT Cloud Broker

Provide a single shop front to our customers

You cant go it alone

Add value to underlying resources

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

Copyright 2009 TeleManagement Forum, All Rights Reserved.

BT Cloud Broker Architecture

East Coast, USA

Copyright 2009 TeleManagement Forum, All Rights Reserved.

BT Cloud Broker Service Scenarios

Cloud App with Business Continuity

Provision of assured App on Cloud A

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Cloud App Without Business Continuity

1. Order cloud app without

AWS EC2 Cloud

Product Active Catalog /

Copyright 2009 TeleManagement Forum, All Rights Reserved.

Cloud App With Business Continuity

1. Order cloud app with

15. Continue to use app

AWS EC2 Cloud

AWS EC2 Cloud

Product Active Catalog /