Transcript OASIS Workshop

Impact of SOA on
TM Forum
Specifications
Tony Richardson
(Senior Program Manager)
1
Copyright © TM Forum, 2008 All Rights Reserved.
Agenda
 Brief
Outline of TM Forum
SOA – Service Delivery
Framework (SDF)
 Applying
 SOA and
NGOSS
 Summary
- Possible TM Forum /
OASIS work areas
2
Copyright © TM Forum, 2008 All Rights Reserved.
About TM Forum
World’s leading trade body focused on the
management of telecom, cable, media & information
services
Improves the way that services are created,
delivered, assured and charged through:
Leadership & guidance
Technology innovation & standards
Practical solutions through an Ecosystem of members
Members include service providers, network
operators, software suppliers, equipment suppliers
and systems integrators
3
Copyright © TM Forum, 2008 All Rights Reserved.
TM Forum Membership
Geographical Spread
4%
3%
Europe
17%
44%
Americas
Africa
32%
Middle East
Asia/Oceania
Around 700 members in
over 70 countries:
Membership Distribution
communications, cable, media,
consumer electronics
5%
Service Providers
4%
Hardware Manufacturers
26%
12%
14%
Software & Middleware Developers
7%
32%
System Integrators
Consultants
Academy
Copyright © TM Forum, 2008 All Rights Reserved.
Other
4
Collaboration Program
Service transformation
Service delivery frameworks
Content & information management
Component based architectures
Device management
Business
Requirements
Defining
Requirements
for NGOSS-based
Development
Enabling technologies and tools
Developers Tools
Business
Process
framework
Application
framework
Information
Framework
SOA
Neutral
Architecture
Prosspero
Interfaces
Lifecycle and Methodology
Collaboration Capabilities
Extensive website, Web Communities; White papers; Collaboration community Tools;
Webinars; Conferences, OpenOSS,
Copyright © TM Forum, 2008 All Rights Reserved.
5
Collaboration Program
Service transformation
Service delivery frameworks
Content & information management
Component based architectures
Device management
Business
Requirements
Defining
Requirements
for NGOSS-based
Development
Enabling technologies and tools
Developers Tools
Business
Process
framework
Application
framework
Information
Framework
SOA
Neutral
Architecture
Prosspero
Interfaces
Lifecycle and Methodology
Collaboration Capabilities
Extensive website, Web Communities; White papers; Collaboration community Tools;
Webinars; Conferences, OpenOSS,
Copyright © TM Forum, 2008 All Rights Reserved.
6
Convergence brings Opportunities and Challenges
Entertain
Cable
ment
Media
Web
Advert
ising
Telecom
•Technology kept many information markets separate
•Convergence allows entry into someone else's market
•Creates market explosion rather than coming together
7
Copyright © TM Forum, 2008 All Rights Reserved.
Service Delivery
Framework (SDF)
program
8
Copyright © TM Forum, 2008 All Rights Reserved.
Change of Communications Industry Landscape
 Delivery of next generation services happens in a framework
where the lines between Network and IT are blurred.
 IT expands its footprint from supporting services to becoming part of the service
to customer.
 Customers / end Users have greater expectations for:
 Blending existing and new services
 Supply of services anywhere, anytime, and through any chosen access means.
 Increasing pressure for efficient and effective Service
Management.
 Necessity for near-zero touch of business processes for delivering “next-gen
services” by integrating existing systems (both for Telco / non-Telco SPs).
 Need to create composite service marketplace across industry
sectors that also need to be managed & monetized.
 Service Providers need interoperability and agreed levels of compatibility across

Service Delivery Platforms (SDPs).
New providers (e.g. Content) enter in the market and organizations operate using
more complex business models.
99
Copyright © TM Forum, 2008 All Rights Reserved.
TM Forum’s Service Delivery Framework (SDF) programme
 Address the industry challenge of producing an environment for the
management of Next Generation Services.
 Supports and integrates all aspects in the lifecycle of “next-gen services” delivered


to a customer, across all the stakeholders, in an integrated Service Provider
environment.
Unifies under a common logical view all the functions to support the service
lifecycle: conceptualization, design, deployment, activation (execution), operation,
retirement.
SDF operation is based upon a defined Reference Model, which itself is based upon
SOA principles.
 SDF impacts
 Management specification for SDF will be realised through updates and additions to
existing TM Forum artefacts (Business Process Framework, Information Framework
etc.).
New specifications will be created by TM Forum (or liaised with other SDOs/Fora)
SDF will have impact on “new” B/OSS systems design and development.


 Strong liaisons with other Industry Groups has been established in
order to share the SDF vision / link into related work in these Groups.
10
10
Copyright © TM Forum, 2008 All Rights Reserved.
Attempt to position SDF and to illustrate relationship
with OSS/BSS
Device /
Client Layer
Access
Layer
Copyright © TM Forum, 2008 All Rights Reserved.
SCE
Application suites
SDF
SDP
Application Servers
SS7
IMS
SIP / IMS
IP / MPLS / PBT
SONET / SDH / WDM
Wireline:
DSL, Cable,
FTTx, PSTN
OSS/BSS Platforms
Transport
Layer
Control
Layer
Service
Layer
Internet / 3rd Parties / Enterprises
Wireless:
2G, 3G
WiFi, WIMAX
11
Overall context for the “TM Forum SDF Reference
Model” for SDF Services and their Management
SDF Management Support Service
Functional Interface
SDF Service
Functional Interface
Management Services
SDF Service
SDF Service
Management
Management
Interface Consumer Interface
SDF Management
Support Services
(SDF MSS)
<qualified name> SDF Services
SDF ISS
Consumer
SDF Infrastructure Support
Service Functional Interface
SDF ISS
Consumer
Infrastructure
Consumer
SDF Infrastructure Support Services
(SDF ISS)
Resource
Consumer
SDF Service
Consumer
Resources
Infrastructure
Legend
In scope
services
Out of scope
services
Out of scope elements
Copyright © TM Forum, 2008 All Rights Reserved.
In scope management/functional interfaces
In scope consumer interfaces
Out of scope management/functional interfaces
Out of scope consumer interfaces
Items for further study
12
Industry Groups involvement

OMA

IPsphere

Parlay / Parlay X

SDP Alliance

OASIS

ETSI / TISPAN

ITU-T / NGNMFG

IEEE/NGSON

ATIS / TMOC

CableLabs
 OSE / OSPE (open SDP for mobile service providers)
 Pan-SP B2B agreements on supply of IP-based services
 Network Service interfaces
 Practical best-of-breed SDP component integration
 IT capabilities for Service Component definition / combination
 NGN Sub-system components / Management Architecture
 NGN Management Roadmap
 NGN Overlay Network
 IPTV Management, NGS Accounting
 Positioning of cable-based services / specifications
Copyright © TM Forum, 2008 All Rights Reserved.
13
TM Forum
NGOSS Program
14
Copyright © TM Forum, 2008 All Rights Reserved.
NGOSS Frameworks
NGOSS (New Generation
Operation Systems and
Software) is based on four
interrelated frameworks
that form the core of the
NGOSS program
• Business Process
Framework – the eTOM
• Information framework –
the SID
• Systems Architecture
Framework – the TNA
• Applications Framework
– the TAM
Copyright © TM Forum, 2008 All Rights Reserved.
NGOSS Frameworks
Business
Process
Framework
eTOM
Information
Framework
SID
Applications
Framework
TAM
Architecture
Framework
TNA
15
Contracts – Lifecycle Development
1. Define the Business
2. Architect the Business
(Leadership Team,
Business Process Engineers)
(Enterprise IT Architects)
2
1
Business
Contract
1
Business
Contract
Corporate
Knowledge Shared
Base
1
System
Contract
NGOSS
Knowledge
Base
2
Business
Contract
System
Contract
Deployment. Implement
Contract
Contract
3
4
1
2
Business
Contract
System
Contract
Implement
Contract
3
4. Execute the Business
(Operations)
3. Implement the Business
(Development Org.)
Copyright © TM Forum, 2008 All Rights Reserved.
16
Related OASIS Specifications
SOA

OASIS SOA Reference Model TC
Developing a core reference model to guide and foster the creation of specific, serviceoriented architectures

OASIS Service Component Architecture / Bindings (SCA-Bindings) TC
Standardizing bindings for SCA services and references to communication protocols,
technologies and frameworks

OASIS Service Component Architecture / BPEL (SCA-BPEL) TC
Specifying how SCA component implementations for SOA can be written using BPEL

OASIS Service Component Architecture / Policy (SCA-Policy) TC
Defining an SCA policy framework to simplify SOA application development
Web Services

OASIS Framework for Web Services Implementation (FWSI) TC
Defining methods and functional components for broad, multi-platform, vendor-neutral crossindustry implementation of Web services

OASIS UDDI Specification TC
Defining a standard method for enterprises to dynamically discover and invoke Web
services

OASIS Web Services Quality Model TC
Defining common criteria to evaluate quality levels for interoperability, security, and
manageability of services

OASIS Web Services Transaction (WS-TX) TC
Defining protocols for coordinating the outcome of distributed application actions

WSDM Management Using Web Services (WSDM-MUWS) v1.0
17
Copyright © TM Forum, 2008 All Rights Reserved.
Summary


Increasing - Telecom / IT Convergence
Business Processes - itSMF
 eTOM /ITIL (IT Information Library - IT Service Management
Forum)

Application of SOA – OASIS
 SDF –
 Development / Application of SDF Management
Framework.
 Linkage into OASIS specifications
 NGOSS
 Development / Application of NGOSS Contracts.
 Extension of NGOSS specifications (eg eTOM, SID, TAM
etc) into other SOA-based applications in other Industry
Sectors
18
Copyright © TM Forum, 2008 All Rights Reserved.
Closing
 Thanks
for your Attention!
 Questions?
 Contact:
 Tony Richardson
 [email protected]
 +44 1394 386293
19
Copyright © TM Forum, 2008 All Rights Reserved.
Additional Information
20
Copyright © TM Forum, 2008 All Rights Reserved.
NGOSS
 NGOSS
 New Generation Operation Systems and
Software
21
Copyright © TM Forum, 2008 All Rights Reserved.
Business Process Framework (eTOM)
Customer
Strategy, Infrastructure & Product
Strategy &
Commit
Infrastructure
Lifecycle
Management
Operations
Product
Lifecycle
Management
Operations
Support &
Readiness
Fulfillment
Assurance
Marketing & Offer Management
Customer Relationship Management
Service Development & Management
Service Management & Operations
Resource Development & Management
(Application, Computing and Network)
Resource Management & Operations
(Application, Computing and Network)
Supply Chain Development & Management
Supplier/Partner Relationship Management
Billing
Enterprise Management
Strategic & Enterprise
Planning
Enterprise Risk
Management
Financial & Asset
Management
Copyright © TM Forum, 2008 All Rights Reserved.
Enterprise Effectiveness
Management
Stakeholder & External
Relations Management
Knowledge & Research
Management
Human Resources
Management
22
Information Framework (SID)
Market / Sales
Market Strategy & Plan
Marketing Campaign
Contact/Lead/Prospect
Market Segment
Competitor
Sales Statistic
Product
Strategic Product
Portfolio Plan
Product Performance
Product Specification
Product Offering
Product Usage
Customer
Customer Order
Customer Problem
Applied Customer Billing
Rate
Customer Bill Collection
Customer Interaction
Customer Statistic
Customer SLA
Customer Bill
Customer Bill Inquiry
Service
Service Applications
Service Performance
Service Strategy & Plan
Service Specification
Service Configuration
Service Usage
Service Trouble
Resource
Resource Topology
Resource Performance
Resource Strategy & Plan
Resource Specification
Resource Configuration
Resource Usage
Resource Trouble
Resource Test
S/P Performance
S/P Bill
Supplier/Partner
S/P Interaction
S/P Order
S/P Problem
S/P Bill Inquiry
S/P Plan
S/P Product
S/P SLA
S/P Statistic
S/P Payment
Product
Customer
Sales Channel
Service
Service Test
Resource
Supplier / Partner
Enterprise
Common Business
Revenue Assurance
(Under Construction)
Copyright © TM Forum, 2008 All Rights Reserved.
Root
Party
Business Interaction
Usage
Project
Base Types
Location
Agreement
Policy
Time
23
Market / Sales
Management
Product Management
Product Strategy /
Proposition
Management
Channel Sales
Management
Product / Service
Catalog Management
Fulfillment
Product Performance
Management
Product Lifecycle
Management
Assurance
Billing
Customer Self Management
Customer
Information
Management
Collections
Management
Customer Contact, Retention & Loyalty
Order Mgt
Customer
QOS/ SLA
Mgt
Quotation
Engine
Service
Specification
Mgt
The TAM R2.0
Service
Inventory Mgt
SLA Mgt
Service
Design /
Assign
Service
Config Mgt
Service
Problem
Mgt
Customer Service /
Account Problem
Resolution
Service
Quality
Monitoring
& Impact
Analysis
Customer Billing
Management
Receivables
Management
Invoicing
Service
Performance
Mgt
Bill
Formatting
Service Rating
/ Discounting
Management
Resource Mgt
Resource Testing Mgt
Workforce
Mgt
Resource
Design /
Assign
Resource
Inventory
Mgt
Resource
Provisioning /
Configuration
Resource
Specification
Management
Resource
Logistics
Resource
Activation
Resource
Performance
Monitoring/
Management
Correlation
& Root
Cause
Analysis
Resource
Planning/
Optimization
Resource
Problem
Management
Resource
Status
Monitoring
Resource Domain
Resource
Data
Mediation
Arbitrage
Management
Billing Data
Mediation
Voucher
Management
Real-time
Billing
Management
Management (IT Computing, IT Applications, Network)
Integration infrastructure:
bus technology/ middleware / business process management
Customer Mgt
Oper Support & Readiness
Service Mgt
Corporate Sales
Management
Campaign Management
Supplier / PartnerManagement
Supply Chain Management
Partner Management
Enterprise Management
Revenue
Assurance
Management
Copyright © TM Forum, 2008 All Rights Reserved.
HR
Management
Financial
Management
Asset
Management
Security
Management
Knowledge
Management
Fraud
Management
24
NGOSS Contracts and the Frameworks

NGOSS (eg eTOM, and SID etc) can be used to define business
interactions across an intended interworking boundary, where the
Contract is positioned
 This boundary remains fixed as we move around the NGOSS
Lifecycle, but our focus on the interactions will shift
 In the Business View, we concentrate on process (eTOM) and
the information (SID) on which the processes act
 In the System View, process is a requirements influence, but a
solution/system architecture now forms, and system interactions
across the boundary are defined to support/realize the process
needs
 The TNA provides a structure for the system design
 TAM can be used to guide positioning of Contracts against
anticipated system “blocks” – TAM applications can be
characterized by the Contracts they provide/use
25
Copyright © TM Forum, 2008 All Rights Reserved.
Populating the Contract Model

A range of elements should be addressed in defining a
Contract
 NGOSS helps us by providing source material that can be
used for each specific Contract
 eTOM for the System Process definitions
 SID for the Entity definitions (SID also assists with
Policy definitions)
 TAM for the System Capability definitions (and System
Operation definitions at a more detailed level)
 TNA for the system environment supporting Contract
operation
 Each of these elements has a part to play in
characterising the required behaviour of the Contract
 In some cases, lower-level detail may be appropriate,
using NGOSS extensions
26
Copyright © TM Forum, 2008 All Rights Reserved.
TM Forum SDF program: Phase II Deliverables
TM Forum SDF Program Phase 2
TM Forum
Board strategic
indications
Other
TM Forum
work areas
SDF Reference Model
specification / enhancement
SDF
Overview
TR 139
Tool
selection
SDF Management
Requirements specification
TMF 519
Communication
to TM Forum
and Industry
SDF
Business
Agreement
Other Industry
Groups
contributions
SDF positioning respect to
related work in other Industry
Groups
TR 141
SDF
Industry Groups
Positioning Document
27
Copyright © TM Forum, 2008 All Rights Reserved.
TMF 519: SDF Business Agreement Requirements

Main characteristics
 The SDF Business Agreement document contains the Requirements that
define the Service Delivery Framework
o List of Business Objectives (19)
o List of Technical Objectives (12)
 SDF requirements are divided in categories (in line with Reference Model):
o Requirements on SDF Infrastructure (25)
o Requirements on SDF Managed Entities (9)
o Requirements on SDF Management (34)
o Requirements on SDF Functional Capabilities (10)
o Requirements on SDF support for Customer, Supplier and Partner relationships (6)

Some info on the “process” to define the BA
 Specific use cases were developed to define scenarios for SDF and gather


requirements
BA document obtained by active team commitment: more than 20 written
contributions, ad-hoc meetings / calls, debate and synthesis
The SDF team usage of a tool (IBM RequisitePro) for Requirements capture /
cross reference etc.
28
Copyright © TM Forum, 2008 All Rights Reserved.
Examples of SDF Requirements

Requirements on SDF Infrastructure
 The SDF Infrastructure MUST enable flexible mash up, composition and reuse of pre


packaged elements. It must be based on standard IT technology as used in other
industries to leverage economy of scale and maximize support.
The SDF Infrastructure MUST enable management of services as they are reused,
reprogrammed or composed.
The SDF Infrastructure MUST provide SDF Services catalogues and other repositories
(e.g. metadata), which contain all the elements (e.g. existing SDF Services, their
dependencies, etc.) available to build new SDF services.
Requirements on SDF Managed Resources
 Every SDF Service in the SDF MUST provide a “SDF Service Management Interface” to


enable exposure of all appropriate operation and management functions (such as, but
not limited to: configuration, performance management, retirement, fault handling,
versioning, monitoring, usage, etc.) of the SDF Service.
For the SDF to be able to manage a resource that is outside the scope of SDF, that
resource MUST be exposed as a SDF Service.
Requirements on SDF Management
 The SDF MUST support functionality to enable the management of the lifecycle of SDF


Services.
The SDF MUST enable the configuration of specific performance parameters for SDF
Services by means of the SDF Service Management Interface (SDF Service MI) (e.g.
driven by customer experience).
Requirements on SDF Functional Capabilities
 The SDF MUST support an explicit state model which enables the management of the
lifecycle of a SDF Service.
Copyright © TM Forum, 2008 All Rights Reserved.
29
Cooperation with Other Industry Groups
30
Copyright © TM Forum, 2008 All Rights Reserved.
Other Industry Group Liaisons
DMTF (Distributed Management Task Force)
• 3GPP (3rd Generation Partnership Program)
• ETSI (European Telecommunications Standards Institute)
• ITU-T International Telecommunications Union
• ATIS (Alliance of Telecommunications Industry Solutions)
• TTC (The Telecommunication Technology Committee)
• OIF (Optical Internetworking Forum)
• MEF (Metro Ethernet Forum)
• MSF (Multi-service Forum)
• OMG (Object Management Group)
• RosettaNet (eBusiness)
• QuEST (Quality Excellence for Suppliers of Telecommunications)
• TOG (The Open Group)
• IPDR (IP Detailed Record organization)
• OMA (Open Mobile Alliance)
• IMSF (IMS Forum)
Copyright © TM Forum, 2008 All Rights Reserved.
•
31