Interoperable Standards for Telecom e-Business

Interoperable Standards for Telecom e-Business

Jenny HuangAT&T Labs

OSS Architecture and Strategic [email protected]

Inte

rope

rabl

e St

anda

rds

for T

elec

om e

-Bus

ines

sIn

tero

p Su

mm

it Ju

ne 2

7, 2

002

Slide 2

Topics

! The Telecom e-Business challenges

! TMF and it’s collaboration with other industry groups

! Summary

Inte

rope

rabl

e St

anda

rds

for T

elec

om e

-Bus

ines

sIn

tero

p Su

mm

it Ju

ne 2

7, 2

002

Slide 3

The Telecom e-Business Challenges

! Delivering Services rather than Physical Products. Most existing e-business approaches have focused on delivery physical goods. Service providers deliver telecommunications services that place additional requirements on e-commerce solutions such as assurance, SLA agreements, and security.

! Service Lifecycle The sale of telecommunications services is a process that starts with the provisioning phase and continues in time for many aspects (e.g. billing, assurance). These aspects are not usually addressed by standard B2B solutions.

! Telecommunication Service complexity Telecommunications services have many attributes amongst which are: the location of the service end point, the technical specification of the service interfaces, the SLA and service wrap around a technical product, pricing packages and volume discount offers.

Based on Eurescom P1106 project feasibility studies

Inte

rope

rabl

e St

anda

rds

for T

elec

om e

-Bus

ines

sIn

tero

p Su

mm

it Ju

ne 2

7, 2

002

Slide 4

The Telecom e-Business Challenges (cont’d)

! Service Platform IntegrationThe complexity of the above lifecycle aspects of Telecom products, makes it more difficult to integrate B2B platforms with legacy systems and network management systems.

! General e-Business technologies can be leveraged but not enough

There is economic value in reusing the investment being made for many other industries, but Telecom specific context need to be introduced and interoperate with generic set of standards. Need knowledge base from both camps.

Inte

rope

rabl

e St

anda

rds

for T

elec

om e

-Bus

ines

sIn

tero

p Su

mm

it Ju

ne 2

7, 2

002

Slide 5

Backend Integration

Service Oriented Architecture

Core XML Format Standards

Business Document Definition

Business DictionaryStructure

Technical Dictionary Structure

Universal Business Dictionary Content

Vertical TechnicalDictionary Content

Process Coordination Framework

Directory Service

Process Description Language

Universal Business Process

Supply Chain Business Process

Business Model Specific Process

Messaging

Security

Trading Partner Agreement

Non e-business specific Standards, Protocols & Tools E-business Definitions, Format, Structure and Choreography

The E-business Software Elements

Adopted from Derek Coleman’s RosettaNet Conceptual Architecture

Backend IntegrationTechnology specific adapters, APIs, shared message bus

Service Oriented ArchitectureDevelopment platform for web-based services

Core XML Format StandardsBuilding blocks of XML content forbusiness document representation

Business Document DefinitionBusiness specific document structure built from

above business vocabularies





Process Coordination Frameworkcomplements messaging layer for loosely

coupled environment

Directory Servicestructure and access protocol for

registries and repositories for partner discovery

Process Description LanguageMethods to record repeatable business process

Universal Business Processbusiness process that areapplicable to all businesse.g. invoice, order

Supply Chain Business Processbusiness process that are specific to a givensupply chain.e.g. DSL ordering, provisioning

Business Model Specific Processbusiness process that

may inherit from universal or supply

chain but for diff. Business model e.g.

retailer, wholesaler, non-profit


Security

MessagingSession management and transaction coordination including reliable and secured messaging

Non e-business specific Standards, Protocols & Tools E-business Definitions, Format, Structure and Choreography

e.g. CORBA, MQseries adapters

e.g. J2EE.NET

e.g. ebXML TRPSOAP-RPC

e.g. XML DTDXML schema

XSLT

e.g. RosettaNet PIPOAG BOD

Schema for business dictionary structure. e.g. RosettaNet BDS

Common business vocabularye.g. ebXML core componentsRosettaNet bus. dictionary

Vocabulary and structure defined forspecific technology domain e.g. T1M1 tML and its artifacts for Telecom industry

e.g. WSDLXLANG

e.g. UDDISi2 Registry

e.g. UMLebXML BPSS

Dynamic creation and management of trading partner agreemente.g. ebXML CPPA

Security mechanism span thru all layers. E.gDigital signature, MIME enveloping,SSLv3, XML signature

E-BUSINESSElements

Telecom Domain SpecificVocabularies & Content

Telecom D

omain Specific

Requirem

ents & Services

Telecom Service

Specific Requirem

ents

Inte

rope

rabl

e St

anda

rds

for T

elec

om e

-Bus

ines

sIn

tero

p Su

mm

it Ju

ne 2

7, 2

002

Slide 7

Topics



! Summary

The voice of the OSS industry

What is TM Forum

! Non-profit global consortium providing leadership on Operations Support Systems (OSS) and management issues for the entire communications industry

– 350 members in 38 countries– Service providers, software and hardware suppliers, systems

integrators! Provides a collaborative environment where companies can

address critical business and technical issues ! Provides on-line access to industry information, market

conditions and technical solutions! Provides in person education,information and networking

opportunities– TeleManagement World Conference & Expo

We Serve the Entire OSS Value Chain

Solutions suppliers:•Systems integrators•Computer companies•Ex telco groups•Equipment suppliers

Middleware suppliers:•Platform suppliers Mediation suppliers•Database suppliers•Software components suppliers

Application/ system suppliers:•Point systems•Small solution suites

Service and network operators:• Fixed•Mobile•ISP•ASP•MVNO•Etc.

Value Chains are Fluid and Complex

! In the past, systems were deployed in a precise and known environment

Today! Partnerships get created, dissolved & re-created

in real time to meet market opportunities! New suppliers brought in to offer new

capabilities but must “fit in”! Mergers & acquisitions keep the situation in a

constant state of flux

Suppliers Service Provider Customers

Value Added

SoftwareSuppliers

EquipmentSuppliers/Systems

Integrators

NetworkTransport Operators

WholesaleBackbone Suppliers

AccessProviders

ContentProviders

Customers

What areas does TM Forum address?

! Provides strategic leadership and guidance on:– New Generation Operations Systems and Software (NGOSS)– Business Process Modeling and Automation– Shared Information and Data Modeling and Usage – Service Creation, Provisioning & Delivery– Web-Based Customer Care (E-Care) and Customer Relationship Management

(CRM)– Service Level Management & Quality of Service– Managing Next Generation Network Technologies (Broadband, Mobile, etc.)– Systems Integration and Implementation

! Enables collaborative, business-driven solutions based on commercially available software and industry standards

TM Forum - Industry Group Advisory BoardIGAB Objectives

– To provide a focal point within TM Forum for knowledge on the work of other Industry Groups who are particularly relevant to the work programme of TM Forum

– To build a picture of the working of TM Forum in relation to a selection of other Industry Groups. This picture to include both technical content and method of working

– To provide advice to TM Forum working teams on the developments available from other Industry Groups in order that TM Forum may take full account and build upon this work where appropriate

– To advise TM Forum Management (including Board of Directors) on benefits of working relationships with selected Industry Groups

– To provide a focus for the dissemination of TM Forum’s work into other Industry Groups in order that they may take full account and build upon this work where appropriate.

– To assist TM Forum in the operation of its work-programme evaluation in relation to the placement of work from other Industry Groups. For example, evaluation of new work proposals – as specified within TM Forum Project Charters.

Through all of the above help to build closer working relationships between selected Industry Groups in order to reduce duplication and confusion within the Information Communications Industry.Contact: Tony Richardson, TMForum Director Strategic Liaison, [email protected]

Backend Integration

Service Oriented Architecture

Core XML Format Standards

Business Document Definition





Process Coordination Framework

Directory Service

Process Description Language

Universal Business Process

Supply Chain Business Process

Business Model Specific Process

Messaging

Security


OMG DMTF

T1M1tML

GTDD

W3C

OSS/J

IETF ANSI ITU-T ETSI 3GPP

OpenGroup

ebXML

ebXML

IPDRT1M1/OBF

T1M1/DSL

TTC

A Rough Mapping of TMF/IGAB Industry Partners

FORM

Official liaison established

3GPP2

Overview TMF Next Generation Operations Systems and Software (NGOSS)

! What is NGOSS ?• A TMF initiative which provides a standardized integration framework

based on commercial off-the-shelf information technologies, instead of technologies unique to the telecommunications industry for OSS.

• NGOSS Program - Key Elements– Definition of business processes and process models – Definition of the systems framework upon which these business solutions will

be built– Definition of a shared information model that enables different NGOSS

components to interoperate – Practical implementations and multi vendor demonstrations via a series of

collaborative projects– Creation of a resource base of documentation, models and code to

support developers, integrators and users.

NGOSS Design Principles - Business Context

• OSS Operations and Interactions Driven by agreed Business Processes and Information Flows (Top-down Business Driven)

• Need Framework of Agreed Business Processes (TM Forum Business Process Model)

• Framework to support various Industry ‘Actors’ (TM Forum Business Reference Model)

• Need to support linkage (Flow - Through) of business processes to provide efficient business operation (TM Forum “Flow-Through / FAB” Model)

• Need detail of the Information Flows / Model associated with each Business Process (TM Forum “Spider Diagrams”)

NGOSS Design Principles - System Context

! Apply Commercial off-the-shelf (COTS) products! Technology neutral architecture! The separation of Business Process from the system functions.! Will be built from distributed components with well-defined contracts.! Integrated using a shared information model.! Service discovery via component trading on the basis of published

contracts.

Inte

rope

rabl

e St

anda

rds

for T

elec

om e

-Bus

ines

sIn

tero

p Su

mm

it Ju

ne 2

7, 2

002

Slide 17

Topics



! Summary

Inte

rope

rabl

e St

anda

rds

for T

elec

om e

-Bus

ines

sIn

tero

p Su

mm

it Ju

ne 2

7, 2

002

Slide 18

What Do We Need from Standards?

! Standards which support real business solutions

! Standards which can be placed within a bigger systems picture and understanding of the positioning of any standards in relation to other appropriate Industry Group efforts

! Standards which are ensured to have practical realizationpotential – e.g. linkage to the TMF Catalyst program

! Standards with the widest possible industry endorsement

Standards that are interoperable !!!

Inte

rope

rabl

e St

anda

rds

for T

elec

om e

-Bus

ines

sIn

tero

p Su

mm

it Ju

ne 2

7, 2

002

Slide 19

Backup Slides

Driven by eTOM Business Process Model

Fulfillment Assurance Billing

Marketing, Sales and Offer Management

Enterprise Management

Customer

Supplier/Partner Relationship Management

Resource Management and Operations

Service Management and Operations

Customer Relationship Management

InfrastructureLifecycleManagement

Supply ChainLifecycleManagement

ProductLifecycleManagement


Marketing, Sales and Offer Management

Enterprise Management

CustomerCustomer

Supplier/Partner Relationship Management

Resource Management and Operations

Service Management and Operations


InfrastructureLifecycleManagement

Supply ChainLifecycleManagement

ProductLifecycleManagement

AssuranceBilling


Customer Customer


MarketingFulfillment

SellingOrder Handling

ProblemHandling

CustomerQoS

ManagementRetention and Loyalty

Billing and Receivables Management

Customer Interface Management

CRM PlanningandDevelopment

Service Development and OperationsServiceConfiguration

Service ProblemManagement

Service QualityManagement

Service Planningand Development

ResourceInventoryManagement

Resource DataManagement

ResourceMaintenance andRestoration

ResourceProvisioning

Resource Element Management

Resource Planningand Development

Supplier/Partner Relationship ManagementSupplier/PartnerDevelopment

ContractDevelopment andNegotiation

DeploymentManagement

Value/ContractMeasurement /Management

Settlements andBillingManagement

Marketing, Sales and Offer ManagementMarketResearch andAnalysis

MarketManagementand Strategy

ChannelManagement

Sales Management

Product and OfferDevelopment andManagement

MarketingPromotion

MarketingCommunicationsand BrandManagement

Enterprise SupportBusinessStrategy...

FinancialManage ...

HR Management

Knowledge Manag ...

LegalManage ...

PR andCommunity Relatio ...

ProcessArchitecture Mana ...

Procurement Man ...

R&D/Technology ...

RealEstate M ...

Regulatory Manag ...

Stockholder Relati ...

Securityand FraudManage ...

Rating andDiscounting

BrokeringManagement

ProductManagement

and Development

Infrastructure and Capability Planning and

Delivery

Resource and Systems ManagementNetwork, Computing and Application Resource Infrastructures

Development andAutomation Support

Change andProblem Mgmt

I&C Planning

New I&CDevelopment

I&C PlanExecution

I&C Deployment

I&C Program Management

I&C PerformanceMeasurement &Reporting

Product andOffer Planning

Product Plan &PerformanceMeasurement &Reporting

Product PlanExecution

New ProductDevelopment

Offer and/orProgram Management

eTOM

Customer

Service Provider

Internal ProcessesE.g. Service andNetwork Mgmt

NetworkSuppliers

E.g. Element Mgmt Systems or Network

Equipment

Other Providers/Operators

Customer / Service Provider Service Provider / Service Provider

Service Provider / Network Provider

The Business Reference Model

Customer

Supplier-provided equipment and systems

Order

Pre-order

Configure

Assign

Test

Activate

Install

Account build

‘Fulfillment’

Service Provider B

‘Billing’‘Assurance’

Typical Fulfillment Activities

KEYActivityProcess/ Sub-process

Assurance& BillingProcesses

CUSTOMER

Sales

OrderHandling Service

Configuration

Network Element Mgmt& Network Elements

Inquiry

Pre-orderOrder Configure

NetworkProvisioningAssign/Activate

Test MgmtTest

NetworkInventory Mgt.

InstallSecurityAccess

12

3 Order

Request5 Assignment Request

6.

7

9 10

11 12

13 Test Request

14 15

16 Test Complete

17

18 Assignment Complete

Other SP

19 Service20

NetworkInventory Mgmt

Configure

Network Config& Routing

(Customer enabledreconfiguration)

3ASelling Order Status and

Completion

Order Status and Completion

Update

Network Config Request

Element Config & Complete

NetworkAccessCheck &

CompletePerform Test &Test Data

8Install

Request &Complete

Network Config. Complete

Complete

20A

4 Service

Inter/Intra Process/Sub-process Interface

Cross-FABDomain InterfaceNote: Security is shown in only one interaction,

but applies on every interface.

Service Fulfilment

Orders/CancelsChange requestsStatus inquiriesDesired Due Date

Estimated Due DateEstimated Price

Order StatusConfirmed Due date

Completion Notification

Sales

Order Handling- Accept orders

- Track order status

- Initiate service installation

- Determine pre-order feasibility- Prepare price estimate

- Complete order, notify customer- Initiate billing process

- Perform credit check- Request customer deposit

ServiceConfigurationActivate service

- Develop order plan

Register QoS & SLA terms, profiles

Customer

CustomerInterface

INPUTS OUTPUTS

CustomerInterface

PricesServicePlanning/Development

Options

Required reports QoS & SLA termsCompletionNotification

Invoicing/Collection

Credit CheckResponse

CreditBureau

Customer

Pre-service feasibility request

New/changed service notification and activation

Rating/Discounting

Special discounts Customer record details

Problem

OtherProvider(s)

Service order& status

Handling

- Establish SLA terms

FeasibilityDue date,Completion

ServiceConfiguration

NetworkPlanning/Development

Network Provisioning

Pre-order engineering/assignments

Service orders to other providers can either be generated by the ordering process or by the service configuration process, depending on the nature of the service ordered by the customer.

Management Management

OtherProvider(s)

Service order &status

Customer QoSManagement

CreditBureau

Credit CheckRequest

“Spider Diagram”

Ordering Process Example

Interoperable Standards for Telecom e-Business

Documents

Transcript of Interoperable Standards for Telecom e-Business