1TMN

P812 TMN Evolution

TMN Evolution - Service Providers’ Needs forthe Next Millennium

Contractors:BT DT PT TF TI

Start: January 98Finish: January 99

Presentation by Mike Slevin, TI/Broadcom

2TMN

P812 TMN Evolution 2TMN

P812 TMN Evolution

Review the role of TMN in the PNOs application of IT to run and manage networks and services

Identify issues regarding the refinement of TMN in the light of emerging network service providers needs including the use of COTS (commercial off the shelf) technology

Formulate recommendations which refine TMN principles and development approaches

Outline further studies that may be appropriate for the EURESCOM workplan to address.

Objectives

3TMN

P812 TMN Evolution

Electronic Trading Enterprise ResourcePlanning

InternetDumb network

Customer Access

Information Technology

EMS

NMS

SMS

Network

Forces of Change

4TMN

P812 TMN Evolution

Definitions

For us, TMN is the standardisation by ITU-Tand ETSI of telecoms management of classical Public Networks and Services

TMN Evolution is the process which strives to harmonise TMN with its environment. It is a non-deterministic process in the sense that nobody knows where it will end with anydegree of certainty.

TMN’s scope could contract or expand!

5TMN

P812 TMN Evolution

Current Status

Issues

Recommend-ations

P812 Landscape

SP/NONeeds

ArchitecturesStandards Technology

6TMN

P812 TMN Evolution

Telecoms Management Information

Status Analysis Intuitition

Issues

Guidelines Future Work Unresolved

P812 Work Flow

7TMN

P812 TMN Evolution

A short main report (D1)

Hardcopy annexes to D1

A set of web pages for future reference

Deliverables

8TMN

P812 TMN Evolution

P812 Web-site

Project Description

Internal Results

Visitors Centre

Useful Links

Participants

URL:http//www.broadcom.ie/evolution

9TMN

P812 TMN Evolution

Initial Questions (1)

1. What should the difference between network management and control be?

2. Can or should TMN be comm.- protocol independent (info models and architecture)?

3. Where should TMN be the chosen solution in the telecom management environment of a Telco?

4. Is TMN specific to Network Operators while SPs need their own technology?

10TMN

P812 TMN Evolution

5. Which (CORBA or Q3 or ?) is the best technology for integrating legacy and other network management systems?

6. Future of classical TMN interfaces (Q, X, F) : should specification continue, why?, by whom

7. Should TMN be limited to particular functional areas and levels of the management hierarchy?

8. What role for Web-based solutions in the management of telecoms networks?

Initial Questions (2)

11TMN

P812 TMN Evolution

AutomationEase of UseConsistent Company ApproachConsistent Global Approach

Reduced Development CostsReduced Operations Costs

Customer Access to ManagementUse of Generic IT Solutions

Use of Special Telecoms Solutions

1 2 3 4 5 1 2 3 4 5

not very not very

CurrentImportance

FutureImportance

Service Providers’ Management Needs Survey

Need

Complete and fax back to Broadcom or give to Mike

12TMN

P812 TMN Evolution

P812 participants need external involvement to produce high quality results

Industry and Universities can help, I hopeHow?Share your results and ideasP812 will be open - challenge our viewsSee Web pages: www.broadcom.ie/p812 (browse + e-mail us) Other ideas?

Final remarks

13TMN

P812 TMN Evolution

ANSI TMN Overview

Presented atIS&N ‘98

May 27, 1998by

Paul V. Hughes Chair - ANSI T1 TMN Subworking Group

14TMN

P812 TMN Evolution

ANSI TMN Overview

• T1M1.5 Subworking Groups

– TMN Architecture, Functions, Communications and Directory Services

– Management Services

– Electronic Access Ordering

– Security

– Liaisons/Contributions

15TMN

P812 TMN Evolution

ANSI TMN Overview

• TMN Architecture, Functions, Communications and Directory Services– Pressure to implement interconnection standards within

six months of publication.– How do we develop immediately implementable

standards?– What testing requirements, results and profiles do we

require?– What’s the process?

16TMN

P812 TMN Evolution

ANSI TMN Overview

• Management Services– Revise T1.256 to include both CMIP and IDL models

when stable– Identified areas for clarification and changes to correct

the Service Level Model– Developed draft standard on Alarm Resynchronization– Connection Management draft standard ready for

ballot. Will be revised when the ITU-T work is stable

17TMN

P812 TMN Evolution

ANSI TMN Overview

• Ordering And Billing Services– Newly formed– Develops and maintains generic information models for

the TMN X interfaces for pre-order, order and billing applications based upon business and protocol requirements received from the Ordering and Billing Forum(OBF) and the Electronic Communications Interconnection Committee(ECIC)

– Developing a Technical Report on ”Guidelines for CORBA/IDL modelling”

18TMN

P812 TMN Evolution

ANSI TMN Overview

• Security– Completed TMN Security Framework document for ITU-T SG 4

in collaboration with ETSI– developed ANSI standard for secure communications between

TMN applications called Application Based Security– Developed ANSI standard for TMN Q3 security– Developed TR-40 addendum for Electronic Bonding security

requirements– Looking at EDI security– Inclusion of security certificates in the TMN Directory schema

19TMN

P812 TMN Evolution

ANSI TMN Overview

• Liaisons/Contributions– ITU-T

• SG 4• SG 7• SG 11• SG 15

– ETSI– NMF– OMG– SIF

Telecom Service Providers OSS Needs

Dave MilhamBT

OSS Technical Collaborations

21TMN

P812 TMN Evolution

Service Provider Challenges

• Deregulation– from monopoly to regulated market

• cost and time matter– regulator sets policy and evaluates progress

• Competition– new market entrants– Move from traditional Telco

• splitting of Service Provider and Network Operator roles• new roles: retailer and broker for third party services• Challenge every historical assumption

• Move to new services: broadband and internetWould you buy a Telco?

22TMN

P812 TMN Evolution

Implications for Telco management(1)

• Move from technology to business focus • New wholesale retail models• Business process flow-through• Improved responsiveness to new service/technology

integration• Intelligence in network

23TMN

P812 TMN Evolution

Implications for Telco management(2)

• Integration of third party and internal S&NM systems• Move from make - to make, buy and integrate • Increased S&NM content in Partners / Suppliers products • Key Telco applications have long lifetimes >9years• So need to de-couple from IT Platform Churn• Design based upon mainstream IT tools

– OMT – Business Process Engineering– Multi protocol for different physical deployments

24TMN

P812 TMN Evolution

Possible Technology Outcomes

• CORBA and UNIX everywhere• Client server apps fails and disappear

– Redmond everywhere CORBA nowhere– Mainframes are back with new Java based 3270 terminals

• Industry resurrects TMN as least of all evils• SP stop guessing platform technology

– No technologists left– Build everything on a Workflow Process

infrastructure

25TMN

P812 TMN Evolution

Service Provider 2000Business Process Models Business Model

supplier value chain

Buy Make

Integrate

Integrationmodel

Implementation

System Design

Implementation

System Design

Focus on integration design using main stream tools - OMT

For a second opinion…

Ask me back next year!!